linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev udevstart merge
Date: Tue, 10 Aug 2004 23:41:49 +0000	[thread overview]
Message-ID: <20040810234149.GA390@smtp.west.cox.net> (raw)
In-Reply-To: <20040810151104.GA854@vrfy.org>

On Tue, Aug 10, 2004 at 04:34:28PM -0700, Greg KH wrote:

> On Tue, Aug 10, 2004 at 05:11:04PM +0200, Kay Sievers wrote:
> > 
> > http://linuxusb.bkbits.net:8080/udev/cset@1.831?nav=index.html|ChangeSet@-2d
> > 
> > Isn't it pretty ugly to decide the behavior of a binary by its name?
> > 
> > +	if (strstr(argv[0], "udevstart"))
> > +		is_udevstart = 1;
> 
> It's the way programs like busybox works.
> 
> > And why you don't just link the necesssary objects to udevstart?
> > It is only run once on a booting system.
> 
> The embedded people wanted to make things smaller.  Overall it is.

And, faster.  While it's not a noticable difference on a desktop box, it
is on slower embedded ones.

> > And at last, why don't we see patches like this on the list?
> 
> Bug Tom about that one...

I didn't know there was a list, but I'm on it now.

-- 
Tom Rini
http://gate.crashing.org/~trini/


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
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-08-10 23:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10 15:11 udev udevstart merge Kay Sievers
2004-08-10 23:34 ` Greg KH
2004-08-10 23:41 ` Tom Rini [this message]

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=20040810234149.GA390@smtp.west.cox.net \
    --to=trini@kernel.crashing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).