On Thu, Apr 27, 2000 at 12:32:37AM +0200, Jens David wrote:
> But still I thing this is solely the distro�s problem. Applications and
> tools should never read such a file directly or via libax25. They should
> use the socket interface as all other protocol families also do.
So pretty much any configuration tools has it values on the command line
like ifconfig or /sbin/ip and any daemons or other things use
/proc/sys/net/ax25/<something> or an ioctl?
Sounds ok to me.
> That�s another thing I�d really like to get rid of. What�s the point of
> having symbolic names? IMHO it causes more confusion (i.e. when to use what)
> than glory. As I understand it you can rename any kernel network interface
> to anything you like (<8 chars) using the ip utility?
Symbolic names are very useful for things that can move around. For
example I have a port that talks to sydney. This port might be a
soundmodem, a packetwin or a kiss modem. Why change the interface name
depending on the hardware? Tunnels are even worse because it depends on
what order you do them in.
Yes, the kernel allows you to use names, why not use the same system
calls? Better yet, if possible why not use the same tools? All my IPv6
tunnels have names, I could never remember who the hell sit3 was, but I
definitely know where 'gonzo' goes to.
Actually can't we just add an address family to /sbin/ip ?
- Craig
--
Craig Small VK2XLZ GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5
Eye-Net Consulting http://www.eye-net.com.au/ <[EMAIL PROTECTED]>
MIEEE <[EMAIL PROTECTED]> Debian developer <[EMAIL PROTECTED]>
