Me. I am typing this without looking at the keyboard. Learnt at college on an old school electric typewriter as part of my computer science course in the mid 1980s.

Not going to happen. :-D

Yes as far as I’ve found so far, the features track quite well, and I’m really aiming to get proficient with the standard interface. I’ve found a few minor differences, but I tried stock Mint (which is Ubuntu 20.04 based) for a while, and I didn’t want to go backwards from Trixie (the current Stable Debian version) so I opted for LMDE which is based on Trixie. I use Debian Stable because of the “2-year cycle” (that’s why it’s called stable); Because stock Mint tracks the latest LTS release of Ubuntu, it’s actually a fair bit more out of date than Debian at this stage, and the next Mint version, based on the new LTE Ubuntu, isn’t slated to come out until December.

So far it’s not been too bad for a hybrid system - I have had a couple of issues, but this is most likely attributable to being a hybrid. I’ve found that I like Cinnamon, which stock Debian does not (as far as I know) support yet - I have used MATE for about 15 years because I don’t get on with Gnome 3 or KDE. You get all the nice things about Mint that I found impressive when I tested it - the printer and scanner support is very good, and the configuration utilities are quite reminiscent of Windows ones (good for new users, but I personally don’t care). Still not sure if I’m going to stick with it long-term, but happy with it for now - I largely stopped distro-hopping when I switched to MATE.

I know right. I had a right game reinstalling Win 10 on a lenovo netbook - I had to put a supported, unmanaged version on it for installing lenovo dock firmware updates. For some reason, the default graphics mode was totally corrupted - almost unreadable, and rotated 90 degrees. Once the installer had finished, I had to manually install the right driver for the graphics hardware, and that fixed it. Took hours - total amateurs. For shits and giggles, after I’d finished with with the firmware updates, I installed Mint on it - and it was flawless, and done in half an hour. This is the way to do it!

No we can’t. I hate football (soccer for you USians) with a passion greater than those that love it, and I can’t avoid it, even though I desperately try.

Favorite: Debian Stable (For my uses, it was the least trouble)

First: Slackware (1995, installed from floppy disks, also a short stretch in 2009)

Current: Linux Mint Debian Edition (LMDE) (Using because I need to support users on stock Mint)

Distro you liked the least: Novell SuSE (Used in a corporate setting)

Distro you want to use in the future: Unknown

Distro you used for the longest time: Debian Stable (15 years)

Distro everyone likes but I don’t: Ubuntu

Honorable mention: DietPi (RaspberryPi and SBC focused OS)

Over time, I’ve used quite a lot of different distros: Red Hat, Red Hat Enterprise, Scientific, CENTOS, Fedora, Mandrake, Damn Small, Puppy, CrashBang, Raspbian, Bazzite, to name just the ones I can remember off the top of my head now.

Everyone who uses O365 is pushed to use the web versions by the O365 ecosystem. When you click on Word/Excel/Outlook/whatever from your menu, it opens the web version; to use the locally installed app, you have to go to File/Open in Desktop or similar. The Open and Save dialogs default to using OneDrive - saving to local filesystem requires extra steps. The locally installed ones are becoming increasingly hard to use, by design, and the new features seem to be going into the web versions first and the local versions “eventually”. For example, the new excel “matrix” functions did not work in local excel the last time I tried to use them, though they might now, but there were a few features (special formatting I think) that only worked on the local version. Templates for word do not work on the web version.

Interestingly, the web 365 apps seem to work on Linux Mint, but I’ve not used them extensively, or on another distro. I did a migration from Win10 to LM last autumn, and I was genuinely shocked to find that web Outlook and OneDrive work on Firefox on LM. Confirmed that web Excel and Word worked enough to allow display and editing of documents - not an extensive test, but definitely worth a look. Obviously, there are still differences between the web and desktop versions, but it might even be possible to run them under Wine, but I have not tried that, and woudn’t expect it to go too well tbh.

Can confirm. I used Linux and Unix almost exclusively for about 20 years, and when I more recently had to use Windoze again for work, this is pretty much what happened.

