On 2015-07-23 09:49, Mario Costa wrote:
Hi all,
I’m using Red Sleeve 7.1 with my Raspberry Pi v1. I downloaded
raspi-redsleeve7.1-cli-0.4.img image.
Anyway, when I ran
# yum update
I found out that the repository trees were changed and I had to edit
the files accordingly.
I'll double-check, what the redsleeve-release file contains, but I
suspect it's to do with the images having been created before the
release was made. That also means the packages the images were made
from are not signed.
In addition to that, I noticed that the
Raspberry Pi specific files were listed under the development folder
and not the stable one.
My question is if it’s safe to use those files in a stable environment
(I’m trying to setup an install and forget server at home, hence the
choice of this distro with no huge package updates) or if I shouldn’t
be using the Raspberry PI repository at all (keeping the same kernel
and firmware files forever?).
The only difference at the moment is that the release packages are
signed. The packages in the el7-devel subtree should work; if they
don't, please do file a bug on http://bugs.redsleeve.org and we'll
see what we can do to fix it.
By the way, I was surprised to see that a very recent kernel was
included.
The recency of the kernel is going to be extremely dependant on
the hardware and the availability of mainline kernels for that
hardware. For example, on the Mk1 Samsung Chromebook we are
stuck with the heavily patched 3.4.0 kernel (which causes issues
with systemd, see the mailing list archives for details I posted
on that) since mainline doesn't fully work on it.
Gordan
_______________________________________________
users mailing list
[email protected]
http://lists.redsleeve.org/mailman/listinfo/users
