#
285830 |
|
23-Jul-2015 |
gjb |
- Copy stable/10@285827 to releng/10.2 in preparation for 10.2-RC1 builds. - Update newvers.sh to reflect RC1. - Update __FreeBSD_version to reflect 10.2. - Update default pkg(8) configuration to use the quarterly branch.[1]
Discussed with: re, portmgr [1] Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
278186 |
|
04-Feb-2015 |
ngie |
MFC r277738:
r277738:
Honor MK_BLUETOOTH with etc/defaults/bluetooth.device.conf
Sponsored by: EMC / Isilon Storage Division
|
#
256281 |
|
10-Oct-2013 |
gjb |
Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
|
#
223543 |
|
25-Jun-2011 |
hselasky |
- Move bus_auto.conf back into /etc/devd/ - Rename bus_auto.conf into usb.conf
Requested by: imp @ MFC after: 14 days
|
#
223536 |
|
25-Jun-2011 |
hselasky |
- Move auto-load devd config file into etc/defaults folder. - Regenerate file after bugfix in the generator.
Suggested by: Jeremy Messenger MFC after: 14 days
|
#
173465 |
|
08-Nov-2007 |
imp |
Another vestige of OLDCARD that needs to be retired.
Prodded by: jhb@
|
#
153272 |
|
09-Dec-2005 |
ru |
Files are installed with mode 444 by default.
|
#
152286 |
|
10-Nov-2005 |
emax |
Start integrating Bluetooth into rc.d system.
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
|
#
139103 |
|
21-Dec-2004 |
ru |
Start the dreaded NOFOO -> NO_FOO conversion.
OK'ed by: core
|
#
136910 |
|
24-Oct-2004 |
ru |
For variables that are only checked with defined(), don't provide any fake value.
|
#
119385 |
|
24-Aug-2003 |
mtm |
o Do not keep a separate list of src/etc/defaults files in the src/etc makefile. This list was used to manually install the files from src/etc. Instead, simply change directory and 'make install'. o There is no reason for the files in src/etc/defaults to be installed as writeable.
Reviewed by: ru
|
#
119166 |
|
20-Aug-2003 |
mtm |
Add a general mechanism for creating and applying 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.
|
#
89976 |
|
30-Jan-2002 |
bde |
Added this makefile. This is not attached to the build yet. I often install parts of /etc manually and it helps to have a makefile for each subdir even if the main makefile doesn't invoke it.
|