All of lore.kernel.org
 help / color / mirror / Atom feed
From: ynezz <ynezz@true.cz>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/udev
Date: Fri, 1 Dec 2006 21:47:43 +0100	[thread overview]
Message-ID: <20061201204743.GH15202@ibawizard.net> (raw)
In-Reply-To: <20061201175030.GB27853@aon.at>

Bernhard Fischer <rep.nop@aon.at> [2006-12-01 18:50:30]:

> On Wed, Nov 29, 2006 at 10:38:47PM +0100, Petr Stetiar wrote:
> >aldot at uclibc.org <aldot@uclibc.org> [2006-11-29 10:59:44]:
> >
> >> Author: aldot
> >> Date: 2006-11-29 10:59:43 -0800 (Wed, 29 Nov 2006)
> >> New Revision: 16723
> >> 
> >> Log:
> >> - build a udev for the target rather than for the host.
> >
> >Attached patch bumps version to 100, fixes Makefile and init script.
> 
> I use busybox's mdev if i need someone to mknod under me, but ok.
> A few questions / remarks.
> 
> Why do we want to update udev?

That I don't know :) I wanted to try it it and then found out, that it don't
work. So that's why I've send a patch.

> me at s37:~/src/buildroot$ patch --dry-run -p1 -i udev_100.patch 
> missing header for unified diff at line 5 of patch
> can't find file to patch at input line 5
> Perhaps you used the wrong -p or --strip option?

Hm strange, it was just svn diff > udev_100.patch. No additional editing.

> Not your fault, but if !; then echo;exit;fi
> looks like it be saner on context switches and also cycle-wise nicer.

Ok.

> I guess that this is not relevant for people who use udev, so i'll
> pretend to have kept my silence in this respect. Wonder why your system
> takes longer to boot than the system i'm playing with which needs less
> than 15s? *shrug*

:) I'm just playing with my board, I'm using udev just for kernel/fs updating
purposes via USB flash disk and yes, it's big overhead. Didn't know about
mkdev, I'll try it, thanks.

-- ynezz

  parent reply	other threads:[~2006-12-01 20:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-29 18:59 [Buildroot] svn commit: trunk/buildroot/package/udev aldot at uclibc.org
2006-11-29 21:38 ` Petr Stetiar
2006-12-01 17:50   ` Bernhard Fischer
2006-12-01 17:57     ` [Buildroot] update to udev-100 Bernhard Fischer
2006-12-01 20:47     ` ynezz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-12-01 17:49 [Buildroot] svn commit: trunk/buildroot/package/udev aldot at uclibc.org
2006-12-06  8:29 aldot at uclibc.org
2006-12-10 13:53 aldot at uclibc.org
2007-01-14  0:59 sjhill at uclibc.org
2007-01-19 16:23 aldot at uclibc.org
2007-05-07  4:02 sjhill at uclibc.org
2007-08-11 16:50 ulf at uclibc.org
2007-08-11 16:52 ulf at uclibc.org
2007-08-14  6:16 ulf at uclibc.org
2007-08-15 15:47 ulf at uclibc.org
2007-08-15 22:31 ulf at uclibc.org
2008-04-06 10:35 nkukard at uclibc.org
2008-12-08 13:41 jacmet at uclibc.org
2008-12-08 13:41 jacmet at uclibc.org
2008-12-08 13:41 jacmet at uclibc.org
2008-12-08 13:48 jacmet at uclibc.org
2009-02-13 19:58 jacmet at uclibc.org

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=20061201204743.GH15202@ibawizard.net \
    --to=ynezz@true.cz \
    --cc=buildroot@busybox.net \
    /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.