As per post #3 above, aplay -L | grep -A2 default says that your default output is the PulseAudio sound server, which suggests that you do use pulseaudio, or that you have had pulseaudio and removed it partially. If I remember right, a simple "remove" of pulseaudio only removes the library but not the configuration files, and that those may cause trouble. There are three configuration files to look for and get rid of:

/usr/share/alsa.conf.d/50-pulseaudio.conf
/usr/share/alsa.conf.d/pulse.conf
/usr/share/alsa/pulse-alsa.conf

Once that is done, you may even need an additional alsactl init, so that you get aplay output to be

$ aplay -L | grep -A2 default
-------------------------------------
default
    HDA Intel PCH, ALC3861 Analog
    Default Audio Device
--
sysdefault:CARD=PCH
    HDA Intel PCH, ALC3861 Analog
    Default Audio Device

That is a good place to be at

@Astara: How about you start by revealing the actual name of that file that you somehow downloaded?

You can but the following line in all your ~/.zshrc (or ~/.bashrc perhaps)

function title() { echo -n "\033]0;$1\007"; }

and then use

$ title Bendigo

to change the terminal title. Endless possibilities....

I'm using gocryptfs rather; basically the same function I think, and installable.

Note that the smallest installer iso to use for offline installation is called "server" iso.

The "netinstall" iso is purely intended for an installation that downloads packages from the net. Its pool (on beta2) is only that of "debootstrap minbase".

@Marjorie, no critcism intended.

Though, I'd like to point out that the forum was not down at any time during this. It really was your browser having some kind of built-in blockage prohibiting you against your will to access the site. The site was up and provided perfectly functional HTTPS access as well as plain HTTP access throughout.

You might also consider that there is no additional security for this site in having an SSL certificate that is less than 3 months old. Still, there's also no particular reason in having one that is older (especially with some 30000 or more python code lines there to help us automating its update)

That's right.

Use deb.devuan.org in your sources list. That name will resolve in DNS for each request to go to the one or the other of the repository mirrors. That domain name is associated with the whole range of mirror IP addresses in "random" order, and the DNS resolution system will pick the one looking "best" at the time (aka "first one").

The name auto.mirror.devuan.org resolves in DNS to the previous main repository, which nowadays may and might not be maintained.

Though you might, on occasion, temporarily use pkgmaster.devuan.org which resolves in DNS to the current main repository. The repository mirrors "rsyncs" their content from this. However, it has quite limited network bandwidh so having a lot of people going there will be detrimental for all. It's thus better community-wise to use the mirror domain deb.devuan.org even though this slightly increases the risk of random network failure.

can't say I know anything about this... maybe I sould?

Beowulf beta "netinstall"  without network gives you nothing. Try using "server" or "desktop" rather.

More importantly you'll need to spell the argument the way it was given,
i.e. --print-architecture rather than --print-architexture

Are you saying that iptables decrements the given option code by 1?

Or is it that you find it confusing that the --tcp-option parameter rejects code 0?

Rejecting option code 0 is of course consistent with the code table, since code 0 is an "end of options list" marker, and not an option code in itself.

When written to a flash, I assume you'd written it to /dev/sdf and not /dev/sdf1 (which is the first partition) and maybe the mdfsum from there matches the iso file?

head -c 4675600384 /dev/sdf | md5sum