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.
Website: https://roffey.au
- 1 Post
- 23 Comments
Joined 9 months ago
Cake day: March 6th, 2024
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
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?
18·3 months agoSecuring 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.
It is fast. It’s the recommended filesystem for MinIO and default for RHEL 7 and above. XFS and ext4 are often recommended for databases if no other filesystem-level features (like snapshots) are needed. XFS has slightly more features than ext4 like CoW and reflink support.
It’s not stupid. They don’t show unverified .deb packages in software centre either.
The main reason I’ve steered clear of OpenSUSE is its commercial backing as opposed to being a true non-profit community distro like Debian or Arch.
Red Hat have influenced Fedora decisions before and obviously blew up CentOS as a RHEL clone when they had the chance. Canonical constantly make bad decisions with Ubuntu.
I will add that I’ve heard nothing but good things about SUSE and OpenSUSE. SLES sounds like a decent alternative to RHEL and the OpenSUSE community distros sound pretty solid.
Windows Vista. I absolutely decked it out with free/open source software (LibreOffice, Firefox, Thunderbird, KDE for Windows) before I dual booted Windows and eventually made a more permanent switch. Never looked back.
I did have to use Windows for my old job (Win10 from memory?) but now I have a job where I can use Linux.
Next step is to switch my partner over from Windows 11 (she’s already on board with the idea).
Windows Vista. I absolutely decked it out with free/open source software (LibreOffice, Firefox, Thunderbird, KDE for Windows) before I dual booted Windows and eventually made a more permanent switch. Never looked back.
I did have to use Windows for my old job (Win10 from memory?) but now I have a job where I can use Linux.
Next step is to switch my partner over from Windows 11 (she’s already on board with the idea).
Yeah me too, safety in numbers. Maybe if Linux desktop gets bigger than Windows they’ll swap it around 👨💻
You can absolutely download apps from F-Droid on GrapheneOS, what makes you think you can’t, and how did you conclude that LineageOS is more private and secure?
I never said that GrapheneOS couldn’t download apps from F-Droid. I didn’t mention GrapheneOS being able to use F-Droid in my dot points but that was just an oversight, not intenttional.
GrapheneOS doesn’t ship with any Google services by default. We do provide an easy and safe way to install the Google Play components if desired, they are run under the same sandbox and constraints as any other ordinary app you install.
The problem with this is that so many apps use Google Play Services. If I didn’t want a phone that used Google, I wouldn’t use an OS that bent backwards to make it work.
The sandbox model is OK in theory, except when your bank app asks for permissions for microphone, camera, contacts and files, and refuses to start without them.
The app model is a bit broken IMO and GrapheneOS both enables and perpetuates it.
LineageOS is pretty commonly behind on updates. As an example, it seems that LineageOS 21 (based on Android 14 QPR1) came out in February of this year. You cannot ship the full security patches without being on the latest version of Android, which is Android 14 QPR3 now.
I might be being a bit naïve here, but Android 14 came out in October, 4 months prior to LOS 21, which is not particularly long. Android 13 is still supported by upstream. This sounds a bit like running RHEL or Debian vs bleeding edge Arch, no? It’s a common debate whether RHEL systems are constantly out of date, the counterargument being that vulnerabilities are often found in new software versions. Without real statistics about security vulnerabilities over time it’s difficult to make an informed decision about software version policies.
LineageOS does make connections to Google by default, as does AOSP. GrapheneOS changes those connections while LineageOS doesn’t.
That is excellent, I’m glad to hear GrapheneOS is changing some of the defaults to be a bit better.
Lineage is kinda bad privacy and security wise, from the little I know its not fully degoogled
My understanding is kinda the opposite:
- GrapheneOS ships with a sandboxed, FOSS Google Play Services which can optionally do a bunch of Google things (use their APIs, login to Google etc.) plus they have some hosted services that can substitute Google services (like geolocation).
- LineageOS basically doesn’t ship with any Google Play style API/frameworks at all. It’s a pure AOSP experience. Any apps on F-Droid work but third party apps (like ones found on Google Play) are hit and miss. If you can just use F-Droid for all of your apps then LineageOS is probably a much more private and secure offering.
- LineageOS for microG is an unofficial fork of LineageOS which includes a FOSS Google Play Services compatibility layer, a bit like GrapheneOS. As far as I know it doesn’t have the same level of sandboxing as Sandboxed Google Play on GrapheneOS.
Both GrapheneOS and LineageOS publish monthly updates with upstream security patches for all supported devices.
Both GrapheneOS use network-provided DNS by default.
Apparently both GrapheneOS and LineageOS connect to connectivitytest.gstatic.com via http as a Captive Portal test by default,althoughh this was as of 2019-2020 and both might have changed since then.
Something that often gets missed is the difference between packaging conventions between distros.
For example, Debian has Apache httpd packaged as “apache2” and has wrapper scripts for enabling sites. Fedora/RHEL has “httpd” and includes conf.d from the main conf. Arch also has “httpd” but doesn’t have a conf.d out of the box. Of course you can pretty much configue Apache to your heart’s content and have an identical setup between all three distros.
From what I’ve read, Debian tends to patch and change software to fit more into their overall system whereas Fedora and Arch tend to be more upstream.
RPM and Arch both have group packages and metapackages. Debian just has metapackages AFAIK. Debian also has “recommended” and “suggested” levels of soft dependencies, the former which is enabled by default. RPM has the capability for weak dependencies but AFAIK most RPM distros don’t use it. Arch doesn’t have soft/weak dependencies AFAIK.
When you install a new system daemon on Debian, it’s generally enabled and started by default, whereas RPM-based and Arch don’t do that.
When I think of the base of the system I tend to think of some of those more subtle idiosyncrasies that tend to spread around the ecosystems, like Ubuntu and Debian behave quite similarly for instance.
Yeah, sorry it was a long time ago (like 10+ years) but I checked and it would’ve been the --overwrite arg.
The manpage for the older ntfsclone command has it:
Clone NTFS on /dev/hda1 to /dev/hdc1: ntfsclone --overwrite /dev/hdc1 /dev/hda1
Moral of the story was to RTFM 😂
ntfsclone /dev/sdc /dev/sdb
/dev/sdb was a blank filesystem and /dev/sdc was my Windows filesystem.
It ran for less than a second and didn’t take me long to figure out what happened. That’s the story of how I stopped using Windows.
There’s also dotnet (.NET Core) available on most distros which is an open source subset of .NET by Microsoft
See https://fiodar.substack.com/p/differences-between-mono-and-net-core
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.