All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olivier Blin <oblin@mandriva.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] optical_gen
Date: Wed, 16 Aug 2006 06:52:24 +0000	[thread overview]
Message-ID: <m38xlpukp9.fsf@dynamo.mandriva.com> (raw)
In-Reply-To: <d5a13c80608141051w3b3e6dabwb6d58dd11b3ba7be@mail.gmail.com>

md@Linux.IT (Marco d'Itri) writes:

> On Aug 15, VMiklos <vmiklos@gmail.com> wrote:
>
>> ok, then what implementation would be ok for you? as Kay said, we need
>> to agree to use _one_, then it could be included in the main tree
> Do you think there is anything wrong with mine? :-)

Does it work fine if /etc is read-only when the rule is run?

In the Mandriva rules, rules are written in /dev/.udev/ if /etc isn't
writable, and then copied to /etc by the initscrips once /etc is
writable (implemented by Andrey Borzenkov).

Please see our scripts and rules here:
http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/udev/current/SOURCES/
62-create_persistent.rules
udev_cdrom_helper (main script, really short and simple)
udev_persistent_lib.sh (helpers shared with net scripts)
udev_copy_temp_rules (copy rules written in /dev/.udev to /etc)

By the way, if we're going to unify the scripts for CD naming, it
would be nice to do the same for network interface names.

-- 
Olivier Blin - Mandriva

-------------------------------------------------------------------------
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

  parent reply	other threads:[~2006-08-16  6:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14 17:51 [PATCH] optical_gen VMiklos
2006-08-14 22:58 ` Greg KH
2006-08-14 23:30 ` Kay Sievers
2006-08-15 18:12 ` VMiklos
2006-08-15 18:32 ` Marco d'Itri
2006-08-15 19:06 ` VMiklos
2006-08-15 19:08 ` Marco d'Itri
2006-08-15 19:22 ` VMiklos
2006-08-16  6:52 ` Olivier Blin [this message]
2006-08-16  8:50 ` Marco d'Itri
2006-08-16 15:49 ` Andrey Borzenkov
2006-08-17 12:43 ` VMiklos
2006-08-17 12:52 ` Alexander E. Patrakov
2006-08-17 13:25 ` Piter PUNK
2006-08-18 15:41 ` Kay Sievers
2006-08-18 17:02 ` Marco d'Itri
2006-08-18 17:13 ` Kay Sievers
2006-08-18 17:22 ` Marco d'Itri
2006-08-18 18:00 ` Kay Sievers
2006-08-18 18:37 ` Marco d'Itri
2006-08-18 23:04 ` Kay Sievers
2006-08-23 10:56 ` VMiklos
2006-08-23 11:40 ` Marco d'Itri
2006-09-01 18:17 ` VMiklos
2006-09-05 13:32 ` Kay Sievers

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=m38xlpukp9.fsf@dynamo.mandriva.com \
    --to=oblin@mandriva.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.