9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Don A. Bailey" <don.bailey@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community.  [Was:Re: [9fans] Supported Notebooks]
Date: Thu, 25 Jan 2024 17:38:18 -0500	[thread overview]
Message-ID: <AFCE0CF2-17F3-4B53-9916-0F5FEBA1F57F@gmail.com> (raw)
In-Reply-To: <2A9D731F59EE68918E3D7E54F21B364A@eigenstate.org>

Last I checked (you) were asking for people to sign up. What’s the actual attendee count at this point? 


> On Jan 25, 2024, at 5:33 PM, ori@eigenstate.org wrote:
> 
> Also: We're organizing IWP9 largely as a forum
> for folks like you to figure out how to make this
> all happen; there's going to be plenty of time
> between talks as well as hacking days to figure
> out what code needs to be written, what patches
> exist in people's local trees, plenty of napkins
> (and, if you're lucky, whiteboards) to figure out
> designs, and even get a head start on it.
> 
> Considering submitting some WIP or opinion papers
> on the details of how you plan to accomplish this.
> 
> Quoth vic.thacker@fastmail.fm:
>> Dear 9fans, as enthusiasts and experts of Plan 9, you are undoubtedly aware of the unique position this operating system holds in the world of distributed computing. Its influence on modern computing paradigms is undeniable. In the spirit of continuing this legacy, the prospect of Plan 9 Release 5 beckons, offering a pathway to not just preserve but also enhance our beloved system. This essay aims to articulate the rationale for Plan 9 Release 5, focusing on the need for modernization, the potential for innovation, and the practical considerations that align with our shared passions and expertise.
>> 
>> The Need for Modernization
>> 
>> Technological Evolution:
>> We've all witnessed the dramatic shifts in technology since Plan 9's last iteration. To keep Plan 9 at the forefront of utility and innovation, it's essential to adapt and update our system in line with the latest advancements in hardware, networking, and programming languages. This evolution is crucial to ensure that Plan 9 remains an indispensable tool in our modern tech toolkit.
>> 
>> Security Enhancements:
>> In our ever-connected world, the sophistication of cyber threats is a reality we cannot ignore. It is imperative that Plan 9 evolves to include cutting-edge security protocols, safeguarding our systems and the unique work we do from emerging cyber risks.
>> 
>> Hardware Compatibility:
>> The advent of new hardware architectures is an exciting challenge for us. Updating Plan 9 to support these new platforms means not only preserving its usability but also expanding our horizons to new forms of computing, something we, as 9fans, have always embraced.
>> 
>> Fostering Innovation
>> 
>> Research and Education:
>> Plan 9’s novel approach to system design and distributed computing has always been a beacon for academic research and education. A new release would re-energize our academic endeavors, offering a modern platform for continued exploration and learning, pushing the boundaries of what we can achieve with Plan 9.
>> 
>> Community Engagement:
>> A new version of Plan 9 stands to reinvigorate our community. This is an opportunity to deepen our engagement, attract new talent, and foster a richer ecosystem around our shared passion. The development of Plan 9 Release 5 could be a rallying point for our community, sparking new collaborations and innovations.
>> 
>> Showcasing Plan 9’s Potential:
>> Plan 9 Release 5 would be a powerful statement of our system's capabilities, especially in burgeoning fields like cloud computing, IoT, and distributed systems. This is our chance to demonstrate the adaptability and forward-thinking design of Plan 9 to the wider world.
>> 
>> Practical Considerations
>> 
>> Resource Allocation:
>> We understand the importance of efficient resource management in bringing Plan 9 Release 5 to fruition. This means tapping into our collective knowledge, drawing on community contributions, and possibly exploring new partnerships or funding avenues.
>> 
>> Backward Compatibility:
>> Maintaining backward compatibility is essential to honor our past work and ensure a smooth transition. We must respect the legacy of Plan 9 while charting a course for its future.
>> 
>> Documentation and Support:
>> Enhanced documentation and support are crucial for the success of this new release. As a community, we can collaborate to create resources that will aid in adoption and usability, ensuring Plan 9 Release 5 becomes a tool we can all be proud of.
>> 
>> Conclusion
>> 
>> The creation of Plan 9 Release 5 is more than a technological update; it’s a reaffirmation of our commitment to a system that has long been at the vanguard of computing innovation. This initiative is a step towards ensuring Plan 9's continued relevance, security, and functionality in the modern era. It's an opportunity to broaden its impact in the realms of research, education, and beyond. As 9fans, we have the passion, the knowledge, and the community to make this a reality, honoring the legacy of Plan 9 while shaping its future. Let's embark on this journey together, shaping the next chapter in the Plan 9 story.
>> 
>> 
>> Thank you for dedicating your time and attention.
>> --vic
>> 
>>> On Thu, Jan 25, 2024, at 05:48, Jacob Moody wrote:
>>> On 1/24/24 14:28, Michael Grunditz wrote:
>>>> I have looked at the reform code and I like how it is done. I think that it would be easy to use for porting 9legacy or in fact any system. But it is more work than a recompile.
>>>> 
>>>> Michael
>>> 
>>> It is certainly not drag and drop. Getting the arm64 compiler and
>>> linker working on
>>> 9legacy is already not what I would consider trivial due to drift in
>>> /sys/src/cmd/cc.
>>> So yes if you have enough understanding on how to work with and debug
>>> the compiler, the linker, and
>>> the kernel then perhaps you could call it "easy". I'll believe it when
>>> I see it.
>>> 

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T42f11e0265bcfa18-Md8bda4d1e7af7ecdfef98b8e
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2024-01-25 22:38 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24 15:47 [9fans] Supported Notebooks alex-ml
2024-01-24 16:07 ` David Leimbach via 9fans
2024-01-24 17:11 ` Don Bailey
2024-01-24 18:09 ` Jacob Moody
2024-01-24 20:28   ` Michael Grunditz
2024-01-24 20:48     ` Jacob Moody
2024-01-24 14:27       ` Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks] vic.thacker
2024-01-24 23:42         ` [9fans] Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community noam
2024-01-25  0:01           ` Lucas Francesco
2024-01-25  1:01         ` Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks] Don Bailey
2024-01-24 16:32           ` vic.thacker
2024-01-25  1:53             ` Don A. Bailey
2024-01-25  2:09               ` Jacob Moody
2024-01-25  2:23               ` Kurt H Maier via 9fans
2024-01-25  3:49                 ` Don A. Bailey
2024-01-25  6:38                   ` Kurt H Maier via 9fans
2024-01-25  2:42               ` Alex Musolino
2024-01-25  3:13                 ` Noam Preil
2024-01-25 14:10               ` hiro via 9fans
2024-01-25 16:44                 ` Don Bailey
2024-01-25 16:53                   ` Jacob Moody
2024-01-25 18:18                     ` Don Bailey
2024-01-25 17:07                   ` Kurt H Maier via 9fans
2024-01-25 17:10                     ` Don Bailey
2024-01-25 17:24                   ` Bakul Shah
2024-01-25 17:31                     ` Don Bailey
2024-01-25 18:00                       ` thedaemon via 9fans
2024-01-25 18:17                         ` Don Bailey
2024-01-25 19:43                           ` Eli Cohen
2024-01-25 21:17                             ` Don A. Bailey
2024-01-25 18:14                   ` Michael Misch
2024-01-25 18:21                     ` Re[2]: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was: " Alexandr Babic
2024-01-25 21:16                     ` Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: " Don A. Bailey
2024-01-25 18:42                   ` noam
2024-01-25 20:14                   ` ori
2024-01-26  4:08                   ` hiro
2024-01-25 20:37               ` ori
2024-01-25 21:09                 ` [9fans] P9F meetings (was: Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community) David Arnold
2024-01-25 21:23                   ` ori
2024-01-25 22:31                   ` Don A. Bailey
2024-01-25 22:03                 ` Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks] Don A. Bailey
2024-01-25 22:19                   ` Jacob Moody
2024-01-25 23:38                     ` Don A. Bailey
2024-01-26  0:00                       ` Jacob Moody
2024-01-26  1:23                         ` Don A. Bailey
2024-01-26  3:50                           ` Lucio De Re
2024-01-26  4:06                             ` Don A. Bailey
2024-01-26  1:01                       ` Michael Misch
2024-01-26  2:31                         ` Don A. Bailey
2024-01-25 18:03                           ` vic.thacker
2024-01-26  3:09                             ` Dan Cross
2024-01-26  3:52                           ` Jeremy Jackins
2024-01-26  5:08                           ` hiro
2024-01-25 22:40                   ` ori
2024-01-26  0:08                     ` Don A. Bailey
2024-01-26  0:51                       ` fig
2024-01-25  2:32             ` Noam Preil
2024-01-25  3:52               ` Don Bailey
2024-01-25  4:26                 ` Noam Preil
2024-01-24 21:17                   ` vic.thacker
2024-01-25  6:58                     ` Kurt H Maier via 9fans
2024-01-25  9:32                       ` Sergey Zhilkin
2024-01-25  6:31                   ` Lucio De Re
2024-01-25 14:14                     ` hiro via 9fans
2024-01-25 11:03         ` ori
2024-01-25 15:35           ` Don Bailey
2024-01-25 16:02             ` Jacob Moody
2024-01-25 17:22               ` Don Bailey
2024-01-25 17:34                 ` Jacob Moody
2024-01-25 18:54                   ` Don Bailey
2024-01-25 18:47                     ` noam
2024-01-25 20:29                       ` Don Bailey
2024-01-25 20:05             ` ori
2024-01-25 21:29               ` Don A. Bailey
2024-01-25 23:40               ` Charles Forsyth
2024-01-25 21:15         ` ori
2024-01-25 21:15         ` ori
2024-01-25 22:38           ` Don A. Bailey [this message]
2024-01-26  6:20             ` Edouard Klein
2024-01-26  6:48               ` noam
2024-01-26 15:44                 ` ibrahim via 9fans
2024-01-26 19:23                   ` g_patrickb via 9fans
2024-01-27  0:09                     ` Vester "Vic" Thacker
2024-01-27  9:44                       ` hiro via 9fans
2024-03-12  0:22                   ` Rui Carmo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AFCE0CF2-17F3-4B53-9916-0F5FEBA1F57F@gmail.com \
    --to=don.bailey@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).