AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070806163759.51e26832@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<maxim.kozlovsky@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E04DFA426@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Mon, 6 Aug 2007 16:38:16 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>
Subject: Re: syslog.conf
Message-ID: <20070806163816.1ea3a9c8@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E04DFA426@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E04DFA3AD@onstor-exch02.onstor.net>
	<20070806151258.5778ba03@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E04DFA3BA@onstor-exch02.onstor.net>
	<20070806153227.2c1bee6c@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E04DFA426@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Mon, 6 Aug 2007 16:05:52 -0700 "Maxim Kozlovsky"
<maxim.kozlovsky@onstor.com> wrote:

> 
> 
> >-----Original Message-----
> >From: Andy Sharp
> >Sent: Monday, August 06, 2007 3:32 PM
> >To: Maxim Kozlovsky
> >Subject: Re: syslog.conf
> >
> >On Mon, 6 Aug 2007 15:14:11 -0700 "Maxim Kozlovsky"
> ><maxim.kozlovsky@onstor.com> wrote:
> >
> >We won't be using that code.  For now just copy
> >/var/nfsroot/bc-masses/etc/syslog.conf
> >by hand.  We will be writing a new method for installing /etc (and
> >similar) files during the makerootfs phase of building.
> [MK] 
> This file does not go in /etc, it goes into /usr/local/agile/etc. I
> don't see any reason to not use the existing code.

Because the existing code el-sucko?  The file is /etc/syslog.conf, yes?
So we should treat it as such instead of having this weird,
unexpected other file around for now good reason.  We've already created
a plan for handling such files.