From: Gordan B. <go...@bo...> - 2007-10-12 10:07:02
|
On Fri, 12 Oct 2007, Mark Hlawatschek wrote: > On Friday 12 October 2007 11:53:08 Gordan Bobic wrote: >> On Fri, 12 Oct 2007, Mark Hlawatschek wrote: >>>> Thus, in the initrd_cleanup, I would need to rm -rf >>>> /var/comoonics/chroot/lib/modules ? >>> >>> In my opinion it would be better to modify the create_chroot function. >>> Here, the files are copied from the initrd. We wouldn't need to copy >>> the /lib/modules. >> >> But wouldn't that only be useful for the disk based init root? I see this >> as an issue only for the ramdisk init root. Or does the init ramdisk make >> a new ramdisk root if there is no disk for init root? > > Yes is creates a new ramdisk root when there is no local disk assigned. Ah, OK. I misunderstood how it works. I thought the initrd is what sticks around. I didn't realise that there was a secondary init rd that gets created to carry the SSI start-up and tear-down. Gordan |