Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
catern
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
45 ms
·
421.
▲
by
catern
10y ago
And as an even deeper correspondence: Once your language is memory-safe and capability-secure, you don't even need a kernel, let alone a microkernel. Rather than use hardware address spaces to separate and modularize components (the pr
422.
▲
by
catern
10y ago
>Not necessarily. If your system supports first-class namespaces, then you can just build a namespace consisting of only the objects to which a program should have access. No need for any further access control. Unfortunately this is usu
423.
▲
by
catern
10y ago
Yes, there's a class on the same subject at CMU with the same policy. Here's the document they handed out to explain the policy: http://cmu.io/~sbaugh/midterm_grading_function.pdf
424.
▲
by
catern
10y ago
>#2 saves a little but not much and precludes unsafe low-level code completely. Sure, in the same way most people today don't run their entire application in ring 0, but instead run on top of a kernel. Privilege levels like that are
425.
▲
by
catern
10y ago
1. Eliminate cache coherency protocols (replacing it with cache manipulation/inter-CPU communication instructions) 2. Eliminate virtual memory (replacing it with nothing) I'm not a CPU designer, but my understanding is that removi
426.
▲
by
catern
10y ago
Linux will (thankfully) never do that because that would be an example of compromising technical quality for political reasons (mediating the problem that hardware makers are not publishing source).
427.
▲
by
catern
10y ago
This is similar to restclient.el for Emacs. https://github.com/pashky/restclient.el wuzz seems to be focused on one request at a time, though.
428.
▲
by
catern
10y ago
It would be quite amusing if it couldn't work with AD, considering Zulip is based on Zephyr which is a very old chat protocol/application heavily dependent on Kerberos.
429.
▲
by
catern
10y ago
Yes, that's a fascinating new technique, known as "CGI scripting".
430.
▲
by
catern
10y ago
Definitely, that is one possible design. Although that would be fairly tricky to implement in the kernel. One way you could do this is to heavily abuse the CRIU project. https://criu.org/Main_Page Just do the following: 1.
431.
▲
by
catern
10y ago
I don't have the inclination to write a long comment about this. But reading sections like this: >This state can then be verified whenever a process performs an action requiring a permissions check. For example, when a process reque
432.
▲
by
catern
10y ago
>most of the other use cases (mount, pt-chown, dbus-daemon-launch-helper, etc.) Those listed examples could also be could be achieved with IPC to a privileged daemon. But unfortunately not all setuid executables can be replaced that way.
433.
▲
by
catern
10y ago
Clearly this has now devolved into mere semantics, but... if your position emphasizes user freedom, then your position is the "free software" position, not the "open source" position, just as a matter of the historical d
434.
▲
by
catern
10y ago
I did not realize that. Given that, I was incorrect when I said that the author (or anyone) could easily use seccomp MODE_STRICT. Capsicum may still be easy to use. And seccomp-bpf is not that complex either.
435.
▲
by
catern
10y ago
Well... there is at least some sense in writing a webapp in C. If you rely on operating system primitives for security (processes, Unix filesystem permissions, seccomp/pledge/capsicum) instead of language features (bounds checking
436.
▲
by
catern
10y ago
Since the author is using cgi: >However, this is definitely something in the crosshairs of ksql(3): forking a process, like kcgi(3) does, that handles the database I/O and communicates with the master over pipes. If they do this, th
437.
▲
by
catern
10y ago
That's incorrect. That's what happens when the info documentation for info has not been installed by your distribution. Normally you get https://www.gnu.org/software/texinfo/manual/info-stnd/inf
438.
▲
by
catern
10y ago
Ah. Just open the libc manual with "info libc", then "i" to look something up in the index, and type "struct timespec". (You can even tab-complete the name of the struct). >And it doesn't help that the
439.
▲
by
catern
10y ago
You should be able to just (setq scroll-conservatively 1000). As you no doubt have guessed, the page-by-page scrolling default in Emacs is to reduce the amount of redrawing necessary.
440.
▲
by
catern
10y ago
>solving the real problems of man pages (which I'd say there are two: lack of hyperlinks and poor searchability texinfo (info) has hyperlinks, and I can search through multiple manuals if that's what you mean by searchability.
441.
▲
by
catern
10y ago
Maybe I don't understand. Is this a joke? Is it not already perfectly possible to edit a song and make it fit your playlist? And how would streaming the audio from a binary be a disincentive for piracy, except inasmuch as on-demand str
442.
▲
by
catern
10y ago
>As always, it's worth pointing out that this is just about the Linux kernel. Different scale, different developer community, different code structure, different testing/CI methodology (i.e. practically none) than just about ev
443.
▲
by
catern
10y ago
I did the same. These advancements in vim are too little, too late for me.
444.
▲
by
catern
10y ago
It looks like LibreOffice Calc does actually support R1C1 notation. There is also the spreadsheet support in Emacs org-mode.
445.
▲
by
catern
10y ago
What if your root password is different from your regular password? For example - if you have a Kerberos root principal? That seems even better.
446.
▲
by
catern
10y ago
I don't believe what you're describing works. You're suggesting reading first the size of a record (stored itself in a fixed-size field), then reading the rest of it? But unfortunately that is not atomic. Another process coul
447.
▲
by
catern
10y ago
Atomic writes are pretty easy - as this article points out, PIPE_BUF sized writes to pipes are atomic. It seems like atomic reads are harder. You want to read a record from a shared input, but you don't know how big a record might be.
448.
▲
by
catern
10y ago
To avoid being exploited and burning out, use the GPL for your projects.
449.
▲
by
catern
10y ago
>Can we at least work on documenting contributor workflow? It is documented. Look at the file "CONTRIBUTE" in the root of the Emacs source. That file is also cited in the manual: https://www.gnu.org/software&#
450.
▲
by
catern
10y ago
>While Emacs indeed does have new leadership under John Wiegley, as a whole, the project cannot change without the blessing of the GNU elders. This isn't true. It's just that the GNU elders are elders for a reason - their opini
More ›