Even with a 10% pay cut the VC will be remunerated over $1,000,000 per year, even despite the university's poor financial performance.

Having worked at a university the waste is in plain sight. Vendor lock-in, consulting fees (especially with the Big 4), high executive pay, and compartmentalisation between professional and academic staff are high on the list.

In my area (different university) there was a constant stream of poor decision making. Moving to the cloud? Let's hire a consultant to tell us what to do, and then do it in the worst possible way, instead of using internal capabilities! I suggested that the contract include provisions for "best practice" as listed by the vendor (HashiCorp) but this was ignored. The consultant gave us spaghetti Terraform code and an inefficient, high cost subscription layout.

The professional and academic staff barely talk in my experience. Academics do their own thing as much as possible. Professional staff throw solutions over the wall, mostly because of the existence of the wall in the first place.

The university was looking at using "crotch sensors" (motion sensors under the desk) to measure desk utilisation, spending money on "smart" ambient sound solutions etc. in the executive building, and other high cost solutions looking for a problem, at the same time as freezing staff and threatening redundancies. I was denied training but offered access to an LLM subscription (GitHub CoPilot) along with other IT staff, because AI is the going buzzword being parroted by the executives.

The higher education sector seriously needs an external review... and a proverbial kick up the bum.

I sold my car last year and barely gave it a secomd thought (I still have access to a car on weekends). Money, environment and space-saving were all factors.

I don't think government should be in the business of subsidising driving (which is currently the case in multiple ways). Instead that money should be used to make public and active transport safe, convenient and reliable.

PSA: if your financial institution/government/ is using SMS codes (aka PSTN MFA) for multi-factor authentication they are practically worthless against a determined attacker who can use SIM swap or an SS7 attack to obtain the code. Basically you are secured by a single factor, your password. If your password is compromised it may be sold via black hat marketplaces and purchased by an attacker who would then likely attempt to break that second factor.

The best way to protect yourself is to use a unique password; a password manager especially helps with this. Sometimes institutions will offer "Authenticator" (TOTP) as a second factor, or PassKey authentication, both secure alternatives to SMS codes.

Here in Aus I'm working with Electronic Frontiers Australia to try and force some change within government and financial institutions (via the financial regulator). Most banks here use SMS codes and occasionally offer a proprietary app. One of the well-known international banks, ING Bank, even uses a 4 pin code to login to their online banking portal. 😖

Unfortunately SMS codes are a legacy left from old technology and a lack of understanding or resourcing by organisations that implement it. Authenticator/TOTP tokens have been around for 16 years (and standardised for 13 years), and PassKeys are relatively newer. There is a learning curve but at the very least every organisation should at least provide either TOTP or PassKeys as an option for security-minded users.

I have a bicycle crate in my rear rack (40L from memory). I can just throw my backpack and/or shopping in there and be on my way. No issues transporting when empty. I avoid riding in the rain but I guess a waterproof bag would help for that. It's durable, the main concern is the rear rack. I had to replace the cheaper rack that I bought last year after the welding snapped in a few places over time (I had it held together with duct tape for a while). My new rack should be much more sturdy this time around.

I have access to borrow a car which I do every few weeks so I don't need to over engineer my bike setup too much.

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?

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.