>> For all 'special' setups, we might just explain how to do that on the >> wiki. > > Perhaps. Unfortunately, a wiki article for that kind of thing would > be both generic and require device specific knowledge on part of the > user. For example, even if I have zfs-fuse-dracut module that works > for me, it would still require the use of an initrd, and since the > kernel will inevitably be a major unknown, it would rely on the user > being able to resolve an issues arising from that themselves. > >> In the end, it is not that difficult. Thinking about this, if we >> create a better comps.xml, we could instruct people to 'yum groupinstall >> base --installroot=xxx --config=yyy' instead of creating all kinds of >> tar.gz files. > > Doesn't that imply already having a running system?
A running linux system, but not necessarily ARM. For the image creation I do now something similar: - create partitions (either on a .img file or directly on SD) - format partitions - mount under /blah and /blah/boot - yum install a specific set of packages to /blah - some little tweaks (set password, enable chrony, etc) - done we could try to describe "cookbooks" on the wiki. So instead of an fixed image, people would always create something uptodate. Jacco _______________________________________________ users mailing list [email protected] http://lists.redsleeve.org/mailman/listinfo/users
