Hi Frans, > As 2.6 will be the default kernel for Etch and /sys is playing an > increasingly important role in system configuration, I was wondering if > it does not make sense to add sysfsutils to base and thus install it by > default on new systems.
It's a small and relatively harmless package, but the actual 'systool' program is more of a debugging tool and not that useful IMHO (I haven't used it myself for months). Probably the most useful thing about this package is the init script and the possiblity to set sysfs variables. I agree that this part makes sense in base. So, we could move the init script to a package that is already in base, if sysfsutils itself is not deemed appropriate for base. I do not have a strong opinion about either option. > BTW. Currently the sysfsutils init script is run at the default (S20) > priority from rc[1-6].d. Is there a specific reason why is not run from > rcS.d instead? I would have expected it earlier... There's no reason; it didn't seem useful enough to me to justify cluttering rcS, so I just left it at the default and didn't bother. If people want me to move it, I can do that, of course. > procps.sh, which has a similar function, is run at S30 from rcS.d. That sounds suitable. Thank you! Martin -- Martin Pitt http://www.piware.de Ubuntu Developer http://www.ubuntu.com Debian Developer http://www.debian.org In a world without walls and fences, who needs Windows and Gates?
signature.asc
Description: Digital signature
