Re: [gentoo-user] Serial modem and permissions problem.
Neil Bothwick wrote: > On Wed, 07 Mar 2007 13:06:23 -0600, Dale wrote: > > >>> The next time you update udev, your changes will be overwritten. >>> Changes should go in 10-local.rules. >>> > > > >> Thanks. I forgot about that little detail. I better find a how to >> somewhere. >> > > http://www.reactivated.net/udevrules.php > > >>> If your serial port driver is built as a module, you can avoid the >>> reboot by rmmodding and modprobing the driver. The second reboot was >>> unnecessary anyway, restarting nut should have picked up the group >>> changes. >>> > > >> The only module I have is nvidia. I build everything into my kernel >> that I can. I was hoping there was a way to sort of "restart" or >> "reload" udev but I couldn't find one and nobody posted one either. I >> guess there is now two reasons you may have to reboot. >> > > Or another reason to use modules. You could try using udevstart to > repopulate /dev. > > > I found that link when I was googling too. You know, udevstart didn't change the permissions when I ran it. Strange. Anyway, I looked, since I put it back the way it was updated to, it shouldn't change anything, unless they change the group again anyway. I put it back to uucp like they had it. So far so good. My modem works, my UPS is happy, I'm happy too. Thanks. Dale :-) :-) :-) -- www.myspace.com/dalek1967
Re: [gentoo-user] Serial modem and permissions problem.
On Wednesday 07 March 2007 21:31:49 Neil Bothwick wrote: > > The only module I have is nvidia. I build everything into my kernel > > that I can. I was hoping there was a way to sort of "restart" or > > "reload" udev but I couldn't find one and nobody posted one either. I > > guess there is now two reasons you may have to reboot. > > Or another reason to use modules. You could try using udevstart to > repopulate /dev I believe it's udevtrigger rather than udevstart that should be used nowadays... -- Bo Andresen pgpQDFfnyAvU5.pgp Description: PGP signature
Re: [gentoo-user] Serial modem and permissions problem.
On Wed, 07 Mar 2007 13:06:23 -0600, Dale wrote: > > The next time you update udev, your changes will be overwritten. > > Changes should go in 10-local.rules. > Thanks. I forgot about that little detail. I better find a how to > somewhere. http://www.reactivated.net/udevrules.php > > If your serial port driver is built as a module, you can avoid the > > reboot by rmmodding and modprobing the driver. The second reboot was > > unnecessary anyway, restarting nut should have picked up the group > > changes. > The only module I have is nvidia. I build everything into my kernel > that I can. I was hoping there was a way to sort of "restart" or > "reload" udev but I couldn't find one and nobody posted one either. I > guess there is now two reasons you may have to reboot. Or another reason to use modules. You could try using udevstart to repopulate /dev. -- Neil Bothwick I have a spelling checker, it came with my Pea See; It helps me too correct Miss Steaks eye mite knot sea. I ran these versus threw it, yew mae bee pleased too no Its word prefect in every weight; my spell cheque tolled me sew! signature.asc Description: PGP signature
Re: [gentoo-user] Serial modem and permissions problem.
Neil Bothwick wrote: > On Tue, 06 Mar 2007 21:47:40 -0600, Dale wrote: > > >> OK. Here's my update. I changed the config file, the 50-udev.rules >> file, back to the way it was when it was updated. >> > > The next time you update udev, your changes will be overwritten. Changes > should go in 10-local.rules. > Thanks. I forgot about that little detail. I better find a how to somewhere. > >> I then added myself >> to the uucp group and rebooted. Well, my UPS didn't like that one bit. >> So I added nut to the uucp group too. Then I rebooted again. >> Everything *appears* to be working fine. Sorry for all the rebooting >> but they are serial ports. >> > > If your serial port driver is built as a module, you can avoid the reboot > by rmmodding and modprobing the driver. The second reboot was unnecessary > anyway, restarting nut should have picked up the group changes. > > > The only module I have is nvidia. I build everything into my kernel that I can. I was hoping there was a way to sort of "restart" or "reload" udev but I couldn't find one and nobody posted one either. I guess there is now two reasons you may have to reboot. So far, it is working fine though. Thanks Dale :-) :-) :-) :-) -- www.myspace.com/dalek1967
Re: [gentoo-user] Serial modem and permissions problem.
On Tue, 06 Mar 2007 21:47:40 -0600, Dale wrote: > OK. Here's my update. I changed the config file, the 50-udev.rules > file, back to the way it was when it was updated. The next time you update udev, your changes will be overwritten. Changes should go in 10-local.rules. > I then added myself > to the uucp group and rebooted. Well, my UPS didn't like that one bit. > So I added nut to the uucp group too. Then I rebooted again. > Everything *appears* to be working fine. Sorry for all the rebooting > but they are serial ports. If your serial port driver is built as a module, you can avoid the reboot by rmmodding and modprobing the driver. The second reboot was unnecessary anyway, restarting nut should have picked up the group changes. -- Neil Bothwick Tribble math: * + * = *** signature.asc Description: PGP signature
Re: [gentoo-user] Serial modem and permissions problem.
Dale wrote: > OK. Here's my update. I changed the config file, the 50-udev.rules > file, back to the way it was when it was updated. I then added myself > to the uucp group and rebooted. Well, my UPS didn't like that one > bit. So I added nut to the uucp group too. Then I rebooted again. > Everything *appears* to be working fine. Sorry for all the rebooting > but they are serial ports. > > Why did I decide to go and do all this right now. Here is the funny > part. Kppp could access the modem, it could tell it to dial out, it > could connect, even get the DNS servers, but it was NOT going to send > data or accept data like it should. It was like spitting on a four > alarm fire. It would send some but it was just a little bit at a > time. Kopete worked fine though. Go figure. All that was run as a > normal user. To test that this was permission related, I opened a > root Konsole and used wvdial to connect with. The pages loaded like > they should when connected that way. I knew then it was either Kppp > or I still had some lingering permission issues. I suspected the later. > > Lesson of all this, watch those udev updates. They may work 99% of > the time but that 1% can drive you nuts. > > All this because my power went out for about 2 hours. Maybe I need a > bigger UPS. ;-) > > Thanks for all the help. > > Dale > > :D :D :D :D :D > > > > -- > www.myspace.com/dalek1967 > One more little update. After a while I starting seeing the same thing again. I then remerged Kppp and it has been working for a while now. I'm not sure what change that would have made though. Just thought I would mention it in case someone else has the same issue. Dale :-) :-) :-) :-) -- www.myspace.com/dalek1967
Re: [gentoo-user] Serial modem and permissions problem.
Dale wrote: > I also went diggin in the groups file, there is a dialout group in > there that *should* address this. I mentioned in a early reply that > this was likely a security thing. Your link seems to show that it is > that. What I can't figure out is why no one warned us? I only use > Linux and only have one puter that connects to the net so if I didn't > know to check the permissions of the modem, I could have been stuck. > Plus, I did get that error about my UPS. That was really helpful > there. It actually showed me the permissions were wrong and I noticed > they were changed from what they used to be. > > I also notice there is no mention of the uucp group in the link. It > does mention using the group ppp but not uucp. Anyway, I plan to > watch those udev config updates closer next time. They have always > worked before but I learned that *may* not always be true. > > Thanks for the info. > > Dale > > :-) :-) :-) :-) > > -- > www.myspace.com/dalek1967 > OK. Here's my update. I changed the config file, the 50-udev.rules file, back to the way it was when it was updated. I then added myself to the uucp group and rebooted. Well, my UPS didn't like that one bit. So I added nut to the uucp group too. Then I rebooted again. Everything *appears* to be working fine. Sorry for all the rebooting but they are serial ports. Why did I decide to go and do all this right now. Here is the funny part. Kppp could access the modem, it could tell it to dial out, it could connect, even get the DNS servers, but it was NOT going to send data or accept data like it should. It was like spitting on a four alarm fire. It would send some but it was just a little bit at a time. Kopete worked fine though. Go figure. All that was run as a normal user. To test that this was permission related, I opened a root Konsole and used wvdial to connect with. The pages loaded like they should when connected that way. I knew then it was either Kppp or I still had some lingering permission issues. I suspected the later. Lesson of all this, watch those udev updates. They may work 99% of the time but that 1% can drive you nuts. All this because my power went out for about 2 hours. Maybe I need a bigger UPS. ;-) Thanks for all the help. Dale :D :D :D :D :D -- www.myspace.com/dalek1967
Re: [gentoo-user] Serial modem and permissions problem.
On Sun, Mar 04, 2007 at 02:18:41PM -0600, Dan Farrell wrote > FWIW, it was kind of a PITA to set up dialup in a secure way for > multiple users to use with traditional UNIX permissioning. I'm the only person on my machine, but things get complicated because the dialup is emergency backup for my ADSL connection. I can't get the two connections to co-exist peacefully. Furthermore, I use different ISPs for broadband and dialup, because problems at an ISP might take down both broadband and dialup access. That means that I have to copy over a different /etc/ssmtp/ssmtp.conf. So my ~/bin/dialup script is... #!/bin/bash /usr/bin/sudo /sbin/ifconfig eth0 down /usr/bin/sudo /usr/bin/cp -f /etc/ssmtp/295.ssmtp.conf /etc/ssmtp/ssmtp.conf /usr/bin/sudo /usr/sbin/pon 295caext The 3 commands... 1) tear down eth0 2) copy in the appropriate ssmtp.conf for my dialup ISP 3) run pon to actually dialup My ~/bin/dialdown (hang up dialup, and restore ADSL) script is #!/bin/bash /usr/bin/sudo /usr/sbin/poff /usr/bin/sudo /usr/bin/cp -f /etc/ssmtp/istop.ssmtp.conf /etc/ssmtp/ssmtp.conf /usr/bin/sudo /etc/init.d/net.eth0 restart 1) hang up the dialup connection 2) copy in the appropriate ssmtp.conf for my ADSL ISP 3) bring up eth0 To enable doing this without passwords, my /etc/sudoers contains... waltdnes m3000 = (root) NOPASSWD: /sbin/ifconfig eth0 down waltdnes m3000 = (root) NOPASSWD: /usr/bin/cp -f /etc/ssmtp/295.ssmtp.conf /etc/ssmtp/ssmtp.conf waltdnes m3000 = (root) NOPASSWD: /usr/sbin/pon 295caext waltdnes m3000 = (root) NOPASSWD: /usr/sbin/poff waltdnes m3000 = (root) NOPASSWD: /usr/bin/cp -f /etc/ssmtp/istop.ssmtp.conf /etc/ssmtp/ssmtp.conf waltdnes m3000 = (root) NOPASSWD: /etc/init.d/net.eth0 restart -- Walter Dnes <[EMAIL PROTECTED]> In linux /sbin/init is Job #1 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Serial modem and permissions problem.
Dan Farrell wrote: > On Sun, 04 Mar 2007 00:30:23 -0600 > Dale <[EMAIL PROTECTED]> wrote: > > >> Hmmm, I wonder why that was changed? I did a google search for uucp >> and group and it was interesting. It seems this is the norm now. >> When I added fax to the search, it seems that will solve my problem >> of having to fax something as root instead of a user. ;-) Learn >> something every day. I just wonder about my UPS and how it is going >> to like this change. Add nut to the group to I guess. >> >> Well, now we know huh? >> >> Thanks for the help. I better watch the rules update next time. >> >> Dale >> >> :-) :-) :-) :-) >> >> > FWIW, it was kind of a PITA to set up dialup in a secure way for > multiple users to use with traditional UNIX permissioning. The > reorganization of groups, if it deals with that ugliness (visit > http://gentoo-wiki.com/HOWTO_Setup_a_Dialup_Connection#Winmodems_with_Lucent_Apollo_.28ISA.29_and_Mars_.28PCI.29_chipsets > to see for yourself what I mean) I say, it's worth a bit of > reorganization of users. > I also went diggin in the groups file, there is a dialout group in there that *should* address this. I mentioned in a early reply that this was likely a security thing. Your link seems to show that it is that. What I can't figure out is why no one warned us? I only use Linux and only have one puter that connects to the net so if I didn't know to check the permissions of the modem, I could have been stuck. Plus, I did get that error about my UPS. That was really helpful there. It actually showed me the permissions were wrong and I noticed they were changed from what they used to be. I also notice there is no mention of the uucp group in the link. It does mention using the group ppp but not uucp. Anyway, I plan to watch those udev config updates closer next time. They have always worked before but I learned that *may* not always be true. Thanks for the info. Dale :-) :-) :-) :-) -- www.myspace.com/dalek1967
Re: [gentoo-user] Serial modem and permissions problem.
On Sun, 04 Mar 2007 00:30:23 -0600 Dale <[EMAIL PROTECTED]> wrote: > Mark Kirkwood wrote: > > Dale wrote: > > > >> If you can, check to see if udev was upgraded and there was a > >> notice that there are group changes. I would think udev would be > >> what was changed. I'm curious to see your reply though. > > > > Ok - here is the state after the emerge (recall group *was* tty): > > > > $ ls -l /dev/ttyS* > > crw-rw 1 root uucp 4, 64 Mar 4 15:53 /dev/ttyS0 > > crw-rw 1 root uucp 4, 65 Mar 4 15:53 /dev/ttyS1 > > crw-rw 1 root uucp 4, 66 Mar 4 15:53 /dev/ttyS2 > > crw-rw 1 root uucp 4, 67 Mar 4 15:53 /dev/ttyS3 > > > > and /etc/udev/rules.d/50-udev.rules has been updated in the emerge > > to make this ownership change: > > > > $ grep ttyS 50-udev.rules > > KERNEL=="ttyS[0-9]*", NAME="%k", SYMLINK="tts/%n", GROUP="uucp", > > MODE="0660" > > > > I didn't see any notice, it just gets processed when doing > > etc-update. Probably worth eyeballing any changes to 50-udev.rules! > > > > > > So looks like you need to be in the uucp group to dial-up now. > > > > Cheers > > > > Mark > > Hmmm, I wonder why that was changed? I did a google search for uucp > and group and it was interesting. It seems this is the norm now. > When I added fax to the search, it seems that will solve my problem > of having to fax something as root instead of a user. ;-) Learn > something every day. I just wonder about my UPS and how it is going > to like this change. Add nut to the group to I guess. > > Well, now we know huh? > > Thanks for the help. I better watch the rules update next time. > > Dale > > :-) :-) :-) :-) > FWIW, it was kind of a PITA to set up dialup in a secure way for multiple users to use with traditional UNIX permissioning. The reorganization of groups, if it deals with that ugliness (visit http://gentoo-wiki.com/HOWTO_Setup_a_Dialup_Connection#Winmodems_with_Lucent_Apollo_.28ISA.29_and_Mars_.28PCI.29_chipsets to see for yourself what I mean) I say, it's worth a bit of reorganization of users. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Serial modem and permissions problem.
Mark Kirkwood wrote: > Dale wrote: > >> If you can, check to see if udev was upgraded and there was a notice >> that there are group changes. I would think udev would be what was >> changed. I'm curious to see your reply though. > > Ok - here is the state after the emerge (recall group *was* tty): > > $ ls -l /dev/ttyS* > crw-rw 1 root uucp 4, 64 Mar 4 15:53 /dev/ttyS0 > crw-rw 1 root uucp 4, 65 Mar 4 15:53 /dev/ttyS1 > crw-rw 1 root uucp 4, 66 Mar 4 15:53 /dev/ttyS2 > crw-rw 1 root uucp 4, 67 Mar 4 15:53 /dev/ttyS3 > > and /etc/udev/rules.d/50-udev.rules has been updated in the emerge to > make this ownership change: > > $ grep ttyS 50-udev.rules > KERNEL=="ttyS[0-9]*", NAME="%k", SYMLINK="tts/%n", GROUP="uucp", > MODE="0660" > > I didn't see any notice, it just gets processed when doing etc-update. > Probably worth eyeballing any changes to 50-udev.rules! > > > So looks like you need to be in the uucp group to dial-up now. > > Cheers > > Mark Hmmm, I wonder why that was changed? I did a google search for uucp and group and it was interesting. It seems this is the norm now. When I added fax to the search, it seems that will solve my problem of having to fax something as root instead of a user. ;-) Learn something every day. I just wonder about my UPS and how it is going to like this change. Add nut to the group to I guess. Well, now we know huh? Thanks for the help. I better watch the rules update next time. Dale :-) :-) :-) :-) -- www.myspace.com/dalek1967 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Serial modem and permissions problem.
Dale wrote: Mark Kirkwood wrote: Dale wrote: Mick wrote: Hmm, this is what I am getting on a x86 build. # ls -al /dev/ttyS* crw-rw 1 root uucp 4, 64 Mar 3 22:09 /dev/ttyS0 crw-rw 1 root uucp 4, 65 Mar 3 22:09 /dev/ttyS1 crw-rw 1 root uucp 4, 66 Mar 3 22:09 /dev/ttyS2 crw-rw 1 root uucp 4, 67 Mar 3 22:09 /dev/ttyS3 BTW, I am a member of the uucp group, but can't remember if I ever added myself to it manually: uucp:x:14:uucp,michael There have been a lot of changes lately. I'm updating today, so will let you know if my /dev/ttyS* change group ownership thereafter. If you can, check to see if udev was upgraded and there was a notice that there are group changes. I would think udev would be what was changed. I'm curious to see your reply though. Ok - here is the state after the emerge (recall group *was* tty): $ ls -l /dev/ttyS* crw-rw 1 root uucp 4, 64 Mar 4 15:53 /dev/ttyS0 crw-rw 1 root uucp 4, 65 Mar 4 15:53 /dev/ttyS1 crw-rw 1 root uucp 4, 66 Mar 4 15:53 /dev/ttyS2 crw-rw 1 root uucp 4, 67 Mar 4 15:53 /dev/ttyS3 and /etc/udev/rules.d/50-udev.rules has been updated in the emerge to make this ownership change: $ grep ttyS 50-udev.rules KERNEL=="ttyS[0-9]*", NAME="%k", SYMLINK="tts/%n", GROUP="uucp", MODE="0660" I didn't see any notice, it just gets processed when doing etc-update. Probably worth eyeballing any changes to 50-udev.rules! So looks like you need to be in the uucp group to dial-up now. Cheers Mark -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Serial modem and permissions problem.
Mark Kirkwood wrote: > Dale wrote: >> Mick wrote: > >>> >>> Hmm, this is what I am getting on a x86 build. >>> >>> # ls -al /dev/ttyS* >>> crw-rw 1 root uucp 4, 64 Mar 3 22:09 /dev/ttyS0 >>> crw-rw 1 root uucp 4, 65 Mar 3 22:09 /dev/ttyS1 >>> crw-rw 1 root uucp 4, 66 Mar 3 22:09 /dev/ttyS2 >>> crw-rw 1 root uucp 4, 67 Mar 3 22:09 /dev/ttyS3 >>> >>> BTW, I am a member of the uucp group, but can't remember if I ever >>> added myself to it manually: >>> >>> uucp:x:14:uucp,michael >>> >>> >> >> There have been a lot of changes lately. > > I'm updating today, so will let you know if my /dev/ttyS* change group > ownership thereafter. > > Cheers > > Mark If you can, check to see if udev was upgraded and there was a notice that there are group changes. I would think udev would be what was changed. I'm curious to see your reply though. Thanks Dale :-) :-) :-) -- www.myspace.com/dalek1967 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Serial modem and permissions problem.
Dale wrote: Mick wrote: Hmm, this is what I am getting on a x86 build. # ls -al /dev/ttyS* crw-rw 1 root uucp 4, 64 Mar 3 22:09 /dev/ttyS0 crw-rw 1 root uucp 4, 65 Mar 3 22:09 /dev/ttyS1 crw-rw 1 root uucp 4, 66 Mar 3 22:09 /dev/ttyS2 crw-rw 1 root uucp 4, 67 Mar 3 22:09 /dev/ttyS3 BTW, I am a member of the uucp group, but can't remember if I ever added myself to it manually: uucp:x:14:uucp,michael There have been a lot of changes lately. I'm updating today, so will let you know if my /dev/ttyS* change group ownership thereafter. Cheers Mark -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Serial modem and permissions problem.
Mick wrote: > On Saturday 03 March 2007 23:37, Dale wrote: > > >> I suspect something changed with the grouping and I just didn't know >> it. It was likely one of those messages in a compile that went by and I >> didn't see it. It may be for the better, mor secure or something, but I >> just missed it. >> >> Now that you mention it, I think I have to be a member of that group to >> be able to fax too. May give that a try. May fix two things. >> >> Thanks for the info. >> > > Hmm, this is what I am getting on a x86 build. > > # ls -al /dev/ttyS* > crw-rw 1 root uucp 4, 64 Mar 3 22:09 /dev/ttyS0 > crw-rw 1 root uucp 4, 65 Mar 3 22:09 /dev/ttyS1 > crw-rw 1 root uucp 4, 66 Mar 3 22:09 /dev/ttyS2 > crw-rw 1 root uucp 4, 67 Mar 3 22:09 /dev/ttyS3 > > BTW, I am a member of the uucp group, but can't remember if I ever added > myself to it manually: > > uucp:x:14:uucp,michael > > There have been a lot of changes lately. I think this is just one of them. I may just change it back to uucp and add myself to the group. I'm not sure about how that will affect my UPS that connects to the serial port though. It didn't like the uucp group either. We may be playing ring around the group here. :/ I still haven't tried the others though. I'm trying to give everyone a chance to reply and see what all options there are available. ;-) Thanks for the info. At least mine wasn't the only one that got changed. Dale :-) :-) :-) :-) -- www.myspace.com/dalek1967
Re: [gentoo-user] Serial modem and permissions problem.
On Saturday 03 March 2007 23:37, Dale wrote: > I suspect something changed with the grouping and I just didn't know > it. It was likely one of those messages in a compile that went by and I > didn't see it. It may be for the better, mor secure or something, but I > just missed it. > > Now that you mention it, I think I have to be a member of that group to > be able to fax too. May give that a try. May fix two things. > > Thanks for the info. Hmm, this is what I am getting on a x86 build. # ls -al /dev/ttyS* crw-rw 1 root uucp 4, 64 Mar 3 22:09 /dev/ttyS0 crw-rw 1 root uucp 4, 65 Mar 3 22:09 /dev/ttyS1 crw-rw 1 root uucp 4, 66 Mar 3 22:09 /dev/ttyS2 crw-rw 1 root uucp 4, 67 Mar 3 22:09 /dev/ttyS3 BTW, I am a member of the uucp group, but can't remember if I ever added myself to it manually: uucp:x:14:uucp,michael -- Regards, Mick pgpNiNmKn42mi.pgp Description: PGP signature
Re: [gentoo-user] Serial modem and permissions problem.
Walter Dnes wrote: > On Fri, Mar 02, 2007 at 04:08:59PM -0600, Dale wrote > > >> Here is my question. What are the permissions supposed to be? >> I have it set to root:users right now. It was set to root:uucp >> which was not working. >> > > Did you try making your user a member of the "uucp" and "dip" groups? > > Well, to be honest, I'm not even sure what uucp group is, dip either. I never heard of that one. I get the tty one though. It's the terminal. LOL I suspect something changed with the grouping and I just didn't know it. It was likely one of those messages in a compile that went by and I didn't see it. It may be for the better, mor secure or something, but I just missed it. Now that you mention it, I think I have to be a member of that group to be able to fax too. May give that a try. May fix two things. Thanks for the info. Dale :-) :-) :-) :-) -- www.myspace.com/dalek1967
Re: [gentoo-user] Serial modem and permissions problem.
On Fri, Mar 02, 2007 at 04:08:59PM -0600, Dale wrote > Here is my question. What are the permissions supposed to be? > I have it set to root:users right now. It was set to root:uucp > which was not working. Did you try making your user a member of the "uucp" and "dip" groups? -- Walter Dnes <[EMAIL PROTECTED]> In linux /sbin/init is Job #1 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Serial modem and permissions problem.
Mark Kirkwood wrote: > Dale wrote: > >> >> Here is my question. What are the permissions supposed to be? I have >> it set to root:users right now. It was set to root:uucp which was not >> working. If someone has a modem and uses dial-up, can you reply with >> the output of ls -al /dev/ttyS* if you would. If anybody else knows the >> answer, that would be cool too. >> > > This machine *has* been used for dial-up (but is connected to DSL > router now) > > $ ls -al /dev/ttyS* > crw-rw 1 root tty 4, 64 Mar 3 19:42 /dev/ttyS0 > crw-rw 1 root tty 4, 65 Mar 3 19:42 /dev/ttyS1 > crw-rw 1 root tty 4, 66 Mar 3 19:42 /dev/ttyS2 > crw-rw 1 root tty 4, 67 Mar 3 19:42 /dev/ttyS3 > > >> Oh, It had been a couple months since I rebooted, anybody know when this >> happened? How do you get udev to update after changing the rules, other >> than rebooting that is. :/ >> > > No sure on that (maybe look at udevcontrol)... Here's the relevant bit > of my 50-udev.rules FWIW (which is default I think): > > $ grep ttyS /etc/udev/rules.d/50-udev.rules > KERNEL=="ttyS[0-9]*", NAME="%k", SYMLINK="tts/%n", GROUP="tty" Thanks for the info. That seems to work for the UPS. I'll check on the modem in a bit. I'm not sure when or what changed the group though. I looked at the udevcontrol man page, I didn't see anything in there about restarting or reloading the rules. Surely they have a way to do that. I can't unplug and plug back up the serial port. Anybody else know how to "reset" udev?? Thanks again. Dale :-) :-) :-) :-) -- www.myspace.com/dalek1967 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Serial modem and permissions problem.
Dale wrote: Here is my question. What are the permissions supposed to be? I have it set to root:users right now. It was set to root:uucp which was not working. If someone has a modem and uses dial-up, can you reply with the output of ls -al /dev/ttyS* if you would. If anybody else knows the answer, that would be cool too. This machine *has* been used for dial-up (but is connected to DSL router now) $ ls -al /dev/ttyS* crw-rw 1 root tty 4, 64 Mar 3 19:42 /dev/ttyS0 crw-rw 1 root tty 4, 65 Mar 3 19:42 /dev/ttyS1 crw-rw 1 root tty 4, 66 Mar 3 19:42 /dev/ttyS2 crw-rw 1 root tty 4, 67 Mar 3 19:42 /dev/ttyS3 Oh, It had been a couple months since I rebooted, anybody know when this happened? How do you get udev to update after changing the rules, other than rebooting that is. :/ No sure on that (maybe look at udevcontrol)... Here's the relevant bit of my 50-udev.rules FWIW (which is default I think): $ grep ttyS /etc/udev/rules.d/50-udev.rules KERNEL=="ttyS[0-9]*", NAME="%k", SYMLINK="tts/%n", GROUP="tty" -- gentoo-user@gentoo.org mailing list
