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
/
scripts
/
functions.subsystem.template
< prev
next >
Wrap
Text File
|
2006-11-29
|
2KB
|
45 lines
# This is a template for individual subsystem functions.
#
# hwup checks for certain individual subsystem functions and calls them if they
# are defined. These functions must reside in a file named functions.SUBSYSTEM
# in /etc/sysconfig/hardware/scripts/. Subsystem may be e.g. pci, usb, ieee1394
# or any other subsystem known by hwup. Look at function 'is_known_subsystem' in
# /sbin/hwup. hwup will only source the matching function.SUBSYSTEM file.
#
# You don't have to define all functions. Just these that you need.
# And replace SUBSYSTEM with your subsystems name of course.
#
# Possible functions are:
# Get all necessary information that hwup need here. E.g. read some value from
# sysfs or any other place specific
get_SUBSYSTEM_information() {
SUBSYS_SPECIAL_VALUE="`get it somehow`"
COMMON_HWUP_VAR="`needs to be overwritten`"
}
# After hwup collected all needed information and possibly sourced a
# configuration file it prints some info lines (depending on log level).
# Add your desired output here. This function wil be called if LOG_LEVEL>=6.
show_SUBSYSTEM_information() {
info_mesg "..."
}
# hwup will mostly load modules. Immediately before and after loading modules,
# these functions are called. It does not matter if we load a module via
# MODALIAS or a from a hwcfg-* file.
# All pre/post scripts are called before/after these functions.
pre_init_SUBSYSTEM() {
prepare something ...
}
post_init_SUBSYSTEM() {
clean up something ...
}
# You may also skip the usage of getcfg (which will be removed completely soon)
# with:
get_config_getcfg() {
get_config_fast
}