Searching txt.sour.is

Twts matching #retrospective
Sort by: Newest, Oldest, Most Relevant
movq
www.uninformativ.de
 (4w ago)
↳ In-reply-to » Made a little program to print the system’s uptime on DOS, OS/2, and Windows NT:

@lyse@lyse.isobeef.org

Crazy, who comes up with things like that?

I didn’t come up with it, but I was close, I guess. DOS is so small, you don’t have much of a choice but to search for “anything related to time”. There aren’t that many syscalls/functions. You’ll quickly notice that there’s no global tick counter. So what else is there? Hmm, “get the mtime of a file” is pretty much the only other time-related thing. And which file is “stable”, probably allocated just once at boot? Mark Aitchison tried to use NUL, which is a pretty good idea. Thinking about it in retrospect, stdin does indeed make more sense, though, because that object really does get allocated just once at “boot” and then it stays the same. That’s not guaranteed for NUL (although just as likely).

But, it is possible in DOS to move “the console” to a serial port:

Image

I wonder what that does to my little uptime program. :-)

Today, I also learned that -R is an alias for -r in rm.

Ah, I remember that. Dug it up and saved it in the blog: -R is more portable/consistent: http://movq.de/blog/postings/2026-09-30/0/POSTING-en.html

⤋ Read More
lwn-net
feeds.twtxt.net
 (1y ago)

[$] LWN.net Weekly Edition for May 1, 2025
Inside this week’s LWN.net Weekly Edition:

  • Front: Mailman 2 vulnerabilities; AI in Debian; __nonstring__; Cache-aware scheduling; Freezing filesystems; Socket-level storage; Debugging information; LWN in 2025.

  • Briefs: Debian election; Kali Linux key; OpenBSD 7.7; Firefox 138.0; GCC 15.1; Meson 1.8.0; Valgrind 3.25.0; FSF review; OSI retrospective; Mastodon; Quotes; …

  • [Announcements](https://lwn.net/Arti … ⌘ Read more

⤋ Read More
lwn-net
feeds.twtxt.net
 (1y ago)

OSI publishes election retrospective
The Open Source Initiative (OSI) has quietly published
“takeaways” from its internal retrospective on the recent board
of directors election as an update
to the March blog\
post that announced the new members of the board. The election was
controversial, in part, due to poor communication and OSI changing the
election rules and disqualifying sever … ⌘ Read more

⤋ Read More
niplav
niplav.site
 (4y ago)

in retrospect, i do remember expecting some message about “yes, you passed the test, you were actually living in a lie”, but i think that died when nobody gave me a bad grade for taking too long to become vegetarian. maybe veganism…

⤋ Read More
quark
ferengi.one
 (5y ago)
↳ In-reply-to » @movq would it be possible to trim the subject to, say, 100 or 140 characters? Just the subject.

@movq@www.uninformativ.de

If Subject contains the full twt, then you can skim over conversations just by reading those lines in mutt’s index pager

Yes, I do the same, true.

So I decided: Okay, let’s have mutt do it.

And Mutt does it well. I agree it was/is a good idea.

The subject lines are already “compressed”

I noticed, yes.

I am not sure why I asked to begin with; in retrospect, in was a silly request. Perhaps the OCD in me got triggered while viewing rich headers, on a specific twt, when I saw the huge subject line that is, otherwise, always hidden.

Anyway, don’t mind me, move along. 😂

⤋ Read More