I had that problem a few years ago on a slackware system;
it was caused by not having my host name (unqualified)
in the first entry in /etc/hosts; once I made sure
that record was first, the boot messages appeared again.
Don't know if that's still true, but might be worth
a check. (I found that s
> >
> >Where is it on the 2.0 version. the /var/log/messages is very abbreviated
> >the /var/log/syslog is also very abbreviated
>
> ditto.
[...]
> I suspect that a line must now be missing from some /etc/init.d/* file, eg,
> klogd -o -f /var/log/messages
> However, such a line would need to b
>Oz Dror wrote:
>Prior to the debian 2.0 installation I used to have a detail boot log
>on /usr/adm/messages.
>
>Where is it on the 2.0 version. the /var/log/messages is very abbreviated
>the /var/log/syslog is also very abbreviated
ditto.
After upgrading to 2.0, I now see the nice syslog entries
3 matches
Mail list logo
