On 5/13/24 10:56, ibrahim via 9fans wrote: > > On Monday, 13 May 2024, at 4:39 PM, Jacob Moody wrote: >> Fine my dude, you don't have to call us Plan 9, you don't have to want to >> use our code. However I ask that you be mindful in how you talk to new users >> and don't assume that they have this same level of care for authenticity and >> "pure" code origins as you. > > You should read more carefully what I replied to the new user. It had nothing > to do with licenses at all.
In your original email, you only mention: > After you have collected enough experience I would stay with 9legacy and > ignore 9front. The reasoning for this is never given. By your immediate followup and complaining about licensing and "being REAL plan9" I figured this was your reason. I drew a path which spares him the frustrations during the time where he gets used to the system. And using 9vx is one way to set one step after the other. I'm wondering why you don't adjust it so that 9front can also be run there. As far as I can tell from once experimenting the reason why 9front doesn't run are your extensions to the kernel interface. 9vx is by far a better more plan9-ish > way to virtualize under linux. But thats your decision. The path I suggested > is the simplest one at least I think so. It takes less than 30 min to have a > running plan9 installation without any problems arising from file servers > without the problems of networking or data exchange. If you really believe > that the path I suggested was a bad one or isn't simpler than directly using > on of the plan9 distros I would really be surprised. This new guy has to > learn rc, acme, rio, about plan9.ini about > mouse shortcuts in acme. And do you really believe doing this directly on > 9legacy or 9front is simpler than by using 9vx ? Because I don't know why I should care about 9vx when every computer has hardware accelerated virtual machines. What is less frustrating I wonder? Telling someone to use some random unmaintained x86 userspace emulation shim or using any existing virtual machine programs that are actively maintained, packaged for their operating system, and much much more documented? We have spent a decent chunk of time making sure our code works under these modern virtual machines (and with acceleration), including writing things like virtio drivers. A virtual machine combined with a local instance of drawterm to access it is how I suggest most new users get started. > > If this guy reaches the 4.step he will find his own path to whatever fork he > pleases. So where exactly was my reply mindless ? I honestly thought that you were suggesting against using 9front for the reasons I stated, if you were indeed basing everything off of 9vx compatibility due to your opinion of it being a better choice than something like qemu or HyperV then I apologize for assuming incorrectly. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te051f230f2656bbb-M339bd65f5ceeb02ce28eedf7 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
