All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kelvie Wong <kwong@wurldtech.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH 2/3] initramfs-module-udev: New module
Date: Mon, 27 Sep 2010 07:39:39 -0700	[thread overview]
Message-ID: <201009270739.40204.kwong@wurldtech.com> (raw)
In-Reply-To: <AANLkTikE+Kqa4OqE50p+_2W1548a1ko40Gb9h8s-NASB@mail.gmail.com>

On September 25, 2010 03:29:15 pm Otavio Salvador wrote:
> Hello,
> 
> On Sat, Sep 25, 2010 at 2:07 PM, Kelvie Wong <kwong@wurldtech.com> wrote:
> > This launches (and kills) udev during the initramfs procedure to populate
> > the /dev tree as udev would.
> 
> I didn't get /why/ do you kill it after starting.
> 
> Personally I think this could be supported by not enabled by default.
> This might be an option that could be set by image.

This was to let the rest of the boot process start udev, if it wants to.

All I need udev for is to populate /dev (specifically, the nodes in /dev/disk 
to set the root partition by label, e.g. for USB disk partitions); I don't 
want to leave processes running when doing the chroot, either.

-- 
Kelvie Wong
Software Developer

Wurldtech Security Technologies Inc.
Suite 1680 - 401 West Georgia St.
Vancouver, B.C.  V6B 5A1
Canada

Phone:       + 1.604.669.6674
Toll Free:   + 1.877.369.6674
Fax:           + 1.604.669.2902
Website:    http://www.wurldtech.com/

"ARE YOU ACHILLES CERTIFIED?"

This message is intended only for the named recipients. This message
may contain information that is privileged, confidential or exempt
from disclosure under applicable law. Any dissemination or copying
of this message by anyone other than a named recipient is strictly
prohibited. If you are not a named recipient or an employee or agent
responsible for delivering this message to a named recipient, please
notify us immediately by telephone at 604-669-6674, and permanently
destroy this message and any copies you may have. Email may not be
secure unless properly encrypted.



  reply	other threads:[~2010-09-27 14:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-25 17:07 [PATCH 1/3] initramfs-image: Make intiramfs images cpio.gz Kelvie Wong
2010-09-25 17:07 ` [PATCH 2/3] initramfs-module-udev: New module Kelvie Wong
2010-09-25 22:29   ` Otavio Salvador
2010-09-27 14:39     ` Kelvie Wong [this message]
2010-09-27 14:51       ` Otavio Salvador
2010-09-27 15:42         ` Kelvie Wong
2010-09-25 17:07 ` [PATCH 3/3] initramfs-udev-image: new image target Kelvie Wong

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=201009270739.40204.kwong@wurldtech.com \
    --to=kwong@wurldtech.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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.