From: Wade Berrier <wberrier@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/vsftpd
Date: Tue, 07 Oct 2008 09:52:09 -0600 [thread overview]
Message-ID: <gcg0k4$7ap$1@ger.gmane.org> (raw)
In-Reply-To: 20081007055134.GF5127@cloud.net.au
Hamish Moffatt wrote:
> On Mon, Oct 06, 2008 at 03:46:41PM -0700,
> wberrier at uclibc.org wrote:
>> Added: trunk/buildroot/package/vsftpd/vsftpd-init
>> ===================================================================
>> --- trunk/buildroot/package/vsftpd/vsftpd-init
>> (rev 0)
>> +++ trunk/buildroot/package/vsftpd/vsftpd-init 2008-10-06 22:46:41 UTC
>> (rev 23611)
>
> Too bad this can't be disabled - as soon as this package is installed
> the init script will be run on boot. Some users may not want this.
Really? I would think if users didn't want it started they wouldn't include
it in their config.
I see config/init handled a bit differently in different projects. Is there
no set standard?
It seems convenient to have a default config set up and installed. That way
not everyone has to write their own custom config and init scripts. And
for those who want a custom config, it should be easily allowable to
integrate custom configs. I like how samba does it:
$(INSTALL) -m 0755 package/samba/S91smb $(TARGET_DIR)/etc/init.d
@if [ ! -f $(TARGET_DIR)/etc/samba/smb.conf ]; then \
$(INSTALL) -m 0755 -D package/samba/simple.conf
$(TARGET_DIR)/etc/samba/smb.conf; \
fi
It installs a base sample config, unless a user has a custom config already
in $(TARGET_DIR).
Opinions? Feedback?
I imagine that most people run into this same issue with their projects.
Or, how is everyone else solving this issue?
Wade
next prev parent reply other threads:[~2008-10-07 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 22:46 [Buildroot] svn commit: trunk/buildroot/package/vsftpd wberrier at uclibc.org
2008-10-07 5:51 ` Hamish Moffatt
2008-10-07 15:52 ` Wade Berrier [this message]
2008-10-07 23:20 ` Hamish Moffatt
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='gcg0k4$7ap$1@ger.gmane.org' \
--to=wberrier@gmail.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