EdSchouten

11 ms·

91.
by EdSchouten 3y ago
How is this different from reductio ad absurdum?
92.
by EdSchouten 3y ago
First we run everything as processes on top of an OS kernel. On UNIX, we have all of these high-level concepts of letting processes interact with each other. Files, pipes, streaming/datagram UNIX sockets, etc. Later on certain people s
93.
by EdSchouten 3y ago
This blog post could really use links to other sources. First of all, I had no idea what an E-graph was, so I had to search for that myself. Then the post presents the problem itself, without explaining a practical situation in which you’d
94.
by EdSchouten 3y ago
I know WinFsp has been around for quite some time, but I wonder how it compares against Microsoft's own ProjFS: https://learn.microsoft.com/en-us/windows/win32/projfs/proje...
95.
by EdSchouten 3y ago
What’s worth mentioning is that IPFS is built on top of a data model named IPLD. https://ipld.io/ If you are planning on doing your own experiments with Merkle tree and such, I can strongly recommend using IPLD as well. The
96.
by EdSchouten 3y ago
As far as I know, Go uses year 1 instead of 1970 as its epoch.
97.
by EdSchouten 3y ago
Interesting! TIL there is a Windows desktop application called "Reddit for Blind" that can be used to access Reddit with a screen reader: https://www.redditforblind.org My instinctive reaction was: "No screenshots
98.
by EdSchouten 3y ago
A couple of days ago I stumbled upon Prolly trees: https://docs.dolthub.com/architecture/storage-engine/prolly-... In a nutshell: B+ trees that are stable w.r.t. insertion order. Great if you want to test them for
99.
by EdSchouten 3y ago
Quite amazing how so many environments of floating point values make the mistake of treating them as equal. YAML 1.2 does the same thing: https://yaml.org/spec/1.2.2/#10214-floating-point
100.
by EdSchouten 3y ago
Which is funny, because coleslaw itself is borrowed from Dutch (koolsla).
101.
by EdSchouten 4y ago
Somewhat desirable, as it means you can get the reciprocal of any number without a loss of precision, right?
102.
by EdSchouten 4y ago
I see this was eventually fixed by manually declaring a structure that matches struct ifreq. Instead of doing that, I would recommend submitting a patch against golang.org/x/sys to get that autogenerated. The Go folks tend to merg
103.
by EdSchouten 4y ago
I think the reason for that is that Protobuf doesn’t provide streaming parsers (yet). As the Protobuf based protocol stored all samples in a single message, this meant that both the client and server had to allocate lots of memory when send
104.
by EdSchouten 4y ago
Also the fact that their package manager is strongly coupled against https://package.elm-lang.org/ . There is no way to override it. This means that if that package site ever goes down, you will be left with an unbuildable p
105.
by EdSchouten 4y ago
It returns a boolean.
106.
by EdSchouten 4y ago
That’s not true. Just create a 32 or 64 bit futex, and use that to let threads write their thread ID into it. https://www.kernel.org/doc/Documentation/pi-futex.txt
107.
by EdSchouten 4y ago
https://archive.ph/fuZ44
108.
by EdSchouten 4y ago
If instead of 'int' you were to use 'size_t' (or the equivalent of that provided by your programming language of choice), then there should be no issues in practice. Then you would only see overflows if your elements wer
109.
by EdSchouten 4y ago
I'm not saying that this isn't a great way for people to familiarize themselves with basic Unix shell commands. That said, why would you want to teach this to kids ?
110.
by EdSchouten 4y ago
> If my WiFi driver crashes, there's nothing helpful or safer about immediately bringing down the whole system when it's possible to keep running with everything but networking still functioning. There have been various example
111.
by EdSchouten 4y ago
One does not rule out the other. You could simply write crash info to some NVRAM or something, and then do a reboot. Then you can recover it during the next boot. But there is no need to let userspace processes continue to run, which is exa
112.
by EdSchouten 4y ago
The policy of ‘oopsing’ and limping on is, in my opinion, literally one of Linux’s worst features. It has bitten me in various cases: - Remember when Linux had that caused the kernel to partially crash and eat 100% CPU due to some bug in th
113.
by EdSchouten 4y ago
Regardless of whether you should use Bazel or not, my hope is that any future build systems attempt to adopt Bazel's remote execution protocol (or at least a protocol that is similar in spirit): https://github.com/bazel
114.
by EdSchouten 4y ago
Though it obviously depends on the case at hand, I sort of agree with this. For a distributed build cluster that I maintain (Buildbarn, https://github.com/buildbarn/bb-remote-execution/ ), I also had to implement a
115.
by EdSchouten 4y ago
For Buildbarn I need to provide a writable file system that acts in a POSIX compliant way. I'm not convinced WebDAV could provide that.
116.
by EdSchouten 4y ago
Sure, LOOKUP would obviously fail, as the object is no longer present in the file system under any name. GETATTR is a different story. Consider this sequence of operations: $ mkdir foo $ cd foo $ rmdir ../foo $ stat .
117.
by EdSchouten 4y ago
> I don't understand the comment about leaking memory, nfs file handles don't have to be persistent. As long as the file the NFSv4 file handle refers to is still usable (i.e., linked into the file system), the NFSv4 file handle
118.
by EdSchouten 4y ago
With it being stateless, I was referring to just the part where I wanted to point out the difference: file handles are stateless, while FUSE's equivalent (nodeids) are stateful. Regardless of whether it's an in-memory or persisten
119.
by EdSchouten 4y ago
Replying to my own comment: I do wonder how this library deals with some of the fundamental differences beween FUSE and NFSv4. For example, with FUSE the kernel and server share intimate knowledge on which part of the file system lives in t
120.
by EdSchouten 4y ago
What a coincidence! For a project that I maintain (Buildbarn, a distributed build cluster for Bazel) I recently generalized all of the FUSE code I had into a generic VFS that can both be exposed over FUSE and NFSv4. The intent was the same:

More ›