On Thu, Aug 07, 2008 at 11:41:46AM +1200, Martin Langhoff wrote: > 2008/8/7 Axel Thimm <Axel.Thimm@xxxxxxxxxx>: > > where this is briefly discussed. E.g. maybe OLPC only needs an > > extended setup package (the package's name is indeed "setup") where > > some key uids/gids are set and thus globally the same even if Fedora > > as upstream may be assigning them dynamically. > > Ah, that's a trick I had not thought about - an early-install package > that creates a list of accts on preset ids. And if that is > complemented with each packaging creating its accounts if they are > missing (in %pre) as outlined in the wikipage you linked to. > > Now, I had read the wikipage before, but not caught the full meaning > of the phrase that mentions "setup" in it -- well placed at the end of > a long paragraph, perhaps my confusion comes from not being a > dedicated enough reader :-) That's why I explicitely mentioned that "setup" is a package. :) > In-te-res-ting. > > Now what I need to learn are tricks to ensure an early install of my > custom setup pkg. Setup is probably the very first package that gets installed, other packages like "filesystem" or "basesystem" depend on it, so it's guaranteed that it will be before any other package with uid/gid necessities. E.g. for a spin or PXE install or even a plain Fedora install with an additional repo configured (during Fedora install you can enable any custom repo you like containing your own "setup" rpm) you are already done. -- Axel.Thimm at ATrpms.net
Attachment:
pgptPmLWHgmn2.pgp
Description: PGP signature
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
