[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[gomd-devel] <CW_TOOLS> new release (with oMFS checks)
From: |
Gian Paolo Ghilardi |
Subject: |
[gomd-devel] <CW_TOOLS> new release (with oMFS checks) |
Date: |
Sun, 24 Aug 2003 11:03:43 +0200 |
Hi Matt.
"cw_tools" now have two new functions to check if oMFS is configured and
started before doing any operation on files/directories.
Checkout the new cw_tools release... :)
I need comments/criticisms/hints...
Thanks.
<rejected>
----- Original Message -----
From: "Matthias Rechenburg" <address@hidden>
To: "Gian Paolo Ghilardi" <address@hidden>; "gomd developers mailing list"
<address@hidden>
Cc: "Roel Baardman" <address@hidden>; "Mirko Caserta"
<address@hidden>
Sent: Sunday, August 24, 2003 9:42 AM
Subject: Re: <CW_TOOLS> cluster-wide (un)installation for gomd/libgomd
> Hey JP, Matt again,
>
> a small feature request for those cw_tools ;)
>
> Since all those scripts are based on oMFS there are basically
> (about) 3, ..eh 4 situations :
> - oMFS is enabled and mounted
> - oMFS is enabled but not mounted
> - oMFS is disabled
> - running a non openMosix kernel -> no oMFS
>
> ....so to my mind those scripts should first check if it is an
> openMosix kernel. Then grep in /proc/filesystems if oMFS
> is supported by the kernel. After that they should "find" the
> oMFS mount-point
> (since it can be mounted everywhere, not only under /mfs)
> e.g. by grepping the df output.
> If oMFS is supported but not mounted the scripts also can create a
temporary
> mount-point, mount it, install gomd clusterwide and umount it again
> (since the user decides if he/she wants to use oMFS or not)
>
> ....... just to make this nice feature more robust ;)))
>
> enjoy,
>
> Matt