Re: [suse-sles-e] A better framework for named configuration

From: Michael James (Michael.James_at_csiro.au)
Date: Tue Mar 14 2006 - 00:35:57 CET


From: Michael James <Michael.James@csiro.au>
Date: Tue, 14 Mar 2006 10:35:57 +1100
Message-Id: <200603141035.58260.Michael.James@csiro.au>
Subject: Re: [suse-sles-e] A better framework for named configuration


> On Monday 13 March 2006 05:35, Michael James wrote:
> > While many of the YaST modules are excellent,
> > the SuSE approach to configuring named
> > has 3 big problems:
> 1) YaST hides the ONLY copy of the master zone files
> > way down in /var/lib/named/ !!!
> > WHAT is important information doing stashed there?
> > Shouldn't ALL configuration info be in /etc ? (Debian style)

On Tue, 14 Mar 2006 12:00 am, Silviu Marin-Caea wrote:
> No, you are not familiar with the Filesystem Hierarchy Standard.
> The files are in the right place.
>
> http://www.pathname.com/fhs

I'm talking about the primary master zone files.
The files I vi to add another host or CNAME.

FHS says: "Users must never need to modify files in /var/lib
   to configure a package's operation."

I modify those files all the time.
I think they belong in /etc where they get backed up religiously.

Slave zones that are axfer-ed in by named DO belong in /var/
 but I like to preserve them between runs; and I like
 to make the chroot jail an exact copy of the master directory.
So, copy slaves up then copy everything down.

-- 
Michael James                         michael.james@csiro.au
System Administrator                    voice:  02 6246 5040
CSIRO Bioinformatics Facility             fax:  02 6246 5166
No matter how much you pay for software,
 you always get less than you hoped.
Unless you pay nothing, then you get more.
---------------------------------------------------------------------
To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
For additional commands, e-mail: suse-sles-e-help@suse.com


This archive was generated by hypermail 2.1.7 : Tue Mar 14 2006 - 00:36:12 CET