[9fans] unknown error message

[9fans] unknown error message

[erik quanstrom]

> Thanks, that's what I was curious about. shoulda grepped but figured
> one of you would know off the top of your head. :)

is posting to 9fans now easier than grep?

probablly not.  recently i've been working with a
few non-plan 9 guys, and the ones that take the
time to look at the system are at first appalled
by the simplicity.  that's it?  really, that's it.  i've
learned to ignore that.  inevitably, a question
similar to this thread comes up.  how to i find xyz.
i get xyz error message.  well, g xyz /sys/src.
that's it?  really, that's it.

i think the complexity of most systems can knock
one of one's rhythm and forget that it can be
as appalingly simple as grep.

plan 9 is fairly unique in that it's a system one can
reasonablly hope to understand by reading the source.
that's it?  really, that's it.

- erik

Re: [9fans] unknown error message

[Mathieu Lonjaret]

[-- Attachment #1: Type: text/plain, Size: 557 bytes --]

Yes, it can be easier in a sense that you sometimes get the explanation
that you would not have gotten in a obvious manner by reading the code.

If I don't need the answer to the issue right away, and if I want to work
on something else in the meanwhile, it can be better to wait and see what
you wise guys come up with, rather that going head first and grok the
whole context where the piece of code is. Especially if I'm unfamiliar
with that part of the code.

Yes, it's a form of lazyness, but not just for the sake of being lazy ;)

Mathieu

[-- Attachment #2: Type: message/rfc822, Size: 4113 bytes --]

From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans]  unknown error message
Date: Sun, 13 Jun 2010 22:46:27 -0400
Message-ID: <20d109f0282a31f9707bb70db11c0864@kw.quanstro.net>

> Thanks, that's what I was curious about. shoulda grepped but figured
> one of you would know off the top of your head. :)

is posting to 9fans now easier than grep?

probablly not.  recently i've been working with a
few non-plan 9 guys, and the ones that take the
time to look at the system are at first appalled
by the simplicity.  that's it?  really, that's it.  i've
learned to ignore that.  inevitably, a question
similar to this thread comes up.  how to i find xyz.
i get xyz error message.  well, g xyz /sys/src.
that's it?  really, that's it.

i think the complexity of most systems can knock
one of one's rhythm and forget that it can be
as appalingly simple as grep.

plan 9 is fairly unique in that it's a system one can
reasonablly hope to understand by reading the source.
that's it?  really, that's it.

- erik

Re: [9fans] unknown error message

[Ethan Grammatikidis]

On 14 Jun 2010, at 03:46, erik quanstrom wrote:
>
> plan 9 is fairly unique in that it's a system one can
> reasonablly hope to understand by reading the source.
> that's it?  really, that's it.

Plan 9 has given me a feeling about computing I haven't had since my 8-
bit days. So refreshing!

Somewhat pointless post, I know, but I had to write something positive
after my last mail to a certain other list.

--
Complexity is not a function of the number of features. Some features
exist only because complexity was _removed_ from the underlying system.

[9fans] unknown error message

[Mathieu Lonjaret]

Hello,

I doubt it will help me debug my problems but out of curiosity, can
anyone tell me where this assertion is coming from please? Even better,
if you have a clue about what I was doing wrong at this point ;)

15014.35 a < t->size && t->size < b: assertion failed
btfs 15014: suicide: sys: trap: page fault pc=0x0001079b

Cheers,
Mathieu

Re: [9fans] unknown error message

[ron minnich]

On Sat, Jun 12, 2010 at 9:42 PM, Mathieu Lonjaret
<mathieu.lonjaret@gmail.com> wrote:
> Hello,
>
> I doubt it will help me debug my problems but out of curiosity, can
> anyone tell me where this assertion is coming from please? Even better,
> if you have a clue about what I was doing wrong at this point ;)
>
> 15014.35 a < t->size && t->size < b: assertion failed
> btfs 15014: suicide: sys: trap: page fault pc=0x0001079b


The proc will still be there in 'broken' state (I love that feature of
Plan 9 ... actually implemented it on Linux but doubt I could ever get
them to take that patch).

acid 15014
stk()

it's great.

ron

Re: [9fans] unknown error message

[erik quanstrom]

On Sat Jun 12 17:46:52 EDT 2010, mathieu.lonjaret@gmail.com wrote:
> Hello,
>
> I doubt it will help me debug my problems but out of curiosity, can
> anyone tell me where this assertion is coming from please? Even better,
> if you have a clue about what I was doing wrong at this point ;)
>
> 15014.35 a < t->size && t->size < b: assertion failed
> btfs 15014: suicide: sys: trap: page fault pc=0x0001079b
>

ron's excellent suggestion notwithstanding, this looks to
be a memory screw:

; g 'a < t->size && t->size < b' /sys/src
/sys/src/libc/port/pool.c:218: 	assert(a < t->size && t->size < b);


setting the various parinoia flags (pool(2)) will probablly help.

- erik

Re: [9fans] unknown error message

[Mathieu Lonjaret]

[-- Attachment #1: Type: text/plain, Size: 122 bytes --]

Thanks, that's what I was curious about. shoulda grepped but figured
one of you would know off the top of your head. :)

[-- Attachment #2: Type: message/rfc822, Size: 4105 bytes --]

From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] unknown error message
Date: Sat, 12 Jun 2010 23:35:14 -0400
Message-ID: <51db8037450bf53ea59616a1d4a2ccfb@coraid.com>

On Sat Jun 12 17:46:52 EDT 2010, mathieu.lonjaret@gmail.com wrote:
> Hello,
>
> I doubt it will help me debug my problems but out of curiosity, can
> anyone tell me where this assertion is coming from please? Even better,
> if you have a clue about what I was doing wrong at this point ;)
>
> 15014.35 a < t->size && t->size < b: assertion failed
> btfs 15014: suicide: sys: trap: page fault pc=0x0001079b
>

ron's excellent suggestion notwithstanding, this looks to
be a memory screw:

; g 'a < t->size && t->size < b' /sys/src
/sys/src/libc/port/pool.c:218: 	assert(a < t->size && t->size < b);


setting the various parinoia flags (pool(2)) will probablly help.

- erik