Can I change the device of the "/" mount point at boot time.
tapan.list at gmail.com
Mon Jul 14 20:38:38 UTC 2008
Thanks a lot Mike. But the problem is the device I am talking about is
not the physical device. I am writing a driver which will create a virtual
device and all the i/os done on this virtual device will be ultimately
redirected to the original device. Correct me if I am wrong, but I guess the
loader will try to mount my new device on '/' and then load the modules into
the kernel. Since my driver would not be loaded at that point in time, it
will fail to even mount '/'. Am I right? Or can our drivers get loaded
before loader mounts '/' ?
On Tue, Jul 15, 2008 at 1:06 AM, Mike Meyer <mwm at mired.org> wrote:
> On Tue, 15 Jul 2008 00:48:42 +0530
> "Tapan Chaudhari" <tapan.list at gmail.com> wrote:
> > This is not exactly what I wanted. I will try to elaborate myself.
> > I am creating my own device which will act as a new boot slice which must
> > mounted as '/'. New device will process i/o calls and then redirect the
> > calls to original device of '/'. Now since I cannot unmount '/' and mount
> > again with my new device while system is running, I will have to find a
> > to tell kernel to mount my new device as '/' from next time onwards it
> > boots.
> > does anyone have suggestions on this?
> That's pretty much exactly what vfs.root.mountfrom does. Edit
> /boot/loader.conf to add a line:
> and you're good to go. The kernel will boot from your default root
> partition, then remount root using the value of that variable. I.e. -
> I set mine to "zfs:internal/root" to boot my system to a zfs root.
> Mike Meyer <mwm at mired.org>
> Independent Network/Unix/Perforce consultant, email for more information.
> O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
More information about the freebsd-hackers