From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <86ipx4s36p.fsf@cmarib.ramside> Date: Tue, 1 Feb 2011 12:20:46 -0500 Message-ID: From: Jacob Todd To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=00032555a81ec9128d049b3bc0a8 Subject: Re: [9fans] RESOLVED: recoving important header file rudely Topicbox-Message-UUID: a6c92aae-ead6-11e9-9d60-3106f5b1d025 --00032555a81ec9128d049b3bc0a8 Content-Type: text/plain; charset=UTF-8 On Feb 1, 2011 1:05 AM, wrote: > Reading about Plan 9, I was quite excited to install it. I was quite > excited when I first booted and ran it, too. But I distinctly felt my > heart sink a little the first time it hung. Since then, I've browsed > some of the OS source code and, having done that, I came to understand > why the system was so buggy. The core applications appear to be written > in a style of C programming reminiscent of the dawn of UNIX. While the > operating system architecture is BEAUTIFULLY designed (with the > exception, perhaps of that fossil/conf gotcha!), the C code used to > implement it doesn't seem to take advantage of any of the programming > paradigms that have emerged in the intervening 30 years... > What hasn't plan 9 adopted that would make it a better system? OOP? Plan 9 adopted (afaik) things like concurrency before other mainstream systems. Plan 9's namespaces are still unique to the system, and the way most things are represented as a fileserver is something very unique to plan 9/inferno. What programming paradigms do you think plan 9 shoul take advantage of? > Getting Plan 9 code to crash is almost too easy: > > term% mkdir trashdir && cd trashdir && mkdir x > term% touch `{i=0; while (test $i -lt 128) { echo -n abcdefghijklmnop; i=`{echo $i+1|hoc} } } > term% cp abc* abc* x > # watch the cp executable suicide > # now, make SURE there's nothing in this rio window that you want to keep... > term% rm abc* > # watch the rio window go bye bye! > Yes, plan 9's file name length can be a bit 'short' in some cases. The example you gave is a bit extreme, as fgb showed. When and why would you need a filename/path that long? --00032555a81ec9128d049b3bc0a8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Feb 1, 2011 1:05 AM, <smile= y@zenzebra.mv.com> wrote:
> Reading about Plan 9, I was quite excited to install it. =C2=A0I was q= uite
> excited when I first booted and ran it, too. =C2=A0But I distinctly fe= lt my
> heart sink a little the first time it hung. =C2=A0Since then, I've= browsed
> some of the OS source code and, having done that, I came to understand=
> why the system was so buggy. =C2=A0The core applications appear to be = written
> in a style of C programming reminiscent of the dawn of UNIX. =C2=A0Whi= le the
> operating system architecture is BEAUTIFULLY designed (with the
> exception, perhaps of that fossil/conf gotcha!), the C code used to > implement it doesn't seem to take advantage of any of the programm= ing
> paradigms that have emerged in the intervening 30 years...
>
What hasn't plan 9 adopted that would make it a better system? OOP? Pla= n 9 adopted (afaik) things like concurrency before other mainstream systems= . Plan 9's namespaces are still unique to the system, and the way most = things are represented as a fileserver is something very unique to plan 9/i= nferno. What programming paradigms do you think plan 9 shoul
take advantage of?
> Getting Plan 9 code to crash is almost too easy:
>
> term% mkdir trashdir && cd trashdir && mkdir x
> term% touch `{i=3D0; while (test $i -lt 128) { echo -n abcdefghijklmno= p; i=3D`{echo $i+1|hoc} } }
> term% cp abc* abc* x
> # watch the cp executable suicide
> # now, make SURE there's nothing in this rio window that you want = to keep...
> term% rm abc*
> # watch the rio window go bye bye!
>
Yes, plan 9's file name length can be a bit 'short' in some cas= es. The example you gave is a bit extreme, as fgb showed. When and why woul= d you need a filename/path that long?

--00032555a81ec9128d049b3bc0a8--