From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <86zko3jt7n.fsf@cmarib.ramside> References: <86fwpz55nj.fsf@cmarib.ramside> <257867.782e4d7b.wsc0.mx@tumtum.plumbweb.net> <5ddd9deccbea5e8556dfc0c228b63311@ladd.quanstro.net> <86vcythf8h.fsf@cmarib.ramside> <86ipusd1wr.fsf@cmarib.ramside> <86zko3jt7n.fsf@cmarib.ramside> Date: Wed, 6 Apr 2011 15:32:17 +0000 Message-ID: From: Jacob Todd To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=0016e6d97286bcd41004a041b29d Subject: Re: [9fans] Making read(1) an rc(1) builtin? Topicbox-Message-UUID: cbe47e6a-ead6-11e9-9d60-3106f5b1d025 --0016e6d97286bcd41004a041b29d Content-Type: text/plain; charset=UTF-8 What are you running plan 9 on? The mouse shouldn't cause that to happen. On Apr 6, 2011 11:29 AM, wrote: > Yaroslav writes: > >>> than appropriate for a line-oriented language like rc(1). As it stands, >>> rc(1) can have it's cake, but it can't eat it without a fork(2). >> >> As it was stated earlier, a fork(2) is rather cheap here, so what's >> your concern then? >> Maybe it's time to forget the lectures about expensive forks and just cary on? > > That was supposed to be a joke. Apparently, no body got (or read) it. > :( > >> I bet you won't even notice much changes in your stats -c graph. > > Just moving my mouse causes change in my stats -cs graph, driving both > measurements up to 75% or so. When the system is at all loaded, the > mouse doesn't respond at all. (Which makes it kind of hard to use the > system, given that it's mouse-based!) I wish there were a way to renice > usb/kb... > > -- > +---------------------------------------------------------------+ > |E-Mail: smiley@zenzebra.mv.com PGP key ID: BC549F8B| > |Fingerprint: 9329 DB4A 30F5 6EDA D2BA 3489 DAB7 555A BC54 9F8B| > +---------------------------------------------------------------+ > --0016e6d97286bcd41004a041b29d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

What are you running plan 9 on? The mouse shouldn't cause that to ha= ppen.

On Apr 6, 2011 11:29 AM, <smiley@zenzebra.mv.com> wrote:
> Yaroslav <yarikos@g= mail.com> writes:
>
>>> than appropriate for a line-oriented language like rc= (1). =C2=A0As it stands,
>>> rc(1) can have it's cake, but = it can't eat it without a fork(2).
>>
>> As it was st= ated earlier, a fork(2) is rather cheap here, so what's
>> your concern then?
>> Maybe it's time to forget the l= ectures about expensive forks and just cary on?
>
> That was s= upposed to be a joke. Apparently, no body got (or read) it.
> :(
>
>> I bet you won't even notice much changes in your stat= s -c graph.
>
> Just moving my mouse causes change in my stats= -cs graph, driving both
> measurements up to 75% or so. When the sy= stem is at all loaded, the
> mouse doesn't respond at all. (Which makes it kind of hard to use= the
> system, given that it's mouse-based!) I wish there were a= way to renice
> usb/kb...
>
> --
> +------------= ---------------------------------------------------+
> |E-Mail: smiley@zenzebra.mv.= com PGP key ID: BC549F8B|
> |Fingerprint: 9329 DB4A 3= 0F5 6EDA D2BA 3489 DAB7 555A BC54 9F8B|
> +-------------------------= --------------------------------------+
>
--0016e6d97286bcd41004a041b29d--