On 08/11/2010 02:25 AM, Martin Gracik wrote: > Well, what about making just an "english" install.img with language, > locales, and fonts just for english, but with everything else we need, > like a base system for everyone, and then provide some locales.img, > one for all locales, or more of them, like an "add-on" image, > which will get downloaded only if the user selects some other language? > > This still splits the install.img to more files, but I think the split > is more logical, and from the images creating perspective, I think > it would not be a mess to implement. > > Maybe we can also move some other stuff to an "add-on" image too. At least with syslinux (extlinux/isolinux/pxelinux) you can concatenate cpio base initrd's as they load, with the first being the base, and subsequent ones layering over what's there. This could be one approach to what your suggesting there: base.img + <additional language>.img and have some sort of all-language.img for people who want everything. The upside is where we are talking about this is going to be almost exclusively syslinux based boot loaders anyway so we can probably get away with a few of it's tricks to boot. > As I'm doing the imagemaking scripts, I'm always looking for a solution, > that will keep it nice and simple when creating the images. So from my > point of view, it would be best to do the split (if we do it) > based on package selection, as in "put all these packages to one image, > and these packages to other image, but don't mess around with single files". > > But this is talking about splitting the image again... Depends on if/why/how we are splitting it. Just setting the initrd's up to even have a base.img and a all-languages.img, the later that you can concatenate to a base.img might be an easy enough thing to test that it might be worthwhile. Just some thoughts anyway. - John 'Warthog9' Hawley > > -- > > Martin Gracik > > ----- "John Reiser" <jreiser@xxxxxxxxxxxx> wrote: > >>> I understand the problem about the magic growing initrd. I'm not >> sure >>> how we can address that (especially given our desire to use system >> stuff >> >> Produce an example that excludes most languages+locales, such as: >> 1) has exactly the six offical languages of the United Nations >> (Arabic, Chinese (Mandarin), English, French, Russian and >> Spanish: >> http://www.un.org/Depts/DGACM/faq_languages.htm) >> or 2) has the only the language+locale of your favorite developer. >> >> Such an initrd will be about 30% smaller. Advertise this cost >> of the "all languages" policy. The result might be support for >> a few editions (say, 4) that are restricted by language+locale >> in order to reduce size. >> >> -- >> >> _______________________________________________ >> Anaconda-devel-list mailing list >> Anaconda-devel-list@xxxxxxxxxx >> https://www.redhat.com/mailman/listinfo/anaconda-devel-list > > _______________________________________________ > Anaconda-devel-list mailing list > Anaconda-devel-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/anaconda-devel-list _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
