Can I change the device of the "/" mount point at boot time.

[Tapan Chaudhari]

Hey,
   Thanks Deniel for the reply. I am aware of the fact you mentioned and
will keep in mind.
Well what i am trying to achieve is a simple thing to write an interception
driver to catch all the i/os going to a particular device, do some
manipulations on it and than let it through to the original device. Well as
you mentioned about geom, I have recently posted a mail on GEOM mailing list
as I could not find geom doing interception, the discussion is still on (You
can see the mails with subject line "Can GEOM be used to intercept the I/o
calls to an existing mounted device?"). Any sugessuions on interception
driver will be helpful?

As an interception driver is not possible, for time being I am going towards
the redirection concept which will require a reboot and changing the devices
on the mount points. For redirection driver, I dont think I will need geom.
I can directly create a new device. Rather I think it would be an overhead
using geom for a virtual device.
Any thoughts on both the issues?


Thanks,
--Tapan.

On Tue, Jul 15, 2008 at 9:02 AM, Daniel O'Connor <doconnor at gsoft.com.au>
wrote:

> On Tue, 15 Jul 2008, Tapan Chaudhari wrote:
> > Thank You Mateusz and Mike. I guess I am clear with my doubt now. I
> > will also go through the man pages to go into depth of it.
>
> The critical thing is that the loader must read the kernel (and modules,
> config etc..) from a disk the BIOS knows about.
>
> After that you can use any device the kernel knows about.
>
> As for the virtual device aspect - could you use a geom class to do you
> want? It's hard to say without an overview of what you actually want to
> achieve :)
>
> --
> Daniel O'Connor software and network engineer
> for Genesis Software - http://www.gsoft.com.au
> "The nice thing about standards is that there
> are so many of them to choose from."
>  -- Andrew Tanenbaum
> GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
>