| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
devfs(8) rules in rc(8). It is most useful for applying
rules to devfs(5) mount points in /dev or inside jails.
The following line of script is sufficient to
mount a relatively useful+secure devfs(5) in a jail:
devfs_mount_jail /some/jail/dev
Some new shell routines available to scripts that source
rc.subr(5):
o devfs_link - Makes it a little easier to create symlinks
o devfs_init_rulesets - Create devfs(8) rulesets from devfs.rules
o devfs_set_ruleset - Set a ruleset to a devfs(5) mount
o devfs_apply_ruleset - Apply a ruleset to a devfs(5) mount
o devfs_domount - Mount devfs(5) and apply some ruleset
o devfs_mount_jail - Mount devfs(5) and apply a ruleset
appropriate to jails.
Additional rulesets can be specified in /etc/devfs.rules.
If the devfs_system_ruleset variable is defined in rc.conf
and it contains the name of a ruleset defined in /etc/defaults/devfs.rules
or user supplied rulesets in /etc/devfs.rules then that ruleset will
be applied to /dev at startup by the /etc/rc.d/devfs script. It can
also be applied post-startup:
/etc/rc.d/devfs start
This is a more flexible mechanism than the previous method of using
/etc/devfs.conf. However, that method is still available.
Note: since devfs(8) doesn't provide any way for creating symlinks
as part of a ruleset, anyone wishing to create symlinks in a devfs(5)
as part of the bootup sequence will still have to rely on /etc/devfs.conf.
|
| |
|
| |
|
|
|
|
| |
Submitted by: Ulrich Spoerlein <q@uni.de>
|
| |
|
|
|
|
| |
support.
|
|
|
|
|
|
|
|
|
| |
use the atmconfig(8) utility instead of route(8) to install those routes.
For this we need a new rc.conf variable natm_static_routes that works
just like static_routes except that the referenced routes use the syntax
of atmconfig(8).
Okay'ed by: mtm
|
|
|
|
|
| |
delay. It seems that dhclient really needs the time
to get killed.
|
|
|
|
|
| |
obsolete. A working dhclient with OMAPI will also not need
this.
|
|
|
|
|
|
|
|
|
|
| |
one internal device. Don't call the startup procedure again if
we already use start.
Support a manually started dhclient and keep its configured
interfaces after pccard removal.
Make pccard_ether working in single-user mode without /usr mounted.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are now many configurations which have a NIC on board, and
pccard slots. If a dhclient is running on the internal nic, the
Improve the handling dhcp handling of pccard_ether.
Improve the dhcp handling of pccard_ether.
There are now many configurations which have a NIC on board and
Improve the dhcp handling of pccard_ether.
There are now many configurations which have a NIC on board and
cardbus slots too. If a dhclient was already running on the internal
NIC, the user was forced to kill a running dhclient manually.
If now a pccard is included at startup time, /etc/rc.d/dhclient
start does include it into the startup list for dhcp devices.
That means you can now do dhcp on the internal and the pccard devices
at the same time. If the card is plugged in later, a running dhclient
(working for the internal interface only) is killed, and restarted,
but the interface name of the new pccard is added to the internal
name. After removal, /etc/rc.d/dhclient is started again. This
script does nothing if there are no devices in /etc/rc.conf
This is only a workaround for a well known problem. After we have
a dhcp client which handles device adding and removal, it will go
away.
|
|
|
|
|
|
|
| |
the required .cf file(s).
Submitted by: ru
X-MFC after: mergemaster MFC
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
| |
PR: 55341
submitted by: Hye-Shik Chang <perky@freebsd.org>
|
| |
|
|
|
|
|
|
| |
/etc/syslogd.conf -> /etc/syslog.conf
MFC after: 3 days
|
|
|
|
| |
Appologies to: those that submitted these to me.
|
|
|
|
|
|
|
|
| |
and the ports assigned by IANA.
PR: conf/55125
Submitted by: Bruce M Simpson <bms@spc.org>
MFC after: 2 days
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The original name was really a mistake since
/usr/local/etc/rc.d scripts can (and usually do) start
more than just daemons. Even the output in the script
uses 'local packages.' Also, the term 'local daemons' is
used by rc.d/local, which was etc/rc.local of rcOG fame.
No repo-copy because there isn't much history to save.
I will remove localdaemons shortly with all the other
files that don't belong in rc.d anymore.
Discussed with: dougb, freebsd-rc@yahoogroups.com
|
| |
|
| |
|
|
|
|
| |
hooked up to the build.
|
|
|
|
|
|
| |
required commands are not on a mounted file system.
Noticed by: bde
|
|
|
|
|
| |
PR: 51729
Submitted by: Kang Liu <liukang@bjpu.edu.cn>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for the harp(4) pseudo driver and for loadable native HARP drivers
(like hfa_pci).
To use harp(4) the rc variable natm_interfaces must be set to the
list of NATM interfaces to be used for HARP. These interfaces
will be brought up with ifconfig and the harp(4) will be loaded.
To use loadable native HARP drivers atm_load must be set to
the list of drivers to load.
Reviewed by: mtm, gordon (partly)
|
|
|
|
| |
cause to much troubles with applications.
|
|
|
|
| |
Reviewed by: mtm
|
|
|
|
|
|
|
|
|
| |
and PAM configuration. Remove the line concerning "auth_list"
from the template, since it's referenced only in the tinyware
password command, and only #ifdef KERBEROS, which isn't defined
in tinyware. Add a comment about auth.conf being on the way
out the door. The one remaining consumer of auth.conf is
crypt(3).
|
|
|
|
|
|
| |
Kill natd in stop().
Reviewed by: mtm
|
|
|
|
|
| |
interface is to be stopped. In this case we don't want to go
beyond releasing the lease.
|
|
|
|
|
|
|
|
|
| |
the address, also kill the dhclient process. Instead of doing the
release in the stop command, move it to the precmd stage and allow
rc.subr(8) to automatically kill the dhclient process by leaving the
stop command undefined.
Noticed by: mbr
|
|
|
|
|
|
|
| |
evaluating the $_precmd command as a string. We're not actually
trying to evaluate the contents of the command.
Reported by: Glenn Johnson <gjohnson@srrc.ars.usda.gov>
|
|
|
|
|
|
|
| |
Fixed small typo
Reviewed by: imp
Approved by: imp
|
|
|
|
|
| |
Submitted by: David Wolfskill
PR: 53356
|
|
|
|
|
|
| |
line and must always appear on the line.
Submitted by: netchild
|
|
|
|
|
|
|
| |
we would lose it's pid file. Also, cleanup the depencies in
rc.d/cleanvar
PR: bin/53516
|
|
|
|
|
|
|
|
| |
variable in rc.conf to have sshd from ports (or somewhere else) installed.
So, don't make the sshd_config for the base system a required file
to start the service.
PR: conf/45766
|
| |
|
|
|
|
|
|
|
|
|
| |
instead of SENDMAIL_MC but don't remove on it 'make clean' as the
user may not have the original .mc file and removing it could be
dangerous (e.g., make SENDMAIL_CF=/etc/mail/sendmail.cf clean).
Noticed by: peter
MFC after: 3 days
|
|
|
|
|
| |
PR: misc/53293
Submitted by: ru
|
|
|
|
| |
reference is not enough.
|
| |
|
|
|
|
|
|
| |
files to get mergemaster working again.
Noticed by: Shin-ichi YOSHIMOTO <yosimoto@waishi.jp>
|
|
|
|
|
|
|
|
|
| |
defined. The only two files installed in this case are aliases (which
I believe other MTAs may use) and mailer.conf (which isn't sendmail,
it belongs to mailwrapper).
PR: 50477
MFC after: 5 days
|
|
|
|
|
|
|
|
|
|
| |
`hostname`.submit.mc which is templated from freebsd.submit.mc if the
default file does not exist. This makes the building of the submit.cf
behavior identical to that of the the sendmail.cf.
PR: 44256
Submitted by: Matt Emmerton <matt@gsicomp.on.ca>
MFC after: 5 days
|
|
|
|
|
| |
Submitted by: ru
MFC after: 5 days
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Stop 'make clean' from removing SENDMAIL_CF
- install and distribute targets should not attempt to build anything
- SENDMAIL_ADDITIONAL_CF were not installed in the distribution case
- If SENDMAIL_SET_USER_ID was defined, submit.cf was needlessly installed
in the distribution case
- Collapse install and distribution target into one to remove code
duplication
Submitted by: ru
MFC after: 5 days
|
|
|
|
|
|
|
| |
second level indent of tab should be four spaces
Submitted by: ru
MFC after: 3 days
|