I have been using Gentoo on my main machine for months with nary a
problem (Thanks to all involved, Gentoo is a great distribution)! But
something odd started happening a few days ago. When I was ssh'd into it
from my Mac OSX machine it would reset the connection. And then it will
not allow me to reconnect. At first I put it down to some oddity with OS
X (it's an old version anyway).
But yesterday it started doing the same thing when I was logged in from
the OpenBSD machine:
[EMAIL PROTECTED] mp3 $ Read from remote host edison: Connection reset by
peer
Connection to edison closed.
[EMAIL PROTECTED] ssh edison
ssh: connect to host edison port 22: Connection refused
I have been logging into the Gentoo machine from the OpenBSD machine for
months and never had it disconnect before. So my next thought was to
reboot the Gentoo machine (it has been up for a few weeks) and see if
that helped.
It didn't help. It's still doing it and now after the reboot it won't let
me access the cdrom from my normal user account. If I try to use any of
the programs that access it, I get permission errors:
[EMAIL PROTECTED] mp3 $ perl cddb.pl
cannot open cdrom [Permission denied] at
/usr/lib/perl5/5.6.1/CDDB_get.pm line 117.
[EMAIL PROTECTED] buffalo $ cdparanoia -B 1-
cdparanoia III release 9.8 (March 23, 2001)
(C) 2001 Monty <[EMAIL PROTECTED]> and Xiphophorus
Report bugs to [EMAIL PROTECTED]
http://www.xiph.org/paranoia/
/dev/cdrom exists but isn't accessible. By default,
cdparanoia stops searching for an accessible drive here.
Consider using -sv to force a more complete autosense
of the machine.
More information about /dev/cdrom:
Checking /dev/cdrom for cdrom...
Testing /dev/cdrom for cooked ioctl() interface
/dev/scsi/host0/bus0/target0/lun0/cd is not a cooked ioctl
CDROM.
Testing /dev/cdrom for SCSI interface
Could not access device
/dev/scsi/host0/bus0/target0/lun0/cd: Permission denied
If I login as root they work fine. I don't remember changing anything
configuration wise in the last few weeks. The only new software I have
installed in the last month was Audacity a couple of weeks ago. (Which I
never got to work.) Could that have broken something and the problem
didn't show up until now?
Thanks
-Scott
--
[EMAIL PROTECTED] mailing list