Digital ads do not promote things I’m interested in buying. I do not see ads very often at all - I haven’t had a TV for 20+ years, I don’t go to cinemas, so I don’t even see those kinds of ads. Occasional ads on YT pop up, and I’ll skip them; if they are unskippable or too frequent, I’ll abandon the vid. I’m not on any commercial “social media”, so I don’t see ads on them either. I’ve just never liked social media - Lemmy and Mastodon are all I use these days.

Occasionally, very, very occasionally, I’ll see a meatspace ad that I pay attention to: there’s a local alternative music collective that wheatpaste ads around in a nearby town. I actually WANT to know about these events, and I will actually go to them, and I actually sought them out in the first place. I also see ads at my local community centre, for local events. Same kind of thing.

So how is this resistance futile?

Yeah it was wild, but I suspect few orgs do things that way any more.

You mean in the context of high availability?

tl;dr: It’s to test if the cluster fail-over configuration is working properly.

So this was before things like Kubernetes or Terraform were a thing, so had to be done by the operating system itself. The simplest HA cluster is made of two nodes, one in “active node”, the other “passive”. The active node does all the work, and the passive node just keeps its data synchronised with the active node. I used to use DRBD for this, which is a system for copying writes to the active node over a network link to the passive node. That only gives you a “second, up-to-date copy” which is not that useful on its own - you also need a way to automatically switch over to using the passive node if the active one “dies”, and for that I used to use “heartbeat”, which simply passes packets back and forth between the two cluster members - ping-pong style - and if the passive node notices that the active node hasn’t sent its scheduled packet for, say, 10 seconds, it cuts it off the current active node (kills it), and promotes itself to the active role, thus preserving the service. Killing the “other node” is necessary to stop data corruption or user requests going to a node that can’t actually service them, and is called STONITH - Shoot The Other Node In The Head. STONITH can involve an electronically controlled switch, which literally cuts off power to the “other” node, or can isolate it on the network, by shutting down its network ports on the switch, or in a VM setup, sending a notification to the hypervisor to kill the VM.

The reason you need to be able to kill the kernel on the active node, is that when you manually shut down the active node, it automatically informs the passive node that it’s going down, known as an “orderly fail-over”, and you’re not actually testing if the heartbeat fail-over works, you’re just testing an orderly fail-over. Killing the active node’s kernel tests that the passive node is properly configured to take over during a catastrophic failure of the active node. You can watch the heartbeat status go from “up” to “down”, and then see the passive node decide to take over, promote itself and bring up its services, and begin processing requests.

To make sure it’s all working, you need to test orderly fail-overs first, from both nodes, then test disorderly fail-overs both ways, by using the kernel gun on the active node.

Things moved on from Heartbeat-based HA clusters to multimode clusters managed by Corosync and other software, enabling other strategies to be employed. This was eventually supplanted by “orchestration” systems like Kubernetes, and proprietary Virtual Cloud systems that move this functionality to the platform rather than the operating system.

Nah man. “kill” doesn’t shut the system down quickly. This is the “instant death” way - the kernel reset gun - no shutdown scripts, no disk sync, just reset to BIOS boot sequence, instantly:

As root:

echo 1 > /proc/sys/kernel/sysrq

echo b > /proc/sysrq-trigger

If you change out the “b” in the second command for “o” it will just halt the kernel instead of rebooting. Still switched on, but the system is doing absolutely nothing.

I used to use this trick all the time to test high availability server clusters.

I learnt to “type” when I was at school, programming a Commodore Vic-20. I thought I was quite fast, but what I had really learnt was just the key combos for common words. It’s what most people who have never learnt properly before do, and it’s called “point and poke”. You don’t realise the extra effort you’re putting in, and the mistakes you’re making (overuse of the backspace key) and so on.

When I went to college at 16 (UK) to study computer science, we had the option of learning touch typing. We all thought we were pretty good at typing, but afterwards, we’d all doubled our typing speed (or more) and increased our accuracy by 10x. We learnt on proper electric golfball typewriters, and as we got better, we all noticed that code entry got a lot faster. The thing that is affected most, though, is typing up from notes or printed copy - because you don’t have to keep looking away from the source, back to the keyboard and screen, you can be much quicker. Also, typing your thoughts is much faster as you are not having to split your attention between the thoughts and the keyboard - what you think just appears on the screen without having to spend mental effort on typing.

