[ale] udev file permissions

[Jeff Lightner]

Haven't done it on RHEL4 but on RHEL5 I was able to set some (disk)
device permissions in udev:

This is my /etc/udev/rules.d/60-raw.rules file for raw devices:

# PERC 5/i Logical Disk partitions to raw bindings for Oracle 10gR2 
#
# Note:  No Oracle Clusterware/CRS this host so no voting disk or OCR
raw)
#
# Note: no redundancy required here - Using PERC 5/i RAID 5 Logical Disk
#
# Basic Bindings
# raw1 & raw2 = Disks for first ASM Disk Group (Data)
   ACTION=="add", KERNEL=="sda6", RUN+="/bin/raw /dev/raw/raw1 %N"
   ACTION=="add", KERNEL=="sda7", RUN+="/bin/raw /dev/raw/raw2 %N"
# raw3 & raw4 = Disks for second ASM Disk Group (Flash Recovery Area
[FRA]
   ACTION=="add", KERNEL=="sda8", RUN+="/bin/raw /dev/raw/raw3 %N"
   ACTION=="add", KERNEL=="sda9", RUN+="/bin/raw /dev/raw/raw4 %N"
#
# Permissions for bound raw devices
# ASM (Data and FRA)
   KERNEL=="raw[1-4]*", OWNER="mrdtora", GROUP="dba", MODE="660"
#
#
##################### END OF ORACLE CUSTOMIZATIONS
#############################


With above udev IS setting permissions, ownership and group on every
boot for my raw devices as required by Oracle.  (No need for a reboot -
run the /sbin/start_udev command for testing.)

A quick Google search for ttyUSB udev revealed this link that seems to
suggest similar syntax for your USB stuff:
http://www.redhat.com/archives/redhat-install-list/2006-February/msg0014
0.html



-----Original Message-----
From: ale-bounces at ale.org [mailto:ale-bounces at ale.org] On Behalf Of
Geoffrey
Sent: Monday, March 10, 2008 9:22 AM
To: ale at ale.org
Subject: Re: [ale] udev file permissions

Jim Lynch wrote:
> Geoffrey wrote:
>> Jim Lynch wrote:
>>   
>>> Geoffrey wrote:
>>>     
>>>> If there is one thing that is stopping Linux from better
acceptance, 
>>>> it's issues like this.  I was running Red Hat Enterprise 4, syncing
my 
>>>> palm via jpilot.  I do a clean install of Red Hat Enterprise 5 and
I can 
>>>> no longer sync my palm.  I know what the problem is, the
permissions on 
>>>> the devices created by udev.  Problem is, I can not find sufficient

>>>> documentation to tell my how to make this work.  I've found various

>>>> references to permissions files and such, but none of them are 
>>>> consistent.  I've spent the better part of a day on this issue,
still, 
>>>> no love.
>>>>
>>>> So, anyone have a pointer as to how to make udev set the proper 
>>>> permissions on the /dev/ttyUSB[12] devices when I plug my palm up?
>>>>
>>>>   
>>>>       
>>> I think the usual way to overcome the inability to use /dev devices
in 
>>> general is to note what group the device belongs to, perhaps tty in
this 
>>> case, and add yourself to that group.  All the devices I've run into
are 
>>> set to 660 so group has read/write access.  At least this is the way
I 
>>> normally get around the problem.
>>>     
>> Well, it's not the solution I was looking for, but it works, so
thanks 
>> for the response.
>>
>> I guess that's the positive side of all this.  Great support from the

>> community and "there's always more then one way to do it."
>>
>> Thanks Jim.
>>
>>   
> I'm going to go out on a limb here and arrogantly suggest "that's the 
> way it is supposed to be done". ;)

Well, the reason I thought there was another approach was based on my 
research into udev.  Udev has permissions specified in two different 
places, thus I assumed I could get it working from that point.

Generally, by adding myself to the group is likely a safer solution then

opening up the perms anyway.

> Glad you got it working.

Yeah, thanks again.

-- 
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
  - Benjamin Franklin
_______________________________________________
Ale mailing list
Ale at ale.org
http://mail.ale.org/mailman/listinfo/ale
----------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.
----------------------------------