Live data from Hacker News

Viewing profile — dalias

dalias

HN member
Joined
Sat, Jun 02, 2012, 10:43 PM UTC
HN karma
162
Public activity
44 items

About dalias

No profile information was provided.

Recent public activity

  1. comment
    Comment #23086951

    5kloc is about 10x larger than musl's existing (old) malloc in source lines. I suspect lots of that is low code density, comments, etc. I have to lookup what exactly mimalloc is/do…

  2. comment
    Comment #23086770

    We'd be happy to address specific problems on the mailing list. I believe it's a known issue that the Rust compiler is making really heavy use of rapid allocation/freeing cycles, a…

  3. comment
    Comment #23086706

    The justifications are partly the same as what Daniel Micay has written extensively on in the rational for hardened_malloc ( https://github.com/GrapheneOS/hardened_malloc ) - unsyn…

  4. comment
    Comment #11626164

    There is no excuse for shell escaping bugs like this. 100% safe and reliable shell escaping is trivial: s/'/'\''/g s/^/'/ s/$/'/

  5. comment
    Comment #10469501

    Nice to see firm getting noticed. It's a really promising project.

  6. comment
    Comment #9657315

    To clarify, the numbers in my tweets are measured on Linux, comparing musl libc's posix_spawn (with CLONE_VM) to plain fork+exec (which should be independent of libc). I just poste…

  7. comment
    Comment #9654703

    The biggest problem with Cygwin is that programs linked with Cygwin inherit global state from from a Cygwin installation on the system they're running on. If you want to produce a …

  8. comment
    Comment #9654620

    These are some good observations. Note that on modern POSIX, calling anything but async-signal-safe functions after forking in a multi-threaded process results in undefined behavio…

  9. comment
    Comment #9653977

    No, fork is only one path that can lead to overcommit. Allocation of new memory as COW references to a zero page, and COW writable MAP_PRIVATE mappings of files (such as the writab…

  10. comment
    Comment #9653829

    No, OOM killer is completely orthogonal to this and is a consequence of not doing correct commit accounting. With strict commit accounting turned on (vm.overcommit_memory=2) fork w…

  11. comment
    Comment #9653674

    Yes, this is the really big deal that everyone focused on fork and mmap semantics and other details is overlooking. Having midipix as the means of producing Windows versions of cro…

  12. comment
    Comment #9653647

    Interix is a lot different because it requires installing a system component, which requires administrator privileges. Midipix produces applications that (at least as I understand …

  13. comment
    Comment #9653628

    I have a sequence of tweets here summarizing basic measurements I did on musl's posix_spawn versus fork+exec: https://twitter.com/RichFelker/status/602313644026761216 There are sti…

  14. comment
    Comment #8355592

    The choice isn't between 30sec or 15sec boot times. It's between 30sec, 15sec, or 1sec boot times, the latter coming from dropping all of the crap and writing a flat linear /etc/rc…

  15. comment
    Comment #8355564

    If your boot time was bad before and decent now, this is not thanks to the goodness of systemd but rather the badness of whatever hideous system your distro was using before, and/o…

  16. comment
    Comment #8355536

    Both forking and double-forking are completely wrong behavior for supervised daemons run as part of any automated system. Forking makes sense for small systems which lack any autom…

  17. comment
    Comment #8355515

    There are plenty of viable alternatives: s6, runit, OpenRC, and so on. I'm not really convinced uselessd is a viable alternative - it keeps way too much of the badness of systemd, …

  18. comment
    Comment #8355483

    People actually _want_ the logging behavior of systemd? My impression is that it's the most widely hated part; I've heard endless stories of journald thrashing the filesystem forev…

  19. comment
    Comment #8355460

    Systems which do not use systemd simply do not have these problems because there is no analogous component. If syslogd goes down, the worst that happens is you don't get logs. Init…

  20. comment
    Comment #8354038

    Whether it's all in pid 1 or not is irrelevant. What matters is that it has a monolithic architecture, whereby breakage in any one part or their communication channels can bring do…

  21. comment
    Comment #7856071

    Is there any proper information on this issue? The patches do not apply cleanly against the latest stable kernel (3.14.5) and there's no indication I can find as to what version th…

  22. comment
    Comment #7437750

    At the time the project was started, Ulrich Drepper was the maintainer of glibc and the official response to any bug report was "STFU". So, no. Aside from that, while a more permis…

  23. comment
    Comment #7436755

    LD_PRELOAD alone wouldn't do it because glibc's dynamic linker is closely tied to glibc. In particular thread-local storage requires close cooperation between them. Likewise, musl …

  24. comment
    Comment #7436026

    Fairly easily. A relatively small number of syscalls are used as part of implementing other functions. Most if not all of these are made via macros that expand to inline syscalls; …

  25. comment
    Comment #7435563

    musl actually has very little in the way of optimization, premature or otherwise. Most functions are written to be as simple and direct as possible. Often but not always this gives…