From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <6e35c0620703070855y53430571pfe07a31aed3001af@mail.gmail.com> Date: Wed, 7 Mar 2007 08:55:17 -0800 From: "Jack Johnson" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] interesting potential targets for plan 9 and/or inferno In-Reply-To: <13426df10703062242q3cdc421fnb45a5e6342b8b5ee@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45EDE39F.8060006@proweb.co.uk> <474b349ac6f7a20920261a714df9b8ef@proxima.alt.za> <32a656c20703062152n6a9bb7b1qfefa9b7827e3a9af@mail.gmail.com> <13426df10703062202g29819385h5d4fe3db57b9867c@mail.gmail.com> <32a656c20703062216h18c65028lba8cc6d8ccde8bbc@mail.gmail.com> <13426df10703062242q3cdc421fnb45a5e6342b8b5ee@mail.gmail.com> Topicbox-Message-UUID: 19cd3f4a-ead2-11e9-9d60-3106f5b1d025 On 3/6/07, ron minnich wrote: > I actually agree with your points in many ways. I just don't know how > to get around the problem of showing this system to people. I have to admit, I'm a waffler (yum, waffles, but way off topic). I have no Plan 9 system running currently, but I managed to wade through the wiki and successfully get a server and netbooting terminals up at one point, and I love the system. But my day job requires certain tools that I neither have the time nor the skillset to reimplement on Plan 9, and though there are workarounds it does pose a barrier to adoption. Now me, I think obstacles were meant to overcome. If I were charged with trying to deploy, enforce adoption, whatever, I'd start with the low-hanging fruit. Something like Plan 9's DNS and DHCP integration is just genius, even for the monkeys who have only ever seen it done the Windows way. I'd probably introduce them to rc outside the Plan 9 environment so they can compare it to bash or whatever shell they've been using and see how much easier it is, then bring them into Plan 9 proper so they can see how much more powerful a shell script can be when supported by the right environment, and let them explore the environment that way, as an extension of the shell. My running joke when I try to explain my fascination with Plan 9 to others is that I always had questions like, "How do you do X?" and someone would respond, "Oh, we use awk for that." Especially for the people who don't enjoy the perspective of history, it really can be a paradigm shift to not need to build a network infrastructure or create and destroy a dozen objects to get at some trivial piece of data. That paradigm shift does haunt us with rio, as people have a heavy expectation of how a windowing environment should behave. One way to fix that is to change the windowing environment, but that may not be the right way. I've used the VNC trick in the past, but it would be nice to be able to resize the VNC window with the expected window behavior, using something like a kind of rootless VNC server, just pushing the app windows. I've seen single applications delivered by Citrix, RDP and now NoMachine NX. That kind of integration, where you could open a browser as if it were a native app (especially if it were coming from a self-hosted xen image) could lower that barrier to entry and help meet those expectations. > most of the Plan 9 guys are at google, running large Linux clusters > ... and I believe many of them carry macos systems around now. My question is, what did they take with them? Can we use that to leverage bringing people back across the bridge? -Jack P.S. And now we all thank Russ again for plan9ports.