any commutators in the chat for a pre-print?
any1 coping/seething 2day?
Replying to @__phantomderp
hit up the relevant netbsd/openbsd lists, they have porterboxes (well, "box" is a generous term for a fridge, but you get my point)
Replying to @__phantomderp
(but also your laptop can run as many fully-featured SIMH VAXen as it has CPUs so)
Replying to @__phantomderp
ive sent mail to/from 4.2BSD-on-SIMH before. Just Works. presumably if you install a system not-from-1983 you can do equally contemporary stuff like ssh
Replying to @__phantomderp
https://twitter.com/nabijaczleweli/status/1524793951001137156
its always "dont open up microwaves", "microwave parts are dangerous", "you can't re-use the bits anyway", but like, its very easy to repurpose the HV/EM parts into the last thing you see, so
god i love POSIX phrasing
in just enumerating du flags ive already encountered a classic coreutils lie moment: https://bugs.debian.org/1014357
Replying to @nabijaczleweli
twofer https://bugs.debian.org/1014360
Replying to @nabijaczleweli
threefer AND consecutive? oh my https://bugs.debian.org/1014361
Replying to @nabijaczleweli
turns out elaborated-type-specifiers do NOT sit well with pointers-to-member, christ
Replying to @nabijaczleweli
gdb-induced momentosis
Replying to @nabijaczleweli
/and/ a free mandoc parsing bug! https://inbox.vuxu.org/mandoc-discuss/20220705151536.tqmlsw4z4pqraue6@tarta.nabijaczleweli.xyz/T/#u
y'know what just occurred to me; this usage string for du is 450 bytes. more than 20 /entire/ programs from V1 (represented here by unix72)
when minecraft posters use the third-person reverse camera and talk? thats vtoob
Replying to @nabijaczleweli
du --time writes in date(1) format, so ive been writing the date(1) date formatter (which is similar but different from strftime(3) because fuck you), so ive found a coreutils date bug instead: https://bugs.debian.org/1014436
Replying to @nabijaczleweli
all i want for christmas is farsi proficiency (proving santa isnt real NOT CLICKBAIT)
Replying to @nabijaczleweli
hm
Replying to @DogGirlJane
king
any grass touchers?
how the fuck am I SIGILLing. my brother in christ clang wrote the code
Replying to @nabijaczleweli
okay its a segfault with -O3 at least. what the fuck is clang generating that it /SIGILLs/ then???????
Replying to @nabijaczleweli
huh
Replying to @nabijaczleweli
bruh
Replying to @nabijaczleweli
ok if i remove a [&]{}() IIFE wrapper it works. im gonna cry
Replying to @nabijaczleweli
notably: I replaced /all/ the non-PODs in the IIFE with manual memory management before trying this
Replying to @nabijaczleweli
(1) crashes, (2) doesn't; the only difference is, indeed, those three commented-out lines
Replying to @nabijaczleweli
oh my fucking god i didnt have a return at the end. why did neither clang nor gcc warn me. im so mad
Replying to @nabijaczleweli
ok i thought it was because i didnt have -Wall -Wextra but thEY ALSO DONT WARN. WAHT THE FUCJK
Replying to @nabijaczleweli
am i losing my goddamn mind
Replying to @nabijaczleweli
for FUCK's sake. i specced -isystem instead of -I. fun fact: that code /has a forbidden narrowing conversion in {}/, a hard error, that -isystem also covered up
Replying to @nabijaczleweli
i hate strftime. in year -90 for %010F im getting 0-90-mm-dd instead of -090-mm-dd like you'd expect (well, from date(1)). for %04z im getting 000+0200 (?!??!??!?!) instead of +200 (like date(1), but thats also the only sensible output)
Replying to @nabijaczleweli
I HATE COREUTILS I HATE COREUTILS
Replying to @nabijaczleweli
note how this shit doesn't even degrade gracefully, right. all :-quantity variants of %2O:::z are literally, unquestionably, plain wrong
Replying to @nabijaczleweli
https://bugs.debian.org/1014497
after literal years i got signed out of android pisscorp and its apparently impossible to sign in if you don't have play services now, even if you haven't updated the app once :)
Replying to @nabijaczleweli
lmfao glibc strftime() domain error; tm_year is the year /minus 1900/: [-2147481748; 2147485547] are i32 + 1900, and coreutils date deals with that correctly; glibc, OTOH, does /not/ and does an unchecked addition(?) – the most positive and most negative times differ by 1 day :)
Replying to @nabijaczleweli
http://bugs.debian.org/444589, apparently, reported 30 Sep 2007 for etch; 0 replies before my own
Replying to @nabijaczleweli
15.5kB/340L of dense C++ just to paper strftime(3) over date(1); hate it here!!
Replying to @nabijaczleweli
im like half-convinced im just cultivating peas at this point
Replying to @nabijaczleweli
hehe
accomplishing in 6 minutes what WG21 couldn't since 2017-01-30. fuck sake.
Replying to @nabijaczleweli
another time-based du bug, apparently coreutils considers year -90 to be later than 2021? and literally swallows it when specified explicitly, defaults to epoch????
Replying to @nabijaczleweli
what the fuck are they *doing* to this poor fucking thing
Replying to @nabijaczleweli
(also found an unrelated tree bug while bisecting that one, because of course: https://bugs.debian.org/1014621)
Replying to @nabijaczleweli
--separate-dirs. of course. and it's different on my rout^Wx32 machine, which hints that it's an even worse initialisation bug. delightful
Replying to @nabijaczleweli
filtering by du got me this old classic: https://bugs.debian.org/1007777, in which an apparently-corrupted filesystem /made du SIGABRT/. the funniest thing is that du, after i wrote the date(1) formatter and parsed all options, was a 2-hour "fill in the blanks" for me. HOW is coreutils s
Replying to @nabijaczleweli
i mean, this is a three-fold bug because -S documentation doesn't say it affects --time at all. so.
Replying to @nabijaczleweli
americans think about the past challenge (difficulty level: impossible) https://bugs.debian.org/1014622
Replying to @nabijaczleweli
consecutive numbers :0
Replying to @nabijaczleweli
posted all of this under the wrong root because im thick as pigshit https://twitter.com/nabijaczleweli/status/1545572394198306816
Replying to @__phantomderp
uuh, mbrtowc(3) (by returning a (character, len) pair) and mbsrtowcs(3) (by returning the next-sequence pointer) do, and they're in C99, so?
Replying to @__phantomderp
the iconv family is entirely unrelated to the rest of the ones you specced – it transliterates a byte stream to byte stream, is unaffected by the current locale (well, nl_langinfo(CODESET) if you've gotta), requires full-character alignment, and uses an unrelated mechanism
Replying to @__phantomderp
most importanly, you don't get actual characters out of it (also, i recall hearing that the gnulib iconv supporting code is fucking wild with corner cases/platform idiosyncracies)
Replying to @__phantomderp
oh wow, even better: glibc goes absolutely fucking apeshit (returns 0 for each mbrtowc() after the initial one that eats 2 bytes; herein wc modified to write the resulting character)
guy who advertises rice as "fabulous new no-grind grain!"
well that's fucking embarrassing
Replying to @nabijaczleweli
ive had it like this since i originally ported it for df on 2021-07-18. it took me literally exactly a fucking year to notice why it's off. kernel modesetting tbh
MEKHANE enthusiasts really out here like "i can fix her", huh
but wasnt eth already a piece of shit chain? what could they mean by this
bro i fucking hate it here point-blank derives from fucking point blanc i want to sleep a thousand deaths
Replying to @nabijaczleweli
this is my god-damn jokair moment
Replying to @nabijaczleweli
i also had the damn fixed-width format string backward, which is also very obvious!, but I didn't notice until i spent [REDACTED] essentially re-implementing "don't do the dot if .0". kernel modesetting 100%
Replying to @nabijaczleweli
how. HOW. my implementation, for every pattern, literally (figuratively: manual strcspn()+strspn()) strtok()s the path, then fnmatch(3)es. how could that POSSIBLY be faster than whatever bullshit coreutils does. how could it be FOUR TIMES faster
Replying to @nabijaczleweli
im going insane
Replying to @nabijaczleweli
(yes, coreutils du --exclude is /four times/ slower! if you give it a trivial expression!)
Replying to @nabijaczleweli
if you permit trivial-string optimisation then, well, i'm 471.5x faster (for the cost of three lines) :)
Replying to @nabijaczleweli
laughing-stock. https://bugs.debian.org/1014738
RT @nabijaczleweli: what if the ZFS Event Daemon had drip?
Replying to @nabijaczleweli
okay i don't get out of bed for less than 1000x but its still fun to laugh at monopolies https://twitter.com/nabijaczleweli/status/1377977095163351044
Replying to @nabijaczleweli
mildly annoying to have iteration times of 3 hours instead of 20 seconds, [c++ joke here], but i think ive arrived at a local winner
Replying to @nabijaczleweli
updated to current sid and it Just Worked :0
Replying to @nabijaczleweli
the year of linux on the babtop has arrived, after only one year, six months, and two weeks
finally bisected the coreutils dd data loss bug i had a comment for in my tests for close to a year now https://bugs.debian.org/1014839
Replying to @nabijaczleweli
well, okay, I just thought it was just an unexpected interaction or whatever, but yeah nah its just a data loss moment
W + ratio
left: clang trunk, bullseye gcc (10.2.1-1)
right: Issue 7
why!!
Replying to @nabijaczleweli
"but it's CX" yeah so why isn't there a flag to make the format string checker check for POSIX strings! if the only way to work around a hard false positive is to #pragma GCC diagnostic (-Wformat in this case) then it's a compiler bug. blergh
Replying to @nabijaczleweli
turns out i cant fucking read (and the man-pages page for this is noodly), and speccing "%1$ *3$.1f%2$c" works on both, no warnings; still: godawful warning especially from clang (less so from GCC, whose warning is correct, but unclear)
what, and I cannot stress this enoguh, the ABSOLUTE FUCK
Replying to @nabijaczleweli
im the dumbest motherfucker on planet earth
Replying to @nabijaczleweli
and a consecutive twofer for FreeBSD: https://bugs.freebsd.org/265199 https://bugs.freebsd.org/265200
ill be honest, i didnt expect 5kg bags of flour to be so unwieldy
Replying to @atomicthumbs
`sudo passwd -d $(id -un)`?
Replying to @CoyoteDen and @atomicthumbs
and you're basing this on what? this is not the case for default sudo.conf(5)/sudoers(5) and a skim over the latter doesn't reveal an obvious way of making that be the case. making the account passwordless is /exactly/ what was requested
Replying to @CoyoteDen and @atomicthumbs
?
Replying to @CoyoteDen and @atomicthumbs
the former is a valid concern, sure; the latter (well, not gksudo, since that got removed in stretch because apparently it was not fit for purpose, but polkit, which I can only assume this is) Just Works, and, indeed, doesn't even prompt for confirmation
Replying to @AssembledGhost
very long voyages, long sight-lines, relatively slow movement v/v the medium and other vessels, hull breach being the ultimate downfall of the vessel => naval
Replying to @nabijaczleweli
do you think you blanket rising doughs so they don't wake up before you cook them
Replying to @nabijaczleweli
how the hell did i shake a 1/15th shot?? must be a bublik deficiency
linux integer parsing moment lmao
Replying to @nabijaczleweli
i was hunting for an overflow bug, but just found a horrible lie instead: https://bugs.debian.org/1014971
mfw a distribution image has the root account passphrased
Replying to @ErisMeatPuppet
i favour single-user mode or passwd -R but yeah
Replying to @nabijaczleweli
anyone taking bugs for V7 du? (represented here in its kingest of forms – V7/x86 https://www.nordier.com/#v7x86)
Replying to @nabijaczleweli
spot the bug (4.3BSD-Reno)
fuck abraham and his prophecies, im investing all my deicoin into acyclovir
Replying to @nabijaczleweli
fucking shameful
WHY does that university site not resolve im gonna CRY
Replying to @nabijaczleweli
fuck this. fuck it all. im done
Replying to @nabijaczleweli
classic standard moment in XPG2 land. writes in 512-byte chunks except when it doesn't. hides errors sometimes. if you suspect you should get an error, try -r? may or may not actually reflect the space used. fuck you.
Replying to @nabijaczleweli
at least it's actually marked PI (The behaviour cannot be guaranteed to be consistent); but this is all in addition to OF (Output format incompletely specified), because it isn't, and UN (Possibly unsupportable feature) because fucking lmao try seriously considering "-r but not b
Replying to @nabijaczleweli
okay okay im like Reading this and i think this doesnt actually.. say anything. also note that the file in -a description is italicised, so it means "for each argument". as-specced, this is literally just a hash function
Replying to @nabijaczleweli
i think this is all it actually says
Replying to @nabijaczleweli
at last: preprint
i hate phototypesetters I HATE PHOTOTYPESETTERS
fun moment. coreutils rm -d just straight up refuses to remove an unreadable directory, doesn't prompt if -i, and lies that it tried to. what the FUCK is happening
Replying to @nabijaczleweli
https://bugs.debian.org/1015273
Replying to @nabijaczleweli
l + bublik + ratio
i just wanted to do timezones portably and found a gcc bug instead https://gcc.godbolt.org/z/6a87eonW1
Replying to @nabijaczleweli
hm, this says "may" so this is legal. boo http://eel.is/c++draft/temp.res#general-6
Replying to @nabijaczleweli
i just wanted to do timezones portably but had to write the stinkiest C++ possible http://coliru.stacked-crooked.com/a/591b8f491b813c13
i love freebsd
Replying to @nabijaczleweli
https://bugs.freebsd.org/265319
i love illumos
Replying to @nabijaczleweli
the Topicbox "Join the Conversation" button says joining will let me post, but it also 250 2.0.0 Queued as 8223A064D31 so who knows
Replying to @eatijr
appx. 100g of flour
third-party analysis (1) tells me im reaching levels of slavic heretofore unseen
can someone PLEASE explain to me why ext4 truncates file times at 0x37FFFFFFF
Replying to @nabijaczleweli
for packing. documented so its fine or whatever
Replying to @nabijaczleweli
it appears my cow cosplay has been put to rest, so this must've been some sort of additive; bublik enjoyers stay winning
Replying to @gaysexdotgov
yeag
Replying to @nabijaczleweli
top 10 salty spelt baker moments
guy who considers tights blackleg
hm. in the seventies, AT&T was the largest computer game manufacturer and distributor by far
Replying to @nabijaczleweli
i realise this is like an insane take right but i think its also literally true by any metric?
given the givens (<title>Impersonate Page), so we think this is a correct namecheap e-mail or nah
Replying to @nabijaczleweli
its valid what the fuck
Replying to @Namecheap
both the text/plain and text/html versions are identical, yes; also: maybe don't have a title of "Impersonate Page"; also: the text/plain version of this has entirely stripped links, which is worse (the text/html has "our website" linked)
Replying to @nabijaczleweli
okay it went through. borderline ecstatic i have no business relationship with namecheap anymore
another POSIX bug (left: XBD, 5 ("File Format Notation"); right: XCU, 3, cksum)
Replying to @nabijaczleweli
https://www.mail-archive.com/austin-group-l@opengroup.org/msg09964.html
Replying to @nabijaczleweli
existing practice says i can output tabs. hog. https://www.mail-archive.com/austin-group-l@opengroup.org/msg09965.html
Replying to @nabijaczleweli
:/
preprint: (1); lie: https://bugs.debian.org/1015996
Replying to @gray_dot_bmp
we'd need BRISTOL STOOL CHART 1..7 to combine with PILE OF POO to accurately scale emoji prefixes imo
fresh! (3 years old, added in 8.31 (2019-03-10)) coreutils env bug(?)
Replying to @nabijaczleweli
gamer moment https://bugs.debian.org/1016049
Replying to @pixelbeat_
sure, and I even agree that it's useful, but the documentation describes the format as -b-s[=s[,s]...] (via a clumsy synopsis and prose, cf. the debian bug), which is not satisfied by the empty string; -b-s[=[s[,s]...]] could be =SIGS, "SIGS is a c.-std list of signal names li…"
Replying to @nabijaczleweli
:v
Replying to @nabijaczleweli
my stupid ass forgot the second egg once and thats why they werent fucking rising. anyway: bublik + ratio
Replying to @eatijr
no, but only because live fish don't sediment out
Replying to @eatijr
but then they're dead fish so they're not in the aquarium as-described. otoh live fish do shit and the shit is outside of the fish even while it's inside so even then its shaky
pinky print :0
i hate the gnu compiler collection. I HATE THE GNU COMPILER COLLECTION
Replying to @nabijaczleweli
cringe-ass nae-nae baby https://gcc.godbolt.org/z/xY8zqe36T
Replying to @nabijaczleweli
also note how the gcc error says 'static' and it very much is not literal static
Replying to @nabijaczleweli
lovely. love that. big fan. its an anonymous namespace thing https://gcc.godbolt.org/z/5rvnPdE8j
Replying to @atax1a
no fucking way
gamer moment
Replying to @nabijaczleweli
:0
i go to bake one set of bread and now "doing what you're paid for" is "quiet quitting" i hate yanks
last one babey https://twitter.com/nabijaczleweli/status/1541705431004971008
Replying to @nabijaczleweli
im in agony
Replying to @nabijaczleweli
how the fuck do babies do this now that we figured out blood thinners give them brain damage
Replying to @nabijaczleweli
okay i guess they do scream 24/7
Replying to @nabijaczleweli
im also like 2kg down since this tooth started lmao