Arm-dev December 2015

arm-dev@lists.centos.org

21 participants
33 discussions

selinux messages during selinux-policy update
by Robert Moskowitz 22 Dec '15

22 Dec '15

I ran yum update via an ssh session and saw the updated included: selinux-policy.noarch 0:3.13.1-60.el7 selinux-policy-targeted.noarch 0:3.13.1-60.el7 Then on my serial console I see: [41323.407978] SELinux: Class netlink_iscsi_socket not defined in policy. [41323.414925] SELinux: Class netlink_fib_lookup_socket not defined in policy. [41323.422242] SELinux: Class netlink_connector_socket not defined in policy. [41323.429483] SELinux: Class netlink_netfilter_socket not defined in policy. [41323.436736] SELinux: Class netlink_generic_socket not defined in policy. [41323.443793] SELinux: Class netlink_scsitransport_socket not defined in policy. [41323.451346] SELinux: Class netlink_rdma_socket not defined in policy. [41323.458115] SELinux: Class netlink_crypto_socket not defined in policy. [41323.465102] SELinux: Permission audit_read in class capability2 not defined in policy. [41323.473425] SELinux: Class binder not defined in policy. [41323.479019] SELinux: the above unknown classes and permissions will be allowed [41638.997450] Ebtables v2.0 unregistered [41641.121256] nf_conntrack version 0.5.0 (15901 buckets, 63604 max) [41641.191453] ip6_tables: (C) 2000-2006 Netfilter Core Team [41641.449223] Ebtables v2.0 registered Is this just 'noise' as there are things not in the armv7 build?

1 1

Nits for the Wiki
by Robert Moskowitz 22 Dec '15

22 Dec '15

Under Supported Boards: Cubietruck Add: Sata boot VGA output Not working: Integrated Bluetooth OTG (only regular USB works) Unteseted: Sound (I think this also does not work) Add Cubieboard2 as supported board. :) Unpacking on my Fedora system, the card is /dev/sdb, sometimes /dev/sdc Selinux enforcing at firstboot for Cubieboards Mount both partitions after dd step. vi /run/media/userid/fa926fa0-ddcb-47ea-9731-ea5c92d9f959/extlinux/extlinux.conf vi /run/media/userid/770af0f9-c7d9-4ae9-b024-1ba3c78d7550/etc/sysconfig/selinux touch /run/media/userid/770af0f9-c7d9-4ae9-b024-1ba3c78d7550/.autorelabel UUID will change with each image boot. userid is logged in user vi, make changes as specified. It would be neat if someone could work out how to use sed for these changes so they can be scripted. Similar for resize. Or for resize: echo ", +" | sudo sfdisk -N 3 "$MEDIA" sudo fsck.ext4 -fy "$ROOTPART" sudo partprobe "$MEDIA" sudo resize2fs "$ROOTPART" where $MEDIA=/dev/_____ $ROOTPART=["${MEDIA}p3"|"${MEDIA}3"] (depending on system) This is from the fedora-arm-installer rpm

1 0

new target c71511 created on the plague build farm
by Fabian Arrotin 22 Dec '15

22 Dec '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 FWIW, I've created the c71511-pass-1 target/repodir for the distributed build farm, and the current status is the following - - waiting for gcc to finish - - then rebuilding glibc - - then enqueing all the other packages I've adapted the .sql and generated html reports on http://armv7.dev.centos.org/ so that you can have a look if you're interested. Cheers, - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlZPUV8ACgkQnVkHo1a+xU5fxQCfYlH8qMBeJjSxquRXBRNa6eGN TWcAn1uzcyszAZr5jQwaw4p1fq6rtrRz =pqA3 -----END PGP SIGNATURE-----

5 14

Fixing the timestamp on files dated 1970-01-01
by Robert Moskowitz 21 Dec '15

21 Dec '15

