Hi Jacek, You should not replace them with generic equivalents, you should replace them with your own equivalent packages (e.g. MYDISTRO-release and MYDISTRO-logos packages). (Get the src.rpm of the generic packages and create your own ones based on them). *Jacek Furmankiewicz <jacek99(a)gmail.com&gt; <jacek99(a)gmail.com&gt;* wrote on Fri, 8 Jun 2012 10:09:57 -0400: As per Fedora trademarks, I removed all the fedora logos, release notes, icons, etc and replaced them with the generic equivalents. However, this causes the word 'Generic' to appear in multiple places: a) 'Generic 17' on the boot up screen b) 'Generic Installer' in Anaconda and there are probably a few more that I haven't noticed. What is the recommended approach to replace all the references to 'Generic' with my actual remix name and what are all the files I need to update / override, etc? Thanks Jacek _______________________________________________ remixes mailing listremixes@lists.fedoraproject.orghttps://admin.fedoraproject.org/mailman/listinfo/remixes _______________________________________________ remixes mailing list remixes(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/remixes

On 09/06/12 04:16, Jacek Furmankiewicz wrote: > Does that mean I should create my own repo? > Or should I just create an RPM, copy it into the ISO using %post --nochroot > and then install it via rpm -ivh instead the %post section? > > What is the best recommended approach? Probably your own repo, although you _could_ just make a local one on your machine and add it to your list of repos in the kickstart file. It's the same as others, just using the file protocol, like: repo --name="Jacek" --baseurl=file:///home/jacket/myrepo/x86_64/ This way the rpm will just automatically get installed. -c _______________________________________________ remixes mailing list remixes(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/remixes

On 10/06/12 02:27, Jacek Furmankiewicz wrote: > Thanks, I am going to look into that soon. > > For now here is my .ks file, I would appreciate if someone could have a > quick look and verify I am not > doing anything particularly stupid: > https://github.com/jacek99/linux-iodine/blob/master/iodine-livecd.ks Looks pretty good, but a few things which you can take or leave. You might want to specify the architecture in your kickstart (and have another for 32bit), that you can build for both archs. You don't need 32bit Adobe repo for 64bit systems any more. You might want to also copy the .repo files into the resulting system (chromium, adobe) into the resulting system, otherwise your users won't get any updates for those programs. They should get rpmfusion and livna because you install the release. I could be wrong, but I thought livna wasn't really used any more? It might not be necessary... As for branding, you might want to also set your branding in: /etc/system-release-cpe /etc/issue /etc/issue.net Setting defaults in /etc/skel will only apply to when users create new accounts. You might want to see if there's a way that you can set xfce defaults outside of this. And finally, keep in mind that any config files you edit directly might be changed back if an update comes out - generic rpms are unlikely but it would mean that your distro loses its branding. So maybe consider your own repo (or at least rpms) where they replace generic rpms, that way they won't be overridden. I think I already mentioned how to do this on the list, but if you need more pointers let us know. In the mean time: http://fedoraproject.org/wiki/How_to_create_an_RPM_package > > And here's a preview of the current version: > https://github.com/jacek99/linux-iodine/raw/master/docs/screenshots/liveu... > > As you can see a very traditional, old-school desktop distro :-) Nice :-) Time to build and start testing! -c _______________________________________________ remixes mailing list remixes(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/remixes