Roland Dowdeswell <elric@imrryr.org> writes:
> On 1045672760 seconds since the Beginning of the UNIX epoch
> Jason R Thorpe wrote:
> >And why do I need a web server installed *at all* on my workstation?
> >
> >The same argument applies for a full-blown MTA... any "real" mail server
> >could build sendmail or postfix or qmail or exim from pkgsrc.
> 
> The problem is that you can make this argument for almost anything.
> What about ftpd?  Why do I need that on my workstation?  What about
> telnetd?  What about named?  I don't use dhcpd on any of my NetBSD
> machines and when I do, I generally only use on one machine per
> subnet.  I don't use YP, so why does the base distribution include
> rpc.yppasswdd?  Why shouldn't we make nfsd into a pkg, since most
> people only run one NFS server and why should their workstations
> have it?  Why ship power management utils considering that most
> NetBSD machines aren't laptops?  Etc, etc.

You know, it is obvious that having a built in named gets in the way
of the people who want to use an alternative, like djbdns
say. Also, when we ship our own named, what if someone wants different
permissions on their named binary? Every time you build NetBSD you
just end up getting the permissions you prefer blown away. It is
obviously wrong that we are shipping with a named at all, especially
given that it isn't clear if people want bind 8, or bind 9, or djbdns,
or whatever. Also, most clients don't need a name server, just a
resolver.

By the way, I never use vi. I hate having to deal with the bloat of
it. Awaiting permission to remove the vi sources....


Perry
PS Every machine I own runs an MTA, even my laptop.