RE: [Cooker] kernel install issues
> > Well, adding some data to this fire, I just upgraded to kernel-2.4.7-11 > and links were correctly made. However, the install process seems to > need of perl-MDK-Common to reload LILO. Perl-MDK-common is required by drakxtools since a couple of builds back Well, first perl couldn't find > some *.pm of this package (yes, I installed it). Yes, mcc is badly broken as of now. I have not yet checked the latest build (1.1.6-2mdk) but previous is no go. Second, it started to > cry wild that it couldn't find what bootloader I had (Grub btw). Looks like outdated initscripts. /proc/partitions changed due to devfs. > > As a matter of fact it is a lot easier to use grub if you know it. At > least, it a lot much easier to forget checking up the boot > process/scripts before you boot a new kernel. > Does grub finally work reliably on reiser with tail conversion? Last time I tried it cried loudly that stage2 is not sector-aligned. -andrej
Re: [Cooker] kernel install issues
Well, adding some data to this fire, I just upgraded to kernel-2.4.7-11 and links were correctly made. However, the install process seems to need of perl-MDK-Common to reload LILO. Well, first perl couldn't find some *.pm of this package (yes, I installed it). Second, it started to cry wild that it couldn't find what bootloader I had (Grub btw). Well, I have a manually redacted menu list to avoid "surprises" and have an nearly all-weather boot process. Boot went smooth and the kernel is working perfectly the last 12 hours. As a matter of fact it is a lot easier to use grub if you know it. At least, it a lot much easier to forget checking up the boot process/scripts before you boot a new kernel. Ektanoor SI Reasoning wrote: >I have had this problem with every kernel upgrade > [...] >
Re: [Cooker] kernel install issues
You are not the only one. Before I found out it was a fluke in the dev package that screwed up my rebooting, I thought it had something to do with the kernels due to the error LILO spewed out. On Wednesday 08 August 2001 10:59 pm, you wrote: > I have had this problem with every kernel upgrade > > the links to config, system.map and vmlinuz are not > being linked to the new kernel when installed. I have > to do this manually. Also initrd.img is not created > (and therefore also not linked). If there is a lilo > script that is supposed to run, it obviously fails but > does not warn the user. This means that any > unsuspecting user will have their system not boot > properly after an upgrade! > > Am I the only person experiencing this? If so, how can > I correct this? > > = > SI Reasoning > [EMAIL PROTECTED] > gnupg/pgp key id 035213BC > > __ > Do You Yahoo!? > Make international calls for as low as $.04/minute with Yahoo! Messenger > http://phonecard.yahoo.com/
