Hacker News Reader

Sure. My most recent headache is with using a USB wifi dongle. During system startup, I want to attach some remote drives over wifi, so I need to be able to do that after the wifi connection is established.

Systemd does not appear to be able to tell when that happens. It thinks the network is established before it actually is, and then the mount calls cause the startup process to pause for 3 minutes for those mount calls to time out before continuing.

View on HN

The funny thing is that sounds like a perfect case for systemd: By eating so many parts of the OS (here, device management, filesystem mounting, networking, and service management), it should be able to create very explicit dependency graphs - "this mount depends on this network which depends on this device". I wonder where the problem is - can it not properly handle something between the device and network? Or is it hitting the "network is up" goal too early?

Thank you. I wish to add bluetooth dongle and expecting some headaches there. It seems setting up a full bluetooth stack would be challenging to say the least and I wander if systemd would contribute more to the challenge or to the solution.

Reply on news.ycombinator.com