wrote:
> > If the local machine crashes or an application program exits without
> > issuing the close system call, it is possible that
> > the modifications are not recorded in the central copy of the file
> > maintained by the File Server.
>
> I'm confused. UNIX applications can't exit without issuing the
> close system call. The exit system call internally calls out
> to close for each open file. Unless some numskull changed it
> since the last time I had my fingers in it. (They've had plenty
> of opportunity -- I haven't touched a non-BSD UNIX kernel in many
> years.)
Not bloody likely. _Many_ applications exit without calling close(), so
such system would die horribly under the leaks. OTOH... name a perversion
and somebody will find a place where it had been implemented.
From 9fans@cse.psu.edu Tue Nov 14 22:41:13 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Tue, 14 Nov 2000 23:41:13 +0100
Subject: [9fans] AFS-client for Plan9 - ?
References: <20001113201911.6003E199EB@mail.cse.psu.edu> <8ur18f$11jj$2@pandora.alkar.net> <10011141433.ZM1200345@marvin>
Message-ID: <01d501c04e8c$030326a0$0ab9c6d4@cybercable.fr>
From: Tom Duff
> Unless some numskull changed it since the last time
sadly you're probably right -- between the sheets.
From 9fans@cse.psu.edu Tue Nov 14 22:51:12 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Tue, 14 Nov 2000 23:51:12 +0100
Subject: [9fans] AFS-client for Plan9 - ?
References:
Message-ID: <01db01c04e8d$692a29a0$0ab9c6d4@cybercable.fr>
From: Alexander Viro
> Not bloody likely. _Many_ applications exit without calling close
here we go. the kernel closes the fd's as a part of exit,
like td said.
duff knows what he's doing -- between the sheets.
you wanna outcode duff?
From td@pixar.com Tue Nov 14 23:00:34 2000
From: td@pixar.com (Tom Duff)
Date: Tue, 14 Nov 2000 15:00:34 -0800
Subject: [9fans] AFS-client for Plan9 - ?
In-Reply-To: Alexander Viro
"Re: [9fans] AFS-client for Plan9 - ?" (Nov 14, 5:41pm)
References:
Message-ID: <10011141500.ZM1198342@marvin>
On Nov 14, 5:41pm, Alexander Viro wrote:
> On Tue, 14 Nov 2000, Tom Duff wrote:
> > UNIX applications can't exit without issuing the
> > close system call. The exit system call internally calls out
> > to close for each open file.
>
> Not bloody likely. _Many_ applications exit without calling close(), so
> such system would die horribly under the leaks.
No.
Read what I said.
The exit system call closes all open files.
You cannot exit without closing. (By `cannot'
I do not mean that you are enjoined from so
doing, but rather that it is not possible to
do so.)
You can, however, exit without fclosing, although
the stdio library tries to make that difficult.
--
Tom Duff. I spent an interesting evening recently with a grain of salt.
From td@pixar.com Tue Nov 14 23:02:20 2000
From: td@pixar.com (Tom Duff)
Date: Tue, 14 Nov 2000 15:02:20 -0800
Subject: [9fans] AFS-client for Plan9 - ?
In-Reply-To: "Boyd Roberts"
"Re: [9fans] AFS-client for Plan9 - ?" (Nov 14, 11:51pm)
References:
<01db01c04e8d$692a29a0$0ab9c6d4@cybercable.fr>
Message-ID: <10011141502.ZM1199788@marvin>
On Nov 14, 11:51pm, Boyd Roberts wrote:
> duff knows what he's doing -- between the sheets.
>
> you wanna outcode duff?
I am sitting in my workshop reading this,
and now my head won't fit through the door.
--
Tom Duff. I spent an interesting evening recently with a grain of salt.
From 9fans@cse.psu.edu Tue Nov 14 23:15:13 2000
From: 9fans@cse.psu.edu (Alexander Viro)
Date: Tue, 14 Nov 2000 18:15:13 -0500 (EST)
Subject: [9fans] AFS-client for Plan9 - ?
In-Reply-To: <10011141500.ZM1198342@marvin>
Message-ID:
On Tue, 14 Nov 2000, Tom Duff wrote:
> On Nov 14, 5:41pm, Alexander Viro wrote:
> > On Tue, 14 Nov 2000, Tom Duff wrote:
> > > UNIX applications can't exit without issuing the
> > > close system call. The exit system call internally calls out
> > > to close for each open file.
> >
> > Not bloody likely. _Many_ applications exit without calling close(), so
> > such system would die horribly under the leaks.
>
> No.
> Read what I said.
Erm... Ditto.
> The exit system call closes all open files.
Precisely. And any kernel that will try _not_ to do that will die under the
leaks produced by the $BIGNUM of applications expecting it do act as any
sane UNIX should. Thus "not bloody likely" - any attempt to change the
behaviour in that area is pretty much doomed.
From 9fans@cse.psu.edu Tue Nov 14 23:36:53 2000
From: 9fans@cse.psu.edu (Ish Rattan)
Date: Tue, 14 Nov 2000 18:36:53 -0500 (EST)
Subject: [9fans] Multiprocessor system..
Message-ID:
I just changed the motherboard of a cpu+terminal machine to
one that has two PIII cpus. What to change in plan9.ini so that
it can use both cpus? Is there a command display the number of
cpus being used?
- ishwar
From td@pixar.com Tue Nov 14 23:54:53 2000
From: td@pixar.com (Tom Duff)
Date: Tue, 14 Nov 2000 15:54:53 -0800
Subject: [9fans] AFS-client for Plan9 - ?
In-Reply-To: Alexander Viro
"Re: [9fans] AFS-client for Plan9 - ?" (Nov 14, 6:15pm)
References:
Message-ID: <10011141554.ZM1200618@marvin>
> Precisely. And any kernel that will try _not_ to do that will die under the
> leaks produced by the $BIGNUM of applications expecting it do act as any
> sane UNIX should.
Which UNIX version lacks this behavior?
(Or are you trying to run UNIX programs
on some non-UNIX?)
--
Tom Duff. I spent an interesting evening recently with a grain of salt.
From 9fans@cse.psu.edu Tue Nov 14 23:57:10 2000
From: 9fans@cse.psu.edu (David Gordon Hogan)
Date: Tue, 14 Nov 2000 18:57:10 -0500
Subject: [9fans] AFS-client for Plan9 - ?
Message-ID: <20001114235716.EA2CB199FF@mail.cse.psu.edu>
> > Precisely. And any kernel that will try _not_ to do that will die under the
> > leaks produced by the $BIGNUM of applications expecting it do act as any
> > sane UNIX should.
> Which UNIX version lacks this behavior?
> (Or are you trying to run UNIX programs
> on some non-UNIX?)
The hypothetical one positted earlier in this thread.
Sorry to butt in, but this is just getting riddiculous.
From cnielsen@pobox.com Tue Nov 14 23:57:44 2000
From: cnielsen@pobox.com (Christopher Nielsen)
Date: Tue, 14 Nov 2000 15:57:44 -0800 (PST)
Subject: [9fans] Multiprocessor system..
In-Reply-To:
Message-ID:
On Tue, 14 Nov 2000, Ish Rattan wrote:
> I just changed the motherboard of a cpu+terminal machine
> to one that has two PIII cpus. What to change in
> plan9.ini so that it can use both cpus? Is there a
> command display the number of cpus being used?
remove the line that begins:
*nomp
--
Christopher Nielsen
cnielsen@pobox.com
From 9fans@cse.psu.edu Wed Nov 15 00:31:13 2000
From: 9fans@cse.psu.edu (Alexander Viro)
Date: Tue, 14 Nov 2000 19:31:13 -0500 (EST)
Subject: [9fans] AFS-client for Plan9 - ?
In-Reply-To: <10011141554.ZM1200618@marvin>
Message-ID:
On Tue, 14 Nov 2000, Tom Duff wrote:
> > Precisely. And any kernel that will try _not_ to do that will die under the
> > leaks produced by the $BIGNUM of applications expecting it do act as any
> > sane UNIX should.
> Which UNIX version lacks this behavior?
> (Or are you trying to run UNIX programs
> on some non-UNIX?)
Grr... OK, let me rephrase it:
I really doubt that there is (or ever was) a UNIX variant that
would not do close-on-exit. Reason: lots and lots of programs that would
kill such system with file leaks.
IOW, "not likely" was about "some numskull changed it" part - such attempt
would backfire immediately. We are in violent agreement...
From 9fans@cse.psu.edu Wed Nov 15 00:38:12 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Wed, 15 Nov 2000 01:38:12 +0100
Subject: [9fans] AFS-client for Plan9 - ?
References:
Message-ID: <020101c04e9c$5ad8db80$0ab9c6d4@cybercable.fr>
From: Alexander Viro
> IOW, "not likely" was about "some numskull changed it" part - such attempt
> would backfire immediately. We are in violent agreement...
if some 'numskull' would stand up and call bullshit on dat
the world world would be a better place.
tell me why the BSD f/S was written?
quadratic rehash -- give me a break.
From 9fans@cse.psu.edu Tue Nov 14 22:43:12 2000
From: 9fans@cse.psu.edu (kim kubik)
Date: Tue, 14 Nov 2000 14:43:12 -0800
Subject: [9fans] %DVIPSPage
Message-ID: <01c04e8c$454658c0$86ccefd1@pkwksj.sjna.corp.dom>
-----Original Message-----
From: Russ Cox
To: 9fans@cse.psu.edu <9fans@cse.psu.edu>
Date: Thursday, November 09, 2000 11:49 AM
Subject: [9fans] %DVIPSPage
>if you do
> dvips -Ppsfonts foo.dvi > foo.ps
>or dvips -Pbitmapfonts foo.dvi > foo.ps
>then you get nice %%Page: boundaries,
>but if you do
> dvips foo.dvi >foo.ps
>or dvips -Pps foo.dvi >foo.ps
>you get this weird %DVIPS stuff.
>
-------------------------
can't help with the dvips stuff (hell, I
almost still need help tying my shoes!) but
Rokicki's web page (and email) is at:
www.radicaleye.com
and he's usually interested in anything that
might be considered a bug in dvips, so altho I'm
sure he's more than busy, he may have a suggestion.
- kim
From 9fans@cse.psu.edu Wed Nov 15 02:20:47 2000
From: 9fans@cse.psu.edu (Russ Cox)
Date: Tue, 14 Nov 2000 21:20:47 -0500
Subject: [9fans] %DVIPSPage
Message-ID: <20001115022049.27937199E6@mail.cse.psu.edu>
I did what I should have done long ago:
type DVIPSSectionPage into google.
It appears that when dvips infers that the printer
would otherwise run out of memory, it breaks the
file into independent sections, and drops the %%Page
comments because the file is no longer DSC compliant.
The default postscript printer configuration apparently
is for 150k.
I've changed /sys/lib/texmf/dvips/config/config.ps
from saying "m 150000" to "m 10000000", which should
fix the problem, in all the printers.
Russ
From 9fans@cse.psu.edu Wed Nov 15 02:24:03 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Wed, 15 Nov 2000 03:24:03 +0100
Subject: [9fans] %DVIPSPage
References: <20001115022049.27937199E6@mail.cse.psu.edu>
Message-ID: <024c01c04eab$249fcb00$0ab9c6d4@cybercable.fr>
russ, you should not know that and you have my sympathies.
From 9fans@cse.psu.edu Wed Nov 15 05:01:00 2000
From: 9fans@cse.psu.edu (Steve Kotsopoulos)
Date: Wed, 15 Nov 2000 00:01:00 -0500
Subject: [9fans] [reminder] pointer to Plan 9 FAQ
Message-ID: <200011150501.AAA01941@smtp.fywss.com>
The Plan 9 faq is posted to comp.os.plan9 at the beginning of each month.
It is also at news.answers archive sites, look for comp-os/plan9-faq
The latest hypertext version of the faq is available at url
http://www.fywss.com/plan9/plan9faq.html
From 9fans@cse.psu.edu Wed Nov 15 08:10:15 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Wed, 15 Nov 2000 08:10:15 0000
Subject: [9fans] AFS-client for Plan9 - ?
Message-ID:
This is a multi-part message in MIME format.
--upas-kxfvdpzzatzirclffacicwhbmt
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Let me explain (and, yes, this is a quote from Fawlty Towers)
Programs which do not explicitly close flies before invoking exit() are
not
1) badly written
or
2) forcing Unix implementations to have to do close on exit to compensate
These are the defined semantics. So the reason is "because that's what
the program quite reasonably expects".
Just in the same way that you don't have to free all memory before
calling exit, unless, as in td's words "they've changed that since I
last looked". I know "they" did for 16 bit Windows applications, and
it's certainly the case for semaphores in Unix.
> Grr... OK, let me rephrase it:
>
> I really doubt that there is (or ever was) a UNIX variant that
> would not do close-on-exit. Reason: lots and lots of programs that would
> kill such system with file leaks.
--upas-kxfvdpzzatzirclffacicwhbmt
Content-Type: message/rfc822
Content-Disposition: inline
Received: from mail.cse.psu.edu ([130.203.4.6]) by cpu; Wed Nov 15 00:32:34 GMT 2000
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.18.6])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP
id D417119A04; Tue, 14 Nov 2000 19:32:08 -0500 (EST)
Received: from math.psu.edu (leibniz.math.psu.edu [146.186.130.2])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 999A019A01
for <9fans@cse.psu.edu>; Tue, 14 Nov 2000 19:31:16 -0500 (EST)
Received: from weyl.math.psu.edu (weyl.math.psu.edu [146.186.130.226])
by math.psu.edu (8.9.3/8.9.3) with ESMTP id TAA03853;
Tue, 14 Nov 2000 19:31:15 -0500 (EST)
Received: from localhost (viro@localhost)
by weyl.math.psu.edu (8.9.3/8.9.3) with ESMTP id TAA06518;
Tue, 14 Nov 2000 19:31:14 -0500 (EST)
X-Authentication-Warning: weyl.math.psu.edu: viro owned process doing -bs
From: Alexander Viro
To: Tom Duff
Cc: 9fans@cse.psu.edu
Subject: Re: [9fans] AFS-client for Plan9 - ?
In-Reply-To: <10011141554.ZM1200618@marvin>
Message-ID:
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0rc1
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the O/S Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive:
Date: Tue, 14 Nov 2000 19:31:13 -0500 (EST)
On Tue, 14 Nov 2000, Tom Duff wrote:
> > Precisely. And any kernel that will try _not_ to do that will die under the
> > leaks produced by the $BIGNUM of applications expecting it do act as any
> > sane UNIX should.
> Which UNIX version lacks this behavior?
> (Or are you trying to run UNIX programs
> on some non-UNIX?)
Grr... OK, let me rephrase it:
I really doubt that there is (or ever was) a UNIX variant that
would not do close-on-exit. Reason: lots and lots of programs that would
kill such system with file leaks.
IOW, "not likely" was about "some numskull changed it" part - such attempt
would backfire immediately. We are in violent agreement...
--upas-kxfvdpzzatzirclffacicwhbmt--
From 9fans@cse.psu.edu Wed Nov 15 08:20:03 2000
From: 9fans@cse.psu.edu (Alexander Viro)
Date: Wed, 15 Nov 2000 03:20:03 -0500 (EST)
Subject: [9fans] AFS-client for Plan9 - ?
In-Reply-To:
Message-ID:
On Wed, 15 Nov 2000 nigel@9fs.org wrote:
> Let me explain (and, yes, this is a quote from Fawlty Towers)
>
> Programs which do not explicitly close flies before invoking exit() are
> not
>
> 1) badly written
Sure.
> or
>
> 2) forcing Unix implementations to have to do close on exit to compensate
Sure.
> These are the defined semantics. So the reason is "because that's what
> the program quite reasonably expects".
... and so many programs _do_ expect it (quite reasonably) that changing
that behaviour would require the audit and rewrite of the whole userland.
Folks, how about finally agreeing that we agree and stopping that subthread?
It's getting really silly.
From 9fans@cse.psu.edu Wed Nov 15 09:07:03 2000
From: 9fans@cse.psu.edu (Richard Miller)
Date: Wed, 15 Nov 2000 09:07:03 0000
Subject: [9fans] Multiprocessor system..
Message-ID:
> Is there a command display the number of
> cpus being used?
cat /dev/sysstat
There is one line of information per active cpu.
From 9fans@cse.psu.edu Wed Nov 15 14:25:43 2000
From: 9fans@cse.psu.edu (Ish Rattan)
Date: Wed, 15 Nov 2000 09:25:43 -0500 (EST)
Subject: [9fans] 10141111.9gz patches..
Message-ID:
I tried to apply the patches as
wrap/inst 10141111.9gz
it says that files are newer and skips, the files have not
been modified but the system was installed on 10/14/00 after
a crash..
skillping /386/bin/acme: newer than archive
...
ls -l /386/bin/acme
-rwxrwxrwx ... Oct 14 16:45 /386/bin/acme
It is safe to use
wrap/inst -F 10141111.9z
I do not want to reinstall?
- ishwar
From 9fans@cse.psu.edu Wed Nov 15 18:44:30 2000
From: 9fans@cse.psu.edu (Russ Cox)
Date: Wed, 15 Nov 2000 13:44:30 -0500
Subject: [9fans] 10141111.9gz patches..
Message-ID: <20001115184435.562F9199E7@mail.cse.psu.edu>
It is safe to use
wrap/inst -F 10141111.9z
This may be a false alarm (regarding /386/bin/acme).
Others have had similar troubles. But you should be
able to edit the wrap/inst -F command that wrap/inst prints
and then send it.
Russ
From arisawa@aichi-u.ac.jp Thu Nov 16 08:34:18 2000
From: arisawa@aichi-u.ac.jp (arisawa@aichi-u.ac.jp)
Date: Thu, 16 Nov 2000 17:34:18 0900
Subject: [9fans] httpd.c
Message-ID: <20001116083551.18EC4199E1@mail.cse.psu.edu>
Hello,
I found a code bellow:
for(;;)sleep(1000);
in /sys/src/cmd/ip/httpd/httpd.c
Is this right?
Kenji Arisawa
E-mail: arisawa@aichi-u.ac.jp
From 9fans@cse.psu.edu Thu Nov 16 09:51:59 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Thu, 16 Nov 2000 09:51:59 0000
Subject: [9fans] another version of the kernel notes
Message-ID: <20001116085109.B1FE1199E1@mail.cse.psu.edu>
You can download it from the same urls I gave before.
Forgive me for the errors yet to be fixed, and feel free
to suggest any kind of thing (reordering, fixes, using a
different approach to explain the code, adding things,
removing things, etc.)
regards
Since the last version of the document, these things have been fixed.
* Starting up chapter:
+ Small section about PC hardware added.
+ Horrendous bug about how do QIDs work fixed (I said that vers
was used to detect removed-and-recreated files, which is not
the case; In fact I think I understood that was not the case
long ago before starting this document. Too sleepy that day?
Too few caffeine? Who knows?).
I already wrote 1000 times how QIDs work, (thanks rc), so
I have paid my mistake.
+ pageinit has nothing to do with software for paging, it is
just initializing the page allocator. The starting up chapter
was saying it had to do with software MMU, although on the
next paragraphs it was described and the reader could know
what it really does.
+ psstate only holds the process state for ps.
+ process groups have name spaces, not processes. The
description was confussing.
* Process chapter:
+ Note added about why to use a scheduler stack.
+ Note added about why to have two scheduling classes.
+ Note added about other synch. means.
+ postnote fix.
+ Note for wakeup in pexit.
+ procstopwait fix.
* Files chapter: not yet fixed, but for...
+ Note added about why to have a limit on file descriptors.
* Memory chapter: not yet fixed.
From 9fans@cse.psu.edu Thu Nov 16 10:35:39 2000
From: 9fans@cse.psu.edu (Stephen Parker)
Date: Thu, 16 Nov 2000 10:35:39 -0000
Subject: [9fans] const declarators in structs
Message-ID:
i spent a while this morning pondering what an error message from 8c meant.
i tracked it down to a struct of the form:
struct S {
int const *p;
};
the compiler suggested that unnamed objects in structs should be of struct
type.
(i know that const isn't really a plan9 thing, but this was a bit of code
from a small device that i was trying to port.)
stephen
From 9fans@cse.psu.edu Thu Nov 16 19:33:24 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Thu, 16 Nov 2000 20:33:24 +0100
Subject: [9fans] httpd.c
References: <20001116083551.18EC4199E1@mail.cse.psu.edu>
Message-ID: <016501c05004$16346e40$0ab9c6d4@cybercable.fr>
From:
> I found a code bellow:
> for(;;)sleep(1000);
> in /sys/src/cmd/ip/httpd/httpd.c
>
my theory is that they're trying to implement unix pause(2).
From 9fans@cse.psu.edu Thu Nov 16 21:23:28 2000
From: 9fans@cse.psu.edu (Richard Miller)
Date: Thu, 16 Nov 2000 21:23:28 0000
Subject: [9fans] const declarators in structs
Message-ID:
stephen.parker@pitechnology.com reports a misleading C compiler error message from:
struct S {
int const *p;
};
The underlying cause is that the compiler expects const/volatile keywords before
other simple type names in a structure/union element declarator (but nowhere else) --
in the same context "const int *p" is considered acceptable.
Is this a deliberate choice or an oversight? If the latter, a simple correction
is to change the grammar as follows:
/sys/src/cmd/cc/cc.y:216 c cc.y:216
< etlist
---
> tlist
/sys/src/cmd/cc/cc.y:221 c cc.y:221
< | edecl etlist
---
> | edecl tlist
The definitions of etlist, etypes and tnlist then become redundant and can be
pruned from cc.y as well.
-- Richard Miller
From Stephen Wynne Thu Nov 16 02:10:19 2000
From: Stephen Wynne (Stephen M Wynne)
Date: Wed, 15 Nov 2000 21:10:19 -0500
Subject: [9fans] select()
Message-ID: <200011160210.VAA06775@mindspring.com>
In http://plan9.bell-labs.com/sys/doc/9.html, there's a hint that Plan 9's
design avoids some of the nastiness with select() here:
Compare this to the UNIX select system call: select applies only
to a restricted set of devices, legislates a style of
multiprogramming in the kernel, does not extend across networks,
is difficult to implement, and is hard to use.
Would someone be so kind as to elaborate? It looks like select() is
implemented very much like BSD select() in the APE.
From 9fans@cse.psu.edu Thu Nov 16 22:43:15 2000
From: 9fans@cse.psu.edu (Russ Cox)
Date: Thu, 16 Nov 2000 17:43:15 -0500
Subject: [9fans] select()
Message-ID: <20001116224334.5EC75199E6@mail.cse.psu.edu>
In http://plan9.bell-labs.com/sys/doc/9.html, there's a hint that Plan 9's
design avoids some of the nastiness with select() here:
Compare this to the UNIX select system call: select applies only
to a restricted set of devices, legislates a style of
multiprogramming in the kernel, does not extend across networks,
is difficult to implement, and is hard to use.
Would someone be so kind as to elaborate? It looks like select() is
implemented very much like BSD select() in the APE.
Select in the APE is implemented entirely at user level,
with no help from the kernel. It continually calls sleep(100)
and then checks for input. Select on most Unix systems
is a system call, which requires the kernel to do all that
and usually more. Further, since select requires that at most
one of the reads succeeds, it is very hard to implement once
you have file systems coming from somewhere other than
local resources (e.g., any network file system). It also often
makes for awkward program structure.
The passage you quote is, I believe, arguing that Alef's
style of multiprogramming is a better solution than select,
not that Plan 9 makes select easier to implement. Select is
inherently hard to implement because of its specification.
Rob argues the benefits of a precursor to the Plan 9 style
of multiprogramming more extensively in
http://plan9.bell-labs.com/cm/cs/doc/89/1-a.ps.gz.
Russ
From 9fans@cse.psu.edu Fri Nov 17 19:13:25 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Fri, 17 Nov 2000 15:13:25 -0400
Subject: [9fans] Tired of the 40 X 40 Plan? 6444
Message-ID: <0000786614e4$00003c7c$000040a0@kimo.com.tw>
Tired of the 40 X 40 X 40 Plan? You know:
Work 40 hours per week for someone else for 40 years, then receive a 40% reduction in pay!
Is working for a "boss" too demeaning and unrewarding?
Are you sick of depending on a job with too little pay and too many hours with no personal reward and even less future?
If you're determined to retire in the next 2 - 5 years with enough income to have REAL Financial Independence and Freedom, and are not afraid to work for it, I can help you.
I am looking for people with a Good Work Ethic and extraordinary Desire to Earn at Least $10,000 per Month Working From Home!
NO SPECIAL SKILLS OR EXPERIENCE REQUIRED. We will give you all the training and personal support you will need to ensure your success!
This LEGITIMATE HOME-BASED INCOME OPPORTUNITY can put you back in Control of your Time, Your Finances, and Your Life!
If you've tried other opportunities in the past that have failed to live up to their promises, THIS IS DIFFERENT THAN ANYTHING ELSE YOU'VE SEEN!
THIS IS NOT A GET-RICH-QUICK SCHEME!
YOUR FINANCIAL PAST DOES NOT HAVE TO BE YOUR FINANCIAL FUTURE!
CALL ONLY IF YOU ARE SERIOUS!
1-800-533-9351 (Free, 24 hour, 2 minute recorded message)
DON'T GO TO SLEEP WITHOUT LISTENING TO THIS!
"All our dreams can come true - if we have the courage to pursue them" - Walt Disney
To be removed from future mailings, send an email to: Chszz8@yahoo.com and type "Remove" in the subject line.
From cnielsen@pobox.com Fri Nov 17 23:48:43 2000
From: cnielsen@pobox.com (Christopher Nielsen)
Date: Fri, 17 Nov 2000 15:48:43 -0800 (PST)
Subject: [9fans] IL and NAT
Message-ID:
I've been tinkering with connecting to my fileserver over IL
at home via my DSL line across the Internet and through a
Cisco router acting as a firewall and NAT.
The router keeps responding with ICMP host unreachable, but
I know I can get to the machines in question.
I've opened a TAC case with Cisco to see what they had to
say. Having probably never even heard of IL, the engineer
has responded that he doesn't think IL is "NAT compliant".
My gut response is bollocks, but is there any reason that IL
wouldn't work through NAT other than Cisco hasn't written
the code to handle it?
--
Christopher Nielsen
cnielsen@pobox.com
From 9fans@cse.psu.edu Fri Nov 17 23:56:38 2000
From: 9fans@cse.psu.edu (Scott Schwartz)
Date: Fri, 17 Nov 2000 18:56:38 -0500
Subject: [9fans] IL and NAT
In-Reply-To: Message from Christopher Nielsen
of "Fri, 17 Nov 2000 15:48:43 PST."
Message-ID: <20001117235638.5280.qmail@g.bio.cse.psu.edu>
| My gut response is bollocks, but is there any reason that IL
| wouldn't work through NAT other than Cisco hasn't written
| the code to handle it?
That's exactly the problem with NAT. Every application has to be
specially hacked into the firewall.
To my way of thinking, it's much nicer to import /net from the firewall
instead.
From 9fans@cse.psu.edu Sat Nov 18 00:17:47 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Fri, 17 Nov 2000 19:17:47 -0500
Subject: [9fans] IL and NAT
Message-ID: <20001118001754.DE2F0199E1@mail.cse.psu.edu>
NAT routers generally have to rewrite port numbers (not just IP
addresses) for protocols that use them, and ports numbers are at
different offsets and of potentially different sizes in different
protocol's headers. IL's port numbers appear later than TCP's and
UDP's, for example. NAT routers will generally understand the headers
of TCP, UDP and ICMP at minimum, but I haven't encountered one yet
that understood IL (even Lucent's own).
Contrary to what Scott just said, it's not each application that has
to be added to a NAT router, but each protocol that rides directly on
IP (or beside it).
From cnielsen@pobox.com Sat Nov 18 00:50:25 2000
From: cnielsen@pobox.com (Christopher Nielsen)
Date: Fri, 17 Nov 2000 16:50:25 -0800 (PST)
Subject: [9fans] IL and NAT
In-Reply-To: <20001118001754.DE2F0199E1@mail.cse.psu.edu>
Message-ID:
On Fri, 17 Nov 2000 geoff@x.bell-labs.com wrote:
> NAT routers generally have to rewrite port numbers (not
> just IP addresses) for protocols that use them, and
> ports numbers are at different offsets and of
> potentially different sizes in different protocol's
> headers. IL's port numbers appear later than TCP's and
> UDP's, for example. NAT routers will generally
> understand the headers of TCP, UDP and ICMP at minimum,
> but I haven't encountered one yet that understood IL
> (even Lucent's own).
That makes perfect sense, and if I would have been a little
more patient and thought it through, I probably would have
figured that out.
That said, I have some sway with Cisco's development team,
so I _might_ be able to get them to implement support for
IL. I'll let you know how it goes.
--
Christopher Nielsen
cnielsen@pobox.com
From 9fans@cse.psu.edu Sat Nov 18 01:19:31 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Sat, 18 Nov 2000 02:19:31 +0100
Subject: [9fans] IL and NAT
References: <20001118001754.DE2F0199E1@mail.cse.psu.edu>
Message-ID: <004701c050fd$a481eca0$0ab9c6d4@cybercable.fr>
From:
> NAT routers generally have to rewrite port numbers (not just IP
> addresses) ...
yes, i tracked down a particularly nasty case of a firewall
doing NAT to UDP packets with a destination port of 53 [DNS].
i found that some DNS servers would not reply to requests
that didn't have a source port of 53; NAT having munged
the source address and port.
i would have found it a lot faster if my pleas for a
protocol analyser had been heeded -- i'd only been
bitching about it for a _year_. somehow i managed
to forge up some queries that demonstrated the
problem.
i also had the added stumbling block of not knowing or
being able to know the firewall's config. contractors
were prohibited from going near them, except when things
were _really_ screwed up.
``oh, but that's impossible, boyd... err, i see''.
From 9fans@cse.psu.edu Sat Nov 18 03:02:08 2000
From: 9fans@cse.psu.edu (Scott Schwartz)
Date: Fri, 17 Nov 2000 22:02:08 -0500
Subject: [9fans] IL and NAT
In-Reply-To: Message from geoff@x.bell-labs.com
of "Fri, 17 Nov 2000 19:17:47 EST." <20001118001754.DE2F0199E1@mail.cse.psu.edu>
Message-ID: <20001118030208.7775.qmail@g.bio.cse.psu.edu>
| Contrary to what Scott just said, it's not each application that has
| to be added to a NAT router, but each protocol that rides directly on
| IP (or beside it).
Isn't it the case that some applications, like ftp, encode ip address
and port information in application layer traffic, which NAT has to
account for? Linux seems to have code to handle that sort of stuff
(linux/net/ipv4/ip_masq*).
From 9fans@cse.psu.edu Sat Nov 18 03:21:26 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Fri, 17 Nov 2000 22:21:26 -0500
Subject: [9fans] IL and NAT
Message-ID: <20001118032427.B11EB199E6@mail.cse.psu.edu>
This is a multi-part message in MIME format.
--upas-wqjntrvqllaokorboxepflkazi
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
I'm not sure; it's certainly possible that individual applications do
such things.
The usual problem with ftp is that by default ftp clients, especially
older ones, tend to trigger connections back from the target system to
port 20. ftp's so-called ``passive'' mode forces the connections to
be placed from the initiating system and avoids this problem.
--upas-wqjntrvqllaokorboxepflkazi
Content-Type: message/rfc822
Content-Disposition: inline
Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by x.bell-labs.com; Fri Nov 17 22:03:33 EST 2000
Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Fri Nov 17 22:03:22 EST 2000
Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Fri Nov 17 22:03:20 EST 2000
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.20.6])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP
id 94546199F9; Fri, 17 Nov 2000 22:03:09 -0500 (EST)
Received: from bio.cse.psu.edu (galapagos.cse.psu.edu [130.203.12.17])
by mail.cse.psu.edu (CSE Mail Server) with SMTP id 97557199E6
for <9fans@cse.psu.edu>; Fri, 17 Nov 2000 22:02:08 -0500 (EST)
Received: (qmail 7777 invoked by uid 991); 18 Nov 2000 03:02:08 -0000
Message-ID: <20001118030208.7775.qmail@g.bio.cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] IL and NAT
In-Reply-To: Message from geoff@x.bell-labs.com
of "Fri, 17 Nov 2000 19:17:47 EST." <20001118001754.DE2F0199E1@mail.cse.psu.edu>
From: Scott Schwartz
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0rc1
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the O/S Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive:
Date: Fri, 17 Nov 2000 22:02:08 -0500
| Contrary to what Scott just said, it's not each application that has
| to be added to a NAT router, but each protocol that rides directly on
| IP (or beside it).
Isn't it the case that some applications, like ftp, encode ip address
and port information in application layer traffic, which NAT has to
account for? Linux seems to have code to handle that sort of stuff
(linux/net/ipv4/ip_masq*).
--upas-wqjntrvqllaokorboxepflkazi--
From 9fans@cse.psu.edu Sat Nov 18 06:32:53 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Sat, 18 Nov 2000 01:32:53 -0500
Subject: [9fans] IL and NAT
Message-ID: <20001118063257.01E01199F7@mail.cse.psu.edu>
//That said, I have some sway with Cisco's
//development team, so I _might_ be able to
//get them to implement support for IL.
ooh, that'd be embarasing. Cisco supporting a
protocol developed at Bell Labs that Lucent's
own products don't support. er, or does Lucent
not do that sort of thing any more? maybe we
should go talk to Avaya...
-Îą.
From 9fans@cse.psu.edu Sat Nov 18 13:53:50 2000
From: 9fans@cse.psu.edu (Theo Honohan)
Date: Sat, 18 Nov 2000 13:53:50 +0000
Subject: [9fans] IL and NAT
In-Reply-To: Your message of "Fri, 17 Nov 2000 22:21:26 EST."
<20001118032427.B11EB199E6@mail.cse.psu.edu>
References: <20001118032427.B11EB199E6@mail.cse.psu.edu>
Message-ID:
geoff@x.bell-labs.com wrote:
> scott wrote:
> >
> > Isn't it the case that some applications, like ftp, encode ip address
> > and port information in application layer traffic, which NAT has to
> > account for? Linux seems to have code to handle that sort of stuff
> > (linux/net/ipv4/ip_masq*).
>
> I'm not sure; it's certainly possible that individual applications do
> such things.
I think Scott's right. All viable NAT products do this, although it's not
strictly part of NAT. A search for "NAT" on Cisco's site confirms
that they support the use of "PORT" in ftp, and a slew of features of
other protocols that would otherwise be broken by NAT.
From 9fans@cse.psu.edu Sat Nov 18 14:04:30 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Sat, 18 Nov 2000 09:04:30 -0500
Subject: [9fans] IL and NAT
Message-ID: <20001118140436.AEAA6199F0@mail.cse.psu.edu>
This is a multi-part message in MIME format.
--upas-betjmtvhbnvytdlijfqvfdsywh
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
we don't do any in home stuff, that all goes off with avaya and Microelectronics,
our 2 current spin offs. Orinoco (aka wavelan) also goes with micro.
--upas-betjmtvhbnvytdlijfqvfdsywh
Content-Type: message/rfc822
Content-Disposition: inline
Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Sat Nov 18 01:33:20 EST 2000
Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Sat Nov 18 01:33:19 EST 2000
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.8.6])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP
id 3BE2119A00; Sat, 18 Nov 2000 01:33:09 -0500 (EST)
Received: from cosym.net (gcollyer-14.dsl.speakeasy.net [216.254.93.14])
by mail.cse.psu.edu (CSE Mail Server) with SMTP id 01E01199F7
for <9fans@cse.psu.edu>; Sat, 18 Nov 2000 01:32:57 -0500 (EST)
From: anothy@cosym.net
To: 9fans@cse.psu.edu, cnielsen@pobox.com
Subject: Re: [9fans] IL and NAT
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Message-Id: <20001118063257.01E01199F7@mail.cse.psu.edu>
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0rc1
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the O/S Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive:
Date: Sat, 18 Nov 2000 01:32:53 -0500
//That said, I have some sway with Cisco's
//development team, so I _might_ be able to
//get them to implement support for IL.
ooh, that'd be embarasing. Cisco supporting a
protocol developed at Bell Labs that Lucent's
own products don't support. er, or does Lucent
not do that sort of thing any more? maybe we
should go talk to Avaya...
-Îą.
--upas-betjmtvhbnvytdlijfqvfdsywh--
From 9fans@cse.psu.edu Sat Nov 18 18:42:05 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Sat, 18 Nov 2000 18:42:05 0000
Subject: [9fans] IL and NAT
Message-ID:
This is a multi-part message in MIME format.
--upas-apybwrxrobjqbpliblsvznsbtl
Content-Disposition: inline
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Before we are too down on NAT implementations, there is a distinction
between NAT and NAPT, according to various RFCs and associated
documents.
NAT means what is says: address translation. NAPT means address and
port. You can simply translate addresses and maintain the port, but
this means that typically only one internal node can communicate.If
you do this, then the protocol is irrelevant, and IL would pass
through.
In fact, since it has been mentioned, Lucent devices (neĂŠ Ascend),
worked this way until it became apparent that Cisco had implemented
NAPT and they rolled out the full monty. They called it "single address
translation".
Once you choose to translate ports as well, as has been said, you need
to understand where the ports are; for TCP and UDP it is in the same place,
so they get done. It is completely unsurprising that other protocols aren't.
ICMP gets done because it's dull if you can't traceroute and ping. It takes
hacks, but it can be done.
FTP is depressing. Anyone out there designing protocols: take note, don't
embed IP addresses in the stream.
Others are as bad, or insoluble: luckily, they are less important, like IRC
or RealAudio.
On top of this, to create some 'reliability', commerical NAT routers
have a list of TCP and UDP ports which they are prepared to translate.
'Known good' if you like. My Pipeline 75 does not do POP3
automatically. I had to tell it to, despite the protestations of the
manuals. I looked for a software update, but since Lucent bought
them, this doesn't happen any more. Some other products, I
understand, refuse straightforward protocols like POP3 despite best
efforts.
So, the summary is use 9p over TCP, not IL, unless you can rewrite
your router. This is becoming easier since both FreeBSD and Linux
have WAN drivers, and NAT code.
As it happens, all translation in FreeBSD is done using a library,
with plug-ins for various awkward protocols. Fix the library, and all
the various translators (natd, pppd, pppoed) would all fall into
line. Modifying the implementation to do IL would be straightforward
I think.
--upas-apybwrxrobjqbpliblsvznsbtl
Content-Type: message/rfc822
Content-Disposition: inline
Received: from mail.cse.psu.edu ([130.203.4.6]) by cpu; Sat Nov 18 13:55:18 GMT 2000
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.18.6])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP
id 16A22199EB; Sat, 18 Nov 2000 08:54:09 -0500 (EST)
Received: from chiark.greenend.org.uk (chiark.greenend.org.uk [195.224.76.132])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 55D44199E6
for <9fans@cse.psu.edu>; Sat, 18 Nov 2000 08:53:52 -0500 (EST)
Received: from localhost (chiark.greenend.org.uk) [127.0.0.1] (theoh)
by chiark.greenend.org.uk with esmtp (Exim 3.12 #2)
id 13x8RD-0007iy-00 (Debian); Sat, 18 Nov 2000 13:53:51 +0000
To: 9fans@cse.psu.edu
Subject: Re: [9fans] IL and NAT
In-Reply-To: Your message of "Fri, 17 Nov 2000 22:21:26 EST."
<20001118032427.B11EB199E6@mail.cse.psu.edu>
References: <20001118032427.B11EB199E6@mail.cse.psu.edu>
From: Theo Honohan
Message-Id:
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0rc1
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the O/S Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive:
Date: Sat, 18 Nov 2000 13:53:50 +0000
geoff@x.bell-labs.com wrote:
> scott wrote:
> >
> > Isn't it the case that some applications, like ftp, encode ip address
> > and port information in application layer traffic, which NAT has to
> > account for? Linux seems to have code to handle that sort of stuff
> > (linux/net/ipv4/ip_masq*).
>
> I'm not sure; it's certainly possible that individual applications do
> such things.
I think Scott's right. All viable NAT products do this, although it's not
strictly part of NAT. A search for "NAT" on Cisco's site confirms
that they support the use of "PORT" in ftp, and a slew of features of
other protocols that would otherwise be broken by NAT.
--upas-apybwrxrobjqbpliblsvznsbtl--
From 9fans@cse.psu.edu Sat Nov 18 19:00:32 2000
From: 9fans@cse.psu.edu (Theo Honohan)
Date: Sat, 18 Nov 2000 19:00:32 +0000
Subject: [9fans] IL and NAT
In-Reply-To: Your message of "Sat, 18 Nov 2000 18:42:05."
References:
Message-ID:
nigel@9fs.org wrote:
>
> Before we are too down on NAT implementations, there is a distinction
> between NAT and NAPT, according to various RFCs and associated
> documents.
Yes, quite. I didn't mean to be "down on" simple NAT implementations;
OTOH, I do still think it's a fair to say that you need to do both NAT
and NAPT to be a viable product, these days.
From 9fans@cse.psu.edu Sat Nov 18 19:24:46 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Sat, 18 Nov 2000 20:24:46 +0100
Subject: [9fans] IL and NAT
References:
Message-ID: <00d101c05195$369b53a0$0ab9c6d4@cybercable.fr>
From:
> In fact, since it has been mentioned, Lucent devices (neĂŠ Ascend),
you mean: nĂŠe; the feminine past participle of the verb 'naĂŽtre' [to be born].
the past participle is 'nĂŠ' and is conjugated with 'ĂŞtre' [to be]. it's highly
irreguler, as most verbs, in the past tense, are conjugated with 'avoir' [to
have].
je suis nĂŠ [i was born]
je suis nĂŠe [if i was female]
bit like 'mourir' [to die]:
je suis mort
je suis morte
where normally you'd use 'avoir', except for movement and reflexive verbs:
j'ai deconnĂŠ [i screwed up or pissed about]
and no 'e' on the end of the past participle if you conjugate with 'avoir'.
but i digress :-) je dĂŠconne...
From 9fans@cse.psu.edu Sat Nov 18 23:19:16 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Sun, 19 Nov 2000 00:19:16 +0100
Subject: [9fans] vito nuova inferno on 98
Message-ID: <013e01c051b5$f93367c0$0ab9c6d4@cybercable.fr>
i want to compile /utils/mk for inferno after configuring
mkconfig and it tries to use:
CC=cl
AS=ml
which don't exist, so i'm a bit confused.
i got in mkconfig:
SYSHOST=Nt
OBJTYPE=386
as i understand it i have to compile it from windows.
From 9fans@cse.psu.edu Sat Nov 18 23:43:52 2000
From: 9fans@cse.psu.edu (Russ Cox)
Date: Sat, 18 Nov 2000 18:43:52 -0500
Subject: [9fans] vito nuova inferno on 98
Message-ID: <20001118234355.9B81A199E8@mail.cse.psu.edu>
CC=cl
AS=ml
cl and ml are the microsoft visual c/c++ compiler/linker
and presumably the assembler/linker. cl stands for
compile and/or link.
From 9fans@cse.psu.edu Sun Nov 19 03:07:46 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Sat, 18 Nov 2000 21:07:46 -0600
Subject: [9fans] 2.9 cents per min. -- agents needed--$9000/mo
Message-ID:
2.9 cents a minute -- No Gimmicks -- No Hidden Fees
+ 10 year old stable company
+ All fibre Optic
+ Available 24/7 365 days a year
+ No Credit Check
+ No Pin Codes
+ No Contracts
+++++++ Covers In State & Out of State +++++++
For those of you that wish to try our service please ask our
represenative about our free vacation offer and $500 spending
benefits GIVEN DIRECTLY TO YOU for trying our service out for
at least 1 month.
Call Today 713.781.6570 *****************713.781.6570
AGENTS NEEDED! NOT MLM!
MAKE $5000 -- $10,000 PER MONTH
TRAINING AND SUPPORT PROVIDED!
AGENTS RECEIVE:
** AGENTS GET PAID DAILY!
** $79.00 VALAUE! -- AMERICA'S HOTTEST INTRODUCTORY TAX COURSE
** $299.00 VALUE! -- 3 DAYS 2 NIGHTS GRAND GETAWAY VACATION
** 500 MINUTES OF FREE LONG DISTANCE
CALL TODAY 713.781.6570*****************713.781.6570
From 9fans@cse.psu.edu Sun Nov 19 08:04:22 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Sun, 19 Nov 2000 02:04:22 -0600 (CST)
Subject: [9fans] 2.9 cents per min. -- agents needed--$9000/mo
Message-ID: <200011190804.CAA32595@sys27.hou.wt.net>
2.9 cents a minute -- No Gimmicks -- No Hidden Fees
+ 10 year old stable company
+ All fibre Optic
+ Available 24/7 365 days a year
+ No Credit Check
+ No Pin Codes
+ No Contracts
+++++++ Covers In State & Out of State +++++++
For those of you that wish to try our service please ask our
represenative about our free vacation offer and $500 spending
benefits GIVEN DIRECTLY TO YOU for trying our service out for
at least 1 month.
Call Today 713.781.6570 *****************713.781.6570
AGENTS NEEDED! NOT MLM!
MAKE $5000 -- $10,000 PER MONTH
TRAINING AND SUPPORT PROVIDED!
AGENTS RECEIVE:
** AGENTS GET PAID DAILY!
** $79.00 VALAUE! -- AMERICA'S HOTTEST INTRODUCTORY TAX COURSE
** $299.00 VALUE! -- 3 DAYS 2 NIGHTS GRAND GETAWAY VACATION
** 500 MINUTES OF FREE LONG DISTANCE
CALL TODAY 713.781.6570*****************713.781.6570
From 9fans@cse.psu.edu Thu Nov 16 11:43:04 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Wed, 15 Nov 2000 23:43:04 -1200
Subject: [9fans] MONEY - GET IT, MULTIPLY IT, AND KEEP IT ! 17611
Message-ID: <000043ea185c$00006f9f$000044cb@1.0.5.6>
Here is the page that will have everyone talking !
http://www.ricokid.cc
Also, there is a two week window of opportunity that displays my
AMAZING "HOLIDAYS" PRESENT to you..based on this, We will accept funds
until December 20, 2000, but only if you have notified us of your intent
by noting the deposit in your account by the November 30th deadline.
Curious?
Use this: http://www.ricokid.cc to GET IT, MULTIPLY IT,
AND MOST IMPORTANTLY, KEEP IT !
(For the "GIFT" to be explained and accessed, please respond through the ORDER PAGE,
or the QUESTION button).
TIME is of the essence.
If you wish to be removed from the list, please replace what is in
the subject line with the word "remove" and hit REPLY.
From 9fans@cse.psu.edu Sat Nov 18 14:20:34 2000
From: 9fans@cse.psu.edu (Steve Kilbane)
Date: Sat, 18 Nov 2000 14:20:34 +0000
Subject: [9fans] IL and NAT
In-Reply-To: Your message of "Fri, 17 Nov 2000 15:48:43 PST."
Message-ID: <200011181420.OAA03216@whitecrow.demon.co.uk>
> My gut response is bollocks, but is there any reason that IL
> wouldn't work through NAT other than Cisco hasn't written
> the code to handle it?
If I recall Firewall-1 correctly, you can bodge up support for
rare protocols by specifying some low-level transformation rules:
if (value at offset x) == y, change bytes elsewhere accordingly.
I was only skimming docs at the time, and never got around to
reading it in detail, so I might be completely wrong. Point is,
though, does your Cisco support something similar?
As for it going into the Cisco base product (from which an entire
range of Cisco units are produced), I'd put the chances at approximately
equal to the market: practically none. Even if you gave them the code
for free, they'd have to make sure it didn't break anything else, and
that'd cost them.
steve
From 9fans@cse.psu.edu Mon Nov 20 08:44:53 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Mon, 20 Nov 2000 18:44:53 +1000 (EST)
Subject: [9fans] Matrox G400
Message-ID: <200011200844.SAA18577@asuncion.dstc.edu.au>
[I posted about 3 variants of this on the local NNTP g/w to 9fans
and if anyone can confirm they got out, I didn't seeums hence
the repeat mail.]
I added my G400 to vgadb using the device ID string the error message that
the initial probe gives, but that didn't seem enough to get it working.
(died in a later phase of PCI vga device frob)
are there simple textfile changes I can make to vgadb to enable
a g400 to work like older Matrox cards or does this one wait
for smarter people to code?
btw, after the addition and the subsequent vga.txt file, the disk was
not a valid FAT object and I had to recut the plan9.9fd floppy. it was
readable but then not writable. a buglet in the FAT emulation?
-George
----
before added to vgadb
aux/vga: controller not in /lib/vgadb
0xC0000 55 AA 40 EB 7B 15 D0 03 A0 04 E0 0B 7E 31 1A 0C U.@.{.......~1..
0xC0010 24 0C FF FF 00 00 00 00 60 00 00 00 00 20 49 42 $.......`.... IB
0xC0020 4D 20 43 4F 4D 50 41 54 49 42 4C 45 20 4D 41 54 M COMPATIBLE MAT
0xC0030 52 4F 58 2F 4D 61 74 72 6F 78 20 47 34 30 30 20 ROX/Matrox G400
0xC0040 56 47 41 2F 56 42 45 20 42 49 4F 53 20 28 56 31 VGA/VBE BIOS (V1
0xC0050 2E 35 29 20 62 32 32 20 00 87 DB 87 DB 87 DB 90 .5) b22 ........
0xC0060 50 43 49 52 2B 10 25 05 00 00 18 00 00 00 00 03 PCIR+.%.........
0xC0070 40 00 15 16 00 80 00 00 38 39 37 2D 31 35 00 FF @.......897-15..
0xC0080 55 33 C0 8E D8 8E C0 E8 4D 59 2E 89 1E F2 7F BF U3......MY......
0xC0090 08 00 B0 08 90 E8 AD 58 2E 88 0E F4 7F E8 02 01 .......X........
0xC00A0 E8 94 56 2E 8B 1E F2 7F 2E 8B 1E F2 7F E8 03 2B ..V............+
0xC00B0 BF 43 00 90 B0 08 90 E8 8B 58 80 C9 10 B0 0B 90 .C.......X......
0xC00C0 E8 82 58 BF 08 00 B0 08 90 E8 79 58 80 F9 02 75 ..X.......yX...u
0xC00D0 13 B1 1A 90 90 E8 6E 5C 80 C9 40 8A E9 B1 1A 90 ......n\..@.....
0xC00E0 90 E8 47 5C 2E F6 06 B5 7A 04 74 13 BF 40 00 90 ..G\....z.t..@..
0xC00F0 B0 08 90 E8 4F 58 80 C9 40 B0 0B 90 E8 46 58 E8 ....OX..@....FX.
main->snarf
vga->snarf
vga->dump
vga misc 67
vga feature 00
vga sequencer 03 00 03 00 02
vga crt 5F 4F 50 82 55 81 BF 1F - 00 4F 0D 0E 00 00 07 80
9C 8E 8F 28 1F 96 B9 A3 - FF
vga graphics 00 00 00 00 00 10 0E 00 - FF
vga attribute 00 01 02 03 04 05 14 07 - 38 39 3A 3B 3C 3D 3E 3F
0C 00 0F 08 00
vga apz 0
vga linear 0
vmf 25175000 vmdf 0 vf1 0 vbw 0
vga->init
dbdumpmode
type=vga, size=640x480x1
frequency=25175000
x=640 (0x280), y=480 (0x1E0), z=1 (0x1)
ht=800 (0x320), shb=664 (0x298), ehb=760 (0x2F8)
shs=664 (0x298), ehs=760 (0x2F8)
vt=525 (0x20D), vrs=491 (0x1EB), vre=493 (0x1ED)
hsync=0, vsync=0, interlace=0
vga->dump
vga flag Fdump|Finit|Fsnarf
vga misc E3
vga feature 00
vga sequencer 03 01 0F 00 06
vga crt 5F 4F 52 9F 53 1F20B 3E - 00 40 00 00 00 00 00 00
1EB 2D1DF 28 001EB1EC C3 -7FF
vga graphics 00 00 00 00 00 00 05 0F - FF
vga attribute 00 01 02 03 04 05 06 07 - 08 09 0A 0B 0C 0D 0E 0F
01 FF 0F 00 00
vga apz 0
vga linear 0
main->exits
-----
after added to vgadb:
main->snarf
vga->snarf
mga2164w->snarf
sequencer->enter on
sequencer->leave on
mga2164w: no Pcidev with Vid=0x102B, Did=0x051[9BF] or 0x521
From 9fans@cse.psu.edu Mon Nov 20 10:33:30 2000
From: 9fans@cse.psu.edu (John A. Murdie)
Date: Mon, 20 Nov 2000 10:33:30 +0000
Subject: [9fans] Re: Plan 9 on notebooks
Message-ID:
On 10th November, I wrote:
>Is the `Plan 9 from Bell Labs - supported PC hardware' page
>(http://plan9.bell-labs.com/plan9dist/pchardware.html) the whole
>story, particularly on the subject of Plan 9 on notebooks? The
>August 2000 FAQ (the latest I've seen) says nothing more. I'd
>rather like Plan 9 on a notebook.
Thanks again to the individuals who mailed me with useful
information. I was a little surprised to hear that 800x600
display resolution was so common. Can anyone tell me which of
the notebooks which will run Plan 9 `out of the box' (or for
which diffs are available) will support 1024x768?
John A. Murdie
From 9fans@cse.psu.edu Mon Nov 20 10:58:38 2000
From: 9fans@cse.psu.edu (Daniel Warmuth)
Date: Mon, 20 Nov 2000 10:58:38 GMT
Subject: [9fans] Matrox G400/SH/32 MB supported?
Message-ID: <3a16f743.34190565@news.cis.dfn.de>
Hi!
Is there any way to get the Matrox G400 SH 32 MB working with Plan9 ?
I didn't try anything but botting with the boot-floppy because
Bell-Labs' website says it is not supported...
There was a hex-dump displayed when booting, i could note it, if it
would help you.
Thanks,
Daniel
From 9fans@cse.psu.edu Mon Nov 20 10:58:02 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Mon, 20 Nov 2000 10:58:02 GMT
Subject: [9fans] Troubles with display - graphics card supported
Message-ID: <8v6qsh$36r$1@nnrp1.deja.com>
Hello!
I'm excited about getting started with Plan 9, but I've run into one
problem. I read all the documentation I could find. I would have dug
into the man pages and papers more, but I thought it would have been a
stab in the dark. I've included stuff from plan9.ini, vgadb, and
vgainfo.txt
aux/vga doesn't seem to be initializing my video card right. I get to
the portion of the install where the display is initialized, and get the
black screen.
I checked to make sure the supported chipset was the one I have on my
card by looking at what Xwindows said. It was indeed the mga2164w on my
Matrox Millenium.
I got the info from the BIOS from the video card from vgainfo.txt the
first time around. The Text was at the right offset according to the
vgadb, but there was a different version bios, so I added it to the
vgadb - its the V2.3 line:
ctlr
0xC002D="MATROX/MILLENNIUM VGA/VBE BIOS (V1.9 )" #
Millennium
0xC002D="MATROX/MILLENNIUM VGA/VBE BIOS (V3.0 )" #
Millennium
0xC002D="MATROX/MILLENNIUM VGA/VBE BIOS (V2.5 )" #
Millennium
0xC002D="MATROX/MILLENNIUM VGA/VBE BIOS (V2.3 )" #
Millennium
0xC002D="MATROX/MISTRAL VGA/VBE BIOS (V1." #
Millennium II
link=vga
ctlr=mga2164w linear=1
hwgc=mga2164whwgc
I also changed the monitor entry in plan9.ini to match the one I have.
And I changed the vgasize to 640x480x8 to be safe:
*nomp=1 distname=plan9 partition=new ether0=type=NE2000 monitor=cpd-1304
vgasize=640x480x8 mouseport=0 audio0=type=sb16 bootargs=local!#f0/fd0disk
bootfile=fd0!dos!9pcflop.gz
installurl=http://204.178.31.2/magic/9down/compressed/974514989.t4893ntezs2y4
vh2vedvisfrqd9mz4wk
for reference heres what vgadb says about the monitor:
#
# Sony CPD-1304
# Horizontal timing:
# Allowable frequency range: 28-50KHz
# Vertical timing:
# Allowable frequency range: 50-87Hz
#
cpd-1304
videobw=65
alias=multisync
,so this too:
# Multisync monitors. The entry with alias=multisync supplies the
bandwidth,
# which in turn decides the refresh rates when possible.
#
multisync
alias=vga
multisync = 1024x768
include=1024x768
multisync = 1024x768i
include=1024x768i
multisync = 1152x900
include=1152x900@70Hz
multisync = 1280x1024
include=1280x1024
multisync = 1280x1024i
include=1280x1024i
multisync = 1376x1024
include=1376x1024
, and some of these by reference:
include = 640x480 # 60Hz, 31.5KHz
clock=25.175
shb=664 ehb=760 ht=800
vrs=491 vre=493 vt=525
include = 640x480@72Hz # 72Hz, 38.5KHz
clock=32
shb=664 ehb=704 ht=832
vrs=489 vre=492 vt=520
include = 800x600 # 60Hz, 37.9KHz
defaultclock=40
shb=840 ehb=1000 ht=1056
vrs=605 vre=607 vt=633
include = 1024x768i # 87Hz, 35.5KHz
defaultclock=44.9
shb=1048 ehb=1208 ht=1264
vrs=776 vre=784 vt=817
interlace=v
include = 1024x768@60Hz # 60Hz, 48.4KHz
defaultclock=65
shb=1032 ehb=1176 ht=1344
shs=1056
vrs=771 vre=777 vt=806
hsync=- vsync=-
include = 1024x768 # 70Hz, 57.2KHz
defaultclock=75
shb=1096 ehb=1232 ht=1328
shs=1072
vrs=771 vre=777 vt=806
hsync=- vsync=-
include = 1280x1024i # 87Hz, 48KHz
defaultclock=80
shb=1312 ehb=1528 ht=1576
vrs=1028 vre=1034 vt=1105
interlace=v
include = 1280x1024@60Hz # 60Hz, 63.9KHz
defaultclock=110
shb=1312 ehb=1496 ht=1720 # All from
xvidtune
vrs=1025 vre=1028 vt=1074
include = 1280x1024 # 74Hz, 79.6KHz
defaultclock=135
shb=1376 ehb=1544 ht=1712
shs=1392
vrs=1028 vre=1034 vt=1075
include = 1376x1024 # 70Hz, 75.3KHz
defaultclock=135
shb=1440 ehb=1616 ht=1792
vrs=1032 vre=1040 vt=1075
include = 1152x900@70Hz # 72Hz,
67.9KHz
clock=100
shb=1184 ehb=1376 ht=1472
vrs=900 vre=902 vt=940
#hsync=- vsync=-
Heres my current vgainfo.txt:
main->snarf
vga->snarf
mga2164w->snarf
x[0]=1
x[1]=2
x[2]=255
x[3]=255
probe found 4 megabytes
vga->dump
vga misc 67
vga feature 00
vga sequencer 03 00 03 00 02
vga crt 60 4F 50 83 55 81 BF 1F - 00 4F 0D 0E 00 00 07 80
9C 8E 8F 28 1F 96 B9 A3 - FF
vga graphics 00 00 00 00 00 10 0E 00 - FF
vga attribute 00 01 02 03 04 05 14 07 - 38 39 3A 3B 3C 3D 3E 3F
0C 00 0F 08 00
vga vmz 4194304
vga apz 0
vga linear 1
vga->attr: 0xC002D=MATROX/MILLENNIUM VGA/VBE BIOS (V2.3 )
mga2164w->dump
mga2164w Devctrl 28000A3
mga2164w Option 5F2C0100
mga2164w Crtcext 00 00 00 00 00 00
mga2164w TVP FF 11 11 11 11 11 00 00 - 00 00 00 00 00 00 00 06
06 06 06 06 06 06 06 06 - 80 98 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 1E EE B2 71 B2
FF FF FF FF FF FF FF FF - 00 18 00 EF 00 00 00 26
mga2164w PCLK FD 3A B2
mga2164w MCLK FD 3A B2
mga2164w LCLK BF 3F B2
mga2164whwgc->dump
mga2164whwgc Devctrl28000A3
mga2164whwgc Option 5F2C0100
mga2164whwgc Crtcext 00 00 00 00 00 00
mga2164whwgc TVP FF 11 11 11 11 11 00 00 - 00 00 00 00 00 00 00 06
06 06 06 06 06 06 06 06 - 80 98 00 00 00 00 00 00
00 00 00 00 00 00 00 00 - 00 00 00 1E EE B2 71 B2
FF FF FF FF FF FF FF FF - 00 18 00 EF 00 00 00 26
mga2164whwgc PCLK FD 3A B2
mga2164whwgc MCLK FD 3A B2
mga2164whwgc LCLK BF 3F B2
vmf 25175000 vmdf 0 vf1 0 vbw 65000000
mga2164w->options
vga->init
mga2164w->init
pixbuswidth=64
dbdumpmode
type=cpd-1304, size=640x480x8
frequency=25175000
x=640 (0x280), y=480 (0x1E0), z=8 (0x8)
ht=808 (0x328), shb=664 (0x298), ehb=760 (0x2F8)
shs=664 (0x298), ehs=760 (0x2F8)
vt=525 (0x20D), vrs=491 (0x1EB), vre=493 (0x1ED)
hsync=0, vsync=0, interlace=0
vga->dump
vga flag Fdump|Finit|Fsnarf
vga misc EB
vga feature 00
vga sequencer 03 01 0F 00 0A
vga crt 60 4F 4F 84 53 9F20B 3E - 00 40 00 00 00 00 00 00
1EB 2D1DF 28 001DF20C E3 -7FF
vga graphics 00 00 00 00 00 50 05 0F - FF
vga attribute 00 01 02 03 04 05 06 07 - 08 09 0A 0B 0C 0D 0E 0F
41 FF 0F 00 00
vga clock[0] f 25175000
vga clock[0] d i m 0 0 - 21
vga clock[0] n p q r 40 3 - 0 0
vga clock[1] f 3725160
vga clock[1] d i m 0 0 - 61
vga clock[1] n p q r 33 3 - 14 0
vga vmz 4194304
vga apz 0
vga linear 1
vga->attr: 0xC002D=MATROX/MILLENNIUM VGA/VBE BIOS (V2.3 )
mga2164w->dump
mga2164w flag Ulinear|Fdump|Finit|Foptions|Fsnarf
mga2164w Devctrl 28000A3
mga2164w Option 5F2C1100
mga2164w Crtcext 00 40 00 80 00 00
mga2164w TVP FF 11 11 11 11 11 00 00 - 00 00 00 00 00 00 00 06
06 06 06 06 06 06 06 06 - 80 4C 25 00 00 00 04 00
00 00 00 00 00 00 00 00 - 00 00 00 1E EE B2 71 B2
FF FF FF FF FF FF FF FF - 00 3E 00 EF 00 00 00 26
mga2164w PCLK E8 15 B3
mga2164w MCLK FD 3A B2
mga2164w LCLK E1 3D F3
mga2164whwgc->dump
mga2164whwgc flag Fdump
mga2164whwgc Devctrl28000A3
mga2164whwgc Option 5F2C1100
mga2164whwgc Crtcext 00 40 00 80 00 00
mga2164whwgc TVP FF 11 11 11 11 11 00 00 - 00 00 00 00 00 00 00 06
06 06 06 06 06 06 06 06 - 80 4C 25 00 00 00 04 00
00 00 00 00 00 00 00 00 - 00 00 00 1E EE B2 71 B2
FF FF FF FF FF FF FF FF - 00 3E 00 EF 00 00 00 26
mga2164whwgc PCLK E8 15 B3
mga2164whwgc MCLK FD 3A B2
mga2164whwgc LCLK E1 3D F3
main->exits
Thanks! I hope someone can help with this. I would really like to
start to use plan 9!
-Justin
PS I like glenda.
Sent via Deja.com http://www.deja.com/
Before you buy.
From 9fans@cse.psu.edu Mon Nov 20 10:57:27 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Mon, 20 Nov 2000 10:57:27 GMT
Subject: [9fans] Promela
Message-ID: <8v38em$baf$1@nnrp1.deja.com>
Have anybody here programmed "The Bakery Algorithm" in promela? If
that's the case, I would appreciate to have a look at it.
Sent via Deja.com http://www.deja.com/
Before you buy.
From 9fans@cse.psu.edu Mon Nov 20 10:56:07 2000
From: 9fans@cse.psu.edu (Alt)
Date: Mon, 20 Nov 2000 10:56:07 GMT
Subject: [9fans] Plaen Nien with 16 MB.
Message-ID: <3A132470.FBC642B8@card.kyiv.net>
Hello there.
Is it possible to run plan 9 at machine with16 mb.
It refuse to be runned at 16 but there is written that it could work at
16 like terminal.
Finally, is such memory really requaired for such small OS like Plan9 ?
Bye.
--Alt.
From 9fans@cse.psu.edu Mon Nov 20 10:55:48 2000
From: 9fans@cse.psu.edu (George Michaelson)
Date: Mon, 20 Nov 2000 10:55:48 GMT
Subject: [9fans] Matrox G400 dev recog via vgadb
Message-ID: <974289235.997283@eeyore.dstc.edu.au>
Ok so I tried the bleeding obvious and stabbed the VGA dev string
back into vgadb. The string added to vgadb was:
0xC002D="MATROX/Matrox G400 VGA/VBE BIOS (V1.5)" # Millennium II
(I'm guessing that #comment rules apply so not changing the comment didn't
freak this file)
It done this:
main->snarf
vga->snarf
mga2164w->snarf
sequencer->enter on
sequencer->leave on
mga2164w: no Pcidev with Vid=0x102B, Did=0x051[9BF] or 0x521
interestingly the floppy is now unreadable. thats a brand new imation disk
out of a box. maybe debug writeback smashes FAT structure sometimes?
cheers
-George
From 9fans@cse.psu.edu Mon Nov 20 10:55:32 2000
From: 9fans@cse.psu.edu (George Michaelson)
Date: Mon, 20 Nov 2000 10:55:32 GMT
Subject: [9fans] Matrox G400 any closer to working?
Message-ID: <974287617.283470@eeyore.dstc.edu.au>
nnnnnnNNNNNNNNNGH! aw. damn. so near and yet....
Gee. almost there. its nice to get dumped to a prompt that
responds to ls. Of course, mandatory humour probably dictated
it was a CSH % instead of a SH $ -but surely a large ? would have
been more fitting?
Silly question but since almost all VGA cards work at 640x480
from base VGA frobs, why is install demanding higher rez driver state?
[If anyone has a simple canned recipe to stash on a 9disk.9fd for a Matrox
G400 I'd love it...]
cheers
-George
From 9fans@cse.psu.edu Mon Nov 20 10:55:16 2000
From: 9fans@cse.psu.edu (Chris Locke)
Date: Mon, 20 Nov 2000 10:55:16 GMT
Subject: [9fans] AFS-client for Plan9 - ?
References: , <01db01c04e8d$692a29a0$0ab9c6d4@cybercable.fr>
Message-ID: <974282820.25325.0.nnrp-08.d4f0e306@news.demon.co.uk>
The kernel cannot close the fds if the machine has crashed.
The original post said "if the local machine crashes".
This can also be read as "some numskul knocked
the reset button / kicked the power lead out /
raccoon sat on local power transformer etc. etc."
Chris.
From 9fans@cse.psu.edu Mon Nov 20 10:54:59 2000
From: 9fans@cse.psu.edu (Wilhelm B. Kloke)
Date: Mon, 20 Nov 2000 10:54:59 GMT
Subject: [9fans] FreeBSD IL and 9P patches
References:
Message-ID: <8utf8q$27ul$1@yorikke.arb-phys.uni-dortmund.de>
In article ,
Christopher Nielsen wrote:
>I've been working on updating the IL and 9P patches for
>FreeBSD so that they apply to the current head branch.
>
>My intention is to get the code committed to the FreeBSD
>source tree. If the original author doesn't have the time to
>act as maintainer, I'm willing to do that.
Very good. I would appreciate, if you announce a place where to find your
work, in case the commit procedure lasts longer.
BTW. Are there chances that the patches apply to 4.0 or do I have to
upgrade first?
--
Dipl.-Math. Wilhelm Bernhard Kloke
Institut fuer Arbeitsphysiologie an der Universitaet Dortmund
Ardeystrasse 67, D-44139 Dortmund, Tel. 0231-1084-257
From 9fans@cse.psu.edu Mon Nov 20 10:54:44 2000
From: 9fans@cse.psu.edu (Greg Shubin)
Date: Mon, 20 Nov 2000 10:54:44 GMT
Subject: [9fans] connecting to ISP with PAP?
References: <20001114195151.5AA83199DC@mail.cse.psu.edu>
Message-ID: <3A11C5C3.AE86BE1A@sonic.net>
David Gordon Hogan wrote:
> there is a Short Term Facilities Issue with my new line, but
> they won't say what it is.
>
It means they haven't built the CO within 17kft of your location.
From 9fans@cse.psu.edu Mon Nov 20 10:56:58 2000
From: 9fans@cse.psu.edu (George Michaelson)
Date: Mon, 20 Nov 2000 10:56:58 GMT
Subject: [9fans] Matrox G400 driver status
Message-ID: <974420680.55422@eeyore.dstc.edu.au>
I posted two on this, but neither showed up in my local newsthread
leading me to suspect a mail:news g/w died. Thatm, or my incoherance
did me no favours again.
booting with an otherwise normal plan9.9fd I got the predictable:
> aux/vga: controller not in /lib/vgadb
> 0xC0000 55 AA 40 EB 7B 15 D0 03 A0 04 E0 0B 7E 31 1A 0C U.@.{.......~1..
> 0xC0010 24 0C FF FF 00 00 00 00 60 00 00 00 00 20 49 42 $.......`.... IB
> 0xC0020 4D 20 43 4F 4D 50 41 54 49 42 4C 45 20 4D 41 54 M COMPATIBLE MAT
> 0xC0030 52 4F 58 2F 4D 61 74 72 6F 78 20 47 34 30 30 20 ROX/Matrox G400
> 0xC0040 56 47 41 2F 56 42 45 20 42 49 4F 53 20 28 56 31 VGA/VBE BIOS (V1
> 0xC0050 2E 35 29 20 62 32 32 20 00 87 DB 87 DB 87 DB 90 .5) b22 ........
> 0xC0060 50 43 49 52 2B 10 25 05 00 00 18 00 00 00 00 03 PCIR+.%.........
> 0xC0070 40 00 15 16 00 80 00 00 38 39 37 2D 31 35 00 FF @.......897-15..
> 0xC0080 55 33 C0 8E D8 8E C0 E8 4D 59 2E 89 1E F2 7F BF U3......MY......
> 0xC0090 08 00 B0 08 90 E8 AD 58 2E 88 0E F4 7F E8 02 01 .......X........
> 0xC00A0 E8 94 56 2E 8B 1E F2 7F 2E 8B 1E F2 7F E8 03 2B ..V............+
> 0xC00B0 BF 43 00 90 B0 08 90 E8 8B 58 80 C9 10 B0 0B 90 .C.......X......
> 0xC00C0 E8 82 58 BF 08 00 B0 08 90 E8 79 58 80 F9 02 75 ..X.......yX...u
> 0xC00D0 13 B1 1A 90 90 E8 6E 5C 80 C9 40 8A E9 B1 1A 90 ......n\..@.....
> 0xC00E0 90 E8 47 5C 2E F6 06 B5 7A 04 74 13 BF 40 00 90 ..G\....z.t..@..
> 0xC00F0 B0 08 90 E8 4F 58 80 C9 40 B0 0B 90 E8 46 58 E8 ....OX..@....FX.
> main->snarf
> vga->snarf
> vga->dump
> vga misc 67
> vga feature 00
> vga sequencer 03 00 03 00 02
> vga crt 5F 4F 50 82 55 81 BF 1F - 00 4F 0D 0E 00 00 07 80
> 9C 8E 8F 28 1F 96 B9 A3 - FF
> vga graphics 00 00 00 00 00 10 0E 00 - FF
> vga attribute 00 01 02 03 04 05 14 07 - 38 39 3A 3B 3C 3D 3E 3F
> 0C 00 0F 08 00
> vga apz 0
> vga linear 0
>
> vmf 25175000 vmdf 0 vf1 0 vbw 0
> vga->init
> dbdumpmode
> type=vga, size=640x480x1
> frequency=25175000
> x=640 (0x280), y=480 (0x1E0), z=1 (0x1)
> ht=800 (0x320), shb=664 (0x298), ehb=760 (0x2F8)
> shs=664 (0x298), ehs=760 (0x2F8)
> vt=525 (0x20D), vrs=491 (0x1EB), vre=493 (0x1ED)
> hsync=0, vsync=0, interlace=0
> vga->dump
> vga flag Fdump|Finit|Fsnarf
> vga misc E3
> vga feature 00
> vga sequencer 03 01 0F 00 06
> vga crt 5F 4F 52 9F 53 1F20B 3E - 00 40 00 00 00 00 00 00
> 1EB 2D1DF 28 001EB1EC C3 -7FF
> vga graphics 00 00 00 00 00 00 05 0F - FF
> vga attribute 00 01 02 03 04 05 06 07 - 08 09 0A 0B 0C 0D 0E 0F
> 01 FF 0F 00 00
> vga apz 0
> vga linear 0
>
> main->exits
I added the device probe string for my Matrox G400 into vgadb but
all it does it make the boot floppy print a different failure:
> main->snarf
> vga->snarf
> mga2164w->snarf
> sequencer->enter on
> sequencer->leave on
> mga2164w: no Pcidev with Vid=0x102B, Did=0x051[9BF] or 0x521
I'm guessing the black art of making mostly similar cards work is
not as simple as I'd hoped.
Has anyone progressed further here? is there a new hwgc entry or
something binaryish which is defeating me?
cheers
-George
PS first one to hit me with a 'buy an obsolete card and stick it in'
gets a free hollerith card pre-printed for basic-by-numbers coding.
I have a ream of them, they make good roaches if you don't mind the ink...
From 9fans@cse.psu.edu Mon Nov 20 10:56:21 2000
From: 9fans@cse.psu.edu (Douglas A. Gwyn)
Date: Mon, 20 Nov 2000 10:56:21 GMT
Subject: [9fans] AFS-client for Plan9 - ?
References: , <01db01c04e8d$692a29a0$0ab9c6d4@cybercable.fr>
Message-ID: <3A14156C.952BDDA2@arl.army.mil>
Boyd Roberts wrote:
> here we go. the kernel closes the fd's as a part of exit,
> like td said.
Further, upon return from main(), all the exit() actions
are performed.
_exit(), on the other hand, does not perform any stdio.
(Its main use is in a child branch of a fork.)
From 9fans@cse.psu.edu Mon Nov 20 10:56:33 2000
From: 9fans@cse.psu.edu (Douglas A. Gwyn)
Date: Mon, 20 Nov 2000 10:56:33 GMT
Subject: [9fans] Installation on Solaris platform
Message-ID: <3A1414EB.44E93448@arl.army.mil>
After considerable wasted effort, I think I have finally
figured out the main culprit thwarting my attempts to get
multiple OSes including Plan 9 installed on a single disk.
Apparently the 10MB "x86 boot" partition that Solaris 8
really wants to use messes up something in the partition
table and possibly in boot blocks in other partitions.
Anyway, when I forced an installation without the x86
boot partition, all four OSes (WinMe, Win2K Pro, Plan9r3,
Solaris8) ended up being bootable and useable. (I'm using
System Commander to handle the various multiboot tasks.)
Anybody else having similar problems might try this.
From 9fans@cse.psu.edu Mon Nov 20 10:57:49 2000
From: 9fans@cse.psu.edu (James)
Date: Mon, 20 Nov 2000 10:57:49 GMT
Subject: [9fans] Ati Xpert 98 Video card
Message-ID: <%yyR5.149579$ib7.19937854@news1.rdc1.nj.home.com>
I should have no problem using a Ati-Xpert video card with Plan 9. Should I
get PCI or AGP?
The Ati Mach64 is 2mb video card?
James
From 9fans@cse.psu.edu Mon Nov 20 10:58:14 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Mon, 20 Nov 2000 10:58:14 GMT
Subject: [9fans] troubles: nevermind
Message-ID: <8v6ru9$3qt$1@nnrp1.deja.com>
I would have answered my own post about the Matrox video card not
working but it hasn't appeared yet. I changed my plan9.ini to 800x600
like the default on the boot disk creation page, and it worked fine.
Thanks
Justin
Sent via Deja.com http://www.deja.com/
Before you buy.
From baruchel.arrobas.libertysurf.point.fr@news4.isdnet.net Mon Nov 20 10:59:00 2000
From: baruchel.arrobas.libertysurf.point.fr@news4.isdnet.net (Thomas Baruchel)
Date: Mon, 20 Nov 2000 10:59:00 GMT
Subject: [9fans] Do you think I can use Plan9 ?
Message-ID: <8v9ad2$25ad$2@news4.isdnet.net>
Brest, le dimanche 19 novembre
Hi, I'm a linux man (tired of linux). I have an old computer and I'm
wondering what I can put in it. I tried several versions of Linux, Minix,
Minix-VMD.
I have 8Mo RAM, and two hard disks: 240Mo + 204Mo + 486processor
For a poetical reason, I think of putting Plan9 in it...
(why? well, because I like sam the editor...)
Do you think it's a good idea ?
I downloaded the install floppy, and it didn't work! I don't remember why, but
if you think it should work, I can try again.
I also have a CD-ROM (is there a way of getting the CD distribution ?)
Is there a way of putting a small part of Plan 9 (like I can do with
Linux: I only use three tools: groff, ghostview, and an editor).
I don't know anything else about Plan9 (except that I really like SAM :-)
--
.~. Thomas Baruchel
/V\ baruchel@libertysurf.fr
// \\ Brest
/( )\ FRANCE
^`~'^
From steve.simon@snellwilcox.com Mon Nov 20 11:08:40 2000
From: steve.simon@snellwilcox.com (steve.simon@snellwilcox.com)
Date: Mon, 20 Nov 2000 11:08:40 +0000
Subject: [9fans] Re: Plan 9 on notebooks
Message-ID: <2240966830@snellwilcox.com>
I use an NEC Versa SX (listed in the HCL) at 1024x768
which runs out of the box beautifully.
-Steve
From 9fans@cse.psu.edu Mon Nov 20 11:34:35 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Mon, 20 Nov 2000 11:34:35 0000
Subject: [9fans] Matrox cards - state of the nation
Message-ID:
Following the sudden resumption of mail to news service,
several emails have appeared about Matrox Millenium and
G series cards. Rather than reply individually, I'll summarise.
The status of the release code is as follows:
1. I have a Millenium and a Millenium II (both PCI). These both
work. There is a possibility that the NOBIOS option in pc/pci.c
might be needed on certain machines, which hints at a small
initialisation problem, but otherwise fine.
2. Only 8 bits per pixel works.
3. Cards with daughterboard memory upgrades are unproven.
They may well work, but I have no means to test.
4. You CANNOT persuade a G series card to work by just
playing with /lib/vgadb. The RAMDACs are different.
I have some improved code with
1. G series support. It work on a G400 MAX 32mb. Can't
promise the others. There are changes to aux/vga,
lib/vgadb, and 9/pc
2. Hardware acceleration. This works like a dream for the
Millenium and Millenium II, but severely slows down (!)
the G400, and corrupts the screen. More work required
here clearly. However, the acceleration is all that the
reputation of Matrox says.
If anyone with the ability to recompile the kernel wants
to do some testing, let me know.
From 9fans@cse.psu.edu Mon Nov 20 13:24:48 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Mon, 20 Nov 2000 14:24:48 +0100
Subject: [9fans] AFS-client for Plan9 - ?
References: , <01db01c04e8d$692a29a0$0ab9c6d4@cybercable.fr> <3A14156C.952BDDA2@arl.army.mil>
Message-ID: <009201c052f5$420a2480$0ab9c6d4@cybercable.fr>
From: Douglas A. Gwyn
> Boyd Roberts wrote:
> > here we go. the kernel closes the fd's as a part of exit,
> > like td said.
>
> Further, upon return from main(), all the exit() actions
> are performed.
>
> _exit(), on the other hand, does not perform any stdio.
> (Its main use is in a child branch of a fork.)
absolutely correct.
From 9fans@cse.psu.edu Mon Nov 20 15:25:10 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Mon, 20 Nov 2000 15:25:10 0000
Subject: [9fans] AFS-client for Plan9 - ?
Message-ID: <20001120142304.0AD6B199D5@mail.cse.psu.edu>
This is a multi-part message in MIME format.
--upas-stdzsrugwcppxrixpqxkzcaiid
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
however, it's worth remembering, that in the Unix i remember at any
rate, _exit() is not always invoked on program exit. it isn't invoked
if the program dies from a signal, for instance.
i've always presumed that the final close of fds is done when their
refcount drops to zero, i.e. when the exited process's file table is
cleared up by the kernel.
so the actual _?exit() system calls are not that crucial to the issue
of file closing under AFS. stdio is a different matter, of course.
but i'm not entirely sure whether we're on topic here... :-)
cheers,
rog.
--upas-stdzsrugwcppxrixpqxkzcaiid
Content-Type: message/rfc822
Content-Disposition: inline
Return-Path: <9fans-admin@cse.psu.edu>
Received: from punt-2.mail.demon.net by mailstore for rog@vitanuova.com
id 974726793:20:12387:2; Mon, 20 Nov 2000 13:26:33 GMT
Received: from psuvax1.cse.psu.edu ([130.203.4.6]) by punt-2.mail.demon.net
id aa2106586; 20 Nov 2000 13:26 GMT
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.20.6])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP
id ABA7A19A00; Mon, 20 Nov 2000 08:26:09 -0500 (EST)
Received: from lafontaine.cybercable.fr (lafontaine.cybercable.fr [212.198.0.202])
by mail.cse.psu.edu (CSE Mail Server) with SMTP id 280DE199D5
for <9fans@cse.psu.edu>; Mon, 20 Nov 2000 08:24:59 -0500 (EST)
Received: (qmail 9761311 invoked from network); 20 Nov 2000 13:24:53 -0000
Received: from d010.dhcp212-185.cybercable.fr (HELO coma) ([212.198.185.10]) (envelope-sender )
by lafontaine.cybercable.fr (qmail-ldap-1.03) with SMTP
for <9fans@cse.psu.edu>; 20 Nov 2000 13:24:53 -0000
Message-ID: <009201c052f5$420a2480$0ab9c6d4@cybercable.fr>
To:
References: , <01db01c04e8d$692a29a0$0ab9c6d4@cybercable.fr> <3A14156C.952BDDA2@arl.army.mil>
Subject: Re: [9fans] AFS-client for Plan9 - ?
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: cse.psu.edu!9fans-admin
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0rc1
Precedence: bulk
Reply-To: cse.psu.edu!9fans
List-Id: Fans of the O/S Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive:
Date: Mon, 20 Nov 2000 14:24:48 +0100
From: Douglas A. Gwyn
> Boyd Roberts wrote:
> > here we go. the kernel closes the fd's as a part of exit,
> > like td said.
>
> Further, upon return from main(), all the exit() actions
> are performed.
>
> _exit(), on the other hand, does not perform any stdio.
> (Its main use is in a child branch of a fork.)
absolutely correct.
--upas-stdzsrugwcppxrixpqxkzcaiid--
From 9fans@cse.psu.edu Mon Nov 20 16:56:10 2000
From: 9fans@cse.psu.edu (Scott Schwartz)
Date: Mon, 20 Nov 2000 11:56:10 -0500
Subject: [9fans] Plaen Nien with 16 MB.
In-Reply-To: Message from Alt
of "Mon, 20 Nov 2000 10:56:07 GMT." <3A132470.FBC642B8@card.kyiv.net>
Message-ID: <20001120165610.23183.qmail@g.bio.cse.psu.edu>
| Is it possible to run plan 9 at machine with16 mb.
| It refuse to be runned at 16 but there is written that it could work at
| 16 like terminal.
I ran the Second Edition ran in 16MB for a while. On the other hand,
you really want more in a terminal, because the window system is in-kernel
and needs lots of ram for windows.
From 9fans@cse.psu.edu Mon Nov 20 17:18:43 2000
From: 9fans@cse.psu.edu (Mike Fletcher)
Date: Mon, 20 Nov 2000 11:18:43 -0600 (CST)
Subject: [9fans] drawterm via ssh
In-Reply-To: <20001120165610.23183.qmail@g.bio.cse.psu.edu>
Message-ID:
I tried to post this to comp.os.plan9, but it didn't make it.
I have Plan9 (rel3) running on a Pentium as a cpu and auth
server. Ssh works fine as client and server between the Plan9
system and my SPARCstation running Solaris 8.
I compiled drawterm on the SPARC and it works fine as well.
Now how do I persuade the ssh server on Plan9 to forward the
drawterm connection through the secure channel? There doesn't
seem to be a dedicated port to forward - or am I missing some-
thing fundamental here?
Any help will be greatly appreciated.
Thanks,
-Mike Fletcher
From 9fans@cse.psu.edu Mon Nov 20 19:22:31 2000
From: 9fans@cse.psu.edu (Russ Cox)
Date: Mon, 20 Nov 2000 14:22:31 -0500
Subject: [9fans] drawterm via ssh
Message-ID: <20001120192247.B2DE7199F0@mail.cse.psu.edu>
The Plan 9 ssh server doesn't do any port forwarding.
Russ
From 9fans@cse.psu.edu Mon Nov 20 20:48:57 2000
From: 9fans@cse.psu.edu (Russ Cox)
Date: Mon, 20 Nov 2000 15:48:57 -0500
Subject: [9fans] memory
Message-ID: <20001120204900.B527B199F0@mail.cse.psu.edu>
The install, because it keeps the file system
in RAM, requires 32MB. I've done an install on a 32MB
system and I was using pretty much all the memory.
As others have pointed out, that's mainly because
the image data is all kept in kernel memory, and the
compressed file system on the floppy is expanded
and kept in memory while being accessed.
You could run a simple 640x480x8 terminal with
16MB, but I'm not sure how much can be done with
only 8MB.
The ATI video cards come with a wide range of
memory depending mainly on the age of the card.
Others have reported trying the Xpert98 but I don't
remember whether the reports were good or bad.
Russ
From 9fans@cse.psu.edu Mon Nov 20 21:11:57 2000
From: 9fans@cse.psu.edu (David Gordon Hogan)
Date: Mon, 20 Nov 2000 16:11:57 -0500
Subject: [9fans] connecting to ISP with PAP?
Message-ID: <20001120211159.620C8199EB@mail.cse.psu.edu>
gshubin@sonic.net writes:
> > there is a Short Term Facilities Issue with my new line, but
> > they won't say what it is.
> >
>
> It means they haven't built the CO within 17kft of your location.
Actually, no it doesn't mean that.
From 9fans@cse.psu.edu Mon Nov 20 21:04:28 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Mon, 20 Nov 2000 22:04:28 +0100
Subject: [9fans] memory
References: <20001120204900.B527B199F0@mail.cse.psu.edu>
Message-ID: <014801c05335$7ab617e0$0ab9c6d4@cybercable.fr>
From: Russ Cox
> You could run a simple 640x480x8 terminal with
> 16MB, but I'm not sure how much can be done with
> only 8MB.
i got the 2nd release installed wih 4mb, but i
had to do it in stages; the uncompression just
took the machine out. it did it piecemeal.
once i'd done it 4Mb was just not enough. you
could get 8 1/2, sam and maybe a window or two.
finally it would choke.
8Mb would have been better, but i reckon 16Mb
would have been the minimum.
From cnielsen@pobox.com Mon Nov 20 21:37:59 2000
From: cnielsen@pobox.com (Christopher Nielsen)
Date: Mon, 20 Nov 2000 13:37:59 -0800 (PST)
Subject: [9fans] FreeBSD IL and 9P patches
In-Reply-To: <8utf8q$27ul$1@yorikke.arb-phys.uni-dortmund.de>
Message-ID:
On Mon, 20 Nov 2000, Wilhelm B. Kloke wrote:
> Very good. I would appreciate, if you announce a place
> where to find your work, in case the commit procedure
> lasts longer. BTW. Are there chances that the patches
> apply to 4.0 or do I have to upgrade first?
I will announce where to retrieve the patches as soon as
I've completed and tested them.
My first priority is to get them updated for -current, but I
will also work on getting them merged into -stable.
--
Christopher Nielsen
cnielsen@pobox.com
From 9fans@cse.psu.edu Mon Nov 20 21:49:38 2000
From: 9fans@cse.psu.edu (Mike Haertel)
Date: Mon, 20 Nov 2000 13:49:38 -0800 (PST)
Subject: [9fans] memory
In-Reply-To: <20001120204900.B527B199F0@mail.cse.psu.edu>
Message-ID: <200011202149.eAKLncI15212@ducky.net>
>The ATI video cards come with a wide range of
>memory depending mainly on the age of the card.
>Others have reported trying the Xpert98 but I don't
>remember whether the reports were good or bad.
I have Xpert 98's (both AGP and PCI) and they
work really well.
From 9fans@cse.psu.edu Tue Nov 21 09:38:01 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Tue, 21 Nov 2000 09:38:01 GMT
Subject: [9fans] Re: Do you think I can use Plan9 ?
References: <8v9ad2$25ad$2@news4.isdnet.net>
Message-ID: <8vd8vf$u9n$1@nnrp1.deja.com>
You can download a version of Sam editor for MSWindows from
ftp://netlib.bell-labs.com/netlib/research/sam.exe .
For installation of Plan 9 you will need (download):
1) an image of install floppy
2) distribution file - plan9.9gz (cca 57MB)
You can install it on standalone PC. But full Plan 9 OS runs on minimal
3 PCs - fileserver, cpuserver and terminal.
Read docs about required hardware configuration. (I think you will need
more than 8MB RAM)
vecera
> Hi, I'm a linux man (tired of linux). I have an old computer and I'm
> wondering what I can put in it. I tried several versions of Linux,
Minix,
> Minix-VMD.
> I have 8Mo RAM, and two hard disks: 240Mo + 204Mo + 486processor
> For a poetical reason, I think of putting Plan9 in it...
> (why? well, because I like sam the editor...)
> Do you think it's a good idea ?
> I downloaded the install floppy, and it didn't work! I don't remember
why, but
> if you think it should work, I can try again.
> I also have a CD-ROM (is there a way of getting the CD distribution ?)
> Is there a way of putting a small part of Plan 9 (like I can do with
> Linux: I only use three tools: groff, ghostview, and an editor).
> I don't know anything else about Plan9 (except that I really like SAM
:-)
>
> --
> .~. Thomas Baruchel
> /V\ baruchel@libertysurf.fr
> // \\ Brest
> /( )\ FRANCE
> ^`~'^
>
Sent via Deja.com http://www.deja.com/
Before you buy.
From 9fans@cse.psu.edu Tue Nov 21 09:37:48 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Tue, 21 Nov 2000 09:37:48 GMT
Subject: [9fans] Re: Ati Xpert 98 Video card
References: <%yyR5.149579$ib7.19937854@news1.rdc1.nj.home.com>
Message-ID: <8vd7jt$teg$1@nnrp1.deja.com>
> I should have no problem using a Ati-Xpert video card with Plan 9.
Should I
> get PCI or AGP?
> The Ati Mach64 is 2mb video card?
> James
I had another Mach64 video card - ATI 3D Charger on AGP with 8 MB RAM.
But with this card I had problems - it produced some flickers on screen.
Later I have tryed another ATI 3D Charger on AGP with 4 MB RAM.
The screen looks better but some noise remain. I dodn't know why...
But autors say the ATI cards have the best support.(?)
vecera
Sent via Deja.com http://www.deja.com/
Before you buy.
From 9fans@cse.psu.edu Tue Nov 21 09:37:19 2000
From: 9fans@cse.psu.edu (James)
Date: Tue, 21 Nov 2000 09:37:19 GMT
Subject: [9fans] Re: Do you think I can use Plan9 ?
References: <8v9ad2$25ad$2@news4.isdnet.net>
Message-ID:
I tried to put Plan 9 on a P 100, with 16mb memory. It told me I had no
physical memory. Do to some hardware restrictions that I ran into (from old
P 100Mhz to new Geforce Video Cards) It was easier for me to build a Plan 9
box, now that would be poetical and artful. Compuvest1.com has the best Plan
9 compatible parts that I found and real cheap too, even Mach64 videocards.
Good Luck
James
"Thomas Baruchel" wrote in message
news:8v9ad2$25ad$2@news4.isdnet.net...
> Brest, le dimanche 19 novembre
>
> Hi, I'm a linux man (tired of linux). I have an old computer and I'm
> wondering what I can put in it. I tried several versions of Linux, Minix,
> Minix-VMD.
> I have 8Mo RAM, and two hard disks: 240Mo + 204Mo + 486processor
> For a poetical reason, I think of putting Plan9 in it...
> (why? well, because I like sam the editor...)
> Do you think it's a good idea ?
> I downloaded the install floppy, and it didn't work! I don't remember why,
but
> if you think it should work, I can try again.
> I also have a CD-ROM (is there a way of getting the CD distribution ?)
> Is there a way of putting a small part of Plan 9 (like I can do with
> Linux: I only use three tools: groff, ghostview, and an editor).
> I don't know anything else about Plan9 (except that I really like SAM :-)
>
> --
> .~. Thomas Baruchel
> /V\ baruchel@libertysurf.fr
> // \\ Brest
> /( )\ FRANCE
> ^`~'^
From 9fans@cse.psu.edu Tue Nov 21 09:37:35 2000
From: 9fans@cse.psu.edu (Greg Shubin)
Date: Tue, 21 Nov 2000 09:37:35 GMT
Subject: [9fans] connecting to ISP with PAP?
References: <20001120211159.620C8199EB@mail.cse.psu.edu>
Message-ID: <3A19B270.624F11B@sonic.net>
David Gordon Hogan wrote:
> gshubin@sonic.net writes:
> > > there is a Short Term Facilities Issue with my new line, but
> > > they won't say what it is.
> > >
> >
> > It means they haven't built the CO within 17kft of your location.
>
> Actually, no it doesn't mean that.
For the sense-of-humor impaired and/or phone company employees, here are
some smileys. Insert as needed.
:-) :-) :-) :-) :) :) :) :) .
From 9fans@cse.psu.edu Tue Nov 21 12:13:36 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Tue, 21 Nov 2000 12:13:36 GMT
Subject: [9fans] wanted icon "Powered by Plan 9"
Message-ID: <8vdok1$a0t$1@nnrp1.deja.com>
Hi,
I play with HTML on my home site and I would like to place there icon
"Powered by Plan 9". Is any on the world?
vecera
Sent via Deja.com http://www.deja.com/
Before you buy.
From 9fans@cse.psu.edu Tue Nov 21 13:28:57 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Tue, 21 Nov 2000 08:28:57 -0500
Subject: [9fans] memory
Message-ID: <20001121132859.17D13199E1@mail.cse.psu.edu>
This is a multi-part message in MIME format.
--upas-kwelspvbqvnazfwqvgicyftsho
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
I was running an 8MB system until 6 months ago. However, it
would go into swap hell if I tried to make kernels
locally. It was only usable because I did most things were
done on a cpu server.
With 16mb, you can still run bigger screens than 640x480x8.
at 16MB on a terminal the kernel gives 60% of the memory to
the kernel. You can make it more still if you want by
including in plan9.ini
*kernelpercent=90
for example, to get 90%. Of course, that leaves precious little
for processes.
--upas-kwelspvbqvnazfwqvgicyftsho
Content-Type: message/rfc822
Content-Disposition: inline
Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Mon Nov 20 15:50:21 EST 2000
Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Mon Nov 20 15:50:21 EST 2000
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.20.6])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP
id 39BC7199F4; Mon, 20 Nov 2000 15:50:10 -0500 (EST)
Received: from plan9.cs.bell-labs.com (plan9.bell-labs.com [204.178.31.2])
by mail.cse.psu.edu (CSE Mail Server) with SMTP id B527B199F0
for <9fans@cse.psu.edu>; Mon, 20 Nov 2000 15:49:00 -0500 (EST)
Received: from ovid.cs.bell-labs.com ([135.104.50.34]) by plan9; Mon Nov 20 15:48:59 EST 2000
From: "Russ Cox"
To: 9fans@cse.psu.edu
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-Id: <20001120204900.B527B199F0@mail.cse.psu.edu>
Subject: [9fans] memory
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0rc1
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the O/S Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive:
Date: Mon, 20 Nov 2000 15:48:57 -0500
The install, because it keeps the file system
in RAM, requires 32MB. I've done an install on a 32MB
system and I was using pretty much all the memory.
As others have pointed out, that's mainly because
the image data is all kept in kernel memory, and the
compressed file system on the floppy is expanded
and kept in memory while being accessed.
You could run a simple 640x480x8 terminal with
16MB, but I'm not sure how much can be done with
only 8MB.
The ATI video cards come with a wide range of
memory depending mainly on the age of the card.
Others have reported trying the Xpert98 but I don't
remember whether the reports were good or bad.
Russ
--upas-kwelspvbqvnazfwqvgicyftsho--
From 9fans@cse.psu.edu Tue Nov 21 15:46:15 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Tue, 21 Nov 2000 15:46:15 0000
Subject: [9fans] problems with marshal
Message-ID: <20001121144412.239EB199E1@mail.cse.psu.edu>
i came across a few problems with upas/marshal; i'm afraid i haven't
got time to fix all of them right now.
most minor problem is that in scanning for 8 bit characters, a
"Content-transfer-encoding: 8bit" header can be output several times.
that's fixed easily with:
diff /n/dump/2000/1121/sys/src/cmd/upas/ned/marshal.c marshal.c
370c370
< for(;;){
---
> while (docontenttype){
385c385
< if(*p++ & 0x80){
---
> if(*p++ & 0x80 && docontenttype){
(which also saves some buffer space on files containing lots of utf)
the other problem is that text attachments containing 8 bit utf don't
propagate the "Content-transfer-encoding: 8bit" into the main header.
fixing this would require reading all the attachments before spitting
out the principal header, which is not currently done.
the alternative (which would likely be preferable, as it would make
the resulting email smtp compatible) would be to encode any 8-bit
plain text attachments in quoted-printable. then i might be able to
see the utf chars sent to 9fans!
one last thing:
diff /n/dump/2000/1121/sys/src/cmd/file.c file.c
345c345
< if (nbuf < 100)
---
> if (nbuf < 100 && !mime)
which stops "file -m" printing two type lines for short files.
cheers,
rog.
From 9fans@cse.psu.edu Tue Nov 21 15:20:34 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Tue, 21 Nov 2000 16:20:34 +0100
Subject: [9fans] problems with marshal
References: <20001121144412.239EB199E1@mail.cse.psu.edu>
Message-ID: <021801c053ce$98a6a3c0$0ab9c6d4@cybercable.fr>
From:
>
> the other problem is that text attachments containing 8 bit utf don't
> propagate the "Content-transfer-encoding: 8bit" into the main header.
> fixing this would require reading all the attachments before spitting
> out the principal header, which is not currently done.
>
i reckon that a lot of careful thought would be required before
stepping into that mimefield [sic].
by the end of the 4th mime doc either the authors had totally
lost it, you have totally lost it or a combination of both.
at least with text messages from plan 9 they are obviously
8bit, 'cos it's UTF. but when you talk smtp you then have to
decide on whether conversion is required depending on who
you're talking to at the other end.
it's a very ugly problem. attatchments complicate it no end.
i agree with what Bill McLean, director of the AIM-9 sidewinder
project said:
it is easy to build something that is complicated but
it is hard to build something so that it's simple
that may not be exact.
during the trials between the sidewinder and what was to
become the AIM-54 phoenix, the phoenix team had a hanger
full of test equipment. when asked for what sort of test
equipment the sidewinder team required the reply was:
oh, a flashlight and a screwdriver
From 9fans@cse.psu.edu Tue Nov 21 15:40:28 2000
From: 9fans@cse.psu.edu (Russ Cox)
Date: Tue, 21 Nov 2000 10:40:28 -0500
Subject: [9fans] Re: Ati Xpert 98 Video card
Message-ID: <20001121154029.C4DA4199E4@mail.cse.psu.edu>
flickers on the screen can be fixed by trying
lower resolutions or refresh rates. it really
means that we're not setting the memory parameters
correctly, but the easiest work-around is to not
push the memory so hard.
vga is a very hard problem. oddly enough the
ati cards do have the best support, because we have
the most complete documentation for them. but
even that's not everything we need to know.
the cards with the "best support" are usually
the cards with the most recently written driver,
since the contemporary cards have not had a chance
to diverge from what was used to write the driver.
the main problem is that vendors think it's
sufficient to release a windows driver rather
than real documentation.
if you pick a random card and hope it
will work, your chances are best if that vendor
is ati. that said, the savage4-based cards
seem to be working quite nicely.
i have a stalled vga rewrite that addresses a
few problems and adds some control of various
common features found on laptops, but
getting vgas working is an inherently ad hoc
process and no amount of rewriting will get rid
of that aspect completely.
russ
From 9fans@cse.psu.edu Tue Nov 21 16:54:15 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Tue, 21 Nov 2000 16:54:15 0000
Subject: [9fans] problems with marshal
Message-ID: <20001121155207.150A4199EC@mail.cse.psu.edu>
boyd wrote:
> by the end of the 4th mime doc either the authors had totally
> lost it, you have totally lost it or a combination of both.
i agree.
i'm very close to losing it totally today.
... (muffled shrieks) ...
rog.
From 9fans@cse.psu.edu Tue Nov 21 16:04:59 2000
From: 9fans@cse.psu.edu (Douglas A. Gwyn)
Date: Tue, 21 Nov 2000 16:04:59 GMT
Subject: [9fans] AFS-client for Plan9 - ?
References: <20001120142304.0AD6B199D5@mail.cse.psu.edu>
Message-ID: <3A1A8F29.B3857BB0@arl.army.mil>
rog@vitanuova.com wrote:
> however, it's worth remembering, that in the Unix i remember at any
> rate, _exit() is not always invoked on program exit. it isn't invoked
> if the program dies from a signal, for instance.
Right; upon abnormal termination (what POSIX terms "termination
with actions" as I recall), the application process has lost
control, so only the kernel clean-up actions can be performed
(which include closing open FDs, as others have remarked).
> i've always presumed that the final close of fds is done when their
> refcount drops to zero, i.e. when the exited process's file table is
> cleared up by the kernel.
It depends on the kernel (there might be process-owned locks to
release, for example), but that's the roght general idea.
Closing a "file" decrements its in-use count and only when that
count goes to zero is the "real" close function performed, e.g.
device driver drops READY etc.
> so the actual _?exit() system calls are not that crucial to the issue
> of file closing under AFS. stdio is a different matter, of course.
Yes, sorry if I digressed.
From 9fans@cse.psu.edu Tue Nov 21 16:04:40 2000
From: 9fans@cse.psu.edu (Douglas A. Gwyn)
Date: Tue, 21 Nov 2000 16:04:40 GMT
Subject: [9fans] vito nuova inferno on 98
References: <20001118234355.9B81A199E8@mail.cse.psu.edu>
Message-ID: <3A1A8DF4.C2A6B2FB@arl.army.mil>
Russ Cox wrote:
> cl and ml are the microsoft visual c/c++ compiler/linker
> and presumably the assembler/linker. cl stands for
> compile and/or link.
I don't think the assembler/linker are included in recent
Visual C++, but they are somewhere among the MSDN disks.
From 9fans@cse.psu.edu Tue Nov 21 17:12:11 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Tue, 21 Nov 2000 18:12:11 +0100
Subject: [9fans] vito nuova inferno on 98
References: <20001118234355.9B81A199E8@mail.cse.psu.edu> <3A1A8DF4.C2A6B2FB@arl.army.mil>
Message-ID: <022a01c053de$2fdafde0$0ab9c6d4@cybercable.fr>
----- Original Message -----
> Russ Cox wrote:
> > cl and ml are the microsoft visual c/c++ compiler/linker
> > and presumably the assembler/linker. cl stands for
> > compile and/or link.
>
> I don't think the assembler/linker are included in recent
> Visual C++, but they are somewhere among the MSDN disks.
yes, but this is not my real problem. the only version
of mk i see is a windows binary and the C source, but
i want to write limbo on inferno, or compile bits of the
source tree. unless i'm missing something, mk.dis does
not exist.
yes have have thought of writing a function that writes
a bat file that runs mk -n, using 'os' and then feeds it
into a shell. this is gross.
maybe this cold has fried all my neurons or some devious
cross compiling was done to create the cd.
From 9fans@cse.psu.edu Tue Nov 21 16:05:15 2000
From: 9fans@cse.psu.edu (Douglas A. Gwyn)
Date: Tue, 21 Nov 2000 16:05:15 GMT
Subject: [9fans] Re: Ati Xpert 98 Video card
References: <%yyR5.149579$ib7.19937854@news1.rdc1.nj.home.com>
Message-ID: <3A1A9060.49C5691E@arl.army.mil>
James wrote:
> I should have no problem using a Ati-Xpert video card with Plan 9. Should I
> get PCI or AGP?
> The Ati Mach64 is 2mb video card?
I have gotten good results from the Xpert-98 (3D RAGE PRO version).
Xpert-128 (RAGE-128) however did not work right last time I tried it.
MACH64 denotes a family of chips, which can be used with various
amounts of memory (the one I used to have was 4MB).
From 9fans@cse.psu.edu Tue Nov 21 17:30:10 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Tue, 21 Nov 2000 12:30:10 -0500
Subject: [9fans] problems with marshal
Message-ID: <20001121173012.12C22199E4@mail.cse.psu.edu>
I originally just said it was UTF-8 and 8bit encoding but backed off because
lots of mailers threw their hands up at UTF-8. Perhaps I should have kept the
8bit part though. I'll try changing it to always say
Content-Transfer-Encoding: 7bit
in the main header and see how it goes.
From 9fans@cse.psu.edu Tue Nov 21 17:31:12 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Tue, 21 Nov 2000 12:31:12 -0500
Subject: [9fans] problems with marshal
Message-ID: <20001121173113.E99FB199F7@mail.cse.psu.edu>
Sorry about that last message... I can't cut and paste anymore, too many
neurons gone. I meant:
I'll try changing it to always say
Content-Transfer-Encoding: 8bit
in the main header and see how it goes.
From 9fans@cse.psu.edu Tue Nov 21 17:33:33 2000
From: 9fans@cse.psu.edu (Lyndon Nerenberg)
Date: Tue, 21 Nov 2000 17:33:33 GMT
Subject: [9fans] Re: Plan 9 on notebooks
References:
Message-ID: <86lmudxmp7.fsf@gollum.esys.ca>
>>>>> "John" == John A Murdie writes:
John> Thanks again to the individuals who mailed me with useful
John> information. I was a little surprised to hear that 800x600
John> display resolution was so common. Can anyone tell me which
John> of the notebooks which will run Plan 9 `out of the box' (or
John> for which diffs are available) will support 1024x768?
The Dell Inspiron 7000 works at 1024x768. You have to select the
"Dell Cptxxx" entry (can't remember the exact modem number) on
the boot floppy creation webpage to get the correct settings in
plan9.ini.
--lyndon
From 9fans@cse.psu.edu Tue Nov 21 17:40:27 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Tue, 21 Nov 2000 12:40:27 -0500
Subject: [9fans] vito nuova inferno on 98
Message-ID: <20001121174032.0F11F199E1@mail.cse.psu.edu>
//the only version of mk i see is a windows binary and
//the C source, but i want to write limbo on inferno, or
//compile bits of the source tree. unless i'm missing
//something, mk.dis does not exist.
nope, you're right: there is no mk.[b|dis]. there are two
building options: 1) use mk on the underlying OS (outside
of Inferno) with that OS's "native" mk and limbo compiler
2) use mash and its make functionality. option 2 may be of
limited life, however, as VN has said mash may not be long
for their distribution. i'm wondering if they have any
alternative in the works. option 1 is the standard on all
the Inferno development efforts i've seen.
-Îą.
From 9fans@cse.psu.edu Tue Nov 21 18:47:45 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Tue, 21 Nov 2000 18:47:45 0000
Subject: [9fans] problems with marshal
Message-ID: <20001121174543.7C373199E4@mail.cse.psu.edu>
> I'll try changing it to always say
> Content-Transfer-Encoding: 7bit
> in the main header and see how it goes.
actually, that's the default anyway. and even if it wasn't, it
wouldn't really help, as that header would be lying if utf8 characters
were included.
the whole thing's a crock of shit, but if it's to be a working crock
of shit i can't really see much alternative to converting utf8
plain/text attachments to quoted-printable.
of course, then there's the issue of utf8 in header lines. =?.....?=,
rfc2047, aargh.
as you might be able to tell, i've had some dealings with
this stuff recently, hence i was plundering upas for ideas
on "nice" ways of dealing with the crud, hence i realised these
problems...
cheers,
rog.
From 9fans@cse.psu.edu Tue Nov 21 17:47:51 2000
From: 9fans@cse.psu.edu (Alex Bochannek)
Date: Tue, 21 Nov 2000 09:47:51 -0800
Subject: [9fans] problems with marshal
In-Reply-To: Your message of "Tue, 21 Nov 2000 12:31:12 EST."
<20001121173113.E99FB199F7@mail.cse.psu.edu>
Message-ID: <200011211747.JAA22290@volition.org>
Keep in mind that 8bit content-transfer-encoding is MTA specific. If
your MTA supports ESMTP, it works fine, but otherwise, that's what
transfer encodings like quoted-printable[1] or base64 are for. See
also UTR #17 at http://www.unicode.org/unicode/reports/tr17/
Alex.
[1] 8bit character encoding schemes like UTF-8 (nee UTF-2) for example
lend themselves nicely to quoted-printable since they preserve the
7bit ASCII character encoding.
From 9fans@cse.psu.edu Tue Nov 21 17:48:29 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Tue, 21 Nov 2000 18:48:29 +0100
Subject: [9fans] vito nuova inferno on 98
References: <20001121174032.0F11F199E1@mail.cse.psu.edu>
Message-ID: <024001c053e3$42161940$0ab9c6d4@cybercable.fr>
From:
> 2) use mash and its make functionality. option 2 may be of
> limited life, however, as VN has said mash may not be long
> for their distribution.
i haven't looked at the mk extensions to mash even though
the author is a mate of mine and i was staying with him when
he wrote it! he's not even sure what state the vita mash is in.
i feel a hideous kludge comming on...
From 9fans@cse.psu.edu Tue Nov 21 17:59:38 2000
From: 9fans@cse.psu.edu (Jean Mehat)
Date: Tue, 21 Nov 2000 18:59:38 +0100 (CET)
Subject: [9fans] password on cpu and file server
Message-ID: <200011211759.eALHxct05496@hon.ai.univ-paris8.fr>
THe v3 file server and cpu server don't ask for the password before
entering the command mode (or running rc) on my machines. Is it the
normal behaviour for Plan 9 version 3? What is the rationale behind
this?
jm
From 9fans@cse.psu.edu Tue Nov 21 19:07:33 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Tue, 21 Nov 2000 19:07:33 0000
Subject: [9fans] vito nuova inferno on 98
Message-ID: <20001121180525.482BE199E3@mail.cse.psu.edu>
> yes, but this is not my real problem. the only version
> of mk i see is a windows binary and the C source, but
> i want to write limbo on inferno, or compile bits of the
> source tree. unless i'm missing something, mk.dis does
> not exist.
you're right, mk.dis doesn't exist. it's on the cards to rectify this
in some way, whether it's by cloning mk, or putting mash-like
functionality into inferno sh, or whatever... it will happen, but
we're snowed under for the time being, and i think there are higher
immediate priorities (charles might correct me).
the thing is that one doesn't tend to feel the lack of mk too much when
developing limbo under inferno, as there's no link stage,
so usually just a {limbo -g *.b; cp *.dis /dis} suffices.
we don't plan on rewriting the C compilers in Limbo anytime
soon, and that's where mk becomes invaluable. so if you're
rebuilding emu or a native kernel, you'll be forced out
into your host environment for the forseeable future
(oscmd aside)
if you really felt the lack, you could use mash, or
write a little sh script:
#!/dis/sh
load std regex
fn depend {
# usage depend source target recipe args...
(src targ recipe) := $*
recent:=${hd `{ls -t $targ $src >[2] /dev/null}}
if {~ $recent $src} {
echo $recipe
$recipe
}
}
for i in *.b {
targ := ${re s '(.*)\.b$' '\1.dis' $i}
depend $i $targ {
limbo -g $*
} $i
}
From 9fans@cse.psu.edu Tue Nov 21 18:23:42 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Tue, 21 Nov 2000 19:23:42 +0100
Subject: [9fans] problems with marshal
References: <20001121174543.7C373199E4@mail.cse.psu.edu>
Message-ID: <024a01c053e8$2e14b140$0ab9c6d4@cybercable.fr>
From:
>
> the whole thing's a crock of shit, but if it's to be a working crock
> of shit i can't really see much alternative to converting utf8
> plain/text attachments to quoted-printable.
>
it is a _very nasty_ problem indeed.
being in france i've had to deal with ISO Latin 1 for a long
time. oh, god, how many arguments have i had over this.
> of course, then there's the issue of utf8 in header lines. =?.....?=,
> rfc2047, aargh.
read that one too.
i had to do some corporate mail snooping so that's why
understand the horror of it all. i understand the horror,
but not all of MIME. it's 150 pages of pure trash.
saying it's 8bit doesn't really help 'cos it's a 7 bit
transport unless it's ESMTP _and_ the ESMTP implementation
returns 8BITMIME as one of the supported options (IIRC).
doesn't 7 bit come from the IMPs?
a long time ago i suggested to paul vixie just to add
a new SMTP command 'will you do 8 bit transport'? if
the response was no the message would be returned. this
was based on the assumption that all messages potentially
had 8 bit chars and no analysis of the message body.
he said that MIME would take care of all of that. i
didn't agree. even in '92 i think it was pretty safe
to say that most/all? transports were 8 bit.
i wanted to force people who had 7 bit transports to
chuck 'em, if such things still existed.
From 9fans@cse.psu.edu Tue Nov 21 19:37:36 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Tue, 21 Nov 2000 14:37:36 -0500
Subject: [9fans] mime
Message-ID: <20001121193744.53C18199F7@mail.cse.psu.edu>
If I were willing to do it correctly, I should have the
smtp program (my only MTA) determine the transfer-encoding
and not marshal. It only needs to convert if it can't get
an esmtp conection.
Seriously though. What brain damaged piece of dog
excrement program would throw away the 8th bit of every
byte in today's world? Smtp's requirement for
7 bit clean was acknowledgement of systems of the time
that really did push messages across serial lines with
parity and/or used the 8th bit in mail files as a signalling
channel. However, I really don't know of any such these
days. Every smtp I call up seems perfectly happy to pass
on all 8 bits despite what the RFC says.
From 9fans@cse.psu.edu Tue Nov 21 20:04:40 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Tue, 21 Nov 2000 21:04:40 +0100
Subject: [9fans] mime
References: <20001121193744.53C18199F7@mail.cse.psu.edu>
Message-ID: <027401c053f6$48b42680$0ab9c6d4@cybercable.fr>
From:
> Seriously though. What brain damaged piece of dog
> excrement program would throw away the 8th bit of every
> byte in today's world?
not even sendmail, which qualifies, smashes the 8th bit
off on the receive side. on the send side it does if
the mailer flag 7 is used. mailer flag 9 (undocumented)
turns whatever encoding you've got back into an 8 bit
stream (in essense).
i have seen lotus notes V4? ack an EHLO but refuse to
offer 8BITMIME -- useless.
From 9fans@cse.psu.edu Tue Nov 21 22:00:15 2000
From: 9fans@cse.psu.edu (Russ Cox)
Date: Tue, 21 Nov 2000 17:00:15 -0500
Subject: [9fans] password on cpu and file server
Message-ID: <20001121220018.7BC6A199F1@mail.cse.psu.edu>
I don't know why the cpu servers don't ask
by default anymore. My best guess would be
that when bootstrapping the system before
authentication, it got commented out and
never put back because no one wanted it.
Uncomment the call to pass(key) in
/sys/src/cmd/init.c and mk init.install if
you want it. We do have one system that
runs a modified init with this change, but
it's the exception.
Russ
From 9fans@cse.psu.edu Tue Nov 21 23:25:05 2000
From: 9fans@cse.psu.edu (rob pike)
Date: Tue, 21 Nov 2000 18:25:05 -0500
Subject: [9fans] mime
References: <20001121193744.53C18199F7@mail.cse.psu.edu>
Message-ID: <00de01c05412$4832b0c0$97036887@cs.belllabs.com>
> Seriously though. What brain damaged piece of dog
> excrement program would throw away the 8th bit of every
> byte in today's world? Smtp's requirement for
> 7 bit clean was acknowledgement of systems of the time
> that really did push messages across serial lines with
> parity and/or used the 8th bit in mail files as a signalling
> channel. However, I really don't know of any such these
> days. Every smtp I call up seems perfectly happy to pass
> on all 8 bits despite what the RFC says.
Brian Ried is the source of the brain damage. Maybe it's
Brian damage. He insisted on making the DEC gateways
clear the 8th bit in a stupefying bid to make everyone
honest. He thought, I guess, that the computing world
didn't have enough complexity yet. I hope he's happy
now.
-rob
From 9fans@cse.psu.edu Tue Nov 21 23:31:43 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Wed, 22 Nov 2000 00:31:43 +0100
Subject: [9fans] mime
References: <20001121193744.53C18199F7@mail.cse.psu.edu> <00de01c05412$4832b0c0$97036887@cs.belllabs.com>
Message-ID: <028501c05413$3552bb20$0ab9c6d4@cybercable.fr>
From: rob pike
>
> Brian Ried is the source of the brain damage. Maybe it's
> Brian damage. He insisted on making the DEC gateways
> clear the 8th bit in a stupefying bid to make everyone
> honest.
i could believe he would do that but back while paul
vixie was with digital (till '93 or so) KJS didn't
clear the 8th bit on input.
then again, you could be talking about an earlier
or later time and over the past few years i've seen
him lose his mind. there is one story that says he'd
smear fertiliser on his hands before flying to trigger
nitrate sniffers.
i could have asked the question on a list he's on but
i got myself kicked off it 'cos i wouldn't apologise
for a flame i sent -- as if no flames were ever sent
to this list.
From 9fans@cse.psu.edu Wed Nov 22 06:01:07 2000
From: 9fans@cse.psu.edu (rob pike)
Date: Wed, 22 Nov 2000 01:01:07 -0500
Subject: [9fans] rio
Message-ID: <20001122060111.27A1B199E1@mail.cse.psu.edu>
Rookie error in rio. In /sys/src/cmd/rio/wind.c,
change the line
memmove(hidden+i, hidden+i+1, nhidden-i);
to
memmove(hidden+i, hidden+i+1, (nhidden-i)*sizeof(hidden[0]));
and a stupid bug will vanish. Astonishing it's lived
this long.
-rob
From 9fans@cse.psu.edu Wed Nov 22 06:21:44 2000
From: 9fans@cse.psu.edu (George Michaelson)
Date: Wed, 22 Nov 2000 16:21:44 +1000
Subject: [9fans] pdp8 lives!!
In-Reply-To: Your message of "Wed, 22 Nov 2000 01:01:07 EST."
<20001122060111.27A1B199E1@mail.cse.psu.edu>
Message-ID: <19508.974874104@dstc.edu.au>
http://www.spies.com/~dgc/pdp8x/
surely not beyond the capabilities of a plan-9er to port...
Is there an Edgar Allan P(lan9) O(n) E(verything) corner somewhere?
-George
--
George Michaelson | DSTC Pty Ltd
Email: ggm@dstc.edu.au | University of Qld 4072
Phone: +61 7 3365 4310 | Australia
Fax: +61 7 3365 4311 | http://www.dstc.edu.au
From 9fans@cse.psu.edu Tue Nov 21 23:07:36 2000
From: 9fans@cse.psu.edu (Steve Kilbane)
Date: Tue, 21 Nov 2000 23:07:36 +0000
Subject: [9fans] mime
In-Reply-To: Your message of "Tue, 21 Nov 2000 21:04:40 +0100."
<027401c053f6$48b42680$0ab9c6d4@cybercable.fr>
Message-ID: <200011212307.XAA17787@whitecrow.demon.co.uk>
Boyd:
> i have seen lotus notes V4? ack an EHLO but refuse to
> offer 8BITMIME -- useless.
Nooo, not Notes - don't go there, please!
From 9fans@cse.psu.edu Wed Nov 22 10:31:00 2000
From: 9fans@cse.psu.edu (matt)
Date: Wed, 22 Nov 2000 10:31:00 -0000
Subject: [9fans] mime
References: <20001121193744.53C18199F7@mail.cse.psu.edu> <00de01c05412$4832b0c0$97036887@cs.belllabs.com> <028501c05413$3552bb20$0ab9c6d4@cybercable.fr>
Message-ID: <00b901c0546f$4eda3440$0301a8c0@freeze>
----- Original Message -----
From: "Boyd Roberts"
> i could have asked the question on a list he's on but
> i got myself kicked off it 'cos i wouldn't apologise
> for a flame i sent -- as if no flames were ever sent
> to this list.
I'm shocked Boyd, that really doesn't sound like you at all, soembody really
must've wound you up for you to step out of character so.
From 9fans@cse.psu.edu Wed Nov 22 10:59:36 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Wed, 22 Nov 2000 10:59:36 0000
Subject: [9fans] wanted icon "Powered by Plan 9"
Message-ID: <20001122105907.BC32A199E1@mail.cse.psu.edu>
This is a multi-part message in MIME format.
--upas-gjypzdvespblzmupnxuwhjhrlz
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
i'd display glenda. that's the universal symbol for plan 9.
--upas-gjypzdvespblzmupnxuwhjhrlz
Content-Type: message/rfc822
Content-Disposition: inline
Received: from finch-punt-12.mail.demon.net ([194.217.242.36]) by lavoro; Tue Nov 21 15:02:42 GMT 2000
Received: from punt-1.mail.demon.net by mailstore for forsyth@caldo.demon.co.uk
id 974809382:10:24157:2; Tue, 21 Nov 2000 12:23:02 GMT
Received: from psuvax1.cse.psu.edu ([130.203.4.6]) by punt-1.mail.demon.net
id aa1105287; 21 Nov 2000 12:22 GMT
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.20.6])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP
id 88182199F7; Tue, 21 Nov 2000 07:21:10 -0500 (EST)
Received: from mercury.bath.ac.uk (mercury.bath.ac.uk [138.38.32.81])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP id E8A8B199E4
for <9fans@cse.psu.edu>; Tue, 21 Nov 2000 07:20:03 -0500 (EST)
Received: from news by mercury.bath.ac.uk with local (Exim 3.12 #1)
id 13yCJ1-00027y-00
for 9fans@cse.psu.edu; Tue, 21 Nov 2000 12:13:47 +0000
Received: from GATEWAY by bath.ac.uk with netnews
for 9fans@cse.psu.edu (9fans@cse.psu.edu)
To: 9fans@cse.psu.edu
From: vecera@writeme.com
Message-ID: <8vdok1$a0t$1@nnrp1.deja.com>
Organization: Deja.com - Before you buy.
Subject: [9fans] wanted icon "Powered by Plan 9"
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0rc1
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the O/S Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive:
Date: Tue, 21 Nov 2000 12:13:36 GMT
Hi,
I play with HTML on my home site and I would like to place there icon
"Powered by Plan 9". Is any on the world?
vecera
Sent via Deja.com http://www.deja.com/
Before you buy.
--upas-gjypzdvespblzmupnxuwhjhrlz--
From 9fans@cse.psu.edu Wed Nov 22 13:12:38 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Wed, 22 Nov 2000 13:12:38 0000
Subject: [9fans] mime
Message-ID: <20001122121028.38BD3199E1@mail.cse.psu.edu>
> What brain damaged piece of dog
> excrement program would throw away the 8th bit of every
> byte in today's world?
annoying thing is that you don't know what the 8th bit means until
you've parsed the Content-transfer-encoding header. it would be nice
if we could convert the whole thing from utf initially, but some
people have a habit of sending latin1 which of course translates as
lots of broken utf runes (and presumably utf translates as broken
latin1 on many machines).
i don't think that the header is allowed 8 bit stuff no matter what.
is the idea that if we just send utf regardless, sooner or later
mailers will assume that 8bit chars in mail headers are utf?
i might hack up a version of marshal that conforms to the standards,
at least superficially. it would be nice to be able to send mail that
people on other platforms could read. we're not so far away.
rog.
From 9fans@cse.psu.edu Wed Nov 22 13:50:53 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Wed, 22 Nov 2000 14:50:53 +0100
Subject: [9fans] mime
References: <200011212307.XAA17787@whitecrow.demon.co.uk>
Message-ID: <000d01c0548b$3b6165c0$0ab9c6d4@cybercable.fr>
From: Steve Kilbane
> Boyd:
> > i have seen lotus notes V4? ack an EHLO but refuse to
> > offer 8BITMIME -- useless.
>
> Nooo, not Notes - don't go there, please!
how do you think i picked up all this mime knowledge?
because of notes' appalling implementation of [e]smtp.
From 9fans@cse.psu.edu Wed Nov 22 14:00:35 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Wed, 22 Nov 2000 15:00:35 +0100
Subject: [9fans] mime
References: <20001121193744.53C18199F7@mail.cse.psu.edu> <00de01c05412$4832b0c0$97036887@cs.belllabs.com> <028501c05413$3552bb20$0ab9c6d4@cybercable.fr> <00b901c0546f$4eda3440$0301a8c0@freeze>
Message-ID: <001601c0548c$9656cf00$0ab9c6d4@cybercable.fr>
From: matt
> I'm shocked Boyd, that really doesn't sound like you at all, soembody really
> must've wound you up for you to step out of character so.
yeah, yeah, yeah... :-)
From 9fans@cse.psu.edu Wed Nov 22 14:21:54 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Wed, 22 Nov 2000 15:21:54 +0100
Subject: [9fans] mime
References: <20001122121028.38BD3199E1@mail.cse.psu.edu>
Message-ID: <002701c0548f$906b9500$0ab9c6d4@cybercable.fr>
From:
> ...it would be nice
> if we could convert the whole thing from utf initially, but some
> people have a habit of sending latin1 which of course translates as
> lots of broken utf runes (and presumably utf translates as broken
> latin1 on many machines).
that's how it goes. je déconne pas...
did you see the e acute?
> i don't think that the header is allowed 8 bit stuff no matter what.
yes, hence that hideous ?...? encoding crap.
> is the idea that if we just send utf regardless, sooner or later
> mailers will assume that 8bit chars in mail headers are utf?
bit of a circular problem; the headers specify the encoding
which you don't know until you've read the headers. it's
been hard enough to get 1 extra bit through [the 8th bit]
without stomping all over rfc 822.
> i might hack up a version of marshal that conforms to the standards,
> at least superficially. it would be nice to be able to send mail that
> people on other platforms could read. we're not so far away.
i'm not sure you want to do that. it's a mimefield.
From 9fans@cse.psu.edu Wed Nov 22 15:46:05 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Wed, 22 Nov 2000 15:46:05 0000
Subject: [9fans] mime
Message-ID: <20001122144404.CE0CB199E1@mail.cse.psu.edu>
> that's how it goes. je dconne pas...
>
> did you see the e acute?
nope.
that's the problem. somewhere a gateway stripped out 'invalid' chars
(didn't even turn the e-acute into an 'i' which is what i would have
expected)
> i'm not sure you want to do that. it's a mimefield.
yeah, but we're already neck deep in the big muddy.
so the damn fool might might as well keep yellin' to push on.
rog.
From 9fans@cse.psu.edu Wed Nov 22 14:53:07 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Wed, 22 Nov 2000 15:53:07 +0100
Subject: [9fans] mime
References: <20001121193744.53C18199F7@mail.cse.psu.edu> <00de01c05412$4832b0c0$97036887@cs.belllabs.com>
Message-ID: <006c01c05493$ecc91260$0ab9c6d4@cybercable.fr>
From: rob pike
>
> Brian Ried is the source of the brain damage...
i've asked another source for confirmation. i'd
forgotten that he's not on said list either. he
asked to be removed.
From 9fans@cse.psu.edu Wed Nov 22 15:02:05 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Wed, 22 Nov 2000 16:02:05 +0100
Subject: [9fans] mime
References: <20001122144404.CE0CB199E1@mail.cse.psu.edu>
Message-ID: <00a201c05495$2dc02000$0ab9c6d4@cybercable.fr>
From:
>
> yeah, but we're already neck deep in the big muddy.
> so the damn fool might might as well keep yellin' to push on.
yeah, well if i was gonna do it, i'd get the docs
and head off down to The White? Swan and ponder
the problem over several pints of taunton dry
blackthorn. at least it'd kill some of the pain.
it's a horrible problem.
From 9fans@cse.psu.edu Wed Nov 22 15:07:09 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Wed, 22 Nov 2000 16:07:09 +0100
Subject: [9fans] mime
References: <20001122144404.CE0CB199E1@mail.cse.psu.edu>
Message-ID: <00bf01c05495$e58c2080$0ab9c6d4@cybercable.fr>
From:
> yeah, but we're already neck deep in the big muddy.
> so the damn fool might might as well keep yellin' to push on.
maybe you should grab the sendmail code from sendmail.org
to get a quick overview of the full horror. it does a
pretty good job and is fairly clean.
i've read quite a bit of it in the last year :-(
From 9fans@cse.psu.edu Wed Nov 22 15:19:40 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Wed, 22 Nov 2000 15:19:40 0000
Subject: [9fans] mime
Message-ID: <20001122151546.D88CF199DC@mail.cse.psu.edu>
>>nope.
>>that's the problem. somewhere a gateway stripped out 'invalid' chars
>>(didn't even turn the e-acute into an 'i' which is what i would have
>>expected)
i think it's demon's smtp mailer that does it. i lose utf-8 in messages sent
between here and home and both are on demon.
220 finch-post-10.mail.demon.net ESMTP Wed, 22 Nov 2000 15:12:40 +0000
From ngr@9fs.org Wed Nov 22 15:16:55 2000
From: ngr@9fs.org (Nigel Roles)
Date: Wed, 22 Nov 2000 15:16:55 -0000
Subject: [9fans] mime
In-Reply-To: <00a201c05495$2dc02000$0ab9c6d4@cybercable.fr>
Message-ID: <3A1BE367.13068.188FE8A@localhost>
> and head off down to The White? Swan and ponder
Black, assuming you're on Peasholme Green.
From 9fans@cse.psu.edu Wed Nov 22 15:23:55 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Wed, 22 Nov 2000 16:23:55 +0100
Subject: [9fans] mime
References: <20001122151546.D88CF199DC@mail.cse.psu.edu>
Message-ID: <017e01c05498$3ab0c780$0ab9c6d4@cybercable.fr>
From:
> i think it's demon's smtp mailer that does it. i lose utf-8 in messages sent
> between here and home and both are on demon.
i got it back fine from 9fans.
From 9fans@cse.psu.edu Wed Nov 22 20:30:26 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Wed, 22 Nov 2000 21:30:26 +0100
Subject: [9fans] mime
References: <20001122151546.D88CF199DC@mail.cse.psu.edu> <017e01c05498$3ab0c780$0ab9c6d4@cybercable.fr>
Message-ID: <005401c054c3$0c887800$0ab9c6d4@cybercable.fr>
my reliable source says:
rfc821 says strip the 8th bit.
rfc822 says strip the 8th bit.
to many people, this was inconvenient
so they didn't implement it.
i implemented it.
brian reid supported the decision.
btw: i'm ex-digital [research]. i worked with the gateway guys,
even though i was in the paris research lab.
From 9fans@cse.psu.edu Wed Nov 22 20:49:43 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Wed, 22 Nov 2000 15:49:43 -0500
Subject: [9fans] mime
Message-ID: <20001122204959.D4FE0199F5@mail.cse.psu.edu>
This is a multi-part message in MIME format.
--upas-vfoxebhimxfxhxzxmxzfizufbn
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 8bit
You don't have to know the transfer encoding when parsing the header.
According to 822,
Each header field can be viewed as a single, logical line of
ASCII characters, comprising a field-name and a field-body.
Of course 821 states
The maximum total length of a text line including the
is 1000 characters (but not counting the leading
dot duplicated for transparency).
To stay consistent with these, headers need to be in the
7bit domain. However, rfc2047 provides the amazing
=?b?gobbledeygook?= syntax to allow non ascii tokens in the
header.
Therefore, the 'Content-Transfer-Encoding: {78}bit' header field
isn't telling you anything per se about the header since the
headers are predefined to be US-ASCII with the =???=
encoding providing an escape in case you want what's there
to be convertible to non-ASCII.
When upas/marshal says that a message (or message portion)
is either 7 or 8 bit, it's just stating a fact. However, if
smtp sees an 8bit message and doesn't get an esmtp connection
to the remote host, it should encode the message (or message
part) in base64 (or quoted printable).
We either have to bite the bullet and encode all 8-bit data
presented to marshal OR change smtp to do the recoding OR
both. However, if we're also willing to relay messages (which
I do) than the marshal change is insufficient since mail may
pass through us from an 8bit to a 7bit channel without passing
marshal.
Therefore, I'm going to make smtp (or a front end to it)
convert and you can all stop your whining.
However, I'm still perplexed as to what to put in the header
of a multipart message. Does the transfer encoding specified
there pertain to the whole message or just to the
nyah nyah, if you only had a MIME mailer you wouldn't see this
message that starts every multipart message?
--upas-vfoxebhimxfxhxzxmxzfizufbn
Content-Type: message/rfc822
Content-Disposition: inline
Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Wed Nov 22 07:11:21 EST 2000
Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Wed Nov 22 07:11:20 EST 2000
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.8.6])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP
id 09A2F199E9; Wed, 22 Nov 2000 07:11:10 -0500 (EST)
Received: from presto.hci-net (unknown [212.240.227.6])
by mail.cse.psu.edu (CSE Mail Server) with SMTP id 38BD3199E1
for <9fans@cse.psu.edu>; Wed, 22 Nov 2000 07:10:28 -0500 (EST)
To: 9fans@cse.psu.edu
Subject: Re: [9fans] mime
From: rog@vitanuova.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-Id: <20001122121028.38BD3199E1@mail.cse.psu.edu>
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0rc1
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the O/S Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive:
Date: Wed, 22 Nov 2000 13:12:38 0000
> What brain damaged piece of dog
> excrement program would throw away the 8th bit of every
> byte in today's world?
annoying thing is that you don't know what the 8th bit means until
you've parsed the Content-transfer-encoding header. it would be nice
if we could convert the whole thing from utf initially, but some
people have a habit of sending latin1 which of course translates as
lots of broken utf runes (and presumably utf translates as broken
latin1 on many machines).
i don't think that the header is allowed 8 bit stuff no matter what.
is the idea that if we just send utf regardless, sooner or later
mailers will assume that 8bit chars in mail headers are utf?
i might hack up a version of marshal that conforms to the standards,
at least superficially. it would be nice to be able to send mail that
people on other platforms could read. we're not so far away.
rog.
--upas-vfoxebhimxfxhxzxmxzfizufbn--
From 9fans@cse.psu.edu Wed Nov 22 20:50:24 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Wed, 22 Nov 2000 15:50:24 -0500
Subject: [9fans] wanted icon "Powered by Plan 9"
Message-ID: <20001122205025.197EF199F5@mail.cse.psu.edu>
This is a multi-part message in MIME format.
--upas-kbgzoqjwxttbcqmzvjpzhkatsf
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 8bit
I'ld display a picture of Boyd to scare people away.
--upas-kbgzoqjwxttbcqmzvjpzhkatsf
Content-Type: message/rfc822
Content-Disposition: inline
Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Wed Nov 22 06:00:23 EST 2000
Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Wed Nov 22 06:00:21 EST 2000
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.8.6])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP
id 6EBE7199EA; Wed, 22 Nov 2000 06:00:10 -0500 (EST)
Received: from lavoro.home.cs.york.ac.uk (caldo.demon.co.uk [194.222.207.148])
by mail.cse.psu.edu (CSE Mail Server) with SMTP id BC32A199E1
for <9fans@cse.psu.edu>; Wed, 22 Nov 2000 05:59:07 -0500 (EST)
To: 9fans@cse.psu.edu
Subject: Re: [9fans] wanted icon "Powered by Plan 9"
From: forsyth@caldo.demon.co.uk
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="upas-gjypzdvespblzmupnxuwhjhrlz"
Message-Id: <20001122105907.BC32A199E1@mail.cse.psu.edu>
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0rc1
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the O/S Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive:
Date: Wed, 22 Nov 2000 10:59:36 0000
This is a multi-part message in MIME format.
--upas-gjypzdvespblzmupnxuwhjhrlz
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
i'd display glenda. that's the universal symbol for plan 9.
--upas-gjypzdvespblzmupnxuwhjhrlz
Content-Type: message/rfc822
Content-Disposition: inline
Received: from finch-punt-12.mail.demon.net ([194.217.242.36]) by lavoro; Tue Nov 21 15:02:42 GMT 2000
Received: from punt-1.mail.demon.net by mailstore for forsyth@caldo.demon.co.uk
id 974809382:10:24157:2; Tue, 21 Nov 2000 12:23:02 GMT
Received: from psuvax1.cse.psu.edu ([130.203.4.6]) by punt-1.mail.demon.net
id aa1105287; 21 Nov 2000 12:22 GMT
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.20.6])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP
id 88182199F7; Tue, 21 Nov 2000 07:21:10 -0500 (EST)
Received: from mercury.bath.ac.uk (mercury.bath.ac.uk [138.38.32.81])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP id E8A8B199E4
for <9fans@cse.psu.edu>; Tue, 21 Nov 2000 07:20:03 -0500 (EST)
Received: from news by mercury.bath.ac.uk with local (Exim 3.12 #1)
id 13yCJ1-00027y-00
for 9fans@cse.psu.edu; Tue, 21 Nov 2000 12:13:47 +0000
Received: from GATEWAY by bath.ac.uk with netnews
for 9fans@cse.psu.edu (9fans@cse.psu.edu)
To: 9fans@cse.psu.edu
From: vecera@writeme.com
Message-ID: <8vdok1$a0t$1@nnrp1.deja.com>
Organization: Deja.com - Before you buy.
Subject: [9fans] wanted icon "Powered by Plan 9"
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0rc1
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the O/S Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive:
Date: Tue, 21 Nov 2000 12:13:36 GMT
Hi,
I play with HTML on my home site and I would like to place there icon
"Powered by Plan 9". Is any on the world?
vecera
Sent via Deja.com http://www.deja.com/
Before you buy.
--upas-gjypzdvespblzmupnxuwhjhrlz--
--upas-kbgzoqjwxttbcqmzvjpzhkatsf--
From 9fans@cse.psu.edu Wed Nov 22 21:13:20 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Wed, 22 Nov 2000 16:13:20 -0500
Subject: [9fans] mime
Message-ID: <20001122211322.49A82199FF@mail.cse.psu.edu>
However, I'm still perplexed as to what to put in the header
of a multipart message. Does the transfer encoding specified
there pertain to the whole message or just to the
nyah nyah, if you only had a MIME mailer you wouldn't see this
message that starts every multipart message?
Just answered my own question. Rfc2045 says:
6.4. Interpretation and Use
If a Content-Transfer-Encoding header field appears as part of a
message header, it applies to the entire body of that message. If a
Content-Transfer-Encoding header field appears as part of an entity's
headers, it applies only to the body of that entity. If an entity is
of type "multipart" the Content-Transfer-Encoding is not permitted to
have any value other than "7bit", "8bit" or "binary".
That makes my life much easier. Someone must have been thinking.
From 9fans@cse.psu.edu Wed Nov 22 21:21:45 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Wed, 22 Nov 2000 22:21:45 +0100
Subject: [9fans] wanted icon "Powered by Plan 9"
References: <20001122205025.197EF199F5@mail.cse.psu.edu>
Message-ID: <009101c054ca$38213040$0ab9c6d4@cybercable.fr>
From:
> I'ld display a picture of Boyd to scare people away.
i have on the web my 512x512x8, taken by rob, if you'd like it.
but you have it anyway.
From 9fans@cse.psu.edu Wed Nov 22 21:26:21 2000
From: 9fans@cse.psu.edu (Boyd Roberts)
Date: Wed, 22 Nov 2000 22:26:21 +0100
Subject: [9fans] mime
References: <20001122204959.D4FE0199F5@mail.cse.psu.edu>
Message-ID: <00a201c054ca$dc4f85e0$0ab9c6d4@cybercable.fr>
From:
>
> Therefore, I'm going to make smtp (or a front end to it)
> convert and you can all stop your whining.
>
i'm not whining. i just think it's a horrible problem
that no-one should have to address, but unfortunately
it has be done.
From 9fans@cse.psu.edu Wed Nov 22 21:32:12 2000
From: 9fans@cse.psu.edu (9fans@cse.psu.edu)
Date: Wed, 22 Nov 2000 16:32:12 -0500
Subject: [9fans] wanted icon "Powered by Plan 9"
Message-ID: <20001122213218.64B9A199DD@mail.cse.psu.edu>
This is a multi-part message in MIME format.
--upas-sjdmnvdbltuazyxonjbjhqjllc
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 8bit
Brucee put a 48x48x? version of your picture for seemail on our systems.
Unfortunately, the rendition has a strange shadow under the nose and
a swept enough hairdo that someone asked why I had the name boyd
under all those pictures of hitler.
--upas-sjdmnvdbltuazyxonjbjhqjllc
Content-Type: message/rfc822
Content-Disposition: inline
Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Wed Nov 22 16:22:22 EST 2000
Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Wed Nov 22 16:22:21 EST 2000
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.4.6])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP
id C241819A07; Wed, 22 Nov 2000 16:22:10 -0500 (EST)
Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200])
by mail.cse.psu.edu (CSE Mail Server) with SMTP id 7542A19A02
for <9fans@cse.psu.edu>; Wed, 22 Nov 2000 16:21:51 -0500 (EST)
Received: (qmail 7538149 invoked from network); 22 Nov 2000 21:21:49 -0000
Received: from d010.dhcp212-185.cybercable.fr (HELO coma) ([212.198.185.10]) (envelope-sender )
by camus.cybercable.fr (qmail-ldap-1.03) with SMTP
for <9fans@cse.psu.edu>; 22 Nov 2000 21:21:49 -0000
Message-ID: <009101c054ca$38213040$0ab9c6d4@cybercable.fr>
From: "Boyd Roberts" | |