First, I just tested seting up for switching to selinux enforcing and resizing during firstboot by making the various changes before first boot. I think it went through 2 reboots, but my Cubieboard2 is up and running with selinux enforcing and the rootfs resized to max for the mSD card. The first step I did after logging in was to use the 'date' command to fix the date, no chrony yet. Even so, a number of files are dated 1970-01-01; 9 files and 2 directories (one with a file) in /var/log/ Do any of these files need to be set with a more current timestamp? I once had problems with logrotate with a file date too old. I won't be able to replicate that event until I let this build run over the weekend with logwatch and logrotate installed. This problem is a basic one for this cards unless there is a way, prior to firstboot to configure chrony to read a time during firstboot, prior to these files being set. So I THINK this matters sometimes (logrotate, to be retested). What can be done for it?

1 0

How to extract the sources from a src.rpm
by Robert Moskowitz 21 Dec '15

21 Dec '15

I want to look at what is in the fedora-arm-installer to compare it with what I have been using without installing it. So I found the src.rpm at http://mirrors.kernel.org/fedora/releases/23/Everything/source/SRPMS/f/fedo… 'all' I want to do is in some directory pull out all the sources to look at. All experience I have with working with src.rpm stuff is probably 5+ years old and the brain is just too filled with other cruft, so I am asking just a little guidance here. If I can figure this out, I can perhaps help Fabian easily add lots of other boards.

3 4

We need to consider system time
by Robert Moskowitz 20 Dec '15

20 Dec '15

Most armv7 boards lack a battery to maintain system time. On firstboot they come up a zero time. This results in the initial log files (and other key files) to have a zero date: # ls /var/log/ -lst total 260 84 -rw-------. 1 root root 82722 Dec 19 21:45 messages 8 -rw-------. 1 root root 4889 Dec 18 16:27 secure 16 -rw-------. 1 root root 14517 Dec 18 16:01 cron 4 drwx------. 2 root root 4096 Dec 18 00:38 httpd 24 -rw-------. 1 root root 19279 Dec 18 00:37 yum.log 0 -rw-------. 1 root root 0 Dec 3 09:07 spooler 0 -rw-------. 1 root root 0 Dec 3 09:05 tallylog 4 drwx------. 2 root root 4096 May 28 2015 ppp 4 -rw-------. 1 root utmp 1152 Dec 31 1969 btmp 16 -rw-rw-r--. 1 root utmp 13824 Dec 31 1969 wtmp 4 -rw-------. 1 root root 200 Dec 31 1969 maillog 28 -rw-r--r--. 1 root root 292292 Dec 31 1969 lastlog 4 drwxr-xr-x. 2 root root 4096 Dec 31 1969 tuned 4 -rw-r--r--. 1 root root 120 Dec 31 1969 wpa_supplicant.log 4 drwxr-x---. 2 root root 4096 Dec 31 1969 audit 8 -rw-r--r--. 1 root root 8180 Dec 31 1969 boot.log 24 -rw-r--r--. 1 root root 23322 Dec 31 1969 dmesg 24 -rw-r--r--. 1 root root 23322 Dec 31 1969 dmesg.old Logwatch will have problems with these files (or that has been my prior experience). I suspect other services will have problems with such 'old' files on the system. First we need to select the time management service: ntp or timesync (I think I got this service naed correctly)? Fedora is using timesync and gets the current proper time from the network shortly after bootup. But there are some problems with this that are not so much an issue for a desktop, but are for a server. The firstboot timestamping problem I show above still occurs. Fedora has a later version of timesync that has this function. The version in Centos7 does not. What happens when a server restarts after a power outage, but before the external network access is available? For some time the system runs with time zero+. Here is what I am thinking as the way to address this: The time services have the ability to read a file for a date hint if the date is less than some set time, or that is what I understand. So add to the centos-arm-installer script (to be made for the fedora-arm-installer script) a set to get the date from the installing system and pushing it into the proper place of the centos7-arm image. Now at first boot, the system SHOULD come up with this date which is at least a good start that will tend to not be too stale. Next this date file should be updated through some automatic process so in the event that a system is turned off then reboots, it comes up with a rather good start time. I don't know what would be a good way to do this on Centos7. I can search back in my various discussions on this subject on a couple of lists. But there are people here that I hope are better able to make the design decisions needed so that our Centos7-armv7 systems have good time.

2 4

Centos-arm-installer
by Robert Moskowitz 20 Dec '15

20 Dec '15

