Thanks, I am working on taking care of that. Learning the Fedora way as I go along, since I've been mostly an Ubuntu/Mint/Debian user prior to this.

Is it possible to have the same kickstart file for all architectures and just do some conditional directives?

e.g.

if arch = 32bit then
   repo ...
else
   repo
end

or you actually need to copy and maintain the same file twice with minor changes?

Also, what is a good place to host the ISO and torrent tracker?
Any recommendations would be welcome, based on past experience.

Jacek


On Sun, Jun 10, 2012 at 7:55 PM, Chris Smart <chris@kororaa.org> wrote:
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/liveuser.png
>
> As you can see a very traditional, old-school desktop distro :-)

Nice :-) Time to build and start testing!

-c
_______________________________________________
remixes mailing list
remixes@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/remixes