Ok, reading man shutdown may help.

On a side note: If you post command output, it should better be in English. Putting LANG=C infront of a command will achieve that (on a per-command basis).

Apropos compiling: Another web browser (and a rather promising one) that can now be built without dbus is Otter Browser.

See:

• https://github.com/OtterBrowser/otter-b … a775aeda3b

• https://github.com/OtterBrowser/otter-b … 1ec5fccf57

@stierlitz:

First, please use [ code ] tags instead of just [ c ] for code blocks. Thanks.

On topic:

1. Which Devuan distribution are you using? Jessie, ASCII, Beowulf, Ceres?

2. What does apt-cache search cuda give you?

It's not wrong, but as the release notes state, you should rather use deb.devuan.org. It will enable Devuan to do some load balancing. See: https://dev1galaxy.org/viewtopic.php?id=2140

How did you install?

You don't have to change that, obviously. But, for the reason mentioned above, it would be nice if you did. Use backports only if you need a particular package to be newer than the one coming with the stable distribution. If you don't, it's probably the best to comment that line.

https://devuan.org/os/etc/apt/sources.list will give you a clue.

I assume this is because mate-power-manager is currently not available. But that should be fixed soonish.

There is:

/usr/bin/xset s off && /usr/bin/xset -dpms

man xset gives an explanation of what that does.

A few comments on this:

Can this be confirmed by anyone?

That's not exactly right. Devuan installation images use a modified version of the Debian Installer. But this will probably change in the future as there are plans to create a new installer for Devuan.

Installing from a Devuan live system, you will, however, be using Refracta Installer[1]. So, all the installer-related issues mentioned in that review apply to Refracta Installer only, not to Devuan's version of the Debian installer.

Untrue. The installer used by the installation images also offers Btrfs, JFS and XFS. You can even format drives and partitions with FAT16 and FAT32. Refracta Installer might, however, have some limitations here.

Again, this is not true if you don't install from within a live system. Just like the original, Devuan's version of the Debian Installer will let you choose your language and locale in a straightforward and totally non-cryptic manner.

Devuan ships whatever Debian ships, except that packages dependent on systemd are either rebuilt to work without it or simply banned.

Well, that's apparently because task-xfce-desktop will not install an e-mail client and mutt being in the default install. Not a big deal, IMO.

I think it's kind of wrong to name Devuan a "conservative" distribution. It's not about just keeping everything as it is. If it was, why would it offer OpenRC as an alternative to SysVinit, for example?

I'd say there is no decision to be made here, since, just like Debian, Devuan aims to provide a "universal operating system".

----
1 https://files.devuan.org/devuan_ascii/d … README.txt

Well, you wrote that using startx, you get "the full desktop but still no Kb or mouse". This could simply be because the Xserver freezes on start-up and may have nothing to do with your keyboard and mouse at all. You need to read the section "Starting X from a console (TTY)".

Just to clarify: I wasn't asking a question there. I just wrote „apparently“ because I didn't have time to check the changelog for AntoFox's mate-power-manager package and therefore be absolutely sure about my statement. But then, it's pretty obvious that it's providing a modified version of mate-power-manager that doesn't depend on systemd. I've also looked at the changelog now to verify that.

So, mate-power-manager here is a third-party package that has apparently been rebuilt so it won't depend on systemd and network-manager is a genuine Devuan package that has been forked from Debian in order to eliminate the systemd dependency.

Normally, you would have an entry for booting into runlevel 1 in your GRUB boot menu as well. But from your description it seemed like it's not there on your system.

It's actually called "single-user mode". Ubuntu calls it "recovery mode"... (mea culpa)

I would have suggested the same. However, you might want to do yourself the favor of reading the section on "Starting X from a console (TTY)" in the ASCII release notes before you use startx to start X.

Well, maybe not. I've found that throwing out /etc/dhcp/dhclient-exit-hooks.d/ntp will make both of the error messages mentioned above go away. So, the one on boot is obviously also triggered by it. There will, of course, be no automatic handling of ntp restarts on DHCP events if the file is missing.

I've been trying to understand what this script really does and I kind of do. But the ntp_servers_setup function is still a mystery to me. Where does it get the value for $reason? It's simply not defined within the script. And neither are $new_ntp_servers and $old_ntp_servers, which are used in the ntp_servers_setup_add function.

Here's the entire file:

NTP_CONF=/etc/ntp.conf
NTP_DHCP_CONF=/run/ntp.conf.dhcp

ntp_server_restart() {
	invoke-rc.d ntp try-restart
}

ntp_servers_setup_remove() {
	if [ ! -e $NTP_DHCP_CONF ]; then
		return
	fi
	rm -f $NTP_DHCP_CONF
	ntp_server_restart
}

ntp_servers_setup_add() {
	if [ -e $NTP_DHCP_CONF ] && [ "$new_ntp_servers" = "$old_ntp_servers" ]; then
		return
	fi

	if [ -z "$new_ntp_servers" ]; then
		ntp_servers_setup_remove
		return
	fi

	tmp=$(mktemp "$NTP_DHCP_CONF.XXXXXX") || return
	chmod --reference=$NTP_CONF $tmp
	chown --reference=$NTP_CONF $tmp

	(
	  echo "# This file was copied from $NTP_CONF with the server options changed"
	  echo "# to reflect the information sent by the DHCP server.  Any changes made"
	  echo "# here will be lost at the next DHCP event.  Edit $NTP_CONF instead."
	  echo
	  echo "# NTP server entries received from DHCP server"
	  for server in $new_ntp_servers; do
		echo "server $server iburst"
	  done
	  echo
	  sed '/^[[:space:]]*\(server\|peer\|pool\)[[:space:]]/d' $NTP_CONF
	) >>$tmp
	
	mv $tmp $NTP_DHCP_CONF

	ntp_server_restart
}

ntp_servers_setup() {
	case $reason in
		BOUND|RENEW|REBIND|REBOOT)
			ntp_servers_setup_add
			;;
		EXPIRE|FAIL|RELEASE|STOP)
			ntp_servers_setup_remove
			;;
	esac
}

ntp_servers_setup

Does the keyboard respond when you boot the system in recovery mode?

What login manager are you trying to use?

That script seems to be there to make sure NTP is being restarted automatically when bringing up and down network interfaces that get their IP address through DHCP.

I've dug a little deeper and found that it has been part of the ntp package at least since Debian Wheezy. Also, it's identical in the Wheezy and Jessie packages, but has seen minor changes in Stretch.

These are:

1. Line 2 was changed from

NTP_DHCP_CONF=/var/lib/ntp/ntp.conf.dhcp

to

NTP_DHCP_CONF=/run/ntp.conf.dhcp

2. Line 43 was changed from

sed -r -e '/^ *(server|peer).*$/d' $NTP_CONF

to

sed '/^[[:space:]]*\(server\|peer\|pool\)[[:space:]]/d' $NTP_CON

I temporarily replaced the current verison of the file with that from Jessie to see if it would make any difference and it didn't. So, the root of the problem must be somewhere else.