On 01/18/2016 07:56 PM, Peter Robinson wrote:
>> Hi All,
>> Just a heads up we've renamed fedora-arm-installer and moved it to a new
> So what do I download to get this new version? Last version was a nice rpm.
> I don't see an rpm at this site.
Using "dnf install" this is purely where to contribute new code, not
where to get the output, that is for standard rpm distribution
OK. So this is just where you are developing the code. You were
letting us all know this is happening, but it just so happens that it
has not been rolled up yet for rpm distribution:
# dnf install arm-image-installer
Last metadata expiration check performed 0:49:25 ago on Mon Jan 18
No package arm-image-installer available.
Error: Unable to find a match.
I will watch for this coming out.
>> The rename is so it's more generic so it can be reused by the CentOS
>> ARM project and anyone else who wishes to make use of it.
> I hope you are making progess with your colleagues over on Centos-arm for
> this. I have proposed this approach over there, but on the list, the
> builder was last pushing still to make an image per board. A unique image
> is needed for RPi2 due to the different kernel, but not the others. I have
> many a post there claiming how simple this installer approach would be.
> More on this use by Centos belongs on the Centos list, of course.
It is not my job to tell the people contributing to the CentOS ARMv7
project what to do with their images. I personally have more than
enough work to do (more work than I have hours available in a day) on
the Fedora ARM project so I have _ZERO_ interest in getting involved
in another project that duplicates a bunch of that work. I am more
than happy for that project to use the work Fedora has already done
over the past years, the lessons we've learnt to make their paths
easier. I have engaged with a bunch of people and will continue to do
so to answer questions and provide direction and suggestions but the
work is for them to do.
Since I AM doing both distros, I will continue my campaign over there.
I really get it that you have your hands full here. And appreciate all
you have done.
>> It's now hosted on pagure too so you can easily submit enhancements,
>> fixes, documentation pull requests.
> I am going to have to remember my FAS account...
> For those boards with sata (cuibes, wands?, linksprites?), you can put just
> the uboot on the mSD and the image on a USB connected sata. It does not
> hurt, it seems, to put the uboot on the sata, but obviously you ONLY want
> the uboot on the mSD. I did a variant of the script to have a 2nd media]
That's why "contributing" is for, I agree it's a useful use case, but
it's a minor one that not many people wish to do, it can actually be
done here with just the update-uboot script in the package to write
the mSD, and then just write the SATA device with the --target=none
I will have to look at the update-uboot script again. My problem
probably on not getting how to use it to build a uboot mSD.
And will contribute changes if needed.
> allowed for just the uboot, and sent that to Paul some months back. I don't
> believe Hans has uboot on NRAND on Cubies working yet. So a script that
> would take uboot from some local tree to mSD in addition to downloading from
> koji the lastest, might be nice.
Maybe you could contribute a pull request to the project with such a
feature, this isn't a thread to dump a list of features you want
others to do, it's a thread for people who wish to contribute
something other than requests for others.
I have seen this on the todo list. I have not seen it completed. There
is nothing I can or should do to get this done. When it works to put
uboot (and maybe some other partitions) on NDRAM, then it is time to
make any contributions for this set of scripts to put stuff there. Got
it, and will do my best in this direction.
And really, I am only suppose to allocate 1hr/dy on this to balance off
those projects that I get paid for.
take care and thanks.