i use udev, but i don't think thats the problem. it's just a bit unpractical to make the device everytime again. i think that's not the way it should work. Reproducible: Always Steps to Reproduce: 1.reboot 2."pon isdn/arcor" 3.there it is Actual Results: well, it says "You need to create the /dev/ppp device node by executing the following command as root: mknod /dev/ppp c 108 0" Expected Results: either remembered /dev/ppp or made it by itself or something which doesn't need my help
greg: Do you think the problem can be solved in udev? Is there any other option than preloading the module?
ummm.. isn't RC_DEVICE_TARBALL=yes setting in /etc/conf.d/rc the natural solution to this problem? what about appending ppp_generic to the /etc/modules.autoload.d/kernel-* ? imo this bug is invalid, but I leave it to you, Stefan.
This is dupe of Bug 76442.
>------- Additional Comment #2 From Alin Nastac 2005-05-30 14:06 PDT ------- > >ummm.. isn't RC_DEVICE_TARBALL=yes setting in /etc/conf.d/rc the natural >solution to this problem? i don't believe that using the device tarball is the solution - loading the module in the kernel-2.6 file yes, but using the device tarball almost defeats the purpose of using udev. At least, my understanding of it is that it only creates/shows hardware that you have on your machine, whereas the tarball takes a snapshot of /dev (which before you have udev, is devfs and thus everything)
if the purpose of udev is to create only useful devices, I don't see how could automagically create /dev/ppp without ppp_generic support being added to the kernel (either included in kernel or as a module but loaded at boot time). obviously, this bug is a duplicate *** This bug has been marked as a duplicate of 76442 ***
