On Sun, Jul 10, 2005 at 08:46:38PM -0700, David N. Lombard wrote:
> Daniel Widyono wrote:
> >Never mind, I can't edit live cramfs, for some reason vi reports it as
> >read-only file even though filesystem shown through mount command is rw.\
>
> The nature of the cramfs beast is that it's read-only
Daniel Widyono wrote:
Never mind, I can't edit live cramfs, for some reason vi reports it as
read-only file even though filesystem shown through mount command is rw.\
The nature of the cramfs beast is that it's read-only. Period.
You need to copy the tree to disk, edit the needed files, and r
Never mind, I can't edit live cramfs, for some reason vi reports it as
read-only file even though filesystem shown through mount command is rw.
So, I was able to add USELOGGER=1 to kernel append line to make logs more
verbose, but I can't modify the initrd to add debugging of my own. I now
get:
That's what I thought/hoped, I do this for floppy images all the time.
Didn't know if cramfs was any different. What I don't know is why the FAQ is
so ... wrong.
Dan W.
> You should be able to mount your initrd.img after you decompress it:
--
Hey Dan:
You should be able to mount your initrd.img after you decompress it:
cp /tftpboot/initrd.img /tmp
cd /tmp
mv initrd.img initrd.img.z
gunzip initrd.img.z
mount -o loop initrd.img /mnt
Then you can modify the files to your hearts content. After you're
done:
umount /mnt
gzip -9 initrd.im
