60ab2ca5c0
kernel and provides the same device on the host with pud(4). I can succesfully talk to my u3g device using tip(1) against the server's devices. Some characters are lost here and there, though (probably a problem with interrupt pipes in ugenhc). Once that issues is solved, there is no reason why e.g. pppd (chat) could not be used against the server. Now, why would anyone want to do this instead of using the kernel driver directly? Well, for one, on my laptop I run netbsd-5 which doesn't have a u3g driver which supports the u3g hardware I have. As anyone with half an eye can see, this is quite copypasted from umserv and there is plenty of opportunity for uncopypasting for the eager vi-wielder. |
||
|---|---|---|
| .. | ||
| amd | ||
| apm | ||
| disktab | ||
| emul | ||
| fstab | ||
| ftpd | ||
| getdate | ||
| hostapd | ||
| isdn | ||
| pppd | ||
| pud/intro | ||
| puffs | ||
| racoon | ||
| refuse | ||
| rump | ||
| secmodel | ||
| supfiles | ||
| syslogd | ||
| wsmoused | ||
| Makefile | ||