svn commit: r318250 - in head: etc etc/newsyslog.conf.d etc/syslog.d tools/build/mk

Ian Lepore ian at freebsd.org
Mon May 15 20:49:34 UTC 2017


On Mon, 2017-05-15 at 20:28 +0000, Alexey Dokuchaev wrote:
> On Mon, May 15, 2017 at 02:11:53PM -0600, Ian Lepore wrote:
> > 
> > ...
> > In general a lot of this feels like "I only needed 6 big config
> > files
> > to control my whole system in 1988, and so I should only need those
> > same 6 files now."
> Yup; doesn't it feel good?  (That's one of our selling points BTW.)
> 
> > 
> > Sure, all us old-timers have the finger memory for editing rc.conf
> > and
> > syslog.conf and so on, but how often do you crack open syslog.conf
> > with
> > the plan of editing 12 different lines in it at once?
> Actually I don't want to open it [newsyslog.conf] at all, and on
> desktop,
> where odd things are noticed quickly, default rotation is good
> enough.
> I might want to edit it on server to e.g. keep at least one year
> worth of
> logs, and when I do, I'd rather edit one file instead of half-dozen.
> 
> > 
> > Because the main objection to .conf.d directories seems to be that
> > there are more files to edit, and that just doesn't feel like a big
> > problem in actual daily use.
> Well, it kind of is.  Keeping in mind "same 6 files" is a big helper;
> for the base you can be sure you won't forget anything accidentally.
> It is not that easy for ports for obvious reasons, but then again: we
> are talking about the base only here.
> 

What you're talking about is how YOU view and use base.  That's fine,
except that obviously it's only a tiny subset of how all freebsd users
view and use base.

Besides how I view things as someone who has to create and maintain
complex embedded systems with freebsd, as a simple user of freebsd I
would much prefer to edit syslog.conf.d/mail than search around in a
big syslog.conf file for lines pertaining to mail logging.

You acknowledge that the situation is different for ports, so does that
mean your objections go away when base becomes packaged and faces the
same installation and update issues that packaged ports do?  Because I
was under the impression that's coming pretty soon.

-- Ian

> ./danfe
> 


More information about the svn-src-head mailing list