dan at danny.cz
Tue Jan 20 12:48:39 UTC 2009
David Huff píše v Po 19. 01. 2009 v 17:36 -0500:
> One of the biggest areas of overlap between the server sig and thincrust
> is in a minimum package set definition that can be extended for
> different needs/applications.
> Thincrust already includes an official Fedora spin, the AOS, which is
> hosted in the "spin kickstart pool". The AOS is basically a
> kickstart file describing a minimal appliance OS that includes: the
> kernel, yum, dns, grub, and se-linux, all working on start-up.
> The first cut of the AOS was built by removing everything, ie. not
> including core or base, and adding the packages we needed. We also
> tired to exclude extra packages that got brought in as deps. This
> produces an disk image of 140 packages and is ~360M.
> While I am not saying this is the prettiest and/or the best approach, it
> was a quick way of producing a working appliance definition with a
> relatively small foot print using the current tools.
> Ideally any "Server spin" would be extensions of this minimum OS
> definition. I would love to see the the AOS definition evolve to become
> a better and smaller minimum OS definition.
> I am in the process of defining the AOS requirements for the F-11
> Spin and would love to get some feedback from the server sig.
> I am looking for ideas/suggestion/opinions on what would be the best way
> of redefine the AOS into a smaller, more fine gained, minimum server
> definition. Something that can be easily be extended by others?
There is work done by Daniel Mach on more precise inter-package
dependencies and on package vs. comps groups assignment. That should
remove the need for manual package excludes. Or at least some of them.
More information about the server