Switching to a devuan base would not help antix avoid systemd. In fact, they have some key packages that have been purged of systemd deps that devuan does not have, such as  gvfs-daemons,  and in stretch/ascii there's xserver-xorg.

All those /lib/systemd/ files are from the udev package. They are in devuan, too.

root@devuan:/home/user# uname -a
Linux devuan 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1+deb8u2 (2017-03-07) x86_64 GNU/Linux
root@devuan:/home/user# find / -name systemd*
/lib/systemd
/lib/systemd/systemd-udevd
/lib/systemd/system/systemd-udev-settle.service
/lib/systemd/system/systemd-udevd.service
/lib/systemd/system/sockets.target.wants/systemd-udevd-kernel.socket
/lib/systemd/system/sockets.target.wants/systemd-udevd-control.socket
/lib/systemd/system/sysinit.target.wants/systemd-udevd.service
/lib/systemd/system/sysinit.target.wants/systemd-udev-trigger.service
/lib/systemd/system/systemd-udevd-kernel.socket
/lib/systemd/system/systemd-udevd-control.socket
/lib/systemd/system/systemd-udev-trigger.service
/etc/systemd
/usr/share/man/man8/systemd-udevd-control.socket.8.gz
/usr/share/man/man8/systemd-udevd.8.gz
/usr/share/man/man8/systemd-udevd.service.8.gz
/usr/share/man/man8/systemd-udevd-kernel.socket.8.gz
/var/lib/systemd

Try this one in antix and see what you get:

root@devuan:/home/user# dpkg -l | grep systemd
ii  libsystemd0:amd64                     215-17+deb8u6                        amd64        systemd utility library

F12, F8, ESC or some other key might get you to a boot device menu where you can choose the usb.

The description for prboom says that it's a dummy package for prboom-plus (and server package). What's wrong with the packages that are already in the repo?

apt-cache policy prboom-plus
prboom-plus:
  Installed: (none)
  Candidate: 2:2.5.1.4~svn4403+dfsg1-1
  Version table:
     2:2.5.1.5~svn4462+dfsg1-1+b2 0
        100 http://us.mirror.devuan.org/merged/ ascii/main amd64 Packages
        100 http://auto.mirror.devuan.org/merged/ ceres/main amd64 Packages
     2:2.5.1.4~svn4403+dfsg1-1 0
        500 http://us.mirror.devuan.org/merged/ jessie/main amd64 Packages

Maybe. Seems like a good guess, anyway.  Did you let the installer format the partition again?

Here's the top hit on a search for your error message. Looks like it might be related.
https://bbs.archlinux.org/viewtopic.php?id=213125

Ged, if you have a local repository that's complete enough to contain all you need, I assume that it would work. I think you just need to edit the debootstrap command to point to your own repo. Look in zlibs/bootstrap.

There are several possible locations of isohdpfx.bin. Maybe we should be finding it instead of hard-coding the location. Look at zlibs/iso.

In the isolinux directory, edit menu.cfg to add a line that says "include live.cfg'
and add a file named live.cfg to the same directory with contents

label live
    menu label Live(or some other name)
    kernel /live/vmlinuz
    append initrd=/live/initrd.img boot=live

If you want something other than Graphical Install to be the highlighted choice at the boot menu, remove 'menu default' from gtk.txt and add it to the entry you want to be the default choice.

You won't need a virus scanner for linux until enough people are using linux to make it worthwhile for someone to start writing linux viruses. Clamav is a linux virus scanner, but it is used for finding windows viruses. You would do better to spend your time securing your web browser.

I don't think that process has been formalized yet, but take a look at https://dev1galaxy.org/viewtopic.php?id=549

The reason hardinfo is in devuan is because it is in debian, and the entire debian repo is available, except for a few systemd packages. You can tell which ones we have changed by looking at the version. The devuanized packages say 'devuan' in the version. devuan1 for jessie, devuan2 for ascii.

The webmaster can see the unique ID number found in /etc/popularity-contest.conf. I don't know if that is associated with your IP address or if they are logged separately. Either way, those numbers don't get published. Whether that's a security risk or not might depend on how paranoid you are. And right now, that's not even working correctly in the desktop-live isos - everyone who uses the same iso gets the same number (there are three in total).

If you install from one of the desktop-live isos, you should delete /etc/popularity-contest.conf before running the installer. That way, you will get a unique number and we get more meaningful statistics. To correct it after installing, delete the file and then run 'dpkg-reconfigure popularity-contest'.

Yes. To do it once, press the e key at the boot menu and add it to the linux line.
To make it permanent, add it to the KERNEL_DEFAULT line in /etc/default/grub (where it has "quiet") and then run update-grub.

Error message says "possibly" but there's no doubt about it. You need to exclude rsyslog and include either syslog-ng or busybox-syslogd. When rsyslog for ascii is ready, you can switch back to it. It's also possible to add rsyslog from jessie-backports after the install. I know that works, but I don't know if there are any problems with it. (Tested minimally by me, once.)

You might need to exclude alsa-base, too. There is no such package in ascii.