107a6eaf0a
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.
|
||
|---|---|---|
| .. | ||
| bridge | ||
| build | ||
| dial | ||
| doc/src | ||
| floppy.tree/etc | ||
| help | ||
| install | ||
| isp | ||
| mfs_tree | ||
| net | ||
| router | ||
| tinyware | ||
| README.html | ||
| Version | ||
<html> <body> <h1><b><center> PicoBSD Development Kit </center></b></h1> <p>All documentation, instructions, list of supported hardware and FAQ are in doc/ directory. If they are missing, go to the doc/src/ subdirectory and do a 'make'. The docs are marked with HTML tags, but we try to keep them readable even without a browser. <p>Please start from <A HREF="doc/intro.html">here</a> for general description of the project and its features, or just go directly <A HREF="doc/how2build.html">here</a> for detailed instructions on how to build your version of PicoBSD. <p>Enjoy!</p> <! $FreeBSD$ > </body> </html>