I have an HL-2270DW and the toner low light comes on well before prints start washing out. Fortunately the toner life is tracked by a plastic gear on the cartridge, and it takes just a minute to roll it back. When it does run out, good third party replacements are under $20.

$ :|wc -c 0 $ touch /tmp/f; :>>/tmp/f; wc -c /tmp/f 0 /tmp/f

Plasma 6 and Wayland are working great under Tumbleweed for me on my 2-in-1 laptop, but there’s still no usable virtual keyboard package like Maliit in Factory.

If you’re piping any of those commands to or from awk, you can also go.

That’s why many modern SoCs have a smaller core for realtime in addition to larger application processors. TI Sitara (Beaglebone) has 2 fast custom arch coprocessors for IO with access to most pins and the ability to DMA into the AP’s address space. All Raspberry Pis up through Pi4 run a proprietary ThreadX runtime on a graphics processor (VPU) to handle bootstrapping the ARM APs, housekeeping, and a large part of the IO.

Scratch machine to test Ansible playbooks for maintaining and restoring your other servers.

Real heads ctrl-[

That’s exactly what they are, but instead of connecting to a VAX at the other end of a modem they talk to a shell attached to a pseudo terminal device on the same machine.

25 years ago I worked at a university computer lab that was Windows-heavy because Dell wouldn’t stop donating PCs. However we didn’t have enough UNIX workstations as we had to pay for Sun / HP / IBM out of pocket. Converting them to Linux workstations would be nice because the Dells had more grunt than the aging RISC workstations.

I proposed to switch a few desks worth to Debian and was given the go-ahead. After a few days learning how to preseed an installation image and getting a PXE server going I had 8 machines running CDE just like the AIX and HP/UX boxes. Users that didn’t need one of the commercial engineering applications tied to one OS or another didn’t notice any difference between the free (now as in both speech and beer) Dells and the proprietary workstations.

A couple of months after we got the pilot rolling, the university’s IT director came to check it out and told me we’re on the “lunatic fringe” for deploying an OS developed by volunteers, but otherwise offered approval as long as we could maintain security and availability.

Now every student in our local school district gets issued a Chromebook running Linux under the hood. Who’s the lunatic now?

If I couldn’t wear fuzzy socks and sweaters at work I’d just quit.

There should be a setting in BIOS for sleep state that lets you choose between “Windows sleep” and “Linux sleep”. I know I have to set that to “Linux sleep” on my P14s gen 2 AMD or it wakes up immediately after going to sleep. Updating BIOS and the other firmwares might help too.

However I have a gen 7 from work running Windows that often fails to wake up from sleep or hibernation, and I have to resort to poking the reset button to get it to respond. Coworkers report similar troubles so I think it may be a cursed model.

That said, I’m running OpenSuSE Tumbleweed KDE on my P14s and an X1 gen 5. Everything works smooth out if the box on both machines except for the fingerprint sensor on the gen 5 which doesn’t have mainline fprintd support in any distro.

I never used Itanium, but I’m guessing that the Alpha workstations also ran x86 code faster than the Itaniums. fx!32 was one of DEC’s marvels that they completely forgot to market.

Similar, but not the same. The biggest difference of course is that the MIPS ISA is still commercially licensed while RISC-V’s ISA is open.

Tumbleweed is boring, and that’s why it’s wonderful.

Nah. The current license holder for MIPS announced its death a couple of years ago.

RISC-V is the new hotness.

Costco still runs stores on AS/400. Ever wonder what those all-text terminals are all over the store?

CC-NC prevents commercial use…

There is no standard for SoCs. If your board has an NXP i.MX6, you can’t just desolder it and drop in a TI Sitara or nVidia Jetson.

Designing a PCB for an SoC isn’t rocket science. There’s nothing magical about the schematic or the layout, and usually the vendor gives out full design files for their eval boards that you can use as a starting point for your product. The silicon is the hard part. You can make your own Beaglebone clone right now for a few hundred dollars including parts and the board, assuming you are comfortable soldering smt. Making a fully open equivalent to the Beaglebone SoC is a nine figure endeavor at a minimum.

The reason you don’t see hobbyist x86 SBCs is that Intel and AMD make customers sign a large pile of NDAs before sharing the documents you’d need to make your own. And in the case of Intel, you need to pay a 3rd party to provide you with a BIOS framework that obfuscates the ME firmware and other blobs (like memory training) so that even the board manufacturer doesn’t have any idea what’s going on in those hidden processors. (source: used to help develop x86 server hardware)

It’s dependent on the manufacturer to decide if they want a black box system management processor, what architecture to use, and what it will be responsible for.

The Raspberry Pi SoC uses the video accelerator processor (VPU) for bootstrapping the ARM CPUs - effectively making the ARM a coprocessor to the VPU. The config.txt and *.elf files you have to put on the SD card are the OS for the VPU and bootloader for Linux that gets loaded to the ARM cores.

Ctrl-[ is escape in ASCII (not specifically ANSI/VT100/etc), and Ctrl is sometimes abbreviated as ^.

I don’t know the exact history of why this is a thing that comes up with vi often. My guess is that ESC on the ADM-3a terminal that vi originally targeted influenced it. On ADM-3a, ESC is where tab is on a PC-101 keyboard, a comfy key to hit while touch typing. When later terminals started to move ESC a couple of rows up it was more ergonomic to hit ctrl-[ instead.