man, 29.11.2004 kl. 20.16 skrev Dirk Westfal:
On Monday 29 November 2004 18:49, Arangel Angov wrote:
> Dirk Westfal wrote:
...
> I'm very interested in this. I wanted to make a fedora 2 live cd for a
> few months now. The problem is, there is no proper documentation and all
> the scripts for making live cd's are buggy or not working. How did you
> do it? Any good documentation?
Well... 'good docu' for the livecd build-process ... that`s a very critical
point yet :)
I`m trying to create a set of scripts to facilitate the process, but it`s
still not very easy to get it right and 'end-user' doable.
It starts with package dependencies (it`s quite easy to end up with a 2,8 GB
install) and ends with mostly small things (some software that needs write
permission in /usr, missing symlinks, changes in system scripts etc.), that
can easely prevent a livecd -system from working.
I`ve automated most of the stuff using a shellscript that guides throught the
build-process in ~11 steps, and eleminated a lot of pitfalls by putting the
livecd-specific adjustments into rpm packages (the 'livecd- rpms' - included
in the 1.40 cd in /rpms folder).
All tools i use are currently included in a 'livecd-devel.tar.gz' in the
barebone image - they are working - at least for me - but there are still a
lot of loose ends, and it is not 'bullet-proof' enough to turn it loose as
single package.
My current approach for end-users is to provide a 'basic' image (the
'barebone') as working example that includes just yum and a few other tools
that can be 'remastered' into full working system or used as a 'base' for
own
systems.
(document:
http://www.linux4all.de/livecd/barebone/customization-1.1.htm )
Just wondering - all that with read-only root etc. - don't this project
share a lot of common goals (or at least technical ways to get there)
with the stateless project?