Index: trunk/minix/man/man8/MAKEDEV.8 =================================================================== --- trunk/minix/man/man8/MAKEDEV.8 (revision 9) +++ (revision ) @@ -1,53 +1,0 @@ -.TH MAKEDEV 8 -.SH NAME -MAKEDEV, DESCRIBE \- make/describe device files -.SH SYNOPSIS -.B MAKEDEV -.RB [ \-n ] -.IR key " ..." -.br -.B DESCRIBE -.RI [ device "] ..." -.SH DESCRIPTION -.B MAKEDEV -may be used to create the device files normally found in the -.B /dev -directory. The -.I key -arguments are simply the names of the devices you want. -.B MAKEDEV -knows about all supported devices and will create them in the current -directory with the proper owner and mode. For many devices -.B MAKEDEV -will not only create the device you want, but also the devices related -to it that you will probably want too. Naming one floppy device will -create all floppy devices for the same drive for instance. -.PP -Call -.B MAKEDEV -without arguments to see a list of keys that it understands. Then use -the -.B \-n -flag to make the script echo the commands it will execute the next time -when you call it without that flag. -.PP -The special key -.B std -must be given alone to -.BR MAKEDEV . -This key will create all standard devices. -.PP -The command -.B DESCRIBE -will give you a one-line description of a given device. It will by -default list all devices in -.BR /dev . -.SH "SEE ALSO" -.BR dev (4), -.BR mknod (8). -.SH BUGS -.BR MAKEDEV "'s" -eagerness to create devices may cause many "File exists" errors from -.BR mknod . -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) Index: trunk/minix/man/man8/add_route.8 =================================================================== --- trunk/minix/man/man8/add_route.8 (revision 9) +++ (revision ) @@ -1,78 +1,0 @@ -.TH ADD_ROUTE 8 -.SH NAME -add_route, del_route \- configure IP routing. -.SH SYNOPSIS -.B add_route -.RB \-g -.RI gateway -.RB [ \-d -.RI destination -.RB [ \-n -.RI netmask " ]]" -.RB [ \-I -.RI "ip device]" -.B del_route -.RB [ \-o "]" -.RB [ \-D "]" -.RB \-g -.RI gateway -.RB [ \-d -.RI destination "]" -.RB [ \-n -.RI netmask " ]]" -.RB [ \-I -.RI ipdev "]" -.RB [ \-v "]" - -.B del_route -.RB \-i -.RB [ \-D "]" -.RB \-g -.RI gateway -.RB \-d -.RI dst -.RB [ \-n -.RI netmask "]" -.RB [ \-I -.RI ipdev "]" -.RB [ \-v "]" - - -.SH DESCRIPTION -.de SP -.if t .sp 0.4 -.if n .sp -.. -.B Add_route -and -.B del_route -are used for manual maintenance of routes in the IP routing table. - -.SH OPTIONS -.TP -.B \-g -.I gateway -specifies the gateway IP address to use. -.TP -.B \-d -.I destination -specifies the destination(s) reached via this gateway. -.TP -.B \-n -.I netmask -specifies a netmask when the destination is a net. -.TP -.B \-I -.I "ip device" -specifies the ip device. -.SH "SEE ALSO" -.BR irdp (8), -.BR pr_routes (8). -.SH AUTHOR -.I Add_route.c -was created August 7, 1991 by Philip Homburg. -This manual page by A. S. Woodhull, last revised 13.02.96. Added -alias for del_route 17.11.05. - - - Index: trunk/minix/man/man8/adduser.8 =================================================================== --- trunk/minix/man/man8/adduser.8 (revision 9) +++ (revision ) @@ -1,43 +1,0 @@ -.TH ADDUSER 8 -.SH NAME -adduser \- add a new user to the system -.SH SYNOPSIS -\fBadduser \fIuser group home-dir\fR\fR -.br -.de FL -.TP -\\fB\\$1\\fR -\\$2 -.. -.de EX -.TP 20 -\\fB\\$1\\fR -# \\$2 -.. -.SH EXAMPLES -.EX "adduser ast other /usr/ast" "How user ast could be added" -.EX "adduser bin operator /usr/src" "How user bin could be added" -.SH DESCRIPTION -.PP -.I Adduser -adds a new user to the system by making new entries in -.B /etc/passwd -and -.B /etc/shadow -for the new user, creating a new home directory, and copying the contents -of the template home directory -.B /usr/ast -into it. The user-id of this new user will be the first free number not less -than 10. The password is initially empty, the full name must be set, and -the shell is the Bourne Shell, -.B /bin/sh . -Use -.I passwd , -.I chfn , -and -.I chsh -to change. -.SH "SEE ALSO" -.BR login (1), -.BR passwd (1), -.BR passwd (5). Index: trunk/minix/man/man8/backup.8 =================================================================== --- trunk/minix/man/man8/backup.8 (revision 9) +++ (revision ) @@ -1,52 +1,0 @@ -.TH BACKUP 8 -.SH NAME -backup \- backup files -.SH SYNOPSIS -\fBbackup\fR [\fB\-djmnorstvz\fR] \fIdir1 dir2\fR -.br -.de FL -.TP -\\fB\\$1\\fR -\\$2 -.. -.de EX -.TP 20 -\\fB\\$1\\fR -# \\$2 -.. -.SH OPTIONS -.FL "\-d" "At top level, only directories are backed up" -.FL "\-j" "Do not copy junk: \fI *.Z, *.bak, a.out, core\fR, etc" -.FL "\-m" "If device full, prompt for new diskette" -.FL "\-n" "Do not backup top-level directories" -.FL "\-o" "Do not copy \fI*.o\fR files" -.FL "\-r" "Restore files" -.FL "\-s" "Do not copy \fI*.s\fR files" -.FL "\-t" "Preserve creation times" -.FL "\-v" "Verbose; list files being backed up" -.FL "\-z" "Compress the files on the backup medium" -.SH EXAMPLES -.EX "backup \-mz . /f0" "Backup current directory compressed" -.EX "backup /bin /usr/bin" "Backup bin from RAM disk to hard disk" -.SH DESCRIPTION -.PP -\fIBackup\fR (recursively) backs up the contents of a given directory and its -subdirectories to another part of the file system. -It has two typical uses. -First, some portion of the file system can be backed up onto 1 or more -diskettes. -When a diskette fills up, the user is prompted for a new one. -The backups are in the form of mountable file systems. -Second, a directory on RAM disk can be backed up onto hard disk. -If the target directory is empty, the entire source directory is copied -there, optionally compressed to save space. -If the target directory is an old backup, only those files in the target -directory that are older than similar names in the source directory are -replaced. -\fIBackup\fR uses times for this purpose, like \fImake\fR. -Calling \fIBackup\fR as \fIRestore\fR is equivalent to using the -r option; -this replaces newer files in the target directory with older files from the -source directory, uncompressing them if necessary. The target directory -contents are thus returned to some previous state. -.SH "SEE ALSO" -.BR tar (1). Index: trunk/minix/man/man8/badblocks.8 =================================================================== --- trunk/minix/man/man8/badblocks.8 (revision 9) +++ (revision ) @@ -1,34 +1,0 @@ -.TH BADBLOCKS 8 -.SH NAME -badblocks \- put a list of bad blocks in a file -.SH SYNOPSIS -\fBbadblocks \fIblock_special\fR [\fIblock\fR] ...\fR -.br -.de FL -.TP -\\fB\\$1\\fR -\\$2 -.. -.de EX -.TP 20 -\\fB\\$1\\fR -# \\$2 -.. -.SH EXAMPLES -.EX "badblocks /dev/hd1 " "Handle bad blocks on \fI/dev/hd1\fP" -.EX "badblocks /dev/hd3 310 570 1680 " "Three bad blocks on \fI/dev/hd3\fP" -.SH DESCRIPTION -.PP -If a device contains bad sectors, it is important to not have them -allocated to important files. This program makes it possible to collect -up to 7 bad blocks into a dummy file, so they will not be allocated for a -\&'real\&' file. -When the program starts up, it asks for a list of bad blocks, unless -they are provided as arguments. -Then it creates a file whose name is of the -form \fI.Bad_xxxxx\fR, where \fIxxxxx\fR is a pid. -.SH "SEE ALSO" -.BR readall (1). - -.\" -.\" $PchId: badblocks.8,v 1.2 1998/07/27 19:47:04 philip Exp $ Index: trunk/minix/man/man8/boot.8 =================================================================== --- trunk/minix/man/man8/boot.8 (revision 9) +++ (revision ) @@ -1,524 +1,0 @@ -.TH BOOT 8 -.SH NAME -boot \- from power on to the login prompt -.SH DESCRIPTION -.de SP -.if t .sp 0.4 -.if n .sp -.. -At power on the machine reads the first sector of the boot device into memory -and executes it. This bootstrap code loads -.BR /boot/boot , -the MINIX 3 Boot Monitor. The monitor loads the kernel binaries from -.BR /boot/image , -or the newest file in -.B /boot/image -if it is a directory. -.PP -The MINIX 3 system is now running, the different tasks initialize themselves -and control is transferred to the last one, -.BR init . -.PP -.B Init -is the grandparent of all MINIX 3 processes, it is responsible for starting -login processes on each terminal, but first it runs -.BR /etc/rc . -.PP -.B /etc/rc -checks the state of the system and starts daemons. First it sets the -keyboard translation to the mapping in -.B /etc/keymap -if present, followed by a call to -.BR readclock (8) -to set MINIX 3 time from the hardware clock. Next the file systems are checked -if necessary and the -.B /usr -file system is mounted. -.PP -The system is now ready for multiuser startup, -.B /etc/rc -calls -.B /usr/etc/rc -that cleans out /tmp, /usr/tmp, and resets or cycles log files by running -.BR /usr/etc/daily , -starts the -.BR update (8) -and -.BR cron (8) -daemons, and initializes the network services. -.B /etc/rc -finally runs -.BR /usr/local/etc -to initialize the system in a site or host dependent way. -.PP -.B Init -reads -.B /etc/ttytab -and starts a -.BR getty (8) -for each enabled terminal line to allow a user to log in. -.SH OPTIONS -.TP -.B bootopts=\-s -The value of the boot variable -.B bootopts -is passed to -.BR /etc/rc . -If it contains -.B \-s -then the system will run a single user shell before continuing with multiuser -startup. (Note that one normally uses -.B boot \-s -instead of setting -.BR bootopts .) -.TP -.B bootopts=\-a -This flag tells that -.B /etc/fstab -must be ignored. The system asks for a device to use as /usr instead. This -will also be done if the root device is not as mentioned in -.BR /etc/fstab . -.TP -.B bootopts=\-f -Force a file system check, even if the system was shut down properly. (Do -this once in a while to be sure about the state of the file systems.) -.TP -.BI servers= program\fR[,\fIprogram\fR...] -Names the special servers that must be started in /usr/etc/rc. The setting -.BR "servers=inet" -will start the TCP/IP server. -.SH "BOOT ENVIRONMENT" -Many features of the drivers inside the kernel are controlled by settings in -the boot environmenti, like -.B bootopts -above does for -.BR /etc/rc . -The values of these variables are usually colon or comma separated -numbers configuring the driver. -.B "DPETH0 = 300:10" -tells the DP ethernet driver to use I/O address 0x300, interrupt request -10, and the default memory address (0xD0000, values may be omitted) for the -first ethernet board. (Note that IRQ 2 is redirected to IRQ 9 on AT's and -PS/2's, so use 9 if a device is jumpered for 2.) -.PP -Variables that are special to both the monitor and the kernel are described -in -.BR monitor (8). -This section lists extra variables or variable settings: -.TP -\fBc\fIn\fR = \fBat\fR | \fBbios\fR | \fBesdi\fR | \fBxt\fR | \fBaha1540\fR | \fBdosfile\fR | \fBfatfile\fR -Choose the driver that is to be used as controller -.IR n , -in order: IBM/AT (classic AT or newer IDE), BIOS (any disk), ESDI -(some PS/2s), IBM/XT, Adaptec 154x, MINIX 3 under DOS "file as disk", -FAT file system "file as disk". -By default -.B at -is used on AT bus systems, -.B bios -on PS/2s and XTs, and -.B dosfile -when running under DOS. -Most drivers are present in the kernel as distributed, but may be taken out -by modifying -.BR /usr/include/minix/config.h . -See -.BR controller (4). -(An XT should always use the BIOS driver, not the XT driver, because BIOS -calls are cheap on an XT. The XT driver can be used on AT machines with an -old XT controller.) -.TP -\fBDPETH\fIn\fR = \fBon\fR | \fBoff\fR -Turn an ethernet board on or off. The driver is by default in "sink" mode -for all boards. The sink mode allows one to use the driver without an -ethernet board installed. The driver will play /dev/null for that device, -i.e. nothing comes in, and anything send out is dropped on the floor. If -the board is turned on then the driver will use it to send out packets, if -it is turned off then the driver will fail for that board. -.PP -.if n .ta \w'DPETHn = I/O-addr:irq:mem_addr:mem_size'u+2m -.if t .ta \w'\fBDPETH\fIn\fR = \fII/O-addr\fR:\fIirq\fR:\fImem_addr\fR:\fImem_size\fR'u+2m -\fBDPETH\fIn\fR = \fII/O-addr\fR:\fIirq\fR:\fImem_addr\fR:\fImem_size\fR (WD80x3) -.br -\fBDPETH\fIn\fR = \fII/O-addr\fR:\fIirq\fR:\fB0\fR (NE2000) -.br -\fBDPETH\fIn\fR = \fII/O-addr\fR:\fIirq\fR:\fIflags\fR (3c503) -.RS -Set the I/O address (hex), IRQ (decimal), memory address (hex), memory -size (hex), or flags (hex) of the -.IR n -th -ethernet board and turn it on. By default they are configured as -280:3:D0000 and 300:5:C8000 with the memory size set to 2000, 4000, or 8000 -depending on the type of board found. -For the Western Digital cards the IRQ must be what the board expects, -but the memory address is programmed into the board by the driver. -The SMC EtherEZ board, a WD8013 successor, has only 8K -memory. This confuses the driver, so you need to explicitly specify the -board size as being 2000. -The memory address and size have no meaning for the Novell ethernet boards, -but the address may be explicitly set to zero to indicate that the board -.B is -a Novell ethernet board. -For the 3Com 3c503 the third parameter are flags, with the low bit indicates -that the on-board tranceiver must be used if 0 (thin ethernet), or that an -external tranceiver is used on the AUI port if set to 1. -The IRQ is software settable, and must be specified as 2 (XT), 3, 4, 5, -or 9 (AT). The memory address is set on the board by jumpers. The driver -does not support I/O mode for the 3c503. -(Note the little differences between board types. For the 8003/8013 and -NE1000/NE2000 the IRQ is fixed and the memory address variable, for the -3c503 the IRQ is variable and the memory address is fixed, but need not be -specified. Messy.) -.RE -.TP -\fBDPETH\fIn\fB_EA\fR = \fIe0\fR:\fIe1\fR:\fIe2\fR:\fIe3\fR:\fIe4\fR:\fIe5\fR -Set the ethernet address of the -.IR n -th -ethernet board. The address is normally obtained from the ethernet board, -so only in exceptional circumstances is this setting ever needed. (Use the -address of the main server if you want a career change.) -.TP -\fBAHA0\fR = \fII/O-addr\fR:\fIbus-on\fR:\fIbus-off\fR:\fItr-speed\fR -Configure the Adaptec 154xA SCSI host adapter to use the given I/O address -(hex), Bus-on time (decimal), Bus-off time (decimal) and transfer speed -(hex). The default is 330:15:1:00. The default transfer speed is always -5.0 Mb/s (code 00) ignoring the jumper settings. -.TP -\fBaha1540-d\fIn\fR = \fIsleep-time\fR:\fItarget\fR,\fIlun\fR -Program SCSI disk -.I n -to have the given target and logical unit number. The target and lun -of a tape or other SCSI device may be changed by setting the -.BI aha1540-d n -variable that would be used had it been a disk. So tape device c0t7 can be -set to target 4, lun 1 with aha1540-d7=:4,1. -(The -.I sleep-time -parameter is present but ignored to be compatible with Minix-vmd.) -.TP -\fBdosfile-d\fIn\fR = \fIfile\fR -Tells the DOS virtual disk driver for disk -.I n -to use a given file as a disk. The file is a DOS file name that the -boot monitor must be able to open. -.TP -\fBfatfile-d\fIn\fR = \fIdriver:minor:file\fR -Tells the FAT virtual disk driver for disk -.I n -to use a given file as a disk. The -.I driver -parameter is the name of driver that handles the disk, and -.I minor -is the device number of the partition where the file is found. See -.BR controller (4) -for names and numbers. -The -.I file -argument is the path to the file from the root directory down. The driver -named must also be tied to a controller with a -.BI c n -variable, so that the FAT file driver can find it. -A handy way to find the proper minor number is to run -.B "ls\ \-l" -on the device where the file is found. As a example, we assume the most -common situation of a disk file on the first partition of the first drive -on an ATA (IDE) controller: -.SP -.in +5 -.ft B -.nf -c0 = fatfile -c1 = at -fatfile-d0 = at:1:/minix/minix.mnx -.fi -.ft P -.in -5 -.TP -.BR TZ " = " GMT0 -This sets the time zone the hardware clock is running in. -.B Readclock -uses this to correctly obtain the time of the clock. The timezone of the -system is set in -.BR /etc/profile . -This boot variable is normally not set, only a few UNIX die-hards who -don't care about the time Windows sees and don't want to change the clock -twice a year for daylight savings use this option. (Set Windows time to the -time zone of Casablanca to match.) -.SH "TCP/IP CONFIGURATION" -To use TCP/IP you need to run the -.B inet -server, and unless you are running standalone you have to enable the -ethernet driver. See the -.B servers -and -.BI DPETH n -boot variables above. The driver supports these ethernet cards: Western -Digital 8003, Western Digital 8013, SMC Elite Ultra 16, -Novell NE1000 and NE2000, 3Com Etherlink II (3c503). Many newer -variants of the WD8013, now under the SMC brand, may also work. -A common PCI reimplementation of the NE2000 using the Realtek 80 chipset is -also supported. Make sure it's just a 10 mbit device and that it has a -chip marked "RTL 8029". -.PP -You are likely to use TCP/IP in one of three situations: -.PP -.RS -Standalone with no connection to a network. -.SP -In a small network with no support from a "big" host. -.SP -Connected to a large network with address and name servers. -.RE -.PP -In each situation you need a different set of configuration files. -.SS Standalone -All you need is a name and an IP address. Suppose the name is "flotsam" -and the IP address is 192.168.0.1 from the private IP space, then this is -put in -.BR /etc/hosts : -.PP -.RS -.ta +\w'192.168.0.1'u+3n -192.168.0.1 flotsam -.RE -.PP -And this in -.BR /etc/dhcp.conf : -.PP -.RS -.nf -host 192.168.0.0/24 {}; -interface ip0 flotsam; -.fi -.RE -.SS "Small Network" -A network requires an ethernet driver. You need to enable one in - and you need to tell -.B inet -that it should use that driver by making -.B /etc/inet.conf -look like this: -.PP -.RS -.nf -eth0 DP8390 0 { default; }; -.fi -.RE -.PP -The second word (DP8390) must the name of the ethernet driver you've enabled. -It can also be seen among the drivers in the output of -.BR "ps ax" . -See also -.BR inet (8). -.PP -In a small network there may not be a DHCP server for MINIX 3 to obtain its IP -address and name from, so you need specify the ethernet address of your machine -and host names of all machines in the hosts and DHCP configuration files. -Suppose your machine is to be named "flotsam", and another machine in the -network is named "jetsam", and let's use network 192.168.0.0/24 again. The -file -.B /etc/hosts -now looks like this: -.PP -.RS -.ta +\w'192.168.0.1'u+3n -.nf -192.168.0.1 flotsam -192.168.0.2 jetsam -.fi -.RE -.PP -And -.B /etc/dhcp.conf -like this: -.PP -.RS -.nf -host 192.168.0.0/24 {}; -client 0:1:1b:a:68:ce flotsam; -.fi -.RE -.PP -Use -.B hostaddr \-e -to find out what the ethernet address of your network card is. (The address -above is an example.) -.PP -A host needs to have all hostnames used on your little network in its -host file. In the DHCP configuration you only need the client entry of the -system itself, but it may be useful to add all client entries to make them all -the same. -.PP -If one of the machines is always on when any of the others is, then you can let -it be a DHCP server. The other machines don't need a hosts or DHCP file -anymore. If flotsam is the server then its -.BR /etc/dhcp.conf -looks like this: -.PP -.RS -.nf -.ta +4m -host 192.168.0.0/24 { - DNSserver flotsam; -}; -client 0:1:1b:a:68:ce flotsam { option server; }; -client 0:0:c0:3a:12:10 jetsam; -.fi -.RE -.SS "Large Network" -In a network with a central network administration your machine's IP address -and name are given by the DHCP server. You don't need any configuration -files. If you want your machine to do more, like being a router or -something, then see -.BR inet (8) -on setting up more than one network interface. -.PP -.SS "Simpler configuration tools" -The -.BR dhcpd -and -.BR nonamed -daemons are complex little programs that try to obtain information about -their surroundings automatically to tell the machine what its place in the -network is. It should come as no surprise that there are simpler utilities -to configure a machine. On a memory starved machine it may even be wise to -configure a machine statically to get rid of the daemons. The first daemon, -.BR dhcpd , -can be replaced by: -.PP -.RS -.B ifconfig \-h -.I host-IP-address -.B \-n -.I netmask -.br -.B add_route \-g -.I gateway-IP-address -.RE -.PP -to set the IP address and netmask of the machine. Note that you can only -do this if the machine has a static IP address, or chaos will follow. Remove -.BR /usr/adm/dhcp.cache -if the DHCP daemon has run before. -.PP -The name daemon, -.BR nonamed , -can be replaced by an entry in -.B /etc/resolv.conf -that specifies an external name daemon: -.PP -.RS -.B nameserver -.I nameserver-IP-address -.RE -.PP -The -.B ifconfig -and -.B add_route -calls can be placed in the file -.BR /etc/rc.net . -Check -.B /usr/etc/rc -to see how -.BR /etc/rc.net -can be used to override running the normal series of network deamons. -Note that -.BR /etc/rc.net -is sourced, so you can use the same variables and functions that -.BR /usr/etc/rc -uses. -These changes undo all the efforts to make MINIX 3 TCP/IP -autoconfigurable. Make very sure that all the IP addresses are correct, and -that the IP address of your machine is unique. (Mistakenly using the -address of a main server will make all other machines look at your machine, -and will make all the users of all other machines look at you.) -.SH FILES -.TP 20n -/boot -MINIX 3 Boot Monitor. -.TP -/minix -Kernel image, or directory containing them. -.TP -/etc/rc -Basic system initialization. -.TP -/usr/etc/rc -Complete system initialization. -.TP -/etc/rc.net -Specialized network initialization. -.TP -/usr/local/etc/rc -Per site initialization. -.TP -/etc/hosts -Name to IP address mapping. -.TP -/etc/dhcp.conf -Network initialization. -.TP -/etc/resolv.conf -Name resolver configuration. -.SH "SEE ALSO" -.BR monitor (8), -.BR init (8), -.BR inet (8), -.BR loadkeys (8), -.BR readclock (8), -.BR fsck (1), -.BR fstab (5), -.BR update (8), -.BR cron (8), -.BR ttytab (5), -.BR getty (8), -.BR hostaddr (1), -.BR ifconfig (8), -.BR dhcpd (8), -.BR nonamed (8), -.BR tcpd (8), -.BR hosts (5), -.BR ethers (5), -.BR resolv.conf (5), -.BR inet (8). -.SH DIAGNOSTICS -.TP 5n -Checking File Systems. -If the system has crashed then -.B fsck -is called for the root and /usr file systems. It is wise to reboot if the -root file system must be fixed. -.TP -Finish the name of device to mount as /usr: /dev/ -The prompt for the -.B \-a -option, or if the name of the /usr file system has not been set in /etc/fstab. -You can type a device name, say -.BR fd0 . -.TP -Unable to obtain an IP address after 10 seconds. -TCP/IP misconfiguration. The DHCP daemon may have failed because the ethernet -address of the machine is not known to the DHCP server, the DHCP -configuration is not filled in properly, or the DHCP server can not be reached. -Either talk to your Network Administrator, or make a dhcp.conf -and a hosts file. -.TP -1.2.3.4 login: -If you see an IP address instead of a host name then the system failed to -translate the IP address. Either talk to your Network Administrator to -have the reverse address translation tables fixed, or make a hosts file. -.SH NOTES -The 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 networks can be used for -private networks. (This so-called CIDR notation names an IP address and -the number of bits in the network number. So 172.16.0.0/12 includes all -addresses from 172.16.0.0 to 172.31.255.255.) -RFC-1597 will tell you why private networks are good, and RFC-1627 why -they are bad. -.SH BUGS -Indefinite hangs are possible if I/O addresses or IRQ's are wrong. A driver -may babble about addresses and IRQ's, but that does not mean that what it -says is true, it may just be configured that way. It is very difficult to -find peripherals on a PC automatically, and MINIX 3 doesn't even try. -.SH AUTHOR -Kees J. Bot Index: trunk/minix/man/man8/checkhier.8 =================================================================== --- trunk/minix/man/man8/checkhier.8 (revision 9) +++ (revision ) @@ -1,29 +1,0 @@ -.TH CHECKHIER 8 -.SH NAME -checkhier \- check the directory hierarchy -.SH SYNOPSIS -.B checkhier -.SH DESCRIPTION -.de SP -.if t .sp 0.4 -.if n .sp -.. -.B Checkhier -checks a number of files and directories that make up the top level file -system hierarchy. The output of the command is a script that could be -applied to fix things like bad mode, wrong owner or group, etc. -.PP -The script should never be executed without checking. I might be better to -examine the differences oneself and to fix any problems by hand. -.PP -.B Checkhier -must be run by the superuser. -.SH "SEE ALSO" -.BR chmod (1), -.BR chown (8), -.BR hier (7). -.SH DIAGNOSTICS -The exit code is 0 if all checks out right, otherwise a script is output and -the exit code is 1. -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) Index: trunk/minix/man/man8/chown.8 =================================================================== --- trunk/minix/man/man8/chown.8 (revision 9) +++ (revision ) @@ -1,35 +1,0 @@ -.TH CHOWN 8 -.SH NAME -chown \- change owner -.SH SYNOPSIS -\fBchown [\fB\-R\fR] \fIowner\fR[:\fIgroup\fR] \fIfile\fR ...\fR -.br -.de FL -.TP -\\fB\\$1\\fR -\\$2 -.. -.de EX -.TP 20 -\\fB\\$1\\fR -# \\$2 -.. -.SH OPTIONS -.FL "\-R" "Change directory hierarchies" -.SH EXAMPLES -.EX "chown ast file1 file2" "Make \fIast\fR the owner of the files" -.EX "chown \-R ast:other dir" "Change the owner and group of all files in dir" -.SH DESCRIPTION -.PP -The owner field (and optionally group field) of the named files is changed -to -.I owner -(i.e., login name specified) and -.I group . -Alternatively, a decimal uid(gid) may be specified instead of a user name. -Only the superuser may execute this command. -.SH "SEE ALSO" -.BR chgrp (1), -.BR chmod (1), -.BR ls (1), -.BR chown (2). Index: trunk/minix/man/man8/cleantmp.8 =================================================================== --- trunk/minix/man/man8/cleantmp.8 (revision 9) +++ (revision ) @@ -1,65 +1,0 @@ -.TH CLEANTMP 8 -.SH NAME -cleantmp \- clean out a tmp dir -.SH SYNOPSIS -.B cleantmp -.RB [ \-d "[\fIlevel\fR]]" -.RB [ \-i -.IR file "] ..." -.BR \-\fIdays\fB | \-f -.RI [ directory " ...]" -.SH DESCRIPTION -.B Cleantmp -removes all files in each of the given directories and their subdirectories -that have not been accessed for at least -.I 'days' -days. Empty subdirectories are removed if their modified times are more -than -.I 'days' -days old. -.B Cleantmp -looks at days as humans do, i.e. they last from midnight to midnight. -Meaning that -.B cleantmp -1 /tmp -removes all files that were not touched after midnight last night. This may -be very helpful, because in many cases that big file that clogs up -.B /tmp -was created yesterday, but less than 24 hours ago. -.PP -The 'days' flag may be replaced by -.B \-f -causing -.B cleantmp -to remove all files in the directory no matter what age. Specifying zero -days doesn't work, because it is assumed to be a mistake. -.PP -.B Cleantmp -knows that files and directories that have a name starting with a '.' are -special and will not delete them or files within them if they are not at -least 14 days old. -.SH OPTIONS -.TP 5 -.BR \-d "[\fIlevel\fR]]" -Set the debug level to -.I level -(by default 1). Normally only errors are reported. Debug level 1 lists the -actions taken on standard error, level 2 also prints the file times used, -and level 3 makes -.B cleantmp -playact, i.e. nothing is really removed. -.TP -.BI \-i " file " -One or more -.B \-i -options name files to be ignored. Files are not removed if they are in the -list of ignored files by either a directory entry match, or a full pathname -match. This option is useful to keep things like named pipes that some -longlived programs foolishly put in temporary directories. -.SH "SEE ALSO" -.BR find (1). -.SH BUGS -Don't use '\fBcleantmp -1\fP' shortly after midnight. -.PP -It would be nice if one could delete files that are, say, 2 hours old. -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) Index: trunk/minix/man/man8/config.8 =================================================================== --- trunk/minix/man/man8/config.8 (revision 9) +++ (revision ) @@ -1,334 +1,0 @@ -.TH CONFIG 8 -.SH NAME -config \- configuring MINIX 3 tasks and servers -.SH DESCRIPTION -.de SP -.if t .sp 0.4 -.if n .sp -.. -MINIX 3 has a number of configuration files containing parameters that can -be changed to enable or disable a device driver, to change the number of -times a resource can be used, or to tune the performance of the system. -We will name the file that contains the parameter, the name of the -parameter, and the values it can be set to. Some comments are prefixed by -"8086" for MINIX 3 running in 16-bit real mode, "286" for 16-bit protected -mode, and "386" for 32-bit protected mode. -Configuration file names can be -.RI < file.h > -for a file in -.BR /usr/include/ , -or a simple file name for a file in -.BR /usr/src/ . -.PP -There may be several definitions for a parameter with only one that is -active. Which one this is is easy to find if you know that -.B "(\s-2CPU\s+2\ ==\ \s-2INTEL\s+2)" -is true, and -.SB _WORD_SIZE -equals -.B 2 -in 16-bit mode, and -.B 4 -in 32-bit mode. -.PP -.ti 2m -.RB < minix/config.h > -.br -This is the main configuration file for the MINIX 3. It contains lots of -boolean variables to enable or disable drivers and a number of parameters -that specify the sizes of system data structures: -.TP -.SB NR_PROCS -The number of slots in the process table, and thus the maximum number of -processes that can be run concurrently. Should be increased from the -default -.B 32 -if networking is enabled (add -.B 8 -for deamons), and if more users are using the system (add -.B 4 -for each active session). There are a lot of -loops in the kernel scanning the process table, so setting -.SB NR_PROCS -too high will slow things down a little bit, so don't overdo it. -.TP -.SB NR_BUFS -The number of disk buffers in the file system server. It is used to keep -frequently used disk blocks in memory. -.BR 8086 " & " 286 : -The default is -.BR 40 , -and that's about as high as it can be set. -.BR 386 : -The default is -.BR 80 , -which is best increased to -.B 1024 -if you can spare the memory. More will help, but the effect won't be as -pronounced as -.B 1024 -is more than enough to contain the working set of one active user. -.TP -.SB NR_CTRLRS -Number of tasks used for disk or tape controllers. By default 2, maximum 4. -You need a controller task for each device class to be handled through a -.BI /dev/c n "*" -set of devices. -.TP -.SB ENABLE_CACHE2 -If set to 1 allows the RAM disk to be used as a second level file system -cache. Any block that is evicted from the normal cache is both written to -disk (if dirty), and copied to the second level cache. If it is needed -again then the block is reloaded from the RAM disk if it is still there. -.BR 8086 : -Forget it, you don't have any memory for it. -.BR 286 : -Turn it on and set the boot environment variable -.B ramsize -to -.B 512 -if you have the memory. That's enough to contain the working set of -one active user, and is also the maximum FS can handle. -.BR 386 : -The installation scripts sets -.B ramsize -to -.B 1024 -if there is enough memory. Your first point of call is to compile a -new kernel with -.SB ENABLE_CACHE2 -off, -.SB NR_BUFS -set to a large value, and -.B ramsize -set back to zero. A normal block cache works much better than a two level -arrangement. -.TP -.SB ENABLE_AT_WINI -Enables the AT or IDE disk driver. (The IDE interface grew out of the old -AT disk interface.) Any run of the mill PC needs this driver. You need to -assign a driver like this one to a controller task using one of the -.BI c n -boot variables. See -.BR boot (8). -.TP -.SB ENABLE_BIOS_WINI -Enables the BIOS disk driver. The BIOS driver uses the system BIOS to read -or write disk blocks. -.BR 8086 : -The preferred disk driver for XT class machines. -.BR 286 " & " 386 : -Use a native driver if possible to avoid switching back to real mode to make -BIOS calls. Especially on the 286 this is a painful affair. -.TP -.SB ENABLE_ESDI_WINI -Enables the ESDI disk driver. Some PS/2 models have this disk. -.TP -.SB ENABLE_XT_WINI -Enables the XT disk driver. Useful for early IBM/AT machines that have XT -disks. In real mode it is best to use the BIOS driver. -.TP -.SB ENABLE_AHA1540_SCSI -Enables the Adaptec 1540 series SCSI driver. -.TP -.SB ENABLE_DOSFILE -Enable the "DOS file as disk" driver that is used when MINIX 3 is run from -MS-DOS to access a large file as a disk. -.TP -.SB ENABLE_FATFILE -Enable the "FAT file as disk" driver that interprets a FAT file system -to find a large file to use as a disk. This driver combined with a fast -native MINIX 3 disk driver is a better choice then the previous driver. (And -it works when MINIX 3 is not started from MS-DOS.) This is the last driver -that needs to be assigned to a controller task. -.TP -.SB ENABLE_SB16 -Enable the Soundblaster-16 audio driver. -.TP -.SB ENABLE_PRINTER -Enable the Printer driver. -.TP -.SB DMA_SECTORS -The size of the DMA buffer for drivers that use DMA or other drivers that -can only do I/O to a single chunk of memory. (BIOS, ESDI, XT, DOSFILE.) -Choose a number between -.B 1 -and -.B 128 -for the sector size of this buffer. The memory cost is twice this amount, -because of trouble getting it aligned in memory properly. A value of -.B 16 -is the minimum to work well, choose -.B 64 -if you have enough memory. -.TP -.SB NR_CONSOLES -Number of virtual consoles. By default -.BR 2 , -so you can have two login sessions that can be switched to by ALT-F1, -ALT-F2 or ALT-left/rightarrow. If you have an EGA screen then you can -specify up to -.B 4 -virtual consoles, for VGA you can have -.BR 8 . -It is best to choose one less to leave some video memory to keep text -scrolling fast. You really should read -.BR console (4) -on this. Note also the -.B console -boot variable, you can use it to put more characters on the screen, at -the cost of video memory. -.TP -.SB ENABLE_DP8390 -Master switch to enable the network drivers. They are required by the -network server, -.BR inet . -See -.BR boot (8) -for information on configuring network support. -.TP -.SB ENABLE_WDETH -Enable code for the WD8003 and WD8013 cards in the network driver. -.TP -.SB ENABLE_NE2000 -Enable code for the NE1000 and NE2000 cards. -.TP -.SB ENABLE_3C503 -Enable code for the 3Com Etherlink II (3C503). -.TP -.SB NR_PTYS -Number of pseudo terminals supported, by default -.BR 0 , -which disables the driver. Pseudo terminals are used for incoming network -logins by telnet or rlogin. One pty is needed per session. -.TP -.SB NR_RS_LINES -Number of RS-232 lines supported. By default -.B 2 -for a normal kernel, but -.B 0 -for a tiny kernel used for XT installation. You can save a bit of memory by -setting this parameter to zero if you don't need serial lines. -.PP -.ti 2m -.BR fs/const.h -.br -This file contains most of the parameters used by the file system code. -Most of these cannot be changed, with the exception of these four: -.TP -.SB NR_FILPS -Maximum number of open file descriptors for all processes combined. A "File -table overflow" error might indicate that this number must be increased. -.TP -.SB NR_INODES -Maximum number of in-use files for all processes combined. Like above a -"File table overflow" error may also indicate that this number should be -increased. In cases like these one usually doubles both parameters. (If -one table runs out then the other one is likely to run out also anyway.) -.TP -.SB NR_SUPERS -Number of file systems that can be mounted. Again a "file table overflow" -error is given if this table is full, but it will be produced by the -.B mount -command, so you know what's wrong in this case. -.TP -.SB NR_LOCKS -Number of active file locks by -.BR fcntl (2). -These locks are often used by programs that update a shared file, like mail -programs do with mail boxes. A "no locks available" error indicates that -this table has run out. -.PP -.ti 2m -.B kernel/bios_wini.c -.ti 2m -.B kernel/dosfile.c -.ti 2m -.B kernel/fatfile.c -.br -The number of disks each of these drivers can handle is specified by: -.TP -.B MAX_DRIVES -This parameter is set to -.B 4 -for the BIOS and "DOS file" drivers, and to -.B 2 -for the "FAT file" driver. It can be set as high as you need to allow for -more disks, or files as disks. (The "FAT" driver needs quite some memory per -disk, which is why it by default only allows 2 disks.) You will need to run -.BR MAKEDEV (8) -to create the extra disk devices in -.BR /dev/ . -.PP -.ti 2m -.B inet/inet_config.h -.br -The maximum number of TCP/IP networks is: -.TP -.B IP_PORT_MAX -Sets the maximum number of networks that can be defined in -.BR /etc/inet.conf . -.BR 8086 , -.BR 286 : -By default 2. -.BR 386 : -By default 4. -.PP -.ti 2m -.B inet/buf.c -.br -The number of 512 byte buffers allocated for data within the TCP/IP server is: -.TP -.B BUF512_NR -These buffers are a shared resource used by the server for any data it wants -to play with. For incoming data this number of buffers determines the time -packets are kept around, with each new packet evicting an old packet. It's -no big deal if packets get lost before a user process reads them, packets -get lost all the time. The only real problem is outgoing TCP data. The -default setting for -.SB BUF512_NR -allows up to four backlogged TCP streams, i.e. when data is output faster -then it is read. If more buffers are needed then one of the TCP connections -is shut down. When this happens you will see a "not enough buffers left" -error. This could happen for instance if a MINIX 3 web server is assaulted by -a browser that likes to open several connections to the server -simultaneously. The fix is to increase -.SB BUF512_NR -to allow more slow outgoing TCP streams. -.BR 86 : -The default of -.B 32 -buffers can be increased up to -.BR 64 . -(The "TCP window size" has been limited in 16-bit mode to keep the buffer -use by TCP down.) -.BR 386 : -The default of -.B 128 -can be increased to any value you like, but -.B 512 -seems to be more than enough. Minix-vmd uses 512 by default, and it seems -happy that way. -.SH "SEE ALSO" -.BR controller (4), -.BR usage (8), -.BR boot (8), -.BR MAKEDEV (8). -.SH NOTES -Associated with drivers there are device files to access the devices -controlled by the drivers that may have to be created. Let's simplify this -sentence: Type -.BR "ls /dev" , -note that there are only -.B c0* -and -.B c1* -devices, and only for two disks each. Some devices, like the audio devices, -are not even present. So if you enable a driver, or increase some limits, you -also need to use -.BR MAKEDEV (8) -in -.B /dev -to allow programs to talk to the drivers. -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) Index: trunk/minix/man/man8/cron.8 =================================================================== --- trunk/minix/man/man8/cron.8 (revision 9) +++ (revision ) @@ -1,165 +1,0 @@ -.TH CRON 8 -.SH NAME -cron \- clock daemon -.SH SYNOPSIS -.B cron -.RB [ \-d\c -.RI [ level ]] -.SH DESCRIPTION -The -.B cron -daemon executes tasks that must be repeated every now and then (cron jobs), -and tasks that must be run just once (at jobs). It is normally used to run -daily or weekly system maintenance scripts. What it needs to run and when -is specified in a number of "cron tables", or crontab files for short. -These tables are: -.PP -.RS -.nf -.ft B -/usr/lib/crontab -/usr/local/lib/crontab -/var/lib/crontab -/var/opt/\fIname\fP/lib/crontab\ \ \fR(Minix-vmd only)\fB -/usr/spool/crontabs/\fIuser\fP -.ft R -.fi -.RE -.PP -These files follow the usual pattern: One for the standard things, one for -local tasks per organization, one for tasks per system, and one crontab per -installed package. (Cron reads -.B /usr/lib/packages -to find names of installed packages, it doesn't just grab everything in -.BR /var/opt .) -The last set of files fall outside the normal pattern, they are per user -crontabs that one can create with the -.BR crontab (1) -command. The file names in -.B /usr/spool/crontabs/ -are login names of the file owners. -.PP -The format of a crontab file is described in -.BR crontab (5). -.SS "AT jobs" -.B Cron -also takes care of the execution of jobs issued by -.BR at (1) -that are found in -.BR /usr/spool/at/ . -Cron simply runs the AT job as if there were an "sh at-job" as a cron job at -the appropriate time under the user-id of the owner of the script. The -script takes care of the rest. See -.BR at (1) -for the details. -.SS "Job I/O" -Standard input, output and error are the same as cron's if the job is -started by the system crontabs or from package crontabs. This means that -output from system jobs usually ends up on the console and in the log file. -Output from personal cron jobs or at jobs are mailed to the owner of the -job. No mail is sent if the job is silent. -.SH OPTIONS -.TP 5 -[\fB\-d\fR[\fIlevel\fR]] -Set the debug level, by default 1. Makes -.B cron -print info on what it happens to be doing. Level 1 just tells about sleep -times and what job is executed, level 2 also shows the internal crontab -data on a table load. (With time fields translated to match those of -.BR "struct tm" , -see -.BR ctime (3).) -.SS SIGNALS -.B Cron -takes the following actions when sent one of the following signals: -.TP 12 -.B SIGHUP -Reload the crontab tables if they changed since the last time they were -loaded, and reexamine the AT job spool. Used by -.BR at (1) -and -.BR crontab (1). -.TP -.B SIGUSR1 -Increase the debug level by 1. -.TP -.B SIGUSR2 -Turn debugging off. -.SH ENVIRONMENT -.B Cron -sets the environment variables -.BR USER , -.BR LOGNAME , -.BR HOME , -and -.BR SHELL -to the user's login name (2x), home directory, and shell if a job is -executed for a given user. The working directory is set to the user's home -directory. Everything else is inherited from -.BR cron , -exactly as -.B cron -got it when it started. Note that commands are always passed to -.BR /bin/sh , -not to the user's shell. -.PP -System cron jobs are in principle executed with -.BR cron 's -environment, use -.B "\-u root" -or the crontab file -.B /usr/spool/crontabs/root -if you want to give root the same treatment as ordinary users. -.SH FILES -.TP 25n -.B /usr/lib/crontab -Main MINIX 3 crontab file. -.TP -.B /usr/local/lib/crontab -Local jobs for all systems in an organization. -.TP -.B /var/lib/crontab -System specific jobs. -.TP -.B /var/opt/\fIname\fP/lib/crontab -Per package jobs for Minix-vmd. -.TP -.B /usr/lib/packages -List of installed packages. -.TP -.B /usr/spool/crontabs/\fIuser\fP -Per user jobs. -.TP -.B /usr/spool/at/* -Jobs issued by -.BR at (1). -.TP -.B /usr/run/cron.pid -Process id of cron when cron is running. Used by -.BR at (1) -and -.BR crontab (1) -to send cron a hangup signal. -.SH "SEE ALSO" -.BR at (1), -.BR crontab (1). -.SH NOTES -A job is not reissued until a previous instance of it has exited. The next -time to execute is computed from the previous time it ran. If job issuing -lags behind on the system time then the next time to run it is computed from -the current system time. -.SH BUGS -.B Cron -doesn't like it if the system time is changed. If set forward then cron -will react when it next wakes up by running all jobs within the skipped time -once or twice before it catches up. Setting the clock backwards makes cron -play dead until the system time passes the old time. (Changing the system -time is bad idea anyway, and not just because of cron.) -.PP -Jobs that fall in the missing hour in a change to Daylight Saving Time are -skipped. Nothing is done in the extra hour on the change out of DST. -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) - -.\" -.\" $PchId: cron.8,v 1.3 2000/07/17 18:49:18 philip Exp $ Index: trunk/minix/man/man8/dhcpd.8 =================================================================== --- trunk/minix/man/man8/dhcpd.8 (revision 9) +++ (revision ) @@ -1,208 +1,0 @@ -.TH DHCPD 8 -.SH NAME -dhcpd \- dynamic host configuration protocol daemon -.SH SYNOPSIS -.in +.5i -.ti -.5i -.B dhdpd -.RB [ \-qar ] -.RB [ \-t [\fIlevel\fP]] -.RB [ \-d [\fIlevel\fP]] -.RB [ \-f -.IR configfile ] -.RB [ \-c -.IR cachefile ] -.RB [ \-p -.IR poolfile ] -.RI [ host " ...]" -.in -.5i -.SH DESCRIPTION -.de SP -.if t .sp 0.4 -.if n .sp -.. -.B Dhcpd -is a client and a server for the Dynamic Host Configuration Protocol. As a -client it collects DHCP data to configure the Ethernet networks with, and as -a server it answers DHCP queries from other machines. -.PP -This manual page describes the operation of -.BR dhcpd , -the associated configuration file is described in -.BR dhcp.conf (5). -(The latter, together with -.BR boot (8), -is of more practical value when it comes to getting a machine's networks -interfaces up and running. See the options section below for debugging DCHP -problems.) -.SS Initialization -On a normal startup, i.e. none of the -.BR \-q , -.BR \-a -or -.BR \-r -options are given, -.B dhcpd -determines what IP devices are present, and which of those are Ethernets. -For each network it looks for information in the configuration file as if -it were a server answering a query for that network. If any information is -found then the IP address is configured and the information stored in the -cache file. -.SS "Client Operation" -For each still unconfigured network a DHCP DISCOVER request is broadcast on -that network. If a DHCP OFFER reply is received then a DHCP REQUEST is -broadcast for the IP address offered, and if a DHCP ACK is received then the -network is configured and the information stored in the cache file. -.PP -If no reply is received then another query is sent after 4 seconds, and then -again after 8 seconds, doubling each time until 64 seconds. Every 64 -seconds thereafter a request is broadcast until a reply is received. -.PP -Once configured the DHCP lease, rebind and renew times are computed. At the -renew time a DHCP REQUEST is sent to the DHCP server to extend the lease. -Normally we get an answer and refresh our information, but if no reply is -received we wait for half the remaining time until the rebind time and keep -retrying and halving the remaining time. When the rebind time is reached -the DHCP REQUEST is broadcast to try and reach some other DHCP server. -Halving the remaining time again and again until the lease expires. At that -point we go back to square one and broadcast a DHCP DISCOVER. -.PP -If at any point a DHCP NAK is received we start over completely. After a -DHCP OFFER an ARP request is transmitted just before the DHCP REQUEST to -check if the address offered is already in use. If an ARP reply is received -before the DHCP ACK then after the ACK we send a DHCP DECLINE to the server -to tell that the address isn't what we want and again we start over. -.SS "Router Discovery" -The gateway offered by the DHCP server is made known to the TCP/IP server by -sending an ICMP router advertisement to the local interface with a short -lifetime and a low priority. Then up to three router solicitations are -broadcast three seconds apart to look for a router. If a router answers -with a router advertisement then we no longer worry about routing for that -interface. Otherwise the router information is refreshed before it expires -and another solicitation is sent out. This happens about twice an hour. -.SS "Server Operation" -Once all networks so marked are configured the daemon starts answering -requests by other machines or relaying requests to other DHCP servers. -DHCP requests are answered if information for a client -can be found in the configuration file, or if a free address can be found in -the pool file, or if a client rerequests an address it already owns. -.PP -If the daemon is both a server and a relay for a network then it will try -to answer a request and only relay if it has no answer. -.SS "Nothing more to do?" -If the daemon finds out that all networks have an infinite lease (configured -with a fixed address), there is no router information to keep warm, and -it isn't a server then it simply exits. -.SS "Asynchronous I/O?" -MINIX 3 doesn't have the asynchronous I/O that Minix-vmd has, so under MINIX 3 -the daemon only works with one network at a time. If it's stuck on the same -network for 32 seconds then that network is closed and another network is -tried for 32 seconds. This usually works ok as a client, but as a server it -can only handle one network. -.SH OPTIONS -.TP -.B \-q -Read and print the cache and pool file contents, showing DHCP information -for each network, and the IP addresses in the pool with lease times and -current/last owners of those addresses. -.TP -.B \-a -Add the named hosts (or IP addresses) to the pool file. -.TP -.B \-r -Remove hosts from the pool file. -.TP -.RB [ \-t [\fIlevel\fP]] -Set the test level (by default 1). At test level 1 all networks are seen as -unconfigured, will not be configured and no data will be put in the cache. -The program will just act as-if. At test level 2 the interfaces will not be -configured from the configuration file, the data must come from a remote -server. At level 3 the renewal, rebind and lease time will be 60, 120 -and 180 seconds. At level 4 these times will be 60, 60, and 120. At -level 5 these times will be 60, 60, and 60. These test levels are meant -to debug the DHCP client code, and are best used with a high debug level. -.TP -.RB [ \-d [\fIlevel\fP]] -Set the debug level (by default 1). At debug level 1 the program shows -Ethernet and IP addresses as they are determined or configured, DHCP -messages sent and received with little detail (one line per message), and -memory use. At debug level 2 each DHCP packet is decoded and shown in -detail. At debug level 3 device opens and closes are shown. The debugging -level may also be increased by 1 at runtime by sending signal -.BR SIGUSR1 -or turned off (set to 0) with -.BR SIGUSR2 . -.TP -.BI \-f " configfile" -Names the configuration file, by default -.BR /etc/dhcp.conf . -.TP -.BI \-c " cachefile" -Names the cache file, by default -.BR /usr/adm/dhcp.cache . -.TP -.BI \-p " poolfile" -Names the IP address pool, by default -.BR /usr/adm/dhcp.pool . -.SH "SEE ALSO" -.BR RFC-2131 , -.BR RFC-1533 , -.BR dhcp.conf (5), -.BR hosts (5), -.BR ifconfig (8), -.BR inet (8), -.BR boot (8), -.BR inetd (8), -.BR nonamed (8). -.SH DIAGNOSTICS -.TP -"'/etc/dhcp.conf', line ..." -The program exits on any configuration file error. You have to correct the -error and restart the program. -.TP -"No lease set for address ..." -There must be a lease time defined for addresses in the pool. Correct and -restart the program. -.TP -"###### declines #.#.#.# saying '...'" -A client with the given client identifier (usually 01 followed by the client's -Ethernet address) declines an IP address, hopefully with a message telling -why. This usually means that the IP address is already in use by another -host. This program, acting as a client, will tell what other host in its -message, but Windows has no additional info alas. -.TP -"Got a NAK from #.#.#.# [through #.#.#.#] saying '...'" -The server with the given IP address doesn't want us to have or keep the IP -address we were offered or are rerequesting. This could mean that the server -has forgotten about us and has given our address to another machine. This -is bad if our lease hasn't yet expired. There may be a relay involved, and -there may even be a text message with precise information. -.TP -"#.#.#.# offered by #.#.#.# is already in use by #:#:#:#:#:#" -We got an ARP reply for an offered address. We won't accept it, and send -out a DECLINE when we get an ACK. -.TP -"DHCP packet too big, ..." -You've got way to much information in the configuration file, more than fits -in a minimum size DHCP packet. (Notify the author if you really need to send -more information. He doesn't think anyone needs to.) -.TP -"Pool table is corrupt" -You will have to remove and refill the pool file. Chaos may ensue if -there are active clients and they don't use ARP to detect each other. -(Most do.) -.SH BUGS -There is no randomization of timers. Modern systems don't blink under the -load of several clients broadcasting a few packets in sync. -.PP -There is no extra time spent waiting for an ARP reply. It is assumed that -any IP stack will immediately respond, so that the DHCP server can't -possibly beat it at sending out an ACK. (The DHCP server has to commit the -lease to stable storage first anyway.) -.PP -Way more nonsense can be sent in a DHCP packet that MINIX 3 could do -something with, but nobody does so we don't bother. -.PP -DHCP was invented by a rabid gerbil on speed. -.SH AUTHOR -Kees J. Bot Index: trunk/minix/man/man8/dosminix.8 =================================================================== --- trunk/minix/man/man8/dosminix.8 (revision 9) +++ (revision ) @@ -1,287 +1,0 @@ -.TH DOSMINIX 8 -.SH NAME -dosminix, mkfile \- Running MINIX 3 under DOS -.SH SYNOPSIS -.RB "C:\eMINIX> " "boot disk0.mnx" "\0\0\0\0\0(Typical example)" -.br -.RB "C:\eMINIX> " "mkfile \fIsize disk" -.SH DESCRIPTION -.de SP -.if t .sp 0.4 -.if n .sp -.. -This text describes running MINIX 3 -.\" or Minix-vmd -under DOS. The DOS version -of the Boot Monitor, described in -.BR monitor (8), -grabs as much memory as DOS is willing to give, loads MINIX 3 into that memory -from the active partition of a "file as disk", and jumps to the MINIX 3 kernel -to let MINIX 3 take control. As far as DOS is concerned MINIX 3 is just a part -of the -.B boot.com -program. -.PP -In the example above -.B disk0.mnx -is the "file as disk". It is a file of many megabytes that is used by MINIX 3 -as a disk of four partitions. These partitions will normally be -.B /dev/dosd1 -through -.BR /dev/dosd4 , -with -.BR /dev/dosd0 -for the whole "disk". The Boot Monitor will set the -.B dosd0 -boot variable to the name of the disk (its first argument), the root file -system will be the active partition, usually -.BR dosd1 . -It is better to use the special name -.B bootdev -to indicate this device, usually in the setting -.BR rootdev = bootdev . -.PP -Once MINIX 3 is running it will operate the same as if started from a regular -disk partition until it is shut down. On shutdown from protected mode it -will return to the Boot Monitor prompt, and with the -.B exit -command you leave the Boot Monitor and return to DOS. Shutting down from -real mode will reboot the machine, just like when run from a disk partition. -(This more or less crashes DOS, but DOS is used to such abuse.) -.SS EMM386 -MINIX 3 can't run in protected mode (286 or 386 mode) if DOS is using a memory -manager like -.BR EMM386 . -You can either temporarily comment out EMM386 from -.BR CONFIG.SYS , -or you can press -.B F8 -on startup to bypass CONFIG.SYS. This is only possible with the later DOS -versions. -.SS "Windows 95" -Press F8 at startup to make the boot menu visible. Choose -"\fBCommand prompt\fP", or "\fBSafe mode command prompt\fP" to run DOS. -Use the "safe mode" if EMM386 is started in CONFIG.SYS. -.PP -Typing F8 at the right moment isn't easy, so you may want to change the way -Windows boots by editing the -.B MSDOS.SYS -file found in the root directory of your Windows system. This is alas not -trivial. -Open a window on your main drive, click on "\fBView\fP" and choose -"\fBOptions\fP." In the Options window choose "\fBView\fP" and enable -"\fBShow all files\fP". The MSDOS.SYS file should now be visible, among -several other hidden files. Right-click on the MSDOS.SYS icon, choose -"\fBProperties\fP" and disable "\fBRead-only\fP". Bring MSDOS.SYS into a -simple text editor such as Notepad. In the -.B "[Options]" -segment add the following lines (or change existing lines into): -.PP -.RS -.nf -BootMenu=2 -BootMenuDelay=5 -.fi -.RE -.PP -The first setting makes the Windows boot menu always visible, and the second -line changes the delay before booting to 5 seconds. Take care not to change -anything else, or things will go horribly wrong. Save MSDOS.SYS and exit. -Don't forget to make MSDOS.SYS read-only again, and also hide all the hidden -files again, unless you like it this way. -.SS "DOS compatibility box" -The 16-bit version of standard MINIX 3 can be run in real mode in a DOS box. -This is somewhat surprising, because it means Windows 95 simulates devices -like the keyboard, timer, and interrupt controller well enough to fool MINIX 3 -into thinking that all is well. Alas it doesn't work as well under Windows -NT. Keypresses get lost if you type to fast, and using the floppy -occasionally locks MINIX 3 up. This is a bit disappointing, because it is the -only way to run MINIX 3 under NT. Under Windows 95 one is better off -putting the system in DOS at boot and then to run MINIX 3 in protected mode. -.PP -One thing that is better under NT is that the Boot Monitor is able to get a -so-called "Upper Memory Block", thereby raising useful memory to about 750K. -Windows 95 however hogs leftover UMB memory in a process named -.BR vmm32 , -whatever that may be. To get -some of this memory you can put -.B "BOOT /U" -at the start of -.BR autoexec.bat . -The monitor will grab a 64K UMB if it can get it, and keep that memory safe -for use by MINIX 3 when it is later started from Windows. -.PP -The easiest way to start MINIX 3 is to give all MINIX 3 disk files the suffix -.BR MNX . -Doubleclick on the disk you want to run to make the "\fBOpen With\fP" window -appear. Click on "\fBOther\fP" and browse to the -.B BOOT.COM -program. Set the name of the .mnx files to "\fBMINIX 3 "disk" file\fP" in the -description box if you want everything right. In the future you can -just click on a MINIX 3 disk file to run it, you don't have to start a DOS -box first. (To make it perfect use "View", "Options", "File Types", choose -"MINIX 3 "disk" file", "Edit", "Change Icon", "Browse", select MINIX.ICO.) -.PP -When MINIX 3 shuts down it will try to reboot what it thinks is a PC. Windows -seems to assume that the DOS session has exited. Right-click on the -BOOT.COM program, "Properties", "Program", and enable "Close on exit" to make -the DOS box disappear automatically when MINIX 3 thinks it reboots. You may -also want to lock the font to -.BR 7x12 , -or any other font that isn't ugly. -.PP -MINIX 3 disk files are opened in a write-exclusive mode. A second MINIX 3 -session can only open it read-only, which may lead to a "can't open -root device" error. -.SS "Mkfile" -MINIX 3 disk files can be created or resized with the -.B mkfile -utility. Its two arguments are the size and name of the disk file. The -size is a number optionally followed by the letter -.BR k , -.BR m -or -.BR g -to specify kilobytes, megabytes, or even gigabytes. So the call -.PP -.RS -.B "mkfile 50m disk5.mnx" -.RE -.PP -will create a 50 megabyte file named -.BR disk5.mnx . -If the file already exist then it is shrunk or grown to 50 megabytes. No -data is lost if the file is grown. If the file is shrunk then only the data -that is cut off is lost. These features allow one to inrease the size of a -MINIX 3 /usr partition with the following recipe: -.PP -.RS -.ta +24n+2m -.nf -copy disk0.mnx disk0.new Copy the disk to disk0.new -mkfile 100M disk0.new Enlarge to 100 megabytes -boot disk0.mnx Boot the old "disk" -[ESC] Get the attention of the monitor -dosd5=disk0.new /dev/dosd5 becomes disk0.new -boot -\&... -login: root -.fi -.in +(24n+2m) -.ti -(24n+2m) -part Choose dosd5, move to the Size field of dosd7 -partition, hit 'm' to fill it out to the end of the "disk". Write and quit. -.in -(24n+2m) -.nf -mkfs /dev/dosd7 Recreate the file system, but larger -mount /dev/dosd7 /mnt -cpdir -v /usr /mnt Copy /usr to the new disk's /usr to be -shutdown Back to the monitor -exit Back to DOS -ren disk0.mnx disk0.old -ren disk0.new disk0.mnx Replace old by new -boot disk0.mnx Run the larger system -.fi -.RE -.PP -Now MINIX 3 runs from a larger "disk". Don't worry if it claims to have -crashed, there wasn't a "shutdown" entry in /usr/adm/wtmp at the time it was -copied. -.PP -The above recipe is for a ordinary standard MINIX 3 installation with /usr on -the second and last partition. -.\" Minix-vmd usually has /usr on the third and -.\" last partition (dosd3 / dosd8), its -.\" .B mkfs -.\" command requires a -.\" .B "-t\ 2f" -.\" option to specify the file system type as "V2 flex", and it knows if -.\" it has crashed or not. -.SS Backups -In the recipe above you saw how simple it is to create a new system, just -copy a disk file. It is equally simple to make a backup, you just copy the -disk file. To make a test system: copy the disk file. To make another test -system: copy the disk file. Let friends have their own MINIX 3: copy the disk -file again. (Exciting, eh?) -.PP -You may want to save a MINIX 3 disk file in a ZIP file to save space. It may -look as a good idea to first run -.B "make clean" -in -.B /usr/src -to remove all the binary junk, but alas that has no effect at all. -The disk file is compressed under DOS, and there it is unknown which blocks -are in use and which are free. With the following trick you can make those -deleted blocks compress really well: -.PP -.RS -.nf -cd /usr/tmp -echo >junk -while cat junk >>junk; do :; done -sync -rm junk -.fi -.RE -.PP -After these commands all free blocks contain newlines. Long runs of the -same byte happen to compress by a factor 1000, so the unused disk blocks -will almost disappear in the ZIP file. -.\" Under Minix-vmd you can use -.\" .PP -.\" .RS -.\" cp /dev/zero junk -.\" .RE -.\" .PP -.\" instead of the echo/while pair of lines above. Standard MINIX 3 doesn't have -.\" /dev/zero. -.SS "FAT driver" -The dos disk driver, described in -.BR dosd (4), -has two identities. By default you get the "\fBfile\fP" driver, that uses -DOS file I/O calls to access a large DOS file as a disk. The other -alternative is the "\fBFAT\fP" driver. The FAT driver sits on top of an -ordinary MINIX 3 disk driver, and interprets a partition as a FAT (File Access -Table) file system to find a file to use as a MINIX 3 disk. The result -has the same effect as the file driver, except that no costly calls to DOS -are made. To enable this feature you have to use the following Boot -environment settings: -.PP -.RS -.nf -dosd = fat -dosd0 = hd1:\eminix\edisk0.mnx -.fi -.RE -.PP -The -.B dosd -setting tells MINIX 3 to use the FAT driver, and the -.B dosd0 -setting tells the MINIX 3 device and DOS file name to use. Disk I/O should -be sped up nicely by this change, although typical use of MINIX 3 doesn't -require fast disk I/O, so the difference won't be too noticable. -.PP -Support for FAT-32 (big file system support added in the later Windows 95 -releases) has not been tested very well. The FAT-12 and FAT-16 code has -been used a lot, and seems safe. Note the risks inherent in these -drivers: The file driver uses simple DOS file I/O calls, leaving it to -DOS to know its own file system. The FAT driver interprets FAT file system -structures by itself. MINIX 3 booted from a real hard disk partition can -only use DOS disk files through the FAT driver. -.SH "SEE ALSO" -.BR dosd (4), -.BR monitor (8), -.BR usage (8). -.SH NOTES -Use at your own risk. -.SH BUGS -Hasn't been tried under Windows 98 yet. -.PP -Pray the deity of your choice will forgive you for running a UNIX-like -system as an ordinary DOS program. The author of this code is already -doomed. When his time comes the daemons wi*(&%*$%*& -.br -Memory fault \- core dumped -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) Index: trunk/minix/man/man8/elvprsv.8 =================================================================== --- trunk/minix/man/man8/elvprsv.8 (revision 9) +++ (revision ) @@ -1,54 +1,0 @@ -.TH ELVPRSV 8 -.SH NAME -elvprsv - Preserve the the modified version of a file after a crash. -.SH SYNOPSIS -.nf -\fB\fBelvprsv\fP ["-\fIwhy elvis died\fP"] /tmp/\fIfilename\fP... -\fB\fBelvprsv\fP -R /tmp/\fIfilename\fP... -.fi -.SH DESCRIPTION -.PP -\fIelvprsv\fP preserves your edited text after \fIelvis\fP dies. -The text can be recovered later, via the \fIelvprsv\fP program. -.PP -For UNIX-like systems, -you should never need to run this program from the command line. -It is run automatically when \fIelvis\fP is about to die, -and it should be run (via /etc/rc) when the computer is booted. -THAT'S ALL! -.PP -For non-UNIX systems such as MS-DOS, you can either use \fIelvprsv\fP -the same way as under UNIX systems (by running it from your AUTOEXEC.BAT file), -or you can run it separately with the "-R" flag to recover the files -in one step. -.PP -If you're editing a file when \fIelvis\fP dies -(due to a bug, system crash, power failure, etc.) -then \fIelvprsv\fP will preserve the most recent version of your text. -The preserved text is stored in a special directory; it does NOT overwrite -your text file automatically. -.PP -\fIelvprsv\fP will send mail to any user whose work it preserves, -if your operating system normally supports mail. -.SH FILES -.IP /tmp/elv* -The temporary file that \fIelvis\fP was using when it died. -.IP /usr/preserve/p* -The text that is preserved by \fIelvprsv\fP. -.IP /usr/preserve/Index -A text file which lists the names of all preserved files, and the names -of the /usr/preserve/p* files which contain their preserved text. -.SH BUGS -.PP -Due to the permissions on the /usr/preserve directory, on UNIX systems -\fIelvprsv\fP must be run as superuser. -This is accomplished by making the \fIelvprsv\fP executable be owned by "root" -and turning on its "set user id" bit. -.PP -If you're editing a nameless buffer when \fIelvis\fP dies, then \fIelvprsv\fP will pretend -that the file was named "foo". -.SH AUTHOR -.nf -Steve Kirkendall -kirkenda@cs.pdx.edu -.fi Index: trunk/minix/man/man8/fdisk.8 =================================================================== --- trunk/minix/man/man8/fdisk.8 (revision 9) +++ (revision ) @@ -1,58 +1,0 @@ -.TH FDISK 8 -.SH NAME -fdisk \- partition a hard disk [IBM] -.SH SYNOPSIS -\fBfdisk\fR [\fB\-h\fIm\fR]\fR [\fB\-s\fIn\fR]\fR [\fIfile\fR]\fR -.br -.de FL -.TP -\\fB\\$1\\fR -\\$2 -.. -.de EX -.TP 20 -\\fB\\$1\\fR -# \\$2 -.. -.SH OPTIONS -.FL "\fB\-h" "Number of disk heads is \fIm\fR" -.FL "\fB\-s" "Number of sectors per track is \fIn\fR" -.SH EXAMPLES -.EX "fdisk /dev/hd0" "Examine disk partitions" -.EX "fdisk \-h9 /dev/hd0" "Examine disk with 9 heads" -.SH DESCRIPTION -.PP -When \fIfdisk\fR starts up, it reads in the partition table and displays -it. -It then presents a menu to allow the user to modify partitions, store the -partition table on a file, or load it from a file. Partitions can be marked -as -\s-1MINIX 3\s-1, -DOS or other, as well as active or not. -Using \fIfdisk\fR is self-explanatory. -However, be aware that -repartitioning a disk will cause information on it to be lost. -Rebooting the system \fIimmediately\fR -is mandatory after changing partition sizes and parameters. -\s-1MINIX 3\s-1, -\&\s-2XENIX\s0, \s-2PC-IX\s0, and \s-2MS-DOS\s0 all have different -partition numbering schemes. -Thus when using multiple systems on the same disk, be careful. -.PP -Note that -\s-1MINIX 3\s-1, -unlike -\&MS-DOS , -cannot access the last sector in a partition with an odd number of sectors. -The reason that odd partition sizes do not cause a problem with -\s-2MS-DOS\s0 is that \s-2MS-DOS\s0 allocates disk space in units of -512-byte sectors, whereas -\s-1MINIX 3\s-1 -uses 1K blocks. -\fIFdisk\fR has a variety of other features that can be seen by typing \fIh\fR. -.PP -.I Fdisk -normally knows the geometry of the device by asking the driver. You can use -the \fB\-h\fP and \fB\-s\fP options to override the numbers found. -.SH "SEE ALSO" -.BR part (8). Index: trunk/minix/man/man8/fingerd.8 =================================================================== --- trunk/minix/man/man8/fingerd.8 (revision 9) +++ (revision ) @@ -1,53 +1,0 @@ -.\" Copyright (c) 1980 Regents of the University of California. -.\" All rights reserved. The Berkeley software License Agreement -.\" specifies the terms and conditions for redistribution. -.\" -.\" @(#)fingerd.8c 6.1 (Berkeley) 5/23/86 -.\" -.TH FINGERD 8 "May 23, 1986" -.UC 6 -.SH NAME -fingerd, in.fingerd \- remote user information server -.SH SYNOPSIS -.B "finger stream tcp nowait nobody /usr/sbin/in.fingerd in.fingerd" -.br -.B "tcpd finger /usr/sbin/in.fingerd in.fingerd" -.SH DESCRIPTION -.B Fingerd -is a simple protocol based on RFC742 that provides an interface to the -Name and Finger programs at several network sites. -The program is supposed to return a friendly, -human-oriented status report on either the system at the moment -or a particular person in depth. -There is no required format and the -protocol consists mostly of specifying a single ``command line''. -.PP -.B Fingerd -listens for TCP requests at port 79. -Once connected it reads a single command line -terminated by a which is passed to -.BR finger (1). -.B Fingerd -closes its connections as soon as the output is finished. -.PP -If the line is null (i.e. just a is sent) then -.B finger -returns a ``default'' report that lists all people logged into -the system at that moment. -.PP -If a user name is specified (e.g. eric) then the -response lists more extended information for only that particular user, -whether logged in or not. -Allowable ``names'' in the command line include both ``login names'' -and ``user names''. -If a name is ambiguous, all possible derivations are returned. -.SH SEE ALSO -.BR finger (1). -.SH BUGS -Connecting directly to the server from a TIP -or an equally narrow-minded TELNET-protocol user program can result -in meaningless attempts at option negotiation being sent to the -server, which will foul up the command line interpretation. -.B Fingerd -should be taught to filter out IAC's and perhaps even respond -negatively (IAC WON'T) to all option commands received. Index: trunk/minix/man/man8/ftpd.8 =================================================================== --- trunk/minix/man/man8/ftpd.8 (revision 9) +++ (revision ) @@ -1,145 +1,0 @@ -.\" Copyright (c) 1985 Regents of the University of California. -.\" All rights reserved. The Berkeley software License Agreement -.\" specifies the terms and conditions for redistribution. -.\" -.\" @(#)ftpd.8c 6.4 (Berkeley) 5/28/86 -.\" -.TH FTPD 8 -.SH NAME -ftpd, in.ftpd, setup.anonftp \- DARPA Internet File Transfer Protocol server -.SH SYNOPSIS -.B "ftp stream tcp nowait root /usr/sbin/in.ftpd in.ftpd" -.br -.B "tcpd ftp /usr/sbin/in.ftpd" -.SH DESCRIPTION -.B Ftpd -is the DARPA Internet File Transfer Prototocol -server process. The server uses the TCP protocol -and listens at the port specified in the ``ftp'' -service specification; see -.BR services (5). -.PP -The ftp server currently supports the following ftp -requests; case is not distinguished. -.PP -.nf -.ta \w'Request 'u -\fBRequest Description\fP -ABOR abort previous command -ACCT specify account (ignored) -ALLO allocate storage (vacuously) -APPE append to a file -CDUP change to parent of current working directory -CWD change working directory -DELE delete a file -HELP give help information -LIST give list files in a directory (``ls -lA'') -MKD make a directory -MODE specify data transfer \fImode\fP -NLST give name list of files in directory (``ls'') -NOOP do nothing -PASS specify password -PASV prepare for server-to-server transfer -PORT specify data connection port -PWD print the current working directory -QUIT terminate session -RETR retrieve a file -RMD remove a directory -RNFR specify rename-from file name -RNTO specify rename-to file name -STOR store a file -STOU store a file with a unique name -STRU specify data transfer \fIstructure\fP -TYPE specify data transfer \fItype\fP -USER specify user name -XCUP change to parent of current working directory -XCWD change working directory -XMKD make a directory -XPWD print the current working directory -XRMD remove a directory -.fi -.PP -The remaining ftp requests specified in Internet RFC 959 are -recognized, but not implemented. -.PP -The ftp server will abort an active file transfer only when the -ABOR command is preceded by a Telnet "Interrupt Process" (IP) -signal and a Telnet "Synch" signal in the command Telnet stream, -as described in Internet RFC 959. -.PP -.B Ftpd -interprets file names according to the ``globbing'' -conventions used by -.BR csh (1). -This allows users to utilize the metacharacters ``*?[]{}~''. -.PP -.B Ftpd -authenticates users according to three rules. -.IP 1) -The user name must be in the password data base, -.BR /etc/passwd , -and not have a null password. In this case a password -must be provided by the client before any file operations -may be performed. -.IP 2) -The user name must not appear in the file -.BR /etc/ftpusers . -.IP 3) -If the user name is ``anonymous'' or ``ftp'', an -anonymous ftp account must be present in the password -file (user ``ftp''). In this case the user is allowed -to log in by specifying any password (by convention this -is given as the client host's name). -.PP -In the last case, -.B ftpd -takes special measures to restrict the client's access privileges. -The server performs a -.BR chroot (2) -command to the home directory of the ``ftp'' user. -In order that system security is not breached, it is recommended -that the ``ftp'' subtree be constructed with care; the following -rules are recommended. -.IP ~ftp) -Make the home directory owned by ``ftp'' and unwritable by anyone. -.IP ~ftp/bin) -Make this directory owned by the super-user and unwritable by -anyone. The program -.BR ls (1) -must be present to support the list commands. This -program should have mode 111. -.IP ~ftp/etc) -This directory could be created, and could have -.BR passwd (5) -and -.BR group (5) -databases in it so that -.B ls -can show file ownership, but outsiders will grab your password file and -misuse it to spam you. So don't bother. -.IP ~ftp/pub) -Make this directory mode 755 and owned by the super-user. Create -directories in it owned by users if those users want to manage an -anonymous ftp directory. -.IP ~ftp/pub/incoming) -Optionally create this directory for anonymous uploads. Make it mode -777. The FTP daemon will create files with mode 266, so remote users -can write a file, but only local users can do something with it. -.PP -The script -.B setup.anonftp -can be used to create or check an anonymous FTP tree. -.SH "SEE ALSO" -.BR ftp (1). -.SH BUGS -The anonymous account is inherently dangerous and should -avoided when possible. -.ig \" MINIX 3 doesn't have privileged port numbers (yet?) -.PP -The server must run as the super-user -to create sockets with privileged port numbers. It maintains -an effective user id of the logged in user, reverting to -the super-user only when binding addresses to sockets. The -possible security holes have been extensively -scrutinized, but are possibly incomplete. -.. Index: trunk/minix/man/man8/getty.8 =================================================================== --- trunk/minix/man/man8/getty.8 (revision 9) +++ (revision ) @@ -1,40 +1,0 @@ -.TH GETTY 8 -.SH NAME -getty \- system login banner -.SH SYNOPSIS -.B getty -.RI [ banner " ...]" -.SH DESCRIPTION -.B Getty -displays a system identification banner, reads a user name from standard -input and executes -.B login -with that name as argument. -.PP -.B Getty -uses its arguments separated by spaces as a login banner. The character -sequences -.BR \en , -.BR \es -and -.BR \et -are printed as newline, space and tab. Any other -.BI \e x -prints that -.IR x . -The character sequences -.BR %s , -.BR %n , -etc. produce the same output as -.BR "uname \-s" , -.BR "uname \-n" , -etc. The default banner is -.PP -.RS -%s\es\esRelease\es%r\esVersion\es%v\en\en%n\eslogin:\es -.RE -.SH "SEE ALSO" -.BR ttytab (5), -.BR init (8). -.SH AUTHOR -Kees J. Bot Index: trunk/minix/man/man8/halt.8 =================================================================== --- trunk/minix/man/man8/halt.8 (revision 9) +++ (revision ) @@ -1,33 +1,0 @@ -.TH HALT 8 -.SH NAME -halt \- abruptly stop the system -.SH SYNOPSIS -\fBhalt\fP [\fB\-f\fP] -.SH DESCRIPTION -.B Halt -stops the system almost immediately. The users are not informed about -the things to come. -.B Halt -is logged in -.B /usr/adm/wtmp -and in -.BR /usr/adm/log , -if these files exist. -.B Halt -should only be run by the super-user, any other caller will be refused. -.PP -.B Halt -is a rather rude program. -.BR Shutdown (8) -is preferred for it performs a more gentle halt routine. -.PP -.B Halt \-f -is even worse, it omits the terminate signals that are normally -sent first to all processes to give them a chance to die peacefully. -.SH "SEE ALSO" -.BR reboot (2), -.BR shutdown (8), -.BR reboot (8), -.BR boot (8). -.SH AUTHOR -Edvard Tuinder (v892231@si.hhs.NL) Index: trunk/minix/man/man8/ifconfig.8 =================================================================== --- trunk/minix/man/man8/ifconfig.8 (revision 9) +++ (revision ) @@ -1,50 +1,0 @@ -.TH IFCONFIG 8 -.SH NAME -ifconfig \- configure a TCP/IP device -.SH SYNOPSIS -.B ifconfig -.RB [ \-I -.IR ip-device ] -.RB [ \-h -.IR ipaddr ] -.RB [ \-n -.IR netmask ] -.RB [ \-m -.IR mtu ] -.RB [ \-iva ] -.SH DESCRIPTION -.B Ifconfig -initializes a TCP/IP device setting the IP address and/or netmask. It will -report the address and netmask set. This command may be used if the system -has not been configured properly yet. It is only used at boot time to set a -fixed address for a system without a physical ethernet. Normally the -.B inet -task will find it out by itself from the RARP server. -.SH OPTIONS -.TP -.B \-h -The decimal TCP/IP address to set. -.TP -.B \-n -The netmask to set. -.TP -.B \-m -The mtu to set. (Minix-vmd only.) -.TP -.B \-i -Don't set the IP address or netmask if already set. This way ifconfig cannot -interfere if the numbers have been found out by RARP. -.TP -.B \-v -Report IP address and netmask. This is the default action if there are no -other options. -.TP -.B \-a -Report the IP addresses and netmasks of all configured interfaces. -.SH "SEE ALSO" -.BR hostaddr (1), -.BR rarpd (8), -.BR inet (8), -.BR boot (8). -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) Index: trunk/minix/man/man8/inet.8 =================================================================== --- trunk/minix/man/man8/inet.8 (revision 9) +++ (revision ) @@ -1,146 +1,0 @@ -.TH INET 8 -.SH NAME -inet, inet.conf \- TCP/IP server -.SH SYNOPSIS -.B inet -.SH DESCRIPTION -.de SP -.if t .sp 0.4 -.if n .sp -.. -.B Inet -is the TCP/IP server. It is a device driver that interfaces between the -file server and the low level ethernet device driver. The interface to this -server is described in -.BR ip (4). -.PP -.B Inet -starts as a normal process, reads a the configuration file -.B /etc/inet.conf -to see what it should do, and uses a few special low level system calls -to turn itself into a server. The format of the configuration file is as -follows: -.SS Configuration -The inet configuration file is fairly simple, here is an example: -.PP -.RS -.ft C -.nf -eth0 DP8390 0 { default; }; -psip1; -.fi -.ft P -.RS -.PP -It tells that network 0 (the one containing devices -.BR eth0 , -.BR ip0 , -.BR tcp0 -and -.BR udp0 ) -uses the ethernet device driver handled -by task "DP8390" at port 0. This network is marked as the default -network, so most programs use it through the unnumbered devices like -.B /dev/tcp -or -.BR /dev/udp . -Network 1 is a Pseudo IP network that can be used for -a serial IP over a modem for instance. -.PP -The configuration file may look like a common configuration file as -described by -.BR configfile (5), -but it is currently just a simple subset allowing only what you see here. -The following network definitions are possible: -.PP -.BI eth N -.I task port -.RI { options }; -.RS -This sets up an ethernet with device name -.BI /dev/eth N\fR, -built on the given ethernet device driver at the given port at that driver. -(If a network driver manages two network -cards then they are at port 0 and 1.) -.br -.RE -.PP -.BI eth N -.B vlan -.I id -.BI eth M -.RI { options }; -\0\0\0\0 -.RS -The ethernet -.BI eth N -uses VLAN number -.I id -and is built on ethernet -.BI eth M\fR. -A packet given to this network has a VLAN tag prefixed to it and is then -handed over to another ethernet for transmission. Likewise a packet on -that ethernet carrying the appropriate VLAN tag has this tag removed and is -sent on to this network. The VLAN ethernet behaves like an ordinary ethernet -as far as applications are concerned. -.RE -.PP -.BI psip N -.RI { options }; -.RS -Creates pseudo IP network -.BI /dev/psip N\fR, -usable for IP over serial lines, tunnels and whatnot. -.RE -.SH OPTIONS -Some options can be given between braces. -.PP -.BR default ; -.RS -Mark this network as the default network. Exactly one of the networks must -be so marked. -When -.B inet -is started it will check and create all the necessary network devices before -becoming a server. To know what major device number to use it checks -.BR /dev/ip , -so that device must already exist. It can be created by -.B MAKEDEV -if need be. -.RE -.PP -.BR "no ip" ; -.br -.BR "no tcp" ; -.br -.BR "no udp" ; -.RS -These options turn the IP, TCP, or UDP layer off. Inet will not enable the -devices for these layers, and will deactivate code for these layers. -Disabling IP will also disable TCP or UDP, because they need IP to function. -An ethernet without an IP layer can be used as for stealth listening. An IP -network without TCP or UDP can be used to pester students into creating the -missing functionality. Keeps them off the streets, and maybe they'll learn -something. -.RE -.SH "SEE ALSO" -.BR ip (4), -.BR boot (8). -.SH NOTES -The number of networks that can be defined are 2 (Minix-86), 4 (Minix-386) -or 16 (Minix-vmd). This limits both the total number and the highest -device number you can use. -.PP -Getting a network administrator to give you a trunk or multi-VLAN port to -run multiple networks on can be a challenge. It questions their idea that -VLANs are separate networks, while in reality it is just one big ethernet. -.SH ACKNOWLEDGMENTS -Cindy Crawford, for providing invaluable help debugging this server. -.SH AUTHOR -.ta \w'Manual:'u+2n -Code: Philip Homburg -.br -Manual: Kees J. Bot - -.\" -.\" $PchId: inet.8,v 1.6 2001/10/08 19:01:35 philip Exp $ Index: trunk/minix/man/man8/init.8 =================================================================== --- trunk/minix/man/man8/init.8 (revision 9) +++ (revision ) @@ -1,141 +1,0 @@ -.TH INIT 8 -.SH NAME -init \- grandparent of all processes -.SH DESCRIPTION -The first program started by MINIX 3 is -.BR init . -The actions performed by -.B init -can be summarized by this pseudo shell program: -.RS -.nf -.if t .ft C - -# Open 0, 1, 2. -exec /dev/log 2>&1 - -# Run the system initialization script. -sh /etc/rc $bootopts - ->/etc/utmp -echo reboot >>/usr/adm/wtmp - -while :; do - # Wait for a process to exit, but don't always block. - wait - - # Record logout. (Not in this dumb way, of course.) - if "pid is in my tables" $pid - then - echo "logout $pid" >/etc/utmp - echo "logout $pid" >>/usr/adm/wtmp - fi - - # Start a new session. - while read line type getty init - do - if idle $line - then - $init ... <$tty >$tty - $getty <$tty >$tty 2>&1 & - pid=$! - "add pid to tables" $pid - echo "login $line $pid" >/etc/utmp - echo "login $line $pid" >>/usr/adm/wtmp - fi - done < /dev/ttytab -done - -.if t .ft R -.fi -.RE -The first action of -.B init -is to run -.B /etc/rc -to initialize the system as described in -.BR boot (8). -.B Init -then enters its main loop where it waits for processes to exit, and starts -processes on each enabled terminal line. The file -.B /etc/ttytab -contains a list of terminal devices, their terminal types, the program to -execute on them to allow one to login (usually -.BR getty (8)), -and the program to execute first to initialize the line (usually -.BR stty (1)). -These fields may be left out to indicate that a line is disabled or that -initialization is not necessary. The commands are searched using the path -.BR /sbin:/bin:/usr/sbin:/usr/bin . -.PP -.B Init -accepts several signals that must be sent to process id 1. (It is the first -process, so natually its process id is 1.) The signals are: -.TP -.B SIGHUP -When receiving a hangup signal, -.B init -will forget about errors and rescan -.B ttytab -for processes to execute. -.B Init -normally rescans -.B ttytab -each time it feels the need to respawn a process, so the hangup signal is only -needed if a line has been shut down, or after a terminate signal. Note -that after turning a line off you will have to kill the process running on -that line manually, -.B init -doesn't do that for you. -.TP -.B SIGTERM -Normally sent by programs that halt or reboot MINIX 3. Causes -.B init -to stop spawning new processes. -.TP -.B SIGABRT -Sent by the keyboard driver when the -.B CTRL-ALT-DEL -key combination is typed. Causes -.B init -to run the -.B shutdown -command. A second abort signal makes -.B init -halt the system directly with a system call. The keyboard driver halts the -system, without a sync, after the third CTRL-ALT-DEL. -.SS "MINIX 3 vs. Minix-vmd" -There are a few differences between standard MINIX 3 and Minix-vmd on how -.B init -is run. The -.B /etc/rc -file is executed under standard MINIX 3 with input connected to -.BR /dev/console , -but under Minix-vmd this is still -.BR /dev/null . -This means that under Minix-vmd processes must be reconnected to -.B /dev/console -with the -.BR intr (8) -program if they need user interaction. -Minix-vmd passes the value of the -.B bootopts -boot variable to /etc/rc. Standard MINIX 3 does not. -.SH FILES -.TP 25n -.B /etc/ttytab -List of terminals devices. -.TP -.B /etc/utmp -List of currently logged in users. -.TP -.B /usr/adm/wtmp -Login/logout history. -.SH "SEE ALSO" -.BR ttytab (5), -.BR utmp (5), -.BR getty (8), -.BR stty (1), -.BR boot (8). -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) Index: trunk/minix/man/man8/installboot.8 =================================================================== --- trunk/minix/man/man8/installboot.8 (revision 9) +++ (revision ) @@ -1,395 +1,0 @@ -.TH INSTALLBOOT 8 -.SH NAME -installboot \- make a device bootable -.SH SYNOPSIS -.B installboot \-i(mage) -.I image -.RI [ label :] kernel -.IR "mm fs" " ... " init -.br -.B installboot \-(e)x(tract) -.I image -.br -.B installboot \-d(evice) -.I device bootblock boot -.RI [[ label :] image -\&...] -.br -.B installboot \-b(oot) -.I device bootblock boot -.RI [ label :] image -\&... -.br -.B installboot \-m(aster) -.I device masterboot -.RI [ keys " [" logical ]] -.SH DESCRIPTION -.de SP -.if t .sp 0.4 -.if n .sp -.. -.B Installboot -may be used to make a device bootable by constructing a kernel image and -installing bootstrap code into the boot block of a MINIX 3 file system. To -understand how this can be done one first has to know what happens when a -PC is booted. -.PP -When the power is turned on the typical PC will try to read the first sector -from the first floppy disk or from the first hard disk into memory and execute -it. The code obtained from the hard disk (from the so-called master boot -sector) will immediately replace itself by the code found in the first sector -of the active partition. Thus the PC is now executing the bootstrap code found -in the first sector of /dev/fd0, /dev/c0d0p0, /dev/c0d0p1, /dev/c0d0p2, or -/dev/c0d0p3 (assuming the boot disk is attached to controller 0.) -The bootstrap will locate the operating system on the device it itself was -loaded from, load it, and execute it. -.PP -To make a MINIX 3 file system -.B /dev/fd0 -mounted on -.B /mnt -bootable, enter the following: -.SP -.RS -.ft B -cp /usr/mdec/boot /mnt/boot -.SP -installboot \-i /mnt/minix kernel mm fs init -.SP -installboot \-d /dev/fd0 /usr/mdec/bootblock boot -.ft P -.RE -.PP -The "boot" program in the example is named the "Boot Monitor". It is loaded -by the bootblock code placed in the boot sector of /dev/fd0 and it will take -care of loading the kernel image "minix" from the root directory of the -file system. See -.BR monitor (8) -for a description of the Boot Monitor. Note that -.B boot -is a name in the file system on -.B /dev/fd0 -in this example, the same file as -.BR /mnt/boot . -Making -.B /mnt/minix -is normally not necessary, there is usually a kernel image in the -.B tools -directory. -.SH OPTIONS -.B \-i(mage) -.I image -.RI [ label :] kernel -.IR "mm fs" " ... " init -.RS -The -.B \-image -option (or the -.B \-i -shorthand) combines the executable files needed to run MINIX 3 in one file. -Only the names and a few zero bytes are inserted into the image. The name -is for identification and the zeros are used to pad separate pieces to -sector boundaries for fast loading. -.SP -An executable may be prefixed by a label. The Monitor may be instructed to -load processes by label. So more than one kernel process may be included in -the image, each with a different winchester driver for instance. So if you -have compiled two different kernels with an AT or XT driver then -.SP -.RS -.BI "installboot \-i" " image AT:at_kernel XT:xt_kernel mm fs init" -.RE -.SP -will make an image with two different labeled kernels and one -unlabeled set of the other binaries. -.RE -.PP -.B \-(e)x(tract) -.I image -.RS -Extract the binaries from -.I image -under the names stored in the image. (The name includes the optional label.) -.RE -.PP -.B \-d(evice) -.I device bootblock boot -.RI [[ label :] image -\&...] -.RS -Installs -.I bootblock -in the boot sector of -.I device -together with the disk addresses to -.IR boot . -These disk addresses are needed to load -.I boot -from the file system at boot time. The argument -.I boot -is first searched in the file system on -.IR device . -If it is not found then it is read as a normal file and added at the end of -the file system. The file system should be smaller than the device it is on -to allow this. Any extra images are also added to the end as described -under -.BR \-boot . -(Make sure you understand all this.) -.SP -The device need not be mounted when -.B installboot -is run, nor does it matter if it is. -.SP -.B Installboot -needs to be run again if -.I boot -is rewritten, because it will then occupy a new place on the disk. -.SP -Old boot parameters are kept if there are no images added. -.RE -.PP -.B \-b(oot) -.I device bootblock boot -.RI [ label :] image -\&... -.RS -This option fills a blank floppy in -.I device -with boot code and kernel images. This "boot disk" does not have a root -file system, only the Boot Monitor and MINIX 3 kernels. The boot parameters -sector is filled with code that enables menu options for selecting an -image. After loading an image, the Monitor will ask you to insert a root -file system diskette before starting MINIX 3. -.SP -The labels used on the images should match those on the executables used -inside the image. You can put a comma separated list of labels on an image -for each label used within the image. For the image created earlier one -would create a boot floppy like this: -.SP -.RS -.nf -.BI "installboot \-b /dev/fd0 bootblock boot" " AT,XT:image" -.fi -.RE -.SP -If a label-list is omitted on an image, then that image will be selected by -default. (Like in the normal one image, no labels case.) -.SP -Note that -.B \-device -and -.B \-boot -together allow you to make a boot floppy with or without a root file system. -With the boot code in the file system, attached to the end of it, or after -the boot block. And with one or more kernel images in the file system or -at the end of the device. Somewhat confusing. -.RE -.PP -.B \-m(aster) -.I device masterboot -.RI [ keys " [" logical ]] -.RS -This option installs the -.I masterboot -program into the boot sector of the given device. If another device is -given instead of -.I masterboot -then its bootstrap code is copied to -.IR device . -The master bootstrap on a hard disk boots the active partition on that disk -at boot time. The MS-DOS fdisk command normally puts a master bootstrap on -the hard disk. MINIX 3 has two bootstraps that can be used as a master -bootstrap, -.B masterboot -and -.BR jumpboot. -.SP -.B Masterboot -is a fairly normal master bootstrap that works as follows: -.RS -.SP -If installed on a hard disk then it will load the bootstrap of the active -partition and run it. -.B Masterboot -can be put in the first sector of a hard disk to boot the active partition, -or in the first sector of a MINIX 3 partition to boot the active subpartition. -.SP -If installed on a MINIX 3 floppy then it will try to boot the next floppy or -the first hard disk. Ideal for floppies with just data on it, they will no -longer obstruct the boot process if left in the drive. Also a very useful -trick to boot from floppy drive 1. -.RE -.SP -The other bootstrap named -.B jumpboot -is used for the weird cases: -.SP -.RS -If your default operating system is installed on another disk then -.B jumpboot -can be installed on the first disk and instructed to boot the disk, -partition or subpartition that must be booted by default. -.SP -If one of your operating systems insists on being active when booted then use -.B jumpboot -to ignore the active flag and boot your preferred O.S. instead. The Boot -Monitor's "\fBboot\ \(**\fP" trick to activate the partition to boot is -useful here. -.SP -To boot a logical partition within an extended partition. Note that you can -put -.B jumpboot -in the first sector of the extended partition in this case, with the -extended partition marked active. -.SP -If you hold down the ALT key while -.B jumpboot -is being executed, then you can type the disk, partition or subpartition -you want to boot as one to three digits followed by typing ENTER. -.RE -.SP -.B Jumpboot -can be programmed to boot a certain partition with the -.I keys -argument and optionally also the -.I logical -argument. -.I Keys -are one to three digits naming the disk, partition or subpartition. If the -device to boot is -.BR /dev/c0d1p3s0 , -then -.I keys -is -.BR 130 . -These are the same three digits you can type manually if you hold down ALT -at boot. To program -.B jumpboot -to boot a logical partition within an extended partition, let -.I keys -be just a disk number, and specify -.I logical -as the name of the logical partition on that disk that is to be booted. -(Actually -.I logical -can be any device name, but this form should be avoided because it offers -less checking to see if the device is still there after a disk -rearrangement.) -.SP -A backup copy of the current master bootstrap (including the partition -table) can be made with: -.RS -.SP -dd if=\fIdevice\fP of=\fIbackup-file\fP count=1 -.SP -.RE -A simple 'cp \fIbackup-file\fP \fIdevice\fP' will put it back. You can -also use -.B fdisk /mbr -under MS-DOS 5.0 (or newer) to restore the master bootstrap. -.RE -.RE -.SH FILES -.TP 25 -.B /usr/mdec/bootblock -MINIX 3 bootstrap for the Minix root device. To be placed in the boot sector. -.TP -.B /usr/mdec/boot -MINIX 3 Boot Monitor. Can usually be found in the root directory of a bootable -device. -.TP -.B /usr/mdec/masterboot -Master bootstrap. Can be placed in the first sector of a disk to select the -active partition. In a MINIX 3 primary partition it selects the active -subpartition. -.TP -.B /usr/mdec/jumpboot -Special "boot this" bootstrap. -.SH "SEE ALSO" -.BR part (8), -.BR monitor (8). -.SH DIAGNOSTICS -.I File -is not an executable -.RS -What you think is boot code or part of the kernel isn't. -.RE -.SP -.I Program -will crash, text/data segment larger then 64K -.RS -One of the 16-bit programs added to an image has a text or data segment -that is larger than 64K. You probably enabled too many drivers, or -configured too many buffers. -.RE -.SP -.I File -can't be attached to -.I device -.RS -You are trying to put the boot monitor or an image after a file system, but -there is no or not enough space. Did you specify the full path of the -monitor instead of just "boot"? -.RE -.SP -.I Device -is not a MINIX 3 file system -.RS -You are using -.B \-device -on a device that doesn't contain a file system. Maybe you specified the -wrong device, maybe you should make a file system, or maybe you should use -.BR \-boot . -.RE -.SP -.I Device -contains a file system -.RS -You are about to destroy a file system with -.BR \-boot . -Maybe you meant to use -.BR \-device ? -You have 10 seconds to make up your mind... -.RE -.SP -.I File -is too big -.RS -Several types of messages like these will tell you that -.I file -can't be installed in a boot sector, or that there is no room to add some -parameters, etc. Is -.I file -really a bootstrap? -.RE -.SS "Bootstrap errors" -Read error -.RS -A read error trying to get the next bit of boot code. You may even get the -BIOS error code in hex. Either the device has a bad block, or jumpboot is -told to read a nonexistent disk. -.RE -.SP -No active partition -.RS -None of the partitions in a partition table is marked active. -.RE -.SP -Not bootable -.RS -Partition does not exist (jumpboot), or it's bootstrap isn't executable. -.RE -.SH NOTES -The MINIX 3 bootstraps can boot beyond the 8G disk size limit if the BIOS -supports the IBM/MS INT 13 Extensions. Alas only Minix-vmd can make use of -this, standard MINIX 3 has a 4G disk size limit. -.SH BUGS -It has four more options than the SunOS installboot program it is modeled -after. -.PP -The bootblock code has been crunched to such ugliness that you can use it -to scare little kids out of your garden. -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) -.\" -.\" $PchId: installboot.8,v 1.7 2000/08/13 22:09:31 philip Exp $ Index: trunk/minix/man/man8/intr.8 =================================================================== --- trunk/minix/man/man8/intr.8 (revision 9) +++ (revision ) @@ -1,71 +1,0 @@ -.TH INTR 8 -.SH NAME -intr \- run a command with interrupts enabled -.SH SYNOPSIS -.B intr -.RB [ \-d ] -.RB [ \-t -.IR seconds ] -.I command -.RI [arg "...]" -.SH DESCRIPTION -.B Intr -executes a command with keyboard interrupts enabled, and standard input, -output and error redirected to the terminal or the console. It may also -be used for the opposite: to detach a process from the terminal. -.PP -There are three situations where intr may be used: From a process that has -no controlling tty, like the shell running -.B /etc/rc -at boot time, from a script that runs in the background, or by the System -Administrator to restart a daemon. -.PP -In the first case -.B intr -will use -.B /dev/console -as a controlling tty and as standard input, output and error. In the -second case -.B intr -will use -.B /dev/tty -to connect the command to the controlling tty. In the third case the -process will be removed from the process group, and will have I/O redirected -to -.B /dev/null -as input, and -.B /dev/log -for output. -.SH OPTIONS -.TP -.B \-d -Daemonize a process instead of bringing it to the foreground. Don't forget -to use '&' to make the shell not wait for the process, because you won't be -able to kill it with the interrupt key. -.TP -.BI \-t " seconds" -Schedule an alarm to kill the process in the given number of seconds. -Use it for a process that may wait indefinitely for a service that may -not be available. -.SH FILES -.TP 20 -.B /dev/console -Main computer console. -.TP -.B /dev/log -Message logging device. -.TP -.B /dev/tty -Name for the controlling tty. -.SH "SEE ALSO" -.BR boot (8), -.BR tty (4), -.BR setsid (2), -.BR alarm (2). -.SH BUGS -Maybe -.B intr \-d -should fork to daemonize a process, but the author likes it if the process -stays in the jobs list of his shell. -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) Index: trunk/minix/man/man8/irdpd.8 =================================================================== --- trunk/minix/man/man8/irdpd.8 (revision 9) +++ (revision ) @@ -1,74 +1,0 @@ -.TH IRDPD 8 -.SH NAME -irdpd \- internet router discovery protocol daemon -.SH SYNOPSIS -.B irdpd -.RB [ \-bd ] -.RB [ \-U -.IR udp-device ] -.RB [ \-I -.IR ip-device ] -.RB [ \-o -.IR priority-offset ] -.SH DESCRIPTION -.B Irdpd -looks for routers. This should be a simple task, but some routers are hard -to find because they do not implement the router discovery protocol. This -daemon collects information that routers do send out and makes it available. -.PP -At startup -.B irdpd -sends out several router solicitation broadcasts. A good router should -respond to this with a router advertisement. -.PP -If a router advertisement arrives then no more solicitations are sent. The -TCP/IP server has filled its routing table with the info from the -advertisement, so it now has at least one router. If the advertisement is -sent by a genuine router (the sender is in the table) then the -.B irdpd -daemon goes dormant for the time the advert is valid. Routers send new -adverts periodically, keeping the daemon silent. -.PP -Otherwise -.B irdpd -will listen for RIP (Router Information Protocol) packets. These packets -are sent between routers to exchange routing information. -.B Irdpd -uses this information to build a routing table. -.PP -Every now and then a router advertisement is sent to the local host to give -it router information build from the RIP packets. -.SH OPTIONS -.TP -.B \-b -Broadcast advertisements instead of sending them to the local host only. -This may be used to keep (non-Minix) hosts alive on a net without adverts. -.TP -.B \-d -Debug mode, tell where info is coming from and where it is sent. Debugging -can also be turned on at runtime by sending signal -.B SIGUSR1 -or turned off with -.BR SIGUSR2 . -.TP -.BI \-o " priority-offset -Offset used to make the gateway's preferences collected from RIP packets look -worse than those found in genuine router adverts. By default -.BR -1024 . -.SH "SEE ALSO" -.BR inet (8), -.BR boot (8), -.BR dhcpd (8), -.BR inetd (8), -.BR nonamed (8). -.SH BUGS -This daemon has gone out of favour thanks to -.BR dhcpd , -that also does router solicitations among other things. -.PP -Under standard MINIX 3 this daemon can't listen to both IRDP and RIP -at the same time, so it starts out with IRDP. It switches over to RIP -if it can't find a router, or if it threatens to lose its router. It -does not switch back. -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) Index: trunk/minix/man/man8/mkdist.8 =================================================================== --- trunk/minix/man/man8/mkdist.8 (revision 9) +++ (revision ) @@ -1,30 +1,0 @@ -.TH MKDIST 8 -.SH NAME -mkdist \- make a MINIX 3 distribution -.SH SYNOPSIS -.B mkdist -.SH DESCRIPTION -.B Mkdist -makes a MINIX 3 distribution on floppies. Run the command as -.B root -and follow the instructions. It will make one or two bootable installation -floppies and a compressed tar file of -.B /usr -on several floppies using -.BR vol (1). -.PP -The result can be installed on another system as described in -.BR usage (8), -except that all of -.B /usr -is saved on one set of floppies instead of being nicely split in binary -and source packages. -.SH "SEE ALSO" -.BR tar (1), -.BR compress (1), -.BR vol (1), -.BR usage (8). -.SH NOTES -Also very useful for making backups. -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) Index: trunk/minix/man/man8/mknod.8 =================================================================== --- trunk/minix/man/man8/mknod.8 (revision 9) +++ (revision ) @@ -1,33 +1,0 @@ -.TH MKNOD 8 -.SH NAME -mknod \- create a special file -.SH SYNOPSIS -\fBmknod \fIfile\fR [\fBb\fR] [\fBc\fR] \fImajor \fIminor\fR -.br -\fBmknod \fIfile\fR \fBp\fR\fR -.br -.de FL -.TP -\\fB\\$1\\fR -\\$2 -.. -.de EX -.TP 20 -\\fB\\$1\\fR -# \\$2 -.. -.SH EXAMPLES -.EX "mknod /dev/plotter c 7 0" "Create special file for a plotter" -.EX "mknod /dev/fd3 b 2 3" "Create a device for diskette drive 3" -.EX "mknod /tmp/stream p" "Create a named pipe" -.SH DESCRIPTION -.PP -.I Mknod -creates a special file named -.I file , -with the indicated major and minor device numbers. -The second argument specifies a block special, a character special, or a -named pipe. Named pipes do not have device numbers so they are omitted. -.SH "SEE ALSO" -.BR mkfifo (1), -.BR mknod (2). Index: trunk/minix/man/man8/monitor.8 =================================================================== --- trunk/minix/man/man8/monitor.8 (revision 9) +++ (revision ) @@ -1,606 +1,0 @@ -.TH MONITOR 8 -.SH NAME -monitor, edparams \- load and start MINIX 3, modify boot parameters -.SH SYNOPSIS -.B /boot -.br -.B edparams -.I device -.RI [ command " ...]" -.br -.B boot.com -.I virdisk -.RI [ command " ...]" -.SH DESCRIPTION -.de SP -.if t .sp 0.4 -.if n .sp -.. -This text describes the Boot Monitor, a boot time interactive program designed -not only to load and start MINIX 3, its most important task, but to also -provide an interface to configure MINIX 3 and to boot other operating systems. -.PP -The monitor is controlled with an environment that is modeled after the -Bourne shell. This environment is filled at startup with default values -that depend on the machine the monitor is running on and the environment -settings saved into the boot parameters sector (the second sector on a -device). When the environment is loaded, the monitor executes the function -named -.BR main , -which by default starts a simple menu. -.PP -The environment can be manipulated at boot time from the monitor prompt, -but may also be edited using -.B edparams -on a given device. -.B Edparams -simulates the monitor as much as it can, echoing commands it can't execute -between brackets. It can also be used in Makefiles and scripts by giving -it commands as arguments. -.PP -The DOS version of the monitor, usually named -.B boot.com -under DOS, boots MINIX 3 from a "DOS virtual disk". -.B Boot.com -is a simple COM program that interprets a DOS -file as a disk, loads a MINIX 3 kernel from the active partition in the same -way as the BIOS based monitor, and executes it to start MINIX 3. All the -monitor commands function in the same way, except for the -.B boot -command, it can only load MINIX 3. The monitor grabs as much free memory as -it can for MINIX 3 to work in, as the -.B memory -variable shows. Further details on how to run MINIX 3 under DOS, Windows 95, -or even Windows NT are written down in -.BR dosminix (8). -.SH COMMANDS -The monitor is best described by the commands you can type to the '>' -prompt. This is known as the "monitor mode". You can enter this mode by -hitting the Escape key. These are the monitor commands: -.PP -\fIname\fP = [\fBdevice\fP] \fIvalue\fP -.SP -.RS -Set environment variable. -.br -Changes the value of -.I name -to -.IR value . -The optional word -.B device -marks -.I name -as being subject to device translation. (See the section on devices.) These -(name, value) pairs are passed to the kernel who uses them to configure -itself. These variables are passed by default: -.SP -.B rootdev -.RS -This is the device used as your root device. It is by default set to -.BR ram, -which means that the device specified by -.B ramimagedev -will be loaded into the RAM disk and used as root. If you change this -variable then a physical device will be used as root, and the RAM disk will -be uninitialized and have the size specified by -.BR ramsize . -.RE -.SP -.B ramimagedev -.RS -Describes the device to use to initialize the RAM disk if -.B rootdev -is set to -.BR ram . -It's by default set to -.BR bootdev , -a special name for the device the monitor booted from. -.RE -.SP -.B ramsize -.RS -The size of the RAM disk. If the RAM disk is used for the root file system -then the root file system is stretched out to -.B ramsize -if possible. -.RE -.SP -.B processor -.RS -Set by default to -.BR 86 , -.BR 186 , -.BR 286 , -.BR 386 , -.BR 486 ", ..." -depending on the hardware you have. You can set it to a smaller value to -test your kernel in a more limited environment. -.RE -.SP -.B bus -.RS -The type of system bus, either -.BR xt , -.BR at -or -.BR mca . -This answers basic questions like: "How many interrupt controllers and how -to initialize?" Or: "Does the keyboard have LEDs?" -.RE -.SP -.B memory -.RS -List of memory free for use by MINIX 3. It is a comma separated list of -.IR base:size -pairs denoting the byte offsets and sizes of free memory in hexadecimal. -.B "800:925E0,100000:F00000" -is a typical example of about 585K starting at 2K, and 15M starting at 1M. -(The first 2K are BIOS parameters and the 53K under the 640K boundary is -the monitor itself.) The very last number you can play with if you know -what you are doing. Either increase it if the monitor has it wrong, or -decrease it to test if MINIX 3 still runs with less memory then normal. -.RE -.SP -.B video -.RS -Describes capabilities of the VDU: -.BR mda , -.BR cga , -.B ega -or -.BR vga . -.RE -.SP -.B chrome -.RS -Either -.B color -or -.BR mono . -.RE -.SP -.B c0 -.RS -By default -.B at -(AT compatibles), -.B bios -(XT or PS/2), or -.B dosfile -(running under DOS). -The -.B c0 -variable binds a driver to the first controller, i.e. the -.B /dev/c0* -devices. The monitor sets -.B c0 -to a suitable default, so that most machines can find their disk. -.RE -.SP -.B console -.RS -If set to a hexadecimal value it makes the monitor set the BIOS video mode to -this value when MINIX 3 is started. -This allows the use of video modes with more rows or colums than the -standard 80x25 mode. You can use any text mode in the 00-FF range, and VESA -extended modes in the 100-FFF range. Most text modes use a 9x16 font with -400 scanlines on screen, so you see 400/16 = 25 lines. The text mode can be -modified by adding special flags to the console setting. Add -2000 to switch to 480 scan lines, adding 20% more lines to the screen. Add -4000 to select a 9x14 font, so 28 or 34 lines are shown. Add 8000 instead -to select an 8x8 font showing 50 or 60 lines. Each setting has drawbacks. -Using 480 scanlines implies a 60 Hz refresh, so the screen may flicker. The -8x8 font looks squashed. More letters on screen require more memory, so there -is less for virtual consoles. Interesting modes to try are 4003 (80x28), -2003 (80x30), 6003 (80x34), 8003 (80x50), A003 (80x60), 109 (132x25), -10A (132x43), 10B (132x50), 10C (132x60). The 109 VESA mode is often -available, and can be modified like mode 3. Use mode 7 instead of 3 for -monochrome. Which modes and flags work can only be found out by experiment. -More parameters may follow the mode number that are of interest -to the console driver, see -.BR boot (8). -.RE -.SP -.B dosfile-d0 -.RS -Set by the DOS version of the monitor to the name of the virtual disk, i.e. -the -.I virdisk -argument as shown above. The "dosfile" driver -will use this as the name of the file to use as a disk. -.RE -.SP -Two variables are only used by the monitor, even though they are passed to the -kernel too: -.SP -.B image -.RS -The name of the file containing the kernel image, by default -.BR minix . -If it refers to a directory however then the newest file inside the -directory is chosen to be the kernel image. The names inside -.B /minix/ -are best set to the MINIX 3 version you are using, which looks good when the -monitor prints its name. Rules for pretty printing image names: -.RS -.SP -A '/' or '_' is changed to a space. -.SP -The first letter is changed from lowercase to uppercase. -.SP -An 'r' if followed by a digit changes to " revision ". -.RE -.RE -.SP -.B label -.RS -If set then only processes marked with this label or without a label are -loaded from the image. -.RE -.SP -.B Installboot \-boot -will create functions to select images and labels. These functions will set -.B label -and -.B image -and echo what you selected. The two numbers separated by a colon used as an -image name tell the starting sector and sector count of the image on disk. -.RE -.SP -\fIname\fP() \fIcommand\fP -.RS -Define function. -.br -Functions may be used to bundle a set of commands, so that you can easily -boot MINIX 3 with a different set of parameters then normal. E.g. -.SP -.RS -ram() { rootdev=ram; boot } -.RE -.SP -will allow you to run MINIX 3 with the root device on RAM for a change, if you -normally use a real device as root. There are three predefined functions, -.BR leader , -with default value an -.B echo -command that shows the monitor's startup banner, -.BR main , -with default value -.BR menu , -and -.BR trailer , -with default value a command that clears the screen. -The monitor executes -.B leader;main -at startup to show the banner message and a menu. The -.B trailer -function is executed just before MINIX 3 is started. These three functions can -be redefined as you please. -.RE -.SP -\fIname\fP(\fIkey\fP) \fIcommand\fP -.RS -Define kernel selecting function. -.br -The menu command uses functions like these to add menu entries to select -a different kernel from a boot disk. -.B Installboot \-boot -produces these functions when the images are labeled. The label -.B AT -would give: -.SP -.RS -AT(a) {label=AT;image=42:626;echo AT kernel selected;menu} -.RE -.SP -With the menu option: -.SP -.RS -a Select AT kernel -.RE -.SP -Typing -.B a -will then execute the -.B AT -function above. -.RE -.SP -\fIname\fP(\fIkey\fP,\fItext\fP) \fIcommand\fP -.RS -User defined menu option. -.br -This variant may be used to make any menu entry you like: -.SP -.RS -dos(d,Boot MS-DOS) boot d0p0 -.RE -.SP -.I Text -may be anything, even parentheses if they match. -.RE -.SP -.I name -.RS -Call function. -.br -If -.I name -is a user defined function then its value is expanded and executed in place of -.IR name . -Try a recursive one like 'rec() {rec;xx}' one day. You can see the monitor -run out of space with nice messages about using -.BR chmem (1) -to increase it's heap. -.RE -.SP -\fBboot\fP [\fB\-\fP\fIopts\fP] -.br -\fBboot\fP \fIdevice\fP -.RS -Boot MINIX 3 or another O.S. -.br -Without an argument, -.B boot -will load and execute the MINIX 3 image named by the -.B image -variable. With options the variable -.B bootopts -is first set to -.BI \- opts -before MINIX 3 is started, and unset when Minix returns. With a -.I device -argument, -.B boot -loads the boot sector of -.I device -into memory and jumps to it, starting another operating system. You would -normally use partitions on the first hard disk for this command (d0p[0\-3]), -using d0 will also work (choosing the active partition). One can also boot -devices on the second hard disk (d1, d1p[0\-3]) if the bootstrap writer did -not hardwire the disk number to disk 0. -.br -Some Operating Systems can only be booted from the active partition, if -you use a '*', e.g. -.BR "boot *d0p2" , -then partition 2 is first made active. You'll then need to use -.SP -.RS -.BI "installboot \-m /dev/c0d0 /usr/mdec/jumpboot" " keys" -.RE -.SP -with -.I keys -chosen so that MINIX 3 is booted at startup. (See -.BR installboot (8).) -.RE -.SP -\fBctty\fP \fIn\fP -.RS -Copies output to and takes input from serial line -.I n -(0-3) at 9600 baud, 8 bits, no parity. -This allows you to control a MINIX 3 system remotely through an RS-232 -connection. -.RE -.SP -\fBdelay\fP [\fImsec\fP] -.RS -Delay (500 msec default). -.br -Fast booting speed was one of the objectives when this program was created, -so a hard disk boot usually takes only a fraction of a second. If you need -some time (to hit Escape, or stare at the numbers) you can use -.B delay -to make the monitor pause for a specified number of milliseconds. -.RE -.SP -\fBecho\fP \fIword\fP ... -.RS -Print these words. -.br -Used to display messages, like the startup banner. Echo normally prints -the words with spaces in between and a newline at the end. Echo understands -special '\e' escape sequences as follows: -.RS -.SP -\e (At the end) Don't print a newline. -.br -\en Print a newline. -.br -\ev Print the monitor's version numbers. -.br -\ec Clear the screen. -.br -\ew Wait until a RETURN is typed -.br -\e\e Print a backslash. -.RE -.RE -.SP -\fBls\fP [\fIdirectory\fP] -.RS -List contents of a directory. -.br -Useful when looking for kernel images. -.RE -.SP -.B menu -.RS -Menu driven startup. -.br -This command allows you to execute functions defined with a -.IR key . -If no menu functions have been defined then -.B menu -will use this one hidden built-in function: -.SP -.RS -*(=,Start Minix) boot -.SP -.RE -Kernel selecting functions only add new options to this set, but if you -define a two argument function yourself then the above one is no longer -shown, allowing you to customize the menu completely. Your first -function definition should therefore be one that starts MINIX 3. -.SP -Menu entries are shown in the same order as -.B set -shows them. If you don't like the order then you have to unset the -functions and retype them in the proper order. -.SP -If you type a key then a scheduled trap is killed and the appropriate menu -function is executed. If you need more time to choose then hit the -spacebar. A key not on the menu also kills a trap, but does nothing more. -.RE -.SP -.B save -.RS -Save environment. -.br -This will save all the environment variables and functions with nondefault -values to the parameter sector (the second sector on the boot device), so -they are automatically set the next time you boot the monitor. -.RE -.SP -.B set -.RS -Show environment. -.br -Show the current values of the environment variables and functions. Default -values are shown between parentheses to distinguish them from values that -were explicitly set. -.RE -.SP -\fBtrap\fP \fImsec\fP \fIfunction\fP -.RS -Schedule function. -.br -Schedules a function to be executed after -.I msec -milliseconds. Only the monitor mode cannot be interrupted, a scheduled trap -is killed when the prompt is printed. Example: -.SP -.RS -main() {trap 10000 boot; menu} -.RE -.SP -This gives you 10 seconds to choose a menu option before MINIX 3 is booted. -.RE -.SP -\fBunset\fP \fIname\fP ... -.RS -Unset environment variables. -.br -Removes the named variables and functions from the environment, and sets -special variables back to their default values. This is also the only way -to remove the "device name translation" property from a variable. -.RE -.SP -\fBexit\fP -.RS -Exit the monitor. -.br -Reboot the machine, exit to MINIX 3 or exit to DOS as appropriate. -.RE -.SP -\fBoff\fP -.RS -Turn the PC off. -.br -If the PC supports power management then turn it off, otherwise -print some error messages and do nothing. -.RE -.SP -\fB{\fP \fIcommand\fP; ... \fB}\fP -.RS -Bundle commands. -.br -Treat a number of commands as a single command. Used for function -definitions when a function body must contain more than one command. -.RE -.SH DEVICES -The MINIX 3 kernel can't do anything with device names, so they have to be -translated to device numbers before they are passed to the kernel. This -number is found under the st_rdev field (see -.BR stat (2)) -of the file on the boot file system. The monitor will look for the device -file with the working directory set to '/dev'. If it can't find the device -name then it will translate names like 'ram', 'fd1', 'c0d1p0', 'c1d0p2s0', -and even the obsolete 'hd2a' to what it itself thinks the numbers should be. -.PP -The special name -.B bootdev -is translated to the name of the device booted from, like 'fd0', -or 'c0d0p1s0', and then searched for in /dev. -.B Bootdev -can only be translated to a device for the first controller, and only if -the disks on that controller are numbered without "gaps". (The master -device on the second IDE channel is always d2 on MINIX 3. The BIOS will -call it disk 0, 1, or 2 depending on the number of disks on the first -IDE channel.) -.SP -Controller numbers are meaningless to the BIOS, so everything is assumed to -be attached to controller 0. You can omit -.B c0 -for device names, and it is best to always omit -.B c0 -for the -.B boot -command, and to always use the full name for variables passed to MINIX 3. -.SH EXTENSIONS -A few extensions have been made to this program for kernel hackers. They -may be triggered by setting bits in the flags word in the kernel startup -code (the mpx file.) The flag bits are: -.TP 10 -0x0001 -Call kernel in 386 mode. -.TP -0x0002 -Do not make space for the bss areas of processes other than the kernel. -.TP -0x0004 -Use the stack size set by -.BR chmem (1). -.TP -0x0008 -Load MM, FS, etc. into extended memory. -.TP -0x0010 -No need to patch process sizes into the kernel. -.TP -0x0020 -The kernel can return to the monitor on halt or reboot. -.TP -0x0040 -Offer generic BIOS support instead of just INT 13 (disk I/O). -.TP -0x0080 -Pass memory lists for free and used memory (processes). -.TP -0x0100 -Kernel returns monitor code on shutdown in boot parameters array. -.SH "SEE ALSO" -.BR controller (4), -.BR installboot (8), -.BR usage (8), -.BR boot (8), -.BR dosminix (8). -.SH BUGS -The -.B delay -command will hang forever on the original IBM PC (not the XT!). Not that it -matters, as everything takes forever on that box. -.PP -By redefining -.B leader -one can easily hide the identity of this program. -.SH ACKNOWLEDGMENTS -Earl Chew, for the inspiration his ShoeLace package provided, unless he wants -to file a "look and feel" suit against me, then I will say I modeled it after -the Sun ROM boot monitor, which is also true. -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) -.\" -.\" $PchId: monitor.8,v 1.11 2002/02/27 19:36:34 philip Exp $ Index: trunk/minix/man/man8/nonamed.8 =================================================================== --- trunk/minix/man/man8/nonamed.8 (revision 9) +++ (revision ) @@ -1,306 +1,0 @@ -.\" These numbers should match those in nonamed.c: -.ds ST "two seconds" -.ds MT "four seconds" -.ds LT "five minutes" -.ds HT "one hour" -.ds NI "256" -.TH NONAMED 8 -.SH NAME -nonamed \- not a name daemon, but acts like one -.SH SYNOPSIS -.B nonamed -.RB [ \-qs ] -.RB [ \-d [\fIlevel\fP]] -.RB [ \-p -.IR port ] -.SH DESCRIPTION -.de SP -.if t .sp 0.4 -.if n .sp -.. -.B Nonamed -is not a name daemon. It can answer simple queries from -.BR /etc/hosts , -but anything else is relayed to a real name daemon. -.B Nonamed -maintaines a small cache of replies it has seen from a name daemon, and will -use this cache to minimize traffic if the machine is permanently connected -to the Internet, or to answer requests if the machine is often disconnected -from the Internet, i.e. a computer at home. -.PP -On startup -.B nonamed -sends a simple query to each of its name servers to see if one is up. This -is repeated every \*(LT in an "at home" situation, or when necessary if the -current name daemon doesn't respond. The first name server to answer is -used as the current name server to answer queries. -.PP -If no name servers are found in the DHCP data or -.BR /etc/hosts -then only the hosts file is used to answer queries, and any query for a name -not in that file gets a failure response. -.PP -.B Nonamed -accepts both UDP and TCP queries under Minix-vmd. Under standard MINIX 3 -only UDP queries are accepted. \*(NI relayed UDP queries can be outstanding -before it forgets where the first one came from. -.PP -Using the hosts file, -.B nonamed -can answer simple DNS queries to translate a host name to an IP address, or -an IP address to a host name. Suppose -.B /etc/hosts -looks like this: -.PP -.RS -.ta +15n -.nf -10.0.0.1 flotsam.cs.vu.nl\0www -10.0.0.2 jetsam.cs.vu.nl -.fi -.RE -.PP -Then queries for the host names listed can be answered with the IP addresses -to the left of them. An alias like "www" above is seen as a CNAME for the -first host name on the line, in the same domain as the first host name if -unqualified (no dots). A reverse lookup for an IP address on the left is -answered by the first host name on the right. If more than one match is -possible then all matches are put in the answer, so all IP addresses of -multihomed hosts can be listed by multiple entries in the hosts file. -.PP -Requests for names like "flotsam.cs.vu.nl.cs.vu.nl" that are often generated -on a domain search for an already fully qualified domain name -are recognized and made to fail. This kludge avoids a lot of unnecessary -requests to possibly unreachable name servers and client timeouts. -.PP -The name "localhost" in any domain is given the IP address 127.0.0.1. -.PP -.B Nonamed -employs several timeouts for efficient operation: -.PP -If no UDP reply is seen in \*(MT then a new search is started for a name -server in the hope of finding one that does work. -A failing TCP connection will also invoke a search, the -TCP connection is then made to the new name server. A client using UDP will -retry eventually, a client using TCP will notice nothing but a short delay. -If a TCP connection fails after 5 tries then an answer is sought in the -hosts file, and failing that the connection is closed. -.PP -Any TCP operation is given \*(LT to show any action before the connection is -aborted. -.PP -UDP replies from a name server are put in a cache of by default 8 (16-bit -system) or 16 kilobytes (32-bit system). New queries are -first sought in the cache, and if found answered from the cache. An entry -in the cache is expired when the resource record with the smallest TTL (time -to live) expires, unless its expire time is artificially extended by the -"%stale" parameter (see below). An answer from the cache has all TTLs -appropriately lowered, and the AA bit ("answer authoritive") is cleared. -Any request answered by stale data is refreshed as soon as -.B nonamed -notices that one of the external name daemons is reachable. -.PP -Data is only cached if it is has "no error" result code, or a "no such -domain" result code with a SOA record in the name server section, and all -records have a nonzero TTL. The %stale parameter has no effect on the -decision to cache a result. -.PP -The cache is rewritten to the cache file \*(LT after a new entry has been -added. Mere changes to the order in the cache don't cause a rewrite. -.SS Configuration through /etc/hosts -The real name servers, stale data extension, and cache size can be -configured by special entries in the hosts file. For example: -.PP -.RS -.ta +\w'172.16.24.3'u+2m +\w'%nameserver'u+2m -.nf -86400 %ttl # Answers from this file get this TTL -2419200 %stale # Stale data may linger on for 4 weeks -32768 %memory # 32k cache size -10.0.0.1 %nameserver # flotsam -172.16.24.3 %nameserver # dns1.example.com -172.16.24.6 %nameserver # dns2.example.com -.SP -10.0.0.1 flotsam.home.example.com\0www -10.0.0.2 jetsam.home.example.com -.fi -.RE -.PP -In this example we have two machines, flotsam and jetsam, that are at home. -Answers from the hosts file get a TTL of one day, by default this is \*(HT. -Normally there is no connection to the Internet, so any stale data in the -cache is allowed to linger on for 2419200 seconds (4 weeks) before it is -finally discarded. The cache size is set to 32 kilobytes. The first name -server is the flotsam. On the flotsam itself this entry is ignored, but the -jetsam will now run its requests through flotsam if possible. This means -that both flotsam and jetsam use the cache of the flotsam. The other -nameserver entries are external name servers of the Internet provider. -.PP -If no nameservers are listed in the hosts file then they are obtained from -data gathered by DHCP. This is the preferred situation. -.PP -If the hosts file contains a line that says: -.PP -.RS -.BI include " file" -.RE -.PP -Then the current hosts file is closed and the file named is read next. -.SS "Automatic calling" -If your connection to the Internet is set up on demand, either in software -on the machine that has the modem, or by a special box such as an ISDN -router, then you need to filter the name server probes that -.B nonamed -sends out every \*(LT to see if a real name daemon is reachable. These -probes need to be recognized as packets that must not trigger a call, and -that must not keep the line up. You can either filter all IP packets -destined for port 53 decimal (the -.B domain -port). This may be a bit too much, the first packet out is often a normal -DNS request (not a probe), so you may want to do better. A probe by -.B nonamed -is a nonrecursive request for the name servers of the root domain. You -can recognize them by looking at the flags, they are all off. Here is a -typical probe in hex (twenty octets per line), followed by the names of -interesting fields, and the octets values you should look for: -.PP -.RS -.nf -45 00 00 2D C8 19 00 00 1D 11 53 18 AC 10 66 41 AC 10 18 03 -00 35 00 35 00 19 79 93 00 00 00 00 00 01 00 00 00 00 00 00 -00 00 02 00 01 -.SP -ip ip ip ip ip ip ip ip ip ip ip ip si si si si di di di di -sp sp dp dp xx xx xx xx id id fl fl qd qd an an ns ns ar ar -dn ty ty cl cl -.SP -45 xx xx xx xx xx xx xx xx 11 xx xx xx xx xx xx xx xx xx xx -xx xx 00 35 xx xx xx xx xx xx 00 00 xx xx xx xx xx xx xx xx -xx xx xx xx xx -.SP -.fi -(ip = IP header, si = source IP, di = dest IP, sp = source port, dp = dest -port, id = DNS ID, fl = DNS flags, qd = query count, an = answer count, ns = -nameserver count, ar = additional records count, dn = domain (""), ty = type -(NS), cl = class (IN).) -.RE -.PP -So if a packet has octets 45, 11, 00 35, and 00 00 at the appropriate places -then don't let it cause a call. Read the documentation of your software/router -to find out how to do this. Hopefully it is possible to view the contents of -the packet that triggered the last call. If so you simply let -.B nonamed -bring up the line once with a probe. -.SS "Remote information" -The program version and name servers it is working with can be obtained with: -.PP -.RS -host \-r \-v \-c chaos \-t txt version.bind. \fIserver\fP -.RE -.PP -.I Server -is the name or IP address of the host whose name server you want to know -this of. -(This call is really an undocumented hack to ask the version numbers of the -BIND name daemon. It just had to be implemented for -.B nonamed -as well.) -.PP -The % variables in the hosts file can be viewed like this: -.PP -.RS -host \-r \-t a %nameserver. \fIserver\fP -.RE -.PP -Don't forget the dot at the end of the name. %ttl and %stale will be shown -as a dotted quad, e.g. 0.36.234.0. The proper value can be computed as 36 * -65536 + 234 * 256 + 0 = 2419200. -.SH OPTIONS -The options are only useful when debugging -.BR nonamed , -although it can be very instructive to watch DNS queries being done. -.TP -.BR \-d [\fIlevel\fP] -Set debugging level to -.I level -(by default -.BR 1 .) -Debug mode 1 makes -.B nonamed -decode and display the DNS queries and replies that it receives, sends and -relays. In debug mode 2 it prints tracing information about the internal -jobs it executes. In debug mode 3 it core dumps when an error causes it to -exit. The debugging level may also be increased by 1 at runtime by sending -signal -.B SIGUSR1 -or turned off (set to 0) with -.BR SIGUSR2 . -.TP -.RB [ \-p " \fIport\fP] -Port to listen on instead of the normal -.B domain -port. -.TP -.RB [ \-q ] -Read the cache file with the debug level set to 2, causing its contents to -be printed, then exit. -.TP -.RB [ \-s ] -Run single: ignore hosts or cache file, only use the DHCP information. This -allows another -.B nonamed -to be run on a different interface to serve a few programs that run there. -.SH FILES -.TP 15n -/etc/hosts -Hosts to address translation table and configuration file. -.TP -/usr/run/nonamed.pid -Process ID of the currently running -.BR nonamed . -.TP -/usr/adm/nonamed.cache -Copy of the cache. Read when the program starts, written \*(LT after -something has been added to it, and written when a SIGTERM signal is -received, which is normally sent at system shutdown. -.TP -/usr/adm/dhcp.cache -Data gathered by the DHCP daemon. Among lots of other junk it lists name -servers that we should use. -.SH "SEE ALSO" -.BR gethostbyname (3), -.BR resolver (3), -.BR hosts (5), -.BR inet (8), -.BR boot (8), -.BR inetd (8), -.BR dhcpd (8). -.SP -.BR RFC-1034 -and -.BR RFC-1035 . -.SH NOTES -Do not use the %stale parameter for a PC that is directly connected to the -Internet. You run the risk of getting wrong answers, a risk that is only -worth taking for a system that is mostly disconnected from the Internet. -.PP -You can specify one or more remote name servers in -.B /etc/resolv.conf -so that nonamed isn't needed. This will save memory, but you'll lose -.BR nonamed 's -cache and its "offline" tricks. That's no problem if you can use a -neighbouring name daemon on another PC at home. -.PP -The default cache size seems to be more than enough for normal use, but if -you do decide to make it larger then don't forget to increase the stack size -of the program under standard MINIX 3. -.PP -Don't let two -.BR nonamed 's -forward queries to each other. They will pingpong a query over the -network as fast as they can. -.SH BUGS -The idea of serving "stale DNS data" will probably make some purists -violently sick... -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) Index: trunk/minix/man/man8/part.8 =================================================================== --- trunk/minix/man/man8/part.8 (revision 9) +++ (revision ) @@ -1,116 +1,0 @@ -.TH PART 8 -.SH NAME -part \- partition table editor -.SH SYNOPSIS -.B part -.RI [ device "] ..." -.SH DESCRIPTION -.B Part -is a screen oriented partition table editor. -.PP -While editing you will see six lines of numbers, the first line shows the -device name and its geometry (number of cylinders, heads and sectors), the -second shows the start and end of the drive or partition you are working on, -the last four lines show the different partitions or subpartitions. All -numbers except those on the second line can be edited. Question marks are -showed instead of numbers if the partition table is not loaded yet. You -have to select a device and type 'r'. -.PP -Editing is a simple matter of moving around with the arrow keys and changing -the values with + and \- (or PgUp and PgDn), or by typing the desired value. -The '?' key will give a small list of commands, the '!' key gives advice on -how to make a new entry. -.PP -The spacebar toggles between showing the size of the partition and the last -sector on the partition. Useful to check if a partition is adjacent to the -next. -.PP -The 'm' key is "magical", it lets you cycle through a set of interesting -values for the base or size of a partition. These values are: Aligned to a -cylinder, taped to other partitions (inside or outside), or filling out holes. -.BR "Use this key" ! -.PP -MINIX 3 subpartition tables or extended partitions may be edited after hitting -the '>' key. The number of this partition will be shown after the device -name on the second row, e.g. -.BR /dev/hd0:2 . -MINIX 3 subpartition tables are shown as is, but extended partition bases are -translated to absolute offsets on the screen to hide the gory details of their -implementation from the innocent user. (Hit 'p' if you dare.) The '<' key -will bring you back to the enclosing partition table. -.PP -With arguments, -.B part -will use the given devices or files. Without arguments, -.B part -will use all interesting block devices in -.B /dev -sorted by device number and starting with -.BR /dev/hd0 . -.PP -Values that are out of range, overlapping, or otherwise strange are shown in -reverse video. Values that may possibly be a problem for operating systems -other then MINIX 3 are shown in bold characters. -.PP -The name of the device is highlighted when it has not been read yet. -.PP -Head or sector numbers are highlighted if the partition does not start or -end at a cylinder boundary. -.PP -The base and/or size field is highlighted if they fall outside the device, -if they are inside some other partition, if the base equals the device's base -(no room for the boot sector), or if the size is zero. -.PP -.B Part -complies with the good old \s-2UNIX\s+2 tradition of trusting the user. -It will write any table, no matter how bad. You have been warned. -.PP -By the way, as far as MINIX 3 is concerned there is absolutely no reason to -make partitions start precisely on a cylinder or track nor does it have to -be an exact number of cylinders long. MINIX 3 only looks at the base and size -of a partition, the geometry of the drive doesn't have to be correct. Other -Operating systems can be very picky about partitions that are not aligned. -Some partition editors may refuse to edit a table, others may even make a -mess of the table. The only exception is the first partition, it -traditionally starts on the first track, not the first cylinder. All -editors must understand this. (Subpartition tables are MINIX 3 specific, so -there is no reason at all for any alignment.) -.SS "Extended Partitions" -Extended partitions are a mess that is only made slightly better by -.B part -by translating the base offsets to absolute numbers. It is better to use DOS -.B fdisk -to create them, but if you insist on using -.B part -then this is what they should look like: -.RS -.sp -The extended partition entry in the primary partition table must cover the -whole logical partition space within it. -.sp -The area thus created is split in segments, each segment contains a partition -table in sector 0 and one (just one) logical partition. -.sp -The first entry of a segment's partition table describes this logical -partition: it's partition ID, base and size. -.sp -The second entry is an extended partition that describes base and size of -the next segment (partition table and logical partition). The last segment's -partition table is empty, or contains one logical partition. -.SH "SEE ALSO" -.BR mkfs (1), -.BR fd (4), -.BR hd (4). -.SH BUGS -You can have a table read, messed up, and written in no time, be careful. -.PP -You can't type head or sector numbers directly. -.PP -Sectors are counted from 0 for consistency, but the partition table counts -from 1 like DOS addresses them. Most confusing. -.PP -You can't write a backup copy to a file, that's what -.BR dd (1) -with count=1 is for. -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) Index: trunk/minix/man/man8/partition.8 =================================================================== --- trunk/minix/man/man8/partition.8 (revision 9) +++ (revision ) @@ -1,66 +1,0 @@ -.TH PARTITION 8 -.SH NAME -partition \- make a partition table -.SH SYNOPSIS -.B partition -.RB [ \-mfn ] -.I device -[\fItype\fP:]\fIlength\fP[\fB+*\fP] ... -.SH DESCRIPTION -.B Partition -makes a partition table on -.I device -using the types and sizes given. It may be used in combination with -.BR repartition (8) -for automatic installation of MINIX 3. -.PP -You may give up to four \fItype\fP:\fIlength\fP[\fB+*\fP] specifications -for the partitions. You may also specify holes before, between, and after -the partitions. A hole differs from a partition specification by not having -a type. -.PP -The first hole is by default 1 sector to make space for the primary -bootstrap and the partition table. The other holes are 0. -.PP -The -.I type -field is the type of the partitition in hexadecimal. The -.I length -field is the partition's size in sectors. The -.B + -or -.B * -may optionally be added to indicate that the partition must be expanded -to contain any leftover space on the device or to mark the partition active. -.PP -Instead of a length you may use the word -.B exist -to indicate that an existing partition of the given type must be kept -from the old partition table. -.PP -Partitions are padded out to cylinder boundaries, except for the first one, -it starts on track 1. Some operating systems care about this. MINIX 3 and -MS-DOS do not. -.SH OPTIONS -.TP -.B \-m -MINIX 3 only, no need to pad partitions. This is the default for subpartition -tables. -.TP -.B \-f -Force making a partition table even if the device is too small. -.TP -.B \-n -Play-act, don't write the new table, just show what it would look like. -.SH EXAMPLE -.B "partition /dev/hd0 01:16384 81:40000 81:2880* 06:20000+" -.PP -Partitions disk 0 into an 8 Mb DOS partition, 20 Mb MINIX 3 /usr, 1.44 Mb MINIX 3 -/ (active), and a DOS partition of at least 10 Mb at the end of the disk. -(06:0+ would have been ok too, it's just a sanity check.) -.SH "SEE ALSO" -.BR hd (4), -.BR part (8), -.BR repartition (8). -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) Index: trunk/minix/man/man8/pr_routes.8 =================================================================== --- trunk/minix/man/man8/pr_routes.8 (revision 9) +++ (revision ) @@ -1,26 +1,0 @@ -.TH PR_ROUTE 8 -.SH NAME -pr_routes \- show IP routing. -.SH SYNOPSIS -.B pr_routes -.RB [ \-i -.RI "ip device]" -.SH DESCRIPTION -.de SP -.if t .sp 0.4 -.if n .sp -.. -.B Pr_routes -displays the IP routing table. -.SH OPTIONS -.TP -.B \-i -.I "ip device" -specifies the ip device. -.SH "SEE ALSO" -.BR add_route (8), -.BR irdp (8). -.SH AUTHOR -.I Pr_routes.c -was written by Philip Homburg. -This manual page by A. S. Woodhull, last revised 13.02.96. Index: trunk/minix/man/man8/printroot.8 =================================================================== --- trunk/minix/man/man8/printroot.8 (revision 9) +++ (revision ) @@ -1,29 +1,0 @@ -.TH PRINTROOT 8 -.SH NAME -printroot \- print the name of the root device on standard output -.SH SYNOPSIS -\fBprintroot\fR -.br -.de FL -.TP -\\fB\\$1\\fR -\\$2 -.. -.de EX -.TP 20 -\\fB\\$1\\fR -# \\$2 -.. -.SH OPTIONS -.FL "\-r" "Print only the root device, not a full mtab line" -.SH EXAMPLES -.EX "printroot" "Print the name of the root device" -.SH DESCRIPTION -.PP -.I Printroot -is useful for initializing the \fI/etc/mtab\fR when the system is booted. -It figures out what the root device is by searching \fI/dev\fR until it -finds a block special file with the right major/minor device numbers. -.SH "SEE ALSO" -.BR fstab (5), -.BR boot (8). Index: trunk/minix/man/man8/pwdauth.8 =================================================================== --- trunk/minix/man/man8/pwdauth.8 (revision 9) +++ (revision ) @@ -1,58 +1,0 @@ -.TH PWDAUTH -.SH NAME -pwdauth \- password authentication program -.SH SYNOPSIS -.B /usr/lib/pwdauth -.SH DESCRIPTION -.B Pwdauth -is a program that is used by the -.BR crypt (3) -function to do the hard work. It is a setuid root utility so that it is -able to read the shadow password file. -.PP -.B Pwdauth -expects on standard input two null terminated strings, the -password typed by the user, and the salt. That is, the two arguments of -the -.B crypt -function. The input read in a single read call must be 1024 characters or -less including the nulls. -.B Pwdauth -takes one of two actions depending on the salt. -.PP -If the salt has the form "\fB##\fIuser\fR" then the -.I user -is used to index the shadow password file to obtain the encrypted password. -The input password is encrypted with the one-way encryption function -contained within -.B pwdauth -and compared to the encrypted password from the shadow password file. If -equal then -.B pwdauth -returns the string "\fB##\fIuser\fR" with exit code 0, otherwise exit -code 2 to signal failure. The string "\fB##\fIuser\fR" is also returned -if both the shadow password and the input password are null strings to -allow a password-less login. -.PP -If the salt is not of the form "\fB##\fIuser\fR" then the password is -encrypted and the result of the encryption is returned. If salt and -password are null strings then a null string is returned. -.PP -The return value is written to standard output as a null terminated string -of 1024 characters or less including the null. -.PP -The exit code is 1 on any error. -.SH "SEE ALSO" -.BR crypt (3), -.BR passwd (5). -.SH NOTES -A password must be checked like in this example: -.PP -.RS -pw_ok = (strcmp(crypt(key, pw->pw_passwd), pw->pw_passwd) == 0); -.RE -.PP -The second argument of crypt must be the entire encrypted password and -not just the two character salt. -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) Index: trunk/minix/man/man8/rarpd.8 =================================================================== --- trunk/minix/man/man8/rarpd.8 (revision 9) +++ (revision ) @@ -1,75 +1,0 @@ -.TH RARPD 8 -.SH NAME -rarpd \- reverse address resolution protocol daemon -.SH SYNOPSIS -.B rarpd -.RB [ \-d [\fIlevel\fR]] -.I network-name -\&... -.SH DESCRIPTION -.de SP -.if t .sp 0.4 -.if n .sp -.. -.B Rarpd -listens on the given networks for broadcast packets asking for reverse address -resolution. These packets are sent by hosts at boot time to find out their -IP address. -.B Rarpd -looks up the six octet ethernet number in the -.B /etc/ethers -file finding a host name. This name is translated to the IP address of the -host by a DNS lookup. The IP address is then sent to the host. -.PP -Under MINIX 3 the program forks as needed to give each network its own server. -Under Minix-vmd all networks are handled in the same program using async I/O. -.SS "Private Ethernet Addresses" -For VU practical work, where students have to create their own IP stack -starting at the bottom with RARP, this implementation recognizes Ethernet -addresses starting with octet 0x76 as special. The next octet is used as a -additional host number and the next and last four octets as an IP address -that this Ethernet address is additional for. The IP address is translated -back to a name, and the first component of that name gets a dash and the -additional host number added to it. That hostname is then looked up and its -IP address returned in a RARP reply. Example: -.PP -.RS -.ta +\w'flotsam-3.example.commmm'u -76:3:c0:a8:e7:fa Additional 3, IP 192.168.231.250 -.SP -flotsam.example.com Reverse lookup on 192.168.231.250 -.SP -flotsam-3.example.com Splicing in additional number -.SP -192.168.231.42 Forward lookup -.RE -.PP -In this example a RARP query for 76:3:c0:a8:e7:fa gets 192.168.231.42 as reply. -.SH OPTIONS -.TP -.BR \-d [\fIlevel\fP] -Turns on debugging messages at the given level, by default 1. At level 1 you -will be shown what answers are sent, and at level 2 or higher you will be told -about queries from unknown hosts or host on the wrong network. -The debug level can also be increased by 1 at runtime by sending signal -.B SIGUSR1 -or turned off (set to 0) with -.BR SIGUSR2 . -.SH "SEE ALSO" -.BR ifconfig (8), -.BR ethers (5), -.BR hosts (5), -.BR inet (8), -.BR boot (8), -.BR dhcpd (8), -.BR irdpd (8), -.BR inetd (8), -.BR nonamed (8). -.SH NOTES -A "network name" is the device name of the IP device of a network, i.e. -.BR ip0 , -.BR ip1 ", ..." -.PP -The RARP protocol has gone out of fashion in favour of DHCP. -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) Index: trunk/minix/man/man8/rdate.8 =================================================================== --- trunk/minix/man/man8/rdate.8 (revision 9) +++ (revision ) @@ -1,20 +1,0 @@ -.TH RDATE 8 -.SH NAME -rdate \- set time and date from a remote host -.SH SYNOPSIS -.B rdate -.IR host " ..." -.SH DESCRIPTION -.B Rdate -obtains the current time from a remote time server. If run by the -super-user then local time is set to that time. The time of the remote host -is printed on standard output. -.PP -More than one host name may be specified. They are tried one by one until -one responds. -.SH "SEE ALSO" -.BR date (1), -.BR readclock (8), -.BR inet (8). -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) Index: trunk/minix/man/man8/readclock.8 =================================================================== --- trunk/minix/man/man8/readclock.8 (revision 9) +++ (revision ) @@ -1,61 +1,0 @@ -.TH READCLOCK 8 -.SH NAME -readclock \- read the AT's real time clock -.SH SYNOPSIS -\fBreadclock\fP [\fB\-nwW2\fP] -.SH DESCRIPTION -.B Readclock -reads the AT's real time clock and sets the machine's time. It is usually -the second thing done in -.BR /etc/rc , -the first thing is setting the time zone by sourcing -.BR /etc/profile . -This means that the clock is assumed to tell the wall clock time. If you -want to run the clock in GMT then you can put -.B "TZ=GMT" -(or any other TZ value) in front of the readclock command. -.SH OPTIONS -.TP -.B \-n -Play-act, don't set the time nor change the calibration data, just show what -would be done. -.TP -.B \-w -Write the current time to the CMOS clock. Dangerous, see -.BR BUGS . -Don't forget to use -.B "TZ=GMT" -in front of readclock if the clock should run in GMT. -.TP -.B \-W -Like -.BR \-w , -but also sets the status registers of the CMOS clock to their proper values. -(For if the clock suddenly runs at an odd pace or has stopped and the BIOS -doesn't repair it.) -.TP -.BR \-2 , -Add 20 to any year before 2000. If your CMOS clock year can't run past 2000, -then you can set it to 1980 and use -.B \-2 -to correct the year. Together with -.B \-w -the year minus 20 is written to the clock. -.SH FILES -.TP 20n -/etc/profile -Timezone and other shell initialization code. -.SH "SEE ALSO" -.BR date (1), -.BR utime (1). -.SH BUGS -Reported to not work on some AT's. -.PP -May mess up the clock royally when setting it -.RB ( \-w ). -Only if you have a very standard AT and you are not afraid of having your -CMOS setup reset to the default with a "checksum error" should you use -.BR readclock -to set the time of the CMOS clock. You have been warned. -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) Index: trunk/minix/man/man8/reboot.8 =================================================================== --- trunk/minix/man/man8/reboot.8 (revision 9) +++ (revision ) @@ -1,49 +1,0 @@ -.TH REBOOT 8 -.SH NAME -reboot \- reboot the system immediately -.SH SYNOPSIS -\fBreboot\fP [\fB\-f\fP] -.SH DESCRIPTION -.B Reboot -can be used to reboot the system after installing a new kernel. It does -not inform the users, but does log it's actions in -.B /usr/adm/wtmp -and -.BR /usr/adm/log . -The system is then rebooted with the -.BR reboot (2) -systemcall. -.PP -If the -.B \-f -flag is not given then all processes are sent terminate -signals to give them a chance to die peacefully before the -.B reboot() -call. -.PP -If the wtmp file exists, -.B reboot -logs itself as if it were a shutdown. This is done to prevent -.BR last (1) -from talking about system-crashes. -.B Reboot -is registered as is in the log file. -.PP -.B Reboot -can only be executed by the super-user. Any other caller will be -refused, either by -.BR reboot (8) -or by -.BR reboot (2). -.SH "SEE ALSO" -.BR reboot (2), -.BR shutdown (8), -.BR halt(8), -.BR boot (8). -.SH BUGS -The error message's given by -.B reboot -are not always useful. There are several routines that can fail, but which -are not fatal for the program. -.SH AUTHOR -Edvard Tuinder (v892231@si.hhs.NL) Index: trunk/minix/man/man8/repartition.8 =================================================================== --- trunk/minix/man/man8/repartition.8 (revision 9) +++ (revision ) @@ -1,41 +1,0 @@ -.TH REPARTITION 8 -.SH NAME -repartition \- load a partition table -.SH SYNOPSIS -\fBrepartition\fP \fIdevice\fP [\fIpartition-file\fP] -.SH DESCRIPTION -.B Repartition -uploads a new partition table for the partitions of -.IR device . -The table is obtained from the first sector of -.I partition-file -if given, -.I device -otherwise. -.I Device -may refer to the whole drive or a primary partition, depending on whether you -want to upload a partition or a subpartition table. The partitions will be -truncated to fit within the enclosing device like the disk driver does, -unless the numbers are coming from -.IR partition-file . -.SH EXAMPLES -repartition /dev/hd0 -.br -repartition /dev/hd4 /etc/hd4.table -.PP -Reload the partition table of drive 0 setting /dev/hd[1\-4], and the -subpartition table of /dev/hd4 setting /dev/hd4[a\-d] using a file. -The latter may be useful if you need more than the 4 subpartitions a -single MINIX 3 partition gives you. -.SH DIAGNOSTICS -The new table is printed on standard output. -.SH FILES -/dev/hd[0-9] -.SH "SEE ALSO" -.BR hd (4), -.BR part (8). -.SH BUGS -The disk must be in use for the changes to stick. The partition table of -an idle disk will be reloaded on the first open. -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) Index: trunk/minix/man/man8/rlogind.8 =================================================================== --- trunk/minix/man/man8/rlogind.8 (revision 9) +++ (revision ) @@ -1,103 +1,0 @@ -.\" Copyright (c) 1983 Regents of the University of California. -.\" All rights reserved. The Berkeley software License Agreement -.\" specifies the terms and conditions for redistribution. -.\" -.\" @(#)rlogind.8c 6.3 (Berkeley) 5/24/86 -.\" -.TH RLOGIND 8 "May 24, 1986" -.UC 5 -.SH NAME -rlogind, in.rlogind \- remote login server -.SH SYNOPSIS -.B "login stream tcp nowait root /usr/sbin/in.rlogind in.rlogind" -.br -.B "tcpd login /usr/sbin/in.rlogind" -.SH DESCRIPTION -.B Rlogind -is the server for the -.BR rlogin (1) -program. The server provides a remote login facility -with authentication based on privileged port numbers from trusted hosts. -.PP -.B Rlogind -listens for service requests at the port indicated in -the ``login'' service specification; see -.BR services (5). -When a service request is received the following protocol -is initiated: -.IP 1) -The server checks the client's source port. -If the port is not in the range 0-1023, the server -aborts the connection. -.IP 2) -The server checks the client's source address -and requests the corresponding host name (see -.BR gethostbyaddr (3), -.BR hosts (5) -and -.BR named (8)). -If the hostname cannot be determined, -the dot-notation representation of the host address is used. -.PP -Once the source port and address have been checked, -.B rlogind -allocates a pseudo terminal (see -.BR tty (4)), -and manipulates file descriptors so that the slave -half of the pseudo terminal becomes the -.B stdin , -.B stdout , -and -.B stderr -for a login process. -The login process is an instance of the -.BR login (1) -program, invoked with the -.B \-r -option. The login process then proceeds with the authentication -process as described in -.BR rshd (8), -but if automatic authentication fails, it reprompts the user -to login as one finds on a standard terminal line. -.PP -The parent of the login process manipulates the master side of -the pseduo terminal, operating as an intermediary -between the login process and the client instance of the -.B rlogin -program. In normal operation, the packet protocol described -in -.BR tty (4) -is invoked to provide ^S/^Q type facilities and propagate -interrupt signals to the remote programs. The login process -propagates the client terminal's baud rate and terminal type, -as found in the environment variable, ``TERM''; see -.BR environ (7). -The screen or window size of the terminal is requested from the client, -and window size changes from the client are propagated to the pseudo terminal. -.SH "SEE ALSO" -.BR rlogin (1). -.SH DIAGNOSTICS -All diagnostic messages are returned on the connection -associated with the -.BR stderr , -after which any network connections are closed. -An error is indicated by a leading byte with a value of 1. -.PP -.B ``Try again.'' -.br -A -.B fork -by the server failed. -.PP -.B ``/bin/sh: ...'' -.br -The user's login shell could not be started. -.SH BUGS -The authentication procedure used here assumes the integrity -of each client machine and the connecting medium. This is -insecure, but is useful in an ``open'' environment. -.PP -A facility to allow all data exchanges to be encrypted should be -present. -.PP -A more extensible protocol should be used. Index: trunk/minix/man/man8/rshd.8 =================================================================== --- trunk/minix/man/man8/rshd.8 (revision 9) +++ (revision ) @@ -1,166 +1,0 @@ -.\" Copyright (c) 1983 Regents of the University of California. -.\" All rights reserved. The Berkeley software License Agreement -.\" specifies the terms and conditions for redistribution. -.\" -.\" @(#)rshd.8c 6.3 (Berkeley) 5/24/86 -.\" -.TH RSHD 8 "May 24, 1986" -.UC 5 -.SH NAME -rshd \- remote shell server -.SH SYNOPSIS -.B "shell stream tcp nowait root /usr/sbin/in.rshd in.rshd" -.br -.B "tcpd shell /usr/sbin/in.rshd" -.SH DESCRIPTION -.B Rshd -is the server for the -.BR rcmd (3) -routine and, consequently, for the -.BR rsh (1) -program. The server provides remote execution facilities -with authentication based on privileged port numbers from trusted hosts. -.PP -.B Rshd -listens for service requests at the port indicated in -the ``cmd'' service specification; see -.BR services (5). -When a service request is received the following protocol -is initiated: -.IP 1) -The server checks the client's source port. -If the port is not in the range 0-1023, the server -aborts the connection. -.IP 2) -The server reads characters from the socket up -to a null (`\e0') byte. The resultant string is -interpreted as an ASCII number, base 10. -.IP 3) -If the number received in step 1 is non-zero, -it is interpreted as the port number of a secondary -stream to be used for the -.BR stderr . -A second connection is then created to the specified -port on the client's machine. The source port of this -second connection is also in the range 0-1023. -.IP 4) -The server checks the client's source address -and requests the corresponding host name (see -.BR gethostbyaddr (3N), -.BR hosts (5) -and -.BR named (8)). -If the hostname cannot be determined, -the dot-notation representation of the host address is used. -.IP 5) -A null terminated user name of at most 16 characters -is retrieved on the initial socket. This user name -is interpreted as the user identity on the -.BR client 's -machine. -.IP 6) -A null terminated user name of at most 16 characters -is retrieved on the initial socket. This user name -is interpreted as a user identity to use on the -.BR server 's -machine. -.IP 7) -A null terminated command to be passed to a -shell is retrieved on the initial socket. The length of -the command is limited by the upper bound on the size of -the system's argument list. -.IP 8) -.B Rshd -then validates the user according to the following steps. -The local (server-end) user name is looked up in the password file -and a -.B chdir -is performed to the user's home directory. If either -the lookup or -.B chdir -fail, the connection is terminated. -If the user is not the super-user, (user id 0), the file -.B /etc/hosts.equiv -is consulted for a list of hosts considered ``equivalent''. -If the client's host name is present in this file, the -authentication is considered successful. If the lookup -fails, or the user is the super-user, then the file -.B .rhosts -in the home directory of the remote user is checked for -the machine name and identity of the user on the client's -machine. If this lookup fails, the connection is terminated. -.IP 9) -A null byte is returned on the initial socket -and the command line is passed to the normal login -shell of the user. The -shell inherits the network connections established -by -.IR rshd . -.SH DIAGNOSTICS -Except for the last one listed below, -all diagnostic messages -are returned on the initial socket, -after which any network connections are closed. -An error is indicated by a leading byte with a value of -1 (0 is returned in step 9 above upon successful completion -of all the steps prior to the execution of the login shell). -.PP -.B ``locuser too long'' -.br -The name of the user on the client's machine is -longer than 16 characters. -.PP -.B ``remuser too long'' -.br -The name of the user on the remote machine is -longer than 16 characters. -.PP -.B ``command too long '' -.br -The command line passed exceeds the size of the argument -list (as configured into the system). -.PP -.B ``Login incorrect.'' -.br -No password file entry for the user name existed. -.PP -.B ``No remote directory.'' -.br -The -.B chdir -command to the home directory failed. -.PP -.B ``Permission denied.'' -.br -The authentication procedure described above failed. -.PP -.B ``Can't make pipe.'' -.br -The pipe needed for the -.BR stderr , -wasn't created. -.PP -.B ``Try again.'' -.br -A -.B fork -by the server failed. -.PP -.B ``: ...'' -.br -The user's login shell could not be started. This message is returned -on the connection associated with the -.BR stderr , -and is not preceded by a flag byte. -.SH SEE ALSO -.BR rsh (1), -.BR rcmd (3). -.SH BUGS -The authentication procedure used here assumes the integrity -of each client machine and the connecting medium. This is -insecure, but is useful in an ``open'' environment. -.PP -A facility to allow all data exchanges to be encrypted should be -present. -.PP -A more extensible protocol should be used. Index: trunk/minix/man/man8/screendump.8 =================================================================== --- trunk/minix/man/man8/screendump.8 (revision 9) +++ (revision ) @@ -1,35 +1,0 @@ -.TH SCREENDUMP 8 -.SH NAME -screendump \- write current console screen to standard output -.SH SYNOPSIS -.B screendump -.SH DESCRIPTION -.B Screendump -prints the contents of the console screen to standard output. It does this -by reading the screen memory, skipping over attribute bytes, omitting -trailing blanks and inserting a newline character at the end of each line. -.SH NOTES -The most common use of -.BR screendump -is with output redirected to a file. This allows screen displays (including -output of F-keys) to be captured for inclusion in other documents. -.PP -This version is for IBM-PC architecture only. -.SH BUGS -A network user captures an image of the main console, not his or her own -screen. The output will usually not be what you expect if the display is in -hardware scrolling mode, since in that mode the order of the lines in screen -memory may not be the same as what appears on the screen. -If you expect to use -.BR screendump -to send notes to someone about problems that occur while using -.BR MINIX -you must remember to toggle to software scrolling before you make the dump. -It will also be necessary to use -.BR su , -because -.BR /dev/mem -is normally not world readable. -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) -.\" preliminary man file by Al Woodhull (awoodhull@hampshire.edu) 01.08.95 Index: trunk/minix/man/man8/serial-ip.8 =================================================================== --- trunk/minix/man/man8/serial-ip.8 (revision 9) +++ (revision ) @@ -1,232 +1,0 @@ -.TH SERIAL-IP 8 -.SH NAME -serial-ip \- Serial IP (SLIP or PPP) setup -.SH DESCRIPTION -.de SP -.if t .sp 0.4 -.if n .sp -.. -\-\-\-\-\-\-\- -.br -.B Note: -This text and the serial IP code is not finished. Code needs to be added to -.B nonamed -to allow it to be used both with and without a connection to the Internet, -and by now there is a PPP program for standard MINIX 3 "out there" that will -change everything that is said in this text. So much to do, so little -time... -.br -\-\-\-\-\-\-\- -.PP -This manual page describes the MINIX 3 network setup to use serial line IP. -The serial IP protocol used can either be the older SLIP by means of the -.BR slip (8) -program, or PPP (Point-to-Point Protocol), the newer and better serial IP -protocol implemented by the -.BR ppp (8) -program. Alas standard MINIX 3 only supports SLIP. -.PP -In the following text all descriptions and examples will name SLIP or the -.BR slip -program, but one may just as well read PPP or -.BR ppp . -Where necessary the differences will be noted. -.PP -A typical use of the -.B slip -program is like this: -.PP -.RS -.B "slip /dev/psip2 /dev/tty01" -.RE -.PP -The argument of the program, the -.B /dev/psip2 -device, is one of the so-called "Pseudo IP" devices that the MINIX 3 TCP/IP -driver -.BR inet (8) -offers to implement a virtual network on. On an ethernet IP packets are -received or transmitted by the ethernet card, but packets on a pseudo IP -network are channeled back to or received from a program running in user -space, such as -.BR slip . -Standard input and output are used by -.B slip -to exchange packets with another SLIP implementation. This is normally -through an RS-232 serial line like the second serial line -.B /dev/tty01 -as used in the example above. -.PP -If we look at the flow of data over normal ethernet then this is what a TCP -connection between two MINIX 3 machines, -.B telnet -for instance, looks like: -.PP -.in 0 -.ce 13 -[telnet] -| -/dev/tcp0 -| -inet -| -[ethernet] -| -inet -| -/dev/tcp0 -| -[in.telnetd] -.PP -One-half (!) of a SLIP connection would look like this: -.PP -.in 0 -.ce 12 -[telnet] -| -/dev/tcp2 -| -inet -| -/dev/psip2 -| -slip -| -[serial line] -\&... -.SS "Configuration for a SLIP network only" -It is important to know that as far as -.B inet -is concerned the pseudo IP network is just another network, nothing special. -So you have to convince -.B inet -that it has to send packets out over that network. One does this by -setting a default route that makes -.B inet -believe that there is a router somewhere on the pseudo-IP network. -.PP -Assume your machine has been given the IP address -.B 192.168.0.13 -by your service provider. Let's choose another address on that network, -.B 192.168.0.1 -for instance. (You can use the address of the SLIP gateway if you want -to make it look pretty, but it doesn't really matter, anything "out there" -is ok.) -To make MINIX 3 aware of the situation you have to configure the pseudo IP -network. For Minix-vmd you need to look for the -.B if-then-else-fi -code in -.B /usr/etc/rc -that tests if -.B /etc/rc.net -should be run. Copy the lines in the -.B else -clause that starts network daemons to -.B /etc/rc.net -and add the following lines to make it look like this: -.PP -.RS -.nf -# My SLIP interface address. -ifconfig -h 192.168.0.13 -n 255.255.255.0 -.SP -# Standard network daemons. -daemonize rarpd $named irdpd rip inetd -.SP -# Default route to the outside world. -add_route -g 192.168.0.1 -.fi -.RE -.PP -For standard MINIX 3 one has to edit -.B /etc/rc -instead at the point of the XXX comments. The -.B ifconfig -goes at the first XXX, the -.B add_route -at the second XXX. The result is conceptually the same as the example -above. The important thing is the order: Configuration, Daemons, Routes. -(First give addresses to the networks, let the daemons meditate over the -results and possibly configure more networks (rarpd), then add routes to -the configured networks.) -.PP -Just one thing left to do. The system uses the first ethernet network -.RB ( eth0 , -.BR ip0 , -.BR tcp0 , -and -.BR udp0 ) -as the default network. With the program -.BR netdefault (8) -you have to change the links to the default devices -.RB ( eth / psip , -.BR ip , -.BR tcp , -and -.BR udp ) -to point to the first pseudo IP network -.RB ( psip2 , -.BR ip2 , -.BR tcp2 , -and -.BR udp2 ): -.PP -.RS -.B "netdefault psip2" -.RE -.PP -In -.B /etc/hosts -list at least -.B localhost -and the name of your machine with its SLIP address. This way your machine -will boot and know its own name. Now you need to find a way to let your -system know the addresses of other machines. There are three ways: -.PP -.RS -List the names and addresses of any other machine you wish to talk -to in -.BR /etc/hosts . -Drawback: This will quickly become a pretty long list. -.SP -Create an -.B /etc/resolv.conf -that lists a nameserver at your ISP and -.B 127.0.0.1 -(localhost). Drawback: With the SLIP link down it takes 5 to 10 seconds for -a name lookup to time out on the remote name server before the local name -server is tried. -.SP -Install the above -.B /etc/resolv.conf -when -.B slip -is started, and remove it when -.B slip -exits. Drawback: Long running programs only read -.B /etc/resolv.conf -at startup, so they don't notice it changing. -.SP -Run a real Internet name daemon from the -.B named -package. Drawback: Nontrivial to set up. -.SS "Configuration for a SLIP - Ethernet router (simple case)" -XXX -.SS "Configuration for a SLIP - Ethernet router (complex case)" -XXX -.SH FILES -.TP \w'/dev/psip*'u+5n -.B /dev/psip* -Pseudo-IP devices for use by -.BR slip -and -.BR ppp . -.SH "SEE ALSO" -.BR boot (8), -.BR inet (8), -.BR netdefault (8), -.BR term (1), -.BR chat (1). -.SH BUGS -.SH AUTHOR -Kees J. Bot (kjb@cs.vu.nl) Index: trunk/minix/man/man8/service.8 =================================================================== --- trunk/minix/man/man8/service.8 (revision 9) +++ (revision ) @@ -1,61 +1,0 @@ -.TH SERVICE 8 -.SH NAME -service \- Start or stop an operating system server or device driver. -.SH SYNOPSIS -.PP -\fBservice up\fR \fI\fR [\fB-args\fR \fIargs\fR] -[\fB-dev\fR \fIspecial\fR] [\fB-period\fR \fIticks\fR] -.PP -\fBservice down\fR \fI\fR -.PP -\fBservice refresh\fR \fI\fR -.PP -\fBservice rescue\fR \fI\fR -.PP -\fBservice shutdown\fR -.br -.de FL -.TP -\\fB\\$1\\fR -\\$2 -.. -.de EX -.TP -\\fB\\$1\\fR -\\$2 -.. -.SH DESCRIPTION -.PP -Tells the reincarnation server to start or stop a system service, such as a -server or device driver. The device driver will be automatically restarted when -it unexpectedly exits, e.g., if it is killed because of a bad pointer. -Starting requires an absoluate path to the binary to be executed. -.PP -When an optional period is specified, the reincarnation server sends a status -request to the system service after every period. If there the response does -not arrive in time, the reincarnation server will kill the misbehaving process -and restart a new one. The period must be specified in ticks, but can be -appended with 'HZ' to make it seconds. -.PP -Stopping a system service requires the process id of a running system service. -Issuing a kill command from the shell will not work, since the reincarnation -server interprets this as an unexpected exit and will automatically restart -a fresh copy of the process. The clean way to restart a process is using the -'refresh' option of the service utility. -.PP -The rescue call can be used to set the current working directory of the reincarnation server. By using a trusted rescue driver to shadow certain binaries in RAM the reincarnation server can check that rescue directory for binaries if the normal execution of the absolute path fails. This allows recovery from failures of the root file system driver. -.PP -If the system is to be shutdown, the reincarnation server should know about this event to prevent it from restarting services that are killed during the shutdown -sequence. -.SH EXAMPLES -.EX "service up /sbin/is -period 5HZ" "Start the IS server and check its status every 5 seconds." -.br -.EX "service up /usr/sbin/dp8390 -args DPETH0=pci" "Start the DP8390 ethernet driver, passing one argument." -.br -.EX "service down 117" "Stop the system service with process id 117." -.br -.SH "SEE ALSO" -.PP -.BR boot (8), -.BR monitor (8) - Index: trunk/minix/man/man8/setup.8 =================================================================== --- trunk/minix/man/man8/setup.8 (revision 9) +++ (revision ) @@ -1,399 +1,0 @@ -.TH SETUP 8 -.SH NAME -setup \- Install MINIX 3 on a hard disk -.SH SYNOPSIS -setup -.SH DESCRIPTION -.tr ~ -.nr a 0 +1 -.de CB -.sp 0.5v -\s-1\\f5\\c -.. -.de CE -\\fR\\s0\\c -.sp 0.5v -.. -.de IT -.ti -0.25i -.PP -.. -.PP -This appendix explains how to install MINIX 3. -Standard MINIX 3 requires a Pentium (or compatible) with at least -16-MB of RAM, at least 200-MB of free disk space, an IDE CD-ROM and an -IDE hard disk. Serial ATA, USB, and SCSI disks are not supported at present. -For USB CD-ROMS, see the Website: \fIwww.minix3.org\fR. - -\fBPREPARATION\fR -.PP -If you already have the CD-ROM (e.g., from the book), you can skip steps 1 and -2, but it is wise to check \fIwww.minix3.org\fR to see if a newer version -is available. -If you want to run MINIX 3 on a simulator instead of native, see Part V first. -If you do not have an IDE CD-ROM, -either get the special USB CD-ROM boot image or use a simulator. - -.IT "Download the MINIX 3 CD-ROM image" -Download the MINIX 3 CD-ROM image from the MINIX 3 Website -at \fIwww.minix3.org\fR. - -.IT "Create a bootable MINIX 3 CD-ROM" -Decompress the downloaded file. -You will get a CD-ROM image file with extension \fI.iso\fR and this manual. -The \fI.iso\fR file is a bit-for-bit CD-ROM image. -Burn it to a CD-ROM to make a bootable CD-ROM. -.PP -If you are using \fIEasy CD Creator 5\fR, select \*(OQRecord CD from CD image\*(CQ from the File -menu and change the file type from \fI.cif\fR to \fI.iso\fR in the dialog box that -appears. Select the image file and click \*(OQOpen.\*(CQ Then click \*(OQStart Recording.\*(CQ -.PP -If you are using \fINero Express 5\fR, choose \*(OQDisc Image or Saved Project\*(CQ and -change the type to \*(OQImage Files,\*(CQ select the image file and click \*(OQOpen.\*(CQ -Select your CD recorder and click on \*(OQNext.\*(CQ -.PP -If you are running Windows and do not have a CD-ROM burning program, take a look at -.br -\fIalexfeinman.brinkster.net/isorecorder.htm\fR -.br -for a free one and use it to create -a CD image. - -.IT "Determine which Ethernet Chip you have" -.PP -MINIX 3 supports several Ethernet chips for networking over LAN, ADSL, and -cable. These include Intel Pro/100, RealTek 8029 and 8139, AMD LANCE, -and several 3Com chips. -During setup -you will be asked which Ethernet chip you have, if any. Determine that now by -looking at your documentation. Alternatively, if you are using Windows, go to -the device manager as follows: -.sp 1 -.ta 0.9i -Windows 2000: -.br -Start> Settings> Control Panel> System> Hardware> Device Mgr -.sp 1 -Windows XP: -.br -Start> Control Panel> System> Hardware> Device Mgr\s0 -.ll -1i -.sp 1 -System requires double clicking; the rest are single. Expand the + next to -\*(OQNetwork adapters\*(CQ to see what you have. Write it down. If you do not have -a supported chip, you can still run MINIX 3, but without Ethernet. - -.IT "Partition your hard disk" -.PP -You can boot the computer from your CD-ROM if -you like and MINIX 3 will start, but to do anything useful, you have to create a -partition for it on your hard disk. -But before partitioning, be sure to \fBback up your data to an external med\%ium -like CD-ROM or DVD\fR as a safety precaution, just in case something goes wrong. -Your files are valuable; protect them. -.PP -Unless you are sure you are an expert on disk partitioning with much experience, it is strongly suggested that you -read the online tutorial on disk partitioning -at \fIwww.minix3.org/doc/partitions.html.\fR -If you already know how to manage partitions, create a contiguous chunk of free -disk space of at least 200 MB (even better: 400 MB or more). -If you do not know how to manage partitions but have a partitioning program -like \fIPartition Magic\fR, use it to create a region of free disk space of at -least 200 MB. Also make sure there is at least one primary partition (i.e., -Master Boot Record slot) free. -The MINIX 3 setup script will guide you through creating a MINIX partition in the -free space, which can be on either the first or second IDE disk. -.PP -If you are running Windows 95, 98, ME, or 2000 \fIand\fR your disk consists of a single -FAT partition, you can use the \fIpresz134.exe\fR program on the CD-ROM -(also available at \fIzeleps.com\fR) to reduce its size to leave room for MINIX. -In all other cases, please read the online tutorial cited above. -.PP -\fBWARNING: If you make a mistake during disk partitioning, you can lose all the data -on the disk, so be sure to back it up to CD-ROM or DVD before starting. -Disk partitioning requires great care, so proceed with caution.\fR - -\fBBOOTING\fR -.nr a 0 -.PP -By now you should have allocated at least 200 MB of free space on your disk. -If you have not done so yet, please do it now unless there is an existing -200-MB (or larger) partition you are willing to convert to MINIX 3. - -.IT "Boot from the CD-ROM" -Insert the CD-ROM into your CD-ROM drive and boot the computer from it. -If you have 16 MB of RAM or more, choose \*(OQRegular;\*(CQ -if you have only 8 MB choose \*(OQsmall.\*(CQ -If the computer boots from the hard disk instead of the CD-ROM, boot again and enter the -BIOS setup program to change the order of boot devices, putting the CD-ROM before -the hard disk. - -.IT "Login as root" -When the \fIlogin\fR prompt appears, login as \fIroot.\fR -After a successful login as root, you will see the shell prompt (#). -At this point you are running fully-operational MINIX 3. If you type: -.PP - ls /usr/bin | more -.PP -you can see what software is available. -Hit space to scroll the list. -To see what program \fIfoo\fR does, type: -.PP - man foo -.PP -The manual pages are also available at -.br -\fIwww.minix3.org/manpages\fR. - -.IT "Start the setup script" -To start the installation of MINIX 3 on the hard disk, type -.PP - setup -.PP -After this and all other commands, be sure to type ENTER (RETURN). -When the installation script ends a screen with a colon, hit ENTER to -continue. If the screen suddenly goes blank, press CTRL-F3 to select -software scrolling (should only be needed on very old computers). -Note that CTRL-key means depress the CTRL key and while holding it down, -press \*(OQkey.\*(CQ - -\fBINSTALLING TO THE HARD DISK\fR -.nr a 0 -.PP -These steps correspond to the steps on the screen. - -.IT "Select keyboard type" -When you are asked to select your national keyboard, do so. -This and other steps have a default choice, in square brackets. -If you agree with it, just hit ENTER. In most steps, the default is generally -a good choice for beginners. -The us-swap keyboard interchanges the CAPS LOCK and CTRL keys, as is conventional -on UNIX systems. - -.IT "Select your Ethernet chip" -You will now be asked which of the available Ethernet driver you want -in\%stalled (or none). Please choose one of the options. - -.IT "Basic minimal or full install?" -If you are tight on disk space, select M for a minimal installation -which includes all the binaries but only the system sources installed. -200 MB is enough for a bare-bones system. If you have 400 MB or more, -choose F for a full installation. - -.IT "Create or select a partition for MINIX 3" -You will first be asked if you are an expert in MINIX 3 disk partitioning. -If so, you will be placed in the \fIpart\fR program to give you full power to -edit the Master Boot Record (and enough rope to hang yourself). -If you are not an expert, press ENTER for the default action, which is an -automated step-by-step guide to formatting a disk partition for MINIX 3. - -\fBSubstep 4.1: Select a disk to install MINIX 3\fR -.PP -An IDE controller may have up to four disks. The \fIsetup\fR script will now -look for each one. Just ignore an error messages. -When the drives are listed, select one. and confirm your choice. -If you have two hard disks and you decide to install MINIX 3 to the second one and have -trouble booting from it, please see \fIwww.minix3.org/doc/using2disks.html\fR -for the solution. - -\fBSubstep 4.2: Select a disk region\fR -.PP -Now choose a region to install MINIX 3 into. You have three choices: -.sp 0.5v - (1) Select a free region - (2) Select a partition to overwrite - (3) Delete an existing partition to free up space and merge with adjacent free -space -.sp 0.5v -For choices (1) and (2), type the region number. For (3) type -.sp -0.25v -.PP - delete -.PP -.sp -0.25v -then give the region number when asked. -This region will be overwritten and its previous contents lost forever. - -\fBSubstep 4.3: Confirm your choices\fR -.PP -You have now reached the point of no return. You will be asked if you want to -continue. \fBIf you do, the data in the selected region will be lost forever.\fR -If you are sure, type: -.PP - yes -.PP -and then ENTER. To exit the setup script without changing the -partition table, hit CTRL-C. - -.IT "Reinstallation choice" -If you chose an existing MINIX 3 partition, in this step you will be -offered a choice between a Full install, which erases everything in the -partition, and a Reinstall, which does not affect your existing \fI/home\fR -partition. This design means that you can put your personal files on -\fI/home\fR and reinstall a newer version of MINIX 3 when it is available -without losing your personal files. - -.IT "Select the size of /home" -The selected partition will be divided into three subpartitions: root, \fI/usr\fR, -and \fI/home\fR. The latter is for your own personal files. Specify how much of the -partition should be set aside for your files. -You will be asked to confirm your choice. - -.IT "Select a block size" -Disk block sizes of 1-KB, 2-KB, 4-KB, and 8-KB are supported, but -to use a size larger than 4-KB you have to change a constant and recompile -the system. If your memory is 16 MB or more, use the default (4 KB); -otherwise, use 1 KB. - -.IT "Wait for bad block detection" -The setup script will now scan each partition for bad disk blocks. This will take -several minutes, possibly 10 minutes or more on a large partition. -Please be patient. -If you are absolutely certain there are no bad blocks, you can kill each scan -by hitting CTRL-C. - -.IT "Wait for files to be copied" -When the scan finishes, files will be automatically copied from the CD-ROM to -the hard disk. Every file will be announced as it is copied. -When the copying is complete, MINIX 3 is installed. -Shut the system down by typing -.PP - shutdown -.PP -Always stop MINIX 3 this way to avoid data loss as MINIX 3 keeps some files on -the RAM disk and only copies them back to the hard disk at shutdown time. - - -\fBTESTING\fR -.nr a 0 -.PP -This section tells you how to test your installation, rebuild the system after -modifying it, and boot it later. To start, boot your new MINIX 3 system. -For example, if you used controller 0, disk 0, partition 3, type -.PP - boot c0d0p3 -.PP -and log in as root. Under very rare conditions the drive number seen by the -BIOS (and used by the boot monitor) may not agree with the one used by -MINIX 3, in which case try other drive numbers. -This is a good time to create a root password. See \fIman passwd\fR for help. - -.IT "Compile the test suite" -To test MINIX 3, at the command prompt (#) type -.PP - cd /usr/src/test -.br - make -.PP -and wait until it completes all 40 compilations. -Log out by typing CTRL-D, - -.IT "Run the test suite" -To test the system, log in as bin (required) and type -.PP - cd /usr/src/test -.br - ./run -.PP -to run the test programs. They should all run correctly but they can take -20 min on a fast machine and over an hour on a slow one. -\fINote\fR: It is necessary to compile the test suite when running as root -but execute it as bin in order to see if the setuid bit works correctly. - -.IT "Rebuild the entire operating system" -If all the tests work correctly, you can now rebuild the system. -Doing so is not necessary since it comes prebuilt, but -if you plan to modify the system, you will need to know how to rebuild it. -Besides, rebuilding the system is a good test to see if it works. Type: -.PP - cd /usr/src/tools -.br - make -.PP -to see the various options available. Now make a new bootable image by typing -.PP - su - make clean - time make image -.PP -You just rebuilt the operating system, including all the kernel and user-mode -parts. That did not take very long, did it? -If you have a legacy floppy disk drive, you can make a -bootable floppy for use later by inserting a formatted floppy and typing -.PP - make fdboot -.PP -When you are asked to complete the path, type: -.PP - fd0 -.PP -This approach does not currently work with USB floppies since there is no MINIX 3 USB -floppy disk driver yet. -To update the boot image currently installed on the hard disk, type -.PP - make hdboot -.PP - -.IT "Shut down and reboot the new system" -To boot the new system, first shut down by typing: -.PP - shutdown -.PP -This command saves certain files and returns you to the MINIX 3 boot monitor. -To get a summary of what the boot monitor can do, while in it, type: -.PP - help -.PP -For more details, see \fIwww.minix3.org/manpages/man8/boot.8.html\fR. -You can now remove any CD-ROM or floppy disk and turn off the computer. - -.IT "Booting Tomorrow" -.PP -If you have a legacy floppy disk drive, the simplest way to boot MINIX 3 is by -inserting your new boot floppy and turning on the power. It takes only a few seconds. -Alternatively, boot from the MINIX 3 CD-ROM, login as bin and type: -.PP - shutdown -.PP -to get back to the MINIX 3 boot monitor. Now type: -.PP - boot c0d0p0 -.PP -to boot from the operating system image file on -controller 0, driver 0, partition 0. -Of course, if you put MINIX 3 on drive 0 partition 1, use: -.PP - boot c0d0p1 -.PP -and so on. -.PP -A third possibility for booting is to make the MINIX 3 partition the active one, -and use the MINIX 3 boot monitor to start MINIX 3 or any other operating system. -For details -see \fIwww.minix3.org/manpages/man8/boot.8.html\fR. -.PP -Finally, a fourth option is for you to install a multiboot loader such as -LILO or GRUB (\fIwww.gnu.org/software/grub\fR). -Then you can boot any of your operating systems easily. -Discussion of multiboot loaders is beyond the scope of this guide, but there -is some information of the subject at \fIwww.minix3.org/doc\fR. - -\fBUSING A SIMULATOR\fR -.nr a 0 -.PP -A completely different approach to running MINIX 3 is to run it -on top of another operating system instead of native on the bare -metal. Various virtual machines, simulators, and emulators are -available for this purpose. Some of the most popular ones are: - - \(bu VMware (www.vmware.com) -.br - \(bu Bochs (www.bochs.org) -.br - \(bu QEMU (www.qemu.org) -.sp 1v -See the documentation for each of them. Running a program on a -simulator is similar to running it on the actual machine, so you -should go back to Part I and acquire the latest CD-ROM and continue -from there. - Index: trunk/minix/man/man8/shutdown.8 =================================================================== --- trunk/minix/man/man8/shutdown.8 (revision 9) +++ (revision ) @@ -1,88 +1,0 @@ -.TH SHUTDOWN 8 -.SH NAME -shutdown \- graciously close the system down -.SH SYNOPSIS -.B shutdown -.RB [ \-hrRmk ] -.RB [ \-x -.IR code ] -.RI [ time-specification -.RI [ message ]] -.SH DESCRIPTION -.B Shutdown -is a program which allows a system operator to close down the system -in an nice way. -.B Shutdown -informs the users why and when the system is going down. This warning -is issued 10 minutes before shutdown time and every minute in the last -5 minutes. At this time (5 minutes), -.B shutdown -creates a file -.B /etc/nologin -to prevent new users from logging in. -.PP -.B Shutdown -keeps a logfile of shutdowns. Every shutdown is registered in -.BR /usr/adm/wtmp , -if this file exists, and by -.BR syslog (3) -(level -.BR auth . notice ). -After these actions, a call is done to -.BR reboot (2) -which actually brings the system down. -.PP -.I Time-specification -may be something like -.BR 15:00 , -.BR 15.00 , -.BR +15 , -or -.B now -for a shutdown at 3pm (twice), 15 minutes from now, or immediately. -.PP -The message may be used to describe why the system is going down, it may -also be typed on standard input with the -.B \-m -option. -.SH OPTIONS -.TP -.B \-h -This flag prevents the system from rebooting after the shutdown. The -system can now be powered off. This is the default. -.TP -.B \-r -This flag indicates that the system should reboot after shutting down. -.TP -.B \-R -Reboot the system by resetting it. Normally the kernel will try to return -to the Boot Monitor. With -.B \-R -the system will receive a hardware reset. -.TP -.BI \-x " code" -Halt the system and let the Monitor execute the given code as if typed at -the monitor prompt. You can for instance use -.B "\-x 'boot hd0'" -as a very fast way to reboot "from the top." -.TP -.B \-m -Allows the operator to type a shutdown message on standard input, that will -be added to the messages displayed on all terminals. -.TP -.B \-k -This option gives the possibility of terminating an already started -shutdown. This is only possible if shutdown time has not yet arrived. -.TP -.B \-C -Check if the system crashed. This option is not used at shutdown time, -but at reboot time. It tells if the file systems should be checked by -testing if the last entry in the wtmp file is a shutdown entry. (A -crude replacement for a file system clean flag.) -.SH "SEE ALSO" -.BR reboot (2), -.BR syslog (3), -.BR halt (8), -.BR boot (8). -.SH AUTHOR -Edvard Tuinder (v892231@si.hhs.NL) Index: trunk/minix/man/man8/slip.8 =================================================================== --- trunk/minix/man/man8/slip.8 (revision 9) +++ (revision ) @@ -1,82 +1,0 @@ -.TH SLIP 8 -.SH NAME -slip \- Serial Line IP -.SH SYNOPSIS -.B slip -.I pseudo-ip-device -.SH DESCRIPTION -.de SP -.if t .sp 0.4 -.if n .sp -.. -The -.B slip -program implements an Internet network connection over a bidirectional 8-bit -transport, usually a serial line. The protocol used for this connection is -the Serial Line Internet Protocol, SLIP for short. -.PP -The -.I pseudo-ip-device -argument names one of the -.B /dev/psip* -devices that is offered by the MINIX 3 TCP/IP driver -.BR inet (8). -The -.B slip -program reads IP packets from standard input and writes them to the pseudo -IP device, and reads packets from the pseudo IP device and writes them to -standard output. A typical use is like this: -.PP -.RS -.nf -.ft B -{ - stty raw 115200 - slip /dev/psip2 & -} /dev/tty01 -.ft P -.fi -.RE -.PP -The SLIP protocol is just a very simple packet framing protocol. It defines -two characters as markers on a byte stream to frame packets. SLIP does -not implement any higher level addressing, error detection, or compression. -Thanks to its simplicity it can be used under MINIX 3, any other system would -prefer to use the Point-to-Point protocol: PPP. -.PP -The SLIP packet framing protocol as defined in RFC-1055 is as follows: -.IP "\-" -Packets are delimited by an END character, octal 300. END is often send at -the start of a packet too to reset the logic of the receiver, so that random -noise isn't added to the beginning of a packet. -.IP "\-" -An ESC character (octal 333) is used to escape any END or ESC characters -that may occur in an IP packet. END and ESC are changed to ESC 334 and ESC -335 in the data stream. (Note that END doesn't occur within the data stream -at all by escaping it this way, making finding the framing END easier.) -.ig -.PP -The manual page -.BR serial-ip (8) -describes how to configure the MINIX 3 network devices to be used with a -serial IP connection. -.. -.SH FILES -.TP \w'/dev/psip*'u+5n -.B /dev/psip* -Pseudo-IP devices for use by -.BR slip . -.SH "SEE ALSO" -.ig -.BR ppp (8). -.br -.. -.BR RFC-1055 . -.SH NOTES -Under MINIX 3 -.B slip -forks in two to handle the two data streams in or out of the serial line. -Under Minix-vmd it uses asynchronous I/O to handle the two streams within -one program. -.SH AUTHOR -Kees J. Bot Index: trunk/minix/man/man8/srccrc.8 =================================================================== --- trunk/minix/man/man8/srccrc.8 (revision 9) +++ (revision ) @@ -1,33 +1,0 @@ -.TH SRCCRC 8 -.SH NAME -srccrc \- compute CRC checksums of the entire source tree -.SH SYNOPSIS -\fBsrccrc\fR -.br -.de FL -.TP -\\fB\\$1\\fR -\\$2 -.. -.de EX -.TP 20 -\\fB\\$1\\fR -# \\$2 -.. -.SH OPTIONS -.SH EXAMPLES -.SH DESCRIPTION -.PP -\fISrccrc\fP traverses the entire /usr/include and /usr/src tree to run -the crc command on all files found. The result is a long list of -filenames with their checksums. The filenames are relative to /usr. -.PP -The command makes an effort to remove most junk files such as .o, .bak -and files in bin directories. It cannot find single binaries however, so -you will have to run \fBmake clean\fP in /usr/src to be able to make a crc -list that contains only source files. -.PP -Two crc files can be compared easily with the \fIdiff\fP command. A crc -list of the original source tree can be found in /usr/src/crclist. -.SH "SEE ALSO" -.BR crc (1). Index: trunk/minix/man/man8/sync.8 =================================================================== --- trunk/minix/man/man8/sync.8 (revision 9) +++ (revision ) @@ -1,33 +1,0 @@ -.TH SYNC 8 -.SH NAME -sync \- flush the cache to disk -.SH SYNOPSIS -\fBsync\fR -.br -.de FL -.TP -\\fB\\$1\\fR -\\$2 -.. -.de EX -.TP 20 -\\fB\\$1\\fR -# \\$2 -.. -.SH EXAMPLES -.EX "sync" "Write out all modified cache blocks" -.SH DESCRIPTION -.PP -\s-1MINIX 3\s-1 -maintains a cache of recently used disk blocks. -The -.I sync -command writes any modified cache blocks back to the disk. -This is essential before stopping the system, and should be done before -running any -.I a.out -program that might crash. -.SH "SEE ALSO" -.BR sync (2), -.BR update (8), -.BR shutdown (8). Index: trunk/minix/man/man8/syslogd.8 =================================================================== --- trunk/minix/man/man8/syslogd.8 (revision 9) +++ (revision ) @@ -1,211 +1,0 @@ -.\" Copyright 1994 Dr. Greg Wettstein, Enjellic Systems Development. -.\" May be distributed under the GNU General Public License -.\" Sun Aug 30 11:35:55 MET: Martin Schulze: Updates -.\" -.\" from SYSKLOGD 8 "13 December 1995" "Version 1.3" "Linux System Administration" -.\" Modified for Minix porting by G. Falzoni -.\" $Id: syslogd.8,v 1.1 2006/04/03 14:59:51 beng Exp $ -.\" -.\" Local macros -.de Xr -.BR \\$1 (\\$2)\\$3 -.. -.de LB -.TP \\$1 -\\fB\\$2\\fR -\\$3 -.. -.de LI -.TP \\$1 -\\fI\\$2\\fR -\\$3 -.. -.de LR -.TP \\$1 -\\fR\\$2\\fR -\\$3 -.. -.\" end local macros -.TH SYSLOGD 8 "Jan. 23, 2000" -.SH NAME -.PP -syslogd \- system logging daemon. -.SH SYNOPSIS -.PP -.B syslogd -.RB [ " \-d " ] -.RB [ " \-f " -.I config file -] -.RB [ " \-m " -.I interval -] -.RB [ " \-p" -.IB port -] -.RB [ " \-v " ] -.LP -.SH DESCRIPTION -.PP -System logging is provided by a version of -.BR syslogd (8) -derived from the -stock BSD sources. -.B Syslogd -provides the kind of logging that many modern programs use. Every logged -message contains at least a time, a hostname field and a -program name field, but that depends on how trusty the logging -program is. -.PP -While the syslogd sources have been heavily modified a couple of notes -are necessary. First of all there has been a systematic attempt to -insure that syslogd follows the default, standard BSD behavior. -The second important concept to note is that this version of syslogd -interacts transparently with the version of syslog found in the -standard libraries, so you must insure that the correct versions are installed. -.PP -The main configuration file -.I /etc/syslog.conf -or an alternative file, given with the -.B "\-f" -option, is read at startup. Any line that begins with the hash mark -(``#'') and empty lines are ignored. If an error occurs during parsing -the whole line is ignored. -.SH OPTIONS -.PP -.LB 9 "-d" "Turns on debug mode. -When using debug mode, the daemon will not proceed to -.BR fork (2) -to set itself in the background, but will stay in the -foreground and write much debug information on the current tty. See the -DEBUGGING section for more information. -.LB 9 "\-f config file" "Specify an alternative configuration file instead of -.IR /etc/syslog.conf "," -which is the default. -.LB 9 "\-m interval" "The syslogd logs a mark timestamp regularly. The default -.I interval -between two -.I \-\- MARK \-\- -lines is 20 minutes. This can be changed with this option. -.LB 9 "\-p port" "You can specify an alternative port instead of -.I syslog/udp -default service. -.LB 9 "\-v" "Print version and exit. -.SH SIGNALS -.PP -.B Syslogd -reacts to a set of signals. You may easily send a signal to it -using the following: -.IP -kill -SIGNAL `cat /usr/run/syslogd.pid` -.LB 9 SIGHUP "This lets syslogd perform a re-initialization. -All open files are closed, the configuration file (default -is '/etc/syslog.conf') will be reread. -.LB 9 SIGTERM "The syslogd will die. -.LB 9 "SIGINT SIGQUIT" "If debugging is enabled these are ignored, otherwise -syslogd will die. -.LB 9 SIGALRM "Every time syslogd receives this signal it will log -the mark line. Normally this is done by -.Xr alarm 2 . -.SH CONFIGURATION FILE SYNTAX DIFFERENCES -.PP -.B Syslogd -uses a slightly different syntax for its configuration file than -the original BSD sources. Originally all messages of a specific priority -and above were forwarded to the log file. -.PP -For example see the following sample file -.IP -## Sample syslog.conf - -## Emergency messages (system may be unusable) -.br -*.emerg * -.br -*.alert /dev/log - -## High severity errors -.br -*.alert;*.crit /usr/adm/syslog - -## every other message (errors/warning and informational) -.br -*.info;*.notice;*.warning;*.err /usr/adm/messages -.br -*.debug /usr/adm/debug - -.SH SUPPORT FOR REMOTE LOGGING -.PP -Not implemented. -.SH OUTPUT TO NAMED PIPES (FIFOs) -.PP -Not implemented. -.SH INSTALLATION CONCERNS -.PP -There is probably one important consideration when installing this -version of syslogd. This version of syslogd is dependent on proper -formatting of messages by the syslog function. -.PP -.B Syslogd -should be started by the rc sequence. -.SH DEBUGGING -.PP -When debugging is turned on using -.B "\-d" -option and syslogd is compiled with debug=1 then syslogd -will be very verbose by writing much of what it does on stdout. -Whenever -the configuration file is reread and re-parsed you'll see a tabular, -corresponding to the internal data structure. This tabular consists of -four fields: -.TP -.I number -This field contains a serial number starting by zero. This number -represents the position in the internal data structure (i.e. the -array). If one number is left out then there might be an error in the -corresponding line in -.IR /etc/syslog.conf . -.TP -.I pattern -This field is tricky and represents the internal structure -exactly. Every column stands for a facility (refer to -.BR syslog (3)). -As you can see, there are still some facilities left free for former -use, only the left most are used. Every field in a column represents -the priorities (refer to -.BR syslog (3)). -.TP -.I action -This field describes the particular action that takes place whenever a -message is received that matches the pattern. Refer to the -.BR syslog.conf (5) -manpage for all possible actions. -.TP -.I arguments -This field shows additional arguments to the actions in the last -field. For file-logging this is the filename for the logfile; for -user-logging this is a list of users; for remote logging this is the -hostname of the machine to log to; for console-logging this is the -used console; for tty-logging this is the specified tty; wall has no -additional arguments. -.PP -Note that if syslogd is compiled with debug=0 only a subset is printed. -.SH FILES -.PP -.LR 28 /etc/syslog.conf "Configuration file for syslogd. See -.Xr syslog.conf 5 -for exact information. -.LR 28 /dev/log "The log device (console) for Minix. -.LR 28 /usr/run/syslogd.pid "The file containing the process id of syslogd. -.SH BUGS -.PP -If an error occurs in one line the whole rule is ignored. -.B Syslogd -doesn't change the filemode of opened logfiles at any stage of -process. If a file is created it is world readable. If you want to -avoid this, you have to create it and change permissions on your own. -.SH SEE ALSO -.BR syslog.conf (5), -.BR logger (1), -.BR syslog (3). -.\" .BR services (5), Index: trunk/minix/man/man8/update.8 =================================================================== --- trunk/minix/man/man8/update.8 (revision 9) +++ (revision ) @@ -1,29 +1,0 @@ -.TH UPDATE 8 -.SH NAME -update \- periodically write the buffer cache to disk -.SH SYNOPSIS -\fBupdate\fR -.br -.de FL -.TP -\\fB\\$1\\fR -\\$2 -.. -.de EX -.TP 20 -\\fB\\$1\\fR -# \\$2 -.. -.SH EXAMPLES -.EX "update &" "Start a process that flushes the cache" -.SH DESCRIPTION -.PP -When the system is booted, -.I update -is started up in the background from -.I /etc/rc -to issue a -\&SYNC -system call every 30 sec. -.SH "SEE ALSO" -.BR boot (8). Index: trunk/minix/man/man8/usage.8 =================================================================== --- trunk/minix/man/man8/usage.8 (revision 9) +++ (revision ) @@ -1,969 +1,0 @@ -.TH USAGE 8 -.SH NAME -usage \- installing and using MINIX -.SH DESCRIPTION -.de SP -.if t .sp 0.4 -.if n .sp -.. -.de XB \" An example in bold print. -.RS -.nf -.ft B -\&\\$1 -.ft R -.fi -.RE -.. -.de 3A \" Three Letter Acronym at 1 point size smaller. -\&\\$3\s-1\\$1\s+1\\$2 -.. -.de 3B \" TLA in bold. -\&\\$3\fB\s-1\\$1\s+1\fR\\$2 -.. -This manual page describes the installation and use of MINIX from a -System Administrators point of view. It contains an installation guide, -instructions on how to do the initial configuration and some other info. -Please read this document entirely before attempting to install MINIX. -The installation steps are in the proper order, but not all the -information you may need is presented at the right moment. -Other detailed information that may be useful can be found in -.BR boot (8), -.BR hier (7), -and in -.BR dosminix (8) -if you run MINIX under DOS. -.SS "1. MINIX UNDER DOS" -Installation of MINIX to run under DOS is a nonevent. Chances are, you are -reading this manual page from an already running MINIX system, but if not -then the setup goes like this: -.PP -Unpack the DOSMINIX.ZIP file using one of the popular ZIP utilities, such as -PKZIP or WinZIP. Next reboot Windows and hit F8 just when you see the -"Booting Windows" message. From the menu that appears choose "Command -prompt only", or if that doesn't work "Safe mode command prompt only". Under -Windows Me you can use a startup disk to boot the PC into DOS. Move -to the directory containing the MINIX files and type: -.PP -.XB "boot minix.mnx" -.PP -Type '=' and presto, you are running MINIX. Most of the rest of this manual, -which deals mainly with running MINIX in a true hard disk partition, does -not apply to you. Your system is already installed completely, with all -binaries and sources present, so all the talk about getting MINIX on your -disk can be skimmed over. Pay attention again when the focus shifts to the -configuration of the system. Section 9 is where this happens first. (The -main challange to a DOS installation is to figure out which parts of the -installation manual do not apply.) -.SS "2. REQUIREMENTS" -The minimum system MINIX can be installed on comfortably is an IBM PC/AT -or PS/2 with a 286 processor, 2 MB memory, a 720 kb diskette drive, and 35 -MB free space on an AT, -ESDI, or SCSI hard disk (the latter controlled by an Adaptec 1540.) MINIX -for the 386 (MINIX-386 for short) can be installed on a machine with at -least a 386sx processor, 3 MB memory and at least 35 MB of disk space. -.PP -The minimum system MINIX can be installed on -.BR un comfortably -is an IBM PC/XT with 640 kb memory. MINIX-386 can more or less run in 2 -MB memory. See sections 16 and 17 on "low memory" issues. -.SS "3. MINIX INSTALLATION BACKGROUND" -The objective of the installation is to create a partition on your disk -and to put MINIX into it. MINIX really requires at least two partitions -however, so the single "primary" partition is split into two or three -subpartitions. -The -.B s0 -subpartition will contain the root file system, the -.B s1 -subpartition may optionally contain swapspace, and the -.B s2 -subpartition will contain the -.B /usr -file system. What Windows calls -"drives", i.e C:, D:, E:, MINIX calls "file systems". MINIX does not use -drive letters, but requires that one file system is made a part of another -file system by "mounting" one on the other. The "root" file system is -always present and starts with the directory "/", the root of the directory -tree. The root file system contains a few programs in -.BR /bin , -device files in -.BR /dev , -and configuration files in -.BR /etc . -This is just enough to get the system started. MINIX will soon extend -its directory tree by mounting a file system on the -.B /usr -directory. What is henceforth known as the /usr file system contains all -MINIX programs in -.BR /usr/bin , -file system sources in -.BR /usr/src , -etc, etc. -The \s-2ROOT.MNX\s+2 image contains the complete MINIX root file system, but -\s-2USR\s+2 contains just a small subset of the /usr file system, with just -enough utilities to install MINIX. The complete /usr file system is -split up into the \s-2USR.TAZ\s+2, \s-2SYS.TAZ\s+2 and \s-2CMD.TAZ\s+2 -archives that are installed later to fill /usr. -.PP -Let's suppose your first hard disk, which has -device name -.BR /dev/c0d0 , -has Windows already present in the first primary partition -.RB ( /dev/c0d0p0 ), -and some free space left after that. After MINIX is installed in that -free space the disk will look like this: -.PP -.nf -.in +4n -.ta +\w'/dev/c0d0p1s0mmmm'u -/dev/c0d0 Whole hard disk #0 -/dev/c0d0p0 Windows C: drive -/dev/c0d0p1 MINIX primary partition -/dev/c0d0p1s0 MINIX root partition -/dev/c0d0p1s1 MINIX swap partition (optional) -/dev/c0d0p1s2 MINIX /usr partition -.in -8n -.fi -.PP -/dev/c0d0 is the sum of a partition table, /dev/c0d0p0 and /dev/c0d0p1. -Likewise is /dev/c0d0p1 the sum of a subpartition table, /dev/c0d0p1s0 and -/dev/c0d0p1s2. Read the "DEVICES" sections for more information on MINIX -devices. -.SS "4. INSTALLATION" -.ig \" Only relevant when on CD-ROM. -If you have not already copied MINIX to floppy disks, please read -the README.TXT file in the MINIX directory now, for it tells how to do this. -You should also print out EXAMPLE.TXT and read it in parallel with this -document. This one tells you what to do; that one shows you what the -screen is supposed to look like at each step, so you can see if everything -is OK. -.PP -.. -You can install MINIX automatically or manually as described in the sections -below. The end result is the same, but manual installation allows -one to deviate from the preconfigured choices. You may wish to read the -manual pages of the programs used below before you start. You may especially -want to read -.BR boot (8) -if your machine is different from what the majority buys, because you -may need to set a few boot parameters to configure drivers. To do this type -.B ESC -to get to the Boot Monitor prompt, set the appropriate variables, use -.B save -to store the settings and -.B menu -to continue where you left off. -.PP -To install the system you need two diskettes: a bootable root diskette and a -diskette full of binaries to use as -.BR /usr . -These diskettes are named -.B \s-2ROOT\s+2 -and -.BR \s-2USR\s+2 . -These two diskettes may also be combined on a single high density diskette. -In that case the \s-2USR\s+2 part is on the -.B p2 -partition. -.PP -Insert the \s-2ROOT\s+2 diskette, boot the machine and type '=' to the menu. -The MINIX kernel is loaded and takes control when you see the copyright -banner. After loading the root diskette into the RAM disk you will be asked -to finish the name of the device to mount on -.BR /usr . -Type -.BR fd0p2 -for a diskette that contains both \s-2ROOT\s+2 and \s-2USR\s+2, otherwise -replace \s-2ROOT\s+2 by \s-2USR\s+2 and type -.BR fd0 . -Login as -.BR root . -.SS "5. AUTOMATIC INSTALLATION" -Before starting the installation, you must either have a free partition -available or have at least 35 MB not in any partition so you can create -a MINIX partition. -.PP -Type -.B setup -to start the installation script. First it offers to install a national -keyboard map. The names should be clear, except for -.BR us-swap , -which swaps the CTRL and CAPS LOCK keys of a standard US style keyboard -for people who believe that the natural place of CTRL is next to A. -The default suggested between [ and ] is the US standard keyboard. -.PP -The next thing to do is to make a partition, for this you are placed in a -partition table editor named -.BR part . -This partition table editor is very easy to use (in the author's opinion), -but you will probably hate it. You can move all over the place with the -arrow keys, change values, and make a mess of your partition table real quick. -So if you get into trouble, type 'q' to quit, 'n' to not write the table, -and RETURN to start over. Use the '?' key to get help. -.PP -With the '+' and '\-' keys you can select the disk device to install on, -probably -.BR /dev/c0d0 , -the first hard disk. Type 'r' to load the partition table of the selected -disk. Either create one new partition by modifying a partition marked -"None", or reuse an existing partition by changing its type to "MINIX" (hex -code 81). DO NOT use part to shrink an existing partition! It will destroy -all data in that partition. MINIX needs a partition of at least 20 MB, but -not larger than 128 MB (MINIX-86) or 1 GB (MINIX-386). The system needs 35 -MB in compiled state. -.PP -The script then wants to know the name of the partition you've created. The -partition name is probably still visible on the screen. Combined with the -drive name you have to type c0d0p1, c0d2p0 or something. -.PP -The next question is the amount of swapspace you want to give MINIX. There -will be a suggested value based on the amount of memory your system has. -If you have more then enough memory then don't bother with swap. MINIX -doesn't handle it very well yet, or ever, only memory starved systems need it -so that -.B "make world" -can run. -.PP -The new partition table is reloaded into the disk driver, and the -new MINIX partition is carved up into two or three subpartitions, a 1440 kb -root, maybe some amount of swap, and the rest for /usr. -.PP -After making /usr, it is immediately put to use to replace the installation -/usr file system so that you can remove the \s-2USR\s+2 diskette and insert -the \s-2ROOT\s+2 diskette (unless they are one and the same). The root file -system is filled with the contents of the \s-2ROOT\s+2 diskette and slightly -patched up to work on the hard disk (/etc/fstab.) -.PP -You can now skip the next section and move to "TESTING", but it may be -instructive to read it anyway. -.SS "6. MANUAL INSTALLATION" -The instructions that follow are at a very low level and require you to be -very careful. The big advantage is that you know precisely what -tools have been used and how everything works. The disadvantage is that -you may easily make a mistake that either forces you to start over if you -are lucky, or wipes out the contents of your hard disk if you are not. -Only if you really want to do something different should you use a manual -installation. Slavishly following the steps shown below will only make -you end up with the same result as an automatic installation. -.PP -Run -.B part -to make partitions to load the system into. The best thing to do is to make -one large primary partition of type "MINIX" and to carve this partition up -into three subpartitions for root, swap and /usr. The assumption is that you -will use the second partition on the first hard disk, -.BR /dev/c0d0p1 , -and that -.B c0d0p1s0 -is the root subpartition, -.B c0d0p1s1 -is swap and -.B c0d0p1s2 -is /usr. If you want to use the first partition on -the second hard disk for instance, then substitute c0d1p0 and c0d1p0s[012] for -the above. See the section on devices below, and the manual -pages of -.BR part (8) -and -.BR controller (4). -Start -.B part -and select the disk that you -want to install MINIX onto. In our example it will be -.BR /dev/c0d0 . -.PP -Use -.B part -to make a single partition in the primary partition table of type "MINIX", -then hit '>' on this new partition to make a subpartition table. -.PP -For the root subpartition you are advised to use 1440 kb exactly. You can -make it larger if you want to, but it is advisable never to let the contents -outgrow a floppy. (The \s-2ROOT\s+2 diskette is a copy of a root file -system, and will be used to fill your root subpartition.) -.PP -The second subpartition is for swapspace. You can use it to enlarge the -amount of total memory (real + swap) if your system has less than 2M -(16-bit mode) or 4M (32-bit mode). Note that only one MINIX swap partition -is needed on your system, so if you have another MINIX partition then you can -use its swap partition instead. -.PP -Use the rest of the partition for -.BR s2 , -the /usr subpartition. -.PP -When you are done check that /dev/c0d0p1s0 is active (the * after the partition -number) so you can boot from it later. -.PP -If your disk has bad blocks then don't put the root or swap subpartition -on top of them. Make sure the inode tables in the other partitions don't -have bad blocks either. You can put the subpartitions out of order on the -disk if that helps. Subpartition tables, unlike the main partition -table, are not sorted by the driver. -.PP -After making the partitions you do not have to reboot. The disk driver -reloads the partition tables on the next access if the disk is not in use. -(Open or mounted.) -.PP -To be able to boot from /dev/c0d0p1s0 you must place a master bootstrap in -/dev/c0d0p1. It has been placed there by -.B part -if it told you that it was creating a new partition table, but -.PP -.XB "installboot\0\-m\0/dev/c0d0p1\0/usr/mdec/masterboot" -.RE -.PP -will put it there for sure. -.PP -Let's start by initializing the swap partition first, if you allocated one. -We may need it already, so mount it. -.PP -.XB "mkswap\0/dev/c0d0p1s1" -.XB "mount\0\-s\0/dev/c0d0p1s1" -.PP -Next make a file system for on-disk /usr and copy the floppy /usr on to it. -.PP -.XB "mkfs\0/dev/c0d0p1s2" -.XB "readall\0\-b\0/dev/c0d0p1s2 | sh" -.XB "mount\0/dev/c0d0p1s2\0/mnt" -.XB "cpdir\0\-v\0/usr\0/mnt" -.PP -This will create a file system on /dev/c0d0p1s2, mount it on /mnt, and copy the -contents of the \s-2USR\s+2 floppy onto it. The call to -.B readall -marks bad blocks on the file system as unusable, you can omit this on a -drive known to be spotless (\s-2IDE\s+2 or \s-2SCSI\s+2.) -.PP -You can now use the new /usr in place of the \s-2USR\s+2 floppy: -.PP -.XB "umount\0/dev/c0d0p1s2" -.XB "umount\0/dev/fd0\0\0\0\0\0\0\0\0\0# fd0p2 if combined" -.XB "mount\0/dev/c0d0p1s2\0/usr" -.PP -This little dance has freed up your floppy drive, so please remove the -\s-2USR\s+2 diskette and replace it by the \s-2ROOT\s+2 diskette. Make a -file system for the root with at least 512 inodes (files), and -fill it from the floppy: -.PP -.XB "mkfs\0\-i\0512\0/dev/c0d0p1s0" -.XB "mount\0/dev/fd0\0/fd0" -.XB "mount\0/dev/c0d0p1s0\0/mnt" -.XB "cpdir\0\-v\0/fd0\0/mnt" -.XB "umount\0/dev/fd0" -.PP -Remove -.B /mnt/etc/issue -to get rid of the "use setup" message that greets you when you boot, and -edit the file -.B /mnt/etc/fstab -to name the devices MINIX has been installed on. In our example it -should look like this: -.PP -.XB "root=/dev/c0d0p1s0" -.XB "swap=/dev/c0d0p1s1" -.XB "usr=/dev/c0d0p1s2" -.PP -Unmount the new root: -.PP -.XB "umount\0/dev/c0d0p1s0" -.PP -Make it bootable: -.PP -.XB "installboot\0\-d\0/dev/c0d0p1s0\0/usr/mdec/bootblock\0boot" -.PP -The automatic script would now set the -.B rootdev -and -.B ramimagedev -boot variables. You can do this now using the -.B edparams -command, but it is easier to postpone it until the testing phase. The -settings should be: -.PP -.XB "rootdev=c0d0p1s0" -.XB "ramimagedev=c0d0p1s0" -.SS "7. TESTING" -By now a new MINIX system is present on your hard disk. Time to see if -it works. Leave the \s-2ROOT\s+2 diskette in the drive and type -.BR halt . -You are now going to use the power of the Boot Monitor on the diskette to -boot the MINIX partition on the hard disk. Use the monitor command -.B boot c0d0p1 -to boot the primary partition MINIX has been installed in. (It is "c0d0p1" in -our example.) -.PP -The hard disk bootstrap is now showing the menu again. You can type '=' -to start MINIX, but you probably want to change the boot parameters. -Hit -.B ESC -once more to get to the command prompt. The command -.B set -shows what the current parameters are. Here is an example that shows how -to make a menu to either start MINIX or boot Windows: -.PP -.XB "minix(=,Minix)\0boot" -.XB "win(w,Windows)\0boot\0c0d0p0" -.XB "save" -.PP -Windows is assumed to be in the first partition in the example above (c0d0p0). -When finished type -.B menu -to see if the menu looks right. If so hit '=' to start MINIX. Log in as -root. -.SS "8. ADDING PROGRAMS AND SOURCES TO /usr" -The -.B setup -command can also be used to add files from floppy sets to the system. The -.B \s-2USR.TAZ\s+2 -(programs and stuff), -.B \s-2SYS.TAZ\s+2 -(system sources), and -.B \s-2CMD.TAZ\s+2 -(commands sources) -are all installed relative to the -.B /usr -directory, so the command to use three times is -.PP -.XB setup\0/usr -.PP -.B Setup -will ask for the size of data on the floppies, which is by default simply -the entire floppy. You will see some "Cannot make directory" errors -while extracting, as some directories already exist. Ignore these messages. -You need the -.B \s-2USR.TAZ\s+2 -set if you want a working MINIX system, -.B \s-2SYS.TAZ\s+2 -if you want recompile the system or study it, and -.B \s-2CMD.TAZ\s+2 -if you also want the sources of the commands. On a disk space -starved machine you could opt to do without the commands sources, as they -are not absolutely necessary to understand MINIX. -.PP -If your machine does not have enough memory to run -.B setup\0/usr -then type these commands manually: -.PP -.XB "cd\0/usr" -.XB "vol\0/dev/fd0 | zcat | tar\0xvfp\0\-" -.PP -If -.3B USR.TAZ -is already present on the hard disk in an -.3A DOS -or Windows partition, then this command can be used under MINIX-386 to -extract it to avoid the floppy detour: -.PP -.XB "cd\0/usr" -.XB "mtools\0copy\0c0d0p0:USR.TAZ\0\- | setup\0/usr" -.PP -In 16-bit mode you don't have mtools, but maybe dosread will work: -.PP -.XB "cd\0/usr" -.XB "dosread\0c0d0p0\0USR.TAZ | setup\0/usr" -.PP -The file doesn't have to be in the root directory of -.BR c0d0p0 , -of course, -.B "c0d1p0:/TMP/USR.TAZ" -would name a file on the first partition of the second hard disk in the -directory -.BR \eTMP . -.PP -The /usr file system can also be filled through a network from a remote host -if MINIX if you can get networking going with the NET.TAZ supplement. Use -.B "setup\0/" -to install NET.TAZ (note that it goes into / instead of /usr), then -follow the instructions in -.BR boot (8) -to configure TCP/IP and boot MINIX. There are now two ways to fill -/usr. One is to add the host name and login name of a remote host and a -remote user to -.BR /.rhosts , -as root, and to use the following command on the remote host: -.PP -.XB "rsh\0\-l\0root\0\fIminix-box\fP\0setup\0/usr\0< USR.TAZ" -.PP -Two is to use -.B urlget -to copy the data directly from a Web or FTP site by using these -commands under MINIX: -.PP -.XB "cd\0/usr" -.XB "urlget\0\fIurl\fP.../USR.TAZ | setup\0/usr" -.PP -The sources may be installed using exactly the same commands, but with -.3B USR.TAZ -replaced by -.3B SRC.TAZ . -Note that this means that the sources must also be extracted relative to -.BR /usr . -.SS "9. NAMES" -A standalone machine will have to be given a name. As -.B root -type -.PP -.XB "echo\0\fIname\fB\0>/etc/hostname.file" -.PP -to change the host name of your machine to -.IR name . -.SS "10. ACTIVE ON BOOT" -You may want to make the MINIX partition active so that it is automatically -booted. With Windows -.B fdisk -or MINIX -.BR part , -mark the primary partition that contains MINIX active. Using the menu you -made earlier you can boot either MINIX or Windows at a keypress. You can even -set timeouts. To boot MINIX automatically after 5 seconds: -.PP -.XB "main()\0{trap\05000\0minix;\0menu}" -.PP -See -.BR monitor (8) -for all the details on the monitor. -.PP -If you don't trust this then you can rig up a diskette that boots the MINIX -partition when left in the drive: -.PP -.XB "installboot\0\-m\0/dev/fd0\0/usr/mdec/jumpboot\0010" -.PP -The numbers 010 indicate the device (disk or partition) that must be booted, -i.e. -.B /dev/c0d0p1s0 -in this example. Take the name of the device, and use the disk, partition -and subpartition numbers, or less. So c0d1p2s0 -> 120, c0d3 -> 3, -c0d2p0 -> 20.) -.SS "11. DEVICES" -A crash course on the MINIX devices in -.BR /dev : -The first two hard disks are named -.BR c0d0 -and -.BR c0d1 . -These devices address the entire hard disk, from the -first to the last byte. Each disk has four partitions, for disk 0 they are -.BR c0d0p0 , -.BR c0d0p1 , -.BR c0d0p2 , -and -.BR c0d0p3 . -And for disk 1 they are named -.BR c0d1p0 -to -.BR c0d1p3 . -These partitions may contain file systems, -.B c0d0p0 -often contains the -.3A MS-DOS -or Windows "C:" file system. MINIX can use these partitions -for file systems too, but you can also partition one of these "primary -partitions" into four so-called "subpartitions". The subpartitions of -.B c0d0p0 -are named -.BR c0d0p0s0 , -.BR c0d0p0s1 , -.BR c0d0p0s2 , -and -.BR c0d0p0s3 . -The other partitions may have four subpartitions that are named in the same -way. See -.BR controller (4) -for an elaborate description. -.PP -You may need to add devices to -.BR /dev , -because not all devices are present to keep down the clutter. -The command -.3B MAKEDEV -knows how to make devices, and -.3B DESCRIBE -can tell you what an unknown device may be, or even what all devices in -.B /dev -may be if called without arguments. Devices are described in -.BR dev (4), -with pointers to more specific pages. -.SS "12. EDITORS" -The editors available are -.B elvis -(a -.B vi -clone), -.B elle -(a simple -.B emacs -clone), -and the old MINIX -.B mined -editor. Of these editors only elvis can recover your file after a system -crash. Only -.B mined -is available at installation time. (All you need to know about mined right -now is that CTRL-X gets you out of it.) -.SS "13. BOOT MONITOR VS. MINIX" -The Boot Monitor uses the -.3A BIOS -to address disks, so it has no idea of controllers, it just lumps everything -together and ignores controller numbers. So what the monitor thinks are -.BR d0 , -.BR d1 , -and -.BR d2 , -may be -.BR c0d0 -(IDE primary master), -.BR c0d2 -(IDE secondary master), and -.BR c1d3 -(SCSI disk at target 3). -One must keep this in mind when MINIX is installed on a disk other than the -very first. So if MINIX is installed in the third partition of the SCSI disk, -then -.B "boot d2p2" -will boot it, and -.B "rootdev=c1d3p2s0" -will tell MINIX where its root file system is. -.SS "14. NATIONAL KEYBOARDS" -The directory -.B /usr/lib/keymaps -contains keymap tables for several national keyboards. If you have a German -keyboard for instance, then -.PP -.XB "loadkeys\0/usr/lib/keymaps/german.map" -.PP -will load the German key translation table into the keyboard driver. Copy -the map to -.B /etc/keymap -once MINIX is installed on the hard disk, because having to type a key -sequence like one of these: -.PP -.XB "loadkezs\0\-usr\-lib\-kezmaps\-german.map" -.XB "loqdkeys\0=usr=lib=key,qps=french.,qp" -.PP -on a reboot gets a bit annoying after a while. Send corrections and new -keymaps to the person named below. (Do not send a Dutch keymap, buy -yourself a real keyboard instead.) -.SH SUGGESTIONS -Below are a few useful suggestions. Some of the information can be of use -in other situations than described here. -.SS "15. VIRTUAL CONSOLES" -Hold down the ALT key and press the left or right arrow key, F1, or F2. -This switches the console between two login sessions. (Unless you have -an old mono adapter, because virtual consoles sit in video memory, and -a mono adapter only has memory for one.) -.PP -Note that kernel messages, including function key output, only appear on -the first console. This may be confusing, but it keeps the other consoles -clean. -.SS "16. LOW ON MEMORY" -The normal installation requires that you have enough memory for a large RAM -disk. You can still install MINIX normally if you either have a high density -diskette drive for a combined root+usr floppy, or you have two floppy drives -of at least 720 kb. Before booting you have to set the variable -.B rootdev -to the same value as -.BR ramimagedev . -This is slower then a RAM disk, but saves a lot of memory. -.PP -The automatic installation script knows how to handle this new situation. -If you install manually then you have to use -.PP -.XB "cpdir\0\-vx\0/\0/mnt" -.PP -to copy the root device to disk. When it is time to fill /usr and you only -have one floppy drive then hit DEL to get out of the installation script and -reboot as described in "TESTING". You can then finish the installation -manually. -.ig -See the XT640K.TXT file for more advice on small machines. -.. -.SS "17. LOW ON MEMORY AND ONLY ONE 720 KB FLOPPY DRIVE" -If you only have one 720 kb floppy drive and your system is low on memory -then you can use the \s-2TINYROOT.MNX\s+2 boot image. This image contains a -small kernel with only the BIOS disk driver, and a small root file system. -You can use this disk to boot your machine. Use the normal \s-2ROOT.MNX\s+2 to -install the root file system. Keep booting your machine with -\s-2TINYROOT\s+2 until you have compiled a small kernel for your system. -Use the -.B rootdev -boot variable to select the hard disk root file system. Do -.B not -use \s-2TINYROOT\s+2 for anything other than booting, always use -\s-2ROOT\s+2 when mentioned. -.SS "18. FLOPPY DRIVE 1 IS A HIGH DENSITY DRIVE" -If you would like to install from floppy drive 1 then you need to copy at -least one sector from the \s-2USR\s+2 image onto a diskette for drive 0. -The \s-2USR\s+2 bootstrap has been rigged to boot the other drive. -.SS "19. INSTALLING ON A SECOND HARD DISK" -MINIX doesn't care if it is installed on the second disk of a system with -two disks. The only problem is to get it booted. You can either rig up -a diskette to boot MINIX as shown earlier, or you can use the same trick -on the first disk. The command -.PP -.XB "installboot\0\-m\0/dev/c0d0\0/usr/mdec/jumpboot\01" -.PP -will lock the first disk into booting the second disk. Note that this -command modifies the disk outside a MINIX partition, overwriting a bit of -code that has likely been put there by Windows fdisk. First verify that the -Boot Monitor can boot a Windows partition, because then the MINIX master -bootstrap can do it too. -.SS "20. LOTS OF MEMORY ON A 286" -You will have a hard time making MINIX use up 3 MB memory. Memory you -can spare can be used for a "second level block cache" on the RAM disk. The -File System uses the second level cache to store copies of disk blocks that -are pushed out of the normal (primary) block cache. The size of the primary -cache is compiled into the FS server, but the size of the second level cache -can be set with the -.B ramsize -boot variable. Set it to a number between 0 and 512. 512 kilobytes is -enough to keep most of the compiler cached. -.SS "21. LOTS OF MEMORY ON A 386+" -Processes can be as big as you would like on a 386, but in practice 4 MB is -a lot, and 8 MB is infinite. -The installation script sets up a second level cache for MINIX-386 -of up to 1024 kilobytes. This is because the default file system cache -is only 80 kb. Your first point of call is to get rid of the poorly -performing second level cache by setting -.B ENABLE_CACHE2 -to 0 and to assign the memory used by it to the -normal block cache by enlarging the appropriate -.B NR_BUFS -and -.B NR_BUF_HASH -constants in with as much as you can spare. (1024 for -NR_BUFS is the minimum to keep -.B "cc \-c" -cached. 2048 is then a nice value for NR_BUF_HASH.) -Disable the second level cache, compile a new kernel, reboot and set -.B ramsize -to 0. -.SS "22. LOTS OF DISK SPACE" -The maximum file system size is 1 GB for MINIX-386 and 128 MB for -MINIX-86. (MINIX-86 can handle larger file systems, but -.B fsck -can't check them.) Note that a MINIX file system can only contain 65535 -inodes (files), so the average file should be 16 kb to completely fill it. -It may be better to make two smaller file systems. Besides, fsck takes -forever on a large file system. -.SH SYSTEM ADMINISTRATION -The system has been set up with the idea that working as root is a bad thing -to do. As root you are in no way protected from doing stupid things. So -don't do development as root, but work as -.BR bin ! -Only in exceptional cases do you want to become root. Being root is fun for -wannabe hackers; administrators know better. -.PP -To make life easier for bin, some programs like -.BR su (1), -.BR install (1) -and -.BR shutdown (8) -treat bin and other members of the operator group as special and allow them -the privileges of root. (One is an operator if one's -group id is zero.) Operators should share the shadow password of root by -having -.B ##root -in their password field. This way they all have one face (password) -to the outside world, forming no greater security risk than root alone. -.PP -The home directory of bin contains one important Makefile. You can use it -to recompile all the commands and libraries of the system. Type -.B make -to see the usage message. If you want to compile just one command then you -can simply type -.B make -to do so. To put it in its proper place you have to type -.BR "make install" . -Read the Makefiles in the -.B commands -and -.B lib -subdirectories to understand how everything is put together. If you are -tight on memory then -.B make -may fail to traverse down the source tree and also compile things. You will -have to type -.B make -in each subdirectory. You can run make in /usr/src at the end to see if -you've missed something or not. -.PP -The shell used by MINIX is a minimal version of -.BR ash , -the BSD shell. It has been modified to offer simple line editing using the -.BR editline (3) -library. -.PP -The kernel is not compiled from the master Makefile. To make a new kernel -you have to step into the -.B tools -directory. There you can run four different make commands: -.PP -.TP -.B make -This makes all the different kernel parts and combines them in the file -named -.BR image . -.TP -.B make fdboot -As above and then makes a boot floppy that you can use to restart your -system with. You are prompted for the floppy device name. -.TP -.B make hdboot -First makes the image file and then copies it into the directory -.BR /minix . -If there are already two images in that directory then the newest image will -be removed to make space for this newer image. It is assumed that the -oldest image is the most stable system image, one that always works, and -that the newest image is experimental. Check beforehand what -.B /minix -contains before you run -.BR "make hdboot" . -Remove the oldest image if you want another image to become the stable -image. The Boot Monitor chooses the newest image in -.B /minix -to boot. You can use the monitor command -.B ls minix -to view the images present, and set the -.B image -variable to the full name of the image you want to use instead if the newest -doesn't work. The images in -.B /minix -are named using the MINIX release and version numbers with an extra revision -number added to distinguish the images. -.PP -The first new kernel you would like to make is one configured for your -system. The kernel you are running now contains several drivers -you don't need, or may be missing drivers that you might want. -In you can find a number of -.BI ENABLE_ XXX -variables that can be set to -.B 0 -to exclude, or -.B 1 -to include a particular driver. The full list of configurable parameters -and what they do are described in -.BR config (8). -It is invaluable in figuring out what to change and how in . -.PP -Configuring a new kernel is sometimes not enough to enable new devices, you -sometimes need to use the -.B MAKEDEV -command to make new device files in -.BR /dev . -For pseudo-ttys you also have to check if -.B /etc/ttytab -mentiones the new devices. -.PP -New additions to the system can be made in the -.B /usr/local -tree. An empty directory tree has been set up for you and binaries and -manual pages are already in the search paths. You can make a new user entry -with the -.B adduser -command. -.PP -The -.B TZ -variable in -.B /etc/profile -tells the time zone offset from the wall clock time to GMT. You have to -change it for your time zone. (See -.BR TZ (5).) -.PP -The function keys produce debug dumps, showing various interesting data -about the system. F1 lists processes and F5 shows ethernet stats, which -may be of use now. Read -.BR console (4) -to know all the details of the screen and keyboard. -.SS "23. SYSTEM SHUTDOWN" -You can't just turn a MINIX system off. MINIX must be told to flush the -modified data in the file system cache first. The following -commands/keystrokes can be used to exit MINIX properly: -.TP -.B shutdown -First alert all users and then all processes of the impending shutdown -then halt or reboot the system in one of various ways. See -.BR shutdown (8). -.TP -.B reboot / halt -Alert all processes of the system shutdown then reboot or halt. -.TP -.B \s-2CTRL\-ALT\-DEL\s+2 -Halt the system by running -.BR "shutdown \-h now" . -.PP -MINIX halts by returning to the Boot Monitor, MINIX reboots by instructing -the monitor to reboot MINIX. (MINIX is just a subprocess to the monitor.) -Either halt MINIX and use monitor commands to escape MINIX, or use -.B shutdown \-R -to reset the system. -.PP -When exiting MINIX running under DOS the Boot Monitor's -.B exit -command will return you to the DOS prompt. The Boot Monitor and MINIX -are together just a pretty big DOS program as far DOS is concerned. -.SH FILES -.TP 12 -.B /usr/ast -Honorary home directory of Andrew S. Tanenbaum. Doubles as the place where -the default setup for a new user is found. -.SH "SEE ALSO" -.BR dosminix (8), -.BR monitor (8), -.BR boot (8), -.BR part (8), -.BR mkfs (1), -.BR mount (8), -.BR M (8), -.BR fstab (5), -.BR hier (7), -.BR config (8), -.BR console (4), -.BR dev (4), -.BR adduser (8), -.BR TZ (5), -.BR mkdist (8), -.BR shutdown (8). -.br -"Operating Systems \- Design and Implementation 2/e" by Andrew S. Tanenbaum -and Albert S. Woodhull. -.SH NOTES -The notation -.BI < file .h> -refers to a C language include file in /usr/include. -.PP -.B Root -and -.B bin -do not have the current directory in their program search path to avoid -executing programs left around by malicious people. This means that to run -.B foo -from the current directory, -.B ./foo -must be typed. -.SH BUGS -There are many PS/2 models, all different. Some will run MINIX, some won't, -some crippled if you lie to MINIX by setting -.B processor -to -.BR 86 . -Almost no PS/2 has a standard disk, so setting -.B c0 -to -.B esdi -or -.B bios -will be necessary. -.PP -Except for the floppy driver, none of the DMA based drivers know about DMA -being limited to a 24 bits address, i.e. the first 16 MB. So under MINIX-386 -you run a slight risk that a -.B tar -or -.B dd -command may use a buffer above 16 MB for reading or writing to a character -device. This only happens if the low 16 MB is taken by some huge processes, -and you have more than 16 MB, of course. -.SH AUTHOR -Kees J. Bot