From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Permissions question with reboots and udev
Date: Mon, 13 Nov 2006 18:22:05 +0000 [thread overview]
Message-ID: <20061113182205.GA3721@kroah.com> (raw)
In-Reply-To: <335DD0B75189FB428E5C32680089FB9F8040C6@mtk-sms-mail01.digi.com>
On Mon, Nov 13, 2006 at 10:15:56AM -0600, Kilau, Scott wrote:
> (Resending to list, first time it got rejected as spam...)
>
> Hi everyone,
> Sorry to bug again.
>
>
> Another quick question that probably has a quick answer.
>
> One of the big "issues" our (Digi's) serial port users seem to always
> have is
> having permissions and ownership of their ttys preserved across reboots.
>
> With non-udev, I wrote a script that would update the major values of
> their
> existing "Digi" tty entries in /dev, while maintaining the current
> permissions/ownerships
> across reboots.
>
> With udev, I am unsure if there is any way to do this...
>
> As far as I can tell, if someone does something like:
>
> chown uucp:uucp /dev/ttya01
>
> Then reboots the system, (or even reloads the driver),
> the devices get blown away, and recreated, and end up back as root:root.
>
> I know you can specify a udev rule to create the devices as a specific
> permission/ownership,
> but that is a sledgehammer approach to it...
Why do you think so?
> I am thinking I could make a rule to ignore "removal" on my devices,
> which I suspect
> will allow me to keep to the ttys around in /dev, but I am stumped on
> making a "rule"
> to "preserve" the existing permission/ownership when/if the device gets
> readded...
>
> Any ideas? Thoughts?
Just add a udev rule that sets the correct owner:group for your devices.
That's what the distros do for all other devices.
Hope this helps,
greg k-h
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x120709&bid&3057&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2006-11-13 18:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 16:15 Permissions question with reboots and udev Kilau, Scott
2006-11-13 18:22 ` Greg KH [this message]
2006-11-13 19:50 ` Kilau, Scott
2006-11-13 20:06 ` Ken Brush
2006-11-14 16:52 ` FW: " Kilau, Scott
2006-11-14 21:40 ` Dan Nicholson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061113182205.GA3721@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).