Skip to contentSkip to conversation

Dumping sysvinit

DISCUSSION Andy Pont 5 participants 11 messages Sep 15, 2015 – Sep 21, 2015 2 messages not in the archive

lore
Share & tools
lore

Andy Pont

author
#0 lore raw

Hello,

Bit of a newbie question (probably) but what is the easiest way to dump sysvinit and use Busybox init in a core-image-minimal image?

Thanks,

Andy.

#1 lore raw
Quoted 4 lines · Andy Pont

Hello,

Bit of a newbie question (probably) but what is the easiest way to dump sysvinit and use Busybox init in a core-image-minimal image?

It has been a while since I've done this. But unless things have changed dramatically. You will need to define your own custom image.

One that does not include the sysvinit component or base initscripts. You will then have to provide your own base initscripts for your system to startup and function. (You might be able to copy some from the initscripts, but many expect the sysvinit [or systemd] to be present on the device.)

You are moving into pure custom boot optimization and implementation at this point.

--Mark

Quoted 5 lines

Thanks,

Andy.

author
#2 lore raw

Mark wrote...

Quoted 5 lines
Quoted 2 lines

Bit of a newbie question (probably) but what is the easiest way to dump sysvinit and use Busybox init in a core-image-minimal image?

It has been a while since I've done this. But unless things have changed dramatically. You will need to define your own custom image.

On the basis that sounded like more hard work than I have time for I thought I would try switching to systemd. Following the instructions in the dev manual [1].

If I add the extra variables to build/conf/local.conf then with the machine type set to genericx86 I get this build error:

ERROR: Function failed: do_configure (log file is located at XXXXX/build/tmp/work/x86_64-linux/qemu-native/2.2.0-r1/temp/log.do_configure .1926)
ERROR: Logfile of failure stored in:
XXXXX/build/tmp/work/x86_64-linux/qemu-native/2.2.0-r1/temp/log.do_configure .1926
Log data follows:

| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function autotools_preconfigure
| DEBUG: Shell function autotools_preconfigure finished
| DEBUG: Executing python function autotools_copy_aclocals
| DEBUG: Python function autotools_copy_aclocals finished
| DEBUG: Executing shell function do_configure
| 
| ERROR: User requested feature sdl
|        configure was not able to find it.
|        Install SDL devel

I'm guessing that this is me being dim and that build/conf/local.conf isn't what the documentation refers to as "your distribution configuration file". Can someone point me in the right direction?

Thanks,

Andy.

[1]
http://www.yoctoproject.org/docs/1.8/dev-manual/dev-manual.html#selecting-an
-initialization-manager

#4 lore raw
In reply to a message not in the archive
Quoted 32 lines · Andy Pont

Mark wrote...

Quoted 4 lines
Quoted 2 lines

Bit of a newbie question (probably) but what is the easiest way to dump sysvinit and use Busybox init in a core-image-minimal image?

It has been a while since I've done this. But unless things have changed dramatically. You will need to define your own custom image.

On the basis that sounded like more hard work than I have time for I thought I would try switching to systemd. Following the instructions in the dev manual [1].

If I add the extra variables to build/conf/local.conf then with the machine type set to genericx86 I get this build error:

ERROR: Function failed: do_configure (log file is located at XXXXX/build/tmp/work/x86_64-linux/qemu-native/2.2.0-r1/temp/log.do_configure .1926)
ERROR: Logfile of failure stored in:
XXXXX/build/tmp/work/x86_64-linux/qemu-native/2.2.0-r1/temp/log.do_configure .1926
Log data follows:

| DEBUG: Executing python function sysroot_cleansstate
| DEBUG: Python function sysroot_cleansstate finished
| DEBUG: Executing shell function autotools_preconfigure
| DEBUG: Shell function autotools_preconfigure finished
| DEBUG: Executing python function autotools_copy_aclocals
| DEBUG: Python function autotools_copy_aclocals finished
| DEBUG: Executing shell function do_configure
| 
| ERROR: User requested feature sdl
|        configure was not able to find it.
|        Install SDL devel
Quoted 3 lines

I'm guessing that this is me being dim and that build/conf/local.conf isn't what the documentation refers to as "your distribution configuration file". Can someone point me in the right direction?

I think the qemu build is looking for your build machine's native SDL (or SDL-devel) so that the resulting qemu can run. Usually a conf/local.conf includes the following lines:

PACKAGECONFIG_append_pn-qemu-native = " sdl" PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl" ASSUME_PROVIDED += "libsdl-native"

I think if you remove/comment-out the last of those 3 lines or install your host's SDL-devel package you'll solve this issue (?)

#5 lore raw
Quoted 3 lines · Trevor Woerner

