Bill Huey:
> > In the specific case of /etc/services, which should be ordered but only
> [snip]
> > service name? The number? Any one of the aliases? IMHO the file doesn't
> > really fit the directory lookup paradigm at all. So why try and force it
> > into one?
> >
> Uh, the idea of having stuff in /etc work like the old flaky NeXTStep
> Mach/Unix conjures up past nightmares of constant flakiness of using that
> particular feature.
>
> Uhg, Text files are good, monkey man scratch... (scratch scratch)
>
Ahem.
I didn't imply that text files are good, only that having a directory
which contains the /etc/services entries isn't exactly a cool idea either
(neither is a text file, BTW).
It's really a database. So use one -- glibc supports DB or NIS or
whatever else you want to implement.
I don't think the semantics for correctly updating /etc/services should
be in the kernel. Where does it stop? Next you'll want /etc/smb.conf, or
/etc/XF86Config. Surprise, I want it too, but not that way please.
-- Matthias Urlichs | noris network GmbH | smurf@noris.de | ICQ: 20193661 The quote was selected randomly. Really. | http://www.noris.de/~smurf/-- Waiters and waitresses do it for tips.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/