Summary: | kernel module tun has wrong device links | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dominik Westner <gentoo> |
Component: | [OLD] Core system | Assignee: | Martin Schlemmer (RETIRED) <azarah> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bartelt, gentoo |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dominik Westner
2002-04-07 08:09:11 UTC
I think it's a devfsd issue. You may want to contact Richard Gooch and see what he says about this. Probably an easy fix is available. this is definitely a devfs issue. a search on google reveals as much, but what it hasn't revealed is a workaround. people simply say use /dev/misc/net/tun in 2.4 w/devfs can we close this bug? # please test this addition to devfsd.conf. # on my system it looks like fixing the link. # net/tun hotfix LOOKUP ^net/tun$ CFUNCTION GLOBAL unlink ${mntpnt}/net/tun LOOKUP ^net/tun$ CFUNCTION GLOBAL mksymlink ${mntpnt}/misc/net/tun ${mntpnt}/net/tun REGISTER ^misc/net/tun$ CFUNCTION GLOBAL unlink ${mntpnt}/net/tun REGISTER ^misc/net/tun$ CFUNCTION GLOBAL mksymlink ${mntpnt}/misc/net/tun ${mntpnt}/net/tun # indented lines shall be joined with previous ones, sorry. this seems to fix it for me. This fix works for me, too. <sasquach> Azarah: and when we speak of bugs... can you look at 1585 and put that fix in devfsd.conf somehow? <stroke> GenBot: bug 1585 ? <GenBot> stroke: Bug http://bugs.gentoo.org/show_bug.cgi?id=1585 nor, P2, All, azarah@gentoo.org, NEW, kernel module tun has wrong device links <stroke> GenBot: thanks <GenBot> stroke: np <Azarah> sasquach: why once again ? <Azarah> sasquach: its an hack for a kernel problem <Azarah> sasquach: recent kernels fix it so please document that and close this bug. Its a kernel issue: nosferatu dev # modprobe tun nosferatu dev # ls net/ tun nosferatu dev # ls net/ -l total 0 crw-r----- 1 root root 10, 200 Jan 1 1970 tun Update to recent kernel (i have 2.4.19_rc1 ... mjc-sources ...). thanks. so it's time to mark this bug as closed/fixed. or is there any reason to let it in status "NEW"? Yeah .. bit busy this side ;-) |