Hi guys, Is there going to be 7.1 for Dreamplug boards too?
Thank you, ioan > On Sep 20, 2015, at 4:54 PM, Gordan Bobic <[email protected]> wrote: > > On 20/09/15 00:57, Jacco Ligthart wrote: >> On 19-09-15 22:10, Bjarne Saltbaek wrote: >>> Hi Jacco. >>> >>> On 19-09-2015 18:21, Jacco Ligthart wrote: >>>> All, >>>> >>>> recently I tried a fresh install of RSEL 7.1. I did not find it a good >>>> experience. There were many manual steps involved and I can imagine >>>> other people will give up on this experience. >>> Oh yes man, I almost gave up on making 7.1 work on my Raspberry Pi. So >>> many things had to be fiddled around :) >>>> >>>> So, we will need newer images. Making images has for me been an >>>> error-prone manual activity. hmm, error-prone is probably exaggerated, >>>> but the reproducibility is low. To make this more robust, I'd like to >>>> start using Mandar's "RootFS Build Factory" >>>> (https://github.com/mndar/rbf). For this to work nicely, we'll need a >>>> "core" group in our repo (comps.xml) and of course and idea of what we >>>> think is core :) >>> Good luck. I have tried and tried and tried and I cant get RBF >>> working. Not even with the CentOS 7 templates supplied. >>> And documentation is not very good. >> I just now tried rbf. For me it worked exactly as it supposed to do. I >> got a working image on the first try. (actually second try, in the first >> try I installed a rpi1 kernel for a rpi2 machine) >> interested in the .xml? >> >>> Why do not take core from upstream? >> Well, it is bound to have x86 specific things, things we don't like and >> it will miss things. (wireless tools for instance) >> >>> >>>> other things on my list of items to change: >>>> * EPEL repo is now difficult to find/configure >>> I am still working and playing with koji and epel building (see my >>> working efforts at >>> http://www.saltbaek.dk/dokuwiki/doku.php?id=koji:start ) >>> When it is completed it will build released epel's automatically. >>> SPEC's are stored in a git repository so I can add your patches). >>> RPM's will be signed automatically and made available in a yum repo. >> looking forward to see the result! >> >> Here my first iteration of a packagelist for core. >> I started with core form upstream, but removed: >> biosdevname >> btrfs-progs >> firewalld >> iprutils >> irqbalance >> kexec-tools >> policycoreutils >> selinux-policy-targeted >> tuned >> xfsprogs >> aic94xx-firmware >> bfa-firmware >> dracut-config-rescue >> ivtv-firmware >> iwl100-firmware >> iwl1000-firmware >> iwl105-firmware >> iwl135-firmware >> iwl2000-firmware >> iwl2030-firmware >> iwl3160-firmware >> iwl3945-firmware >> iwl4965-firmware >> iwl5000-firmware >> iwl5150-firmware >> iwl6000-firmware >> iwl6000g2a-firmware >> iwl6000g2b-firmware >> iwl6050-firmware >> iwl7260-firmware >> kernel-tools >> libertas-sd8686-firmware >> libertas-sd8787-firmware >> libertas-usb8388-firmware >> linux-firmware >> microcode_ctl >> NetworkManager-team >> ql2100-firmware >> ql2200-firmware >> ql23xx-firmware >> rdma >> dracut-config-generic >> dracut-fips >> dracut-fips-aesni >> dracut-network >> openssh-keycat >> selinux-policy-mls >> tboot >> (note: I wanted all firmware stuff to be board specific, therefore they >> are excluded from core) > > I'd keep firewalld and selinux related packages. > > Gordan > > _______________________________________________ > users mailing list > [email protected] > http://lists.redsleeve.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] http://lists.redsleeve.org/mailman/listinfo/users
