Before we go any further in that, try to scan something! scanimage seems to be talking to the scanner just fine. Try
$ scanimage > image.pnm and see what happens!
Then, even try xsane!
With syslog.conf, the line you want to uncomment is this one:
Code:
#*.* /var/log/all.log
. The other ones are instructions to you, and syslogd will not be able to understand them.
Please, put the '#' back in front of that first one, and try the one I suggested.
Most programs' config files have a way of including comments: human-readable text to tell users how to use the config file. Generally, they mark these lines using shell-style # marks, C++ style '//' marks, C style /*....*/, samba style ';', or even HTML/XML- style <!--....-->. All lines or areas marked like this are ignored by the program. So in that syslog.conf file, any line with a '#' is ignored, so, as far as syslogd is concerned, that file looks like this:
Code:
*.err;kern.warning;auth.notice;mail.crit /dev/console
*.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages
security.* /var/log/security
auth.info;authpriv.info /var/log/auth.log
mail.info /var/log/maillog
lpr.info /var/log/lpd-errs
ftp.info /var/log/xferlog
cron.* /var/log/cron
*.=debug /var/log/debug.log
*.emerg *
*.* /var/log/all.log
!startslip
*.* /var/log/slip.log
!ppp
*.* /var/log/ppp.log
Get the idea?
Putting a comment mark (#, for instance) in front of a valid statement is called 'commenting out', because it is functionally the same as deleting it. Such 'commented-out' (not, not comment-outed, because that sounds silly!) lines are used to provide examples. You then "un-comment", or remove the comment mark, to enable the example line.