tomegun

7 ms·

1. 31.▲
   by tomegun 10y ago

   What's high-level about bus1? This has nothing to do with systemd, and very little (apart from history) to do with kdbus. As to portability, this is a linux kernel module, but there is nothing really inherent to linux about it, so port
2. 32.▲
   by tomegun 12y ago

   Similarly broken how? Just because strdupa is not magical, does not mean it has its valid uses. In particular, the problem you allude to (knowing the scope of your memory) is something you would have to get right also if you use heap-alloca
3. 33.▲
   by tomegun 12y ago

   Hm, this criticism seems hardly fair. systemd is explicitly unportable (it uses glibc/gcc/linux-specific features liberally), this is not some sign of sloppy coding, but an explicit design decision as codified in the CODING_STYLE
4. 34.▲
   by tomegun 12y ago

   Care to point to the line with the memory leak. Can't see one here (you sure you understood how the _cleanup_* macros work?).
5. 35.▲
   by tomegun 13y ago

   We (the systemd developers) want systemd to provide the basic building blocks from which you can build an operating system. Networking is definitely one of these, so we want to include it by default. However, you are of course free to use a