Re: [Cooker] Why don't recent kernels build initrd?
| Hi all!
|
| I've noticed that since, uhmm, kernel-2.4.0-xx no initrd is automatically
| built when updating the kernel package. (Hmm, thinking of it, has it ever
| been built automatically?)
| Well, why is this? IMO it would be better if the initrd were built. As I
| imagine (without looking at the .spec), it's just one additional command
for
| the %post section:
|
| mkinitrd /boot/initrd-%{version}-%{release} %{version}-%{release}
|
| This should do it. And so that fixing of /boot/grub/menu.lst is not
| necessary when updating kernels, I've also added a symlink
|
| /boot/initrd - /boot/initrd-%{version}-%{release}.img
|
| This way, if only /boot/initrd is referenced in /boot/grub/menu.lst,
| /boot/grub/menu.lst doesn't need to be touched.
|
| I assume that something similiar also holds true for LILO, but I don't use
| LILO anymore, so I can't say for sure. I guess that a call to /sbin/lilo
| would be necessary if LILO is used.
|
No it is not that simple you must
- postuninstall : insert loop.o
- install the kernel
- postinstall : mkinitrd
- remove the loop.o
RedHat does it on its latest kernel if you want to get an easy spec file ..
Thomas
Re: [Cooker] Why don't recent kernels build initrd?
So sprach Andrej Borsenkow am Tue, Feb 27, 2001 at 09:11:15AM +0300: Hmm ... does not that happen when you install kernel-2.4.1-xxx RPM? I do not No, it does not. For sure a initrd is not built after a rpm -ivh kernel-2.4.2-xxmdk.i586.rpm, I don't know if it were built after a rpm -Uvh, but I don't upgrade my kernel - WAY to dangerous *G* Alexander Skwar -- How to quote: http://learn.to/quote (german) http://quote.6x.to (english) Homepage: http://www.digitalprojects.com | http://www.iso-top.de iso-top.de - Die guenstige Art an Linux Distributionen zu kommen Uptime: 14 hours 33 minutes
Re: [Cooker] Why don't recent kernels build initrd?
So sprach Thomas Mangin am Tue, Feb 27, 2001 at 08:59:44AM -: No it is not that simple you must - postuninstall : insert loop.o Well, I don't upgrade, for certain reasons :] But yes, you are right - but that's not big a deal, is it? Alexander Skwar -- How to quote: http://learn.to/quote (german) http://quote.6x.to (english) Homepage: http://www.digitalprojects.com | http://www.iso-top.de iso-top.de - Die guenstige Art an Linux Distributionen zu kommen Uptime: 14 hours 36 minutes
Re: [Cooker] Why don't recent kernels build initrd?
On 2/27/01 12:59 AM, "Thomas Mangin" [EMAIL PROTECTED] wrote: No it is not that simple you must - postuninstall : insert loop.o - install the kernel - postinstall : mkinitrd - remove the loop.o RedHat does it on its latest kernel if you want to get an easy spec file .. Yeah, but obviosuly it *can* be done, and as yourself confirmed, RedHat does do it - so the original question still applies - why isn't it done by Mandrake? Harry
[Cooker] Why don't recent kernels build initrd?
Hi all!
I've noticed that since, uhmm, kernel-2.4.0-xx no initrd is automatically
built when updating the kernel package. (Hmm, thinking of it, has it ever
been built automatically?)
Well, why is this? IMO it would be better if the initrd were built. As I
imagine (without looking at the .spec), it's just one additional command for
the %post section:
mkinitrd /boot/initrd-%{version}-%{release} %{version}-%{release}
This should do it. And so that fixing of /boot/grub/menu.lst is not
necessary when updating kernels, I've also added a symlink
/boot/initrd - /boot/initrd-%{version}-%{release}.img
This way, if only /boot/initrd is referenced in /boot/grub/menu.lst,
/boot/grub/menu.lst doesn't need to be touched.
I assume that something similiar also holds true for LILO, but I don't use
LILO anymore, so I can't say for sure. I guess that a call to /sbin/lilo
would be necessary if LILO is used.
Alexander Skwar
--
How to quote: http://learn.to/quote (german) http://quote.6x.to (english)
Homepage: http://www.digitalprojects.com | http://www.iso-top.de
iso-top.de - Die guenstige Art an Linux Distributionen zu kommen
Uptime: 0 hours 31 minutes
RE: [Cooker] Why don't recent kernels build initrd?
Hmm ... does not that happen when you install kernel-2.4.1-xxx RPM? I do not
remember exactly how it was in 2.4.0 - and cannot find it anyway :-)
Or do you mean rebuilding from SPRM?
-andrej
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Alexander Skwar
Sent: Tuesday, February 27, 2001 1:54 AM
To: Mandrake Cooker Mailing List
Subject: [Cooker] Why don't recent kernels build initrd?
Hi all!
I've noticed that since, uhmm, kernel-2.4.0-xx no initrd is automatically
built when updating the kernel package. (Hmm, thinking of it, has it ever
been built automatically?)
Well, why is this? IMO it would be better if the initrd were built. As I
imagine (without looking at the .spec), it's just one additional command for
the %post section:
mkinitrd /boot/initrd-%{version}-%{release} %{version}-%{release}
This should do it. And so that fixing of /boot/grub/menu.lst is not
necessary when updating kernels, I've also added a symlink
/boot/initrd - /boot/initrd-%{version}-%{release}.img
This way, if only /boot/initrd is referenced in /boot/grub/menu.lst,
/boot/grub/menu.lst doesn't need to be touched.
I assume that something similiar also holds true for LILO, but I don't use
LILO anymore, so I can't say for sure. I guess that a call to /sbin/lilo
would be necessary if LILO is used.
Alexander Skwar
--
How to quote: http://learn.to/quote (german) http://quote.6x.to (english)
Homepage: http://www.digitalprojects.com | http://www.iso-top.de
iso-top.de - Die guenstige Art an Linux Distributionen zu kommen
Uptime: 0 hours 31 minutes
