From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] How to move to rc from sh/bash
Date: Mon, 11 Feb 2008 10:04:25 -0500 [thread overview]
Message-ID: <e7087fd0361a6bfd326ceb424b66f8d0@quanstro.net> (raw)
In-Reply-To: <20080210181244.GA801@shodan.homeunix.net>
> Well, that isn't so much about rc's advantages. Keep in mind though that
> this would force getflags to be present whenever you need a shell script.
> For most installations this isn't an issue, but for those running Plan 9
> embedded it is. And with space constraints providing some of /rc/bin might
> be reasonable, providing aux/getflags might not.
i don't buy this argument. if you're running plan 9 with rc & scripts, you
have many MB of ram and mmu and several MB of persistant storage.
it's hard to get small flash parts these days. i can't see 64k mattering.
> Besides, if a script
> doesn't use more than two or three different options getflags doesn't reduce
> much complexity (if you aren't writing a new script). And concerning speed,
> if command line parsing dominates the execution time I honestly wouldn't
> bother.
i would think that the reason to do this would be for consistency. i
don't know that that's a compelling argument. but i can see the
attraction of all or nothing; it would be nice if either none of the
scripts used getflags or all of them did.
- erik
next prev parent reply other threads:[~2008-02-11 15:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 7:53 Hongzheng Wang
2008-02-09 8:01 ` mattmobile
2008-02-09 8:41 ` Hongzheng Wang
2008-02-09 8:57 ` mattmobile
2008-02-09 9:00 ` erik quanstrom
2008-02-09 9:21 ` Hongzheng Wang
2008-02-09 10:11 ` Charles Forsyth
2008-02-09 10:27 ` Lluís Batlle
2008-02-09 15:06 ` Uriel
2008-02-09 17:54 ` Charles Forsyth
2008-02-09 21:59 ` geoff
2008-02-09 13:00 ` Anthony Sorace
2008-02-10 16:59 ` Gorka Guardiola
2008-02-10 17:16 ` Pietro Gagliardi
2008-02-10 17:47 ` erik quanstrom
2008-02-10 18:12 ` Martin Neubauer
2008-02-11 15:04 ` erik quanstrom [this message]
2008-02-11 23:03 ` Martin Neubauer
2008-02-11 23:25 ` Pietro Gagliardi
2008-02-20 15:04 ` maht
2008-02-20 15:08 ` Federico G. Benavento
2008-02-20 15:24 ` erik quanstrom
2008-02-20 15:55 ` maht
2008-02-11 23:59 ` Uriel
2008-02-12 11:57 ` Martin Neubauer
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=e7087fd0361a6bfd326ceb424b66f8d0@quanstro.net \
--to=quanstro@quanstro.net \
--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).