If you do nothing at the boot menu, you will get the first item, which is desktop-live i386. The system is set for automatic login, so if you got a login screen, something is wrong.

What kind of instructions would you like? There's not much to say. Just dd the image to a usb stick, boot the stick and choose a system. If you want to install one of those systems, it's probably better to download one of the 2.1 isos, because they are newer.

I don't forsee any immediate changes. Yesterday's vote leaves us in a slightly better position than before. There was no commitment at all to work with us. Now there is.

It wasn't my favorite proposal, but it's something we can work with. It could have been worse.

I think the first thing to try would be the backports kernel. That's easy to do or undo, and it won't hurt anything. I'd try it with the ascii version of the xserver package.

The only difference I can find between the jessie version and ceres version of xserver-xorg-input-wacom is in the wacom.conf file. There's no difference between the ascii and ceres versions of 70-wacom.conf.

The udev rules file is the same (jessie/ceres), and the pkgconfig file was moved and is only different in the version listed within.

(jessie) -xserver-xorg-input-wacom: /usr/share/X11/xorg.conf.d/50-wacom.conf
(ceres) +xserver-xorg-input-wacom: /usr/share/X11/xorg.conf.d/70-wacom.conf

Sorry I don't know what to do with this information, but here are the diffs.

$ diff -u 50-wacom.conf 70-wacom.conf 
--- 50-wacom.conf	2019-12-26 11:19:49.159183000 -0500
+++ 70-wacom.conf	2019-12-26 11:21:26.183183000 -0500
@@ -1,24 +1,69 @@
+# Some of the below input classes appear 3x times, once for each of
+# "tablet", "touchscreen", and "touchpad" to ensure that the Wacom
+# driver is not accidentally bound to other types of hardware that
+# Wacom has made which are not handled by the wacom driver (e.g the
+# Wacom Bluetooth Keyboard)
+#
+# https://sourceforge.net/p/linuxwacom/bugs/294/
+
 Section "InputClass"
-        Identifier "Wacom USB device class"
+        Identifier "Wacom USB tablet class"
         MatchUSBID "056a:*"
         MatchDevicePath "/dev/input/event*"
+        MatchIsTablet "true"
         Driver "wacom"
 EndSection
 
 Section "InputClass"
-        Identifier "Wacom PnP device class"
-        MatchPnPID "WACf*|WCOM*|WACM*|FUJ02e5|FUJ02e7|FUJ02e9"
+        Identifier "Wacom USB touchscreen class"
+        MatchUSBID "056a:*"
         MatchDevicePath "/dev/input/event*"
+        MatchIsTouchscreen "true"
         Driver "wacom"
 EndSection
 
 Section "InputClass"
-	Identifier "Wacom class"
+        Identifier "Wacom USB touchpad class"
+        MatchUSBID "056a:*"
+        MatchDevicePath "/dev/input/event*"
+        MatchIsTouchpad "true"
+        Driver "wacom"
+EndSection
+
+Section "InputClass"
+	Identifier "Wacom tablet class"
+	MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
+	MatchDevicePath "/dev/input/event*"
+	MatchIsTablet "true"
+	Driver "wacom"
+EndSection
+
+Section "InputClass"
+	Identifier "Wacom touchscreen class"
+	MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
+	MatchDevicePath "/dev/input/event*"
+	MatchIsTouchscreen "true"
+	Driver "wacom"
+EndSection
+
+Section "InputClass"
+	Identifier "Wacom touchpad class"
 	MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
 	MatchDevicePath "/dev/input/event*"
+	MatchIsTouchpad "true"
 	Driver "wacom"
 EndSection
 
