[Sugar-devel] How big might a full install of Fedora Sugar be?

[Mathieu Bridon (bochecha)]

>>> What about doing a F11 GNOME install to a large USB drive, yum installing
>>> Sugar stuff, removing the unwanted bits, resizing the partitions to
>>> desirable size, and then dd ing that to a desirable USB stick (marked
>>> bootable) as a master img?
>>
>> And do that process again each time you want to release an updated image ?
>>
>> Use a kickstart file, create the master image with pungi, then let it
>> install itself automatically on the USB sticks.
>>
>> That's exactly what Sebastian has been doing with SoaS, except he
>> created live images when you want installed systems.
>
> For the non-fedora people....
>
> A kickstart file is a list of packages which you want to install.  You
> first create the kickstart file using a tool called pungi.  Then you
> put the kickstart file on your install DVD.  So, whenever you do an
> install with that dvd you get the package set defined in the kickstart
> file.

Just to be the boring pedantic guy who loves correcting people: you
actually first write the kickstart file (manually, or using
system-config-kickstart) and then feed it to pungi who will take all
the infos in the kickstart file and generate the isos.

But the rest of your message still holds true :)

> This is how the xs image is create.  The xs team takes a few standard
> rpm files and modify them to meet the usecases intended for the xs and
> stick those file in a xs repo.  Then they create a kickstart file
> listing the files that want to install.  To save space they really
> limit the required packages.  Then they tell kickstart to first in the
> xs repo and second in standard fedora repo for packages packages.
>
> There is a step of creating a special package to run post install
> configure scripts. But don't think too hard about that.... it is
> enough to make your head explode.
>
> So there is no 'set' size for an install
>
> hope that helps


----------

Mathieu Bridon (bochecha)