On Mar 29, 2011, at 2:45 PM, John Floren wrote:
> On Tue, Mar 29, 2011 at 12:17 PM, erik quanstrom
> wrote:
>>>
>> except to talk to russ.
>>
>
> In this case, if you have a bitbucket account, just make a fork of
> russ's repo, make the change in your fork, then send Russ a pull
> request on
> I've got a rejected-by-usenix paper somewhere about writing a 9p
> encryption fs which you could stack on anything that served 9p:
do you have a copy of this paper? did you just rewrite a block-at-a-time?
- erik
> hi,
> i saw some project ideias in the following page:::
> http://www.plan9.bell-labs.com/wiki/plan9/gsoc-2011-ideas/index.html
>
> i liked some project ideias, like ::
> Native asn.1 DER encode/decode library
> Make a keyboard file server
> Create an alternative window manager
>
> but there ar
hi,
i saw some project ideias in the following page:::
http://www.plan9.bell-labs.com/wiki/plan9/gsoc-2011-ideas/index.html
i liked some project ideias, like ::
Native asn.1 DER encode/decode library
Make a keyboard file server
Create an alternative window manager
but there are missing some infor
On Tue Mar 29 16:07:39 EDT 2011, fors...@terzarima.net wrote:
> >also, since this is the kernel, you either get a 4k or a 4k - sizeof(Mach)
> >structure (depending on if up is set or not), so the maximum sprint
> >to something on the stack is always going to be < 4k.
>
> that's fine, but the spri
On Tue, Mar 29, 2011 at 1:25 PM, Charles Forsyth wrote:
>one question is: why does the 9vx environment
> make the original version of sprint fail?
I'm glad you asked that question :-)
I ran out of time to track it down. It's got something to do with how
the address space is set up in 32-bit 9vx
>I'm still not sure a length limit on the string of 1 Gbyte makes
>sense, and I have no idea if 64K is too low, but the 64k-limit patch
>does make it all work. I'm going to try to apply it tomorrow and see
>what shakes.
at some point, a value
ep = bp + lim
will be formed. if bp+lim is too
>also, since this is the kernel, you either get a 4k or a 4k - sizeof(Mach)
>structure (depending on if up is set or not), so the maximum sprint
>to something on the stack is always going to be < 4k.
that's fine, but the sprint is the one from the c library
which needs to support more than that. t
On Tue, Mar 29, 2011 at 12:05 PM, erik quanstrom
wrote:
> On Tue Mar 29 12:48:21 EDT 2011, fors...@terzarima.net wrote:
>> in fact, even 64k might be too big a value for the given buf if it's near the
>> top of memory (eg, a local variable on a stack that's in high memory);
>> the PowerPC referenc
On Tue, Mar 29, 2011 at 12:17 PM, erik quanstrom
wrote:
>> On Tue, 29 Mar 2011 10:58:55 -0700 John Floren wrote:
>> >On Tue, Mar 29, 2011 at 10:46 AM, John A. Grahor wrote:
>> >>What form of diff and relative to what?
>> >>
>> >>Where to post?
>> >>
>> >>
>> >
>> >man 1 patch
>> >
>> Sorry, I wa
> On Tue, 29 Mar 2011 10:58:55 -0700 John Floren wrote:
> >On Tue, Mar 29, 2011 at 10:46 AM, John A. Grahor wrote:
> >>What form of diff and relative to what?
> >>
> >>Where to post?
> >>
> >>
> >
> >man 1 patch
> >
> Sorry, I was too terse. I'm using plan9port. (9 man 1 patch) == nothing.
>
>
the great techs from at&t came today. the 24-pair termination
right in front of the house was blow apart, and the termination
pcb was 25% vaporized. i wish i had a picture. the techs fixed
that like nothing, and found few other blown connections. my
dsl modem had a hole in the pcb. amazing tha
On Tue Mar 29 12:48:21 EDT 2011, fors...@terzarima.net wrote:
> in fact, even 64k might be too big a value for the given buf if it's near the
> top of memory (eg, a local variable on a stack that's in high memory);
> the PowerPC reference in the original comment is misleading because that
> was jus
On Tue, 29 Mar 2011 10:58:55 -0700 John Floren wrote:
On Tue, Mar 29, 2011 at 10:46 AM, John A. Grahor wrote:
What form of diff and relative to what?
Where to post?
man 1 patch
Sorry, I was too terse. I'm using plan9port. (9 man 1 patch) == nothing.
Is this the wrong list for plan9p
> So I guess I must change BUF and MAXLINELEN. But shouldn't these
> defines be ideally at one place?; also they have no comments... :(
> Wouldn't it be nice to have the limits mentioned (automatically, say
> during compilation process) in the man page? Or, would it be difficult
> to get rid of any
On Tue, Mar 29, 2011 at 10:46 AM, John A. Grahor wrote:
> What form of diff and relative to what?
>
> Where to post?
>
>
man 1 patch
What form of diff and relative to what?
Where to post?
On 29 March 2011 18:45, erik quanstrom wrote:
> your problem is that you have a line that exceeds diff's line-length limits
> of 4096 characters:
>
> 6: !cat /mail/fs/mbox/323/3/body.txt|awk 'length($0)>4096 {print NR " "
> length($0)}'
> 33 4122
>
> - erik
aha. thanks!
But how is it? Does the
My bet here is that if you build yiyus or ron tree and force 32-bit,
it will fail on a 64-bit system, no idea why. if you build with 64-bit
on yiyus tree, it will work.
In other words, I think the issue crops up on 32-bit 9vx on 64-bit
environments. At least that is how it seems to work.
I'm stil
your problem is that you have a line that exceeds diff's line-length limits
of 4096 characters:
6: !cat /mail/fs/mbox/323/3/body.txt|awk 'length($0)>4096 {print NR " "
length($0)}'
33 4122
- erik
2011/3/29 ron minnich :
> On Tue, Mar 29, 2011 at 8:42 AM, Mathieu Lonjaret
> wrote:
>> Well, since Ron's tree is based on Yiyus', and Ron's doesn't have that
>> patch, I think that means Yiyus' doesn't have it either. And yet,
>> Yiyus' works for me, so I doubt this bug was the culprit for me. Mo
in fact, even 64k might be too big a value for the given buf if it's near the
top of memory (eg, a local variable on a stack that's in high memory);
the PowerPC reference in the original comment is misleading because that
was just a particular system where the general problem appeared.
>+ n = vsnprint(buf, 65536, fmt, args);
...
>Note the len = 1 << 30; why was that ever done? I never figured that out
there is nothing to limit the length of a string to 64k bytes
On Tue, Mar 29, 2011 at 6:09 PM, ron minnich wrote:
> On Tue, Mar 29, 2011 at 8:42 AM, Mathieu Lonjaret
> wrote:
>> Well, since Ron's tree is based on Yiyus', and Ron's doesn't have that
>> patch, I think that means Yiyus' doesn't have it either. And yet,
>> Yiyus' works for me, so I doubt this b
On Tue, Mar 29, 2011 at 8:42 AM, Mathieu Lonjaret
wrote:
> Well, since Ron's tree is based on Yiyus', and Ron's doesn't have that
> patch, I think that means Yiyus' doesn't have it either. And yet,
> Yiyus' works for me, so I doubt this bug was the culprit for me. More
> like a 64 bits issue as Yi
Well, since Ron's tree is based on Yiyus', and Ron's doesn't have that
patch, I think that means Yiyus' doesn't have it either. And yet,
Yiyus' works for me, so I doubt this bug was the culprit for me. More
like a 64 bits issue as Yiyus mentionned earlier, no?
On Tue, Mar 29, 2011 at 5:06 PM, Chri
This one is extremely weird.
On Tue, Mar 29, 2011 at 2:00 AM, Mathieu Lonjaret
wrote:
> Hi all,
>
> this is probably trivial; this is what I get when trying to start 9vx:
>
> Warning! factotum can't protect itself from debugging: '#p/5' file does not
> exist
> init: warning: can't open #p/2/ctl:
Hello,
Mathieu Lonjaret wrote:
this last error keeps on repeating.
as a plan 9 tree I'm using the same old one that I kept using with rsc's
9vx (minimal tree provided by rsc, and later filled with more plan 9
stuff), could that be the issue? if yes, what do you guys for a tree
with ron's 9vx?
I've got a rejected-by-usenix paper somewhere about writing a 9p
encryption fs which you could stack on anything that served 9p:
exportfs, fossil, tarfs, whatever. It essentially attached to a 9p
server, you set the key, it encrypted/decrypted the data as it wrote
to its server.
The neat thing abo
There's two implementations that i know of: one is in russ' contrib, and
there another one called cbfs (i think), which is also on contrib, although
i don't remember where. The latter version could be russ' implementation
with changes, it's been a while since I tried either. Russ' didn't compile
at
Hello,
Back in 2009, someone on this list posted about encrypting /usr on a
Plan 9 laptop they had. Does anyone know how to encrypt a file system
on Plan 9? (I'm talking about encrypting the storage on disk, not just
the network connection to it.)
My intuition would be to look for a "crypt" com
Good call; yours starts without a problem, thanks.
On Tue, Mar 29, 2011 at 11:47 AM, yy wrote:
> ron's 9vx and mine are compiled differently in 64bits systems, so you
> can try mine and see if there is any difference, but I don't really
> know. I don't have any x86_64 system I can use to test 9vx
ron's 9vx and mine are compiled differently in 64bits systems, so you
can try mine and see if there is any difference, but I don't really
know. I don't have any x86_64 system I can use to test 9vx, so please
let me know if things get better (or worse). If you don't want to
download the whole vx32 t
I don't know enough about the causes to be of much help. Ron, Yiyus or
Russ might know.
Noah
On Tue, Mar 29, 2011 at 11:25 AM, Mathieu Lonjaret
wrote:
> Nothing remote or fancy here, just starting 9vx locally (-u glenda -r
> plan9vx) after having built it.
> However, it is a 64 bits linux and
Nothing remote or fancy here, just starting 9vx locally (-u glenda -r
plan9vx) after having built it.
However, it is a 64 bits linux and I haven't done anything special or
set any flag when building (cd src; make; make install). Should I?
On Tue, Mar 29, 2011 at 11:18 AM, Noah Evans wrote:
> I've
I've seen this behavior before, once using 9vx on a remote xsession
and once when using strace on a (broken) 9vx that was compiled for
32bit on a 64bit linux. Are there any mitigating factors that could be
causing your problem?
Noah
On Tue, Mar 29, 2011 at 11:00 AM, Mathieu Lonjaret
wrote:
> H
Hi all,
this is probably trivial; this is what I get when trying to start 9vx:
Warning! factotum can't protect itself from debugging: '#p/5' file does not
exist
init: warning: can't open #p/2/ctl: '#p/2' file does not exist
init: starting /bin/rc
FAILED
Warning! auth/factotum can't protect its
37 matches
Mail list logo