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
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
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
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
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.
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
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.
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.
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
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
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
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.
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
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
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
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.
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
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
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
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
Hi folks,
I had a power failure this morning. I lost my uptime too. :-( Anyway,
I had to shutdown my rig. After the lights came back on I started
having trouble with internet access. I could connect fine with Kppp.
Thing is, it wouldn't let hardly any data transfer. I could get Kopete
to
21 matches
Mail list logo
