The officially official Devuan Forum!

You are not logged in.

#1 Re: Desktop and Multimedia » PulseAudio always resets to mute » 2024-07-14 12:07:49

@alexkemp; late evening perhaps smile
Please check /etc/default/dbus again (which indeed is different from  /etc/init.d/dbus).

#2 Re: Devuan » require rDNS for senders » 2024-07-10 10:02:55

I had a quick look and apparently neither of mx1 or mx2 of your domain are in the domain's spf.
Aren't those the mailout hosts? Or should spf include an "a" or its ip to indicate itself, if that's your mailout host (and host ...7 doesn't have rdns)

#3 Re: Desktop and Multimedia » Dhcpdiscover freezes boot, when there is no wifi network » 2024-07-09 20:43:49

You might want to use the following setup variant:
First, create or edit  /etc/wpa_supplicant/wpa_supplicant.conf to have 2 initial lines like this:

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev

Secondly, change /etc/network/interfaces for wlan0 to read like this

auto wlan0
iface wlan0 inet manual
    wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp

Thirdly, add the user to the group netdev.

Then that user can operate the wlan0 connection with wpagui (which you might need to install), and all details for networks that they connect to gets saved in /etc/wpa_supplicant/wpa_supplicant.conf, to be autimatically re-used upon roaming... (it's also possble for you to enter that beforehand with a text editor, but the file is also updated by wpa_supplicant. See man wpa_action for details).

EDIT: Note that there are two iface blocks for wireless in this setup. Firstly the wlan0 block that registers it to wpa_supplicant via the wpa_roam setting, telling the name of the connection database file to use. Secondly a default block that wpa_action uses for configuring the interface. Note that "default" is the name of that block.

EDIT 2: Technically this solves the issue of running a dhcp attempt too early to the wrong network by  the wireless setup being broken up into two phases. The first phase happens on boot, where the interface is brought up to link level. That enables wpa_supplicant to scan for available networks. The interface is thereafter raised to ip level when wpa_supplicant discovers a network it has connection details for, and then dhcp is used (as configured by the default iface block) with the approrpiate link encryption for aquiring the network address(s) etc.

This setup also allows for static (rather than dhcp) network configurations to be made for individual networks. You do that by other specially named iface blocks to identify the concerned connections. See the man page if you need that.

#4 Re: Other Issues » [SOLVED] no fix for CVE regreSSHion on armhf? » 2024-07-08 12:28:35

Yes, the files in /var/lib/apt/lists are the package index files, and the Priority in those is a categorical grouping of packages that is something different from Pin-Priority.

(see my previous reply that overlapped yours)

#5 Re: Other Issues » [SOLVED] no fix for CVE regreSSHion on armhf? » 2024-07-08 12:17:30

Sorry, I replied before I saw your edit... hmm.

According to man apt_preferences there is an automatic priority of 990 to the versions that belong to the "target release", which would be declared in /etc/apt/apt.conf or some file in /etc/apt/apt.conf.d by a line like APT::Default-Release "stable";
Comment out that line (with initial #)

#6 Re: Other Issues » [SOLVED] no fix for CVE regreSSHion on armhf? » 2024-07-08 12:09:38

You have an explicit Pin-Priority of 990 for daedalus in some /etc/apt/preferences.d/* file.

#7 Re: Other Issues » [SOLVED] no fix for CVE regreSSHion on armhf? » 2024-07-08 11:55:10

Use apt-mark showhold to check if it's held or not.

/etc/apt/preferences.conf and files in /etc/apt/preferences.d/ define preferences.

And apt-cache policy openssh-server would tell about pinning as well.

#8 Re: Other Issues » [SOLVED] no fix for CVE regreSSHion on armhf? » 2024-07-08 11:42:11

Pointing your broswer at you'll see all currently available versions of the package and the repository points they are found in.

Do you have a hold on the package, or some blocking preferences? It should update.

See also for some new and relevant information.

EDIT: hmm pkginfo favours amd64 ... that might not be ideal for you...
however, armhf has the same versions in the same repositories, at least for openssh-server.

#9 Re: Other Issues » [SOLVED] no fix for CVE regreSSHion on armhf? » 2024-07-08 05:22:11

You may want to include daedalus-proposed-updates in your sources.list
as well as daedalus-security

#11 Re: Hardware & System Configuration » Looking for the RIGHT way to create a bridge » 2024-07-06 23:24:43

With ifupdown, bridges get set up by the /etc/network/if-pre-up.d/bridge script when that script detects that the iface block has a bridge_ports setting. That script is provided by the bridge-utils package which nowadays is "optional", so perhaps it's not installed?

Bridges are of course available as kernel networking elements regardless of that package, and the ip command operates on the kernel elements.

Generally speaking, the ifup and ifdown commands are tunable and extensible by means of scripts/programs in the /etc/network/if-* directories which all get invoked when interfaces are brought up or down by those commands. See man interfaces for more.

The ip command only operates on the kernel's networking setup and it does not make use of ifupdown. It's rather the opposite, that ifupdown scripts (and built-in functions) make use of ip to effectuate declared configurations.

#12 Re: Installation » Installer with AMD Graphics » 2024-06-30 08:12:32

At the boot screen, push TAB for editng the boot command line, then left-arrow to move to the vga=788 parameter and change that to a vga=785 parameter, then push enter to start booting the installer. By that you have changed the VGA mode from 800x600 to 640x480 which is the old, traditional default resolution for VGA monitors. You may also search the web for other VGA resolution codes that might possibly work for your monitor, if it's wort the trouble. There is also the possibility to use the parameter vga=ask although that typically dumps too many screenfulls of codes to be useful.

#13 Re: Installation » How to install devuan lxc-container on debian? » 2024-06-26 13:47:18

You need to use Devuan's debootstrap (not Debian's).

#14 Re: Off-topic » The Joke Thread » 2024-06-20 22:08:13

I like the way you put deep and serious thought into a Joke Thread.
Quite agreeable since serious thought is fun! smile
And yet contrary to the topic.
Which I guess is one of the 7 styles of jokes

#15 Re: Installation » Choosing hotplug handler during installation » 2024-06-20 11:02:38

Thanks, I think it does require coding though.

Generally a debconf dialog (set) is driven by a control script (typically an sh (dash) script) with successions of dialog building "commands", possibly in groups with intermediate decision logic. In this case it might be simply a single dialog for asking whether to use eudev or vdev, although designed so as to allow for expansion with further options. Then there would also be code for effectuating the choice at the appropriate time during an installation. I haven't thought about it in detail.

The debconf subsystem kicks in during package installation just prior to the processing of the postinst script. Thus this choice dialog software would be made as a package to be "automatically" installed so it then brings up the dialog. This would be similar to other debconf dialogs, and that is really the reason for implementing within that paradigm. I suppose the point is to fit it into the current installer framework which therefore requires a bit of learning about that framework.

There is also a point in that "hotplug handling" is kind of a forgotten concept area where a single solution (udev) has become unduly dominant whilst having grown into a rather opaque complexity. Perhaps one would be better off with something less opaque and complex?

#17 Re: Off-topic » The Joke Thread » 2024-06-18 20:41:28

Have we found the bottom now?
Or should I be less pessimistic?
Maybe jokes can always be worse...

#18 Re: Installation » Choosing hotplug handler during installation » 2024-06-16 23:08:50

NOTE: the above post was taken out of the GNIinOS thread as it was rather off topic there.

But the project idea remains.

#19 Installation » Choosing hotplug handler during installation » 2024-06-15 22:42:04

Replies: 6

Yes, Great! Thanks, Aitor.

The most recent excalibur preview iso still uses the home-cooked "just in case" method as basis for the driver module loading; slightly improved from the daedalus isos' "all, whatever" method, but it still lacks the subsequent hotplug handling to better guarantee proper handling of less common h/w.

And then, I was secondly thinking of the prospect of a later additional debconf dialog (set) that would also offer  a "vdev or eudev" choice for the installed system. This idea is just a twinkling in the back of my mind atm as I'm not at all sure about dependency ramifications. It would be a fairly fundamental policy choice that would have some impact for all of the desktop installs.

Actually, anyone looking for an isolated Devuan project with high utility as well as deeply satisfying as cognitive challenge, but with well-defined technical boundaries and likely comfortably small in terms of final code line count (in short: Fun!), should make themselves known; I'd be happy guiding you over the shallow end of that pool.

#21 Re: Installation » [SOLVED] How to force the ESP partition to be formatted at installation ? » 2024-06-15 01:06:51

I don't have your setup so can't say for sure, but experimented a little with the installer's partitioning dialogs.

It sure does seem that the partman developers try to be clever about the "EFI System Partition" and exclude the offer to erase a pre-existing ESP.

So instead you'll need to fiddle with the shell at that point, which of course is far from ideal. Basically enter the shell with C-A-F2 and erase the partition with dd.

#22 Re: Installation » daedalus: network interface names changing with (nearly) each boot » 2024-06-15 00:03:48

A good alternative would be to install and use ifrename. Possibly easier and safer. You would then pick your own name series and declare the mapping from PCI bus addresses to your names.

Install and check out its man pages (ifrename and iftab).

EDIT: with ifrename you would not have add that boot parameter.

#23 Re: Other Issues » Shaping script wondershaper seems FUBAR » 2024-06-12 22:26:16

The traffic shaping uses cbp and sfq (which are the queue types used) so you'll need the modules.

#24 Re: Installation » [SOLVED] Migrating Rackspace Bookworm to Daedalus? » 2024-06-11 22:58:49

Hmm. It then appears is unreliable.(?)
Never mind; good it all works for you.

#25 Re: Installation » [SOLVED] Migrating Rackspace Bookworm to Daedalus? » 2024-06-11 20:58:58

eth0 etc is the name of the interface assigned by the kernel module. All the rest are done afterwards, typically via udev rule(s). It may have been due to that eventually (with bookworm) udev has got programmed to generate specific naming rules for itself into /etc/udev/rules.d/ that then apply subsequently regardless of boot options. It requires a bit of "surgery" of the udev rules to get rid of that.

There is a web site,, where one can search for details about debian packages. net-tools does exist in bookworm (version 2.10-0.1) so apparently Rackspace applies some "we know best" filter on package availabiility. I would choose some other mirror.

Board footer

Forum Software