| 1 |
Yep. It's async and that's an expected udev behaviour. |
| 2 |
I've been just lucky. |
| 3 |
Those interested may search for "udev is too slow creating devices" |
| 4 |
thread in linux kernel mailing list archives or google:) |
| 5 |
|
| 6 |
> There now seems to be certain time lag between tun module is loaded |
| 7 |
> and /dev/net/tun is created. So the script would die on the following lines: |
| 8 |
> |
| 9 |
> modprobe tun |
| 10 |
> if [ ! -c /dev/net/tun ]; then |
| 11 |
> echo "/dev/net/tun doesn't exist" |
| 12 |
> exit |
| 13 |
> fi |
| 14 |
> |
| 15 |
> Adding tun to /etc/modules.autoload.d/kernel-2.6 helps |
| 16 |
> but the question now is if it's normal behaviour or a bug |
| 17 |
> introduced with recent udev upgrade? |
| 18 |
> |
| 19 |
> |
| 20 |
>>Do you have "Universal TUN/TAP device driver support" (CONFIG_TUN) |
| 21 |
>>enabled in your kernel configuration? It should be a network device in |
| 22 |
>>your kernel configuration: |
| 23 |
>> |
| 24 |
>>Device Drivers --> |
| 25 |
>> Networking support --> |
| 26 |
>> Network device support --> |
| 27 |
>> <*> Universal TUN/TAP device driver support |
| 28 |
>> |
| 29 |
>>You can also build it as a module, and it will be called "tun". |
| 30 |
>>Hope that helps! |
| 31 |
> |
| 32 |
> |
| 33 |
|
| 34 |
-- |
| 35 |
gentoo-user@g.o mailing list |
Archives