From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/tvheadend: change configuration directory
Date: Wed, 30 Nov 2016 23:27:12 +0100 [thread overview]
Message-ID: <20161130232712.636daccd@free-electrons.com> (raw)
In-Reply-To: <20161130221053.GA3619@free.fr>
Hello,
On Wed, 30 Nov 2016 23:10:53 +0100, Yann E. MORIN wrote:
> On 2016-11-28 10:45 +0100, Damjan Marion spake thusly:
> > Currently tvheadend configuration is stored in
> > /home/tvheadend/.hts/tvheadend. This patch changes this location
> > to /etc/tvheadend which seems to be more appropriate place.
>
> I disagree. This location is not only about "configuration" but also
> about "state". It contains user-specified settings, recordings, DVB scan
> status...
>
> For example, accesscontrol can be updated from the WebUI to add/remopve
> users or change their rights. I don't remember the full set of stuff
> that gets in there, but there's almost no "configuration", but mostly
> "settings" than can be updated a lot; the most ovious being records (not
> the media streams, but the settings like channel, start and end times...)
>
> Besides, /etc can be read-only, and we need a writable location. And
> /etc is not a correct location to expect to be writable. /home is most
> probably writable by users (although we do not provide that guarantee in
> Buildroot, it is still much better than /etc).
>
> So, it does not belong to /etc.
>
> What was your rationale for moving it, besides "it seems more appropriate" ?
Could we have the configuration in /etc and the state in /var, like most
sane Linux daemons do?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-11-30 22:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 9:45 [Buildroot] [PATCH] package/tvheadend: change configuration directory Damjan Marion
2016-11-28 20:56 ` Thomas Petazzoni
2016-11-30 22:10 ` Yann E. MORIN
2016-11-30 22:27 ` Thomas Petazzoni [this message]
2016-11-30 22:28 ` Damjan Marion
2016-11-30 22:46 ` Thomas Petazzoni
2016-11-30 22:52 ` Damjan Marion
2016-12-01 8:19 ` Thomas Petazzoni
2016-12-01 9:04 ` Damjan Marion
2016-11-30 22:27 ` Damjan Marion
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161130232712.636daccd@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox