Hi On Wed, Jan 19, 2005 at 02:45:51PM +0200, Lior Kesos wrote: > Let me refine my question ... > What controls the mounts that exist after you pivot_root it isn't done > through the fstab - because it's not synced in my case.
from what I know: /etc/fstab should be on the root filesystem (or even somewhere else) and definetly not needed for mounting the root filesystem. it is used later. Normally the init scripts fsck and mount files according to data from it. So I can't understand how /usr and /boot got mounted. The kernel is passed a parameter called 'root'. I believe that it is mounted just before running the init process and after the initrd . > So what can it be? > googlin' on > Lior. > > > On Wed, 19 Jan 2005 14:42:52 +0200, Lior Kesos <[EMAIL PROTECTED]> wrote: > > On Tue, 18 Jan 2005 07:58:04 -0800, Ranga Nathan wrote - > > >> umount: /initrd: device is busy > > >> Usage: init.new 0123456SsQqAaBbCcUu > > >> VFS: Cannot open root device "dasdb1" or unknown-block(0,0) > > > > >Seems like initrd has this baked in. I had similar problems when > > >changing the boot device. Would you perhaps have to do mkinitrd and > > zipl or the equivalent? > > > > I'm not sure what you mean by baked in I have a zipl that is run > > before this step and sets disk through it's paramfile flag. > > > > -- > > Peace Love and Penguins - > > Lior Kesos > > > > > -- > Peace Love and Penguins - > Lior Kesos -- Tzafrir Cohen +---------------------------+ http://www.technion.ac.il/~tzafrir/ |vim is a mutt's best friend| mailto:[EMAIL PROTECTED] +---------------------------+ ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