Take the fedora-arm-installer rpm and install it and use it! The image you work from MUST have /usr/share/uboot The list of supported boards is in the board.d directory in fedora-arm-installer. Lots of boards supported. But NOT RPi2! I have to sign off now.

1 1

Sharing experiences running a mail server on a Cubetruck
by Robert Moskowitz 20 Dec '15

20 Dec '15

I have indicated that I have been running my mail server on a Cubietruck. It is running well enough for the past 270+ days since last boot. It supports 4 domains and receives ~5K messages per day, most spam. There are around a dozen users of this server. So not a big server, but what may be common for in a SOHO environment. My one complaint is how the anti-virus scanning software can temporarily tie up both cores. This is sometimes noticable when I (or one of the other users) send an email (via imap - dovecot) and wait frm some seconds until the message starts to upload. Since getting mail is typically a background function, delays caused by big anti-virus scans don't show. Same with the actual receiving and sending of mail by postfix. So I would recommend using a 4 core board, like the Wandboard, and somehow limiting the anti-virus software to 3 of the cores so one is available for actual mail work. I don't know how to limit services to specific cores so this would work. I suppose that even on the Cubietruck, you could limit the anti-virus to one of the cores. Perhaps Cubietech will actually come out with their 4 core server board as they have hinted at on their site, and we will quickly have a uboot to support it. Until then the Wandboard looks really good (and I think there is a BananaPi or OrangePi that is a 4 core with sata). Of course it may be once I get Centos7 running with this software mix, I will be pleasantly supprised that things are better scheduled so that imap uploads do not get held up by other tasks like anit-virus scanning of big attachments. Or someone here will show me a simple way to change service priorities to get things working better. I think this is the only real performance issue I have on my server. But then I have not tested DANE yet either...

1 0

Fwd: [CentOS-announce] Release for CentOS AltArch 7 (1511)
by Fabian Arrotin 20 Dec '15

