Re: Permissions on /dev/ttyS1 (Was: Re: debian 1.3.1 troubles)
Bob Hilliard writes: > I have been troubled with intermittently changed permissions on > /dev/ttyS1,... > Why does pppd find it necessary to fiddle with these permissions > anyway? Security, I assume. Perhaps you could have pppd talk to a symlink? -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Permissions on /dev/ttyS1 (Was: Re: debian 1.3.1 troubles)
I have been troubled with intermittently changed permissions on /dev/ttyS1, and have been searching for some cron job that might have caused it. Your comments about the pppd source gave me a clue. I thought that if pppd changes these permissions, then restores them on exit, an abnormal exit could cause the problem. I just started ppp, then killed pppd with kill -9, and found that the permissions on /dev/ttyS1 were now 640. Also, /var/run/ppp1.pid and /var/lock/LCK..ttyS1 were still in place, which would be problematical for some modem operations. Why does pppd find it necessary to fiddle with these permissions anyway? Bob you wrote: >Joseph Carter writes: >> Congratulations, you're now part of dialout and can now .. dialout! The >> bad news is that SOMETHING at least on my machine keeps changing it back >> to mode 640! This is naturally QUITE annoying. Seems the only one that >> gets changed back is ttyS1, which leads me to believe pppd is doing it. >> Not a clue how at the moment. > >From a quick glance at the source, pppd should save the mode and restore it >on exit. I just tested this with pppd-2.3.3 on hamm. Seems to work. -- _ |_) _ |_ Robert D. Hilliard<[EMAIL PROTECTED]> |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debian 1.3.1 troubles
Joseph Carter writes: > Congratulations, you're now part of dialout and can now .. dialout! The > bad news is that SOMETHING at least on my machine keeps changing it back > to mode 640! This is naturally QUITE annoying. Seems the only one that > gets changed back is ttyS1, which leads me to believe pppd is doing it. > Not a clue how at the moment. >From a quick glance at the source, pppd should save the mode and restore it on exit. I just tested this with pppd-2.3.3 on hamm. Seems to work. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debian 1.3.1 troubles
> Debian will not work with my mouse or modem. I installed several times and > the last time I left on the system, and wrote down what I did/ was asked to > do ect. > here is what I did on my final install: okay, let's see here... [..] > #chagned root password , created a user ryder made a pass word for ryder# > - Shall I install shadow passwords? > =N That was probably not the best answer to the question, but it has nothing to do with your problem, so... > - put the META key in minicom config file > =no > - installing xring > -error modem device not found do this as root, assuming COM2 for modem: cd /dev ln -s ttyS1 modem > -configuring gpm > -actual config is: -m /dev/ttys0 -t bare > (as I understand this is like com 1, and is a micorsoft 2 button mouse, > which ins > not mine so I changed it) > -do you want to change anything (Y,n) > =y > -where is mouse? > =/dev/mouse > -what type > =ps2 > =responsiveness (normally not needed) > = > -additional arguments? > = > test (y/N) > =N > -Actual config: -m /dev/mouse -t ps2 > -do you want to change (Y/n) > =N Okay. go back to /dev as root: ln -s psaux mouse Go back and try gpm's config--but test it this time. => > On the previous installs I tried to use makedev to make /dev/mouse, since > gpg complained about no file or directory but I obviously didn't know what > I was doing since it told me some think along the lines of "you cant do > that". But I noticed in this install that during the install of the > drivers, that the PS/2 driver found the device ( Its in the way to long > transcription of my install above) does any one have any suggestions for me > / help?? Oh.., Slakware also recognized my modem, it said it was "___ > (some tty) = com2 in DOS" (I can't remember the device it said but I thing > it might have been /dev/ttys1) Try the symlinks above. They'll make everything happy for you. My system is set up EXACTLY the same in terms of modem and mouse. One caveat: For some really oddball reason Debian defaults making /dev/ttyS1 crw-r--- owned by root.dialout and it's damned annoying. pppd runs as root on debian anyway, so that's no biggie. What IS a biggie is that minicom doesn't (in fact it refuses to for quite valid security reasons..) To make it so you can use the modem, chmod 660 ttyS1 and adduser dialout. Congratulations, you're now part of dialout and can now .. dialout! The bad news is that SOMETHING at least on my machine keeps changing it back to mode 640! This is naturally QUITE annoying. Seems the only one that gets changed back is ttyS1, which leads me to believe pppd is doing it. Not a clue how at the moment. pgpMfGAtVCmRS.pgp Description: PGP signature
Re: debian 1.3.1 troubles
On Thu, Apr 16, 1998 at 03:13:08PM +, Kenneth F. Ryder III wrote: > -configuring gpm > -actual config is: -m /dev/ttys0 -t bare > (as I understand this is like com 1, and is a micorsoft 2 button mouse, > which ins > not mine so I changed it) > -do you want to change anything (Y,n) > =y > -where is mouse? > =/dev/mouse As root, rerun gpmconfig and use /dev/psaux. I think /dev/ttyS1 = com2 to get your modem working. -- Lee Bradshaw [EMAIL PROTECTED] (preferred) Alantro Communications [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: debian 1.3.1 troubles
On Debian, the PS/2 mouse device is /dev/psaux, not /dev/mouse. You must also have PS/2 mouse support compiled into the kernel or as a module, which it seems you already have. -Ossama __ Ossama Othman <[EMAIL PROTECTED]> --- PGP Keys --- Public: http://astrosun.tn.cornell.edu/staff/othman/OO_PUBLIC.asc REVOKED: http://astrosun.tn.cornell.edu/staff/othman/OO_REVOKED.asc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
