SEO

greets, ladies, gents

i'm having a small prob with udev, very small but annoying anyway. Rules
in udev.rules dont seem to get set 100% at system init when rc.udev is
called. For example, I've got 2 rom drives, at bootup group ownership on
the devices are "disk" however working rules are setup to set group
onwership to "cdrom." However if i should run udevstart after the system
as fully initialized all the permissions are set correctly.

pg wrote:
> greets, ladies, gents
>
> i'm having a small prob with udev, very small but annoying anyway. Rules
> in udev.rules dont seem to get set 100% at system init when rc.udev is
> called. For example, I've got 2 rom drives, at bootup group ownership on
> the devices are "disk" however working rules are setup to set group
> onwership to "cdrom." However if i should run udevstart after the system
> as fully initialized all the permissions are set correctly.
>
>

is /etc/rc.d/rc.udev executable?

Olive

It is executable and is called by rc.S.

On Fri, 25 Nov 2005 10:09:01 +0100, olive wrote:

> pg wrote:
>> greets, ladies, gents
>>
>> i'm having a small prob with udev, very small but annoying anyway. Rules
>> in udev.rules dont seem to get set 100% at system init when rc.udev is
>> called. For example, I've got 2 rom drives, at bootup group ownership on
>> the devices are "disk" however working rules are setup to set group
>> onwership to "cdrom." However if i should run udevstart after the system
>> as fully initialized all the permissions are set correctly.
>>
>>
>
> is /etc/rc.d/rc.udev executable?
>
> Olive

On Fri, 25 Nov 2005 20:06:03 -0500, pg <g.bizniz@gmail.com> wrote:

>It is executable and is called by rc.S.

?etad ot pu ti si tuB

..tnarG

pg wrote:
> It is executable and is called by rc.S.

How do you know it is being run? Without the script outputting with echo
a message to the first console you cannot tell for sure. What does dmesg
say? Does the following text appear on the first console?
Initializing udev dynamic device directory.

Have you altered the rc.udev file?

Richard

On Sat, 26 Nov 2005 13:34:11 +1000, richard wrote:

> pg wrote:
>> It is executable and is called by rc.S.
>
> How do you know it is being run? Without the script outputting with echo
> a message to the first console you cannot tell for sure. What does dmesg
> say? Does the following text appear on the first console?
> Initializing udev dynamic device directory.
>
> Have you altered the rc.udev file?
>
> Richard


yes it is run at boot, the echo'd udev msg is displayed and I have not
altered the rc in anyway.

Been reading up a bit on on udev and rules, I see it says it'll stop
processing rules for devices when the first rule is applied, ignoring any
subsequent rules for said devices. When I check the default udev.rules it
has rulues with apply to the device in question, my rom drives, which are
hda and hdb. Here is th first rule that applies;

# all block devices
SUBSYSTEM="block", GROUP="disk"

here is the second;
# permissions for IDE CD devices
BUS="ide", KERNEL="*[!0-9]", PROGRAM="/bin/cat /proc/ide/%k/media",RESULT="cdrom*", NAME="%k", GROUP="cdrom", MODE="0660"


Thought i was onto something until I remembered the rules get applied if i run udevstart after boot.

On Sat, 26 Nov 2005 13:13:06 +1100, Grant wrote:

> On Fri, 25 Nov 2005 20:06:03 -0500, pg <g.bizniz@gmail.com> wrote:
>
>>It is executable and is called by rc.S.
>
> ?etad ot pu ti si tuB
>
> .tnarG


..detadpu si ti ,sey

gp

pg wrote:
> Thought i was onto something until I remembered the rules get applied if i run udevstart after boot.

Are you calling typing in
#/etc/rc.d/rc.udev

or
#/sbin/udevstart

Richard

On Sun, 27 Nov 2005 03:40:02 +0000, richard wrote:

> pg wrote:
>> Thought i was onto something until I remembered the rules get applied if i run udevstart after boot.
>
> Are you calling typing in
> #/etc/rc.d/rc.udev
>
> or
> #/sbin/udevstart
>
> Richard

I run via sbin/udevstart

pg wrote:
>>>Thought i was onto something until I remembered the rules get applied if i run udevstart after boot.
>>
>>Are you calling typing in
>>#/etc/rc.d/rc.udev
>>
>>or
>>#/sbin/udevstart
>>
> I run via sbin/udevstart

What happens when you run rc.udev ?
Again after start without having run udevstart.

Does it work as well?

Richard