| 1 |
> It could be I found a bug. After a reboot it went from the normal enp0s1 |
| 2 |
> (or whatever) to eno1677789 or something ridiculous. I had this happen |
| 3 |
> on two different machines. |
| 4 |
Sounds like you have other problems than an init system with your |
| 5 |
systems. Could be your PCIe stuff isn't working correctly |
| 6 |
> |
| 7 |
|
| 8 |
> For what it's worth, systemd works fine on my 11-year-old laptop. It had |
| 9 |
> issues with my desktop (which is almost 9 years old now) but I really |
| 10 |
> don't know if it was related to mdadm, or ??? I thought I had it figured |
| 11 |
> out on my desktop but on reboot systemd wouldn't mark my IMSM mdadm |
| 12 |
> array as clean leading to a disk thrashing every time I rebooted, making |
| 13 |
> my computer almost unusable. |
| 14 |
|
| 15 |
I don't see a strong relation between bugs in your RAID and systemd |
| 16 |
itself. Maybe service files are buggy or wrong. But imagine, your |
| 17 |
init-script has a bug? Stuff will certainly break. |
| 18 |
|
| 19 |
Easy to blame things on something you don't like, I know. |
| 20 |
I don't like every aspect of using systemd either. Still I have more |
| 21 |
benefits than drawbacks from using it. Even the binary log files have |
| 22 |
their benefits. Personally I make heavy use of `--boot -p err --since= |
| 23 |
--unit" flags in journalctl to get logs I want without trying to figure |
| 24 |
out the right grep pattern and wasting my time to get it right. And |
| 25 |
still you can configure it to pass logs to rsyslog. |
| 26 |
|
| 27 |
You can look at the bugtracker in udev if someone experiences random |
| 28 |
if-name changes. |
| 29 |
|
| 30 |
Cheers, |
| 31 |
Andrej |
Archives