| Art Alexion on 24 Nov 2006 16:02:33 -0000 |
|
On Thursday 23 November 2006 16:27, Will Dyson wrote: > > Yeah, it looks like hal's behavior here is, if not correct, then at > > least what it always does. > > > > What is in your 'ls /sys/class/tty/ttyS*'? /sys/class/tty/ttyS0: dev device uevent /sys/class/tty/ttyS1: dev device uevent /sys/class/tty/ttyS10: dev device uevent /sys/class/tty/ttyS11: dev device uevent /sys/class/tty/ttyS12: dev device uevent /sys/class/tty/ttyS13: dev device uevent /sys/class/tty/ttyS14: dev device uevent /sys/class/tty/ttyS15: dev device uevent /sys/class/tty/ttyS16: dev device uevent /sys/class/tty/ttyS17: dev device uevent /sys/class/tty/ttyS18: dev device uevent /sys/class/tty/ttyS19: dev device uevent /sys/class/tty/ttyS2: dev device uevent /sys/class/tty/ttyS20: dev device uevent /sys/class/tty/ttyS21: dev device uevent /sys/class/tty/ttyS22: dev device uevent /sys/class/tty/ttyS23: dev device uevent /sys/class/tty/ttyS24: dev device uevent /sys/class/tty/ttyS25: dev device uevent /sys/class/tty/ttyS26: dev device uevent /sys/class/tty/ttyS27: dev device uevent /sys/class/tty/ttyS28: dev device uevent /sys/class/tty/ttyS29: dev device uevent /sys/class/tty/ttyS3: dev device uevent /sys/class/tty/ttyS30: dev device uevent /sys/class/tty/ttyS31: dev device uevent /sys/class/tty/ttyS32: dev device uevent /sys/class/tty/ttyS33: dev device uevent /sys/class/tty/ttyS34: dev device uevent /sys/class/tty/ttyS35: dev device uevent /sys/class/tty/ttyS36: dev device uevent /sys/class/tty/ttyS37: dev device uevent /sys/class/tty/ttyS38: dev device uevent /sys/class/tty/ttyS39: dev device uevent /sys/class/tty/ttyS4: dev device uevent /sys/class/tty/ttyS40: dev device uevent /sys/class/tty/ttyS41: dev device uevent /sys/class/tty/ttyS42: dev device uevent /sys/class/tty/ttyS43: dev device uevent /sys/class/tty/ttyS44: dev device uevent /sys/class/tty/ttyS45: dev device uevent /sys/class/tty/ttyS46: dev device uevent /sys/class/tty/ttyS47: dev device uevent /sys/class/tty/ttyS5: dev device uevent /sys/class/tty/ttyS6: dev device uevent /sys/class/tty/ttyS7: dev device uevent /sys/class/tty/ttyS8: dev device uevent /sys/class/tty/ttyS9: dev device uevent > > > > Do you have stuff in /lib/udev/devices/ ? ls /lib/udev/devices/ console fd loop net ppp shm stderr stdout core kmem MAKEDEV null pts sndstat stdin > > > > If you want to know where those extra device files are coming from, > > you can set udev_log="debug" in /etc/udev/udev.conf and then restart > > the system and look in the syslog. > > > > Otherwise, just reinstalling udev should probably do it. I can't remember if I did this. I am doing it again. Will reboot after completed and follow up. > > Hi Art, > > Just out of curiosity, how did this eventually work out for you? Nothing seemed to work. I just got a DVD-RW for this box, and after getting some blanks and backing up /home, /usr/local and /opt, I am going to do a clean reinstall. I don't want to do this because I have installed stuff that I use periodically that I fear I won't remember where I got, or just to do the reinstall, but it looks like the only solution. I hate when I give in to the temptation of upgrading what was a "well oiled machine". -- _____________________________________________________________ Art Alexion PGP fingerprint: 52A4 B10C AA73 096F A661 92D2 3B65 8EAC ACC5 BA7A Keyserver: hkp://subkeys.pgp.net The attachment - signature.asc - is my electronic signature; no need for alarm. Info @ http://mysite.verizon.net/art.alexion/encryption/signature.asc.what.html _____________________________________________________________ Attachment:
pgpc2RXbs9TK2.pgp ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|