🚀 go-pugleaf

In article <5790@jade.BERKELEY.EDU> edmoy@opal.berkeley.edu () writes:
>The main problem with ND is that on the server, the "disk" is just a huge
>file.  If the "file" gets trashed, preventing the client from booting, you
>can't poke around on the server side to figure out what's wrong, since it's
>just one huge data file and not a hundred odd Unix files in a Unix file system.
>The only way to fix the ND partition is to copy a good one on top of it.
>Particularily in an environment where users are not all computer science
>majors, it too often occurs that users think that if the system doesn't
>respond for 10 seconds, it's time for L1-A (Reboot key sequence).  This often
>trashes the ND partition, and the client is dead until someone can fix it.
>
WRONG!
I know this doesn't belong in comp.sys.mac but then again neither does
mis-information. ND partitions can be treated like file-systems. See
ND(4p). In brief, you can use /dev/ndl* (the server side of an ND
partition) to run mkfs/fsck/mount....though the server should only
do this when the client is halted.

-Len


ARPA:len%spar@decwrl.dec.com	UUCP:decwrl!spar!len	BELL:(408) 732-2343
USPS:MS 32-930 1601 Technology Drive, San Jose, CA 95110-1397
Schlumberger Technologies ATE will disavow any knowledge of my opinions.