beefhash

The tree only contains configure.in, not the generated configure output, and Makefile.am, not the generated Makefile.in. You do need the entire autotools suite installed for it to build.

Why they published it like this is beyond me, however. The whole point of autotools is not making your users install them (unlike CMake and virtually every other build system for C there is).

The installer also leaves a random.seed file so that there's a direct chain from the very first boot.

I think my favorite (in terms of humor) is a commit from mpv complaining about locales and encodings. You can practically feel the committer's sheer frustration.

[1] https://github.com/mpv-player/mpv/commit/1e70e82baa9193f6f02...

UNIX was written in assembly at first. By the Fourth Edition, the kernel was rewritten to be in a version of C (that won't go through a modern C compiler anymore), both 1973. The C compiler itself was introduced in the Third Edition. Parts of userland would still be in assembly even until the 7th Edition (1979), such as roff(1) (nroff/troff were in C), parts of as(1) or chess(6).

People are working on transcribing it: https://minnie.tuhs.org/pipermail/pdp7-unix/2019-October/000...

Incidentally, wkt confirmed that's one of the two artifacts[1] which he [teased a while ago[2].

[1] https://minnie.tuhs.org//pipermail/tuhs/2019-October/019106....

[2] https://minnie.tuhs.org//pipermail/tuhs/2019-September/01868...

> Nobody! There were no copyright notices, and this is a work made before the US adopted the BERN convention. Prior copyright law required copyright notices.

...in the U.S.

This does not apply to other countries, especially continental European ones. They'll happily retroactively apply copyright for software, even when it wasn't explicitly protected by means of their jurisdiction claiming that software has is categorized as a work even before the convention. No license, no luck over there.

cf. https://virtuallyfun.com/wordpress/2018/11/26/why-bsd-os-is-...

If it's not deemed a work for hire (and given UNIX was a rogue operation at the time, that's not entirely unreasonable to question), then the copyright probably remains with Thompson and Ritchie themselves, or rather Thompson and Ritchie's family (or whichever way the inheritance process went). If it is, then probably Micro Focus via Attachmate via Novell via USL. Special considerations may also apply because it wasn't "published" in any sense of the world until past Ritchie's death.

tbf, that IRC channel may not exactly be super canonical.

https://cvsweb.openbsd.org/cgi-bin/cvsweb/www/index.html?rev...

"remove freenode channel from index, it lacks any form of sensible moderation."

I still kind of wish SunOS (the BSD-based version, before AT&T made them switch over to System V) had made it out of Sun as an open source version.

Sources for 4.1.4 leaked, but of course that's without official blessing... And Oracle's lawyers probably make up more than half the company.

I'm not sure if this is only an about accessibility to non-tech people.

Think about it: You can't get files on your device in a useable format anymore. This means piracy becomes exponentially harder to consume (i.e. you can't use your iPad [easily] as a reader for your pirated ebooks). Quite honestly, that's a stroke of genius and likely a secondary motivation for this workflow.

Their TLS certificate expired over a year ago. This doesn't exactly seem to inspire my confidence in the project's ongoing development.

I, for one, rather enjoy the 2000s aesthetic. Different tastes for different folks.

