Re: [OSR-devel] initrd cleanup

[Mark H. <hla...@at...>]

On Friday 12 October 2007 11:14:01 Gordan Bobic wrote:
> On Fri, 12 Oct 2007, Mark Hlawatschek wrote:
> > On Friday 12 October 2007 10:37:22 Gordan Bobic wrote:
> >>>>> I'm figuring that just adding rm -rf /lib/modules would help. I have
> >>>>> just added this to clean_initrd function. I'll have a look at what
> >>>>> else can be pruned after the GFS root is mounted.
> >>>>
> >>>> Hmm, this doesn't appear to have worked. I think it happens too late.
> >>>> I'd need to delete these before the new chroot is fired up. Any
> >>>> suggestion on where would be a good time to put this?
> >>>
> >>> The chroot environment is builded in
> >>> etc/rhel{4,5}/boot-lib.sh:create_chroot() There might be a more
> >>> intelligent way to create the chroot environment ;-)
> >>
> >> I think there may be a path issue here. What is the absolute path of
> >> /lib/modules in the initrd? I told it to mv /lib/modules /lib/modules2,
> >> and this doesn't appear to have happened in either the initrd nor in the
> >> real GFS root. :-/
> >
> > during the initrd init process, a new chroot environment is build to hold
> > the cluster services itsself. This has to be done to solve the
> > chicken-egg problem with rootfs depending on userspace cluster services.
> >
> > The new chroot environment ist created in the function create_chroot.
> > The default path for the chroot environment is /var/comoonics/chroot.
>
> Does that mean the /lib/modules, even during the initrd boot sequence,
> live under /var/comoonics/chroot/lib/modules?
Yes. 
>
> 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. 

Mark