siebenmann

4 ms·

31.
by siebenmann 7y ago
Putting safe in quotes is accurate, because our updates are not limited to truly safe packages at all for the simple reason that the Debian package format makes all package updates potentially dangerous. Any package update can decide to ask
32.
by siebenmann 7y ago
An OS thread M can run on any available P. While there are some caches associated with each P, Ps are fundamentally there to insure that only so many CPUs worth of Go user code is ever running at once, so the important thing is that an M th
33.
by siebenmann 7y ago
This should work fine. The goroutine making the system call that touches the NFS mount will consume an OS thread (an 'M' in Go terminology), but it will release its hold on other resources. Go uses as many OS threads as necessary
34.
by siebenmann 8y ago
Belatedly: that was a very interesting read on the history of this in both Linux and Unix more generally. Thank you for the link.
35.
by siebenmann 9y ago
This is great work in general and excellent historical research. As an additional historical note: in Unix, load averages were introduced in 3BSD, and at that time they included processes in disk IO wait and other theoretically short-term w
36.
by siebenmann 10y ago
If people are interested, the specifics of our current OmniOS environment are here: https://utcc.utoronto.ca/~cks/space/blog/solaris/ZFSFileserv... We have been broadly happy with it and it has been quit
37.
by siebenmann 11y ago
The general SELinux issue is a complex subject. My short form take is that regardless of its potential in theory if implemented nicely, in practice SELinux as deployed has consistently prioritized mathematical perfection (and yelling at peo
38.
by siebenmann 11y ago
I believe that what Matthew Garrett is talking about is mostly different from SELinux and AppArmor and so on. Those are all kernel features to harden user-level software in the face of vulnerabilities. Garrett is (mostly?) talking about int
39.
by siebenmann 11y ago
Our viewpoint is ultimately pragmatic: at the moment, both SELinux and AppArmor appear to be too much work for the potential benefit they offer in our environment. We could spend a great deal of time configuring both of them in order to mak
40.
by siebenmann 11y ago
I suspect that the answer is 'badly'. V7's chroot() seems to be more than a little bit of a fast hack, one that was good enough for some things but not at all comprehensive or problem free. (There are PDP-11 emulators and V7
41.
by siebenmann 12y ago
Almost any time PID 1 segfaults, it's PID 1's fault. With PID 1 being systemd, that makes it systemd's fault here. Based on gdb stack backtraces in the Fedora bug report and looking at the systemd code, it seems like some sor
42.
The Unix (Source Code) Tree at The Unix Heritage Society(minnie.tuhs.org)
2 points by siebenmann 15y ago|0 comments
43.
by siebenmann 15y ago
I've written server-side software that generated a meaningful Last-Modified header (it's very useful information) and also did an exact comparison instead of a time-based one. I did the exact comparison because I realized that it was very h