John Nemeth writes:
> On Jun 23,  2:14am, David Kelly wrote:
> } 
> } I fail to see why AX.25 belongs in the kernel, as Linux has done. Timing
> 
>      Umm, because that's where the lower layers of network protocols
> normally live.  This helps to improve general system performance since
> you don't need to context switch multiple times for every packet.

See other message. At 5 packets/sec its a non-issue.

> } needed then use the kernel's SL/IP, PPP, or BPF interface. Direct 
> } access to the 8530 serial port would be nice as then one could use a 
> 
>      Direct hardware access is a major no-no on multiuser systems.

Out of context. The above was an argument for in-kernel.

> } With that said, there used to be a suite of patches against NetBSD for 
> } adding AX.25 into the kernel at ftp.ucsd.edu. Have heard said that this 
> 
>      I poked around there, but didn't find it.  Could you post an exact
> URL please?

ftp://ftp.ucsd.edu/hamradio/packet/tcpip/bsd/386bsd.faq
The site isn't working very well for me tonight.

> } Unix needs a Unix-AX25 userland suite of applications. But nobody seems 
> 
>      Why, what's wrong with running TCP/IP over AX25?

No one to talk to.

--
David Kelly N4HHE, dkelly@hiwaay.net
=====================================================================
The human mind ordinarily operates at only ten percent of its
capacity -- the rest is overhead for the operating system.