summaryrefslogtreecommitdiffstats
path: root/release/picobsd/mfs_tree
Commit message (Collapse)AuthorAgeFilesLines
* Use a default of 25 lines for xterm. This only affects the behaviourluigi2002-03-081-1/+1
| | | | | over a serial line, because the terminal negotiations using ssh/telnet does the right thing anyways.
* Major cleanup of PicoBSD startup scripts, which now should beluigi2002-03-082-61/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | closer to doing "the right thing". The structure is now the following: * /etc/rc (from MFS) loads the rest of /etc and /root from /fd and then from floppy (if present), then transfers control to /etc/rc1 * /etc/rc1 loads defaults from /etc/rc.conf.defaults, tries to set the hostname basing on the MAC address of the first ethernet interface, and then sources /etc/rc.conf and /etc/rc.conf.local for local configurations * The rest of the startup process is then performed (rc.network and so on). Everything except the initial /etc/rc (from MFS) can be overridden with a local version loaded from floppy. But in most cases, you should only need to customize the following files in /etc: rc.conf rc.firewall hosts Previously there were a number of inconsistencies in the calling between files, and also a lot of clutter in rc.conf and rc.firewall. Also, "rc1" was called "rc" and would overwrite the initial /etc/rc from MFS, making it really hard to figure out what was going on in case of bugs.
* Add entry for xterm-colorluigi2002-03-061-0/+2
|
* Add entries for "dumb" and "dialup" terminals, as the shell in HEADluigi2001-11-011-0/+4
| | | | | | | | | refuses to start if it does not find a matching entry for the terminal type. My impression is that this is a problem in the shell, because at least on PicoBSD images, the shell itself coredumps. Anyways, this is the quickest fix i can come up with.
* Use /dev/fd0 instead of /dev/fd0c for mounting the floppy.luigi2001-06-211-2/+4
| | | | | | | | | | | This must have to do with the use of devfs in -CURRENT, but i have no idea when the devfs is actually mounted (is it a side effect of mount -t nonfs or what ?) and when /dev/fd0c becomes available. For the time being, let's use this hack. Once I understand how devfs works, this can be reverted back to the previous value, and also the part of the build script which creates device entries can be nuked. This is for -current only.
* MF4S: Syncronise with Luigi's work in -stable.joe2001-04-2413-13/+750
|
* The magic for autodetecting the boot media does not work anymoreluigi2001-01-272-2/+2
| | | | on STABLE or CURRENT. Put the explicit name for the floppy.
* remove rc and login.conf files prior to extraction of the newroger2000-07-031-2/+4
| | | | | | | | rc and login.conf files from the /etc directory on the floppy. This prevents the overwrite yes/no prompt from occuring in gzip. (some PicoBSD disks use gzip and some use minigzip, so the gzip -f flag (force) is not an option. minigzip has a different meaning for the -f flag.}
* Add a missing 'fi' from an if statementroger2000-07-011-0/+1
|
* Move mfs-related files to a different subtreeluigi2000-05-312-0/+91
|
* Move mfs-related files to a new locationluigi2000-05-311-0/+38
OpenPOWER on IntegriCloud