4 ms·

I found a few bugs where journald was losing data for example. I reported them and they got fixed in later releases. Of course I still got called a neckbeard a

by LtWorf 4mo ago

I found a few bugs where journald was losing data for example. I reported them and they got fixed in later releases. Of course I still got called a neckbeard and got told that I didn't like systemd because I'm a dinosaur and so on. So I have a really hard time to take positions such as your seriously to be honest.

0dayz 4mo ago
If you mean that there are times systemd has a critical bug; sure the same way x11, kernel modules or drivers have critical bugs are annoying. You can always point to where I said you are a neckbeard, so I do not get the "hard time" angle. You can not like systemd, but the arguments for it is silly, and that is fine it's your machine and I don't care as long as people stop spreading FUD on such awful grounds. Say in contrast with BTRFS or BcacheFS there are genuine issues with those and there are technical philosophical arguments (I want journaling, I do not want or need CoW features, snapshot? never heard of her).
- LtWorf 4mo ago
  You are precisely part of the mob I was describing. Perhaps you did not say exactly word by word "neckbeard" but you are dismissing all the arguments as FUD. As I said, when distributions were already using systemd by default I installed it and tried it for one hour and found 3 different ways it was losing data sent to journald. According to you when a logging daemon loses log entries, stating that it's not ready for real use is FUD. Funny how you think of yourself as being the reasonable one here :)
  - 0dayz 4mo ago
    Right, why did you feel the need to straw man me to somehow justify your victim complex? You can cite me for when I said all arguments are FUD, or even that yours was. And if your issue is that it's not ready, okay? That had nothing to do with my point. So let me repeat, do you swear to never use a certain Linux kernel module because it has critical bugs? If yes okay good that is a most likely temporary technical argument so why spread FUD about it?

by LtWorf 4mo ago

0dayz 4mo ago

If you mean that there are times systemd has a critical bug; sure the same way x11, kernel modules or drivers have critical bugs are annoying. You can always point to where I said you are a neckbeard, so I do not get the "hard time" angle. You can not like systemd, but the arguments for it is silly, and that is fine it's your machine and I don't care as long as people stop spreading FUD on such awful grounds. Say in contrast with BTRFS or BcacheFS there are genuine issues with those and there are technical philosophical arguments (I want journaling, I do not want or need CoW features, snapshot? never heard of her).

LtWorf 4mo ago
You are precisely part of the mob I was describing. Perhaps you did not say exactly word by word "neckbeard" but you are dismissing all the arguments as FUD. As I said, when distributions were already using systemd by default I installed it and tried it for one hour and found 3 different ways it was losing data sent to journald. According to you when a logging daemon loses log entries, stating that it's not ready for real use is FUD. Funny how you think of yourself as being the reasonable one here :)
- 0dayz 4mo ago
  Right, why did you feel the need to straw man me to somehow justify your victim complex? You can cite me for when I said all arguments are FUD, or even that yours was. And if your issue is that it's not ready, okay? That had nothing to do with my point. So let me repeat, do you swear to never use a certain Linux kernel module because it has critical bugs? If yes okay good that is a most likely temporary technical argument so why spread FUD about it?