9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] 9grid
Date: Fri, 14 Nov 2008 08:53:05 -0500	[thread overview]
Message-ID: <3b07210f0a4d57d7bd32955ed08af27e@coraid.com> (raw)
In-Reply-To: <1c363208-d3c4-4e4a-8215-bc324c4f65ce@35g2000pry.googlegroups.com>

On Fri Nov 14 04:48:04 EST 2008, torsbohn@gmail.com wrote:
> On Nov 13, 8:45 am, quans...@quanstro.net (erik quanstrom) wrote:
> ...
> > cpu -h node -c 'name=`{cat ''#c/sysname''}; echo do something with $name'
>
>
> I added 'role=cpu' to my cpu servers in /lib/ndb/local, now I can do
> this
>
> for (node in `{ndb/query -a role cpu sys})
>   cpu -h $node -c 'name=`{cat ''#c/sysname''}; echo do something with
> $name'
>
>
> torsbohn - Nothing can stop Tor!

not sure what the deal with these emails is.
they're not from gmail and they contain
invalid quoted-printable, which is why things
look so bad.

i've got a patch for upas/fs that i'll put up shortly.
but you may just want to apply this yourself since
you're probablly not running nupas:

mbox.c:/^hex2int should change:

static int
hex2int(int x)
{
	if(x >= '0' && x <= '9')
		return x - '0';
	if(x >= 'A' && x <= 'F')
		return x - 'A' + 10;
	if(x >= 'a' && x <= 'f')
		return x - 'a' + 10;
	return -1;
}

then :/^decquotedline should have the case '='
changed like so

		case '=':
			c = hex2int(*in++)<<4;
			c |= hex2int(*in++);
			if(c != -1)
				*out++ = c;
			else{
				*out++ = '=';
				in -= 2;
			}
			break;

- erik



  reply	other threads:[~2008-11-14 13:53 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-13 15:43 erik quanstrom
2008-11-13 17:06 ` lupin636
2008-11-13 17:24   ` andrey mirtchovski
2008-11-13 17:26     ` erik quanstrom
2008-11-14  9:44     ` lupin636
2008-11-14  9:44 ` torsbohn
2008-11-14 13:53   ` erik quanstrom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-11-17 14:14 erik quanstrom
2008-11-17 16:22 ` lupin636
2008-11-14 12:23 erik quanstrom
2008-11-14 15:10 ` lupin636
2008-11-17 10:12 ` lupin636
2008-11-17 11:54   ` erik quanstrom
2008-11-17 14:13   ` lupin636
2008-11-11 12:09 erik quanstrom
2008-11-11 13:18 ` lupin636
2008-11-11 14:42   ` john
2008-11-11 15:12   ` lupin636
2008-11-11 15:40     ` Uriel
2008-11-11 16:32     ` lupin636
2008-11-11 17:14       ` Uriel
2008-11-12  0:13     ` ron minnich
2008-11-12  0:11       ` erik quanstrom
2008-11-12  0:41         ` ron minnich
2008-11-12  0:36           ` erik quanstrom
2008-11-12  0:59             ` ron minnich
2008-11-12 10:27     ` lupin636
2008-11-12 14:38       ` john
2008-11-12 16:16       ` lupin636
2008-11-13 12:08       ` lupin636
2008-11-13 12:28         ` erik quanstrom
2008-11-13 15:32         ` lupin636
2008-11-10 18:38 erik quanstrom
2008-11-11  9:50 ` lupin636
2008-11-10 11:35 erik quanstrom
2008-11-10 14:13 ` lupin636
2008-11-10 17:35 ` lupin636
2008-11-10 17:46   ` ron minnich
2008-11-11  9:50   ` lupin636
2008-11-10  9:56 lupin636
2005-06-09  2:17 YAMANASHI Takeshi
2005-06-09  2:28 ` andrey mirtchovski
2005-06-09  1:41 andrey mirtchovski
2005-06-09  1:27 YAMANASHI Takeshi
2005-06-09  3:01 ` Ronald G. Minnich
2005-06-08 14:14 Steve Simon
2005-06-08 15:16 ` Russ Cox
2005-06-08 20:55 ` arisawa

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=3b07210f0a4d57d7bd32955ed08af27e@coraid.com \
    --to=quanstro@coraid.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).