From Fedora Project Wiki
(New page: == Init scripts == The interesting init scripts for power management are those which are switch on by default. New services had been probably added after this review (February 2009). The s...)
 
No edit summary
Line 1: Line 1:
== Init scripts ==
== Init scripts ==
The interesting init scripts for power management are those which are switch on by default. New services had been probably added after this review (February 2009). The simplest way how to check most of them was installed all packages which have init script in rawhide (future F-11) and then review them. Our attempt lead to new daemon which should started services on demand. But because of small number of services, which could be handled that way was [[https://bugzilla.redhat.com/show_bug.cgi?id=487665| soud]] refused. Services of appropriate devices should be catching events from upstart/udev/DeviceKit instead of new daemon.
The interesting init scripts for power management are those which are switch on by default. New services had been probably added after this review (February 2009). The simplest way how to check most of them was installed all packages which have init script in rawhide (future F-11) and then review them. Our attempt lead to new daemon which should started services on demand. But because of small number of services, which could be handled that way was [[https://bugzilla.redhat.com/show_bug.cgi?id=487665| soud]] refused. Services of appropriate devices should be catching events from upstart/udev/DeviceKit instead of new daemon.
Part of the review was going through comps, whether there exist some barely used services in @base or so on, but nothing had been found.


=== Hardware services ===
=== Hardware services ===
{|
{|cellpadding="5" cellspacing="0" border="1" width="95%"
service | device | comment
|-
|'''package''' || '''device''' || '''/etc/rc.d/init.d/''' || '''comment'''
|-
|-
bluez | bluetooth | [[https://bugzilla.redhat.com/show_bug.cgi?id=484345 | bugzilla]]
|bluez || bluetooth || bluetooth || patch in [[https://bugzilla.redhat.com/show_bug.cgi?id=484345| bugzilla]]
|-
|-
fnfx | | only for Toshiba laptops  
|fnfx || only for Toshiba laptops || fnfxd || Verify CPU: "dmidecode -s system-manufacturer" and output will be f.e. "Dell Inc."
|-
test with "dmidecode -s system-manufacturer" f.e. "Dell Inc."
/etc/rc.d/init.d/fnfxd
|-
|-
isdn4k-utils | configuration of isdn |/etc/rc.d/init.d/isdn
|isdn4k-utils || configuration of isdn || isdn || /etc/rc.d/init.d/isdn
|-
|-
microcode_ctl | updates the microcode on Intel x86/x86-64 CPU's |
|microcode_ctl || updates the microcode on Intel x86/x86-64 CPU's || microcode_ctl || Verify CPU: "dmidecode -s processor-manufacturer" output will be f.e. "Intel" and command give us architecture "uname - f.e. "x86_64"
test: "dmidecode -s processor-manufacturer" f.e. "Intel"
test: "uname - f.e. "x86_64"
/etc/init.d/microcode_ctl
|-
|-
mt-st | tape drive management Mt (for magnetic tape drives) and st (for SCSI tape devices) |
|mt-st || tape drive management Mt (for magnetic tape drives) and st (for SCSI tape devices) || stinit ||
devices are connected through scsi (the better one) and usb (low-end devices)
devices are connected through scsi (the better one) and usb (low-end devices)
/etc/rc.d/init.d/stinit
|-
|-
openct | PC/SC-Lite, as CT-API driver, have primitive mechanism to export smart card readers to remote machines via TCP/IP |
|openct || PC/SC-Lite, as CT-API driver, have primitive mechanism to export smart card readers to remote machines via TCP/IP || openct || udev wasn't sending information about our smart card reader inclued in keyboard
test: here we can catch the devices with devkit
/etc/rc.d/init.d/openct
|-
|-
pcsc-lite | PC/SC Lite is to provide a Windows(R) SCard interface |
|pcsc-lite || PC/SC Lite is to provide a Windows(R) SCard interface || pcscd || probably same problem as the previous smart card reader
test: here we can catch the devices with devkit
/etc/rc.d/init.d/pcscd
|}
|}

Revision as of 10:38, 20 March 2009

Init scripts

The interesting init scripts for power management are those which are switch on by default. New services had been probably added after this review (February 2009). The simplest way how to check most of them was installed all packages which have init script in rawhide (future F-11) and then review them. Our attempt lead to new daemon which should started services on demand. But because of small number of services, which could be handled that way was [soud] refused. Services of appropriate devices should be catching events from upstart/udev/DeviceKit instead of new daemon.

Part of the review was going through comps, whether there exist some barely used services in @base or so on, but nothing had been found.

Hardware services

package device /etc/rc.d/init.d/ comment
bluez bluetooth bluetooth patch in [bugzilla]
fnfx only for Toshiba laptops fnfxd Verify CPU: "dmidecode -s system-manufacturer" and output will be f.e. "Dell Inc."
isdn4k-utils configuration of isdn isdn /etc/rc.d/init.d/isdn
microcode_ctl updates the microcode on Intel x86/x86-64 CPU's microcode_ctl Verify CPU: "dmidecode -s processor-manufacturer" output will be f.e. "Intel" and command give us architecture "uname - f.e. "x86_64"
mt-st tape drive management Mt (for magnetic tape drives) and st (for SCSI tape devices) stinit

devices are connected through scsi (the better one) and usb (low-end devices)

openct PC/SC-Lite, as CT-API driver, have primitive mechanism to export smart card readers to remote machines via TCP/IP openct udev wasn't sending information about our smart card reader inclued in keyboard
pcsc-lite PC/SC Lite is to provide a Windows(R) SCard interface pcscd probably same problem as the previous smart card reader
Retrieved from "https://fedoraproject.org/w/index.php?title=Features/PowerManagement/initscripts&oldid=91625"