intended usage of /dev/.udev/rules.d/

intended usage of /dev/.udev/rules.d/

[Andrey Borzenkov]

[-- Attachment #1.1: Type: text/plain, Size: 384 bytes --]

Could somebody show where these rules are useful? So far rules, created on the 
fly, are usually created in response to add event and apply to already 
existing objects (i.e. they are for future use). And timeframe where root is 
read-only is really short, not much happens at this time; after root is 
remounted those rules must be copied to stable storage anyway.

Thank you

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 315 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

[-- Attachment #3: Type: text/plain, Size: 226 bytes --]

_______________________________________________
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

Re: intended usage of /dev/.udev/rules.d/

[Marco d'Itri]

[-- Attachment #1.1: Type: text/plain, Size: 266 bytes --]

On Aug 11, Andrey Borzenkov <arvidjaar@mail.ru> wrote:

> Could somebody show where these rules are useful? So far rules, created on the 
Finally we can implement a way to prevent loading a module from the
kernel command line, for a start.

-- 
ciao,
Marco

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 315 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

[-- Attachment #3: Type: text/plain, Size: 226 bytes --]

_______________________________________________
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

Re: intended usage of /dev/.udev/rules.d/

[Kay Sievers]

On 8/11/07, Marco d'Itri <md@linux.it> wrote:
> On Aug 11, Andrey Borzenkov <arvidjaar@mail.ru> wrote:
>
> > Could somebody show where these rules are useful? So far rules, created on the
> Finally we can implement a way to prevent loading a module from the
> kernel command line, for a start.

Right, it's more meant as place to put "temporary triggers" than rules
that should be moved to the real root and persist. Temporary rules
from the rules_creator could be placed there, but it is probably not
needed, don't know now if there is any real use case like this.

But you could do auto-mounting and swap activation of "hotplug"
volumes which are listed in fstab. At bootup you can create temporary
rules by parsing fstab, which trigger on the device/symlink name. That
way, you can have an entry in fstab to specify the mount point, but
don't require the device to be available at bootup.

We can also place a dynamic rule at  bootup which maintains the
/dev/root symlink pointing to the real root device, so kernels without
initramfs will not have an entry in /proc/mounts that points nowhere.

The temporary rules allow to hook actions into specific devices
without the need to do external lookups (like parsing fstab) for all
devices again and again.

We will see, it is just "infrastructure" for now, it isn't really used
besides a few tests we did, so we will need to find out what it is
useful for. :)

Kay

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
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