From: "Russ Cox" <rsc@swtch.com>
To: 9fans@9fans.net
Subject: Re: [9fans] 9vx and local file systems
Date: Wed, 23 Jul 2008 13:51:58 -0400 [thread overview]
Message-ID: <20080723174936.CA1F71E8C1F@holo.morphisms.net> (raw)
In-Reply-To: <072320081440.1316.488742E0000663F50000052422243651029B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net>
> I'm doing all of this on Linux. Since then, I have seen
> it lock up when running from a fossil/venti root and #Z
> not bound. I can't support it with statistics, but my gut
> reaction is that it's less often though.
If this happens again, then running "thread apply all where 20"
in gdb should help determine what's going on.
> 9vx read a plan9.ini file. So I've been folding 9load's
> ini file reader into 9vx. This is not so much massaging
> as with part.c, but liposuction.
I would be inclined to do away with full plan9.ini
parsing and just read a file containing
name=value
lines that get stuffed immediately into the config
environment (ksetenv). Or just pass a couple
name=value pairs on the command line.
Allowing the plan9.ini disease to spread seems
like a lose.
Russ
next prev parent reply other threads:[~2008-07-23 17:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 18:22 Brian L. Stuart
2008-07-18 20:39 ` Russ Cox
2008-07-18 20:55 ` Charles Forsyth
2008-07-18 20:55 ` Charles Forsyth
2008-07-18 20:50 ` Sape Mullender
2008-07-18 22:10 ` Brian L. Stuart
2008-07-20 7:53 ` Russ Cox
2008-07-23 14:40 ` Brian L. Stuart
2008-07-23 17:51 ` Russ Cox [this message]
2008-07-23 18:50 ` Brian L. Stuart
2008-07-24 19:14 ` Brian L. Stuart
[not found] ` <1cb06bb5ba32c2070a940af01f4d91c3@plan9.bell-labs.com>
2008-07-24 19:24 ` Brian L. Stuart
2008-07-24 19:26 ` David Leimbach
2008-07-24 23:23 ` Francisco J Ballesteros
[not found] <071820081822.3544.4880DF75000734D900000DD822218675169B0A02D2089B>
2008-07-18 19:00 ` erik quanstrom
2008-07-18 19:50 ` Roman V. Shaposhnik
2008-07-18 20:20 ` erik quanstrom
2008-07-18 20:28 ` ron minnich
2008-07-19 1:31 ` erik quanstrom
2008-07-19 2:10 ` ron minnich
2008-07-19 2:37 ` Russ Cox
2008-07-18 20:31 ` Russ Cox
2008-07-18 21:55 ` Francisco J Ballesteros
2008-07-18 20:35 ` Russ Cox
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=20080723174936.CA1F71E8C1F@holo.morphisms.net \
--to=rsc@swtch.com \
--cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).