9srv Manual Collection/plan9/fsconfig(8) | 9srv Manual Collection/plan9/fsconfig(8) |
---|
config device
nvram device
filsys name device
ip ipaddr
ipgw ipaddr
ipmask ipaddr
ipauth ipaddr
ipsntp ipaddr
ream name
recover name
allow
readonly
noauth
noattach
copyworm
copydev from-dev to-dev
halt
end
The configuration information is stored in block zero on a device whose device string is written in non-volatile RAM. The config and nvram commands identify the device on which the information is recorded. The config command also erases any previous configuration.
The filsys command configures a file system on device and calls it name. Name is used as the specifier in attach messages to connect to that file system. (The file system main is the one attached to if the specifier is null; see attach(5)).
The rest of the configuration commands record IP addresses: the file server's address (ip), the local gateway's (ipgw), the local authentication server's (ipauth), the local subnet mask (ipmask), and the address of a system running an SNTP server (ipsntp). Ipauth is no longer used. If the server has more than one network interface, a digit may be appended to the keywords ip, ipgw and ipmask to indicate the interface number; zero is the default.
For the recover command, the named file system must be a cached WORM. Recover clears the associated magnetic cache and initializes the file system, effectively resetting its contents to the last dump.
Allow turns off all permission checking; use with caution.
Readonly disables all writing to all devices. This is useful for trying dangerous experiments.
Noauth disables authentication.
Noattach prevents attachs.
Copyworm will copy a file system named main to one named output, block by block, and loop. It knows how to read a fake worm file system.
Copydev will copy the device from-dev to the device to-dev. block by block, and panic.
Halt will cause the server to immediately exit and reboot.
The various configuration commands only record what to do; they write no data to disk. The command end exits config mode and begins running the file server proper. The server will then perform whatever I/O is required to establish the configuration.
Initialize a file server kremvax with a single disk on target 0 partitioned as a cached pseudo-WORM file system with the cache on the third quarter of the drive and the pseudo-WORM on the interleave of the first, second, and fourth quarters.
A complete and complex example: initialize a file server fsb with a single SCSI disk on target 0 for a scratch file system, a cached WORM file system with cache disk on target 2 and an optical-disc jukebox on targets 4 (robotics) and 5 (one optical drive), and another cached WORM file system with cache disk on target 3 and another optical-disc jukebox on a second SCSI bus at targets 3 and 4. Both jukeboxes contain 16 slots of optical discs. It has two Ethernet interfaces and can reach an SNTP server on the first one.
9srv Manual Collection/plan9/fsconfig(8) | Rev: Sun Dec 02 23:42:26 GMT 2007 |