Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
JdeBP
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
121.
▲
by
JdeBP
4mo ago
If you look closely, you'll see that some faint dots are already outlining an order 7 triangular tiling.
122.
▲
by
JdeBP
4mo ago
You're not getting the full experience of analogue telly artifacts until you emulate colour subcarrier phase shift and colour burst detection failure. (-: And of course PAL and Hanover bars.
123.
▲
by
JdeBP
4mo ago
That's actually less accurate, not more. It's a post-hoc revision that conflates Unix with Linux. The Unix model was invented over a decade before the idea of multithreading percolated into mainstream operating systems at all. Th
124.
▲
posix_spawn syscall added (2012)
(blog.netbsd.org)
1 points
by
JdeBP
4mo ago
|
0 comments
125.
▲
by
JdeBP
4mo ago
Not really. They didn't get anywhere near as far as noticing the prior art of NetBSD, not even on the mailing list discussion behind that article.
126.
▲
by
JdeBP
4mo ago
You haven't read the doco. I did point to some. The image file is supplied (or not) via the section object. Think it through. Windows NT supported fork from the start in its POSIX subsystem, that subsystem was layered on top of the
127.
▲
by
JdeBP
4mo ago
This is an oft-overlooked point. An obvious place to look for improving fork+execve is to see whether posix_spawn can be given more efficient kernel mechanisms to be based upon. And of course that has already been done. On NetBSD, posix_s
128.
▲
by
JdeBP
4mo ago
These discussions were definitely had back in the 20th century too. The spawn model versus the fork+execve model has been an on-going debate since the time of MS/PC/DR-DOS.
129.
▲
by
JdeBP
4mo ago
As mentioned elsewhere on this page, Windows NT had fork from the start. Vide NtCreateProcess and what happens if an image file is not explicitly supplied. * https://computernewb.com/~lily/files/Documents/NTD
130.
▲
by
JdeBP
4mo ago
Actually, there is a native fork. There had to be, as POSIX personality support was a part of the Windows NT 3.1 design. What there wasn't was a Win32 form of fork. The Native API for Windows NT allowed it quite straightforwar
131.
▲
by
JdeBP
4mo ago
Heh! The Unix didn't embrace the idea of file descriptor 3 meaning something specific. (-: * https://jdebp.uk/FGA/bernstein-on-ttys/cttys.html Interestingly, on MS/PC/DR-DOS file descriptor 3 was
132.
▲
by
JdeBP
4mo ago
You may be mixing up fork and exec. Library data state isn't retained over execve(), and O_CLOEXEC does not take effect at fork().
133.
▲
by
JdeBP
4mo ago
Windows NT was never designed with pre-386 machines in mind. That was the territory of the old DOS+Windows. Windows NT from the get-go was for machines with page-based virtual memory. * https://computernewb.com/~lily/
134.
▲
by
JdeBP
4mo ago
Sort of. It's also footway when denoting the no-carriages part of a road that also has a carriageway. There's a whole complex terminology of footway , cycleway , bridleway , bridle path , footpath , cycle path , and carr
135.
▲
by
JdeBP
4mo ago
Not having a written constitution is not the same as not having rights in everyday practice.
136.
▲
by
JdeBP
4mo ago
That response looks like it is generated from boilerplate, so the 'reported to the authorities' part is as likely true as when sudo says the same thing. * https://postimg.cc/3kVXKzhk
137.
▲
by
JdeBP
4mo ago
Interesting. My first thought is wondering whether the keyboard HID is adding report IDs to its input reports, because it isn't in boot mode or something. That would have that effect.
138.
▲
by
JdeBP
4mo ago
I'm not from GL. I write my own USB HID handlers and I'm being nosy about bad protocol that exists in the wild. Was the 0 byte in some input report? In a descriptor? Somewhere else?
139.
▲
by
JdeBP
4mo ago
This really isn't factually based. MFT entries are conceptually equivalent to i-node table entries. And the execute bit is what traversal checking bypass is all about.
140.
▲
by
JdeBP
4mo ago
I think that 7 decades's worth of telly and movie set designers will take issue with the claimed uselessness of blinkenlichten. Blinkenlichten make money. (-:
141.
▲
by
JdeBP
4mo ago
One does not even need to squint. The first page of RFC 882 explains outright that the DNS came about in the first place because the mechanisms for updating a HOSTS.TXT file and publishing it to loads of places did not scale. That's s
142.
▲
by
JdeBP
4mo ago
Yes, and under the covers some parts of Windows NT, notably server processes, do something akin to this; although its interactive login on a windowstation system follows the Unix model of the TCB doing the login dialogue and then spawning a
143.
▲
by
JdeBP
4mo ago
That sort of idea, yes. I've just done some research and it looks like the Debin Hurd people did attempt to actually implement this. I just never heard about it. There was a 'login shell' and a 'nouser'. The la
144.
▲
by
JdeBP
4mo ago
No. The multiplexers are all turned off, and I have devd/udev rules that spawn my own userspace driver processes (as services, via service management) to attach to the individual USB devices. The driver services in turn use an autoco
145.
▲
by
JdeBP
4mo ago
We should start telling them again, then. (-: In the current versions of FreeBSD, NetBSD, DragonFlyBSD, Illumos, and Debian, it is still /usr/share/dict . * https://cgit.freebsd.org/src/tree/share&#
146.
▲
by
JdeBP
4mo ago
Not enough reading of Hacker News, young grasshopper! (-: Used several times within the last month alone. * https://news.ycombinator.com/item?id=48375691
147.
▲
by
JdeBP
4mo ago
I don't know. This was a very early description of how it would work that I read, a long time ago. Thinking it through as a thought experiment, the way that I'd do it, a process with no credentials would not be able to open anyth
148.
▲
by
JdeBP
4mo ago
One interesting idea, never realized that I know of, was for Hurd. The idea was that 'login' would be a simple utility program. One started a session with no user credentials, and ran 'login' as a command to add creden
149.
▲
by
JdeBP
4mo ago
There is only one 'blue', colour number 4, in ECMA-45.
150.
▲
by
JdeBP
4mo ago
It's the decades-old problem of blue on black, which has led to interminable discussions of which exact tint of blue should be ECMA-45 blue on a terminal. Pick one, it has poor contrast with a black background. Pick another, it has p
More ›