| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Submitted by: Panagiotis Astithas ( past at ebs dot gr )
Reviewed by: brooks, imp
MFC after: 1 week
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Introduce /etc/rc.d/bluetooth script to start/stop Bluetooth devices. It
will be called from devd(8) in response to device arrival/departure events.
It is also possible to call it by hand to start/stop particular device
without unplugging it.
Introduce generic way to set configuration parameters for Bluetooth devices.
By default /etc/rc.d/bluetooth script has hardwired defaults compatible
with old rc.bluetooth from /usr/share/netgraph/bluetooth/examples. These
can be overridden using /etc/defaults/bluetooth.device.conf file (system
wide defaults). Finally, there could be another device specific override
file located in /etc/bluetooth/$device.conf (where $device is ubt0, btccc0
etc.)
The list of configuration parameters and their meaning described in the
/etc/defaults/bluetooth.device.conf file. Even though Bluetooth device
configuration files are not shell scripts, they must follow basic sh(1) syntax.
The bluetooth.device.conf(5) and handbook update will follow shortly.
Inspired by: Panagiotis Astithas ( past at ebs dot gr )
Reviewed by: brooks, yar
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
> > There is no need to explicitly add "status" to $extra_commands in
> > the /etc/rc.d/pf script as it is implicitly added by /etc/rc.subr's
> > run_rc_command() because of the existing $pf_program.
> >
> > Submitted by: Christoph Schug <chris@schug.net>
...because as yar@ points out: "[...] you were relying on evil
side-effects of the variable being named *_program. hose side-effect
have been eliminated since rc.subr rev. 1.42. [...] The point is that
the default "status" method is for rc.d scripts that handle startup and
shutdown of conventional daemons, and not for custom tasks like the pf
case."
The change is still valid in RELENG_6 (and still doesn't have to be
backed out) as long as rc.subr:r1.42 is not MFC'ed to RELENG_6, too.
|
| |
|
|
|
|
|
|
|
|
| |
the /etc/rc.d/pf script as it is implicitly added by /etc/rc.subr's
run_rc_command() because of the existing $pf_program.
Submitted by: Christoph Schug <chris@schug.net>
MFC after: 1 week
|
|
|
|
| |
reverse (thus allowing /conf to be unmounted).
|
|
|
|
|
|
|
| |
writable /tmp (or TMPDIR) and thus is unsuitable for this job.
Tested by: Joerg Pulz <Joerg dot Pulz at frm2 dot tum dot de>
PR: conf/88293
|
|
|
|
|
|
|
|
|
|
|
| |
extraction.
This will allow cpio archive support to work, at least in situations
where /tmp is writable. Because pax requires a writable /tmp it is
unsuitable for this task, but replacing it will come in a later commit.
Submitted by: Joerg Pulz <Joerg dot Pulz at frm2 dot tum dot de>
PR: conf/88293
|
|
|
|
| |
Finally, delete the old, unfittingly named file "ppp-user".
|
|
|
|
| |
The legacy script "/etc/netstart" will start "ppp", not "ppp-user".
|
|
|
|
| |
Install "ppp" (just repocopied) instead of "ppp-user".
|
|
|
|
|
| |
PR: 88076
Submitted by: Andriy Gapon
|
|
|
|
|
| |
The sendmail script already was on this way,
but it didn't reach the end of it yet.
|
|
|
|
|
|
|
|
| |
command="/path/to/${name}"
since it's applicable here. It's the current style of rc.d.
Pointed out by: pjd
|
|
|
|
|
|
|
|
|
|
|
| |
The rcorder(8) condition PROVIDE'd by the script
and REQUIRE'd by the others becomes "ppp".
The ultimate goal of the transformation is to reduce
confusion resulting from the fact that $name has been
"ppp" already.
Discussed with: pjd, -rc
|
|
|
|
|
|
|
|
|
|
| |
has been set in the first place. This should reduce
unwanted side-effects in rc.d scripts that don't mean
to use $command and rc.subr(8) methods associated with
it at all.
Discussed with: brooks
Reviewed by: -rc (silence)
|
|
|
|
| |
yet it can be enabled when applicable.
|
|
|
|
|
| |
Submitted by: Ulrich Spoerlein
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
/etc/defaults/rc.conf will provide foo_program, too.
By specifying "command" we explicitly say that we're
going to rely on rc.subr(8) default methods, and
rc.subr(8) will take advantage of this soon.
The majority of our rc.d scripts already set "command"
if appropriate, so fix just the non-compliant handful.
|
| |
|
|
|
|
|
|
| |
PR: conf/82430
Submitted by: Pavel Volkov pol at iib dot ru
MFC after: 1 week
|
| |
|
|
|
|
|
|
| |
NFS file system over IPsec.
Suggested by: Tomasz PiĀ³at <tomasz.pilat@axelspringer.pl>
|
|
|
|
|
|
| |
This will allow for NFS mount of /usr over IPsec.
Discussed on: arch@
|
|
|
|
| |
MFC after: 1 month
|
|
|
|
|
|
|
|
|
| |
/etc/defaults/rc.conf. Both daemons can run even if no Bluetooth devices
are attached to the system. Both daemons depend on Bluetooth socket layer
and thus disabled by default. Bluetooth sockets layer must be either loaded
as a module or compiled into kernel before the daemons can run.
MFC after: 1 month
|
|
|
|
| |
MFC after: 1 day
|
|
|
|
|
|
|
|
| |
features. Both the presence of a NOAUTO keyword and an interface being
up can be ignored is the forcestart option is used. Additionally, a
restart option has been added.
Reviewed by: ume
|
|
|
|
|
|
| |
glue.
Submitted by: David Boggs
|
|
|
|
|
| |
Reduce code duplication.
Follow the current style of rc.d scripting.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Start before routing for better system protection.
(pf used to start late during system boot, after
many a network daemon have started already, which
sucked from security POV.)
Remark: For maximum security, pf should start before
netif, but it would create a dependency loop because
pfsync has to start after netif, yet before pf.
Discussed with: mlaier on -pf
MFC after: 5 days
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
system boot, and hook it up in the system.
The separate script is needed because in the presence of various
interface lists in rc.conf ($network_interfaces, $cloned_interfaces,
$sppp_interfaces, $gif_interfaces, more to come) it is hard to start
them orderly, so that pfsync is brought up after its syncdev, which
is required for the proper startup of pfsync.
Discussed with: mlaier on -pf
MFC after: 5 days
|
|
|
|
|
|
|
|
| |
- utilize default methods instead of rolling local ones;
- avoid to specify BEFORE conditions we don't really need
(pflog will be REQUIRE'd by pf);
- omit extra decoration from warning messages, warn() will
decorate them sufficiently.
|
|
|
|
|
|
| |
bsdextended_script from rc.conf(5):
Not objected by: trhodes
|
|
|
|
|
|
| |
a list of possible keywords, not all them in a single argument.
This also fixes the issue of extra delimiter characters appearing
on the help line from rc.d scripts not setting $extra_commands.
|
| |
|
|
|
|
|
| |
configured, check if the UP flag is set instead of checking for the
netmask keyword.
|
| |
|
|
|
|
|
|
|
| |
does this).
Submitted by: Andre Albsmeier <Andre dot Albsmeier at siemens dot com>
PR: conf/86606
|
|
|
|
| |
No objections from: mlaier
|
| |
|
|
|
|
|
| |
file either. This clears the way for third-party SSH ports to install
an RCng startup script.
|
|
|
|
|
|
|
| |
administrator to specify additional start-up flags to the Kerberos
5 Authentication Server.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
| |
override the value of mountd_args. This fixes the problem
where mountd_args was not properly being set if
weak_mountd_authentifcation="YES" was set in rc.conf.
PR: conf/86260
Submitted by: Thierry Herbelot <thierry at herbelot dot com>
MFC after: 3 days
|
|
|
|
|
|
| |
printing boot-time errors that don't reflect true error conditions.
MFC after: 1 week
|
|
|
|
|
|
|
| |
spamming the console in the event that a loader tunable 'dumpdev'
isn't defined, which is not a relevant failure to report.
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
until we realize if ipfw(4) ever used.
PR: bin/85970
Submitted by: Andre Albsmeier
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
| |
The OpenFirmware console isn't used on real systems anymore and
I never get to multi-user mode in psim. There are problems with
zs that need to be resolved before these lines can be enabled.
This eliminates disconcerting warnings on boot.
MFC after: 2 days
|