Qid.type == mode24, and since they should agree, they have equal authority.
it's the file server or the device driver that ensures equality.
dev.c:/^devdir\( does so for many device drivers, based on the type value of
the incoming Qid.
it looks like a mistake that devusb.c doesn't set QTEXCL in
If it has to wait, it will panic. Given that, why do the locking at all?
i assume the intention is along these lines:
it's to allow the use during reset of a given driver's
standard functions that normally must qlock, to avoid requiring two copies
of them, with and without the qlock.
after
% ls -lqd /n/dump/2006/0707/usr/rog
(0003d540 1122 80) d-rwxr-xr-x M 42850 rog rog 0 Jun 7 2005
/n/dump/2005/0707/usr/rog
% ls -lqd /n/dump/2006/0707/usr/rog
(0003d540 1157 80) d-rwxr-xr-x M 42850 rog rog 0 Jun 12 2006
/n/dump/2006/0707/usr/rog
they have the same qid but they're
http://code.google.com/p/inferno-os/source/browse/#hg/appl/cmd/mash
that one is indeed fairly old, much as we received it, except for
changes to fit any changes in the environment, but
http://www.vitanuova.com/inferno/man/1/mash.html
and
quite typically it's more than a little late, but i was finally able to scan in
an old RSRE paper that was relevant to the following. the scanning system i had
at the time couldn't cope.
anyway, it's at
http://www.vitanuova.com/dist/doc/rsre-3522-curt.pdf
But then I start to wonder why we feel we want to compete with HTTP when it
already works, and is still fairly simple.
http is by no means simple, although yes, it could be still more complicated.
As per C89 in this case the unsigned char value should be
promoted to a *signed* int value. The sum will be of type
signed int and so the division will do the right thing. In
kencc case it seems the sum has type unsigned int for some
reason and further, the signed divisor (2) is promoted to an
network protocol standards (IL not withstanding), but it _did_ choose to fight
the POSIX/C99 et. al battle.
there are several different aspects to this:
1. the language accepted by the C compiler excluding the preprocessor and
#include files
2. the C standard's include files
3. POSIX interface
Just to clarify, you do mean the TV show?
yes, yes i do.
-T is great. But Python can't be built with it. Python explicitly
creates functions with type signatures that don't match and this makes
-T very unhappy.
the examples i had to fix (that didn't simply require
#pragma incomplete) were errors, for instance something like the following:
one
perhaps Plan 9 is just the Black Books of software?
but by 1990 with microchannel c. things were much more closed off.
i thought only one company ever really made microchannel,
and even they weren't terribly in earnest in the end,
except on non-PC things like RS6000.
Just like you wouldn't have wanted to redo the microcode
in your Vax 11/750, even if you could have.
i thought several universities did modify the microcode in various ways,
to test some research ideas, or just to improve things.
it does seem like a ridiculous thing, but it
seems to be something of a religious issue with them.
that was my impression. we aren't the only ones to find
the restriction irksome, by any means. to avoid this
intransigence spreading, i should say that we'll compensate
for it somehow. i agree with
Or else commit some hidden file in those directories?
there isn't a `hidden file' in either Plan 9 or Inferno.
I'm actually looking at the javascript implementations of [9p] as well.
has javascript finally got support for binary data?
they emphatically don't go for posix semantics...
what are posix semantics?
Lucent had little to do with Inferno externally
after 1 September 1999, and nothing to do with
it externally (technically) after 1 March 2000, so there was
no reason for Lucent to keep that external domain name.
Internally Inferno continued in use in Lucent in
several projects (both products and
I hope the services I want to use (will) have a non-browser API (eg Twitter).
although it uses http, twitter has got an api that you can use outside
a browser. it's much the same with several others, including aws.
there are reasonably clear descriptions of the messages, and you can construct
and
I'm having a continuous problem, symptom being failures in archWalk,
but had assumed it was a hard disk getting ready to die.
i see those on one of my old drives, but i don't think
it's the drive. i thought it might have been
caused by a power failure catching out fossil or venti,
but if you've
Knowing *who* made the change is often even more useful than the change
comment.
yes. i use ls -lm on our trees, but that might not work on less direct things
like sources.
the amd64 compiler uses only SSE.
i thought about putting it in 8[acl] and might
have asked about that here, but i think i concluded
at the time that 64-bit would appear on all boards.
for 32-bit i wouldn't bother trying to mix the 387 and SSE,
so there would be two 386 environments, old and new,
if i were you, i'd start with something simple first, to
find my way round the system. it's probably also not a bad
idea, as someone else suggested, to write a few small programs
for plan 9 itself, just to see the differences. write a silly
concurrent program using thread(2), for instance, and
And even we we stick with the resources
as regular files approach on the client you're stuck with mostly POSIX
environment + locking (+caching). POSIX means symlink(2) and mknod(2)
no, because (unless i've misunderstood) they are accessing resources
(as regular files) on a remote server, and
I did some work on it when in the Inferno Business Unit,
based on my journalfs. As far as I can tell it doesn't appear in the
Vita distribution.
no, i don't think i ever saw it, and at one stage i had a look round
the file stores we inherited to see if there were any interesting things
that the
also, it assumes that the vm/vs
service provider will be able to provide as good or better quality of
service as you would maintaining your own infrastructure.
also that they are as sound as a bank and just as unlikely to go bust.
wait a minute ...
of course, that's just the protocol, and to show the larger
idea of the representation of things by name spaces
(instead of ioctls and special system calls)
would have to include section 3 (devices).
it's fairly pervasive.---BeginMessage---
mostly section 4 of the manual, i'd have said,
although
Any plan to run it for end users?
Sole purpose of visit
as someone supposedly quipped in answer to the question on the US entry form:
Is it your intention to overthrow the government of the United States?
(that response is variously attributed, although both Evelyn Waugh and Gilbert
Harding
ut I used both of you commands, no error messages
ip/ipconfig -D
will print a little bit more (and i mean `a', `little' and `bit')
Any chance of Plan 9's factotum learning how to speak infauth?
that was done as a GSoC project, but i then made the mistake
of trying to include it as part of a much larger change on
the Inferno side. it wasn't a silly mistake: factotum doesn't
support the key structure required for public keys
how does u9fs depend on that option?
that seems odd to me.---BeginMessage---
Just to save on the list: to compile u9fs on IBM AIX add
-qenum=small to CFLAGS in the makefile.
It's of their compiler. More info at
http://www.navo.hpc.mil/usersupport/IBM/XLC/compiler/ref/ruoptenu.htm
.
Yarek.---End
the alternative is to add very
large amounts of code to the kernel.
not really. the alternative is to add some code to the
kernel, and varying amounts of code to quite a few applications.
Furthermore, does anyone out there run Plan 9 on non-x86 hardware anymore?
yes: http://tinyurl.com/5jc8u8, for instance
bentley.ms: troff -ms input yes (Bentley
paper)
doctype might produce better guesses at troff macro packages and preprocessors
if you make it executable, i think you should also find that the resulting
executable has its contents read into memory on demand (ie, a page fault causes
a read from the executable file), which might suit you.
35 matches
Mail list logo
