orion5x housekeeping
I was looking at debian-installer and thought it would be good to see if there are maintainers (and if not, at least users) for the orion5x devices we supposedly support. I see 3 classes of devices: 1) Linkstation: these were added by various people over the years but I don't think we had a formal maintainer in a long time. Roger Shimizu put in some effort recently but I'm not sure which devices he has to test. Looking at debian-installer, I see support for: * Buffalo Kurobox Pro: I know various Debian people had these. Are people still using these devices? Is Debian working? Is the installer working? * Buffalo Linkstation Mini (LS-WSGL): Roger pointed out that this was converted to Device Tree recently, so it's definitely broken in the installer in unstable. Adapting the build scripts to append the DT blob is easy, but can anyone test? * Buffalo Linkstation Pro/Live: no idea * Buffalo Linkstation Live V3 (LS-CHL): no idea. Any comments? Roger mentioned u-boot restrictions on the size of the kernel that we broke. Does that apply to all Linkstation devices? Do we have to drop support for all of them in stretch? 2) HP Media Vault mv2120: this used to work fine and had users but I haven't heard anything recently. Any users? 3) QNAP TS-109/TS-209 and QNAP TS-409: we dropped installer support in 2011 due to the installer ramdisk being too large to fit in flash, but I brought support back to life in the last few days thanks to XZ compression and some other changes. There's a problem with qcontrol but otherwise they work fine. I'm happy to take care of them for stretch. [and I should add 4) D-Link DNS-323: the Debian kernel team dropped support due to size limits and this is not coming back.] -- Martin Michlmayr http://www.cyrius.com/
banana pro | bananian does boot, debian armhf-netinst not.
Hello, # The versions used: bananian version: 15.08 (released 2015-08-22) debian version: 8.2.0 armhf-netinst (2015-09-06 16:24) Accoding to http://www.debian.org/releases/stable/armhf/ch02s01.html.en the armhf architecture is the correct one. command for both: sudo dd bs=4M if=[path]/[imagename] of=/dev/sde && sync => bananian works, debian not. It simplay doesn't show any reaction => What is my mistake?
security labeling handle: No such file or directory (what file?)
With my Debian Kit installation on a phone (Motorola Mote-e2, Android 5.02) I seem to be having selinux problems. I've read part of Gentoo's selinux tutorial at https://wiki.gentoo.org/wiki/SELinux/Tutorials and I'm trying to figure this out. Did: setenforce permissive root@gsm:/# getenforce Permissive root@gsm:/# apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following extra packages will be installed: binutils Suggested packages: binutils-doc The following NEW packages will be installed: binutils 0 upgraded, 1 newly installed, 0 to remove and 28 not upgraded. 3 not fully installed or removed. Need to get 0 B/3542 kB of archives. After this operation, 17.8 MB of additional disk space will be used. Do you want to continue? [Y/n] y dpkg: error processing archive /var/cache/apt/archives/binutils_2.25-5_armhf.deb (--unpack): cannot get security labeling handle: No such file or directory Errors were encountered while processing: /var/cache/apt/archives/binutils_2.25-5_armhf.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ls -lZ binutils* -rw-r--r--. 1 root root u:object_r:unlabeled:s0 3533014 Feb 25 2015 -binutils_2.25-5_armhf.deb [cd /etc] ls -lZ | grep selinux drwxr-xr-x. 3 root root u:object_r:unlabeled:s0 4096 Dec 30 01:23 selinux There was a posted suggestion that remounting /etc/selinux ro fixes this error but it's not a mountpoint here. What if I chmod it not writeable? chmod 600 selinux root@gsm:/etc# ls -la | grep selinux drw---. 3 root root4096 Dec 30 01:23 selinux Doesn't work. Set it back to 755 Do I need to get the source of dpkg to find out what file it's not finding or does somebody know what this error message is talking about? Is it because the deb apparently doesn't have selinux attributes set? I did a little reading and Android 5 was the first version where selinux wasn't permissive by default, wonder if that's why there are so many problems. I'm a little confused about how having the Android side using selinux affects the Debian side. I can't install binutils and some other packages, some I can. Mostly I just want Make, for now, and stuff to compile C programs. -- Credit is the root of all evil. - AB1JX
Re: security labeling handle: No such file or directory (what file?)
Maybe I figured out something. I don't have an selinux policy under Debian, no files for creating one. But the kernel was built for Android which expects one. That could be the missing file. In OpenBSD there are tools for finding out things about the kernel, I don't know how to do that in Linux. The error message may come from the kernel. I'll try setting up some policy just so there is one. seinfo says there's no default policy. On 12/30/15, Alan Coreywrote: > With my Debian Kit installation on a phone (Motorola Mote-e2, Android > 5.02) I seem to be having selinux problems. I've read part of > Gentoo's selinux tutorial at > https://wiki.gentoo.org/wiki/SELinux/Tutorials and I'm trying to > figure this out. > > Did: > setenforce permissive > root@gsm:/# getenforce > Permissive > root@gsm:/# apt-get -f install > Reading package lists... Done > Building dependency tree > Reading state information... Done > Correcting dependencies... Done > The following extra packages will be installed: > binutils > Suggested packages: > binutils-doc > The following NEW packages will be installed: > binutils > 0 upgraded, 1 newly installed, 0 to remove and 28 not upgraded. > 3 not fully installed or removed. > Need to get 0 B/3542 kB of archives. > After this operation, 17.8 MB of additional disk space will be used. > Do you want to continue? [Y/n] y > dpkg: error processing archive > /var/cache/apt/archives/binutils_2.25-5_armhf.deb (--unpack): > cannot get security labeling handle: No such file or directory > Errors were encountered while processing: > /var/cache/apt/archives/binutils_2.25-5_armhf.deb > E: Sub-process /usr/bin/dpkg returned an error code (1) > > ls -lZ binutils* > -rw-r--r--. 1 root root u:object_r:unlabeled:s0 3533014 Feb 25 2015 > -binutils_2.25-5_armhf.deb > > [cd /etc] > > ls -lZ | grep selinux > drwxr-xr-x. 3 root root u:object_r:unlabeled:s0 4096 Dec 30 01:23 > selinux > > There was a posted suggestion that remounting /etc/selinux ro fixes this > error > but it's not a mountpoint here. What if I chmod it not writeable? > chmod 600 selinux > root@gsm:/etc# ls -la | grep selinux > drw---. 3 root root4096 Dec 30 01:23 selinux > Doesn't work. Set it back to 755 > > Do I need to get the source of dpkg to find out what file it's not > finding or does somebody know what this error message is talking > about? Is it because the deb apparently doesn't have selinux > attributes set? > > I did a little reading and Android 5 was the first version where > selinux wasn't permissive by default, wonder if that's why there are > so many problems. I'm a little confused about how having the Android > side using selinux affects the Debian side. > > I can't install binutils and some other packages, some I can. Mostly > I just want Make, for now, and stuff to compile C programs. > > > -- > Credit is the root of all evil. - AB1JX > -- Credit is the root of all evil. - AB1JX
Re: orion5x housekeeping
On Wed, Dec 30, 2015 at 6:51 PM, Martin Michlmayrwrote: > 2) HP Media Vault mv2120: this used to work fine and had users but I > haven't heard anything recently. Any users? > I just installed Debian Jessie on two HP MV2120's I use for backup systems at my house in the past week. Jessie came up perfectly fine. My only complaint is that SATA performance is a bit slow, but I don't know if this is from the low specs on the orion5x CPU or if the SATA drivers are not very polished. Otherwise they are great little systems to run Debian and software RAID on. Hopefully Debian can be maintained on the HP MV2120 into the future... Mike