User Details
- User Since
- May 17 2014, 3:06 AM (606 w, 5 d)
Yesterday
I've verified that graphics/drm-66-kmod builds cleanly with these changes.
The summary is incorrect. Early operating systems including DEC's TOPS-10 and VMS used CR LF because that was what teletypes expected. CP/M was heavily inspired by TOPS-10 and continued to use CR LF despite rarely if ever being used with teletypes. DOS inherited CR LF from CP/M, and Windows inherited it from DOS; Windows NT and OS/2 borrowed heavily from VMS which also used CR LF, in addition to needing to remain compatible with DOS and pre-NT Windows. Apple historically used CR but switched to LF with Mac OS X (later renamed to macOS). Unix and its descendants (such as Plan 9) have always used LF despite originally being written for teletypes, relying instead on the device driver to inject a CR if needed.
What's the point of copying the NetBSD tests if we end up having to change everything about them, and then end up adding our own test script anyway as you do in D54265?
Mon, Dec 29
I did indeed write sockstat(8) but I did not write (most of) formataddr(), and I certainly would not have approved it if asked to review it.
Wed, Dec 24
Tue, Dec 23
Mon, Dec 22
Sun, Dec 21
Fri, Dec 19
Wed, Dec 17
Note: I separated out the whitespace and comment fixes before pushing.
sort optstr
getopt
parse
Can I please get a decision on this?
Tue, Dec 16
Mon, Dec 15
update builtins(1)
readlink directly from lower vnode
comment the tests
Sun, Dec 14
drop -devel
We can't move the MAC initialization, it has to happen before we call priv_check_cred().
plug knlist leak
Should we also move mac_proc_init() and knlist_alloc() into proc_init()?
@kib can you also please take a look at the PR? the originator claims this used to work as recently as 14.2 but I see no evidence that it has ever worked, the code to zero out the fsid has been there since 1997.