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. 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 ---------------------------------------------------------------------- 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
