Re: Time to stop buildling named (and friends) by default in 6-current?

From: Philip Paeps (philip_at_FreeBSD.org)
Date: 03/19/05

  • Next message: John Baldwin: "Re: Time to stop buildling named (and friends) by default in 6-current?" 
    Date: Sat, 19 Mar 2005 23:55:07 +0100
To: Robert Watson <rwatson@FreeBSD.org>

    On 2005-03-18 12:14:03 (+0000), Robert Watson <rwatson@FreeBSD.org> wrote:
    > On Thu, 17 Mar 2005, Doug Barton wrote:
    > > Scott Long wrote:
    > > > John Baldwin wrote:
    > > > > If we are going to do this, then why not just have users install bind
    > > > > from ports and only install the client as part of the base system?
    > > > > This is what we do with DHCP for example. Basically, if it's going to
    > > > > be an optional component, I think it belongs in ports, not the
    > > > > /usr/src.
    > > >
    > > > I agree here, though maybe the argument is moot now that Doug imported
    > > > 9.3.1 last night? Not changing the status quo is ok too.
    > >
    > > Scott, did you see my response to John's post? I don't consider any of
    > > this a done deal, but I had to get 9.3.1 in the tree asap in order to try
    > > and make an MFC before 5.4 goes out. If we collectively decide to strip
    > > named and friends out of the base, we can still do that. I know how to
    > > remove files from the vendor branch now. :)
    >
    > Personally, I'm something of a fan of keeping the complete BIND in the base
    > tree as is -- built by default, but not started at boot by default. It's
    > well-maintained, historically "BSD", and probably widely used as such.

    I agree with this. I wasn't very fond of BIND 8, but I've changed my mind
    after BIND 9 :-) It's a bit like sendmail -- very 'historically' BSD, and
    just something one expects to 'be there' in a complete way. Like sendmail,
    it's also very well maintained, which is an argument in favour of keeping it
    the way it is.

     - Philip 

    -- 
Philip Paeps                                    Please don't Cc me, I am
philip@freebsd.org                               subscribed to the list.
  If you can't measure it, I'm not interested.
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
  • Next message: John Baldwin: "Re: Time to stop buildling named (and friends) by default in 6-current?"

    Relevant Pages

    • music outside medical trainee
      ... My proposed gun won't gasp before I bind it. ... longing since cultural, plus prior, in response to bitter gates. ... The poor authority rarely invents Hakeem, ...
      (sci.crypt)
    • Correction: 9.3.0rc4 [Re: HEADS UP! BIND 9.2.3 coming soon!]
      ... Scott Long wrote: ... > I wanted to give everyone fair warning that BIND 9.2.3 will be replacing ... If you are running production BIND servers then you might want ...
      (freebsd-current)
    • SUMMARY - NIS question
      ... Everyone thanks for your response. ... one as a primary or one as a slave) or will NIS only allow me to bind to ... When you set up the client with 'ypinit -c', you can specify one or more ...
      (SunManagers)
    • Re: GridView LINQ double foreign key
      ... You may have noticed that Scott Gu's blog uses "Eval", ... databinding keyword, to bind the 2-level property "Supplier.CompanyName". ... Scott uses an additional dropdownlist "CategoryList" to ...
      (microsoft.public.dotnet.framework.adonet)
    • Re: DNS response for non-fqdn domain
      ... Syafril Hermansyah wrote: ... NXDOMAIN instead of SERVFAIL when client query NON-FQDN domain just like ... linux BIND did. ... above is response from W2K3 DNS ...
      (microsoft.public.windows.server.dns)