Oh, I didn't realize you have an ethernet port. You're all set. Plug in, then

apt-get update
apt-get upgrade
apt-get install broadcom-sta-dkms linux-headers-$(uname -r) build-essential

You might need to reboot to get it to work.

Maybe the local coffee shop will let you plug in with a wire. Then you don't have to wait for the next visit to a hotel.

While you're there, you can install whatever php packages you need. You should already have ncurses. I don't understand the part about matching versions - I didn't think they were related in any way. ncurses-base in ascii is 6.0+20161126-1+deb9u2 and php7.0 is 7.0.30-0+deb9u1.

A search for 'php-ncurses debian' brings up a a few hits. This one from 2015 looks promising, but my browser is timing out trying to get there. http://grosan.co.uk/how-to-install-php- … on-debian/

1, ctrl-alt-backspace hasn't worked in a long time. (maybe not since squeeze)
    Use alt-SysRq-k instead (SysRq is probably the same key as PrntScr.)

2. I don't know. I have been able to type those characters in a terminal when I was testing, but I can't tell you how I got there, and I don't remember the key combinations I used. Try the xfce4 keyboard plugin to switch layouts. (xfce4-xkb-plugin)

Un-set wlan0 as the default wireless device, either in wicd preferences or in manager-settings.conf, and wlan0 will not be configured. When you want to connect to wireless (or if you get a sudden urge to see what wireless signals you can get) you'll need to set the default wireless device to wlan0 again.

Another option might be rfkill to turn it off.

I think you have to go back to squeeze to find --root-directory in the grub-install man page. Pretty sure it still works, though. These days, I tend to chroot into the system to install grub, so I don't use that option.

off-topic message for mchasard:

dpkg-reconfigure locales

Hint for more effective use of irc - stay logged in, and the answer may come minutes or hours later.

I can imagine a future google service that warns you if someone is standing behind you when you're about to enter a password.

What you tried looks right to me, but the man page for mke2fs doesn't actually say what units to use for offset. Further down the page where it talks about specifying the location of the journal, the wording suggests that you might need to use 'offset=1M'.

One thing you did looks odd - why partition with cfdisk if you want gpt? gdisk is the right tool for that.

Yeah, I get the "unknown option" message in jessie, but not in ascii. The option is not mentioned in the jessie man page but is in the ascii man page.

These two do the same thing. With the first one, it assumes you mean to use the file with the same name minus the .asc.

gpg --verify SHA256SUMS.asc
gpg --verify SHA256SUMS.asc SHA256SUMS 

This didn't work:

$ sha256sum --ignore-missing -c SHA256SUMS
sha256sum: unrecognized option '--ignore-missing'
Try 'sha256sum --help' for more information.

To check a signed iso, I'd do this.

gpg --verify isofile.iso.asc

You could also use a different keyserver. I use MIT because it's just up the road from here, and I can remember pgp.mit.edu.

'Cause it's too much to type, and I got lucky and saw my own name when I used just eight characters. If someone else's name showed up, I'd use 16. I'm not sure if using the whole fingerprint number works with --recv-keys. Did you try that?

I'll tell you what I know. The digits before the key ID in the fingerprint are, well... the fingerprint. Since it's possible for two keys to have the same ID, the fingerprint gives you a more reliable indicator of whether it's the right key or not. I don't know how that gets calculated.

This will get my public key from a public keyserver.

gpg --keyserver=pgp.mit.edu --recv-keys 094c5620

Here's what I do to verify. I can't guarantee that it's right, but the output looks good.

$ gpg --verify SHA256SUMS.asc 
gpg: assuming signed data in `SHA256SUMS'
gpg: Signature made Wed 06 Jun 2018 05:49:36 PM EDT using RSA key ID 094C5620
gpg: Good signature from "fsmithred (aka fsr) <fsmithred@gmail.com>"

We don't sign the isos. We sign the SHA256SUMS file. If the checksum on the iso matched what's in the file we signed, it's good.

If I try to verify KatolaZ's signature on a computer that doesn't already have his public key, I get this (using the SHASUMS from the installer isos):

$ gpg --verify SHA256SUMS.asc 
gpg: assuming signed data in 'SHA256SUMS'
gpg: Signature made Wed 06 Jun 2018 06:55:55 PM UTC
gpg:                using DSA key 8E59D6AA445EFDB4A1533D5A5F20B3AE0B5F062F
gpg: Can't check signature: No public key

I know the 2017-12-15 amd64 exegnu iso is jessie. I assume the i386 is the same.

Dual-boot first. If you want TDE on ascii, you could upgrade the exegnu or you could add TDE to a fresh ascii install. There are instructions for devuan at the TDE site. Mixing TDE with Mate in the same installation might cause some conflicts with session managers. Doing this on a test install would be the less stressful way to go.