From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Nigel Roles" <nigel@9fs.org>
To: 9fans@cse.psu.edu
MIME-Version: 1.0
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: Quoted-printable
Subject: Re: [9fans] undocumented fs config options?
Message-ID: <3AF90041.3117.2E7770AE@localhost>
In-reply-to: <20010509041059.A94A6199E7@mail.cse.psu.edu>
Date: Wed,  9 May 2001 08:30:57 +0100
Topicbox-Message-UUID: 9bf92546-eac9-11e9-9e20-41e7f4b1d025

I believe the sntp option is also undocumented....

If you enter the config 

ipsntp <address>

the fileserver will periodically set the clock from an sntp server
running on the machine with the given address. This allows
a variety of clock sources to be used, rather than relying on
something attached to the fileserver.

The configuration I use is an ARC Galleon Rugby clock receiver
connected to the cpu server, a small daemon to read the clock
and set the rtc, and sntpd to serve time to whomever requires it.

> On Tue May  8 11:20:27 EDT 2001, anothy@cosym.net wrote:
> > in reading through /sys/src/fs/worms and the file
> > server source, there seem to be two undocumented
> > device types: r and x.
> > 
> > x is Devswab - i believe this bit-swaps whatever's
> > on the physical disk, presumably for moving a file
> > system between different-endian servers. correct?
> 
> yes, 'x' does the non-trivial swap between big and little
> endian filesystem formats. this allowed us to move our old
> sony jukeboxes from a big-endian mips magnum to a little-endian
> pc. since then we've copied the data off the sonys and
> turned them off.
> 
> > 
> > i'm not clear on r; it seems related to be the same
> > as w, but for optical disks (described in
> > port/portdat.h as "scsi video drive"), or l with no
> > label (l is described as "scsi video drive
> > (labeled)"). in the examples, r, like l, is only
> > used within a j device to describe the unmountable
> > platters. it seems either r or l is required in the
> > device3 section of a j definition; fsconfig(8)
> > makes no mention of that.
> 
> my understanding is that 'r' and 'l' only differ in that
> with 'l' one block is reserved on the platter for a label.
> 
> > 
> > can l or r be used on regular disks? what's the
> > difference between r and w devices?
> > -=CE=B1.
> 
> i believe 'r' and 'l' devices can only be used as the third
> part of a 'j' device. there is no individual 'init' routine for
> 'r' and 'l' devices, it's part of the 'j' initialisation.
> 
> that's not to say it might be possible to concoct a filesystem
> specification with 'r' or 'l' devices not associated with a
> jukebox that would pass the configuration parsing, but it wouldn't
> work.