home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Chip 2007 January, February, March & April
/
Chip-Cover-CD-2007-02.iso
/
boot
/
i386
/
rescue
/
etc
/
sysconfig
/
hardware
/
config
Wrap
Text File
|
2006-11-29
|
2KB
|
57 lines
## Path: Network/Hardware/Config
## Description: Set some general network configuration
## Type: string("","-","+")
## Default: "+"
## ServiceRestart: network
#
## Type: yesno
## Default: no
# Switch on/off debug messages for all hardware configuration stuff. If set to
# 'no' most scripts can enable it locally with "-o debug".
# Better use the new switch LOG_LEVEL below. DEBUG will be deprecated soon.
# DEBUG=yes will set the loglevel to 7 (debug).
DEBUG="no"
## Type: string("","0","1","2","3","4","5","6","7")
## Default: ""
# Most scripts already use new logging functions where you can choose the same
# loglevels as known from syslog: emerg=0 alert=1 crit=2 err=3 warning=4
# notice=5 info=6 debug=7. Currently we use only err, info and debug.
# If you leave that empty we check for an environment variable LOG_LEVEL or use
# the loglevel from udev. If there is no environment variable nor udev calling
# the script we use the loglevel 3 (err).
DEFAULT_LOG_LEVEL=""
## Type: yesno
## Default: yes
# Should error messages from network configuration scripts go to syslog, or do
# you like them on stderr?
USE_SYSLOG="no"
## Type: yesno
## Default: yes
#
# Every kernel module has a flag 'supported'. If this flag is not set loading
# this module will taint your kernel. You will not get much help with a kernel
# problem if your kernel is marked as tainted. In this case you firstly have
# to avoid loading of unsupported modules.
# If you set this variable to no, then no unsupported module will be loaded
# automatically via
# - udev (hotplug), except modules from dedicated configuration files
# - rcacpid, except there is a manually written list of modules
# Note that there are many other places where modules are loaded which do not
# respect this setting.
LOAD_UNSUPPORTED_MODULES_AUTOMATICALLY=yes
## Type: string
## Default: ""
#
# Since version 0.42 hwup does also bind devices to drivers which are already
# loaded. If you did not specify a driver explicitely in the hardware
# configuration file (hwcfg-*) it tries to determine the driver name (It is not
# always equal to the module name!). You may also set DRIVER=skip in the hwcfg
# files. Then hwup will not bind anything for this device.
# Since some drivers are still buggy concerning device binding you may also
# disable this feature completely by setting 'skip' in the main config file.
DRIVER=