It didn’t quite work like that. They used to arrive boxed in batches. The keyboards were worth about £100 back then - so would be worth a lot more in today’s money - and they were looked after with care whilst in transit. It was the end users (in offices) that put the gunk there.

Can confirm. Back at the beginning of my IT career (mid 1980’s), I worked as a temp for a computer manufacturer in their refurb repairs department. In those days, kit was so expensive that everything got repaired if it went wrong, and one of my jobs was repairing keyboards - PC keyboards, and dumb terminal ones - and the first part of the process was stripping and cleaning them. There was a lot more room for crumbs and dust back then, too, and man did they get full. Crumbs, staples, paper clips, hair grips, all sorts. I had literal mould growing in some of them. I remember the ones coming in from Italy were the worst for that for some reason.

Well, it depends what you call spam, how well known your server is (are your email addresses spread far and wide on the web or only known to a couple of people) but a lot of spam is automated and algorithmic, so most servers will be showered with speculative mail addressed to likely mailboxes - which your server still has to process, if only to bounce the message; if you have antispam measures, your server can just drop the connection when it detects a spammy sender (e.g. from an address on a black or greylist). I’m not currently running any mail servers, but a few years back when I did, I used to get about 80% spam incoming.

The list is immense, and I didn’t want to clutter my post with all the details. So just listing off things that spring to mind (because I don’t know what OP doesn’t know):

• Choosing an MTA - sendmail, postfix, exim, etc. and why you might choose one over the others
• Firewall settings
• Software/package management on your chosen distro
• Learning about DNS:
  • Host it - yourself via BIND
  • Or via a DNS service provider
  • DNS record types
    • Domains
    • Subdomains
    • A records/CNAMEs
    • MX records
    • Mail authority records - SPF’s
    • Mail encryption records - DKIM
• Spam filtering, anti-virus
• Learning how to configure your MTA, which requires learning:
  • the configuration file language your MTA uses
  • what all the options mean and what they do
  • what the bare minimum options are to get up and running
  • how to make sure your configuration is secure and won’t be exploitable by bad actors
  • how mail really gets delivered
  • how to setup secure smtp
  • how to set up SPFs
  • troubleshooting why GMAIL or Microsoft won’t accept your mail
  • troubleshooting why GMAIL or Microsoft have stopped accepting your mail
  • dealing with blacklists/greylists when someone sends too many messages, or something that “looks too spammy”
• Mail hosting pitfalls
  • Being an open relay
  • Rate limiting
  • Reputation management
  • Vulnerabilities that let a hacker take over your server
  • Resource management - disk, memory, processes, queues, etc.
  • Downtime when you need to do updates
  • Downtime if you change your DNS configuration

I’ve definitely missed some stuff, and each of those things requires knowing other stuff too, so you can see that it’s really a pretty deep subject. This is precisely why not many people self-host email themselves these days - the big guys have made it harder and harder to do so, in the name of eradicating spam, which they themselves are the biggest vectors for.

I’d suggest you start with a simple static web server if you’re looking for a good beginner project. Use something like Nginx, and just set it up on your local network at first, then work out how to harden it, and open it up to the real internet. There’s a lot less to learn for this usage case, and it’s less likely to get you into trouble.

I say that, because, after reading through the thread, it seems you are hoping to find an (educational) use for an old computer. I did Linux and Unix admin professionally for 15 years, for some famous brands. I would NOT recommend setting up a mail server as a first project - it’s complex in ways you will never expect, and will require learning skills and knowledge that are very specific and you literally can’t “start small and build up” because a lot of the things you don’t know yet will get you into big trouble. Essentially, it’s not too hard to set up the server software, and your hardware is certainly capable of running this task, but making it safe and secure IS hard these days - especially with all the encryption and anti-spam setups you have to learn how to do.

Depends on accent:

South West: jrink me loike a bo’oh wa’er ('=glottal stop like in “ugh”)

London: drink me lyke a botto a wawtah

Merseyside: dlrinch me liche a bottull a wahtah (ch=choking sound)