catern

88 ms·

361.
by catern 9y ago
No, https://en.wikipedia.org/wiki/Active_networking
362.
by catern 9y ago
Aw... I thought this was a post explaining active networking using capsules.
363.
by catern 9y ago
Using network namespaces does require root. User namespaces can give you something close enough to root to use network namespaces. But that only helps you if user namespaces are usable unprivileged, which they usually aren't, due to di
364.
by catern 9y ago
If you can use it, https://github.com/lethalman/nix-user-chroot is the best way. But, it depends on user namespaces being enabled on your system. That may not be the case.
365.
by catern 9y ago
I don't see anything to suggest that nsjail has the main feature of bubblewrap: It is safe to make bubblewrap setuid-root, and therefore bubblewrap is a safe way for unprivileged users to use containers. (arguably the only safe way at
366.
by catern 9y ago
Helm/unite/denite are not the same thing as what I am talking about.
367.
by catern 9y ago
Emacs Lisp is not a declarative language, of course, but this kind of declarative logic - regular expressions which parse shell command output and apply hidden text properties or keybindings - is common in Emacs. dired does it, as does magi
368.
by catern 9y ago
Interesting framework. I like the fairly declarative style. The approach to writing terminal applications which interact with shell utilities seems a lot like certain Emacs applications, such as dired.
369.
by catern 9y ago
>Most people already work (95%+) and those that don't - children, elderly, sick, disabled - those people aren't ever joining your work programs. They make up a huge percentage of the total population and you just.. ignore them
370.
by catern 9y ago
It's quite an indictment of the current state of our tooling (not just tmux) that such an application as this is necessary. Why isn't it easy to configure this in tmux itself, and persist the resulting configuration?
371.
by catern 9y ago
You don't find it a bit odd that a project built using distribution packages, with distribution package managers, with (eventually) a choice between which of several distributions to use, is called "Distroless"? It's als
372.
by catern 9y ago
It's not just "an easy way to get built packages". It makes this project trivially easy. No need for Bazel, you can do what this project does with a small shell script. I'm a bit disappointed to see Google releasing a pr
373.
by catern 9y ago
This project is still reliant on Debian to build all the packages. This project merely selects a set of packages that Debian has built.
374.
Argdata: a binary serialisation format(nuxi.nl)
2 points by catern 9y ago|0 comments
375.
by catern 9y ago
TRAMP reuses ssh connections. It's straightforward to configure OpenSSH to reuse its connection, see e.g. https://en.wikibooks.org/wiki/OpenSSH/Cookbook/Multiplexing and that is what TRAMP does. >Can
376.
by catern 9y ago
>A saner approach would be based on a local editor editing remote files. Yes, this is the basis of the very popular and widely used TRAMP component in Emacs. >Imagine if you could type ‘edit foo.conf’ on the server and have it pop ope
377.
by catern 9y ago
See also http://catern.com/posts/pipes.html
378.
by catern 9y ago
>Given reality, something must substitute for open source drivers Linux is quite real, I assure you.
379.
by catern 9y ago
Nix package definitions sit in a Git (or other VCS) repo, which you can access-control through your usual means. The binary artifacts are behind an HTTP server, which you can access control through whatever normal access control mechanisms,
380.
Continuous integration for iOS with Nix and Buildkite(medium.com)
3 points by catern 9y ago|0 comments
381.
by catern 9y ago
How exactly are you going to sandbox your drivers? Run them in user-mode, perhaps? But then you've constructed a microkernel, and no-one uses your system because it's slow. Anyway, what I said is that sandboxing isn't a subst
382.
by catern 9y ago
True but irrelevant. The key new "feature" of Fuschia is that its stable ABI makes closed-source drivers easier to write in the short term, relative to Linux. As a result, the vast majority of Fuschia drivers will be closed-source
383.
by catern 9y ago
Sandboxing isn't a substitute for having your drivers be open source. Even if all drivers were written in safe languages, you'd still have CVEs and still want to fix those CVEs.
384.
by catern 9y ago
>Fuchsia is not going to be burdened by Linux kernel dev policies of constantly breaking APIs and their requirement for driver developers to open source their stuff, obey the kernel coding preferences (like when they rejected AMD's
385.
by catern 9y ago
Nix doesn't guarantee bit-for-bit reproducibility: That is, two different builds of a Nix package may not produce bit-identical output. (They probably will, because of all the sandboxing, but nothing prevents an arbitrary package from
386.
by catern 9y ago
Setting up your own binary cache is straightforward: https://nixos.org/nix/manual/#sec-sharing-packages Is using Artifactory or Nexus a requirement? Why?
387.
by catern 9y ago
There's also nothing wrong with wanting tools to reuse existing platforms rather than reinvent the wheel. minimega looks neat, but I don't want to sacrifice all the other libvirt-based tooling that's out there. If minimega&#x
388.
by catern 9y ago
But according to a sibling comment, you support containers too (like libvirt)... you must already have an abstraction layer between you and QEMU. libvirt exposes pretty much every QEMU feature in existence, anyway, and allows passing throug
389.
by catern 9y ago
Does this use libvirt? It doesn't look like it. Why not? libvirt already provides almost all the functionality you need, you just need to layer a distribution mechanism for configuration across multiple hosts on top.
390.
by catern 9y ago
That's an interesting idea. If I understand correctly, you're suggesting that services simply broadcast the data mutations they are going to perform. Then, any other services that wish to use that data can filter those broadcasted

More ›