Carl Lowenstein wrote:
On 3/8/06, Ralph Shumaker <[EMAIL PROTECTED]> wrote:
I have just installed fc4 on a clean new system.
On my old system, rh9 saw the modem as /dev/ttyS4 (note the "S4") and
automatically setup the link /dev/modem to point to it (or come to think
of it, I /may/ have had to set up the link manually). Anyway, this link
survived reboots.
On my new system, fc4 sees the same modem as /dev/ttyS14 (note the
"S14") and does not set up the /dev/modem link. What's more, each and
every time I reboot, the link disappears. The link survives logouts,
but not reboots.
It wouldn't be so bad if the PPP program interfaces would offer
/dev/ttyS14, but they don't go beyond /dev/ttyS4. But since they offer
/dev/modem, I can just link /dev/modem to /dev/ttyS14, except that I
have to do it after every boot to keep them working.
Anyone know what's going on with the evaporating link?
Brute-force solution: in /etc/rc.local add the line
ln /dev/ttyS14 /dev/modem
I realize that this fixes the symptom and not the disease.
In principle, the creation of the /dev entries is controlled by files
in /etc/makedev.d but I don't offhand understand how it is supposed to
work.
carl is on the right track. Read the man page for MAKEDEV. In the
/etc/makedev.d directory create a file called modem. The contents of the
file should contain the following:
l modem ttyS14
That first character is a lower case ELL. When the system starts up,
MAKEDEV runs and searches the /etc/makedev.d directory for files which
contain instructions on what it is supposed to create. The modem file
above tells MAKEDEV to create a symbolic link (the l at the beginning of
the line) named modem to point to the real device ttyS14.
Make the modem file owned by root, group root, -rw-r--r--, i.e. set
ownership and permissions the same as the other files in the directory.
Gus
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
