All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] optical_gen
Date: Fri, 18 Aug 2006 15:41:07 +0000	[thread overview]
Message-ID: <1155915667.3333.97.camel@pim.off.vrfy.org> (raw)
In-Reply-To: <d5a13c80608141051w3b3e6dabwb6d58dd11b3ba7be@mail.gmail.com>

On Thu, 2006-08-17 at 18:52 +0600, Alexander E. Patrakov wrote:
> VMiklos wrote:
> > 2006/8/15, Kay Sievers <kay.sievers@vrfy.org>:
> >   
> >> I need to support that, when it's in there. So I'm not willing to put
> >> something in, that isn't already used and has shown that it works for a
> >> lot of people.
> >
> > as far as i see, the Debian scripts are okay for most
> >
> >> Again, it should be commonly used, or at least a common agreement that
> >> it will replace the current distro specific versions, before we ship it.    
> >
> > so what about including the Debian ones so that every distro could
> > drop their own (same) implementations?
> >   
> Debian scripts make a very specific expectation of the bootscript: 
> namely, they expect that the udev-mtab bootscript moves the generated 
> rules from the temporary location in /dev/shm to the final one in 
> /etc/udev/rules.d. Some other systems work in a different way: they fail 
> the entire uevent if /etc is mounted read-only in hope that a script 
> will retrigger it later.

>  * Either the Debian script should be included as-is and its expectation 
> about copying rules in the udev-mtab script has to be documented
>  * Or the Debian script has to be made configurable in order to adapt to 
> the two above-mentioned configurations (i.e., "copy rules" vs "retrigger 
> uevents").

Marco, how does Debian handle the other issues when it never triggers
failed events again? Like /usr or other part of the filesystem, or
whatever service not available at that time of the bootup?

The generic 'retrigger' to create the rules later, when /etc is writable
sounds much easier than having a special boot script logic for that
special case.

In an initramfs boot, which is the standard distro setup today, /etc is
writable at that point anyway, and we don't have that problem, right?

Kay


-------------------------------------------------------------------------
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-18 15:41 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
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 [this message]
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=1155915667.3333.97.camel@pim.off.vrfy.org \
    --to=kay.sievers@vrfy.org \
    --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.