I swear by OpenBSD. I use it on my home server. I use it to write C code (their C standard library has a few very nice things, such as arc4random, strl{cat,cpy}, explicit_bzero, timingsafe_memcmp, libtls, and other things that I run into often enough that I don't want to think about them before I start adding portability stuff).

Of course, it's not much of an option for anything I require proprietary software.

I suppose that's the curse of the success of Linux. Now that it's everywhere, it also has to answer to all kinds of usage scenarios.

There may be some systems where storing entropy in a file across reboots isn't an option, e.g. diskless situations or non-writable filesystems. Though those should be a rare case. Of course, this would actually require cooperation from userspace, and given Linux is just a kernel and userland kind of free to do what they want, it's not as easy as it sounds.

Incidentally, I really wish we could get the arc4random(3) family on GNU/Linux already. It's the only notable *NIX platform that still doesn't provide it; illumos has it, every BSD has it, macOS has it. Given the difficulties with entropy as noted above, however, the whole "non-failing cryptographically secure PRNG" model just won't work with Linux.

I suppose I'm not a reasonable person, then. I was under the impression FaceTime was a Facebook product, or at least bought from them.

Debian ships with it. That's why I "use" it.

(I don't send e-mail to the outside or listen for any outside e-mail, so the choice of MTA is irrelevant to me as long as the system can still send over localhost to /var/mail/$USER.)

Funny you'd wrote a wrapper like that, too. I ended up making something in C that uses readpassphrase(3) [with -lbsd on Linux, but I haven't built it on a Linux machine in years] and zeroes the memory with explicit_bzero(3) as it goes out.

The keys come from a dedicated password manager that only stores TOTP secrets and the password manager wipes the clipboard.

All this happens on a physically separate machine.

> Please be honest about why you are using social media for login.

Without speaking for Regex Crossword (I'm in no way affiliated with them):

I suspect the reason may at least in part be security. Passwords are dangerous to keep around, hard to handle, computationally expensive if done right, and if an attacker gets at the database, people get angry. A social network provider (especially the options here, Facebook, Google, Twitter, GitHub and Windows Live) is much more likely to get security (against third party attackers) a lot more right.

SunOS 4 was still BSD-based. You can find the source code for SunOS 4.1.4 on TUHS's code comparison site[1], but for some reason, you can't browse the tree.

Solaris was when Sun made the jump to System V. AFAIK part of that was because Sun had financial difficulties at the time and AT&T offered to help them -- in exchange for Sun to rebase on System V.

[1] e.g. https://minnie.tuhs.org/cgi-bin/utree.pl?file=SunOS-4.1.4/us...

> Iirc OpenBSD actively disabled it for you, making it the default.

They have, as of this commit[1] on 2018-06-19.

[1] https://marc.info/?l=openbsd-cvs&m=152943660103446&w=2

See also: GNU parallel showing a nag for being cited in papers.

https://git.savannah.gnu.org/cgit/parallel.git/tree/src/para...

> Then what's the next version of Perl 6 supposed to be

raku 2? Perl 5 gets the Perl name back and gets a version number leap to show it's not dead yet and raku is off doing its own thing with its own version numbers, probably hitting 1.0 barely before GNU Hurd.

That's not what grandparent claimed, though. "Intellectual property" is an umbrella term for copyright, trademarks, patents, design protection laws, etc. throwaway_law's retort seems justified to me.

Though the irony of charging money for type design that was thrown in the river to prevent a certain someone from doing so is not lost on me.

Font copyright is a weird thing[1]. In the U.S. at least, the letterforms themselves cannot be subject to copyright, but font files themselves as "software" may be. This may differ between jurisdictions (or even be entirely unclear and yet undecided by the courts in some places).

[1] See for a gentle overview in the U.S. e.g. https://practicaltypography.com/the-copyright-status-of-font...

Not that ripping it from there has become any more legal in the meantime.

Well, yes. Mature, boring technology. I meant it in the sense of this essay[1].

[1] https://mcfunley.com/choose-boring-technology

Rails just became boring technology. It works. The hype is gone, but it continues chugging along happily and is generally an understood problem.

> and some people are very good at digging up and pointing out precedent.

As one of the people who loves being that guy in another community: They're not only very good at digging up and pointing out precedents, they likely have systematic archives of everything that remotely relates to the decisions they wish to see made.

It seems worth noting that the "Syslog message format" was introduced in RFC 5424; the article cites RFC 3164 for message delivery (and should be citing RFC 5424 based on the format).

RFC 5424 defines a more formal and more complete version of the protocol. NetBSD understands and emits it, FreeBSD is still in the process of gaining support for it and OpenBSD seems to be perfectly content sticking to traditional BSD syslog as recorded in RFC 3164.