Naturally the nature of virix shall remain /diskless-
oriented\.
However, the feature would include support for
OpenGFS within the kernel/images and for the HOST to
be configured to automatically accept certain remote
storages (a designated virix-especial mountpoint on
CLIENT) on client connect. This will all be more
possible with initrd support, within which (beside the
network stuff) the code would reside to immediately
export [ex. /virixshared] and of course the backend
(which currently only shuts down and services mosix)
would listen for these upon connection in accordance
with how HOST was configured and the CLIENT code
should echo a signal over to HOST prior to CLIENT
shutdown so that HOST can sync and data doesn't
disappear.
This 1) Increases availability by increasing the
number and distribution of fs 'pressure points' 2)
Increases speed for the same reason 3) Is what GFS was
made for (to some extent).
DEPS:
1. Further conf work by mg.
2. The initrd move by lv.
3. Backend exploration and soil tilling by lv.
ETFA:
15 weeks.
STAT:
Prepatory investigation by mg.
Being put aside for more urgent conf script work.
XXX
Logged In: NO
Unofficially assigned to me.
Can I be an admin?
=P
XXX