From: Natanael Copa <natanael.copa@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: [gentoo-embedded] init.d scripts and bash
Date: Thu, 08 Mar 2007 17:00:04 +0100 [thread overview]
Message-ID: <1173369604.5480.20.camel@localhost> (raw)
Hi,
Are there anybody more than me that use the gentoo init.d scripts
without using bash?
Most init.d scripts runs just fine with a small runscript wrapper. A few
needs patching to work, typically replacing:
[[ expr || expr ]]
with:
[[ expr ]] || [[ expr ]]
But sometimes arrays and such are used (very often its easy to work
around)
Are there any hope for setting a gentoo policy that says bash specific
things should be avoided if possible in init.d scripts?
Natanael Copa
--
gentoo-embedded@gentoo.org mailing list
next reply other threads:[~2007-03-08 16:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 16:00 Natanael Copa [this message]
2007-03-09 0:00 ` [gentoo-embedded] init.d scripts and bash Ned Ludd
[not found] ` <20070309073937.154cff79@uberpc.marples.name>
2007-03-09 9:08 ` Ned Ludd
2007-03-09 10:06 ` Natanael Copa
2007-03-09 11:51 ` Natanael Copa
[not found] ` <20070309115825.52cd9d73@uberlaptop>
2007-03-09 12:58 ` Natanael Copa
[not found] ` <20070309142717.6373940c@uberlaptop.development.ltl>
2007-03-09 15:12 ` Natanael Copa
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=1173369604.5480.20.camel@localhost \
--to=natanael.copa@gmail.com \
--cc=gentoo-embedded@lists.gentoo.org \
/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