pelya

Back in the 80386 days there was one model of BIOS that would print ‘CPU not found’ if you had your CRT monitor and VGA videocard plugged in.

You simply need to accept the risc.

I guess that phone would use eSim, so no slot is needed.

This needs some simple hardware trigger, that can be queried by bootloader, but specific wnough so it won’t trigger in your pocket. If buttons are unavailable, I can propose several idead:

• Cover the proximity sensor 10 times per second. Requires good motor skills.
• Shine separated red, green, and blue lasers into three of the phone cameras. You’ll need a box with three different-colored LEDs to cover cameras module.
• There is a low-speed data channel in wireless chargers. Just add the button to the charger instead of the phone.
• Put your phone at exactly 2.5G of acceleration. Accelerometer is easy to use even from the bootloader, however you will need to put your phone in a centrifuge and reboot it while it’s rotating.
• An option ‘Reboot into recovery’ in system settings, duh. Won’t help if your ROM fails to boot.

I recently used my cast iron pan to roast peanuts. 20 minutes roasting on low flame, preceded by two hours of flame torture to burn off dust and re-glassify the 60-year-old layer of burned grease.

“How do we make a 7-feet-long blade with a 25-foot-long edge?”

Ask the guy to hold down the wolves while I teach them how to install Debian

Because TeamViewer will set up a port forwarding and a NAT traversal for you.

VNC and RDP only work when your host has a public IP, or you know how to set up a proxy.

RISC-V is not proprietary enough.

So if I’m developing a garage door opener using ESP32 RISC-V module, I’m not a RISC-V developer? The dev tools and the cross-compiler only come in x86_64 variant, they simply won’t work on RISC-V laptop. But at least they provide a Linux installer.

The only use case I can think of is to build Debian packages on a target architecture without cross-compilation, because many packages do not support cross-compilation, but it’s more an issue of poor build scripts.

Targeting developers is, I dunno, misses the audience. It would have been a great netbook, or a Raspberry Pi replacement.

If I develop something for Risc-V arch, it is probably some embedded thing with 100 MHz CPU and 2 Mb RAM, and I am cross-compiling it anyway on my more powerful PC.

It’s false that you cannot sell GPL-licensed work.

Busybox was quickly replaced by BSD-licensed Toybox everywhere for that exact reason.

Copyleft licenses (like the Gnu General Public License) mandate that all derivative works remain free.

This is false. It’s perfectly legal to take GPL-licensed work, modify it, and sell it. As long as the work itself does not reach the general public, you don’t need to release it’s source code to the public (e.g. your work for the military, you take money for your work, and provide source code to them, but not release it publicly).

TIL someone ported the collection of classic Linux screen savers to Android.

I’m in the same boat, I have (or rather had) published a few Android games which I don’t have time to update anymore, and Google had been unpublishing them one by one.

The first one is a fancy CPU warmer. The second one will play loud noise through your headphones, and setsid will make sure you can’t stop it with Ctrl-C.

There was a thread about console commands seen in movies or TV, when the actors need to do some ‘hacking’ on camera. And the most common one was just installing updates to your Linux distribution of choice.

My go-to joke is

cat /dev/urandom | pxz | grep haxx

Or if you want to be nasty

setsid sh -c 'cat /dev/urandom | pacat -p'

As for puns, less command does the same thing as more on MS-DOS.

tar c file | pxz > file.tar.xz

Baptise

Because military engineers overengineer these things from the most expensive materials available, and they also perform frequent maintenance on them, which is also expensive.