Live data from Hacker News

Viewing profile — davidstrauss

davidstrauss

HN member
Joined
Tue, Jun 18, 2013, 4:33 PM UTC
HN karma
66
Public activity
31 items

About davidstrauss

Chief Product Officer at Amutable. Former co-founder of Pantheon.

Recent public activity

  1. comment
    Comment #46785809

    Hi, I'm David, founding product lead. Our entire team will be at FOSDEM, and we'd be thrilled to meet more of the Mullvad team. Protecting systems like yours is core to us. We want…

  2. comment
    Comment #10496771

    > because upstart could grok the scripts without change I don't believe that's the case. The "service" command (which is part of the sysvinit-utils package, not Upstart) invokes ei…

  3. comment
    Comment #10496726

    The closest I could find in the docs to what digi_owl said is the following: > Internally, these functions send a single datagram with the state string as payload to the AF_UNIX so…

  4. comment
    Comment #10495524

    > it's not exactly a good choice for embedded systems. I don't develop embedded systems, but systemd is actually popular in that space because of its watchdog capabilities and its …

  5. comment
    Comment #10495497

    Directly talking to the notify socket is not considered using systemd internals. It is documented as a stable, public interface: https://wiki.freedesktop.org/www/Software/systemd/I…

  6. comment
    Comment #9998147

    The entire BSD kernel and init system are all in one repository. Are those developers "bringing on" confusion by doing that?

  7. comment
    Comment #9984131

    > The fact that Lennart was giving out presentations about nspawn specifically makes me believe it's very much intended to be used in production, as a "chroot on steroids". This is…

  8. comment
    Comment #9983690

    I don't think Red Hat was the driving force behind systemd's container and VM integration. systemd-nspawn was created to provide rapid testing of systemd, and it was (and, for now,…

  9. comment
  10. comment
    Comment #9983272

    > Might wish to check your history a bit. No matter how many complaints you may find about SysV boot time -- or even discussion about how to improve it -- it does not make systemd'…

  11. comment
    Comment #9983220

    > Why assume the user is too stupid or lazy to manually invoke vim and then systemctl daemon-reload? This is what it does: (1) Locates the current unit file, regardless of whether …

  12. comment
    Comment #9983181

    If that were the case, wouldn't the author support the kdbus work? It seems like they're not a fan of that, either, given the (misleading) complaints about systemd's support for kd…

  13. comment
    Comment #9982983

    > Honest question: Why does an init system need to know anything about screen brightness in the first place? Shouldn't X11 handle screen brightness? I think that's a reasonable que…

  14. comment
    Comment #9982903

    As a systemd committer, I certainly can. I don't have time for all of them, so I'll pull the first couple and a few other egregious ones. > Systemd was introduced to decrease the b…

  15. story
  16. comment
    Comment #5904376

    Especially once you start using hardware RAID controllers, the physical overhead of running I/O commands is pretty abstracted away from the kernel.

  17. comment
    Comment #5904361

    > However, using xen or kvm solves that problem, by giving each guest their own ram that nobody else can fuck with. It gets hard to say whether a shared page cache is a good thing …

  18. comment
    Comment #5903553

    Just a note as the author of the Linux Journal article, I absolutely would have mentioned Docker if I had written the article now. Unfortunately, the article only recently made it …

  19. comment
    Comment #5903453

    I just timed a spin-up of a 16GB Fedora 18 instance on in the current-generation Rackspace Cloud's DFW data center. It took 7 minutes and 10 seconds to complete. Launching a somewh…

  20. comment
    Comment #5903308

    > I am intimately familiar with eWLM and I think it's quite unfair to call it containers. I feel like you're strawmanning me, here. I specifically avoided calling WLM "containers."…

  21. comment
    Comment #5902739

    Yes: "All the buffered writes are still system wide and not per group. Hence we will not see service differentiation between buffered writes between groups." [1] [1] https://www.ke…

  22. comment
    Comment #5902471

    RCTL can enforce specific limits, which is good if you either want to divide resources such that there can't be (or is unlikely to be) contention. cgroups offers hard limits for so…

  23. comment
    Comment #5902316

    > Citation needed. First, I define containers by their capabilities, not a vendor or kernel calling them "containers." The Linux kernel, internally, has no concept of containers; i…

  24. comment
    Comment #5900819

    I'm the author of the article. It doesn't mention Windows Azure because I wrote it for the Linux Journal, and a full discussion of containerization outside of Linux wasn't possible…

  25. comment