[Bug 968573] systemd fails on symlink
![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
http://bugzilla.suse.com/show_bug.cgi?id=968573 http://bugzilla.suse.com/show_bug.cgi?id=968573#c14 --- Comment #14 from Liuhua Wang <lwang@suse.com> --- (In reply to Dieter Jurzitza from comment #10)
I just see that things that used to work for decades are changed because changing appears to be sexy.
IMHO it is a good idea to assign the modem device to a single identifier - and the best way to do this is parsing the output of hwinfo and then assign a device, thus keep the "software behind" entirely untouched. This reduces maintainance efforts, reduces the risk of errors and so on and so forth.
However, I can only suggest what I guess is the right way to do - moreover I do not consider it right to have a daemon run on each and every ttySx I do not use it for.
What regards your second question: no, changing the device does not happen often - but as readily said, I consider it much more efficient to determine the right device prior to fiddling around with tty - devices in unit names. What do you think about a feature request upstream to make /usr/lib/systemd/system/dm-event.socket work on softlinks to devices? Sorry but I don't understand why tty device has relationship with device-mapper? dm-event only cope with events from device-mapper devices. Shouldn't it be something with udev event?
Do you want to create a soft symlink(named modem) to actual device(for example ttyS*) ? If so I think you need to make some udev rules of your own to achieve that. Correct me if I am wrong. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com