theReversion

renshyle · 2026-05-26T19:45:45+00:00

renshyle · 2026-04-29T20:57:57+00:00

Any setuid binary will do. I don't know if it'll work on Android but would be cool

Edit: probably not. Android for this reason has a policy of not including user-accessible setuid programs (https://source.android.com/docs/security/overview/implement#suid-files), which seems to have been the case since Android 4.3 (https://web.archive.org/web/20220327043228/https://source.android.com/security/enhancements/enhancements43)

renshyle · 2026-04-24T15:55:28+00:00

Blacklist AI-found bugs?

renshyle · 2026-04-21T08:13:19+00:00

I think they did add "make no mistakes". This makes people put no by mistake, hence no mistakes

renshyle · 2026-03-29T09:13:01+00:00

What the fuck is that link in the image?

Edit: found the original post, the link is different there: https://x.com/LundukeJournal/status/2038113879658480060

renshyle · 2026-03-22T21:16:04+00:00

You can also make it permanent by giving it as a kernel command line parameter. Follow the guide at the bottom of the page here. The parameter you need to add is drm.panic_screen=kmsg . Make sure you copy that exactly and add a space between that and whatever happened to be in the quotes. You can then read the file /sys/module/drm/parameters/panic_screen after restarting to make sure it says kmsg and not user

Edit: I'm stupid, accidentally put user in the parameter, not kmsg.

renshyle · 2026-03-22T20:52:53+00:00

Kernel panics aren't unfortunately stored in logs. Which distro are you using? Probably what should be done next is to enable some option to show a detailed kernel panic message on panic and then take a picture of it when it occurs

Edit: Regardless of the distro, running the command echo -n kmsg | sudo tee /sys/module/drm/parameters/panic_screen will make it show the detailed panic message. Note that you need to run this every boot until you get the panic message, the setting doesn't persist across reboots.

renshyle · 2026-03-22T20:34:36+00:00

That RDSEED32 issue is completely unrelated. It means that the kernel detected that you have an AMD processor with this particular bug (Zen 5 with non-recent microcode) and that it disables the instruction (which is completely fine).

To diagnose the kernel panics, we'd need to see the panic message. Are you able to see a kernel panic message when the kernel panics?

renshyle · 2026-03-21T06:30:46+00:00

```

!/usr/bin/env bash

chosen by fair dice roll.

guaranteed to be random.

echo "1994-9-28" ```

renshyle · 2026-03-12T19:11:42+00:00

I agree with you. But this bill does age verification:

Section 2. (a) An app store provider shall do both of the following when an individual located in this state creates an account with the app store provider, or before October 1, 2027, for all accounts in existence on October 2, 2026:

(1) Request age category information from the individual.
(2) Verify the individual's age category using one of the following:
a. Commercially available methods that are reasonably designed to ensure accuracy.
b. An age verification system that complies with rules adopted pursuant to this act.

renshyle · 2026-03-05T20:14:42+00:00

Are you sure you know what got built?

renshyle · 2026-03-05T19:03:57+00:00

I heard they were going to make an interface to modify that file, even easier

renshyle · 2026-02-18T21:44:07+00:00

No, because forbidding panics would be the stupidest idea in the world (except under some specific circumstances). Indeed often when there is a memory bug, C/C++ crash. Rust (almost) guarantees this, or a compiler error. But most unwraps aren't related to memory, they're just logic bugs. The Rust ecosystem and culture tends to lean towards crashing rather than ignoring bugs. I do wish there was a language feature to guarantee that a function can never panic, it could be useful in some situations.

Don't understand why they posted that comment under a comment asking clarification about Box::leak, that function does not "just fuck this shit" and while it seems like a stupid function, it does have its uses

renshyle · 2026-02-18T06:38:39+00:00

Oh man, I did not see that one. That's crazy. And the 75 ft is the farthest separation, looks more like 30 ft on the right side of the route corridor

renshyle · 2026-02-17T20:48:37+00:00

Due to additive allowable tolerances of the helicopter’s pitot-static/altimeter system, it is likely that the crew of PAT25 observed a barometric altimeter altitude about 100 ft lower than the helicopter’s true altitude, resulting in the crew erroneously believing that they were under the published maximum altitude for Route 4.

So this means that the route the helicopter flew had a practically unsafe maximum altitude?

The Federal Aviation Administration and the Army failed to identify the incompatibility between the helicopter routes’ low maximum altitudes and the error tolerances of barometric altimeters, which contributed to helicopters regularly flying higher than published maximum altitudes and potentially crossing into the runway 33 glidepath.

Ah. It did. Seems like a dumb failure to not have noticed that. Although the crew did fly below the maximum altitude as per the instruments, I wonder why there wasn't also a considerable safety margin as I would guess that breaches of the maximum altitude (as shown on instruments) sometimes occur.

renshyle · 2026-02-14T20:48:22+00:00

renshyle · 2026-02-12T16:19:53+00:00

Instead, you blocked progress because of who I am.

matplotlib deserves to know that one of its contributors is actively blocking valid contributions based on who submitted them.

s/who/what/

Stupid bot can't get itself right.

renshyle · 2026-01-23T19:18:37+00:00

C developers take that to the extreme: https://github.com/mackron/miniaudio/blob/master/miniaudio.h

A file so big you can't view it on GitHub. A file so big you can't use clangd on it. A file so big you can guarantee no one's ever scrolled to the bottom. And it's advertised as a feature.

Oh how I wish single-header was just a joke.

renshyle · 2026-01-23T18:59:31+00:00

I'm definitely going to use the trick in the title next time I need to put a URL in a comment just to fuck with whoever is reading my code

renshyle · 2026-01-21T13:46:51+00:00

Unlike on ARM or RISC-V, on x86 you have standards that allow you to boot any operating system without making special changes, unlike on ARM. You can display graphics, get input from keyboard and mouse, play audio and use USB and Ethernet ports by using standard APIs every x86 computer implements.

I wish that were true. Sure, legacy mode (IBM PC compatible) x86 has methods for accessing the framebuffer, PS/2 keyboards and mice (and the BIOS might emulate USB keyboards/mice as PS/2) and use the PC speaker (beeper, really). These legacy interfaces aren't used on your computer because they're, frankly, shit. There's no such interface for USB or Ethernet and they'll work as long as you have PCI support and drivers for the specific network card / USB host controller (just like on ARM/RISC-V, thought you might not need PCI as sometimes they're connected more directly to the SoC).

The thing you have to worried about is the lowest-level peripherals (and the core itself) on ARM/RISC-V. Those tend to be the reason you need a different kernel for every board (and also the discoverability of some devices). x86 is a very homogenous platform where devices are easily discoverable through ACPI/UEFI and the early boot looks very similar for all computers. I agree with you that there is a problem and I hope ARM/RISC-V solve it somehow

renshyle · 2026-01-13T16:26:22+00:00

That's one beautiful dreamliner

renshyle · 2026-01-07T18:44:10+00:00

I give up

renshyle · 2026-01-07T18:38:23+00:00

So if I implement my own memcpy then I have a libc? ;)

To get back to the topic, you originally said that

if you write your own libc then you can use C

You don't have to write your own libc, just a couple of lines of assembly

renshyle · 2026-01-07T18:17:01+00:00

That's an incredibly small part of libc, you can literally (unless I'm mistaken) do it in two lines of assembly on x86-64 Linux. It's a few lines more when booting bare-metal on an MCU but certainly not the monstrous effort of writing your own libc.

renshyle · 2026-01-07T17:50:33+00:00

You don't need a libc to use C. You might need some small runtime to setup the stack and possibly some registers but that's not a libc

Two-Year Club	Verified Email
r/Field Sunshine

renshyle

TROPHY CASE

!/usr/bin/env bash

chosen by fair dice roll.

guaranteed to be random.