From mi@rtfm.ziplink.net  Fri May 29 10:52:59 1998
Received: from aldan.ziplink.net (mi@kot.ne.mediaone.net [24.128.29.55])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25103
          for <FreeBSD-gnats-submit@freebsd.org>; Fri, 29 May 1998 10:52:56 -0700 (PDT)
          (envelope-from mi@rtfm.ziplink.net)
Received: from rtfm.ziplink.net (rtfm [199.232.255.52])
	by aldan.ziplink.net (8.8.8/8.8.7) with ESMTP id RAA07068
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 29 May 1998 17:52:49 GMT
	(envelope-from mi@rtfm.ziplink.net)
Received: (from mi@localhost)
	by rtfm.ziplink.net (8.8.8/8.8.5) id NAA23538;
	Fri, 29 May 1998 13:52:49 -0400 (EDT)
Message-Id: <199805291752.NAA23538@rtfm.ziplink.net>
Date: Fri, 29 May 1998 13:52:49 -0400 (EDT)
From: Mikhail Teterin <mi@aldan.algebra.com>
Reply-To: mi@aldan.algebra.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: /etc/dump.conf
X-Send-Pr-Version: 3.2

>Number:         6785
>Category:       bin
>Synopsis:       place for all the default dump flags
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          suspended
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Fri May 29 11:00:01 PDT 1998
>Closed-Date:    
>Last-Modified:  Fri Jul  5 12:30:01 PDT 2002
>Originator:     Mikhail Teterin
>Release:        FreeBSD 3.0-CURRENT i386
>Organization:
Virtual Estates, Inc.
>Environment:


>Description:

	When using dump(8) indirectly (such as through Amanda) it is
	often inconvenient/hard to alter flags like ``h'' on command
	line. Something like /etc/dump.conf and/or DUMPFLAGS env variable
	would allow to alter dump's default behaviour without
	recompilations.

>How-To-Repeat:


>Fix:
	
	If this is not "a bad idea which will never make it into
	FreeBSD", I can try myself in adding this in. If there is
	something like this in other OSes, please, tell me...
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->suspended 
State-Changed-By: phk 
State-Changed-When: Tue Jun 2 02:53:12 PDT 1998 
State-Changed-Why:  
sounds like a good idea.  Maybe to avoid an explosion of /etc/foo.conf 
files we should introduce /etc/defaults.conf or something, which has a 
section for each program.  This would be strongly dependen on a library call 
to get the values from that file in a systematic way. 

From: "Cox SMTP central" <harry685@cox.net>
To: <freebsd-gnats-submit@FreeBSD.org>, <mi@aldan.algebra.com>
Cc:  
Subject: Re: bin/6785: place for all the default dump flags
Date: Fri, 5 Jul 2002 14:24:50 -0500

 This is a multi-part message in MIME format.
 
 ------=_NextPart_000_0003_01C2242F.B8C8B7A0
 Content-Type: text/plain;
 	charset="iso-8859-1"
 Content-Transfer-Encoding: quoted-printable
 
 Why not use, say, a "dupflags.conf" file instead?
 
 ------=_NextPart_000_0003_01C2242F.B8C8B7A0
 Content-Type: text/html;
 	charset="iso-8859-1"
 Content-Transfer-Encoding: quoted-printable
 
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <HTML><HEAD>
 <META http-equiv=3DContent-Type content=3D"text/html; =
 charset=3Diso-8859-1">
 <META content=3D"MSHTML 6.00.2716.2200" name=3DGENERATOR>
 <STYLE></STYLE>
 </HEAD>
 <BODY bgColor=3D#ffffff>
 <DIV><FONT face=3D"Microsoft Sans Serif" size=3D2>Why not use, say, a=20
 "dupflags.conf" file instead?</FONT></DIV></BODY></HTML>
 
 ------=_NextPart_000_0003_01C2242F.B8C8B7A0--
 
 
>Unformatted:
