Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martyn Welch <martyn.welch@ge.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] Rootfs without busybox in it
Date: Mon, 22 Mar 2010 08:33:27 +0000	[thread overview]
Message-ID: <4BA72B57.9050807@ge.com> (raw)
In-Reply-To: <201003191752.13129.marcin@juszkiewicz.com.pl>

Marcin Juszkiewicz wrote:
> Hi
>
> As part of my work for BugLabs company I am working on creating root 
> filesystem which does not rely on BusyBox for 90% of commands but rather use 
> normal versions of them.
>   

I have a patch series that completely removes the need for busybox we
have been working on that I have been trying to get in shape to post on
this list . It's definitely not quite right yet, however it works. I'll
post it to the mailing list.

Martyn

> I have something what boots and more or less works but found few issues for 
> which I want to get some discussion.
>
> 1. 'ifupdown' package needed changes:
>
> - removal of 'networking' initscript
> - removal of 'interfaces' definition
> - shipping /etc/network/run/ directory
>
> first two are present in 'netbase' and are usually more optimised for OE 
> targets, last one is required for keeping information about state of 
> interfaces
>
> 2. lack of '/bin/sh' makes device not bootable
>
> One solution is to use 'update-alternatives' script for handling that. But 
> this is 'egg & chicken' problem because 'u-a' is shell script. So far my 
> temporary solution is creation of 'bash-sh' package which symlinks '/bin/bash' 
> in post install script and in pre remove symlinks it to busybox. It is not 
> ideal but I needed something to get it working.
>
> 3. lack of '/etc/init.d/hwclock.sh'
>
> We provide it with BusyBox package, Debian has own one in util-linux(-ng) 
> package. I am planning to strip Debian one from log functions and test it.
>
> 4. lack of 'start-stop-daemon'
>
> So far I am using one from 'dpkg' but not extracted it to separate package.
>
> 5. 'adduser' is from 'tinylogin'
>
> We can not use Debian one because it is written in Perl. 'useradd' comes from 
> 'shadow' package. There are few versions of 'adduser' command in contrib/ 
> directory of shadow sources - 'adduser.sh' one looks simplest.
>
> Tinylogin should be dropped in OE anyway in favour of BusyBox (but that's 
> other story).
>
> Will write more when will remind them.
>
> Regards, 
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel


-- 
Martyn Welch (Principal Software Engineer)   |   Registered in England and
GE Intelligent Platforms                     |   Wales (3828642) at 100
T +44(0)127322748                            |   Barbirolli Square, Manchester,
E martyn.welch@ge.com                        |   M2 3AB  VAT:GB 927559189




      parent reply	other threads:[~2010-03-22  8:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19 16:52 [RFC] Rootfs without busybox in it Marcin Juszkiewicz
2010-03-19 17:00 ` Marcin Juszkiewicz
2010-03-22  8:33 ` Martyn Welch [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=4BA72B57.9050807@ge.com \
    --to=martyn.welch@ge.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox