Ok, I see this epel-release in the epel1 repo that I installed via the wiki.
So I decide to install it, and it created an epel.repo.rpmnew file. I swicth around the files and try a 'yum update' and get:
epel/armhfp/metalink | 47 kB 00:00 Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=armhfp error was No repomd file
One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this:
....
File /var/cache/yum/armhfp/7/epel/metalink.xml does not exist
So I put everything back.
Robert, that file shouldn't be there, since our epel is actually a rebuild. I'll remove it
El 23/10/18 a las 19:42, Robert Moskowitz escribió:
Ok, I see this epel-release in the epel1 repo that I installed via the wiki.
So I decide to install it, and it created an epel.repo.rpmnew file. I swicth around the files and try a 'yum update' and get:
epel/armhfp/metalink | 47 kB 00:00 Could not parse metalink https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=armhfp error was No repomd file
One of the configured repositories failed (Unknown), and yum doesn't have enough cached data to continue. At this point the only safe thing yum can do is fail. There are a few ways to work "fix" this:
....
File /var/cache/yum/armhfp/7/epel/metalink.xml does not exist
So I put everything back.
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
I found this old email about epel, it said that the epel repos were 'broken' ?
when I tried to install it with 'yum install epel-release' it says it's not available.
Is there a different way to install it?
Ron
On 22/6/20 16:26, R C wrote:
I found this old email about epel, it said that the epel repos were 'broken' ?
when I tried to install it with 'yum install epel-release' it says it's not available.
Is there a different way to install it?
For c7 we have this https://wiki.centos.org/SpecialInterestGroup/AltArch/armhfp, but for c8, there's nothing yet
Ron
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Hi Pablo,
C7 is fine, that is what I am working with now.
thanks!
Ron
On 6/22/20 1:52 PM, Pablo Sebastián Greco wrote:
On 22/6/20 16:26, R C wrote:
I found this old email about epel, it said that the epel repos were 'broken' ?
when I tried to install it with 'yum install epel-release' it says it's not available.
Is there a different way to install it?
For c7 we have this https://wiki.centos.org/SpecialInterestGroup/AltArch/armhfp, but for c8, there's nothing yet
Ron
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Hello,
ownership/permissions on gpio device are like tis:
crw-------. 1 root root 254, 0 Jan 1 1970 gpiochip0 crw-------. 1 root root 254, 1 Jan 1 1970 gpiochip1 crw-------. 1 root root 254, 2 Jan 1 1970 gpiochip2 crw-------. 1 root root 246, 0 Jan 1 1970 gpiomem
while other device like ttys, are owned by root and "group owned" by tty, similar for video, disk, dialout etc.
wouldn't it be 'better' to have these gpio devices owned by root, "group owned" by a group other then root (gpio)?
(or did 'we' inherit that from further up/down the development chain?)
Ron
On 29/6/20 16:49, R C wrote:
Hello,
ownership/permissions on gpio device are like tis:
crw-------. 1 root root 254, 0 Jan 1 1970 gpiochip0 crw-------. 1 root root 254, 1 Jan 1 1970 gpiochip1 crw-------. 1 root root 254, 2 Jan 1 1970 gpiochip2 crw-------. 1 root root 246, 0 Jan 1 1970 gpiomem
while other device like ttys, are owned by root and "group owned" by tty, similar for video, disk, dialout etc.
wouldn't it be 'better' to have these gpio devices owned by root, "group owned" by a group other then root (gpio)?
(or did 'we' inherit that from further up/down the development chain?)
Yeap, that's inherited, I'm guessing you could write some udev rule to set the permissions you need (or even setfacl)
Ron
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Pablo.
On 6/30/20 5:35 AM, Pablo Sebastián Greco wrote:
On 29/6/20 16:49, R C wrote:
Hello,
ownership/permissions on gpio device are like tis:
crw-------. 1 root root 254, 0 Jan 1 1970 gpiochip0 crw-------. 1 root root 254, 1 Jan 1 1970 gpiochip1 crw-------. 1 root root 254, 2 Jan 1 1970 gpiochip2 crw-------. 1 root root 246, 0 Jan 1 1970 gpiomem
while other device like ttys, are owned by root and "group owned" by tty, similar for video, disk, dialout etc.
wouldn't it be 'better' to have these gpio devices owned by root, "group owned" by a group other then root (gpio)?
(or did 'we' inherit that from further up/down the development chain?)
Yeap, that's inherited, I'm guessing you could write some udev rule to set the permissions you need (or even setfacl)
I didn't even go that route, I just created a group, called gpio, added myself and the uid stuff is running under to it, changed the group permission on the devices to rw . That way a user that is in the gpio group can use the devices, it's easy and similar to how serial devices etc (by being a member of dialout) work
Would be convenient if the gpio devices in /dev could be treated the same, permission wise, as modem/ACM0-n etc.
Ron
Arm-dev mailing list Arm-dev@centos.org https://lists.centos.org/mailman/listinfo/arm-dev
Pablo.
-
Pablo Sebastián Greco -
R C -
Robert Moskowitz