Re: [DNG] writable efi
My new Asus laptop is EFI. Running debian sid, no dual-booting or anything like that. and cat /proc/mounts has this:- efivarfs /sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0 DaveT and for the sake of completeness the whole thing:- cat /proc/mounts sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0 udev /dev devtmpfs rw,relatime,size=10240k,nr_inodes=1009093,mode=755 0 0 devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /run tmpfs rw,nosuid,relatime,size=1616108k,mode=755 0 0 /dev/sda2 / ext4 rw,noatime,errors=remount-ro,data=ordered 0 0 securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0 tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0 cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd 0 0 pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0 efivarfs /sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0 cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0 cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0 cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0 cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0 cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0 cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0 cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0 systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=23,pgrp=1,timeout=0,minproto=5,maxproto=5,direct 0 0 debugfs /sys/kernel/debug debugfs rw,relatime 0 0 hugetlbfs /dev/hugepages hugetlbfs rw,relatime 0 0 mqueue /dev/mqueue mqueue rw,relatime 0 0 /dev/sda4 /home ext4 rw,noatime,data=ordered 0 0 /dev/sda1 /boot/efi vfat rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro 0 0 binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0 tmpfs /run/user/116 tmpfs rw,nosuid,nodev,relatime,size=808056k,mode=700,uid=116,gid=124 0 0 tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=808056k,mode=700,uid=1000,gid=1000 0 0 fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0 On 06/02/16 19:26, Hendrik Boom wrote: On Sat, Feb 06, 2016 at 03:37:05PM +, Go Linux wrote: Is it true that /sys/firmware/efi is also mounted rw under sysvinit? Apologies if I missed the answer to this question in this long thread. Not on my nonefi devuan jessie alpha2 system. Anyone have an efi jessie to report on? -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Definitely OT!! Re: Bad UEFI: was Systemd at work: rm -rf EFI
Svante Signell writes: > On Sat, 2016-02-06 at 21:07 +, Rainer Weikusat wrote: >> [...] >> >> > And BTW: How many packages have you (meaning all on this list) >> > volunteered to maintain?? >> >> As far as I can tell, the "official standpoint" of 'Devuan' in this >> respect is 'no help wanted'. At least, no question for that I saw on >> this list, including my own, has ever received an answer. >> >> So, whom are you assaulting for what? > > Iv'e never seen a statement like 'no help wanted', where did you see > that? This surely breaks a record for tl;dr but comment ... ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Change netman into another name.
Hi, Although, some comments were mean, I apologize for my behaviour. This apology has to be taken in the light, that I wish Devuan to continue developing into a distribution, that can be used by all those who respect freedom of choice. As I am one of those who became uneasy with the introduction of systemd and the way it is taking over what we know of Linux, I makes sense that I forget, but I am no living human perfection. Hopefully, many accept this apology. Edward On 07/02/2016, Adam Borowski wrote: > On Sun, Feb 07, 2016 at 02:26:16AM +0100, Arnt Karlsen wrote: >> On Sun, 07 Feb 2016 01:27:26 +0100, aitor_czr wrote: >> > On 02/06/2016 07:27 PM, dng-requ...@lists.dyne.org wrote: >> > > On Sat, 2016-02-06 at 19:03 +0100, Edward Bartolo wrote: >> > >> >Whether you like it, systemd TROLL or NOT, it is me who can only >> > >> >change the name of the project. >> > >> > >> > >> >Keep punning for your family members, SCUMBAG!!! >> > >> > >> > > Please Edward, Peter is no scumbag. Read what he suggests instead. >> > > And calm down! >> > >> > Peter Olson is not offending you. I don't understand your anger. >> >> ..he may have taken offence from my comment on the name, >> which he may have interpreted as "netbark", I never meant >> to offend him or anyone else here. > > The offence is right, as instead of referring to useless creatures we should > pay homage to the Master Species instead and name netman "netmeow". > > > But really, it's getting ridiculous. > > -- > A tit a day keeps the vet away. > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Easynetaid is for now netman's new name
Hi, I did all necessary changes in the netman project to rename it to: "easynetaid" which is unique on google. If someone suggests a serious name that is better suited than the new name, I will consider it. I pushed the changes. The GUI's help was debugged to work. Manpage can be invoked by: man easynetaid Edward ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] writable efi
Arnt Karlsen writes: [...] >> > /sys/firmware/ and everything in it is mounted rw on my Gigabyte >> > legacy board with Devuan installed. >> >> That's true on my non=efi system, too, but it has >> no /sys/firmware/efi. > > ..can an efi board set up with legacy boot and running e.g. sys-v, > be tricked into bricking itself e.g. by reading an "ad" flash movie > off a web site and writing it into a new bad /sys/firmware/efi and > then "try" a kexec reboot? Etc? As far as I remember, I'm using an EFI-capable system in legacy mode[*] and the efivarfs module can't be inserted into my kernel. It's rejected with ERROR: could not insert 'efivarfs': No such device But this may be different on other systems and there's reportedly also a /sys-based older interface for accessing the EFI variable service. It should be possible to test this with modprobe efivarfs one could also remove the module (mine is called 4.5.0-rc2-net/kernel/fs/efivarfs/efivarfs.ko ) or compile a kernel without support for the efivarfs (File systems/ Pseudo filesystems/ EFI Variable filesystem) or without any support for EFI runtime services (Processor type and features/ EFI runtime service support) [*] I installed that by taking the disk out and connecting it to my former work computer, followed by copying the old system and then switched everything off which looked unfamiliar/ fishy during first boot of the new one without paying much attention to that. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] writable efi
On Sun, 7 Feb 2016 10:42:04 +, Dave wrote in message <56b71f7c.9060...@barradas.free-online.co.uk>: > My new Asus laptop is EFI. > Running debian sid, no dual-booting or anything like that. > and cat /proc/mounts has this:- > > efivarfs /sys/firmware/efi/efivars efivarfs > rw,nosuid,nodev,noexec,relatime 0 0 > > DaveT ..you missed: /dev/sda1 /boot/efi vfat rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro 0 0 ..based on #..wtf??? I understand from your own completeness list, I'd say you also missed these: ... udev /dev devtmpfs rw,relatime,size=10240k,nr_inodes=1009093,mode=755 0 0 # ..why this nr_inodes=1009093 thing??? devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 ... /dev/sda2 / ext4 rw,noatime,errors=remount-ro,data=ordered 0 0 securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0 #..wtf _is_ this??? ... tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0 cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd 0 0 pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0 #..wtf _is_ this??? efivarfs /sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0 #..you found this, wtf _is_ this??? cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0 #..wtf _is_ this??? cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0 cgroup /sys/fs/cgroup/net_cls,net_prio cgroup rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0 #..wtf _is_ this, systemd's own tor??? cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0 cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0 cgroup /sys/fs/cgroup/perf_event cgroup rw,nosuid,nodev,noexec,relatime,perf_event 0 0 cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0 #..wtf _is_ this, systemd's own dd??? systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=23,pgrp=1,timeout=0,minproto=5,maxproto=5,direct 0 0 #..wtf _is_ this, a new /proc root tree??? debugfs /sys/kernel/debug debugfs rw,relatime 0 0 ... mqueue /dev/mqueue mqueue rw,relatime 0 0 /dev/sda4 /home ext4 rw,noatime,data=ordered 0 0 #..wtf _is_ this, systemd's sensoring your root's email??? /dev/sda1 /boot/efi vfat rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=utf8,shortname=mixed,errors=remount-ro 0 0 #..wtf, this must be your pants around your toes? ..based on wtf I understand from systemd now, I'd say Donald Trump's run for president will survive Debian. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] writable efi
Arnt Karlsen writes: > On Sun, 7 Feb 2016 10:42:04 +, Dave wrote in message > <56b71f7c.9060...@barradas.free-online.co.uk>: >> My new Asus laptop is EFI. >> Running debian sid, no dual-booting or anything like that. >> and cat /proc/mounts has this:- >> >> efivarfs /sys/firmware/efi/efivars efivarfs >> rw,nosuid,nodev,noexec,relatime 0 0 >> >> DaveT > > ..you missed: > /dev/sda1 /boot/efi vfat That's the EFI boot partition. Since that's a specfication written by hardware guys, EFI using global variables for inter-module communication and the FAT filesystem (and god-only-knows what other kinds of deficient 1980s technology --- edge-triggered interrupts, anyone?) shouldn't come as a surprise. [...] > securityfs /sys/kernel/security securityfs FS-interface for configuring kernel 'security modules'. [...] > pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0 > #..wtf _is_ this??? 'Persistent storage fs' for storing kernel crashdump information such that it survives a reboot./ > efivarfs /sys/firmware/efi/efivars [...] > #..you found this, wtf _is_ this??? The filesystem providing access to the EFI variable service. > cgroup /sys/fs/cgroup/freezer cgroup > rw,nosuid,nodev,noexec,relatime,freezer 0 0 > #..wtf _is_ this??? [...] Altogoether, some bizarre 'control group filesystem' arrangement chosed by systemd. 'Control groups' (originally implemented by SGI) support putting processes in - well - control groups. This is (together with namespace support) the base for 'Linux containers' virtualization (another feature systemd usurped[*]). [*] Disclaimer: I'm getting paid to work on a product which uses this technology such that it cannot possibly coexist with systemd. As such I'm one of these morally repugnant closed-source developers and RedHat using money made from Linux for subsidizing Poettering et al breaking out stuff is obviously just what we deserve. > systemd-1 /proc/sys/fs/binfmt_misc autofs > rw,relatime,fd=23,pgrp=1,timeout=0,minproto=5,maxproto=5,direct 0 0 > #..wtf _is_ this, a new /proc root tree??? Automounter filesystem. [...] > mqueue /dev/mqueue mqueue rw,relatime 0 0 /dev/sda4 /home ext4 > rw,noatime,data=ordered 0 0 > #..wtf _is_ this, systemd's sensoring your root's email??? Pseudo-filesystem which is part of the POSIX message queue implementation. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Easynetaid is for now netman's new name
On 02/07/2016 01:00 PM, Edward Bartolo wrote: > > If someone suggests a serious name that is better suited than the new > name, I will consider it. > I'd like to suggest *netbeam*, also callable by `beammeup` or `beam [me] up [Scotty]` There's no netbeam package nor any `beam` UNIX command. == hk -- _ _ We are free to share code and we code to share freedom (_X_)yne Foundation, Free Culture Foundry * https://www.dyne.org/donate/ ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] transmission-daemon package
On 2016-02-07 03:26, shraptor wrote: On 2016-02-06 17:18, dev1fanboy wrote: So I am trying to build transmission-daemon without systemd, was just testing this locally and run into an issue. It can be built without systemd but transmission-gtk will no longer start downloading torrents. I think it is down to this error which appears when running transmission-gtk in a terminal: ** (transmission-gtk:32682): WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files I downloaded source and built transmission without systemd. Started transmission-daemon and successfully downloaded a torrent using transmission-remote. If I then start transmission-gtk I get the same behavior as you. The torrent doesn't start. I get no dbus error in terminal though. If I kill transmission-daemon and restart transmission-gtk the torrent starts. I am not sure what setup you're after but transmission-gtk works without transmission-daemon!? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] transmission-daemon package
Thanks for confirming, after your last reply I tried from source and after tinking with the flags to match the ones by debian, I found the same thing you just mentioned. It's when transmission-daemon is started that transmission-gtk (or qt) won't work and the reason seems to be transmission-daemon (the part that uses systemd) being started at the same time. Transmission remote features are working using a remote client. Mostly I've been trying to help with this: https://git.devuan.org/devuan/devuan-maintainers/issues/17 Will test it on debian with systemd, if it's the same I'll upload and fix transmission (transmission-daemon). Cheers, chillfan On Sunday, February 7, 2016 3:20 PM, shraptor wrote: > On 2016-02-07 03:26, shraptor wrote: >> On 2016-02-06 17:18, dev1fanboy wrote: >>> So I am trying to build transmission-daemon without systemd, was just >>> testing this locally and run into an issue. It can be built without >>> systemd but transmission-gtk will no longer start downloading >>> torrents. >>> >>> I think it is down to this error which appears when running >>> transmission-gtk in a terminal: >>> >>> ** (transmission-gtk:32682): WARNING **: Error retrieving >>> accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: >>> The name >>> org.a11y.Bus was not provided by any .service files > > I downloaded source and built transmission without systemd. > > Started transmission-daemon and successfully downloaded a torrent > using transmission-remote. > > If I then start transmission-gtk I get the same behavior as you. > The torrent doesn't start. I get no dbus error in terminal though. > > If I kill transmission-daemon and restart transmission-gtk the torrent > starts. > > I am not sure what setup you're after but transmission-gtk works without > transmission-daemon!? > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- Take back your privacy. Switch to www.StartMail.com ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Easynetaid is for now netman's new name
Le 07/02/2016 14:00, Edward Bartolo a écrit : I did all necessary changes in the netman project to rename it to: "easynetaid" which is unique on google. It's a very long name! Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Easynetaid is for now netman's new name
On Sun, 2/7/16, Edward Bartolo wrote: Subject: [DNG] Easynetaid is for now netman's new name To: "dng" Date: Sunday, February 7, 2016, 7:00 AM Hi, I did all necessary changes in the netman project to rename it to: "easynetaid" which is unique on google. If someone suggests a serious name that is better suited than the new name, I will consider it. I pushed the changes. The GUI's help was debugged to work. Manpage can be invoked by: man easynetaid Edward Sounds very geriatric. Please consider hellekin's suggestion. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] transmission-daemon package
Turns out both can work on debian jessie, so can't fix this unless there is a patch somewhere. Cheers, chillfan On Sunday, February 7, 2016 3:41 PM, dev1fanboy wrote: > Thanks for confirming, after your last reply I tried from source and after > tinking with the flags to match the ones by debian, I found the same thing > you just mentioned. It's when transmission-daemon is started that > transmission-gtk (or qt) won't work and the reason seems to be > transmission-daemon (the part that uses systemd) being started at the same > time. Transmission remote features are working using a remote client. > > Mostly I've been trying to help with this: > https://git.devuan.org/devuan/devuan-maintainers/issues/17 > > Will test it on debian with systemd, if it's the same I'll upload and fix > transmission (transmission-daemon). > > Cheers, > > chillfan > > On Sunday, February 7, 2016 3:20 PM, shraptor wrote: >> On 2016-02-07 03:26, shraptor wrote: >>> On 2016-02-06 17:18, dev1fanboy wrote: So I am trying to build transmission-daemon without systemd, was just testing this locally and run into an issue. It can be built without systemd but transmission-gtk will no longer start downloading torrents. I think it is down to this error which appears when running transmission-gtk in a terminal: ** (transmission-gtk:32682): WARNING **: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files >> >> I downloaded source and built transmission without systemd. >> >> Started transmission-daemon and successfully downloaded a torrent >> using transmission-remote. >> >> If I then start transmission-gtk I get the same behavior as you. >> The torrent doesn't start. I get no dbus error in terminal though. >> >> If I kill transmission-daemon and restart transmission-gtk the torrent >> starts. >> >> I am not sure what setup you're after but transmission-gtk works without >> transmission-daemon!? >> ___ >> Dng mailing list >> Dng@lists.dyne.org >> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > -- > Take back your privacy. Switch to www.StartMail.com > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- Take back your privacy. Switch to www.StartMail.com ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Change netman into another name.
On Sat, 6 Feb 2016 13:34:11 +0100, Arnt wrote in message <20160206133411.74d85...@nb6.lan>: > On Sat, 06 Feb 2016 01:46:21 +0100, aitor_czr wrote in message > <56b5425d.6020...@gnuinos.org>: > > > On 02/05/2016 07:18 PM, Go Linux wrote: > > > Every name I came up with was already in multiple use. I also > > > thought of netbarx which is completely unique. Kinda like it > > > actually. > > > > > > golinux > > > > IMO, netbarx is the best choice :) > > > > Aitor. > > ..it's immune to "netbarf"? ;o) ..it is. ;o) ..I vote for netbarx. :o) -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Easynetaid is for now netman's new name
On Sun, 7 Feb 2016 14:55:27 + hellekin wrote: > I'd like to suggest *netbeam*, also callable by `beammeup` or `beam [me] > up [Scotty]` I dont want to be beamed "up Scotty" ... Cheers, Ron. -- As long as the answer is right, who cares if the question is wrong ? -- http://www.olgiati-in-paraguay.org -- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] transmission-daemon package
Hi, I suggest you do some software analysis for: a) libraries b) functions exported by these libraries c) functions imported by the executable you are interested in running. This way you should be a able to determine which function/s are linked to from dbus and/or systemd. There are CLI tools for that. I have done it in the past. I have written a howto on forums.debian.net If I remember, the commands are: a) nm -D /path/to/executable b) ldd /path/to/executable Edward On 07/02/2016, dev1fanboy wrote: > Turns out both can work on debian jessie, so can't fix this unless there is > a patch somewhere. > > Cheers, > > chillfan > > On Sunday, February 7, 2016 3:41 PM, dev1fanboy > wrote: >> Thanks for confirming, after your last reply I tried from source and after >> tinking with the flags to match the ones by debian, I found the same thing >> you just mentioned. It's when transmission-daemon is started that >> transmission-gtk (or qt) won't work and the reason seems to be >> transmission-daemon (the part that uses systemd) being started at the same >> time. Transmission remote features are working using a remote client. >> >> Mostly I've been trying to help with this: >> https://git.devuan.org/devuan/devuan-maintainers/issues/17 >> >> Will test it on debian with systemd, if it's the same I'll upload and fix >> transmission (transmission-daemon). >> >> Cheers, >> >> chillfan >> >> On Sunday, February 7, 2016 3:20 PM, shraptor wrote: >>> On 2016-02-07 03:26, shraptor wrote: On 2016-02-06 17:18, dev1fanboy wrote: > So I am trying to build transmission-daemon without systemd, was just > testing this locally and run into an issue. It can be built without > systemd but transmission-gtk will no longer start downloading > torrents. > > I think it is down to this error which appears when running > transmission-gtk in a terminal: > > ** (transmission-gtk:32682): WARNING **: Error retrieving > accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: > The name > org.a11y.Bus was not provided by any .service files >>> >>> I downloaded source and built transmission without systemd. >>> >>> Started transmission-daemon and successfully downloaded a torrent >>> using transmission-remote. >>> >>> If I then start transmission-gtk I get the same behavior as you. >>> The torrent doesn't start. I get no dbus error in terminal though. >>> >>> If I kill transmission-daemon and restart transmission-gtk the torrent >>> starts. >>> >>> I am not sure what setup you're after but transmission-gtk works without >>> transmission-daemon!? >>> ___ >>> Dng mailing list >>> Dng@lists.dyne.org >>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng >> -- >> Take back your privacy. Switch to www.StartMail.com >> ___ >> Dng mailing list >> Dng@lists.dyne.org >> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > -- > Take back your privacy. Switch to www.StartMail.com > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Easynetaid is for now netman's new name
On Sun, 7 Feb 2016 14:55:27 +, hellekin wrote in message <56b75adf.6090...@dyne.org>: > On 02/07/2016 01:00 PM, Edward Bartolo wrote: > > > > If someone suggests a serious name that is better suited than the > > new name, I will consider it. > > > > I'd like to suggest *netbeam*, also callable by `beammeup` or `beam > [me] up [Scotty]` > > There's no netbeam package nor any `beam` UNIX command. > > == > hk > ..netbarx, I raise you "barx": arnt@celsius:~$ man -k barx barx: nothing appropriate. arnt@celsius:~$ dpkg -l |wc -l 15854 # ..a lot of crap on my Debian Sid box. ;o) arnt@celsius:~$ -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] transmission-daemon package
Turns out both can work on debian jessie, so can't fix this unless there is a patch somewhere. Do you mean both transmission-gtk and transmission-daemon ? I tested some more and if you define another port than default then you can run transmission-gtk and transmission-daemon at the same time. If it's that, this could be said to be fixed by changing default port to something else, perhaps this can be done in config-files? Or did I get you wrong? What do you want to patch? ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Change netman into another name.
> I never meant to insinuate or otherwise say anything about your > programming skill, I'm talking about how easily your netbarx name > can become "netbarf" and you proved my point by reading it as > "netbark" in your first response to me. This lack of strength is something that I have to face. > the only thing I'd critisize on your part, is your mail list > reader skills seeing malice where no malice was intended It would be nice if I don't see malice, but how do you succeed to interpret no malice? Maybe, I am expecting users of dng to express themselves in a way that appears to them unnatural. > naïvite on believing "systemd is only a tech issue" Of course systemd is a poltical issue. I agree on that. Systemd is a software lock-in, which is a bad thing for choice. > whichever bugs I might in your work, not the fact that your are doing good > work >here. I beg your pardon for that, I was tired from trolling, it can happen. Edward On 07/02/2016, Arnt Karlsen wrote: > On Sat, 6 Feb 2016 13:34:11 +0100, Arnt wrote in message > <20160206133411.74d85...@nb6.lan>: > >> On Sat, 06 Feb 2016 01:46:21 +0100, aitor_czr wrote in message >> <56b5425d.6020...@gnuinos.org>: >> >> > On 02/05/2016 07:18 PM, Go Linux wrote: >> > > Every name I came up with was already in multiple use. I also >> > > thought of netbarx which is completely unique. Kinda like it >> > > actually. >> > > >> > > golinux >> > >> > IMO, netbarx is the best choice :) >> > >> > Aitor. >> >> ..it's immune to "netbarf"? ;o) > > ..it is. ;o) > > ..I vote for netbarx. :o) > > > -- > ..med vennlig hilsen = with Kind Regards from Arnt Karlsen > ...with a number of polar bear hunters in his ancestry... > Scenarios always come in sets of three: > best case, worst case, and just in case. > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] writable efi
On Sun, 07 Feb 2016 14:47:54 +, Rainer wrote in message <87pow84lwl@doppelsaurus.mobileactivedefense.com>: > Arnt Karlsen writes: > > On Sun, 7 Feb 2016 10:42:04 +, Dave wrote in message > > <56b71f7c.9060...@barradas.free-online.co.uk>: > >> My new Asus laptop is EFI. > >> Running debian sid, no dual-booting or anything like that. > >> and cat /proc/mounts has this:- > >> > >> efivarfs /sys/firmware/efi/efivars efivarfs > >> rw,nosuid,nodev,noexec,relatime 0 0 > >> > >> DaveT > > > > ..you missed: > > /dev/sda1 /boot/efi vfat > > That's the EFI boot partition. Since that's a specfication written by > hardware guys, EFI using global variables for inter-module > communication and the FAT filesystem (and god-only-knows what other > kinds of deficient 1980s technology --- edge-triggered interrupts, > anyone?) shouldn't come as a surprise. ..right, so the key to your boot is in /dev/sda1 alias /boot/efi, or in a chip on the board, or is it Facebook style "complicated"? > [...] > > > securityfs /sys/kernel/security securityfs > > FS-interface for configuring kernel 'security modules'. ..controlled by what??? ..or by whom, the kernel guys or the systemd boys? > [...] > > > pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0 > > #..wtf _is_ this??? > > 'Persistent storage fs' for storing kernel crashdump information such > that it survives a reboot./ ..sounds abuseable, e.g. "crashdump" a "suspend-image" and kexec boot it to e.g. "edit" Ian Murdock's autopsy report? Etc? > > efivarfs /sys/firmware/efi/efivars > > [...] > > > #..you found this, wtf _is_ this??? > > The filesystem providing access to the EFI variable service. > > > cgroup /sys/fs/cgroup/freezer cgroup > > rw,nosuid,nodev,noexec,relatime,freezer 0 0 > > #..wtf _is_ this??? > > [...] > > Altogoether, some bizarre 'control group filesystem' arrangement > chosed by systemd. 'Control groups' (originally implemented by SGI) > support putting processes in - well - control groups. This is > (together with namespace support) the base for 'Linux containers' > virtualization (another feature systemd usurped[*]). > > [*] Disclaimer: I'm getting paid to work on a product which uses this > technology such that it cannot possibly coexist with systemd. As > such I'm one of these morally repugnant closed-source developers > and RedHat using money made from Linux for subsidizing Poettering et > al breaking out stuff is obviously just what we deserve. ..good to know. ;o) > > systemd-1 /proc/sys/fs/binfmt_misc autofs > > rw,relatime,fd=23,pgrp=1,timeout=0,minproto=5,maxproto=5,direct 0 0 > > #..wtf _is_ this, a new /proc root tree??? > > Automounter filesystem. ..automounting everything behind the scenes? > [...] > > > mqueue /dev/mqueue mqueue rw,relatime 0 0 /dev/sda4 /home ext4 > > rw,noatime,data=ordered 0 0 > > #..wtf _is_ this, systemd's sensoring your root's email??? > > Pseudo-filesystem which is part of the POSIX message queue > implementation. ...which can or cannot be used to censor root's etc email??? Etc? ..I used to help teach AA gunnery flying target "drones." AA gunnery is done "leading the target", aiming ahead of "where it is now" far enough so your ammo can make it into your target and bring it down or scare it away. ..lots of guesswork involved in AA gunnery, some can be guesstimated, and ofcourse you'll miss if you guess your target's manouvering wrong, and ofcourse his ammo can hit you pretty badly. AFAICT, systemd is no different. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] writable efi
On Sun, 07 Feb 2016 13:10:16 +, Rainer wrote in message <87h9hkmzt3@doppelsaurus.mobileactivedefense.com>: > Arnt Karlsen writes: > > > [...] > > >> > /sys/firmware/ and everything in it is mounted rw on my Gigabyte > >> > legacy board with Devuan installed. > >> > >> That's true on my non=efi system, too, but it has > >> no /sys/firmware/efi. > > > > ..can an efi board set up with legacy boot and running e.g. sys-v, > > be tricked into bricking itself e.g. by reading an "ad" flash movie > > off a web site and writing it into a new bad /sys/firmware/efi and > > then "try" a kexec reboot? Etc? > > As far as I remember, I'm using an EFI-capable system in legacy > mode[*] and the efivarfs module can't be inserted into my kernel. > It's rejected with > > ERROR: could not insert 'efivarfs': No such device > > But this may be different on other systems and there's reportedly > also a /sys-based older interface for accessing the EFI variable > service. It should be possible to test this with > > modprobe efivarfs > > one could also remove the module (mine is called > > 4.5.0-rc2-net/kernel/fs/efivarfs/efivarfs.ko ..these are the fairy tales we are told nowadays. ..can a Devuan box be bricked etc with such EFI/systemd type stunts using _other_, non-EFI, non-systemd names??? > ) or compile a kernel without support for the efivarfs (File systems/ > Pseudo filesystems/ EFI Variable filesystem) or without any support > for EFI runtime services (Processor type and features/ EFI runtime > service support) > > [*] I installed that by taking the disk out and connecting it to my > former work computer, followed by copying the old system and then > switched everything off which looked unfamiliar/ fishy during first > boot of the new one without paying much attention to that. ..sounds familiar, I have a laptop disk running in its 5th machine, online with "wlan4"... once I yank "eth2"... ;oD -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Migration to devuan Jessie failed on rpi-zero
Hi folks, I recently got one of those new raspberry pi zero. The little thing should have exactly the same hw of the first version of rpi. Hence, I thought I could have migrated it swiftly from raspbian (jessie) to devuan, and I was eager to post my report here. Unfortunately, my enthusiasm left room to frustration. To cut a long story short, apt-get dist-upgrade fails on unpacking bash_4.3, and in particular it seems that the pre-installation script is bein killed with SIGILL (Illegal Instruction). This seems to suggest that there might be something wrong in how the devuan armhf packages are compiled, or just an incompatibility due to rpi-zero. However, the "normal" raspbian jessie runs smoothly (apart from the fact that, notwistanding systemd, the boot still requires more than 90 seconds...), hence it should be possible to have the correspoinding devuan packages working... Any ideas? I also thought at some point that I could have dist-upgraded directly from (debian) jessie to (devuan) ascii, but has any of you tried this before? HND KatolaZ -- [ Enzo Nicosia aka KatolaZ --- GLUG Catania -- Freaknet Medialab ] [ me [at] katolaz.homeunix.net -- http://katolaz.homeunix.net -- ] [ GNU/Linux User:#325780/ICQ UIN: #258332181/GPG key ID 0B5F062F ] [ Fingerprint: 8E59 D6AA 445E FDB4 A153 3D5A 5F20 B3AE 0B5F 062F ] ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] transmission-daemon package
Ah I didn't think to check that, it does work here when changing the port. Maybe this behaviour is okay, e.g someone would normally use only one at a time, or otherwise change the port. Anyone have any thoughts on that? If it doesn't seem like the right behaviour I could try to change the default ports somehow. Thanks, chillfan On Sunday, February 7, 2016 6:25 PM, shraptor wrote: >> Turns out both can work on debian jessie, so can't fix this unless >> there is a patch somewhere. > > Do you mean both transmission-gtk and transmission-daemon ? > > I tested some more and if you define another port than default > then you can run transmission-gtk and transmission-daemon > at the same time. > > If it's that, this could be said to be fixed by changing > default port to something else, perhaps this can be done > in config-files? > > > Or did I get you wrong? What do you want to patch? > > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- Take back your privacy. Switch to www.StartMail.com ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Migration to devuan Jessie failed on rpi-zero
KatolaZ writes: > Unfortunately, my enthusiasm left room to frustration. To cut a long > story short, apt-get dist-upgrade fails on unpacking bash_4.3, and in > particular it seems that the pre-installation script is bein killed > with SIGILL (Illegal Instruction). You could put bash on hold, echo 'bash hold' | dpkg --set-selections and see if the remaining installation succeeds. Or download the bash .deb by hand and try to install it via dpkg -i It should also be possible to get coredump from the SIGILL which would identify the exact program and the faulting instruction/ address. While I haven't written any ARM assembly[*] for some years, I'm confident to understand enough of an ARM binary to detemine if this is in fact an illegal instruction or something else, ie, flaky hardware, ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Migration to devuan Jessie failed on rpi-zero
On Sun, Feb 07, 2016 at 07:26:27PM +, KatolaZ wrote: > I recently got one of those new raspberry pi zero. The little thing > should have exactly the same hw of the first version of rpi. Hence, I > thought I could have migrated it swiftly from raspbian (jessie) to > devuan, and I was eager to post my report here. My understanding is that both the rpi0 and rpi1 are based on a ARMv6 chip, which makes them closer to armel than to armhf. So, I'm afraid you're stuck with raspbian for now. > > Unfortunately, my enthusiasm left room to frustration. To cut a long > story short, apt-get dist-upgrade fails on unpacking bash_4.3, and in > particular it seems that the pre-installation script is bein killed > with SIGILL (Illegal Instruction). This seems to suggest that there > might be something wrong in how the devuan armhf packages are > compiled, or just an incompatibility due to rpi-zero. However, the > "normal" raspbian jessie runs smoothly (apart from the fact that, > notwistanding systemd, the boot still requires more than 90 > seconds...), hence it should be possible to have the correspoinding > devuan packages working... I'd say it's an incompatibility. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] transmission-daemon package
On 2016-02-07 20:38, dev1fanboy wrote: Ah I didn't think to check that, it does work here when changing the port. Maybe this behaviour is okay, e.g someone would normally use only one at a time, or otherwise change the port. Anyone have any thoughts on that? If it doesn't seem like the right behaviour I could try to change the default ports somehow. I think its fine as it is. Its enough to remove dependency on libsystemd ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Dng Digest, Vol 17, Issue 39
Message: 6 Date: Sun, 7 Feb 2016 19:26:27 + From: KatolaZ To:dng@lists.dyne.org Subject: [DNG] Migration to devuan Jessie failed on rpi-zero Message-ID:<20160207192627.gg23...@katolaz.homeunix.net> Content-Type: text/plain; charset=us-ascii Hi folks, I recently got one of those new raspberry pi zero. The little thing should have exactly the same hw of the first version of rpi. Hence, I thought I could have migrated it swiftly from raspbian (jessie) to devuan, and I was eager to post my report here. Unfortunately, my enthusiasm left room to frustration. To cut a long story short, apt-get dist-upgrade fails on unpacking bash_4.3, and in particular it seems that the pre-installation script is bein killed with SIGILL (Illegal Instruction). This seems to suggest that there might be something wrong in how the devuan armhf packages are compiled, or just an incompatibility due to rpi-zero. However, the "normal" raspbian jessie runs smoothly (apart from the fact that, notwistanding systemd, the boot still requires more than 90 seconds...), hence it should be possible to have the correspoinding devuan packages working... Any ideas? I also thought at some point that I could have dist-upgraded directly from (debian) jessie to (devuan) ascii, but has any of you tried this before? HND KatolaZ The original Pi is not fully armhf (ARM6 instruction set instead of ARM7) and your choice is to use armel packages or compile armhf with the arm6 flag. http://raspberrypi.stackexchange.com/questions/9912/how-do-i-tell-which-version-arm-cpu-on-my-pi Nick ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Migration to devuan Jessie failed on rpi-zero
Gregory Nowak writes: > On Sun, Feb 07, 2016 at 07:26:27PM +, KatolaZ wrote: >> I recently got one of those new raspberry pi zero. The little thing >> should have exactly the same hw of the first version of rpi. Hence, I >> thought I could have migrated it swiftly from raspbian (jessie) to >> devuan, and I was eager to post my report here. > > My understanding is that both the rpi0 and rpi1 are based on a ARMv6 > chip, which makes them closer to armel than to armhf. So, I'm afraid > you're stuck with raspbian for now. The armhf wiki states that The lowest worthwhile CPU implementation is ARMv7-A but ARMv6 surely includes a FPU. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Dng Digest, Vol 17, Issue 39
On Sun, Feb 07, 2016 at 09:01:25PM +0100, info at smallinnovations.nl wrote: > [cut] > > The original Pi is not fully armhf (ARM6 instruction set instead of > ARM7) and your choice is to use armel packages or compile armhf > with the arm6 flag. > The problem is that Devuan has only armhf so far :) I know the pi zero has an ARM6, but it has a FPU and the raspbian jessie declares itself as "armhf". This probably means that they compiled all the packages for arm6? If it is inly a matter of recompiling for armhf with the arm6 flag, shall we try to put together a devuan for arm6? HND KatolaZ -- [ Enzo Nicosia aka KatolaZ --- GLUG Catania -- Freaknet Medialab ] [ me [at] katolaz.homeunix.net -- http://katolaz.homeunix.net -- ] [ GNU/Linux User:#325780/ICQ UIN: #258332181/GPG key ID 0B5F062F ] [ Fingerprint: 8E59 D6AA 445E FDB4 A153 3D5A 5F20 B3AE 0B5F 062F ] ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Dng Digest, Vol 17, Issue 39
On Sun, Feb 07, 2016 at 09:07:12PM +, KatolaZ wrote: [cut] > > The problem is that Devuan has only armhf so far :) I know the pi zero > Well, it seems that I am wrong here. In the "merged" repository "armel" is present, and there is also a version of the installer for armel, hence it should be possible (at least in principle) to use the armel port in the pi0... I will try to get around this and let you know. My2Cents KatolaZ -- [ Enzo Nicosia aka KatolaZ --- GLUG Catania -- Freaknet Medialab ] [ me [at] katolaz.homeunix.net -- http://katolaz.homeunix.net -- ] [ GNU/Linux User:#325780/ICQ UIN: #258332181/GPG key ID 0B5F062F ] [ Fingerprint: 8E59 D6AA 445E FDB4 A153 3D5A 5F20 B3AE 0B5F 062F ] ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] transmission-daemon package
I reckon so too, will sort it out then. Thanks for helping me figure out the problem. Cheers, chillfan On Sunday, February 7, 2016 7:57 PM, shraptor wrote: > On 2016-02-07 20:38, dev1fanboy wrote: >> Ah I didn't think to check that, it does work here when changing the >> port. Maybe this behaviour is okay, e.g someone would normally use >> only one at a time, or otherwise change the port. Anyone have any >> thoughts on that? >> >> If it doesn't seem like the right behaviour I could try to change the >> default ports somehow. > > I think its fine as it is. Its enough to remove dependency on libsystemd > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- Take back your privacy. Switch to www.StartMail.com ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Dng Digest, Vol 17, Issue 39
On Sun, 7 Feb 2016 21:07:12 +, KatolaZ wrote in message <20160207210712.ga...@katolaz.homeunix.net>: > On Sun, Feb 07, 2016 at 09:01:25PM +0100, info at smallinnovations.nl > wrote: > > > > [cut] > > > > > The original Pi is not fully armhf (ARM6 instruction set instead of > > ARM7) and your choice is to use armel packages or compile armhf > > with the arm6 flag. > > > > The problem is that Devuan has only armhf so far :) I know the pi zero > has an ARM6, but it has a FPU and the raspbian jessie declares itself > as "armhf". This probably means that they compiled all the packages > for arm6? > > If it is inly a matter of recompiling for armhf with the arm6 flag, > shall we try to put together a devuan for arm6? ..yup, and it is worth the while starting from the Raspian Wheezy flavor a year ago, rather than todays Raspian Jessie. I have one of each ready for guinea pig service. ;o) -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Dng Digest, Vol 17, Issue 39
On Sun, Feb 07, 2016 at 10:49:48PM +0100, Arnt Karlsen wrote: [cut] > > > > If it is inly a matter of recompiling for armhf with the arm6 flag, > > shall we try to put together a devuan for arm6? > > ..yup, and it is worth the while starting from the Raspian > Wheezy flavor a year ago, rather than todays Raspian Jessie. > I have one of each ready for guinea pig service. ;o) > The problem is that the old Raspbian wheezy won't boot on pi0, due to a firmware problem (I tried that one before trying the tainted jessie, obviously...). There is a workaround though, which consists on upgrading the firmware to the newest version from a pi1 or a pi2, but I haven't tried it. I really would like to have a devuan armhf port compiled for arm6, to get advantage of the FPU. Honestly, it has been a long time since I had the whole toolchain installed to cross-compile for arm, but this would probably be worth the effort, and convince me to travel a few years back in time. There are a lot of people out there using pis, and some are already complaining about systemd, and many would love a pi-vuan. Any volunteers around? :) HND KatolaZ -- [ Enzo Nicosia aka KatolaZ --- GLUG Catania -- Freaknet Medialab ] [ me [at] katolaz.homeunix.net -- http://katolaz.homeunix.net -- ] [ GNU/Linux User:#325780/ICQ UIN: #258332181/GPG key ID 0B5F062F ] [ Fingerprint: 8E59 D6AA 445E FDB4 A153 3D5A 5F20 B3AE 0B5F 062F ] ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] pi-vuan
On 02/07/2016 11:09 PM, KatolaZ ¡¡ wrote: There are a lot of people out there using pis, and some are already complaining about systemd, and many would love a pi-vuan. Any volunteers around?:) Yes :) ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Change netman into another name.
Dear Edward, On 07/02/2016, Arnt Karlsen wrote: >On Sat, 6 Feb 2016 13:34:11 +0100, Arnt wrote in message ><20160206133411.74d85...@nb6.lan>: > >>On Sat, 06 Feb 2016 01:46:21 +0100, aitor_czr wrote in message >><56b5425d.6020...@gnuinos.org>: >> >> >On 02/05/2016 07:18 PM, Go Linux wrote: >> > >Every name I came up with was already in multiple use. I also >> > >thought of netbarx which is completely unique. Kinda like it >> > >actually. >> > > >> > >golinux >> > >> >IMO, netbarx is the best choice:) >> > >> > Aitor. >> >>..it's immune to "netbarf"? ;o) > >..it is. ;o) > >..I vote for netbarx. :o) You can't fight against the avalanche of netbarx. I'm a hooligan of netbarx. Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Change netman into another name.
Can we Move On? On 2016-02-07 20:10, aitor_czr wrote: Dear Edward, On 07/02/2016, Arnt Karlsen wrote: On Sat, 6 Feb 2016 13:34:11 +0100, Arnt wrote in message <20160206133411.74d85...@nb6.lan>: On Sat, 06 Feb 2016 01:46:21 +0100, aitor_czr wrote in message <56b5425d.6020...@gnuinos.org>: On 02/05/2016 07:18 PM, Go Linux wrote: > Every name I came up with was already in multiple use. I also > thought of netbarx which is completely unique. Kinda like it > actually. > > golinux IMO, netbarx is the best choice :) Aitor. ..it's immune to "netbarf"? ;o) ..it is. ;o) ..I vote for netbarx. :o) You can't fight against the avalanche of netbarx. I'm a hooligan of netbarx. Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -- Stop slacking you lazy bum! ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] pi-vuan
On 08/02/16 11:58, aitor_czr wrote: > > On 02/07/2016 11:09 PM, KatolaZ ¡¡ wrote: >> There are a lot of people out there using pis, and >> some are already complaining about systemd, and many would love a >> pi-vuan. Any volunteers around? :) > > Yes :) > I've previously said that I'd be interested in bootstrapping a port for raspberry pi abi, but that will have to wait until a little later down the track ... unless we get a big donation of hardware suitable for building and testing the port.. and even then probably won't start until post jessie 1.0 release. Daniel -- Daniel Reurich Centurion Computer Technology (2005) Ltd. 021 797 722 signature.asc Description: OpenPGP digital signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] pi-vuan
I can do testing, I have a few raspberry pi's, all still running wheezy. On Mon, Feb 8, 2016 at 9:58 AM, aitor_czr wrote: > > On 02/07/2016 11:09 PM, KatolaZ > ¡¡ wrote: > > There are a lot of people out there using pis, and > some are already complaining about systemd, and many would love a > pi-vuan. Any volunteers around? :) > > > Yes :) > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Dng Digest, Vol 17, Issue 39
On Sun, 7 Feb 2016 22:09:44 +, KatolaZ wrote in message <20160207220944.gc...@katolaz.homeunix.net>: > On Sun, Feb 07, 2016 at 10:49:48PM +0100, Arnt Karlsen wrote: > > [cut] > > > > > > > If it is inly a matter of recompiling for armhf with the arm6 > > > flag, shall we try to put together a devuan for arm6? > > > > ..yup, and it is worth the while starting from the Raspian > > Wheezy flavor a year ago, rather than todays Raspian Jessie. > > I have one of each ready for guinea pig service. ;o) > > > > The problem is that the old Raspbian wheezy won't boot on pi0, due to > a firmware problem (I tried that one before trying the tainted jessie, > obviously...). There is a workaround though, which consists on > upgrading the firmware to the newest version from a pi1 or a pi2, but > I haven't tried it. > > I really would like to have a devuan armhf port compiled for arm6, to > get advantage of the FPU. Honestly, it has been a long time since I > had the whole toolchain installed to cross-compile for arm, but this > would probably be worth the effort, and convince me to travel a few > years back in time. There are a lot of people out there using pis, and > some are already complaining about systemd, and many would love a > pi-vuan. Any volunteers around? :) ..I did mention "guinea pig service" for my test animals? ;o) ..and I still haven't heard any disk space numbers here, are our mirrors the same size as Debian's mirrors??? Decides which disk etc I use in my own mirror box. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Migration to devuan Jessie failed on rpi-zero
On 08/02/16 07:15, Rainer Weikusat wrote: Gregory Nowak writes: On Sun, Feb 07, 2016 at 07:26:27PM +, KatolaZ wrote: I recently got one of those new raspberry pi zero. The little thing should have exactly the same hw of the first version of rpi. Hence, I thought I could have migrated it swiftly from raspbian (jessie) to devuan, and I was eager to post my report here. My understanding is that both the rpi0 and rpi1 are based on a ARMv6 chip, which makes them closer to armel than to armhf. So, I'm afraid you're stuck with raspbian for now. The armhf wiki states that The lowest worthwhile CPU implementation is ARMv7-A but ARMv6 surely includes a FPU. raspbian is in between armel and armhf because debian armel is (or was then) compiled without hard float support while debian armhf is compiled for arm7 ... so since PIs are arm6 with FPU neither is suitable ... raspbian is compiled to suit PIs. It was also made very lean, essentially for console use with X available when desired via startx or vncserver over a local connection. I think it may have quite a lot of modifications in the graphics area since the chip has its graphics processor on board, and it is broadcoms, and its specs are not fully released, and the raspberry team has very deep knowledge of this part (one of them at least was on the development team for it). I have mucked about a bit with its multimedia capacities ... both nice and frustrating at the same time. I believe is a platform that suits their release formats as a fairly bare board with minimal peripherals for incorporation in DIY embedded systems quite well. It can also be used by experienced people willing to put time into making a single purpose kiosk style setup. But anyone hoping for a cheap, open general computer will be frustrated. It is quite a good learning tool though, since the community is big and helpful. Simon ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Easynetaid is for now netman's new name
On Sun, Feb 07, 2016 at 02:00:26PM +0100, Edward Bartolo wrote: > Hi, > > I did all necessary changes in the netman project to rename it to: > "easynetaid" which is unique on google. That is a good name. Simple, unique, and descriptive. I wish all names were as good. -- hendrik ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Migration to devuan Jessie failed on rpi-zero
On Mon, Feb 08, 2016 at 01:27:19PM +1100, Simon Wise wrote: > raspbian is in between armel and armhf because debian armel is (or > was then) compiled without hard float support while debian armhf is > compiled for arm7 ... so since PIs are arm6 with FPU neither is > suitable Just to be clear, the rpi2 is based on a ARMv7. My rpi2 is running devuan jessie nicely, as I have posted here a few months ago. > It > can also be used by experienced people willing to put time into > making a single purpose kiosk style setup. But anyone hoping for a > cheap, open general computer will be frustrated. It is quite a good > learning tool though, since the community is big and helpful. I think that depends on what one expects. If someone gets one of these, and hopes it can replace a modern desktop/laptop, then that person will indeed be frustrated. I wanted to use mine as a router possibly running i2p and freenet as well, and I thought when I was getting it I had a good understanding of its limitations. It does the router part very well as I expected. It ran i2p well enough also, though I have since transferred that to my laptop for reasons unrelated to performance. The freenet node ran fine when it was idle. However putting some downloads in the queue made the freenet node slow to respond, and it crashed once a day or so.. I had hoped all of that would be otherwise, but am not surprised by the reality of things. The main job for my rpi2 is to be a router, and it does that very well so far. Greg -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-mana...@eu.org ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Migration to devuan Jessie failed on rpi-zero
I have 3 raspberry pi's original B, B+, 2 B (quad) I'm using the B+ as a headless server for apt-cacher, I use for live-build's The 2 B I'm going to make a lightweight desktop, as it's better spec'd than my netbook and used less power. On Mon, Feb 8, 2016 at 2:18 PM, Gregory Nowak wrote: > On Mon, Feb 08, 2016 at 01:27:19PM +1100, Simon Wise wrote: > > raspbian is in between armel and armhf because debian armel is (or > > was then) compiled without hard float support while debian armhf is > > compiled for arm7 ... so since PIs are arm6 with FPU neither is > > suitable > > Just to be clear, the rpi2 is based on a ARMv7. My rpi2 is running > devuan jessie nicely, as I have posted here a few months ago. > > > > It > > can also be used by experienced people willing to put time into > > making a single purpose kiosk style setup. But anyone hoping for a > > cheap, open general computer will be frustrated. It is quite a good > > learning tool though, since the community is big and helpful. > > I think that depends on what one expects. If someone gets one of > these, and hopes it can replace a modern desktop/laptop, then that > person will indeed be frustrated. I wanted to use mine as a router > possibly running i2p and freenet as well, and I thought when I was > getting it I had a good understanding of its limitations. It does the > router part very well as I expected. It ran i2p well enough also, > though I have since transferred that to my laptop for reasons unrelated > to performance. The freenet node ran fine when it was idle. However > putting some downloads in the queue made the freenet node slow to > respond, and it crashed once a day or so.. I had hoped all of that > would be otherwise, but am not surprised by the reality of things. The > main job for my rpi2 is to be a router, and it does that very well so far. > > Greg > > > -- > web site: http://www.gregn.net > gpg public key: http://www.gregn.net/pubkey.asc > skype: gregn1 > (authorization required, add me to your contacts list first) > If we haven't been in touch before, e-mail me before adding me to your > contacts. > > -- > Free domains: http://www.eu.org/ or mail dns-mana...@eu.org > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng > ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Migration to devuan Jessie failed on rpi-zero
On 08/02/16 14:18, Gregory Nowak wrote: On Mon, Feb 08, 2016 at 01:27:19PM +1100, Simon Wise wrote: raspbian is in between armel and armhf because debian armel is (or was then) compiled without hard float support while debian armhf is compiled for arm7 ... so since PIs are arm6 with FPU neither is suitable Just to be clear, the rpi2 is based on a ARMv7. My rpi2 is running devuan jessie nicely, as I have posted here a few months ago. The RPi2 is a quite different beast, the OP was about the original chip. Raspbian wheezy has lots of specific stuff for them, and a lot of work went into it. I have found that compiling anything not in it from source is the way to go. It can also be used by experienced people willing to put time into making a single purpose kiosk style setup. But anyone hoping for a cheap, open general computer will be frustrated. It is quite a good learning tool though, since the community is big and helpful. I think that depends on what one expects. If someone gets one of these, and hopes it can replace a modern desktop/laptop, then that person will indeed be frustrated. I wanted to use mine as a router possibly running i2p and freenet as well, and I thought when I was getting it I had a good understanding of its limitations. It does the router part very well as I expected. It ran i2p well enough also, though I have since transferred that to my laptop for reasons unrelated to performance. The freenet node ran fine when it was idle. However putting some downloads in the queue made the freenet node slow to respond, and it crashed once a day or so.. I had hoped all of that would be otherwise, but am not surprised by the reality of things. The main job for my rpi2 is to be a router, and it does that very well so far. Yes, just the kind of use-case by someone experienced in the task that they are great for. I have a few on the shelf in front of me now, but haven't used them for a while. Simon ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Dng Digest, Vol 17, Issue 39
On 08/02/16 09:09, KatolaZ wrote: On Sun, Feb 07, 2016 at 10:49:48PM +0100, Arnt Karlsen wrote: [cut] If it is inly a matter of recompiling for armhf with the arm6 flag, shall we try to put together a devuan for arm6? ..yup, and it is worth the while starting from the Raspian Wheezy flavor a year ago, rather than todays Raspian Jessie. I have one of each ready for guinea pig service. ;o) The problem is that the old Raspbian wheezy won't boot on pi0, due to a firmware problem (I tried that one before trying the tainted jessie, obviously...). There is a workaround though, which consists on upgrading the firmware to the newest version from a pi1 or a pi2, but I haven't tried it. I really would like to have a devuan armhf port compiled for arm6, to get advantage of the FPU. Honestly, it has been a long time since I had the whole toolchain installed to cross-compile for arm, but this would probably be worth the effort, and convince me to travel a few years back in time. There are a lot of people out there using pis, and some are already complaining about systemd, and many would love a pi-vuan. Any volunteers around? :) I have a B and a B+ here, though too busy with some other projects to dedicate serious time to it at the moment I could set them up to build packages at least. Now they run raspbian wheezy, the B+ with a different kernel to run a nice sound card. Depending on the ambition simply dropping any of the systemd dependent gnome and desktop stuff would make sense for these old models, they need a very light desktop, preferably none. I have used them as media players, directly to the graphics not via X. Networking is weak, the A or the zero might be better since they do not add the crappy usb chip but rather expose the tablet-style usb directly, so may work better with appropriate usb network dongles. But I have not tested this, maybe I should get a zero. The new rpi2 is not useful to me since it seems that the way the cores and threading are managed is not good for audio throughput at all, but maybe messing around and locking cores and process etc may achieve something??? Wheezy was set up by default to boot in a very manual way, the recommended place to add services from was often rc.local, so maybe a similar approach was taken in Jessie. But I have not looked at it. Simon ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Migration to devuan Jessie failed on rpi-zero
On Mon, Feb 08, 2016 at 01:27:19PM +1100, Simon Wise wrote: > >>My understanding is that both the rpi0 and rpi1 are based on a ARMv6 > >>chip, which makes them closer to armel than to armhf. So, I'm afraid > >>you're stuck with raspbian for now. > > raspbian is in between armel and armhf because debian armel is (or was then) > compiled without hard float support while debian armhf is compiled for arm7 > ... so since PIs are arm6 with FPU neither is suitable ... raspbian is > compiled to suit PIs. Actually, armel _is_ perfectly suitable, just a bit slower. However, rapbian guys wanted to use all the computing power of pi's CPU, and thus used a debased version of armhf. They really should have named the architecture different. -- A tit a day keeps the vet away. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Migration to devuan Jessie failed on rpi-zero
On 08/02/16 17:35, Adam Borowski wrote: On Mon, Feb 08, 2016 at 01:27:19PM +1100, Simon Wise wrote: My understanding is that both the rpi0 and rpi1 are based on a ARMv6 chip, which makes them closer to armel than to armhf. So, I'm afraid you're stuck with raspbian for now. raspbian is in between armel and armhf because debian armel is (or was then) compiled without hard float support while debian armhf is compiled for arm7 ... so since PIs are arm6 with FPU neither is suitable ... raspbian is compiled to suit PIs. Actually, armel _is_ perfectly suitable, just a bit slower. However, rapbian guys wanted to use all the computing power of pi's CPU, and thus used a debased version of armhf. They really should have named the architecture different. They certainly could not do anything useful for me without hard float! simon ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Easynetaid is for now netman's new name
El 08/02/16 a las 07:35, Hendrik Boom escribió: On Sun, Feb 07, 2016 at 02:00:26PM +0100, Edward Bartolo wrote: >Hi, > >I did all necessary changes in the netman project to rename it to: >"easynetaid" which is unique on google. That is a good name. Simple, unique, and descriptive. I wish all names were as good. I also like it :) Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
