On Sat, Dec 06, 2008 at 12:15:51PM +1300, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > Hi, > > I had the same problem. My solution was to check and change the > permissions on the file that 'soundmodem0' points to. > > IIRC /dev/soundmodem0 is a link to /dev/pts/<something>. If you type ls > -l /dev/soundmodem0 you will see where it points. As root, change the > permissions on the file pointed to to allow rw access.
Changing permissions of devices is probably not the best approach, although on a system where there's only one user it might seem unimportant. > Sorry I cannot be more specific, the laptop I was doing this on is packed > away. Obviously an automated solution is required, especially as the > /dev/pts/xxx device is not always the same one. The automated solution is as Curt suggests, to change Xastir so it actually runs as root at the time it tries to access the sound modem (it then drops that privilege) --- it's done with a single "chmod" command as documented in step two of the "INSTALL" document for Xastir (which you likely wouldn't have read if you installed from a binary package). -- Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM In some cultures what I do would be considered normal. -- Ineffective daily affirmation _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
