[RULE] RULE files not yet reloaded on Savannah?

[C David Rigby]

I have not seen my last post from earlier today yet (hopefully there are 
no mailing list problems this morning) but in it I wrote erroneously:

My procedure for a kernel upgrade is to download the necessary RPMs for 
the architecture in question (usually this includes the CPU-specific AND 
i386 RPMs for other packages as well).  For the example of my P5-100 
notebook w/ 40 MB of RAM, I run rpm -Fvh kernel-2.4.20-30.9.i586.rpm, 
immediately followed by doing the same with rpm -Fvh --nodeps 
glibc-common-2.3.2-27.9.7.i386.rpm, then glibc-2.3.2-27.9.7.i586.rpm.  I 
check the /etc/lilo.config file and run lilo.  Then I reboot, and 
upgrade the rest of the relevant i386.rpm packages.  I have not tried 
this recently on the really low-end system (486DX4-100, 16MB RAM).

This is (almost) the procedure I ran on the server, which is i686-based. 
  There is no glibc-2.4.20-30.9.i586.rpm, nor 
openssl-0.9.7a-20.2.i586.rpm.  Only the i686-based systems have a 
separate glibc & openssl packages.

So, for the pentium system:

rpm -Fvh kernel-2.4.20-30.9.i586.rpm, check /etc/lilo.conf, run lilo, 
reboot.  Then rpm -Fvh --nodeps glibc-common-2.3.2-27.9.7.i386.rpm, 
followed by glibc-2.3.2-27.9.7.i386.rpm, then everything else.

For the i686-system, dual-processor system:

rpm -Fvh kernel-smp-2.4.20-30.9.i686.rpm, immediately followed by doing 
the same with rpm -Fvh --nodeps glibc-common-2.3.2-27.9.7.i386.rpm, then 
glibc-2.3.2-27.9.7.i686.rpm, then openssl-0.9.7a-20.2.rpm.  I check the 
/etc/lilo.config file and run lilo.  Then, reboot and perform the same 
procedure for the remaining *i386.rpm updates.

CDR
C David Rigby wrote:
> The current kernel from RedHat updates is 2.4.20-30.9.  It is one of the 
> things that should be upgraded, since kernel bugs tend to have large 
> impact, particularly on multiuser systems.  I believe that the RH9 CDs 
> include kernel 2.4.8-something.
> 
> 
> Marco Fioretti wrote:
> 
>>> Marco & all,
>>>     
>>> The slinky-v0.3.96.iso & image files are on the test server here as 
>>> well, and the md5sums match those Michael gives for 
>>> slinky-v0.3.96.iso, slinky-v0.3.96.img, disk2.img, and pcmcia.img.
>>
>>
>>
>> OK, great!
>>
>>
>>> I am going to try to collect all of the relevant RPMs (updated RedHat 
>>> ones as well as third party ones, as applicable) and create an iso of 
>>> just those. So, since I have not gotten the complete install iso 
>>> finished, one can use slinky-v0.3.96.[img|iso] to perform a RedHat 
>>> install, then use rpm directly to update from the CD.  Not pretty, 
>>> but it should work.
>>
>>
>> Yes, this is good too, thanks. It also provides a way to RULE+RH9+updates
>> in parallel with your work.
>>
>> One (maybe paranoid) question: would the kernel upgrade be in this
>> scenario different by one on vanilla RH9 on new PC?
>>
>> Later,
>> Marco Fioretti
>>
>>
>>
>> _______________________________________________
>> Original home page of the RULE project: www.rule-project.org
>> Original Rule Development Site http://savannah.gnu.org/projects/rule/>> 
Original RULE mailing list: Rule-list at nongnu.org, hosted at http://mail.nongnu.org/mailman/listinfo/rule-list
>> 
>>
> 
> 
> _______________________________________________
> Original home page of the RULE project: www.rule-project.org
> Original Rule Development Site http://savannah.gnu.org/projects/rule/> 
Original RULE mailing list: Rule-list at nongnu.org, hosted at http://mail.nongnu.org/mailman/listinfo/rule-list
> 
> 


_______________________________________________
Original home page of the RULE project: www.rule-project.org
Original Rule Development Site http://savannah.gnu.org/projects/rule/
Original RULE mailing list: Rule-list at nongnu.org, hosted at http://mail.nongnu.org/mailman/listinfo/rule-list