Are you using ascii or beowulf? Try installing xfce4 in parts instead of with the metapackage, and maybe you'll see what is pulling in pulseaudio. They might have added the dep because there's no more xfce4-mixer.

I know that Refracta ascii does not have pulseaudio installed, so I know it's possible in ascii, and I'm pretty sure it's possible in beowulf.

Looks like that bug only affects systemd. I've been using that version of live-config in ascii and haven't run into problems with it. But what live iso are you using? Both the desktop-live and minimal-live should have refractainstaller installed already. You could use the cli version of the installer and then add vnc to the installed system later.

The inittab in the live session does not contain the line you posted for the getty. It gets changed by /lib/live/config/0160-sysvinit to the following:

1:2345:respawn:/bin/login -f devuan </dev/tty1 >/dev/tty1 2>&1

If you want to change it again, you could make a hook script that runs after the other live-config scripts, but I'm not sure where you could put it without rebuilding the iso. In the refracta8 (jessie) isos, I put a hook script in /live/hooks and then add 'hooks=file:///live/hooks/myscript' to the boot command. (yes, three slashes, and this is from memory, so check man live-config)

Or, if you're going to mount the iso and mess with files, you could just change that live-config script to do what you want.

It's not a known issue. That iso should work on hardware as new as yours. (2008?)

How far into the boot do you get?

Make sure the boot command contains 'username=devuan'.

Maybe try adding 'nomodeset' to the boot command. (That might be in the failsafe entry, which you should also try.)

I didn't put refractsnapshot-gui in the ascii repo because it wasn't working well with gtk3. You might get off-screen buttons in some of the windows. If so, just use the cli version. They are the same. The latest version (10.2.0) at sourceforge (and soon to be in unstable repo) doesn't have this problem. That version also has the fix for isos larger than 4GB. Nevertheless, you should exclude your data if there's any significant amount and use a different method for the data backup.

If you want to make a bootable backup of a non-uefi system, you can ignore the warnings about grub-efi. If you want your iso to be bootable on bios or uefi (in case you want to install on a uefi system) you need to do a few simple things:
- install grub-efi-amd64 and grub-efi-amd64-bin but don't let grub install the bootloader. Tell it NO when it asks.
- include the grub-pc package in the iso. Put it in the root of your filesystem before you make the snapshot. When you get around to installing the system, if you boot on bios, the installer will find the grub-pc iso and install the package. It will also ask if you want the bootloader installed. Most likely, you will want to say YES here.
Note: It's also possible to do the opposite of the above. Keep grub-pc installed, include grub-efi-amd64 and grub-efi-amd64-bin packages, set force_efi=yes in the config file, and make the snapshot. If you boot on a uefi system, the installer will find the grub-efi packages and install them.

If you know you will only install on a bios system, you can do nothing and just ignore the warning. Your iso will not boot on uefi systems.

I haven't tried that yet, but I will let my ceres install take over the boot on this machine. Meanwhile, can you tell me how your grub directory got into the efi partition? The only file I have in any of the efi directories is grubx64.efi. My grub directory is a subdir of /boot, as it has always been.

Good one to know. I never heard of multipath-tools and don't have it installed. Also never used dmsetup commands. Thanks for that!

Here's a video showing how to do what you want to do, except not on a logical partition. It's very easy to get it wrong. (the '4' in the file name means it was my fourth attempt, and I've done it many times before.)
http://distro.ibiblio.org/refracta/misc … rypt-4.ogv

Sorry about that, but we didn't get to choose who left and who didn't. If we did have that power, we would have taken a few more. But it turns out that would not have been necessary - they're coming around eventually. First year, we got all people who didn't want systemd, but as time goes by, we keep getting more people who thought they did want systemd and changed their minds after they got it.

Welcome to devuan.

P.S. Also sorry I didn't see your post a year ago. I don't think I've ever had two installs come out exactly the same with debian-installer.

I don't know how that could happen. Are you making new snapshots or doing this on a persistent partition after making changes? Either of those ways should work.

I don't know the answer. You should be able to make a backup of the whole mmc device if you can read it while windows is not running. You would need to either boot a live-usb or pull out the card and connect it to another computer. Then dd if=/dev/mmcblk0 of=some-file

If you install devuan to the hdd instead, the grub bootloader will go into the efi partition, and it should include the windows system in the boot menu. That is what normally happens. No guarantees with this. Check your bios to make sure you can turn off secure boot.

One solution would be to force eudev to use the new naming scheme. Add 'net.ifnames=1' to the boot command, and you'll get interface names that will not change.