All of lore.kernel.org
 help / color / mirror / Atom feed
From: GNUtoo <GNUtoo@no-log.org>
To: openembedded-devel@lists.openembedded.org
Subject: [RFC] remove mdev recipe(already in busybox)
Date: Thu, 24 Sep 2009 15:11:05 +0200	[thread overview]
Message-ID: <1253797865.5877.110.camel@localhost> (raw)

hi, Tom Rin said:
"To follow up to myself, the 'mdev' package should just go away really.
This particular bug is because 'mdev' has an empty mdev.conf while
busybox's mdev does not, and it contains console/null/etc entries."
in "Re: [oe] [PATCH] mdev: mdev.sh: permit serial console login and
correct init runlevel" 
( http://article.gmane.org/gmane.comp.handhelds.openembedded/25296 )
So should we remove mdev recipe and use busybox's mdev instead...if so
all the recipe/distro that were using it must be updated.
for intance the micro-base-image use it:
IMAGE_DEV_MANAGER = "mdev"
that should be replaced by:
IMAGE_DEV_MANAGER = "busybox-mdev"
A quick grep for IMAGE_DEV_MANAGER in the dev branch shows that only the
micro-base-image use it...

Does someone have an objection(for the mdev recipe removal)?

By the way i sent that mail because there could have things that I
didn't thought,people that could depend on .dev but use external
recipes(I was thinking of thing like MokoMakefiles),or issues with other
branches,But also because I was told to do so.

Denis.






             reply	other threads:[~2009-09-24 13:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24 13:11 GNUtoo [this message]
2009-09-25 17:55 ` [RFC] remove mdev recipe(already in busybox) Otavio Salvador
2009-09-27 19:30   ` GNUtoo

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=1253797865.5877.110.camel@localhost \
    --to=gnutoo@no-log.org \
    --cc=openembedded-devel@lists.openembedded.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.