大家好

shark vs the universe
$LAYYYTER
2025 on Tumblr: Trends That Defined the Year

No title available
KIROKAZE
almost home
No title available
d e v o n
noise dept.
Noah Kahan
ojovivo
No title available

gracie abrams
The Bowery Presents
NASA
The Stonewall Inn
untitled

Origami Around
🪼
RMH

seen from Bangladesh

seen from United States
seen from Türkiye

seen from France

seen from Singapore
seen from Germany

seen from Malaysia
seen from United States
seen from Portugal

seen from United Kingdom

seen from Austria
seen from Belgium
seen from Ukraine
seen from United States
seen from Türkiye
seen from United States

seen from Türkiye
seen from Colombia
seen from Brazil

seen from United States
@ariusha
大家好
tricked into watching the first 10 seconds of an ad because Ooh Pretty
aurgh i am now on major kernel rewrite №6
most of them have been just rewriting the contracts for a single component to make it "cleaner", but that means everything that touches it need to be slightly either twiddled or completely rewritten
which usually means i make another local project, copy over the "clean" components, rewrite the bit i want, and then slowly merge back components until either i am back to 75% of a kernel or i enter an overtired fugue state and unravel the secrets of safe & reuseable abstractions
i have about 10ish components, 4 or 5 of which are as clean as they'll ever be, and like 5 more left to write
if i understand what i need to do to implement pci, acpi, and my own uneducated take on procfs, (which i don't), i should only need to write 5 or 6 more components, and only 2 of them might involve fundamental rewrites
the primary problem with the unix architecture (other than random legacy cruft) is that there is no good way for programs to provide services to eachother. d-bus, wayland, x11, all rely on sockets and shared memory to communicate, sacrificing structure to allow these programs to exist outside the kernel.
kernel services have much easier, structured communications with userspace through filesystem-mapped devices. the /sys subsystem, even most of the ancient protocols of /dev, all provide elegant and discoverable interfaces to kernel services that userspace can barely mimic.
all of this encourages an ever-ballooning kernel size. the worst part imo isn't even that all this random shit like networking is running in kernel space, it's that the kernel and all the kernel modules are just such massive components now that they're difficult to work on without prior experience in the codebase.
now FUSE is definitely a step in the right direction, but it is unequivocally the pinnacle of legacy cruft. even the simplest readdir calls require messing with e.g. hardlink reference counting to maintain correctness in edge cases like e.g. using a rename() call to move a file between different mountpoints.
on the other hand, the solution to this has already been demonstrated: plan 9 from bell labs solves the crux of the issue (although still not entirely escaping the legacy cruft from back when it was just designed to export a unix filesystem). it still has the issue of drivers being merged into kernel space, but this seems to be out of inertia rather than out of necessity. and it doesn't seem to take much of a performance hit from serialising and deserialising 9p messages into a stream for communicating with the server program (since userspace file servers are just a managing program reading from and writing to a stream that is mounted into a kernel-managed 9p device file).
i have a kernel + os project (that i'm not yet ready to share, but soon) where i'm trying to fix this by shrinking the kernel to just a standard microkernel + 9p-like multiplexer. and i am not under the impression that this will ever be used for anything.
i am cooking up such a spaghetti of generics and trait bounds for synchronisation primitives
the primary problem with the unix architecture (other than random legacy cruft) is that there is no good way for programs to provide services to eachother. d-bus, wayland, x11, all rely on sockets and shared memory to communicate, sacrificing structure to allow these programs to exist outside the kernel.
kernel services have much easier, structured communications with userspace through filesystem-mapped devices. the /sys subsystem, even most of the ancient protocols of /dev, all provide elegant and discoverable interfaces to kernel services that userspace can barely mimic.
all of this encourages an ever-ballooning kernel size. the worst part imo isn't even that all this random shit like networking is running in kernel space, it's that the kernel and all the kernel modules are just such massive components now that they're difficult to work on without prior experience in the codebase.
now FUSE is definitely a step in the right direction, but it is unequivocally the pinnacle of legacy cruft. even the simplest readdir calls require messing with e.g. hardlink reference counting to maintain correctness in edge cases like e.g. using a rename() call to move a file between different mountpoints.
on the other hand, the solution to this has already been demonstrated: plan 9 from bell labs solves the crux of the issue (although still not entirely escaping the legacy cruft from back when it was just designed to export a unix filesystem). it still has the issue of drivers being merged into kernel space, but this seems to be out of inertia rather than out of necessity. and it doesn't seem to take much of a performance hit from serialising and deserialising 9p messages into a stream for communicating with the server program (since userspace file servers are just a managing program reading from and writing to a stream that is mounted into a kernel-managed 9p device file).
i have a kernel + os project (that i'm not yet ready to share, but soon) where i'm trying to fix this by shrinking the kernel to just a standard microkernel + 9p-like multiplexer. and i am not under the impression that this will ever be used for anything.
electron tube
bought from antiques store
information:
- model "6cm5" electron valve
- beam power pentode
- australian / new zealander
- requires 500-watt power supply to be useful
- glass vacuum is intact and filament works
- i am unwilling to give it more power than from my multimeter (i am not trusting it)
- manufactured in 1950s / 1960s
cleaned it up
"mullard" manufacturer
a person has pulled off the anode cap (separate metal component on top) in the last 70 years, and there is a wire sticking out
啊哈!i have soldered that component on top again
there is no lead left in my lungs)))
这是我那愚蠢的孩子
dialectical materialist philosophical concept: "the law of the unity and conflict of opposites" -> all movements are the result of multiple conflicting forces.
example:
"yanqui blue party rhetorically claims prosecution of president Maduro must be lawful and unbiased"
force 1. it is logistically mandatory, but in no way justified, for the american empire to capture Venezuela
force 2. red and blue parties must convince usamericans that they are in opposition to each other
force 3. republican party is not following "legal" procedure to invade Venezuela (ignoring congress, abducting president Maduro, all of this for out-of-scope strategic reasons)
result: the democrat party must oppose the republican party, but cannot take any effective action against the invasion (as it is also in their interest). therefore, the democrat party must criticise minor aspects of the republican party's methodology
electron tube
bought from antiques store
information:
- model "6cm5" electron valve
- beam power pentode
- australian / new zealander
- requires 500-watt power supply to be useful
- glass vacuum is intact and filament works
- i am unwilling to give it more power than from my multimeter (i am not trusting it)
- manufactured in 1950s / 1960s
cleaned it up
"mullard" manufacturer
a person has pulled off the anode cap (separate metal component on top) in the last 70 years, and there is a wire sticking out
electron tube
bought from antiques store
information:
- model "6cm5" electron valve
- beam power pentode
- australian / new zealander
- requires 500-volt power supply to be useful
- glass vacuum is intact and filament works
- i am unwilling to give it more power than from my multimeter (i am not trusting it)
- manufactured in 1950s / 1960s
electron tube
bought from antiques store
我朋友的柠檬猪
"please use the docker image for our program" no.