20 Dec '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In case some people wouldn't be subscribed to the centos-announce list ;-) - -------- Forwarded Message -------- Subject: [CentOS-announce] Release for CentOS AltArch 7 (1511) on x86_64 Date: Sat, 19 Dec 2015 00:47:23 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Reply-To: centos(a)centos.org To: CentOS Announcements List <centos-announce(a)centos.org> I would like to announce the general availability of the following CentOS AltArch 7 Releases: * CentOS AltArch 7 (1511) for i686 * CentOS AltArch UserLand 7 (1511) for Armhfp * CentOS AltArch 7 (1511) for PowerPC64 (TechPreview) * CentOS AltArch 7 (1511) for PowerPC8 LE (TechPreview) We anticipate CentOS AltArch 7 (1511) for Aarch64 will be ready for release within the coming days, and will be announced independently. The CentOS AltArch SIG is a group of people working to build alternative architecture support derived from CentOS Linux's sources. You can find more details about the AltArch group at https://wiki.centos.org/SpecialInterestGroup/AltArch including details on how to get involved and ways to get help for architecture specific issues. Releases under the AltArch SIG are hosted at http://mirror.centos.org/altarch/ and available from external mirrors via rsync, http, ftp as usual, however under the /altarch/ path. Yum configs shipped in the altarch builds points at mirror.centos.org instead of mirrorlist or the external mirrors, as we are still working through the mechanics to facilitate the wider mirrorlist process. We hope to have this in place within the next 2 months, and updates to the yum configs will be issued, when ready, via an updated centos-release rpm. We are hosting a CentOS Dojo in Brussels, Belgium on the 29th Jan 2016. Lots of the key people working on the AltArch builds will be present there and it would be a great forum to engage with these groups. You can get the details for the event at https://wiki.centos.org/Events/Dojo/Brussels2016 including the registration links. In order to bootstrap these builds, we have turned on direct downloads of this content from mirror.centos.org. We do encourage people with the capacity to help seed with external mirrors. Details on howto run a CentOS Mirror are available at https://wiki.centos.org/HowTos/CreatePublicMirrors A key part of our AltArch plans is to make resources available to all the other SIG's in the CentOS environment, so they are able to build, test, deliver their content for these architectures. We are working on setting things up, and hope to start rolling out altarch support for https://cbs.centos.org/ in the first quarter of 2016. If you are engaged in any of the SIGs and would like to find out more details, please come along to our buildsystems meeting that takes place on Mondays in #centos-devel on irc.freenode.net. Details on this meeting and the other SIG meetings can be found in our community meetings calendar published at https://www.centos.org/community/calendar/ . Bug reports and feedback about specific packages should be filed at https://bugs.centos.org/ against the relevant package name, for project CentOS Linux 7, in the same manner as you would for x86_64. However, do mention the architecture as applicable. - -------- CentOS AltArch 7 (1511) for i686 : This architecture build supports 32-bit Intel/AMD x86 machines and 32 bit IOT x86 boards. SIG Notes: https://wiki.centos.org/SpecialInterestGroup/AltArch/i386 * CentOS-7-i386-DVD-1511.iso sha256sum : 6af64d8371ed8fb95a56c99530f0dc3eb287e58f72c009c686db0fb80c39f83f direct link : http://mirror.centos.org/altarch/7/isos/i386/CentOS-7-i386-DVD-1511.iso * CentOS-7-i386-Everything-1511.iso sha256sum : 918e0ade9f642c93531c414defeecfc9b2c2a9589d57642d690e46e42b0af82a direct link : http://mirror.centos.org/altarch/7/isos/i386/CentOS-7-i386-Everything-1511.… * CentOS-7-i386-LiveGNOME-1511.iso sha256sum : a03af3c7f6c75c74e1da5d1551ceaf5922427762c5cd6503f4f5e972737134ed direct link : http://mirror.centos.org/altarch/7/isos/i386/CentOS-7-i386-LiveGNOME-1511.i… * CentOS-7-i386-LiveKDE-1511.iso sha256sum : 9fdef81423b872c361bac3ac55718822b4420de1645a4da8d7a255ae500965fc direct link : http://mirror.centos.org/altarch/7/isos/i386/CentOS-7-i386-LiveKDE-1511.iso * CentOS-7-i386-Minimal-1511.iso sha256sum : df6edebec370bdee59e67eb70fab7ddc2fcf4c437803ca9e3213552b3908c4e1 direct link : http://mirror.centos.org/altarch/7/isos/i386/CentOS-7-i386-Minimal-1511.iso * CentOS-7-i386-NetInstall-1511.iso sha256sum : b106a0c13c86db86aaf821b66da1119063479e8776b8711dbbd35042b16bfd6d direct link : http://mirror.centos.org/altarch/7/isos/i386/CentOS-7-i386-NetInstall-1511.… - -------- CentOS AltArch UserLand 7 (1511) for Armhfp : This architecture build delivers support for ARMv7hl devices including the Raspberry pi2, Cubie Truck, Bananapi and similar hardware. SIG Notes: https://wiki.centos.org/SpecialInterestGroup/AltArch/Arm32 The armhfp build is delivered as a userland build, implying that kernel and bootloader delivered is not derived from the CentOS Linux 7 distro, but comes from either an upstream kernel.org mainline kernel or is a vendor supported kernel for their own hardware piece. As such, the Armhfp build does not aim to deliver a complete feature set, and is labelled as a UserLand release. There are also no installer images delivered for this architecture. The images shipped are ready to run and are board specific. While there is plenty of desktop and X related support available, our focus for these builds has been towards the server and IoT roles. We have a dedicated mailing list for the ARM ports ( both Armhfp and Aarch64 ) at https://lists.centos.org/mailman/listinfo/arm-dev ; questions specific to these builds and images should be posted there. * CentOS-Userland-7-armv7hl-Minimal-1511-BananaPi.img.xz sha256sum : d461144b471434a275268e85828def38c09e265da24b71d2f10771d264532368 direct link : http://mirror.centos.org/altarch/7/isos/armhfp/CentOS-Userland-7-armv7hl-Mi… * CentOS-Userland-7-armv7hl-Minimal-1511-CubieTruck.img.xz sha256sum : 17c3944429ac323c636ee955062d8177219f397fea4416dca87ca19092b646ec direct link : http://mirror.centos.org/altarch/7/isos/armhfp/CentOS-Userland-7-armv7hl-Mi… *CentOS-Userland-7-armv7hl-Minimal-1511-RaspberryPi2.img.xz sha256sum : 05e8c58cd837b90c0ab423b3730ee20ad185e19f346f531d3717c51358ea72cf direct link : http://mirror.centos.org/altarch/7/isos/armhfp/CentOS-Userland-7-armv7hl-Mi… - -------- CentOS AltArch 7 (1511) for PowerPC64 (TechPreview) : This architecture is for 64-bit IBM POWER7 machines using big endian byte ordering. We are marking this as a Tech Preview release, as it needs wider testing before it can be adopted as a GA release. SIG Notes: https://wiki.centos.org/SpecialInterestGroup/AltArch/ppc64 * CentOS-7-AltArch-ppc64-Everything-1511.iso sha256sum : 40ce665db62483a044a6d1a4996b2d5b507eb7f43c5e7846116dbd72e9e64e6a direct link : http://mirror.centos.org/altarch/7/isos/ppc64/CentOS-7-AltArch-ppc64-Everyt… * CentOS-7-AltArch-ppc64-NetInstall-1511.iso sha256sum : 46715a965f98901fabed13076aba879c32dd51b7bab63fa035b61a5b051f0b04 direct link : http://mirror.centos.org/altarch/7/isos/ppc64/CentOS-7-AltArch-ppc64-NetIns… - -------- CentOS AltArch 7 (1511) for PowerPC8 LE (TechPreview) : This architecture is for 64-bit IBM POWER8 machines using little endian byte ordering. We are marking this as a Tech Preview release, as it needs wider testing before it can be adopted as a GA release. SIG Notes: https://wiki.centos.org/SpecialInterestGroup/AltArch/ppc64le * CentOS-7-AltArch-ppc64le-Everything-1511.iso sha256sum : 713ea707eea4eb75d7ff27648e6e3a4e97738bc3b2b274d1e9dc629fe537a170 direct link : http://mirror.centos.org/altarch/7/isos/ppc64le/CentOS-7-AltArch-ppc64le-Ev… * CentOS-7-AltArch-ppc64le-NetInstall-1511.iso sha256sum : fa7c5f504e56ad9115b820b1cf6650e6c20c6ca6224b155ef0c12e1be8e8f666 direct link : http://mirror.centos.org/altarch/7/isos/ppc64le/CentOS-7-AltArch-ppc64le-Ne… - -------- I'd like to thank everyone involved in this process. We have come a long way down the route from the initial plans of getting the AltArch project bootstrapped, and its only down to the dedciated efforts from the people involved in this process that we are able to deliver support for five new architectures. I also want to take this opportunity to point out that we run an office hours forum, twice a week. Details are available at https://www.centos.org/community/calendar/#Karanbir_Singh_Office_Hours , please feel free to stop by and say hi. We welcome comments and questions around pretty much anything / everything relevant to the CentOS community. enjoy! - -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlZ1O7EACgkQnVkHo1a+xU4wTACfXYWbQc6HeHBgZGeRWB5CDupw sSEAn1uc1Tw2Zkn/AoLSnh8ad9c4cugv =V31D -----END PGP SIGNATURE-----

2 1

Supporting the Cubieboard2 and lots other boards as Fedora does
by Robert Moskowitz 17 Dec '15

17 Dec '15

I kind of assumed that there would be a /usr/share/uboot/ dir with all the u-boot-sunxi-with-spl.bin and I could just dd the Cubieboard2 uboot with bs=1024 seek 8, but no such directory. And I can't find a Fedora-arm image that has the 2015-10 uboot. Actually it would probably be in a Rawhide image, as F23 has 2015-09 and current Rawhide has 2016-01. So in your next image, include all of the uboots, or a least a lot more than none. Then we can take the Fedora-installer (which is now an rpm to install on a Fedora workstation, use to be a downloadable zip. Ask Paul Whalen, its author where it is these days) and pretty much use it as is. At least point me to the Cubieboard2 uboot 2015-10 and I will give it a test spin. And, yes RPi2 has its own set of differences...

2 6

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Arm-dev December 2015