gerdesj

If I recall correctly Arch has ... ssh into wifey's laptop ... python installed out of the box.

Run up a console and type python, and hit enter. Type in print ("Hello World") and hit enter. There you go!

If you lack a python: $ yay -S python.

"Anyways, point is that I associate Windows with bad memories. While I associate Linux with good ones."

Me too. I use Arch/Kubuntu ... actually!

Do you have any idea how hard it is to go from Linux to Windows?

Nightmare. The bloody thing keeps on wanting to peek up your skirt (even if you don't wear one)

I usually do Arch myself these days and spent many years with Gentoo. So I'm not too terrified of breakage!

I am putting together a Linux distro strategy for my company. I am the MD of a very small IT company in the SW of England. I already have my office manager asking me to liberate her from Windows! I recently had a techie asking me to help his transition! This is organic stuff and not pushed down by me. The techie is a dyed in the wool Azure lover.

I am used to being patient. It took me roughly five years to get a helicopter company that I worked for back in the day (late 1990s) to use DHCP properly - ie let them "roam free" and let DDNS pin them down. Sounds a bit ridiculous until you encounter "enterprise" grade nonsense.

I have set up laptops with most of the usual suspects and tried them out. However, I have to comply with Cyber Essentials Plus which is a UK standard. It is fine but rather Windows n that 'centric. That means I need full disc encryption and anti virus (AV) and Secure Boot. I got away with ClamAV in the past but ideally I get cross platform and that means ESET for AV/web etc. I use the usual Linux FDE.

I also need to join an Active Directory until I have got rid of AD! Oh and there is Exchange.

https://cid-doc.github.io/ - AD and Evolution with the EWS addon for Exchange.

So I dive in with Kubuntu after trying Rawhide and all sorts. Ubuntu is flexible enough whilst being stable enough for me. For example, Kerberos is screwed for the Firefox snap. I need Kerb for auth to my corp websites such as our wiki. Mozilla does a PPA - I dump the built in FF snap and use the Mozilla blessed PPA. All documented and all controllable in an enterprise sense.

Closed In Directory (CID) is a configuration for Linux boxes joining into the MS world. Its a super piece of work, getting Samba, krb etc all working together well, and with a GUI. You can run scripts from your DC for that GPO feel with it.

My needs are a bit more corp than your gaming shenanigans but my notes might help you decide what you want, what you really (really) want (zigazig ... ahhhh!)

Ubuntu PPAs are a bit like the AUR for Arch ... well you have to decide what you really want. You could start from scratch: https://www.linuxfromscratch.org/

Bizarre article: "Recently, Linux-based firmware has emerged as a powerful alternative"

I have a stack of Dell OS9 switches in my computer room - they boot BSD. I have sold and set up Dell OS10 switches - they boot Debian ... on the control plane. To be fair they can run quite a few OS's on the control plane. On both, you can switch to a shell (BASH) and fiddle with Ansible and the like or you stick with the usual interface.

They are not glorified PCs! Frames and packets pass through some very fancy electronics and some very specialized memory (CAM - Content Addressable Memory) is employed for certain tasks. The manuals for these beasts run to 1500 pages.

I also have a large fleet of pfSense and VyOS routers and a Mikrotik or two and a slack handful of Fortiwotsits, oh and a Cisco thing or two and some others. pfSense is BSD and the rest are Linux. The Fortis are a bit more like modern switches with their own rather odd and twitchy way of doing things, backed up with some fancy and not so fancy hardware.

I have also played with all of the distros mentioned: Tomatoe/DD-WRT/OpenWRT and they are great for cheekying up a rather rubbish ISP provided router. They are also great for running on budget gear. They are basically superb for budget conscious consumers that are capable of reading some very decent docs. Prosumer is the term, I think.

Anyway, this article is rather odd and is basically filler. The section titled: "Case Studies and Real-World Examples" is a contender for fluff of the month.

Rustdesk is pretty decent and being developed quite fast. Why not look at MeshCentral too. Choice is good and MC has been around for a fair old while.

My company replaced Teamviewer with MC and we have thousands of client machines across the UK.

Files are files and filesystems are filesystems. You keep your files on filesystems.

NTFS and ext4 are non convertible - you cannot turn one into the other directly, in place. However you can take files from one and put them on another.

Yes, moving TBs does take time, sorry it is unbearable.

My wife's laptop absolutely has to work. For some mad reason I decided on Arch for it. Actually a rolling distro is not so mad. You get the latest stuff and in general issues are fixed as quickly as a LTS jobbie or you get a work around in the forums or you dig out the source and a compiler. It's no accident that the Arch wiki is an oft cited resource. Its not for everyone!

I've been looking at a similar thing for my company and Kubuntu so far is my choice and I've already ditched the LTS bit. I need to run AV and the usual corporate bollocks to pass silly tick box exercises, so my options are rather limited.

There is no perfect one size fits all distro, that's what we have rather a lot of them to choose from - they rise and fall according to natural selection and not artifice. Imagine if all computers were sold with a free/libre OS or none at all and Windows or Apples were a paid for add on. Monolithic OSs are completely deluded about being able to cater for all, without some dreadful contortions.

Anyway, back to the job in hand! If you want a LTS then you must accept older software or you use an LTS as a base and add newer stuff yourself. Most Linux distros allow you to run your own add-ons formally or informally. Gentoo has a rather nifty user patching mechanism for distro ebuilds and you can have your own ebuilds take over entirely. RPM and pkg distros can handle user packages and Ubuntu has PPAs too. I could go on. Also you can go off piste and put stuff into /opt and/or /usr/local!

Please reconsider your use of the term "unstable". I suggest you write down a list of your requirements and score them according to importance. Then grab a list of OSs and distros - all of them, don't preclude Windows and Apples: they have their uses. Then score the OSs/distros against your requirements. The scoring might be in the form of a matrix (table). I suggest keeping it simple with a score of -1 to 1 for each item (-1=dislike, 0=neutral/whatevs, +1=like)

Do a pilot project and see how that goes. Take your time. If it is for personal use then run your tests in a VM. Most modern hardware can easily run a VM or two. Virtualbox or VMware Worskstation or KVM (libvirt is a good effort)

The choice is yours. Note that word "choice" - its very important.

"I understand that Canonical has every right to make the decision about their product."

That seems fair. There are loads of distros available so why not try something else if you don't like Ubuntu?

Linux and other mainstream Unices such as FreeBSD or OpenBSD int al (that's not something I ever thought I'd be able to say a few decades back) are not Windows or Apples or whatevs. You do you and not them!

If Ubuntu fails to scratch your itch then move on. Debian is the upstream for Ubuntu so you'll probably be fine with that instead. There is loads of documentation for Debian via the wiki etc and of course most Ubuntu docs will apply as well.

They don't need a new distro, unless they hire a lot of highly skilled packagers. I'd take say Ubuntu or OpenSuSE ... but it would be RedHat with Oracle for the NHS - they just can't help losing money.

For my tiny company, I'm going Kubuntu ... bear with ... Ubuntu means:

• Multiple "enterprise AV" are available (ESET and others)
• Secure Boot
• Full disc encryption is available

Those boxes ticked gets you on the way in the rather naff enterprise security word of tick boxes. Without those - give up now.

The K(DE) bit gets you a lot of configurability and its reasonably easy to get an environment out of the box that Windows users can get to grips with. Besides, I like KDE/Plasma.

I then tack on this rather fine project: https://cid-doc.github.io/ for AD, SYSVOL, "Drive letter" etc integration. Evolution with EWS does email.

My test machine is my desktop (it used to run Arch (actually), my laptop still does) - I started off with Kubuntu 22.04 and wired up all the above and then whilst in a Teams meeting kicked off the upgrade to 23.04 for a laugh. Sound stopped after a while because the kernel modules switched out. Anyway, all good after a reboot.

Seeing as I am competing with something that has GPO, I'll allow myself to use Ansible.

PS - I should point out that an Arch box can run one of the ESET for Linux products OK (I have). You can get it to do secure boot and it can do FDE. So can Gentoo but I spent 15 years constantly fixing my Gentoo pets too.

I do use it quite a lot. The pfSense package for ACME can run scripts, which might use scp. Modern Windows boxes can run OpenSSH daemons and obviously, all Unix boxes can too. They all have systems like Task Scheduler or cron to pick up the certs and deploy them.

I do IT security for a living. It is quite complicated but not unrealistic for you to DIY.

Do a risk assessment first off - how important is your data to you and a hostile someone else? Outputs from the risk assessment might be fixing up backups first. Think about which data might be attractive to someone else and what you do not want to lose. Your photos are probably irreplaceable and your password spreadsheet should probably be a Keepass database. This is personal stuff, work out what is important.

After you've thought about what is important, then you start to look at technologies.

Decide how you need to access your data, when off site. I'll give you a clue: VPN always until you feel proficient to expose your services directly on the internet. IPSEC or OpenVPN or whatevs.

After sorting all that out, why not look into monitoring?