NetBSD/etc/rc.d/mountcritremote

#!/bin/sh
#
# $NetBSD: mountcritremote,v 1.7 2002/04/29 12:29:53 lukem Exp $
#

# PROVIDE: mountcritremote
# REQUIRE: NETWORKING root mountcritlocal

. /etc/rc.subr

name="mountcritremote"
start_cmd="mountcritremote_start"
stop_cmd=":"

mountcritremote_start()
{
	#	Mount critical filesystems that may be `remote'.
	#	(as specified in $critical_filesystems_remote)
	#	This usually includes /usr.
	#
	mount_critical_filesystems remote

}

load_rc_config $name
run_rc_command "$1"
rc.d scripts derived from /etc/rc 2000-03-10 14:53:23 +03:00			`#!/bin/sh`
			`#`
don't bother warning or supporting obsolete $critical_filesystems_beforenet or $critical_filesystems; postinstall now checks for these 2002-04-29 16:29:53 +04:00			`# $NetBSD: mountcritremote,v 1.7 2002/04/29 12:29:53 lukem Exp $`
rc.d scripts derived from /etc/rc 2000-03-10 14:53:23 +03:00			`#`

			`# PROVIDE: mountcritremote`
Rename NETWORK to NETWORKING, to allow rc.d to be on a case insensitive file system (prevents conflict with 'network'). PROVIDE both NETWORKING and NETWORK (the latter for compatibility with 3rd party scripts). 2002-01-31 04:26:05 +03:00			`# REQUIRE: NETWORKING root mountcritlocal`
rc.d scripts derived from /etc/rc 2000-03-10 14:53:23 +03:00
			`. /etc/rc.subr`

			`name="mountcritremote"`
Replace $critical_filesystems_beforenet with $critical_filesystems_local . Replace $critical_filesystems with $critical_filesystems_remote . The new names are now consistent with the type argument that mount_critical_filesystems() is called with, and allows for other types to be easily supported by that function. For backwards compatibility purposes, if the now obsolete variable is defined (even empty), it takes precedence over the new form, and you will be warned. If you want to stop the warnings, update your rc.conf(5) settings! 2002-03-27 11:53:39 +03:00			`start_cmd="mountcritremote_start"`
rc.d scripts derived from /etc/rc 2000-03-10 14:53:23 +03:00			`stop_cmd=":"`

Replace $critical_filesystems_beforenet with $critical_filesystems_local . Replace $critical_filesystems with $critical_filesystems_remote . The new names are now consistent with the type argument that mount_critical_filesystems() is called with, and allows for other types to be easily supported by that function. For backwards compatibility purposes, if the now obsolete variable is defined (even empty), it takes precedence over the new form, and you will be warned. If you want to stop the warnings, update your rc.conf(5) settings! 2002-03-27 11:53:39 +03:00			`mountcritremote_start()`
			`{`
			# Mount critical filesystems that may be `remote'.
			`# (as specified in $critical_filesystems_remote)`
			`# This usually includes /usr.`
			`#`
			`mount_critical_filesystems remote`

			`}`

Use load_rc_config() (from rc.subr) instead of sourcing /etc/rc.conf. This allows us or a user to change the configuration file method in one place - rc.subr - without having to edit all of the rc.d/* files. 2000-05-13 12:45:06 +04:00			`load_rc_config $name`
rc.d scripts derived from /etc/rc 2000-03-10 14:53:23 +03:00			`run_rc_command "$1"`