I think if you remove/comment-out the last of those 3 lines or install your host's SDL-devel package you'll solve this issue (?)

Yes, that's right. Either disable the graphical qemu support, or install the host's sdl-devel package so it can build.

Ross

author
#6 lore raw

Hello all,

Quoted 5 lines
Quoted 3 lines

I think if you remove/comment-out the last of those 3 lines or install your host's SDL-devel package you'll solve this issue (?)

Yes, that's right. Either disable the graphical qemu support, or install the host's sdl-devel package so it can build.

On my CentOS 6.7 host system running the package manager reports that SDL-devel is already installed:

# yum install SDL-devel
Package SDL-devel-1.2.14-6.el6.x86_64 already installed and latest version
Nothing to do

This is probably something to do with the fact that in order to get Fido to build I have to use the devtoolset-2.1 package to get a recent gcc version and it probably isn't aware of the standard SDL-devel libraries.

Commenting out just the last line of the 3 QEMU/SDL related lines throws out a couple of errors whereas removing all of them gives me a build.

Now to figure out why the tar.gz file for the root file system has grown from just under 3MiB to almost 15MiB!

Thanks for all the help and advice.

Andy.

#8 lore raw
In reply to a message not in the archive
Quoted 3 lines · Andy Pont

Now to figure out why the tar.gz file for the root file system has grown from just under 3MiB to almost 15MiB!

That would be systemd... it pulls in a lot of libraries that are fairly common on complex systems but on a minimal image less so.

Ross

author
#9 lore raw

Ross wrote...

Quoted 5 lines
Quoted 2 lines

Now to figure out why the tar.gz file for the root file system has grown from just under 3MiB to almost 15MiB!

That would be systemd... it pulls in a lot of libraries that are fairly common on complex systems but on a minimal image less so.

Back to plan A then, trying to figure out how to get Busybox init and mdev as the defaults in the image.

Thanks for the feedback!

Andy.

#10 lore raw
Quoted 9 lines · Andy Pont

Ross wrote...

Quoted 5 lines
Quoted 2 lines

Now to figure out why the tar.gz file for the root file system has grown from just under 3MiB to almost 15MiB!

That would be systemd... it pulls in a lot of libraries that are fairly common on complex systems but on a minimal image less so.

Back to plan A then, trying to figure out how to get Busybox init and mdev as the defaults in the image.

Create your own distro, here's an example that uses mdev:

https://github.com/topic-embedded-products/meta-topic/blob/master/conf/distro/tiny.conf

author
#11 lore raw

Hi Mike,

Quoted 7 lines
Quoted 1 line

Back to plan A then, trying to figure out how to get Busybox init and

mdev as the defaults in the image.

Create your own distro, here's an example that uses mdev:

https://github.com/topic-embedded-products/meta-
topic/blob/master/conf/distro/tiny.conf

Thanks for pointing me in the direction of this. I have cloned it and used it as the basis of my distro, tweaked it a bit and it is starting to behave how I want. There are a few anomalies that I haven't managed to figure out yet...

Despite having VIRTUAL-RUNTIME_initscripts = "" the root file system still contains /etc/rcX.d directories

On other embedded Linux projects that boot using Busybox init the /etc/init.d directory contained the individual service start and kill files e.g. S50-dropbear and K50-dropbear but I can't see how to make Yocto populate this directory in that form.

Thoughts and guidance from anyone would be much appreciated!

Andy.

#12 lore raw
Quoted 18 lines · Andy Pont

Hi Mike,

Quoted 7 lines
Quoted 1 line

Back to plan A then, trying to figure out how to get Busybox init and

mdev as the defaults in the image.

Create your own distro, here's an example that uses mdev:

https://github.com/topic-embedded-products/meta-
topic/blob/master/conf/distro/tiny.conf

Thanks for pointing me in the direction of this. I have cloned it and used it as the basis of my distro, tweaked it a bit and it is starting to behave how I want. There are a few anomalies that I haven't managed to figure out yet...

Despite having VIRTUAL-RUNTIME_initscripts = "" the root file system still contains /etc/rcX.d directories

Quoted 6 lines

On other embedded Linux projects that boot using Busybox init the /etc/init.d directory contained the individual service start and kill files e.g. S50-dropbear and K50-dropbear but I can't see how to make Yocto populate this directory in that form.

Thoughts and guidance from anyone would be much appreciated!

I didn't go as far as attempting to get rid of initscripts as well. I just patched the initscripts to remove the things I did not want in a do_install_append.

Many recipes will create /etc/rcX.d entries to start/stop things.

Kind regards,

Mike Looijmans
System Expert

TOPIC Embedded Products Eindhovenseweg 32-C, NL-5683 KH Best Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: [email protected]
Website: www.topicproducts.com

Please consider the environment before printing this e-mail