2.4 kernel style boot using pivot_root (RFC)
Jakub Bogusz
qboosh at pld.org.pl
Fri Mar 8 13:15:44 CET 2002
On Fri, Mar 08, 2002 at 01:10:55PM +0100, Michal Moskal wrote:
> On Fri, Mar 08, 2002 at 12:52:56PM +0100, Jakub Bogusz wrote:
> > On Fri, Mar 08, 2002 at 12:43:37PM +0100, Michal Moskal wrote:
> > > On Fri, Mar 08, 2002 at 12:33:48PM +0100, Jakub Bogusz wrote:
> > > > On Fri, Mar 08, 2002 at 12:15:53PM +0100, Michal Moskal wrote:
> > > > > 6) directory to put old root in, could be created automagicly by bsp,
> > > > > we would have to mount root read-write, create the directory,
> > > > > and in stage 2 remove it and mount root read-only. But I guess this
> > > > > isn't very bright idea (to mess with writing root before fsck
> > > > > has a chance to run).
> > > >
> > > > Somebody wrote at news:pl.comp.os.linux that in some distribution
> > > > (RedHat or Mandrake) there is persistent empty /initrd directory,
> > > > and when he removed it, system boot failed. Guess why :)
> > > >
> > > > This may be an answer - but I think it's at least a little nasty...
> > >
> > > Having "unused" directory in / is like asking for truble.
> > > But if it's in /var/lib/bsp/initrd, then nobody will remove it.
> >
> > But it will be inaccessible if /var isn't on root filesystem (and it
> > isn't rare case) so... it must be something on root... in /etc?
>
> Right.
>
> Maybe /lib or /boot ?
Not /boot - I thought about it before I wrote "/etc", but /boot can be on
separate fs too (and during boot only bootloader can access it, using
BIOS to disk read operations). Maybe if it would be mounted in initrd
- but it would require more devices, possibly more drivers and... more
problems :)
--
Jakub Bogusz
More information about the pld-devel-en
mailing list