From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Machine-specific cpurc customisation?
Date: Wed, 15 Oct 2003 11:51:33 +0200 [thread overview]
Message-ID: <1a00bd74118a0aacdc816bb3158aa117@plan9.escet.urjc.es> (raw)
In-Reply-To: <3F8CF3BF.5040306@ajft.org>
We ended up with machine specific config to be run
before most of /rc/bin/*rc in some cases, and after
most of /rc/bin/*rc in other cases, sic.
The config to be run before is for those machines where
we need specific ipconfig lines, and the one to be run after
is for those machines where particular programs should run
after all of cpurc, sic.
What about doing something like this?
/sys/lib/sys/config/machine/rc:
fn before() { blah blah }
fn after() { blah blah }
/rc/bin/termrc
test -e /env/fn#before && before
blah blah
test -e /env/fn#after && after
I just don't know of a cleaner solution, and, as probably
happen to you, I'm scared of facing toward the atrocity of
sys-v rc scripts.
next prev parent reply other threads:[~2003-10-15 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 7:14 Adrian Tritschler
2003-10-15 9:51 ` Fco.J.Ballesteros [this message]
2003-10-15 10:13 ` Charles Forsyth
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=1a00bd74118a0aacdc816bb3158aa117@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).