From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: ebo@sandien.com, Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9vx patch to read environment var PLAN9
Date: Wed, 14 Apr 2010 23:51:42 +0100 [thread overview]
Message-ID: <EAF05111-899A-463C-8FB6-4C9A3802570D@fastmail.fm> (raw)
In-Reply-To: <twig.1271270284.79955@swcp.com>
On 14 Apr 2010, at 19:38, EBo wrote:
>
>> hardcode your own path and let the next sucker repeat the story
>
> fair enough, and now for the heart of the question that I have been
> dancing
> around all along (actually I thought it was obvious) -- what is the
> best way
> to fix this section of code so that we can be done with it once and
> for all?
> Remove all hard coded paths and require -r and startup from root
> dir? ok.
> add the env variable? ok. do whatever I am going to do and never
> post my
> patches to start another flame drizzle (as compared to an all out
> flame war)?
> So, what's to be done?
Watching yet another 'flame drizzle' (good term, btw) is precisely
what made me grumpy, sorry about that. I get really tired of watching
them but don't do any good when I get involved, so I don't know what
to do really. Perhaps if I only comment if I can think of something
positive.
If I do have a constructive comment on this subject, I can't see any
harm in adding both /usr/local/9vx and /opt/9vx to the hard-coded
paths as these are paths on the host system, not plan 9, and thus
*shouldn't* start up that old debate again. I think /usr/local and /
opt are both commonly used for odd binary trees, P9p being a prime
example with build instructions suggesting /usr/local/plan9 and more
than one Linux distro choosing /opt/plan9.
I'm not so sure about /usr/lib or /usr/share. I'd tolerate both (I've
stopped caring about the unix filesystem hierarchy), but speaking as a
long-time Linux user they don't feel right, especially not /usr/share.
If you do put them in they probably won't draw any trouble as just
hard-coded paths hidden in the source.
Is there any harm in putting in as many hard-coded paths in as might
be reasonable?
--
Simplicity does not precede complexity, but follows it. -- Alan Perlis
next prev parent reply other threads:[~2010-04-14 22:51 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 10:13 [9fans] how about intel D510MO Alex
2010-04-08 3:53 ` John Barham
2010-04-08 13:04 ` erik quanstrom
2010-04-11 17:06 ` [9fans] 9vx patch to read environment var PLAN9 EBo
2010-04-11 17:11 ` erik quanstrom
2010-04-11 17:24 ` Devon H. O'Dell
2010-04-11 17:30 ` erik quanstrom
2010-04-11 17:48 ` Devon H. O'Dell
2010-04-11 17:52 ` erik quanstrom
2010-04-11 21:01 ` [9fans] /sys/lib/newuser patch EBo
2010-04-11 21:48 ` erik quanstrom
2010-04-11 22:04 ` EBo
2010-04-11 23:06 ` Iruata Souza
2010-04-12 3:58 ` EBo
2010-04-11 23:19 ` Anthony Sorace
2010-04-12 3:49 ` EBo
2010-04-12 5:34 ` EBo
2010-04-12 12:28 ` erik quanstrom
2010-04-12 13:13 ` EBo
2010-04-12 13:28 ` hiro
2010-04-12 13:37 ` erik quanstrom
2010-04-12 14:11 ` hiro
2010-04-12 14:35 ` Devon H. O'Dell
2010-04-12 14:40 ` erik quanstrom
2010-04-12 15:01 ` Devon H. O'Dell
2010-04-12 15:28 ` erik quanstrom
2010-04-12 15:08 ` hiro
2010-04-12 15:23 ` hiro
2010-04-13 2:23 ` Anthony Sorace
2010-04-13 2:53 ` EBo
2010-04-13 3:14 ` Anthony Sorace
2010-04-13 3:23 ` EBo
2010-04-13 4:05 ` EBo
2010-04-12 13:38 ` EBo
2010-04-13 13:37 ` maht
2010-04-13 13:59 ` EBo
2010-04-11 18:03 ` [9fans] 9vx patch to read environment var PLAN9 EBo
2010-04-11 17:32 ` EBo
2010-04-11 17:42 ` Devon H. O'Dell
2010-04-11 17:47 ` EBo
2010-04-12 0:43 ` Russ Cox
2010-04-12 3:22 ` EBo
2010-04-12 10:46 ` Francisco J Ballesteros
2010-04-12 11:38 ` EBo
2010-04-12 12:36 ` erik quanstrom
2010-04-13 4:47 ` Skip Tavakkolian
2010-04-13 5:20 ` EBo
2010-04-13 5:43 ` Skip Tavakkolian
[not found] ` <43c85712dd833ad7544f72b7c66a3b2e@9netics.com>
2010-04-13 6:19 ` EBo
2010-04-13 6:33 ` Skip Tavakkolian
2010-04-13 6:47 ` EBo
2010-04-14 16:22 ` Ethan Grammatikidis
2010-04-14 18:10 ` EBo
2010-04-14 18:23 ` Federico G. Benavento
2010-04-14 18:33 ` lucio
2010-04-14 18:38 ` EBo
2010-04-14 22:51 ` Ethan Grammatikidis [this message]
2010-04-15 0:30 ` Patrick Kelly
2010-04-15 4:32 ` Russ Cox
2010-04-15 6:48 ` EBo
2010-04-15 8:26 ` Ethan Grammatikidis
2010-04-15 7:39 ` EBo
2010-04-15 9:22 ` Ethan Grammatikidis
2010-04-15 13:55 ` Devon H. O'Dell
2010-04-15 14:01 ` EBo
2010-04-14 18:36 ` erik quanstrom
2010-04-14 18:50 ` EBo
2010-04-14 18:44 ` Skip Tavakkolian
2010-04-14 19:01 ` EBo
2010-04-15 8:44 ` Balwinder S Dheeman
2010-04-15 10:11 ` Ethan Grammatikidis
2010-04-15 13:06 ` EBo
2010-04-15 14:29 ` Balwinder S Dheeman
2010-04-15 15:38 ` hiro
2010-04-16 7:52 ` Ethan Grammatikidis
2010-04-16 12:08 ` erik quanstrom
2010-04-16 8:20 ` Ethan Grammatikidis
2010-04-16 10:57 ` hiro
2010-04-26 8:43 ` [9fans] how about intel D510MO Pavel Klinkovsky
2010-04-15 16:52 [9fans] 9vx patch to read environment var PLAN9 Chad Brown
2010-04-15 17:03 ` erik quanstrom
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=EAF05111-899A-463C-8FB6-4C9A3802570D@fastmail.fm \
--to=eekee57@fastmail.fm \
--cc=9fans@9fans.net \
--cc=ebo@sandien.com \
/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).