Thanks for doing this write-up, I like it very much and have seen people coming over to Devuan using this post.

Cheers!

I'm not an expert but I think this would do it:

Change --enable-official-branding to --disable-official-branding and rename your package in debian/control to whatever name you like. I think so long as you don't use their artwork and don't call it palemoon you should be fine.

lf I remember the browser will call itself "New Moon" by default. That would seem ok in the meantime, but you'd want to rename eventually I think.

Otherwise just use the mozconfig they provide, but it will limit you to the defaults.

Also Intel looks to have pulled the latest microcode for 2018, so most people have to wait for this to change.

@miroR I've made some initial changes for that and more to follow, please let me know in a couple of days if you find more. A couple of pages are gone now, so I need to try to remember their locations but with any luck I should be able to unbreak most of the links. If you have a git account, I'd appreciate any other feedback you have or opening of issues.

There's a fair bit of reading for the topic(s) but if I understand, there is something wrong with the Ceres APT pinning? I believe in Ceres you won't be able to avoid systemd that way if you use either dbus or xorg, and will have to make do with libsystemd0 being installed (also for ascii in some areas). I am actually considering removing that document, since it's not that useful anymore for that reason.. unless anyone finds it still useful somehow?

As far as full D-Bus removal it's very difficult if you need a fully featured browser from the Devuan repos. Firefox was mentioned mostly because you don't need to have the dbus daemon installed and running, so maybe your suggestion is not to be concerned about features and go with no dbus at all?

The changes to the wiki do seem to be confusing people, what I'll point to.. is that contributors can't easily view the source of those pages with the older location. Just as a note you can update older posts on d1g, but I may have to revert things anyway if enough people are finding it confusing. Does anyone agree with that? It would be good to have some feedback about that.

So you probably can get around the issue by forcing xorg to use only the vesa driver for now. That seems like the best option to me unless you really do need the accelerated driver, at least until you can find a better work-around.

I think the problem with xorg permissions is already known and I noticed there was an update yesterday for the xserver-xorg-legacy package that allows setting permissions for xorg (dpkg-reconfigure xserver-xorg-legacy). Using the console users only setting and starting as root works fine for me.

You seem to have narrowed it down quite a bit there. You only have problems when the intel driver loads so you could try a few work-arounds if you want, like disabling modesetting or maybe try the pci=noacpi boot parameter.

So it's probably the same as this issue.

You could try using noapic or nolapic as a kernel parameter, it's been known to fix some blank screen issues in the past.

Or try with the latest kernel from ascii-backports.

apt-get -t ascii-backports install linux-image-4.13.0-0.bpo.1-amd64

Failing that you could try to use the xorg vesa driver instead of the intel driver.

[Updated post]

Instructions to migrate from Debian are now available here.

It's not available in the Jessie release, but is available in ASCII. In general it's not recommended to mix repos, but you could try apt pinning if you need to this.

See https://wiki.debian.org/AptPreferences

The installer menus make it look complicated, so it's easy to make a mistake there.

Be sure to post /etc/crypttab and /etc/fstab as mentioned. You can just login with your root password at the maintenence shell and do cat /etc/crypttab and cat /etc/fstab.

I think what you're looking for is an x32 port, like Debians x32 port: https://wiki.debian.org/X32Port. It's an unfinished port with not enough interest as far as I can tell.

The closest Devuan has to that is an install from a 32-bit i386 ISO, as there is no x32 port in Devuan.

If you're looking for a simpler system another option is to not support 32-bit in your system, which will make your install simpler and remove some packages.

dpkg --remove-architecture i386
apt-get update
apt-get autoremove --purge

You can remove 32-bit support in the kernel as well if you compile your own.

Give lightdm a try, it has all those buttons/menus etc plus better support upstream vs slim.