Shouldn't /var/log/setup/setup.90.modem-device setup script be updated to create an udev rule instead of a non persistent /dev/modem symlink? And if so, who I can report it to?

thanks
kc

You would report such issues to Patrick himself.

But if I had to guess, I would assume it is done this way because the user is directly asked which device he wants to link to /dev/modem during the installation. Modems are generally not going to be removable devices and changing device nodes (there are obviously USB modems, but 90% are going to be internal or at most RS232 external) so there really isn't any reason to have udev handle it. udev is better left for things that have a high likelihood of changing during the lifespan of the computer, like optical drives and video cards.

Thanks, just wanted to make sure to be right before bothering Patrick

I'm not concerned about the modem changing device node, but rather about udev resetting the whole device nodes sytem at each boot and destroying your /dev/modem symlink. Pretty useles to ask for it during the installation

http://www.linuxquestions.org/questi...d.php?t=358522
http://www.linuxquestions.org/questi...d.php?t=387006
http://www.linuxquestions.org/questi...d.php?t=354951

Is this issue still relevant though? All of those topics are from the Slackware 10/11 days, where the udev implementation was unreliable at best (the time in which Slackware attempted to juggle a 2.4 and 2.6 kernel was arguably the most unstable period since it's early days).

Slackware 12 has made vast improvements on the udev and kernel fronts. I would be surprised (though not totally disbelieving) if this situation was still the case. Granted very few people are still using dial-up modems, but I have a hard time believing that this issue could have gone unnoticed for so long.

In my Slackware 12, nothing I put in /dev survive reboot (unless I make an udev rule).
Isn't this the normal udev behaviour? Can a Slackware 12 user verify it by making a symlink in /dev and checking if it survive reboot?

This is indeed normal behavior.

I have a hard time too, believing that this issue could have gone unnoticed for so long, but...

1) during my slackware 12 installation I choosed to link /dev/modem to /dev/ttyS0 and after the first reboot /dev/modem wasn't there anymore;
2) no matter how many times I run that setup script, /dev/modem keeps disappearing;
3) that script just use ln to make the symlink: ( cd $T_PX/dev ; ln -sf $MODEM_DEVICE modem );
4) symlinks in /dev don't survive reboot unless you make an udev rule (normal behavior);

I'll report it to info@... (unless anyone is going to provide evidence that I'm wrong )