Have no idea if this is the problem, but, have you compared the version
of lockfile-progs? I noticed that my updated cron seemed to have
issues, and that it depends on lockfile-progs now, so I wonder if the
latest lockfile-progs has problems. Don't know why things would be
different between kerne
There is nothing in the /var/lock after a clean reboot. Also, if I drop back
to the old 2.0.36 kernel, the problem clears. This is very perplexing since my
other 3 linux boxes are all running the same type of setup (potato/2.2.14).
Any other ideas?
On Fri, 11 Feb 2000, Eric G . Miller wrote:
>
On Fri, Feb 11, 2000 at 10:30:55AM -0800, Chris HOOVER wrote:
> HELP,
>
> I finally took the plunge and upgraded my linux
> server from slink to frozen last night. After running
> apt-get dist-upgrade and moving from 2.0.36 to 2.2.14,
> I can no longer dial out to the internet. When I try
> to
HELP,
I finally took the plunge and upgraded my linux
server from slink to frozen last night. After running
apt-get dist-upgrade and moving from 2.0.36 to 2.2.14,
I can no longer dial out to the internet. When I try
to run pon, syslog reports that /dev/ttyS2 (my modem)
is locked. I tried doin
4 matches
Mail list logo