All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: automatic init.d script installation
Date: Tue, 02 Mar 2004 01:34:37 +0000	[thread overview]
Message-ID: <20040302013436.GA12561@kroah.com> (raw)
In-Reply-To: <1078186231.10733.36.camel@localhost>

On Mon, Mar 01, 2004 at 07:54:02PM -0500, Robert Love wrote:
> On Mon, 2004-03-01 at 19:47, Richard Troth wrote:
> 
> > Yes!
> 
> ... why? :>
> 
> Right now, it just rebuilds udev by walking sysfs.  If we do not _need_
> udev to be rebuilt, then why have the initscript?

I agree.  I don't think it's needed.

Actually I don't use it today at all anyway, I just use that start_udev
script...

Or you can use the udevstart binary I just added to the udev bk tree :)

thanks,

greg k-h


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
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:[~2004-03-02  1:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-02  0:10 automatic init.d script installation Robert Love
2004-03-02  0:22 ` Kay Sievers
2004-03-02  0:23 ` Marco d'Itri
2004-03-02  0:24 ` Robert Love
2004-03-02  0:33 ` Kay Sievers
2004-03-02  0:37 ` Marco d'Itri
2004-03-02  0:38 ` Marco d'Itri
2004-03-02  0:45 ` Richard Troth
2004-03-02  0:47 ` Richard Troth
2004-03-02  0:54 ` Robert Love
2004-03-02  1:34 ` Greg KH [this message]
2004-03-02  1:35 ` Greg KH
2004-03-02 14:58 ` Richard Troth

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=20040302013436.GA12561@kroah.com \
    --to=greg@kroah.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.