If it's already dual boot and you're adding another OS, couldn't you just make a new entry in the existing boot menu?

You could let it install grub and then switch to extlinux. When I did that, it was easy. I didn't set it up for multiple systems, but I do use syslinux on multiboot live-usb frequently, but those are all on the same partition. I'm not sure what happens when you want to boot from different partitions.

At the slim login screen, press F1 to toggle different window managers.

Re-reading this thread...

If the motherboard is set to uefi, it will look for bootloaders on the efi partition, which must be fat32 with esp and boot flags. If you use the version of refractainstaller currently in ascii, it will complain if there's no proper efi partition, and if there's more than one, it will give you a choice of which one to use. (Which may or may not be the one your motherboard chooses to use.)

Are you using one of the isos I made with the ascii-backports kernel? (I think it was 4.12 or 4.13.) Ryzen needs newer kernels than the stock ascii kernel.

If it turns out that your hardware won't let you boot from the nvme disk, you could probably just move the /boot dir to its own partition on a sata drive. Or maybe it only wants the efi partition on a different drive. (Just making guesses here.)

And if you're using gpt partitioning with legacy boot, you need to make a special partition, >1MB unformatted, with bios_grub flag (in gparted) or ef02 (in gdisk), otherwise grub-install will fail.

init 1 then ctrl-d might take the place of a reboot.

If you have too many deer, you should invite some to dinner. (Assuming you have a big freezer.)

At the grub boot menu, press e to edit. Add a line before the linux line with the desired resolution. On my laptop, I have to use:

set gfxpayload=1366x768

Then ctrl-x to boot.

If you want it to be permanent, plug the live-usb into a running system and edit boot/grub/grub.cfg to add the resolution. You could use the above line in selected menuentries, or you could set it for all of them as I do in the example below. All the individual menuentries (not shown) have "set gfxpayload=keep".

if loadfont $prefix/font.pf2 ; then
  set gfxmode=1366x768
  insmod efi_gop
  insmod efi_uga
  insmod video_bochs
  insmod video_cirrus
  insmod gfxterm
  insmod jpeg
  insmod png
  terminal_output gfxterm
fi

background_image /boot/grub/splash.png
set menu_color_normal=light-gray/black
set menu_color_highlight=white/black
set timeout=15
<snip>

If you boot with the right resolution, and the graphical refractainstaller still has buttons off-screen, it may be a gtk2/gtk3 problem. Let me know if that's the case. (I've only seen that with refractasnapshot.) One way around that is to use the cli refractainstaller. The other way is to use yad compiled for gtk2 - http://distro.ibiblio.org/refracta/file … _packages/

DO NOT CHANGE ANYTHING IN MXLINUX!

We gave you several easy ways to be able to access mxlinux file from devuan. If you want it to work in devuan the same as it works in mxlinux, we need more information. (And it will probably be more complicated.)

What desktop environment, display manager and file manager does mxlinux use?
What desktop environment, display manager and file manager is installed in devuan?

That looks correct. You can confirm that it's mxlinux by looking in /mnt/home/keos and recognizing files in your mx home. Or look at other files under /mnt that you can identify as mx files, or run 'mount' or 'df -h' to show that the right partitions are mounted in the right place.

What does "without any result" mean? Again, what's the output of df -h?

I don't know anyone who has used extlinux/syslinux/isolinux for uefi boot.

I have used grub2 with uefi in a multiboot situation, and it's pretty easy once you see what's going on. Each OS will add a directory with a bootloader to the efi partition. You can see the order of the bootloaders by running 'efibootmgr'. Whichever one is first in the boot order will be used to boot the system. Whichever one you installed last will be the first in the boot order.

If you have more than one linux system, boot the first one and add the second linux to the boot menu. (Run update-grub in debian-based systems.) If you let devuan be in charge of booting, you can boot slackware from devuan's grub menu just like you'd boot windows from the grub menu. No need to use elilo.

There might be a way to use elilo and let devuan boot from the slackware menu, but I don't know elilo at all.

If there's a kernel upgrade, you may need to update the boot menu. This will happen automatically in devuan. If devuan is managing the boot, and you have a kernel upgrade in slackware, you may need to run update-grub in devuan again. (unless your grub entry for slackware uses a constant name for the kernel and initrd, such as /vmlinuz and /initrd.img)

The general recommendataion against using outside repos is because they haven't been tested with devuan. If that repo contains programs or libraries that require versions that aren't in devuan, you could end up with a big mess of dependency problems. Since you might be the first one trying this, take good notes and let us know how it goes.

Here's a good reference for uefi bootloaders (including rEFInd, which is another possibility.)
http://www.rodsbooks.com/efi-bootloaders/index.html

rxvt is a dummy package. With both rxvt and rxvt-unicode installed, this is what I see. (in jessie and ascii)
rxvt runs rxvt-xterm, and rxvt-unicode runs urxvt.

