end me
funny how "stack overflow developer survey" lists "HTML/CSS" as a programming language, but doesn't list roff. mark of the times!!
Replying to @atax1a
doesn't
Replying to @nabijaczleweli
there's an ethnicity question and i misread one checkbox as East Sussex and i cannot measure the psychic damage i took
work laptop btw, and the fans are Going
happy pride month to all australians, i applaud your perseverance in face of your vowels being in what society would call the absolute wrong places
me
a C++ programmer wrote this template
DESSICANT
SILICA GEL
DO NOT EAT
DANGEROUS
THROW AWAY
Replying to @nabijaczleweli
babe wake up, new dessicant messaging dropped
VGA GPU (400W)
Replying to @nabijaczleweli
dont tell seasonic, but i plugged it into a 5700XT which doesnt have a vga output (but it does have the six-pin hole spaced to fit an eight-pin, which I thought rather neat)
nieblo*d
girls on this website, or something, dunno
My Cat Smells Of Cat Spit! And Other Unexplainable Mysteries
Replying to @atomicthumbs
three-way multitenancy on the gameing motherboard, what a time to be alive
FreeBSD (Free Berkeley SystemD)
Replying to @nabijaczleweli
unbothered, moisturised, in his lane, well-hydrated, flourishing
anyone ever get an urge to just write coreutils
Replying to @nabijaczleweli
busybox is more than fine for what it is, but it also sucks ass for interactive use for that very reason, and GNUwno coreutils have several outstanding problems that are simply unsolvable because you can't patch them (and also they're GNU, which is reason itself to berid thereof)
Replying to @nabijaczleweli
like we would all be better off if someone forked NetBSD coreutils and provided a mostly-drop-in-equivalent interface for GNU coreutils
Replying to @nabijaczleweli
like, the very ability to have an rm(1) with error reporting as good as the Macintosh one without needing to send feet pics to stoolman would be good enough for me
Replying to @nabijaczleweli
i mean, how hard would it really be to get NetBSD coreutils to be drop-in Policy-compatible, really, and to backfill the rest with simple C++
Replying to @nabijaczleweli
yes I've seen the Rust coreutils, they were annoying and Rust doesn't (didn't? last time I tried I had to port half my dependency tree and LLVM generated broken/missing relocations) have a competent x32 back-end
Replying to @nabijaczleweli
like, dpkg -L coreutils | grep bin/ is just 105 lines and half of that is shit no-one has ever used before and ls with presets
Replying to @nabijaczleweli
i may be most a two-liter bottle of harslevelu in, but I still oddly think that's not that outrageous a concept, really
Replying to @leftpaddotpy
x32 is an x86-64 ILP32 ABI; in the context of Linux support, yes, you do enable it at configuration time on an x86-64 kernel like i486, and if Rust were Go, the story'd end there,
Replying to @leftpaddotpy
but because it isn't, like with any ABI, you also need a userland to match, and for environmental reasons (openssl, libssl, libgit2, &c.), you end up with pretty much 90%, if not more, of a normal system for any non-trivial program
Replying to @leftpaddotpy
so, yes, you can run normal amd64 Rust binaries on an x32-capable kernel just fine (and if you're on Debian, you already are! x32 syscalls are just a cmdline switch away), but on native x32 systems using Rust like that in any real capacity means a full second set of lib*:amd64
Replying to @leftpaddotpy
(hope that answers your question?)
Replying to @leftpaddotpy
musl does also support x32, but i haven't seen a quad to match, yeah
producing the binaries is also just half the battle, IME; when i did get gnux32 builds, most nontrivial programs would sigbus or segfault because the codegen Wasn't Very Good (improved in newer LLVM, i think?)
you're in her DMs. I'm scanning her argument vector. we are not the same
uhoh
Replying to @nabijaczleweli
waagh https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901636#40
has anyone done cppreference as man3/ yet?
think I just found a bug in FreeBSD's uname(1) lol
Replying to @nabijaczleweli
waaagh, it strips the whitespace differently than uname(3)
Replying to @nabijaczleweli
lol https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256486
[becomes hexavalent]
yo, when they do butt implants do they just.. stuff a bunch more poop in there?? or what. any1 know?
holy fucking shit Windows has now decided that it will not, in fact, be displaying the Notification Area at all past very early login; what exactly is the point of a commercial system that's literally more broken than early X
Replying to @nabijaczleweli
toggled a Widget, it reappeared, minimised total commander, its back babey
not only does netbsd unexpand(1) somehow destroy the glibc allocator so thoroughly that the only way to get it to not assert in malloc is to run it under valgrind, i also think its terminally broken for sone input patterns
Replying to @nabijaczleweli
i mean i cant really fault it, log indicates it got some fixes in 2009ish and i dont think the manpage has changed since 4.3BSD so all documentation is so out of date to be 100% meaningless
Replying to @nabijaczleweli
plus its already annoying enough to test even with a solid baseline, i cant imagine writing a remotely comprehensive suite of test data by hand. hell, i had to compromise on /my/ suite since its extremely superlinear and grows to hundreds of megabytes very easily
Replying to @nabijaczleweli
even then, some 512B random hunks and nonobvious -ts shuffled into 3MBish of fuzz reveal that, e.g., [2 spaces, "bread", 10 spaces, "whatever"] with -at2,26 yields [tab, "bread", tab, "whatever"], but it should be " whatever", since the w is 1 column beyond the stop, not on it
Replying to @nabijaczleweli
im quite sure because ive spent like 10 dry hours rewriting this and have 4 different spellings of unexpand that arrive at the same mismatches and i feel like im gonna throw up
Replying to @nabijaczleweli
pinnacle of consistency
Replying to @nabijaczleweli
not true actually! turns out my test dataset was unrepresentative! this is still fucked for some inputs!
Replying to @nabijaczleweli
фуцкин кмс дуде
Replying to @nabijaczleweli
genuinely the worst time ive had in a long time
Replying to @nabijaczleweli
three fucking days to get a sum +102 to behave right. just mercy-kill me at this point
just realised one of my friends has turned 21 this week. chilling
Replying to @nabijaczleweli
in no small part because that means that so will I this december, but in so many others because all I've done for, well, ugh, years, now, is stare at a screen and be depressed and/or angry, which is hardly of note, let alone import
i think instead of overloading operator[], std::vector should just have operator+(size_t) -> iterator and operator[] should remain *(vec + off) always
Replying to @nabijaczleweli
this goes for all standard containers like std::map, too
so you're telling me an electrical machine discharged this feature?
daemon (aff) vs god (pej!)
Replying to @nabijaczleweli
passed on to its next owner today – same description, photos, and price – as is tradition
Replying to @the6p4c
i recommend simply becoming part of a standardisation body and getting standards to opine on for free
Replying to @the6p4c
well, rather, this worked for me and WG21, I assume it'd be less easy for something like SD
Replying to @nabijaczleweli
also the packaging, which was also very clearly used before prior to me getting it, heh
warning!!!!! hog :)
Replying to @nabijaczleweli
this is also bollocks, seeing as it's been here for like a week(? reportedly) and I've last passed a full-size pig on the side of the road no more than a month ago
Replying to @nabijaczleweli
indeed, there's a multitude of pigs that just live here; i can't imagine what point this is supposed to make https://twitter.com/nabijaczleweli/status/1251224980366471171
splotchy cat in da flannel! unthinkable
need a girl to take me here 🥺
Replying to @nabijaczleweli
it's genuinely fucking insane that you can just download a 4.1BSD tape, but simultaneously it really shouldn't be an "it popped up on bitsavers" affair
Replying to @nabijaczleweli
(i really should publish the AMIX font extraction at some point, I even got it into a sensible format for Linux to use for VTs at one point, but then I upgraded from an 1024x768-in-normal-size to a 2K-in-hand-size uhidpi laptop which pushed that back a bit)
Replying to @nabijaczleweli
anyway I'm writing an env(1) page and apparently literally nobody notes when the single dash option happened and just says it's obsolete; so far, lessing over raw tapes, I think it split off printenv(1) in 4.2 and had it innately
Replying to @nabijaczleweli
The UNIX Heritage Society's 4.3BSD-Tahoe/{usr,src}.tar.gz are broken :/
Replying to @nabijaczleweli
apparently this is a known issue and there just isn't a base system of 4.3BSD-Tahoe in existence :(
Replying to @nabijaczleweli
the official canonical source of the CSRG ISO, which purportedly contains the source set is very dead, but http://archive.org has it, but it's 60kB/s and 560M. im going to die
Replying to @nabijaczleweli
currently in 2006
Replying to @nabijaczleweli
design language of a warez site but its entirely software you didn't think about since 2003
Replying to @nabijaczleweli
if ATT-SYSIII.7z is correct, env(1) existed in that form in SysIII; this is less helpful than anticipated, considering it's not in V7 and SysIII is derived from about seventy other different unixes
Replying to @nabijaczleweli
WARNING
Over-use of this program will cause it to go away.
Replying to @nabijaczleweli
love too types
Replying to @nabijaczleweli
it also uses =+, =-, =| and declares initialised data like this, which is truly enlightened
Replying to @nabijaczleweli
it's also written for a 16-bit int and too broken to link after you patch these all away such that a modern C compiler accepts them, unfortunately
Replying to @nabijaczleweli
oh my god
Replying to @leftpaddotpy
very much not so lol, needs =s
but a global =? -> ?=, this file, and booki() was pretty much all I needed to fix, which is astounding in its own right
Replying to @nabijaczleweli
"cbunix_man3_02.pdf", it can't possibly be, right? oh it is. the way it was meant to be read
Replying to @nabijaczleweli
i'm not sure what i expected from SourceCode/cbunix*.pdf, but it was /not/ filthy scans of pr(1)ed src/
Replying to @nabijaczleweli
🥺
Replying to @nabijaczleweli
we NEED to go back to the times when this was pertinent information
Replying to @nabijaczleweli
i'm gonna be honest, I didn't expect to (be able to) read an actual literal UNIX manual
Replying to @nabijaczleweli
like, ever
Replying to @nabijaczleweli
there's just something about the register (and presumed epistemological context to a significant but less obvious degree) of UNIX manuals that you can't get anywhere anymore
Replying to @nabijaczleweli
so true, bestie!
Replying to @nabijaczleweli
NOTE:
This page was copied from PWB/UNIX Release 2.0 (1H) and brought to you for your amusement.
Replying to @nabijaczleweli
"No shell", "cannot open password file", "no directory": consult a UNIX programming counselor.
Replying to @nabijaczleweli
the last two pages of the first PDF are.. completely different? cpio(1) from UNIX 5.0, which I assume means SysV, from a line printer (or photocopied, I guess, but it looks pretty clean? but I don't think the original can be anything else), and someone scribbled over them!
Replying to @nabijaczleweli
the second PDF starts with the much shorter cpio(1) from CB-UNIX, which likely means that that site had upgraded to a cpio(1) from a SysV distribution
similarly, 45(!) pages of the second PDF are csh(1) – native to 2BSD – printed on a dot matrix(!)
Replying to @nabijaczleweli
a true delight
Replying to @nabijaczleweli
> Getty also understands the "standard" ESS protocols for erasing, killing and aborting a line, and terminating a line.
this sounds much more insane when you remember ESS is the Electronic Switching System. standard protocols for killing and aborting lines on a telephone switch
Replying to @nabijaczleweli
oddly, that's also the diagnostic /I/ issue when my input is garbage or out of range!
Replying to @nabijaczleweli
aaaand here it is!
Replying to @nabijaczleweli
out of SysIII's parents listed on Wikipedia (Version 7 Unix, PWB/UNIX 2.0, CB UNIX 3.0, UNIX/RT, UNIX/32V): V7 doesn't have it (well, one tape does, but in usr/lbin, and no manpage), PWB doesn't (neither the Spencer nor Bostic version from the TUHS – the intro for both says (1)),
Replying to @nabijaczleweli
UNIX/RT isn't in the archive and there's one »"PDP-11 UNIX/RT ldp" files ?« alt.folklore.computers post, but it's narkive so it might as well not exist, and UNIX/32V doesn't have it either
Replying to @nabijaczleweli
> Downloaded: 2 files, 608M in 2h 35m 36s (66.7 KB/s)
aaand it just has 4.4. time well spent
Replying to @nabijaczleweli
and the winner is... 4.3BSD-Reno!
this is also congruent with the other tidbit i saw that people weren't happy about Reno doing POSIX conformance, hence Quasijarus et al.
Replying to @nabijaczleweli
i just wanted to not lie in my manpage and somehow ended up downloading 2.7G of UNIX source and deadmen
Replying to @nabijaczleweli
that being said, if anyone /does/ have a 4.3BSD-Tahoe source tree, I'd be ecstatic to have a copy
Give tape to SYSTEM GURU.
dae
one hundred and seventy three dollars for a PDF of a standard one-and-a-half-times my age, for which the current versions are free from the austin group
Replying to @nabijaczleweli
h-hello? based department?
Replying to @nabijaczleweli
pahz-itive is not how I'd describe reading most IEEE standards, generally
Replying to @nabijaczleweli
at least it's got a text layer
everyone's heard of -1 for errors, but have you heard of the -2 supererror?
as of to-day, my personality is no longer the sole magnetic thing about me!
Replying to @nabijaczleweli
this doesnt work as well when not forced by a selfie where I look deranged in front of a hospital, does it
Replying to @nabijaczleweli
it was definitely a nice vaguely socrealist hospital, but it didn't look like one, and i walked 2.4km mostly uphill to get there and apparently summer has started so it was 30 degrees, still, and almost high noon; can't force a gag with emulsions that are not fit for broadcast
Replying to @the6p4c
was it not the rumour that mister pfizer (who i assume excretes all vaccines) had figured out a way to express magnetism in the inoculated?
i think ive just found "the good shit"?
Replying to @nabijaczleweli
all I really want is POSIX.2, which is 100% unobtanium. NIST published POSIX.1-1992 via FIPS, which means you can freely download it. IEEE still wants over a hundred dollars for the PDF of a thirty-year-old standard
Replying to @nabijaczleweli
the interpretation (comments) is readily available, but it's (a) one PDF per page and (b) doesn't have the thing I want, even tangentially. pain
Replying to @nabijaczleweli
what a deal!
Replying to @nabijaczleweli
AFAICT, nobody /actually has/ POSIX.2. not IEEE – what's labelled "1003.2-1992 - IEEE Standard for Information Technology--Portable Operating System Interfaces (POSIX(R))--Part 2: Shell and Utilities" is just interpretation requests, not even NIST, which published it as well
Replying to @nabijaczleweli
the best reference so far is FIPS publication 189, which is 14 pages, incl. blanks, and it has what I need now (tangentially, would prefer the actual standard wording)
Replying to @nabijaczleweli
it also lists POSIX.2, but it's 7 pages and also published in 1994, which likely also makes it likely to be the interpretation requests
it's also in the NIST library on the main floor, so who knows
Replying to @nabijaczleweli
proverbially this close to mailing the austin group chair with puppy eyes
Replying to @nabijaczleweli
I've now mirrored all FIPS publications, and there's the entirety of POSIX.1 there, but just notes on POSIX.2 and how obsolete options apply to federal computer systems :(
Replying to @leftpaddotpy
gibberish, AFAICT, since https://dblp.org/db/journals/cacm/cacm4.html lists no such article
Replying to @alanc
interesting, cheers!
Replying to @nabijaczleweli
holy shit i think I got it
Replying to @nabijaczleweli
http://www.oldlinux.org/Linux.old/Ref-docs/POSIX/
Replying to @nabijaczleweli
final version
bitches b going outside dressed like this and still wonder why they're being homophobiad!
lads, how are we feeling about this?
you nicks
in good company lol
just had the worst hour of my life as my computer hard-reset and i seemed to've lost all 1191 tabs in my firefox session
Replying to @nabijaczleweli
turns out, even when you can't get to it from within firefox because it's too big, 1.5G is a happy size for appending addon userdata, even if the actual data blobs are somehow compressed and/or scrambled
Replying to @nabijaczleweli
praise fucking be firefox developers for making it tolerant of just yeeting 99% of the sqlite database
Replying to @nabijaczleweli
anyway, and yes this is advertising but I don't care because its saved my ass (well, life in this case) twice in as many months, use tackup, kids
i pressed C-A-D -> Switch User literal fucking minutes ago. please.
scouring old manuals again, and it's very cute how up to V6(!) pages were officially numbered restor(VIII)
ex/cuse/ me?
Replying to @nabijaczleweli
TYPE is a string on one or more two-digit SPCS type numbers (e.g. "01" for No. 1 ESS; "01 02" or "0102" (the space is optional) for No. 1 ESS and No. 2 ESS.
Replying to @nabijaczleweli
(sic! tremendous UNIX typists strike again)
Replying to @nabijaczleweli
SCCS September 16, 1975 (!!)
Replying to @nabijaczleweli
the oldest one in this set is, of course, BJ(1L) at March 1972
Replying to @nabijaczleweli
fascinating how "file descriptor 1/2", repeatedly, instead of some variation on the standard output stream, was a Normal thing to write at some point in history
Replying to @nabijaczleweli
a truly scathing review of IBM's cheap mainframe programming language from the late fifties
Replying to @nabijaczleweli
not oft do you see an official signed AT&T Bell Telephone Laboratories memo stock
Replying to @nabijaczleweli
Unfortunately, VAX 11/780 based UNIX systems seem to be naturally immune to all viruses that infect can produces. It seems that such systems are self-VAXcinated
BUGS (pardon the pun)
NOTE:
This page was copied from PWB/UNIX release 2.0 (1H) and brought to you for your amusement
haveing a terrible urge to acquiesce a small-format "¹ UNIX® is a registered trademark of AT&T" sticker
Replying to @nabijaczleweli
Replying to @nabijaczleweli
Replying to @nabijaczleweli
hm.
Replying to @nabijaczleweli
how does font licensing work. do I technically need a blessing from Sun Microsystems and/or Commodore International (or, indeed, Commodore-Amiga, Inc.) for this or do the almost 30 years and the fact that none of them exist anymore pre-emptively exonerate me
thank you groff, very cool
Replying to @mycoliza
oh you'd /love/ abigail output
Replying to @mycoliza
(cf. https://github.com/openzfs/zfs/blob/zfs-2.0.3/lib/libzfs/libzfs.abi, which is, yes, user and glibc code in XML with hard widths (and paths!), everything is type-id-num for thousands of lines, and it doesn't fold redundant consts together, so you can only generate these on gcc, and it's not compatible across versions)
Replying to @nabijaczleweli
(this appears to be the peak of (semi)automatic ABI versioning)
met uhh bright splotchy today
Replying to @nabijaczleweli
day well spent
so you're telling me this guy pre-dates pursuits?
Replying to @the6p4c
this but its tweets from people who are more online than me