On 12.01.2011 16:22, Rolf Leggewie wrote: > Hallo Sven, > > On 12.01.2011 08:50, Sven Hartge wrote: >> In upload 1:3.9.20060704+dfsg.2-8 you removed the MAKEDEV call from >> init.d.functions but this causes isdnlog and vboxgetty to fail for me, >> complaining about missing /dev/isdnctrl0 and /dev/ttyI1. > > The calls were obviously removed on purpose, I'm sure you were aware of > that. We as isdnutils maintainers feel that it's the kernel's job and > specifically the drivers' jobs to create the device nodes. Please > report a new ticket against the isdn4linux part of the kernel. It would > be cool if you let me know the ticket number so that I can follow it.
I know, the kernel (and udev) should create them, unfortunately i4l is deprecated and was never ported to use sysfs, so udev does not create any devices. And from the (sad) state of ISDN in the kernel I am guessing, nobody will port the code to sysfs. I even found discussions with Karsten Keil concerning this matter on the i4l-list as back as the days of Linux 2.6.6 in 2004 (!!). Have look at the following thread: http://osdir.com/ml/linux.isdn.i4l.user/2004-05/msg00011.html Quote: | - what is the best way to get these device nodes? create it in the ISDN start script with mknod (Answer from Karsten Keil) The kernel maintainers even removed i4l for a short period of time (see bug#588551) and I am afraid to submit a bug concerning this issue, because this might cause another removal from the kernel in Debian. (Note: you might want to document the fact one has to blacklist the mISDN drivers like hfcpci you want to use hisax, since the mISDN ones get automatically loaded and the i4l ones don't.) > I will leave this ticket open to document the necessary steps the users > have to take. Depending on the kernel team's reaction I may also > consider other options to make sure things are working as expected. > Overall, we feel that this is not really an isdnutils issue, though, but > should be dealt with elsewhere. Question is: where? As is, the packages don't work, since the needed devices are missing and nobody creates them. >> Additionally the following code should IMHO be changed to use "-sf" to not >> fail if the link already exists: >> >> 91 if [ ! -e /dev/isdnctrl ]; then >> 92 cd /dev && ln -sf isdnctrl0 isdnctrl >> 93 fi > > Thank you for this suggestion. But I don't quite understand the need to > force the creation. That's what the if-part is for, isn't it? During the state of my system without any ISDN device nodes, the start script for isdnlog etc. complained about an already existing symlink. This is because -e dereferences the symlink and if the target is not available, it will fail. So the correct solution here is not to use "ln -sf" but to use "[ -L /dev/isdnctl ]" to check for the existance of the symlink. > > PS: I hope this one goes out as plaintext and not HTML. TB is getting > too smart for its own good lately. Was in HTML. Grüße, Sven. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