+# Serial Wacom devices should always be one of tablet, touchscreen, or
+# touchpad so we can safely get away with just one match section in
+# these cases
+Section "InputClass"
+        Identifier "Wacom PnP device class"
+        MatchPnPID "WACf*|WCOM*|WACM*|FUJ02e5|FUJ02e7|FUJ02e9"
+        MatchDevicePath "/dev/input/event*"
+        Driver "wacom"
+EndSection
+
 Section "InputClass"
 	Identifier "Wacom serial class"
 	MatchProduct "Serial Wacom Tablet"
@@ -56,4 +101,3 @@
 	Driver "wacom"
 	Option "Button2" "3"
 EndSection
-

"Install bootloader" would have been the right choice.
https://devuan.org/os/documentation/ins … dl18.2.png

You can either reinstall or else boot the live, chroot the installed system and run grub-install && update-grub

Here's the link to the full install guide:
https://devuan.org/os/documentation/ins … e-gui.html

My recommendation is not impartial, and I won't try to debug unetbootin. Use my software to make a multi-boot usb.
refracta2usb download - https://sourceforge.net/projects/refrac … b/download
Instructions (at least read the Quick Start!) - https://refracta.org/docs/readme.refracta2usb.txt

It uses isolinux/syslinux. If you want grub bootloader on it, we can change it to that later.

Thanks for finding that!

There's a new version in ascii-proposed with the fix. (3.2.2-17)  Please test and report.

I'm not clear on what this means:

Try adding --force-downgrade

I use optical media, too. Any directories under /media that are needed get created automatically. I think udev takes care of that.

To preserve any directories you made under /media, take a look at the rsync excludes list (/usr/lib/refractasnapshot/snapshot_exclude.list) and comment out one or more of the following lines, as needed.
Like this:

#- /cdrom/*
#- /media/*

Do the same with /usr/lib/refractainstaller/installer_exclude.list

To add a line to fstab in the installer, you just need to add this line:

echo -e "/dev/sr0\t/media/cdrom\tauto\tnoauto,owner,ro,users\t0\t0" >> /target/etc/fstab

You can put it right after the section that adds the swap line to fstab. That section starts around line 1430 in /usr/bin/refractainstaller and around line 1570 in /usr/bin/refractainstaller-yad. The last two lines in the following code block are what you need to add.

# add entry for swap to fstab if needed
if [[ $use_existing_swap = "yes" ]] ; then
        if [[ $use_uuid = yes ]]; then
                swap_part="$(/sbin/blkid -s UUID $swap_dev | awk '{ print $2 }' | sed 's/\"//g')"
        else
                swap_part="$swap_dev"
        fi
        echo -e $"\n Adding swap entry to fstab...\n"
        echo -e "$swap_part\tswap\tswap\tdefaults\t0\t0" >> /target/etc/fstab
else
        echo -e "/swapfile\tswap\tswap\tdefaults\t0\t0" >> /target/etc/fstab
fi

# Make entry for cdrom in fstab
echo -e "/dev/sr0\t/media/cdrom\tauto\tnoauto,owner,ro,users\t0\t0" >> /target/etc/fstab

Oh yeah, I didn't think of that. Once you get everthing set up, you could make a hookscript that will run when you boot the live iso and inject the necessary lines into /etc/fstab. But that won't work for a rescue usb that you're booting on some other box. For that, you might be better off doing it manually in a root terminal. Then you can run fdisk, df and blkid to get information about the partitions and figure out which one you want to mount.  That's my preferred method, even on a box that will let me mount partitions from the desktop.

I can understand why you want to be able to boot an iso for rescue/repair, and I can understand why you want to be able to mount your installed partitions from that live system, but I still don't understand why you need to mount the isos. Are you planning to do frequent editing of the iso's boot menu?

According to the xfe docs here: http://roland65.free.fr/xfe/index.php?page=docs
You can mount filesystems with ctrl-M and unmount with ctrl-U. What I can't figure out is how/where you find these unmounted filesystems. I don't see anything in the preferences about volume management or devices. I can only see mounted filesystems.

Edit: Oh, I'm looking at an older version in jessie. I see this for 1.42, which is the version in ascii: