The 10, 100 and 500 are priority numbers. All except the 500 are there because I pinned those repos at lower priority to prevent accidental install from the wrong repo. However, I haven't actually tested that. I won't share my full sources.list because it would be hazardous for anyone to use it. Including me. It's like that only so I can see what versions are in which release. One of these days I'll need to comment out all but the jessie repos and do another upgrade. Or maybe not - I really want to switch my main system to ascii soon.

I'll delete those posts from that other thread.

I'm sure there were changes upstream from 1.6 to 1.75 in debian. I think the only changes that devuan made to 1.75 was to remove the dependency on libsystemd0, but it may have been more involved than that. The only way to know for sure what changes were made would be to compare the source code of both packages.

One possible simple solution is to try one of the generic drivers. I think you'll find them at the end of the list of drivers when you're adding a printer in the cups admin. (http://localhost:631)

Right now, all the devs are focused on ascii, so getting changes/fixes in jessie or doing anything with wheezy packages is unlikely to happen. There may be a way to get your printer working by editing some cups config files, but I don't know my way around that enough to even give you a hint.

You probably need the netboot files.
https://packages.devuan.org/merged/dist … s/netboot/
https://packages.devuan.org/merged/dist … s/netboot/

The need for nomodeset is fairly common. It depends on the video card. I got a black screen without it on my old nvidia card and a black screen with it on my new nvidia card.

I looked at refractainstaller-uefi and found some errors. It won't see the mmc drive for the grub selection, but it should see it for /, /home and /boot choices. What does fdisk show for the drive's device name? I would expect something like /dev/mmcblk0p1 for the first partition on the first drive. I'd like to know if I need to change my search pattern. Thanks.

If you want to try a corrected version of the script, I can post it somewhere.

In Debian and Devuan (and many other derivatives), runlevels 2-5 are the same.

To disable wicd in all runlevels:

update-rc.d -f wicd remove

To reverse the above:

update-rc.d wicd defaults

Another way to do it is to install sysv-rc-conf and un-check all runlevels on the wicd line. (use arrow keys and space bar)

apt-get install hddtemp libxfcegui4-4 ristretto xfce4-artwork xfce4-battery-plugin...

and any other packages from the autoremoval list that you want to keep. They will then be marked as manually installed.

xclock is part of x11-apps, which has other cool stuff like xeyes and xcalc. That's just there to have something non-essential to kill. Break the line up into multiple lines, and it will make more sense. The numbers set the exit code for each button, the ans="$?" stores the exit code, then you test to see which action to perform based on the exit code.

The second way is easier. The first way should work, but I can never do it correctly.

The devuan live isos are made with live-config and live-boot, same as debian, so the options are the same.

One thing different from the debian-live isos - the current (jessie) devuan-live isos have a pre-configured user, so you should not use "config" or "components" (live-config or live-components) on the command line. If you do use that option, you will only get the components that you named. (i.e. you must name every component that you want. See /var/log/live/config during a live session. That will show you which ones were used.)

If you use the hookscript, it will create a file, /etc/profile.d/zz_locale.sh (or maybe tt_locale.sh) which will contain:

export LANG=fr_FR.UTF-8
export LC_ALL=fr_FR.UTF-8

Every user on the system will get French. If you want only one user to have French, remove that file and put those lines in ~/.profile for that user.

Yes, devuan is following debian releases. Most of the packages in devuan are unchanged from debian. The plan is to change as little as possible to provide a debian-based system without systemd.

I have an lxqt install, and all the logout buttons work. We have the same policykit packages installed (except you included the l10n package). Mine started out as openbox with lxpanel. You have libpam-gnome-keyring. I don't. Other libpam stuff is the same.

Maybe it's in the 'power' packages. I have libupower-glib3 that you don't have, and I see that xfce4-power-manager is running in mine. Not saying you need to do anything about it. All the logout buttons work in your iso. But since so many people run into problems with logout buttons, I figured this was a good place to drop my observations.

Howtos are supposed to go in the Documentation section. It even says so.

There isn't much official documentation yet, but I think the idea was that some of the howtos might develop into official docs.