"recovery options for devices already impacted remain limited."
Really? You'd think they could come up with a rescue image you could boot from USB. Fixes the permissions; exits. (Caveat: I haven't used Windows in 20 years.)
765 publicly visible posts • joined 21 May 2007
The standard Ubuntu setup, inherited or copied by other distributions, is that logging in as root is disabled, but sudo grants the logged-in user root access to all commands (on submission of their own password). This is why many tutorials on system administration put "sudo" at the front of all commands.
It seems wrong, but I can't put my finger on exactly why.
On Wednesday afternoons, I play an acoustic gig in a local coffee shop. It's called "The Bank House", because, unsurprisingly, it used to be a bank. There's still an ATM in the wall outside, and I guess that the back of the machine was accessible from within the bank. But when the bank was decommissioned, they built a concrete block wall around that corner of the room, and cut a hole for an armoured door in the outside wall. That's security!
Can someone give an example of a use case for rebooting to use systemd occasionally, and sysv usually? Or vice-versa? I've been using Linux for over 20 years and have never needed systemd. (I've disliked sysv's init method of file symlinks ever since first encountering it {in Solaris?} but it's lightweight and it works.)
GRUB tries to cope with many, many scenarios, which makes it quite large and complex, whereas extlinux can only boot a Linux kernel running with an unencrypted ext4 root partition*. Since that is exactly what I need, I opt for that simplicity. It has meant that I needed to write a custom script to replace the usual one started by "make install" in a kernel build, but, excellently, the kernel developers have put in the hooks to enable you to do just that.
*(Actually, I think it might work with more partition formats, but I've never used anything else. Oh, it supports an initrd too, but I've eliminated that.)
Ah, I created the EFI boot partition at what seemed to me to be a "tiny" 2Gb on a 2Tb drive. That's why I didn't come up against the shortcomings of gparted. I then installed extlinux as the boot manager, with the (custom) kernel in the EFI partition, which df shows as 10% full. Since I've not used anything other than Linux on the metal for 20 years now I've never had much to do with dual-booting, although I'm sure it would be straightforward. Obviously, I'm not the typical computer user. Not even the typical Linux user. Installers? Who needs 'em?!
I tried Alpine a short time ago, first on an old 32-bit netbook, and then on a Pi Zero 2. It worked perfectly well -- no hiccups -- but on the netbook, I found that after 20 years of apt-get and dpkg, I'm too set in my ways to get used to apk. On the Pi, I installed the camera, which required the rpi-cam apps and libraries, and I was too lazy to compile from scratch with musl. Currently, I have that as a Devuan install with the Raspian repositories added. I thought that might cause dependency problems, but it hasn't.
Oh, the old netbook now has Peppermint, the Devuan flavour. They haven't updated that in a while, but have continued to keep up with their Debian-based one.
Giving the default user full root access to everything is a Ubuntu thing. (Inherited in derived distros.) Many other Linux distros stick to the traditional Unix-y permissions regime. So, if I need to do system admin, I log in as root. That's the way I've always done it, and that's the way I like it.
It's Devuan 7 now.
The help for the package kde-full says:
"This metapackage includes all the official modules released with KDE Sotware
Compilation that are not specific to development and as well other KDE
applications that are useful for a desktop user. This includes multimedia,
networking, graphics, education, games, system administration tools, and other
artwork and utilities."
Great. A VPN in the browser. And a mail client. And a Bitcoin wallet. And a Calendar. And an e-book reader. And a pop-up toaster. And a rechargeable vacuum cleaner. We won't rest until we've ticked off the entire list of things that users haven't asked for.
I don't have a "desktop environment". Just openbox and a pick'n'mix array of applications. Up until I read this article, I had Evince as the default application for PDF files. I thought its text rendering looked better than other ones I tried originally. But if it's being retired I'll use something else. I've just installed Atril from the Mate desktop. Looks fine.
I'm a human (honest) and I find captchas really difficult. I think it's partly because some of them, Google in particular, are American-centric, but also because I'm on the autistic spectrum, and my logic doesn't match that of the captchas creators.
If I had a desktop or online agent that would do them for me, that would be great.
I think that although we may be in a period when AI results are useful sometimes, this is because they have been trained on human-generated content. As a larger proportion of the internet becomes filled with AI slop, the bots will ingest more of it and the "answers" will become progressively worse. At some point, the bubble will burst.
I've been trying to use DDG as my preferred search engine for a few years, but the absolute worst thing it does is to return "hits" which don't include all my search terms. I wasted time reading irrelevant web pages until I was sure it was happening. Now I can recognize unlikely hits and try Google instead.
The core function of systemd is to act as a service manager... which is why it is factually inaccurate to describe it as an "init system".
I've been using Linux exclusively on my own machines, and then exclusively-exclusively when I retired, for almost 25 years. And I have never had an essential system process that crashed and needed to be restarted. OK, I'm just a home user, but none of my machines need a "service manager".
Although a long-time Debian and eventually Devuan user, I've started trying out Alpine on low-spec machines. From doing "ps -ax" I see that it seems to have a "service manager". I'll bet that its codebase is a tiny fraction of systemd's.
My sister's elderly laptop stopped working the other day, and she emailed me to ask what replacement she should buy. I pointed out that Windows 10 was on its way out, and Windows 11 laptops would likely be more expensive htan she was expecting. "Would a Chromebook suit your purposes?" I asked.
A hour later, she had gone to Currys, bought a Lenovo Chromebook, and was on line. She is completely clueless about technology, and has only ever used Windows.
I, on the other hand, have been using Linux almost exclusively for 25 years, and I bought a Raspberry Pi Zero 2 and camera module to use as a security camera. Apalled at the amount of bloat in Raspberry Pi OS when I did a test install, I decided to use Alpine instead. It took me 4 goes to get it right.
That's the difference between ChromeOS and Linux.
I use a Pixel 5a with LineageOs/microG. Installing Play Store apps was clunky, until a fellow Reg reader pointed me to the Aurora store. After that, the phone does everything I require and has an excellent battery life. I haven't come across any app that failed from lack of Google services (microG provides an emulation).
I don't know when it happened, but ALSA support is back. I previously used Chromium for streaming radio on my "music server" (a Pi 4) but after an update, sound was dropping out regularly. I installed Firefox ESR and it works perfectly.
(I use Vivaldi on the desktop PC for everyday browsing, Librewolf in a virtual machine for banking, and Chromium with previous data wiped when a site won't work with ads and scripts blocked.)
I have a Pixel 5a running LineageOS/microG. Monthly updates download and install painlessly. When the Android main version changes, you have to install the update manually, but I've done that five times now (currently on 13) and nothing has broken.
LineageOS is available for the Pixel 7 Pro, so you could easily get your previous phone working again.
Your problem isn't that Linux doesn't work. Your problem is that you don't know enough to get it to work. But as a Reg reader you must be far better informed than the average Windows punter. That's why I don't see a mass movement to any form of Linux after Windows 10 becomes unsupported.