Re: Building our own targets

Hi,

On Monday 22 January 2007 20:07, Kevin Fries wrote:
> On Mon, 2007-01-22 at 19:44 +0100, Rene Rebe wrote:
> > When you searched thru the T2 Handbook and the homepage HTML then
> > probably not yet. However we are currently overworkign the Handbook
> > radically and writing especially this target how-tos because it the whole
> > book will go into print this year.
>
> This explains why I am not really finding anything that matches what I
> am seeing in the $T2/target folder

The handbook, the english version anyway, will remain Open Source - so the 
first gaps of the historically grown handbook will be filled over one by one 
over the next weeks.

> > When you speak about uClibC and Busybox you should find the new rescue
> > target quite matching - it exactly does this.
>
> I refreshed my svn checkout this morning, but did not see t-resc there,
> only rescue... am I missing something?

Yeah - sorry for the confusion. T-Resc is rescue. T-Resc is just what we use 
as "advertising" name.

> > When you do not want a LiveCD but some pre-build ext2/squashfs the final
> > image creation can be just scripted at the end.
>
> Device will run from CF or DOC, but the final file system will consist
> of a series of unionfs layers, the majority of which will be either
> cramfs or squashfs based file systems.

I just did a simillar setup for a Linux based Info terminal. This overlaying 
is already in trunk as part of the gneric LiveCD code - even including 
detecting writeable ones and marking the unionfs dirs properly.

You can e.g. test it with the latest T-Resc version, just place additional 
files on the CD/Stick names:

live-*

They will be all loop mounted and unioned together with alphabetical sorting, 
and ro/rw marks as needed.

However be warned that I run into problems with multiple write branches with 
unionfs. In a tiny test-case it worked, but in the real system unionfs 
dead-locke (or so). Be sure to test if your unionfs setup works in production 
use.

> > If you run into an issue with the rescue target just ask about this
> > issues on the list and we can discuss them in detail (until the homepage
> > has this mentioned sections).
> >
> > Btw. Will your target be x86 or for a different architecture?
>
> Target at this time is X86 P4M based board, but we have also run through
> several ARM and XScale boards, and have not ruled them out for our final
> build.  The idea of T2 and its build system, coupled with a fast moving
> final target, is what makes this project so appealing to me.  I guess I
> am just getting impatient with the documentation, and need to slow down
> a bit, lol.

Just keep askign on the mailing list and/or bother us in the #t2 IRC channel. 
However you reach a wider audience on the mailing list, especially as it can 
be read asynchronously when a third of the world was asleep.

Yours,

-- 
  René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
  http://exactcode.de | http://t2-project.org | http://rene.rebe.name
  +49 (0)30 / 255 897 45

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
lists@xxxxxxxxxxxxxx with a subject of: unsubscribe t2