ls -l /usr/bin/*rxvt*
lrwxrwxrwx 1 root root      22 Jun  3 16:10 /usr/bin/rxvt -> /etc/alternatives/rxvt
lrwxrwxrwx 1 root root       5 Aug 15  2014 /usr/bin/rxvt-unicode -> urxvt
-rwxr-sr-x 1 root utmp  196232 Jul 30  2014 /usr/bin/rxvt-xpm
-rwxr-sr-x 1 root utmp  138680 Jul 30  2014 /usr/bin/rxvt-xterm
-rwxr-sr-x 1 root utmp 1312280 Aug 15  2014 /usr/bin/urxvt
-rwxr-xr-x 1 root root   72688 Aug 15  2014 /usr/bin/urxvtc
-rwxr-xr-x 1 root root      86 Aug 15  2014 /usr/bin/urxvtcd
-rwxr-sr-x 1 root utmp 1320536 Aug 15  2014 /usr/bin/urxvtd

ls -l /etc/alternatives/*rxvt*
lrwxrwxrwx 1 root root 19 Jun  3 16:10 /etc/alternatives/rxvt -> /usr/bin/rxvt-xterm
lrwxrwxrwx 1 root root 35 Jun  3 16:10 /etc/alternatives/rxvt.1.gz -> /usr/share/man/man1/rxvt-xterm.1.gz

With only rxvt-unicode installed, I see the following:
Both rxvt and rxvt-unicode will run urxvt.

ls -l /usr/bin/*rxvt*
lrwxrwxrwx 1 root root      22 Jun  3 16:10 /usr/bin/rxvt -> /etc/alternatives/rxvt
lrwxrwxrwx 1 root root       5 Aug 15  2014 /usr/bin/rxvt-unicode -> urxvt
-rwxr-sr-x 1 root utmp 1312280 Aug 15  2014 /usr/bin/urxvt
-rwxr-xr-x 1 root root   72688 Aug 15  2014 /usr/bin/urxvtc
-rwxr-xr-x 1 root root      86 Aug 15  2014 /usr/bin/urxvtcd
-rwxr-sr-x 1 root utmp 1320536 Aug 15  2014 /usr/bin/urxvtd

ls -l /etc/alternatives/*rxvt*
lrwxrwxrwx 1 root root 14 Jun  3 16:23 /etc/alternatives/rxvt -> /usr/bin/urxvt
lrwxrwxrwx 1 root root 30 Jun  3 16:23 /etc/alternatives/rxvt.1.gz -> /usr/share/man/man1/urxvt.1.gz

I think you want to choose rxvt-xterm for your alternative. If that's not a choice, installing rxvt should provide it.

This is what I'm getting on a desktop-live iso that I made a few weeks ago.

Distributor ID:	Devuan
Description:	Devuan GNU/Linux testing/unstable
Release:	testing/unstable
Codename:	n/a

Get:1 http://pkgmaster.devuan.org/merged ascii InRelease [22.2 kB]
Get:2 http://pkgmaster.devuan.org/merged ascii-updates InRelease [22.2 kB]
Get:3 http://pkgmaster.devuan.org/merged ascii-security InRelease [21.6 kB]
Get:4 http://pkgmaster.devuan.org/merged ascii/main amd64 Packages [7,239 kB]
Get:5 http://pkgmaster.devuan.org/merged ascii-security/main amd64 Packages [357 kB]
Fetched 7,662 kB in 5s (1,525 kB/s)
Reading package lists...

After update/dist-upgrade

Distributor ID:	Devuan
Description:	Devuan GNU/Linux 2.0 (ascii)
Release:	2.0
Codename:	ascii

After adding beowulf and doing another update

Distributor ID:	Devuan
Description:	Devuan GNU/Linux 3.0 (n/a)
Release:	3.0
Codename:	n/a

I don't know where your 9 is coming from. I've got a 9 in /etc/debian_version, but it doesn't seem to be interfering.

/etc/devuan_version says "ascii/ceres"
/etc/issue says "Devuan GNU/Linux ascii/ceres \n \l"

/etc/os-release

PRETTY_NAME="Devuan GNU/Linux ascii/ceres"
NAME="Devuan GNU/Linux"
ID=devuan
HOME_URL="https://www.devuan.org/"
SUPPORT_URL="https://www.devuan.org/support/"
BUG_REPORT_URL="https://bugs.devuan.org/"

I don't know where else to look.

@fungus: I didn't edit any relase files, if that's what you were thinking. I might have added the beowulf line and not run an update until after the change.

You do not need to be root to use pmount.

Make sure you're a member of the plugdev group. Run groups to see what groups you're in. If plugdev is not listed, then run as root, adduser keos plugdev

Then the user must log out and log in again.

I'm not implying anything, and there's nothing in my posts to even remotely suggest that. Most of this thread consists of reporting and comparing observations, with documentation. This is normal problem-solving behavior. Jumping to conclusions doesn't solve anything.

jimmyjhn suggested in his last post that there was a recent change in the repo. He's right.
Here's the answer: https://dev1galaxy.org/viewtopic.php?pid=9636#p9636

I can also state that I recall someone bringing this to our attention in irc a few days ago.