Yeah it is a bit of a pain. I currently only have a few users. Tooling-wise there are ways to tail the journals (if you're using journalctl) and collate them but I haven't gotten around to doing this myself yet.
theroff
That's probably a fair point. I can't say too much as I haven't touched Windows desktop or server too much.
Could be apples vs oranges here though as we're talking about getting started versus well established setup, but my current employer is looking at adopting Ansible + Packer for imaging and partially Ansible-managing Windows servers where it makes sense because of limitations in SCCM and GPO. As far as I can see across the divide Windows Server isn't all smooth sailing.
I can't say I've managed Linux desktops at scale (so technically I should leave it there) but I do manage several hundred Linux VMs with Ansible, and I manage all of my PCs with Ansible. Desktops are a different ballgame to servers, dealing with end users and all, but I still don't think it would be that hard once it's been set up.
That sucks :( I'm pretty much in the same boat. I get to use a Linux desktop at work on the proviso that I don't raise support requests. We use Microsoft for nearly everything so naturally it's an uphill battle. The web UI is quite buggy and "not recommended" by my org. Teams doesn't support Firefox so I have to run a separate browser especially for it.
But aside from interfacing with Microsoft everything just works, and really nicely.
That's awesome - great to hear about Linux desktops bring used by non-techies especially in a company.
How was it received out of interest?
At work we use separate clusters for various things. We built an Ansible collection to manage the lot so it's not too much overhead.
For home use I skipped K8s and went to rootless Quadlet manifests. Each quadlet is in a separate non-root user with lingering enabled to reduce exposure from a container breakout.
It's called Microsoft Clarity, and yes, Teams does it https://clarity.microsoft.com/ https://en.wikipedia.org/wiki/Session_replay
Securing proprietary hardware against peeps installing alt OSes
Technically XFS is also a CoW filesystem, but it doesn't have the vast array of features that ZFS does like volume management, snapshots, send/recv etc. It does have reflink support which I guess is a kind of snapshot for a file.
OpenZFS is under a completely FOSS license but it's incompatible with the GPL and can't really ever be merged into the Linux kernel. The workaroundids to provide it as source code which gets compiled as a module every time there's a new kernel via dkms.
More controversially, Canonical ship OpenZFS pre-compiled in Ubuntu which some lawyers believe to be infringing on ZFS' codebase.
Honestly the OpenZFS situation on Linux is probably the biggest single reason for the growing interest in btrfs and bcachefs, the former slowly becoming default on more Linux distros over time and lots of investment from SUSE and Facebook AFAIK.
ext3 had journaling, but not ext2. Also ext3 doesn't really exist anymore as it was merged into the ext4 driver which can read the old format.
On one hand, the hate that's being directed to the e-Safety commish is disgraceful.
On the other hand she is effectively proposing an internet licence for all Australians to be able to interact online via mandatory age verification. It applies to all social media sites but the definition of social media is so vague it basically just says a digital service which can be used to communicate with other people. She is deserving of our scrutiny.
https://www.aph.gov.au/Parliamentary_Business/Committees/Joint/Social_Media/SocialMedia/Terms_of_Reference