make rpm target

make rpm target

Post by Josh » Thu, 28 Nov 2002 14:33:30



        Using the "make rpm" target under 2.4.18, the binary RPM ends up
with a kernel that lacks the auto version number. The rpm is named appropri
ately, but the kernel version simply doesn't match the resultant package name.
        For example, a "make rpm" generated package might wind up with th
e name kernel-2.4.18test-3.i386.rpm. After installing this rpm, an rpm -q
 shows "kernel-2.4.18test-3". However, once booted into the new kernel, un
ame -r returns only 2.4.18test (no trailing -3).
        In attempting to use this kernel RPM in an unattended installation th
e most obvious quirk is that the kernel line generated for grub.conf is appa
rently parsed from the RPM package info and no matching kernel exists in /boot.
        Possibly just a 2.4.18 bug but I thought I'd see if anyone else had n
oticed this behavior.

-josh

 
 
 

1. Making qla2200 ignore node name of the target device

I have a question regarding qla2200 behaviour on Solaris 8
platform.

By default the qla2200 driver assigns the SCSI target ID
of a device depending on the port name (WWPN) and
node name (WWNN) of the target.

I want to know if there is any way by which qla2200 driver
can be made to assign the SCSI tartget ID depending only on
the port name (WWPN) of the target.

-- Regards
   Mayur

2. AnalogX Proxy / Loopback Error

3. problems with making multiple targets

4. ccd driver and aha2940 driver where?

5. making multiple targets with make

6. Default font problem

7. Changing RPM target Directory?

8. Open source advocacy letter

9. fix for RPM build target under newer versions

10. RPM build target fixes

11. iptables: rule with RETURN target just after a rule with ACCEPT target

12. Target 0: Target not connected

13. iptables: rule with RETURN target after a rule with the ACCEPT target