From mboxrd@z Thu Jan 1 00:00:00 1970 From: smiley@zenzebra.mv.com To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> References: <86fwpz55nj.fsf@cmarib.ramside> <257867.782e4d7b.wsc0.mx@tumtum.plumbweb.net> <5ddd9deccbea5e8556dfc0c228b63311@ladd.quanstro.net> <86vcythf8h.fsf@cmarib.ramside> <86ipusd1wr.fsf@cmarib.ramside> Date: Wed, 6 Apr 2011 15:27:24 +0000 In-Reply-To: (Yaroslav's message of "Tue, 5 Apr 2011 22:50:12 +0300") Message-ID: <86zko3jt7n.fsf@cmarib.ramside> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] Making read(1) an rc(1) builtin? Topicbox-Message-UUID: cbd541ca-ead6-11e9-9d60-3106f5b1d025 Yaroslav writes: >> than appropriate for a line-oriented language like rc(1). =C2=A0As it st= ands, >> 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 car= y 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... --=20 +---------------------------------------------------------------+ |E-Mail: smiley@zenzebra.mv.com PGP key ID: BC549F8B| |Fingerprint: 9329 DB4A 30F5 6EDA D2BA 3489 DAB7 555A BC54 9F8B| +---------------------------------------------------------------+