[asterisk-dev] minimal default configuration

Michiel van Baak michiel at vanbaak.info
Sun Nov 25 05:18:43 CST 2007

On 08:13, Sun 25 Nov 07, Tzafrir Cohen wrote:
> > > So I'd like to get to a situation where Asterisk is as functional as
> > > possible with the minimal ammount of configuration files, rather than
> > > rely on the sample config files.
> > > 
> > 
> > All them configuration files will only be installed if you
> > manually run 'make samples'
> > I think you should do the same with the debian package. Make
> > it optional. Dont let asterisk or asterisk-addons or
> > whatever package depend on it.
> But then I install asterisk and it will not work.
> This is because some modules fail to load. Or because chan_alsa /
> chan_oss (who ever got there first) hogs on my sound card and won't
> release it. Or whatever.

Have a look at pound.
That package wont start unless you set some variable in
/etc/default/pound.conf. The installation of the package
will mention this as soon as the package is succesfully

> > 
> > Yes, I'm a big OpenBSD fan, I know, but hear me out.
> > For this same reason OpenBSD upgrades dont install the
> > etc<version>.tgz
> > the etc<version>.tgz tarball has the default configs for
> > that version, and during an upgrade you cannot select the
> > etc tarball to be installed. They do notify you to compare
> > the stuff by hand and they also give a list of files you
> > probably can copy verbatim and a list of files you most
> > probably edited to reflect your install.
> As I mentioned before, that strategy will lead you to have an obsolete
> sample files under /etc/asterisk/ . That policy is practically the same
> except you thift the whole burder to the user. The problem remains the
> same.

Every package that comes with configuration files have this
problem. If I altered the files and upgrade the package the
configfiles will be obsolete. If a user upgrades software
they know this.

> > 
> > I think this is the way to go for packages.
> > The asterisk source install is very nice as it requires an
> > extra step before you overwrite your configs.
> But again, this eventually leaves you with obsolete configs under
> /etc/asterisk . Because noone should run 'make samples' on a system that
> has already been configured.
> Again, you're ignoring the problem.

I'm not ignoring it.
I'm basically saying the same thing as you. 'make samples'
should never being run on a system that is configured.
UPGRADE.txt is your friend here.

> > Specially because every howto/source/install refers to
> > UPGRADE.txt so you can look there what you need to change.
> > (yes, this is even doable for 1.0->1.4 upgrades, I just did
> > that last friday on a couple of production boxen)
> I also refer to updates between versions in the stable branch.

Updates between versions in a stable branch should never
render your configs unusable. stable branch only gets
bugfixes, not new features.


Michiel van Baak
michiel at vanbaak.eu
GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x71C946BD

"Why is it drug addicts and computer afficionados are both called users?"

More information about the asterisk-dev mailing list