Re: Howto change ownership of device under devfs

2002-02-25 Thread Matijs van Zuijlen
On 2002.02.26 01:02:03 +0100 Matijs van Zuijlen wrote: On Mon, Feb 25, 2002 at 03:08:02PM -0500, dman wrote: > I don't know anything about flushd, but This is all I got. I'm trying to figure out which part of mail system messed up (spamassassin, procmail, or exim), and I'm waiting for this messa

Re: Howto change ownership of device under devfs

2002-02-25 Thread Matijs van Zuijlen
On Mon, Feb 25, 2002 at 03:08:02PM -0500, dman wrote: > I don't know anything about flushd, but This is all I got. I'm trying to figure out which part of mail system messed up (spamassassin, procmail, or exim), and I'm waiting for this message to show op in the archives, so I can actually read it

Re: Howto change ownership of device under devfs

2002-02-25 Thread dman
On Mon, Feb 25, 2002 at 02:33:44PM +0100, Matijs van Zuijlen wrote: | On Sun, Feb 24, 2002 at 11:47:28PM +1000, mdevin wrote: | > Yes. I agree. But it would be interesting to check if the config file | > shows that devfs was selected but not enabled at boot to be sure. | | Yes, that is the case

Re: Howto change ownership of device under devfs

2002-02-25 Thread Matijs van Zuijlen
On Sun, Feb 24, 2002 at 11:47:28PM +1000, mdevin wrote: > On Thu, Feb 21, 2002 at 01:12:22PM +0100, Matijs van Zuijlen wrote: > > Umm.. this actually brings me to a question: I upgraded my kernel to > > 2.4.17 from 2.2.something, and after a while found a complaint from > > noflushd that I had a de

Re: Howto change ownership of device under devfs

2002-02-24 Thread mdevin
On Thu, Feb 21, 2002 at 01:12:22PM +0100, Matijs van Zuijlen wrote: > Umm.. this actually brings me to a question: I upgraded my kernel to > 2.4.17 from 2.2.something, and after a while found a complaint from > noflushd that I had a devfs-enabled kernel, but devfs wasn't on, and > so it wouldn't st

Re: Howto change ownership of device under devfs

2002-02-23 Thread dman
On Sat, Feb 23, 2002 at 04:07:01PM -0500, Jerome Acks Jr wrote: | On Wed, Feb 20, 2002 at 11:04:44PM -0600, Michael Heldebrant wrote: | > I created a file in the conf.d directory for my system that contains the | > following lines: | > | > REGISTER ^tts/0 PERMISSIONS root.nut 0660

Re: Howto change ownership of device under devfs

2002-02-23 Thread Jerome Acks Jr
On Wed, Feb 20, 2002 at 11:04:44PM -0600, Michael Heldebrant wrote: > On Wed, 2002-02-20 at 22:14, mdevin wrote: > > I need to change the ownership of my 2nd serial port for nut to work > > properly with my ups. I am using devfs which is enabled at boot. > > > > I can set the ownership with a com

Re: Howto change ownership of device under devfs

2002-02-21 Thread Matijs van Zuijlen
On 2002.02.21 11:47:01 +0100 mdevin wrote: OK, I will do that for now. But there must be a way to tell devfs the ownership directly rather than have devfsd fudge them the way you want after. What if you don't run devfsd. devfs is supposed to work without devfsd. It's possible, apparantly. Y

Re: Howto change ownership of device under devfs

2002-02-21 Thread mdevin
On Wed, Feb 20, 2002 at 11:04:44PM -0600, Michael Heldebrant wrote: > On Wed, 2002-02-20 at 22:14, mdevin wrote: > > I need to change the ownership of my 2nd serial port for nut to work > > properly with my ups. I am using devfs which is enabled at boot. > > > > Also, I would prefer to change the

Re: Howto change ownership of device under devfs

2002-02-20 Thread Michael Heldebrant
On Wed, 2002-02-20 at 22:14, mdevin wrote: > I need to change the ownership of my 2nd serial port for nut to work > properly with my ups. I am using devfs which is enabled at boot. > > I can set the ownership with a command like: > chown root.nut /dev/tts/1 > That works no problem, but I need it

Howto change ownership of device under devfs

2002-02-20 Thread mdevin
I need to change the ownership of my 2nd serial port for nut to work properly with my ups. I am using devfs which is enabled at boot. I can set the ownership with a command like: chown root.nut /dev/tts/1 That works no problem, but I need it to continue to have those ownerships when the computer