[ELDK] Creating small target rootfs in DENX

[Dave Rensberger]

OK I'll take a look at this.   I'm actually trying really hard to come
up with a way to do it that doesn't involve any modified RPMS.   My
tentative plan is to try to use the ELDK to build all of the completely
generic (i.e. unmodified) parts of my target Linux distro, and then add
all of my companies customized components as a separate step.  

If possible, I'd like to keep the customized part of my target build
process RPM free.   I understand why the DENX distro is RPM based, but
for my own purposes, I've always found RPMs to be extremely awkward to
create and modify.  I also think that the complexity of RPM is
unwarranted in my company's final product, since we won't be delivering
software to our customer as individual components.

I'm fairly confident that I'll find a decent way to do this, but I'd
welcome any suggestions from anyone else who's tried to do something
similar.

--Dave  


-----Original Message-----
From: Phil Terry [mailto:pterry at micromemory.com] 
Sent: Friday, May 23, 2008 3:07 PM
To: Dave Rensberger
Cc: pterry at vmetro.com; eldk at lists.denx.de
Subject: RE: [ELDK] Creating small target rootfs in DENX

On Fri, 2008-05-23 at 14:48 -0400, Dave Rensberger wrote:
> OK. I saw that, but the documentation that I read had lead me to
believe
> that SELF was nothing more than a collection of small example
rootfses.

Well thats what you want right? An example setup of how to create and
manage a subset installation to a rootfs which is absolutely minimal so
you can simply add to it.

You will need to edit the line in spec file which just copies in the
"dummy" application, a hello world shell script, with something more
substantial. 

In the source tree you edit the various *.list files which control the
subset of your "full install" tree which get copied in.

In the spec file you could either explicitly copy your application
executables, libraries and data files instead of the dummy or set up an
"application.list" mechanism as they use for the other stuff, or simply
edit the libraries and files list files which are already there to
include your application.

When you've done all that you simply rpmbuild a new src and binary rpm
so that your fellow developers and/or customers simply install your
version of the SELF rpms

SELF is an example of a package which you actually have to get in and
edit using the install of the src rpm, rpmbuild -bp, edit, rpmbuild -ba
etc.

Hope this is helping...

> I'll go back and read about it again.
> 
> --Dave
> 
> -----Original Message-----
> From: Phil Terry [mailto:pterry at micromemory.com] 
> Sent: Friday, May 23, 2008 2:29 PM
> To: Dave Rensberger
> Subject: Re: [ELDK] Creating small target rootfs in DENX
> 
> On Fri, 2008-05-23 at 13:04 -0400, Dave Rensberger wrote:
> > This is a multi-part message in MIME format.
> >  discussed or documented, but I haven't
> > been able to find any info on this topic.
> > 
> >  
> > 
> > My question regards how to create the subset of the default root
file
> > system generated by the ELDK "install" script that will be the
rootfs
> > resident on my target.   
> 
> I believe what your looking for is the SELF package in ELDK, install,
> edit to taste and install.
> 
> Simple Embedded Linux Filesystem (SELF)
> 
> Its not obvious, I missed for a long time then once I found it and
> realized what it was I couldn't work out why it wasn't obvious.... :-)
> 
> Cheers
> Phil
> 
> 
> 
> 
>