Bruce Ellis wrote:
If you stopped to pick up the penny you'd get hit by lightning and
fail to cash in your lottery ticket while getting bitten by a moose!
But thank god, there would be no collision. I hate getting hit by cars.
Paul
brucee
On Fri, Mar 7, 2008 at 6:45 AM, Paul La
You don't have to care about the chance of a collision. Work out the
expected value of the collision by estimating the maximum that might
cost you. I'll go nuts, and claim that a collision will cost *one
BILLION* dollars.
Not checking for a collision, assuming a 2**-90 collision rate (which is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 3, 2008, at 1:12 AM, Philippe Anel wrote:
So, does this mean the latency is only required by the I/O system
of your program ? If so, maybe I'm wrong, what you need is to be
able to interrupt working cores and I'm afraid libthread doesn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 3, 2008, at 4:49 PM, erik quanstrom wrote:
really? to out-predict the cache hardware, you have to have pretty
complete knowlege of everything running on all cores and be pretty
good at guessing what will want scheduling next. not to mention
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 2, 2008, at 2:00 PM, Philippe Anel wrote:
I agree with you, taking care about memory hierarchy is becoming
very important. Especially if you think about the upcoming NUMAcc
systems (Opterons are already there though).
But the fact is doesn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
CSP doesn't scale very well to hundreds of simultaneously executing
threads (my claim, not, as far as I've found yet, anyone else's). It
is very well suited to a small number of threads that need to
communicate, and as a model of concurrency fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 2, 2008, at 3:12 AM, Charles Forsyth wrote:
C++ is probably the wrong language for the application, then;
it should appear straightforward.
Almost certainly. And so is C. Programming many-core shared-cache
machines in languages with gl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a project on the go that would make an awesome plan9 platform.
Except that all our users code in C++. The complicated kind, with
templates and hideous metaprogramming. And can even show good reason
to do so.
Makes me weep.
Paul
On Ma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Airports. Remote offices. The gap between the wall and the desk.
Hotel rooms.
I'm glad the mice are the only thing I seem to lose this way.
Paul
On 28-Feb-08, at 7:27 AM, Charles Forsyth wrote:
I ordered an extra 5 a couple of years ago whe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I really like Dell's base model optical mouse. Big scroll wheel
that's stiff enough not to roll when I middle-click.
I ordered an extra 5 a couple of years ago when work got me a system
through them; it's almost time to order 5 more.
Paul
On 2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If time is the constraint, then just uninstall all your web browsers,
or just run native plan9.
Paul
On 9-Feb-08, at 2:08 PM, Richard Uhtenwoldt wrote:
Steve Simon writes:
I turn flash off on all the browsers I use, I find it irritating and
s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It's hard to tell what might be wrong with your transformation if you
don't also show the transformation matrix you are using, including
the camera parameters. What you probably want is for your transform
to go from some world space coordinates
What's the largest number of shared-memory cores plan9 has been run on?
I'm guessing the constraint is in fitting all the mach structures in the
appropriate reserved memory space. Are there other constraints?
Paul
textures and vertex
buffers and have a cache on the GPU manage those for me. It's a much
simpler user model than the current myriad ways of setting up
different data types.
Paul
On 10-Nov-07, at 5:12 PM, Joel C. Salomon wrote:
On Nov 10, 2007 6:28 PM, Paul Lalonde <[EMAIL PROTECT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10-Nov-07, at 4:27 PM, Anthony Sorace wrote:
The cheapest ATI card I could find on their website has 128MB of DDR.
The lowest of NVidia's modern line comes with 256MB. Clock speeds are
in the 400Mhz range and go up from there. You can get GPUs pa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I suspect a lot of eyecandy would be easier to implement on
plan9. I have been thinking about openGL on plan9. Has
anyone looked at adding openGL to Plan9?
Disclaimer: I work for Intel, in a graphics group tied closely to
GPUs. All my words a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8-Nov-07, at 5:07 PM, [EMAIL PROTECTED] wrote:
Is it just me or is the whole linux universe stark raving bonkers?
Insular is the word you're looking for.
Paul
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFHM+WCpJeHo/Fbu
I'm trying to run the most recent Plan9 image in a Virtual PC 2007 VM.
The install went flawlessly, but I'm getting write errors, at which time
things just go really bad and the console starts spewing this error
every few seconds:
command 30
data f18d8520 limit f18da520 dlen 8192 status 0 err
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What does it mean when acme-SAC says:
can't fstat /n/c/dev/Users/plalonde/readme: The trust relationship
between this workstation and the primary domain failed?
It failed to find any of my files in /n/c/dev/Users/plalonde, but
didn't generate a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ah, I see the light.
I'll give it a shot :-)
Paul
On Nov 6, 2007, at 10:28 AM, ron minnich wrote:
On 11/6/07, Robert William Fuller <[EMAIL PROTECTED]> wrote:
Paul Lalonde wrote:
On Nov 6, 2007, at 10:29 AM, Robert William Fuller
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 6, 2007, at 10:29 AM, Robert William Fuller wrote:
In UNIX, set up a signal handler for SIGSEGV.
Not quite enough - I still need to reserve some address space. mmap
doesn't let me reserve it without backing it.
Paul
-BEGIN PGP SIG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I connect to my QEMU using drawterm; the mac files show up under /mnt/
term. Drawterm seems to work better, generally, than doing the
graphics on the QEMU side.
Paul
On Nov 6, 2007, at 9:42 AM, Pietro Gagliardi wrote:
Hello. I freed up about 2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have an application I'm building which requires OS support to allow
a user-space function to fill a page on page-faults. Ideally, I
could reserve a chunk of address space but not back it with memory,
and then on fault my handler would serve o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(Sorry to come in late, I've been on the road all week)
One thing about doing this Cocoa port --- I've been reflecting on
this since Leopard was announced as dropping Carbon --- is that we
should probably take the opportunity to build the front-e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It works fine as an editor, but if I understand correctly runs
command lines under the hosted Inferno; is there some way I can set
it up to run windows command line tools? I need to run my compiler...
Paul
On Oct 25, 2007, at 9:00 AM, Iruata S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've just changed employers (now at Intel, Neoptica having been
absorbed late last week), and I'm obliged to work under Windows.
Has anyone made progress getting plan9ports going under cygwin? I'd
rather not live without a real editor, and I'm no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
inferno/plan9 on cell :-(
Too big a project, too little time from me, and me not putting enough
pressure on the student.
Should probably have gone straight to inferno instead of trying to
get the Cell mmu up.
The MMU is coming up now, but there
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If I'm reading brucee correctly, he's cross compiling using kencc but
running natively; there's no "native" compiler involved, just a (very
old-school seeming) loader program and his system-call thunks. Clever.
Paul
On 10-Aug-07, at 6:41 PM, e
On 10-Aug-07, at 3:34 PM, David Leimbach wrote:
I'm sorry to hear it's not well structured.
Less a problem of structure of gsoc than of a mismatch between how
the plan9 community operates, the gsoc expectations, and my over-
expectations. I think Uriel did a great job getting something
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm one of the "guilty" parties regarding plan9-tech. GSOC requires
public communications, but I'm entirely unhappy passing "did you
check bit 11 of the VPN register" level of crap to 9fans - it's
clearly not where it belongs (I believe it belo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(think I (was gorka correct))
On 31-Jul-07, at 7:35 PM, erik quanstrom wrote:
either grouping (well-behaved dogs) and interns or well-behaved (dogs
and interns)
in a rather ambiguous way. Can we bring bad-behaved interns?.
The "and" is redundant i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
That depends on if I already had the mouse in my hand. And which
window has focus. And if the command had a parameter.
Remember: line editing forces higher concentration on the task at hand.
Paul
On Jul 9, 2007, at 3:45 PM, [EMAIL PROTECTED] w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm just annoyed at the repeated fallacy that a pointing tablet &
stylus is better than the mouse. That's only true if the display is
the tablet - absolute position interfaces are very awkward to
navigate with when you're not looking at them.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Control and clover give you 2 more buttons, although I have my
version hacked to use F1-F3 as mouse buttons on my macbook pro. I've
not had any problems with cut-and-paste.
My biggest problem with it is that it doesn't do window-on-top focus
co
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Signed bit field overflow.
You (don't) want "unsigned int botch:1;"
Yuck.
On 5-Jun-07, at 5:36 PM, ron minnich wrote:
/* catch the bug */
struct x {
int botch:1;
};
fun(){
struct x x;
x.botch = 0;
x.botch = 1;
}
ok, what's the bug? anyone?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As I said - my first pass at power64 needed /power64.
But this should be infrequent.
Paul
On May 23, 2007, at 11:49 AM, ron minnich wrote:
On 5/23/07, Fabrizio Colalucci <[EMAIL PROTECTED]> wrote:
Hi all,
I'm a newbie in Plan 9.
My proble
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 23, 2007, at 11:41 AM, Sape Mullender wrote:
1. Why would you want to create a file in the root directory in the
first place?
it's probably not a good place.
I had occasion to do this recently while porting to a new
architecture. In
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Edit r filename
will read filename at the current selection.
Edit .w filename
will write the current selection to filename.
Paul
On May 22, 2007, at 10:48 AM, ISHWAR RATTAN wrote:
If there is a file open (being edited) in acme. I
want to read-in t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm an idjit. cpurc.local gets run *long* before it should try
listening...That would be the *wrong* place to put the aux/listen
commands for your auth server.
ty fgb.
Paul
On 12-May-07, at 9:46 AM, Paul Lalonde wrote:
-BEGI
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm pointing the drawterm at the correct auth/cpu servers, both
p9cpu, and I'm getting a connection.
auth/debug tells me "cannot decrypt ticket1 from auth serve (bad
t.num=0x3a)"
Still digging. I'll be in China soon.
Paul
On 12-May-07, at 1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
No, just the drawterm.
On 12-May-07, at 3:19 AM, Martin Neubauer wrote:
* Paul Lalonde ([EMAIL PROTECTED]) wrote:
[EMAIL PROTECTED] password. I've been unable to find this string
anywhere in my config files anymore, and have rebooted th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
That changed it back, but my password (after a new auth/changeuser
and echo ok>/mnt/keys/plalonde/status) is still rejected.
It's odd that I didn't re-specify authdom: et al. after pulling, yet
it changed.
More digging.
Paul
On 12-May-07, at 1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm getting to add myself into set of people who have botched their
latest pull. But I think I might have done it in a novel way.
When I try to drawterm in I get "?password mismatch with auth
server"; I've reset my password (auth/changeuser), I'v
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 10, 2007, at 10:13 PM, Uriel wrote:
And that problem goes away if people actually puts their damned code
somewhere where people can see it, and they can 1) see it for
themselves 2) try it for themselves 3) fix/finish it by themselves
It's a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Woot. I'm starting to really like Coraid :-)
Now the real question: How do we get Coraid interested in USB 2.0
drivers? ;-)
Paul
On May 10, 2007, at 1:53 PM, erik quanstrom wrote:
coraid is pleased to release an intel ahci driver for the
63x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sometimes I feel illiterate.
Thanks all.
Paul
On May 8, 2007, at 9:31 AM, Russ Cox wrote:
Almost. I was insufficiently specific - I also need to control
placement of the window, in order to have it use up nearly my whole
screen. -W doesn't seem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Almost. I was insufficiently specific - I also need to control
placement of the window, in order to have it use up nearly my whole
screen. -W doesn't seem to handle the extended X11 -geoemtry string: -
geometry 1865x1150+0-0
If that's not ther
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ok, I'm giving up and asking.
I want to start my acme session with a particular geometry. The -l
dump.acme option works great for laying out my columns and guide
file, but doesn't cover the startup geometry of the window, which
means my Holler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 4, 2007, at 2:58 PM, Dave Eckhardt wrote:
One possible goal might be a language in which you could
describe high-level algorithms of a certain class which
could then be compiled to run well on a Cell (and, to be
a cool result, on some other t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been trying to think of ways to evangelize rio and acme. It's a
tough sell - there is no "new user" subset.
In particular, to be at all effective with rio (and especially acme)
you need to be a capable command-line user and understand how to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 4, 2007, at 2:24 AM, C H Forsyth wrote:
if it's on (say) a DSP, it's a bit of a mixture of that and people
thinking that
language design stopped with C, so the language provides too little
scope for a compiler sensibly to do the work.
Th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The right answer is for someone motivated (it won't be me until late
summer, I'm afraid) to take the OS X native drawterm back end and
drop it into p9p. And maybe fix the couple of bugs left in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Autohell is caused by an underlying, much more dangerous problem that
needs to be addressed: the belief that the myriad POSIX derivatives
are somehow "different" systems. The superficial incompatibilities
between the lot of them are addressed b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Typical. I'm in Seattle tomorrow, before the meeting, and in SF the
14th.
But I'll host the Victoria chapter meeting of the P9UG meeting this
saturday evening ;-)
Paul
On 30-Apr-07, at 7:54 PM, Tim Wiess wrote:
i'm thinking it should be on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
From someone who pushes pixels every day:
You almost certainly don't want a pixel-processing framework that
breaks things down to pixels!
Most interesting operations on images require a neighbourhood of
pixels, or even whole-image information. F
ough hoops.
Paul
On 27-Mar-07, at 2:57 PM, ron minnich wrote:
On 3/27/07, Paul Lalonde <[EMAIL PROTECTED]> wrote:
What is the state of our PPC64 compiler?
according to my records, you're doing it :-)
You have a milestone! get busy!
thanks
ron
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I would love to boot Plan9 on my PS3 :-)
I'm pretty sure it would be straightforward given that a linux
already exists to show us how to boot under the LV-1 hypervisor.
What is the state of our PPC64 compiler?
Paul
On 27-Mar-07, at 1:54 PM, Loren
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a hideous little hack in my version of drawterm that turn F1-
F2-F3 into the three mouse buttons to help with using my macbook. It
took some getting used to, but it works. Andrey also added some
support for using the option and apple key
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I looked at this when I did the drawterm back-end.
The basic structure of the implementations is similar, but there's a
fair bit of tweaking required to move the drawterm back end to P9P.
I hacked at it a bit and ran out of time; there's nothing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The less cynical part of me says that windows got so huge through the
usual process by which software gets huge: hiring.
It's really easy to believe you need more manpower on your software
project. That eventually leads to dividing your now-unman
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Preaching to the choir (I hope):
The fundamental issue with the GUI isn't one of prettiness. It's one
of naive/novice use. Like the rest of Plan9, the GUI assumes an
expert user. But ever since t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I get a pretty regular p9p acme crash on my linux box (from using win
for other things than a terminal):
Feb 20 11:56:09.507 write error: Broken pipe
9pserve: 9pserve.c:578: connthread: Assertion `c-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The flush after each separate pass is run on each file? That would
be my first guess.
But this is all theoretical - I've not stopped to actually measure
the thing.
Paul
On 14-Feb-07, at 6:34 AM, erik quanstrom wrote:
i wouldn't think so.
eb-07, at 6:13 AM, ron minnich wrote:
On 2/14/07, Paul Lalonde <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Without kqemu, qemu uses dynamic translation/jit compilation to
emulate the target architecture.
Right. So once you get a bit of jit compiled you're
advantage there.
Paul
On 13-Feb-07, at 8:42 PM, ron minnich wrote:
On 2/13/07, Paul Lalonde <[EMAIL PROTECTED]> wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
IIRC, without kqemu, qemu does actual per-instruction emulation, even
if running on the same platform.
well, from my reading, t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
IIRC, without kqemu, qemu does actual per-instruction emulation, even
if running on the same platform.
15:1 is actually pretty impressive!
Paul
On 13-Feb-07, at 7:10 PM, ron minnich wrote:
this is qemu without kqemu, since I have had problems w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5-Feb-07, at 11:52 AM, Joel Salomon wrote:
Maybe if someone needs/wants to implement a language
with a built-in string type…
That's crazy-talk.
;-)
Paul
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (Darwin)
iD8DBQFFx6SrpJeHo/Fbu1wRAh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Really that should be "net!¢¢smtp!smtp"
But that's just my two cents.
On 15-Jan-07, at 11:28 AM, erik quanstrom wrote:
'$' seems like an unfortunately choice for dial strings because
it is easy to confuse with a shell/environment variable.
perhaps
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sweet! I never saw that option! Thanks!
On 13-Jan-07, at 10:36 AM, Gregory Pavelcak wrote:
You need to select "Save As" from the AppleScript editor and
save your script as an application instead of a script.
Greg
How do I use this to be able
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have it installed in the AppleScript menu - dropping it into
application format is a pain; I'll see if I can't track it down this
evening.
Paul
On 13-Jan-07, at 10:26 AM, Brantley Coile wrote:
How do I use this to be able to click
on an ico
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have an AppleScript command that contains the single line:
do shell script "/Users/plalonde/bin/drawterm -a p9cpu -c p9cpu"
On 13-Jan-07, at 6:44 AM, Gregory Pavelcak wrote:
OK, this may be the h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Which was the reason for the original cast to 16 bits :-(
What gets reported in the case of the mice that were overflowing?
Paul
On 12-Jan-07, at 12:44 PM, David Leimbach wrote:
On 1/12/07, andrey mirtchovski <[EMAIL PROTECTED]> wrote:
i fixed th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The real question is if we can get iPhone to replace Bitsy :-)
On 12-Jan-07, at 11:33 AM, Steve Simon wrote:
Nice for you (grump), still wishing for Win-Fuse,
or even better Win-9p.
There is MS technology to do this (IFS) but, when I started
to lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The P9P version of acme has had multi-line tags for a while now, but
there is still a "bug" lurking in the implementation; it's a bit of a
semantic issue with allocating lines of pixels to the various
windows, which I'll get to below. The bug m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The nice folks at google keep doing us favours (sort of...), this
time with an OS X port of Fuse:
http://googlemac.blogspot.com/2007/01/taming-mac-os-x-file-systems.html
Do we have a user space 9p-to-Fuse bridge anywhere?
Paul
-BEGIN PGP SIG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I believe a change to gui-osx/screen.c 73 minutes ago fixes this;
Please let me know if it doesn't and I'll track down a mouse to
reproduce it.
Paul
On 12-Jan-07, at 10:31 AM, David Leimbach wrote:
On 1/12/07, Skip Tavakkolian <[EMAIL PROTECT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm running it on my MBP just fine; I'll try it on my mini when I get
back to Victoria.
Paul
On 10-Jan-07, at 8:07 AM, David Leimbach wrote:
On 1/10/07, Skip Tavakkolian <[EMAIL PROTECTED]> wrote:
> Paul got the native OS X graphics code worki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There's already a bug fix in (Thanks Charles), where I missed the
qlock around flushmemscreen - you might want to wait until it shows
up in cvs before distributing an executable.
Paul
On 9-Jan-07, at 4:58 PM, andrey mirtchovski wrote:
i just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I might add that I witnessed a crash bug today (first in several days
of use); of course I didn't have OS X set to generate a core dump. Grr.
I'll happily accept core dumps :-)
Paul
On 9-Jan-07, at 2:22 PM, Russ Cox wrote:
Any update here?
P
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It certainly is reactionary.
"Hateful in the eyes of God" is how I've come to see it.
On 5-Jan-07, at 9:44 AM, [EMAIL PROTECTED] wrote:
I believe the intent was to force indentation to match block
st
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Guess people are not used to thinking about systems that don't have
error numbers :-)
Err, no.
ron
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFFjfRDpJeHo/Fbu1wRAkbqAKCoXqWvyH+vAZuMDmmR9CWGVqAYAwCfUAHk
yZE/YM2gkNlfKEuJ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I just backed up my VM and gave it a shot. I confirm that
behaviour. Yikes.
On 21-Dec-06, at 4:53 PM, Dan Cross wrote:
Uh, I just ran pull and it deleted nearly every file on my system;
something
tells me this is not normal. Anyone else jus
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
That said, I have vague recollections of adding bootes to the adm
group - I don't recall if that is in the wiki.
Paul
On 21-Dec-06, at 1:49 PM, John Floren wrote:
On 12/21/06, Paul Lalonde <[EMAIL PROTECTED]> wrote:
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As a data point, I followed the cpu/auth server instructions about 2
weeks ago with complete success, and got a server running in a
Parallels machine quite easily (thanks to David Leimbach's patches).
Paul
On 21-Dec-06, at 1:31 PM, John Floren
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yowza. Someone slipped something into Ron's coffee!
Ron - any chance of the /dev/fb based drawterm making its way to more
general distribution?
Thanks,
Paul
On 20-Dec-06, at 2:19 PM, ron minnich wrote:
It is called JD for a reason ...
a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
That doesn't match blank lines.
g/^/m0
On 17-Dec-06, at 8:41 AM, Rob Pike wrote:
why would moving everything as a block reverse it?
try
g/./m0
-rob
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFFhXh/pJeHo/Fbu1wRArvKAKCOx
it into a CPU server.
Paul
On 12-Dec-06, at 4:33 PM, David Leimbach wrote:
keep in mind that the source that runs well on parallels is not the
same as the source on sources. I don't know if the BIOS changes JMK
did ever got merged in.
Dave
On 12/12/06, Paul Lalonde <[EMAIL PROTECTED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been following David Leimbach's directions on getting plan9 to
run under parallels, and have run into a glitch while rebuilding the
kernel. At link I get:
configure: undefined: pcibussize in configure
Any quick clues as to what's up? It's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Victoria, BC might be possible; but that's a lot of timezones for our
european friends.
Paul
On 11-Dec-06, at 7:22 PM, ron minnich wrote:
is canada easier for people? toronto or even somewhere really cool
like newfoundland?
ron
-BEGIN PG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ham, beer, wine, and arguments ;-) All the best bits were there!
A big thank-you to the organizers, and to Gorka especially for
finding a restaurant to seat 30 on short notice.
Fabulous to meet you all.
And Uriel - g/^/m0 is the best I've manag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm soon to be Madrid-bound. Is there anyone kicking about being a
tourist on Sunday who'd like to get together? I was thinking of
spending a couple of hours in the Prado in the morning, and the
afternoon discovering local food and beverage.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm fed up with having to use an ugly GUI for running perforce, and
I've just realized that a synthetic file system interface to it would
let me automate a lot of my acme-side connection to it, reasonably
cleanly.
On plan9 I'd just crib one of t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
But that's good style - if he changes the fundamental theme, he can
fix it in just one place!
On 14-Nov-06, at 11:14 AM, Sape Mullender wrote:
shoenberg's "Style and Idea" is a good reference.
he had lots of both, and knew how to distill them.
n
On 14-Nov-06, at 8:39 AM, elbing wrote:Of course, if you drink DYC with Bruce, you won't need Taj Mahal when sleep time comes. Although, given that the Taj Mahal is a mausoleum, that might be more appropriate than the hotel!Ahm, about spanish beer: it has too much CO2 (heh).2006/11/14, Gorka guardi
"Ear to the floor"? That sounds like it's for later in the evening!On 14-Nov-06, at 7:07 AM, elbing wrote:You can drink spanish whisky too (be carefull). Try "oreja a la plancha" too.2006/11/14, Paul Lalonde <[EMAIL PROTECTED]>: -BEGIN PGP SIGNED MESSAGE-Has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14-Nov-06, at 1:26 AM, Bruce Ellis wrote:
i'll be in madrid for a week. others will be. we should collaborate
glenda strangers speaking bad spanish (e.g. me).
i can't hang out too much longer, i have to preside my sister's
wedding, and a day
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 13-Nov-06, at 3:06 PM, David Leimbach wrote:
Not this year sadly. I still have the glenda tatoos from last
year's though :-)
That's the thing about tattoos, there's a kind of permanence. At
least it's not particularly embarrassing expla
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Looking at this briefly, I discovered that the p9p version of acme
doesn't make available body/addr/ctl/event of the current selected
window. So the straightforward "substitute 9p commands" fails.
What is the correct way for a script to discove
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 30-Oct-06, at 7:16 AM, Russ Cox wrote:
Say...Does anyone know of a patch for OS X that
makes chording work? Then I could bind to copy and paste properly.
See #define chording in
http://swtch.com/usr/local/plan9/src/cmd/samterm/main.c
That wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Because some people like the tag/command line per window (acme) and
others like the single command window (sam)?
I occasionally use sam as a stream editor, but I couldn't imagine
doing all my work in it. The cut and paste mechanic feels so awkw
1 - 100 of 216 matches
Mail list logo
