Re: [yocto] Dumping sysvinit

2015-09-21 Thread Mike Looijmans
On 21-09-15 12:48, Andy Pont wrote: Hi Mike, 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

Re: [yocto] Dumping sysvinit

2015-09-21 Thread Andy Pont
Hi Mike, > > 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 pointin

Re: [yocto] Dumping sysvinit

2015-09-17 Thread Mike Looijmans
On 16-09-15 16:13, Andy Pont wrote: Ross wrote... 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.

Re: [yocto] Dumping sysvinit

2015-09-16 Thread Andy Pont
Ross wrote... > > 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, tryin

Re: [yocto] Dumping sysvinit

2015-09-16 Thread Burton, Ross
On 16 September 2015 at 10:24, Andy Pont wrote: > 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.

Re: [yocto] Dumping sysvinit

2015-09-16 Thread Andy Pont
Hello all, > > 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

Re: [yocto] Dumping sysvinit

2015-09-16 Thread Burton, Ross
On 15 September 2015 at 17:27, Trevor Woerner wrote: > 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

Re: [yocto] Dumping sysvinit

2015-09-15 Thread Trevor Woerner
On 09/15/15 12:03, Andy Pont wrote: > Mark wrote... > >>> 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

Re: [yocto] Dumping sysvinit

2015-09-15 Thread Andy Pont
Mark wrote... > > 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.

Re: [yocto] Dumping sysvinit

2015-09-15 Thread Mark Hatle
On 9/15/15 6:16 AM, Andy Pont wrote: > 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

[yocto] Dumping sysvinit

2015-09-15 Thread 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? Thanks, Andy. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto