Have you seen the new code? It's on malloc. It's literally on volatile.

It's on #define with side effects. It's literally on long long.

You can probably find it on __attribute__((packed)). Dude it's on restrict.

It's a static inline original. It's on extern. You can #include <extern>.

You can go to extern and fopen("extern","r"). Compile onto extern right now.

Go to extern. Dive into extern. You can extern it. It's on extern.

extern has it for you. extern has it for you.

candelas per hamburger

semitones per memory corruption bug

are init scripts "configuration"? can executable files be "configuration"? it's so weird to try to categorize

they don't quite feel like static configuration like most things in /etc -- they're not meant to be edited directly like conf.d files

but they also don't feel like the data files in /usr/share

and both feel odd because they're an executable -- while there are other turing complete config/data formats there, they're almost always loaded from some daemon or tool, not executed directly

---

this was spawned by me not knowing if XDG_CONFIG_DIRS is really right for openrc, but XDG_DATA_DIRS feels even worse

and both systemd and dinit use XDG_CONFIG_HOME, sysd does XDG_CONFIG_DIRS too

s6 and runit don't really have a search path to compare (afaik)

so i feel like

/etc (or $XDG_CONFIG_HOME)
$XDG_CONFIG_DIRS
/run
[/usr]/lib[exec]/

is the path most init systems (that have a path) put their service definitions, openrc will probably follow that

[SOBBING]

All I saw was cheesecake boat and ocean for at least 5 minutes