undefined - 2002-01-07

Logged In: YES
user_id=16258

i would like to add that this feature would be beneficial,
not only for the above mentioned reason, but just because it
would be a good feature in general. (i say this after
having to patch the previous release, 2.0, because the
daemon would abort after finding an atapi cd-rom/r/rw device
running under scsi emulation [ide-scsi module]; smart
enabled but cannot be read. turning probing and/or a
specific device on/off in a /etc config file [or more simply
on the command-line, which the init script could parse a
config file and obtain the device list] would have allowed
for an easy work-around.)

ps i'm not a debian maintainer (especially not of the
smartsuite package in debian), but a debian user that
decided to take a little time to "bridge the gap" so to say
between the smartsuite sf.net project and the debian
bug-report page.

pps sorry if this has been reported/requested to the
smartsuite author directly (ie an email) and thereby redundant.