Re: [DNG] Chimaera on Dell Wyse 3040 installs but won't boot
The Dell Wyse 3040 has a broken EFI implementation which requires to install GRUB into the removable media path aka "fallback device location". This option is available in the "expert install" mode of the Devuan Installer. https://blog.roberthallam.org/2020/05/psa-dell-wyse-3040-uses-fallback-efi-location/ Regards, JP ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] vdev in chimaera
Hi Didier, On 7/2/22 19:21, Didier Kryn wrote: If you remove the "allow-hotplug" and "auto" stanzas, ifup -a will just do nothing, hence no wait. Therefore the solution is to install ifplugd or netplug, configure it, and eliminate the "allow-hotplug" stanzas from /etc/network/interfaces. I've found a workaround replacing in the init script: if ifup -a $exclusions $verbose && ifup_hotplug $exclusions $verbose then log_action_end_msg $? else log_action_end_msg $? fi with this: if [ $(runlevel) != "unknown" ] || ! [ -z $(grep '^id:1:initdefault:$' /etc/inittab) ]; then if ifup -a $exclusions $verbose && ifup_hotplug $exclusions $verbose then log_action_end_msg $? else log_action_end_msg $? fi fi which means: "skip these lines if the boot process still has not switched to the default runlevel, unless it is single user". The following script located in /etc/boot.d: #!/bin/sh -e # # networking-restart # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. if test -x /etc/init.d/networking ; then service networking restart fi will restart the service and from this moment, both "auto " and "allow-hotplug " will take effect. This way, the delay will occur only in the case of a single user default runlevel, which is often not the case. Cheers, Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Installing on a Raspberry or a Banana?
On 07-02-2022 22:17, Antony Stone wrote: On Monday 07 February 2022 at 22:14:32, d...@d404.nl wrote: On 07-02-2022 22:03, Antony Stone wrote: I want to install Devuan on a Raspberry Pi Zero W, and also on a Banana Pi R1. Last time I needed an RPi image I used this link https://arm-files.devuan.org/ Oh! Thanks - I didn't spot this linked from any of the "download" or "how to install" pages I looked at. Antony. I did bookmark this link some time ago so I do not know if it is anywhere linked on the site. Golinux maybe? Grtz. Nick ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Installing on a Raspberry or a Banana?
On Monday 07 February 2022 at 22:14:32, d...@d404.nl wrote: > On 07-02-2022 22:03, Antony Stone wrote: > > > > I want to install Devuan on a Raspberry Pi Zero W, and also on a Banana > > Pi R1. > Last time I needed an RPi image I used this link > https://arm-files.devuan.org/ Oh! Thanks - I didn't spot this linked from any of the "download" or "how to install" pages I looked at. Antony. -- "If I've told you once, I've told you a million times - stop exaggerating!" Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Installing on a Raspberry or a Banana?
On 07-02-2022 22:03, Antony Stone wrote: Hi. I'm wondering what has happened to the "embedded" subdirectory which was present under Jessie and Ascii, but no longer seems to exist for Beowulf or Chimaera (or later). I want to install Devuan on a Raspberry Pi Zero W, and also on a Banana Pi R1. Are these still possible? Do I need to start from Ascii and then upgrade on the system itself? Thanks for any pointers. Antony. Last time I needed an RPi image I used this link https://arm-files.devuan.org/ Grtz. Nick ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Menu of applications vanished from lxqt
Hi Hendrik, On 7/2/22 19:38, Hendrik Boom wrote: I believe this started when I did a routine security upgrade, and installed a program to convert markdown files to asciidoc format. You can try moving out converter's .desktop file from /usr/share/applications or /usr/local/share/applications to know whether the origin of the issue is in the installed program, causing the launcher to freeze. On the other hand, if I am not mistaken lxqt uses the openbox window manager, and I assume you aren't starting a window manager session instead of the desktop environment. Cheers, Aitor. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Installing on a Raspberry or a Banana?
Hi. I'm wondering what has happened to the "embedded" subdirectory which was present under Jessie and Ascii, but no longer seems to exist for Beowulf or Chimaera (or later). I want to install Devuan on a Raspberry Pi Zero W, and also on a Banana Pi R1. Are these still possible? Do I need to start from Ascii and then upgrade on the system itself? Thanks for any pointers. Antony. -- Numerous psychological studies over the years have demonstrated that the majority of people genuinely believe they are not like the majority of people. Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Menu of applications vanished from lxqt
Normally, lzqt has an icon baar (which I think they call a panel) It contains icons 1, 2, 3, 4 for the available workspaces, and a few more little squares with icons for a ile manager, a qterminal, and a(I think) an editor. But in fromt of those icons, it normally has another little square. Clicking on that square puts up a menu with sibmenuse for various classes of applications. Starting a day or two ago that little square has been missing. This means that excpet for the applications I just mentioned, I cannot start any applications from lxqt. (Yes there's a workaround -- I can start anything I know the filename of from the command line in a qterminal. But that's not the way a desktop is really supposed to work.) And I can still log out -- if I use control-alt-F1, log in as root, and killall lxqt-session. I believe this started when I did a routine security upgrade, and installed a program to convert markdown files to asciidoc format. Does anyone else have this problem? Anyone know how I can get my menu of applications back? -- hendrik P.S. over the last year I occasionally would lose this menu, but it always came back when I powered down, rebooted, and logged in again. Not this time. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] vdev in chimaera
Le 07/02/2022 à 16:22, fsmithred via Dng a écrit : On 2/7/22 06:35, Didier Kryn wrote: Le 07/02/2022 à 08:29, aitor a écrit : I've uploaded new iso images fixing a bug related to the last change in simple-netaid for compatibility with static ip addresses, that involved the response to routing table netlink events triggered by other processes. The images come with vdev by default. Next step will be to write a runit script for ifupdown that intend to solve the problem of the still remaining (at least booting with vdev) long delayed boot time when using "allow-hotplug " stanzas in /etc/network/interfaces. The long delay is also present with sysvrc. It can be supressed by just removing the "allow-hotplug" line, without replacing it by an "auto" line, and relying on ifplugd or netplug to detect the presence of the carrier and trigger the configuration of the interface. The delay is suppressed because 'ifup -a' does not find any interface to bring up and carrier to wait for; and then ifplugd/netplug brings them up only when the carrier is detected. Dunno if simple-netaid can play the role of ifplugd or netplug. -- Didier I keep updating your check-link-state.patch on /etc/network/interfaces. It seems to still be working with allow-hotplug. The original discussion on DNG is gone, but I saved part of it here: https://dev1galaxy.org/viewtopic.php?pid=15493#p15493 I think the line numbers are right for chimaera, but I always edit this manually. --- networking.orig 2021-11-08 08:47:47.520020285 -0500 +++ patches/networking.patched 2019-12-14 11:13:07.842536000 -0500 @@ -112,7 +112,13 @@ done) if [ -n "$ifaces" ] then - ifup $ifaces "$@" || true + # link detection does not work unless we up the link + ip link set "$iface" up || true + if [ "$(cat /sys/class/net/$link/operstate)" = up ] + then + echo "$iface" + fi + fi fi } Sorry but I doubt that the patch is from me, specially because I'm not familiar (yet) with the ip command, which replaced ifconfig. The problem I met, like most people with a laptop is that I have both eth0 and wlan0. Invoquing ifup -a at boot causes a delay when no Ethernet cable is plugged in, which is the usual situation. This is because ifupdown then waits for the carrier and only gives up after a delay, and only then, brings up wlan0 (given eth0 is listed first in the interfaces file). "allow-hotplug" is meant for network *devices* (not cables) you plug in on the fly, like USB-Ethernet adapters. The word hotplug does not mean that the cable is plugged in/out on the fly. In most cases, "allow-hotplug" is equivalent to "auto". But, when bringing up an interface, ifupdown waits until the carrier is detected or the timeout is expired. When there is no cable, there is no carrier, and the timeout is pretty long. On the other hand, ifplugd or netplug are awakened when the carrier is detected on one of the interfaces they control, and then, they invoke ifup for the interface in question, just when it makes sense. If you remove the "allow-hotplug" and "auto" stanzas, ifup -a will just do nothing, hence no wait. Therefore the solution is to install ifplugd or netplug, configure it, and eliminate the "allow-hotplug" stanzas from /etc/network/interfaces. -- Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Stability will be achieved when you spend all of your time reporting on the nothing you did.
One more thing to note, in about:config you'll notice one of the options is telemetry *server*. Is it possible that firefox is actually 'serving' the telemetry data to sites that request it? Sure seems like the kind of dirty underhanded trick that someone might try. The fact that the data is there leaves that open as a possibility at any point anyway. I might be wrong, but since they've taken away our ability to turn off telemetry (except for about:config), I think it's worth being suspicious of their intent. I'm going to spend a little time this morning learning about telemetry in FF 78. I'll share anything interesting I find. Gabe ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Stability will be achieved when you spend all of your time reporting on the nothing you did.
On Mon, 2022-02-07 at 09:23 -0500, Ken Dibble wrote: > Application: firefox 78.15.0esr > > > URL: about:telemetry#home-tab > > Page contains statement: Telemetry is collecting release data and > upload > is disabled. > > > URL :about:telemetry#histograms-tab > > Page contains seemingly endless amounts of collected data. > > > If this data is supposedly not being uploaded by user preference, > > then why in the H,E,double hockey sticks is so much of it being > collected? Thanks for this headsup. I checked my firefox and noticed that, despite the warning, no data seems to have been collected. I checked about:config and apparently I changed some telemetry related entries there that stopped the data collection. I don't know which setting exactly, but if you go into about:config and search for telemetry you'll get 20 to 30 results. Gabe ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] vdev in chimaera
On 2/7/22 06:35, Didier Kryn wrote: > Le 07/02/2022 à 08:29, aitor a écrit : >> I've uploaded new iso images fixing a bug related to the last change in >> simple-netaid for >> compatibility with static ip addresses, that involved the response to >> routing table netlink >> events triggered by other processes. The images come with vdev by >> default. Next step will be >> to write a runit script for ifupdown that intend to solve the problem of >> the still remaining >> (at least booting with vdev) long delayed boot time when using >> "allow-hotplug " >> stanzas in /etc/network/interfaces. > > The long delay is also present with sysvrc. It can be supressed by > just removing the "allow-hotplug" line, without replacing it by an "auto" > line, and relying on ifplugd or netplug to detect the presence of the > carrier and trigger the configuration of the interface. The delay is > suppressed because 'ifup -a' does not find any interface to bring up and > carrier to wait for; and then ifplugd/netplug brings them up only when the > carrier is detected. Dunno if simple-netaid can play the role of ifplugd > or netplug. > > -- Didier > I keep updating your check-link-state.patch on /etc/network/interfaces. It seems to still be working with allow-hotplug. The original discussion on DNG is gone, but I saved part of it here: https://dev1galaxy.org/viewtopic.php?pid=15493#p15493 I think the line numbers are right for chimaera, but I always edit this manually. --- networking.orig 2021-11-08 08:47:47.520020285 -0500 +++ patches/networking.patched 2019-12-14 11:13:07.842536000 -0500 @@ -112,7 +112,13 @@ done) if [ -n "$ifaces" ] then - ifup $ifaces "$@" || true + # link detection does not work unless we up the link + ip link set "$iface" up || true + if [ "$(cat /sys/class/net/$link/operstate)" = up ] + then + echo "$iface" + fi + fi fi } ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Stability will be achieved when you spend all of your time reporting on the nothing you did.
On Mon, 7 Feb 2022 15:30:33 +0100, Antony wrote in message <202202071530.33269.antony.st...@devuan.open.source.it>: > On Monday 07 February 2022 at 15:23:41, Ken Dibble wrote: > > > Application: firefox 78.15.0esr > > > > URL: about:telemetry#home-tab > > > > Page contains statement: Telemetry is collecting release data and > > upload is disabled. > > > > URL :about:telemetry#histograms-tab > > > > Page contains seemingly endless amounts of collected data. > > > > If this data is supposedly not being uploaded by user preference, > > then why in the H,E,double hockey sticks is so much of it being > > collected? > > Sorry, but in what way is this a Devuan question rather than a > Firefox one? ..me, I read this as an heads-up to the Devuan community on this question to the Firefox (dev?) community on an espionage trap. -- ..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] Stability will be achieved when you spend all of your time reporting on the nothing you did.
On 2/7/22 9:30 AM, Antony Stone wrote: On Monday 07 February 2022 at 15:23:41, Ken Dibble wrote: Application: firefox 78.15.0esr URL: about:telemetry#home-tab Page contains statement: Telemetry is collecting release data and upload is disabled. URL :about:telemetry#histograms-tab Page contains seemingly endless amounts of collected data. If this data is supposedly not being uploaded by user preference, then why in the H,E,double hockey sticks is so much of it being collected? Sorry, but in what way is this a Devuan question rather than a Firefox one? Antony. I apologize. Except for this being the browser supplied under Chimaera, it probably isn't. I just thought the information was of value for Devuan users. I will try and find a Mozilla resource, sorry again for the noise. Ken ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Stability will be achieved when you spend all of your time reporting on the nothing you did.
On Monday 07 February 2022 at 15:23:41, Ken Dibble wrote: > Application: firefox 78.15.0esr > > URL: about:telemetry#home-tab > > Page contains statement: Telemetry is collecting release data and upload > is disabled. > > URL :about:telemetry#histograms-tab > > Page contains seemingly endless amounts of collected data. > > If this data is supposedly not being uploaded by user preference, then why > in the H,E,double hockey sticks is so much of it being collected? Sorry, but in what way is this a Devuan question rather than a Firefox one? Antony. -- Was ist braun, liegt ins Gras, und raucht? Ein Kaminchen... Please reply to the list; please *don't* CC me. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Stability will be achieved when you spend all of your time reporting on the nothing you did.
Application: firefox 78.15.0esr URL: about:telemetry#home-tab Page contains statement: Telemetry is collecting release data and upload is disabled. URL :about:telemetry#histograms-tab Page contains seemingly endless amounts of collected data. If this data is supposedly not being uploaded by user preference, then why in the H,E,double hockey sticks is so much of it being collected? Regards, Ken ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] vdev in chimaera
Le 07/02/2022 à 08:29, aitor a écrit : I've uploaded new iso images fixing a bug related to the last change in simple-netaid for compatibility with static ip addresses, that involved the response to routing table netlink events triggered by other processes. The images come with vdev by default. Next step will be to write a runit script for ifupdown that intend to solve the problem of the still remaining (at least booting with vdev) long delayed boot time when using "allow-hotplug " stanzas in /etc/network/interfaces. The long delay is also present with sysvrc. It can be supressed by just removing the "allow-hotplug" line, without replacing it by an "auto" line, and relying on ifplugd or netplug to detect the presence of the carrier and trigger the configuration of the interface. The delay is suppressed because 'ifup -a' does not find any interface to bring up and carrier to wait for; and then ifplugd/netplug brings them up only when the carrier is detected. Dunno if simple-netaid can play the role of ifplugd or netplug. -- Didier ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] vdev in chimaera
On 2/7/22 01:35, aitor wrote: Hi, On 7/2/22 8:29, aitor wrote: Next step will be to write a runit script for ifupdown that intend to solve the problem of the still remaining (at least booting with vdev) long delayed boot time when using "allow-hotplug " stanzas in /etc/network/interfaces. I have Laurent Bercot's s6 in mind, and shortly i'll give a try to Obarun. Cheers, Aitor. Thank you! ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
