Your message dated Mon, 28 May 2007 20:28:50 +0200 with message-id <[EMAIL PROTECTED]> and subject line disagree has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: base-files Version: 3.0.9 Severity: wishlist File: /var/log Many directories, like /etc/alternatives, have READMEs. Perhaps add one to /var/log saying what the sequence of boot/startup logs are, and which processes make them (as e.g. dlocate -S /var/log/boot finds none), etc. e.g. $ dlocate -S /var/log/faillog $ So without you saying what, why, etc. about many of these logs, the user is left scratching their heads. # dlocate README|wc -l 2111 # dlocate README|grep \ /etc|wc -l 9 so one more wouldn't hurt. I would help you write it, except I'm the kind of user who needs to read it.
--- End Message ---
--- Begin Message ---I don't think it's reasonable, and even if, not only syslogd writes into /var/log, it's not its domain, thus it should not clutter it with additional files. Regards, Joey -- It's practically impossible to look at a penguin and feel angry. Please always Cc to me when replying to me on the lists.
--- End Message ---
