kernel presentation at ILUG on Sat.
James Sissel
James.Sissel at labone.com
Mon May 5 17:41:24 CDT 2003
Thanks. Now I understand why my compile with reiserfs as a module wouldn't
boot.
-----Original Message-----
From: Charles Steinkuehler [mailto:charles at steinkuehler.net]
Sent: Monday, May 05, 2003 11:46 AM
To: James Sissel
Cc: kclug at kclug.org
Subject: Re: kernel presentation at ILUG on Sat.
James Sissel wrote:
> Thank you, Charles. It was an excellent presentation.
>
> One part I missed. How did you uncompress and mount the initrd? I'd like
> to take a look at my current one. If I modified it how would I recompress
> it back into an .img?
The initial ramdisk images are simply gzipped filesystem images, so you
can gzip or gunzip as appropriate to go between the .img format used to
boot and the "raw" format you can mount with the loopback option.
<Snip>
To uncompress and mount an initial ramdisk file, then re-create a new
initial ramdisk image (from a handy RH7.2 system):
[root at falcon boot]# cd /boot
[root at falcon boot]# gunzip <initrd-2.4.9-13.img >/tmp/image
[root at falcon boot]# mount -o loop /tmp/image /mnt
...<edit ramdisk image at /mnt as desired>...
[root at falcon boot]# gzip </tmp/image >initrd-2.4.9-13-new.img
...edit bootloader as desired (or manipulate filenames) to use new
ramdisk image. If you're using lilo, remember to run lilo at the
command prompt to update the block-map file. Grub users can simply reboot.
--
Charles Steinkuehler
charles at steinkuehler.net
This transmission (and any information attached to it) may be confidential and is intended solely
for the use of the individual or entity to which it is addressed. If you are not the intended
recipient or the person responsible for delivering the transmission to the intended recipient, be
advised that you have received this transmission in error and that any use, dissemination,
forwarding, printing, or copying of this information is strictly prohibited. If you have received
this transmission in error, please immediately notify LabOne at the following email address:
securityincidentreporting at labone.com
More information about the Kclug
mailing list