freebsd-dev/release/picobsd/mfs_tree/etc/rc

#!/bin/sh

stty status '^T'
trap : 2
trap : 3

HOME=/; export HOME
PATH=/sbin:/bin:/usr/sbin:/usr/bin; export PATH
dev="/dev/fd0"

trap "echo 'Reboot interrupted'; exit 1" 3
echo "Loading /etc from MFS:/fd ..."
cp -Rp /fd/* /
echo "Updating /etc from ${dev}..."
mount -o rdonly ${dev} /fd && \
{ cd /fd; cp -Rp etc root / ; cd / ; umount /fd ; }
cd /etc
#rm files to stop overwrite warning
for i in *; do
    [ -f $i.gz ] && rm $i
done
gzip -d *.gz
. rc1
exit 0
Move mfs-related files to a different subtree 2000-05-31 12:27:38 +00:00			`#!/bin/sh`

			`stty status '^T'`
			`trap : 2`
			`trap : 3`

			`HOME=/; export HOME`
Major cleanup of PicoBSD startup scripts, which now should be 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. 2002-03-08 05:15:08 +00:00			`PATH=/sbin:/bin:/usr/sbin:/usr/bin; export PATH`
Use /dev/fd0 instead of /dev/fd0c for mounting the floppy. 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. 2001-06-21 08:53:21 +00:00			`dev="/dev/fd0"`
Move mfs-related files to a different subtree 2000-05-31 12:27:38 +00:00
			`trap "echo 'Reboot interrupted'; exit 1" 3`
Major cleanup of PicoBSD startup scripts, which now should be 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. 2002-03-08 05:15:08 +00:00			`echo "Loading /etc from MFS:/fd ..."`
			`cp -Rp /fd/* /`
			`echo "Updating /etc from ${dev}..."`
			`mount -o rdonly ${dev} /fd && \`
			`{ cd /fd; cp -Rp etc root / ; cd / ; umount /fd ; }`
Move mfs-related files to a different subtree 2000-05-31 12:27:38 +00:00			`cd /etc`
remove rc and login.conf files prior to extraction of the new 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.} 2000-07-03 22:31:08 +00:00			`#rm files to stop overwrite warning`
MF4S: Syncronise with Luigi's work in -stable. 2001-04-24 07:46:35 +00:00			`for i in *; do`
Major cleanup of PicoBSD startup scripts, which now should be 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. 2002-03-08 05:15:08 +00:00			`[ -f $i.gz ] && rm $i`
MF4S: Syncronise with Luigi's work in -stable. 2001-04-24 07:46:35 +00:00			`done`
Move mfs-related files to a different subtree 2000-05-31 12:27:38 +00:00			`gzip -d *.gz`
Major cleanup of PicoBSD startup scripts, which now should be 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. 2002-03-08 05:15:08 +00:00			`. rc1`
Move mfs-related files to a different subtree 2000-05-31 12:27:38 +00:00			`exit 0`