[9fans] Supported Notebooks

[alex-ml]

Hello everyone,

I would like to know which hardware (apart from the hardware listed here: 
https://plan9.io/wiki/plan9/Supported_PC_hardware/index.html) is supported by 
Plan 9. Is there any experience, especially with regard to other Thinkpad 
models?

9front even runs on the MNT Reform, would the corresponding code be easily 
transferable to 9legacy?

Many thanks in advance!

Best regards, 
alex
--
9fans: 9fans
Permalink: 
https://9fans.topicbox.com/groups/9fans/T724dd319036f59d3-Me3be0af8080652c166755c6a
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

Re: [9fans] Supported Notebooks

[Don Bailey]

I used to run plan9 exclusively (main OS) between around 2004-2010 and I
had a lot of luck with Compaq and Thinkpad (Lenovo). In fact, I was
considering doing this again... but... instead of buying a newer laptop and
worrying about chip compatibility, I actually am considering buying an
older compatible Thinkpad on Ebay. They are only a couple hundred dollars
now and honestly are fine speed-wise to run something as low intensity as
plan9. Something to consider.

D


On Wed, Jan 24, 2024 at 12:08 PM  wrote:

> Hello everyone,
>
> I would like to know which hardware (apart from the hardware listed here:
> https://plan9.io/wiki/plan9/Supported_PC_hardware/index.html) is
> supported by Plan 9. Is there any experience, especially with regard to
> other Thinkpad models?
>
> 9front even runs on the MNT Reform, would the corresponding code be easily
> transferable to 9legacy?
>
> Many thanks in advance!
>
> Best regards,
> alex
> *9fans * / 9fans / see discussions
>  + participants
>  + delivery options
>  Permalink
> 
>

--
9fans: 9fans
Permalink: 
https://9fans.topicbox.com/groups/9fans/T724dd319036f59d3-Mbab6b8f6ddabb38867797364
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

Re: [9fans] Supported Notebooks

[David Leimbach via 9fans]

Or you could just run 9front?Sent from my iPhoneOn Jan 24, 2024, at 10:48 AM, alex...@posteo.de wrote:
Hello everyone,I would like to know which hardware (apart from the hardware listed here: https://plan9.io/wiki/plan9/Supported_PC_hardware/index.html) is supported by Plan 9. Is there any experience, especially with regard to other Thinkpad models?9front even runs on the MNT Reform, would the corresponding code be easily transferable to 9legacy?Many thanks in advance!Best regards, alex

9fans
  / 9fans / see
discussions
  +
participants
  +
delivery options
Permalink

Re: [9fans] Supported Notebooks

[Jacob Moody]

On 1/24/24 09:47, alex...@posteo.de wrote:
> Hello everyone,
> 
> I would like to know which hardware (apart from the hardware listed here: 
> https://plan9.io/wiki/plan9/Supported_PC_hardware/index.html 
> ) is supported 
> by Plan 9. Is there any experience, especially with regard to other Thinkpad 
> models?
> 
> 9front even runs on the MNT Reform, would the corresponding code be easily 
> transferable to 9legacy?

It is likely transferable but it will certainly not be easy, the code has 
drifted quite a bit at this point.
I would suggest giving 9front a try first, but it sounds like you have already 
ruled that out.


Thanks,
moody


--
9fans: 9fans
Permalink: 
https://9fans.topicbox.com/groups/9fans/T724dd319036f59d3-M66908ce5c382ef598ed46645
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

Re: [9fans] Supported Notebooks

[Michael Grunditz]

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 

> 24 jan. 2024 kl. 20:28 skrev Jacob Moody :
> 
> On 1/24/24 09:47, alex...@posteo.de wrote:
>> Hello everyone,
>> 
>> I would like to know which hardware (apart from the hardware listed here: 
>> https://plan9.io/wiki/plan9/Supported_PC_hardware/index.html 
>> ) is supported 
>> by Plan 9. Is there any experience, especially with regard to other Thinkpad 
>> models?
>> 
>> 9front even runs on the MNT Reform, would the corresponding code be easily 
>> transferable to 9legacy?
> 
> It is likely transferable but it will certainly not be easy, the code has 
> drifted quite a bit at this point.
> I would suggest giving 9front a try first, but it sounds like you have 
> already ruled that out.
> 
> Thanks,
> moody
> 

--
9fans: 9fans
Permalink: 
https://9fans.topicbox.com/groups/9fans/T724dd319036f59d3-M3200fc2fdc9a396b144cee47
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

Re: [9fans] Supported Notebooks

[Jacob Moody]

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/T724dd319036f59d3-M495d507e61f64a8d7f97b074
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

Re: [9fans] Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community.

[Lucas Francesco]

Yeah, can we keep chatgpt generated wall of texts outside of the 9fans
mailing list ?

On Wed, 24 Jan 2024 at 20:58,  wrote:
>
> Quoth vic.thac...@fastmail.fm:
> > [redacted for sanity]
> 
> This is AI-generated spam, right? :P
> 
> - Noam Preil
> 

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

Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks]

[Don A. Bailey]

Tbf I took it as genuine. 

One reason I responded with no is that Rob noted that further 9 releases should 
not be a release at all, but should be fluid updates through the network. I 
think if 9 lives on it should be that was, as intended. 

I am not a fan of the weird 9front split from the standard repo. I’d prefer the 
sources to be managed by the foundation and would like to only receive patches 
through them. 

D


> On Jan 24, 2024, at 8:50 PM, vic.thac...@fastmail.fm wrote:
> 
> To clarify, my message represented a genuine exploration of the idea of 
> envisioning a new release.
> 
> --vic
> 
> 
>> On Thu, Jan 25, 2024, at 10:01, Don Bailey wrote:
>> Breh. No.
>> 
>> 
>> 
>>> On Wed, Jan 24, 2024 at 7:45 PM  wrote:
>>> 
>>> 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 

Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks]

[Jacob Moody]

On 1/24/24 19:53, Don A. Bailey wrote:
> Tbf I took it as genuine. 
> 
> One reason I responded with no is that Rob noted that further 9 releases 
> should not be a release at all, but should be fluid updates through the 
> network. I think if 9 lives on it should be that was, as intended. 

I have a hard time following what "fluid updates through the network" is 
supposed to mean.
If you mean that patches should be made by the community then that is exactly 
what 9front is.

> 
> I am not a fan of the weird 9front split from the standard repo. I’d prefer 
> the sources to be managed by the foundation and would like to only receive 
> patches through them. 

Why do you dislike 9front? 9front works with the foundation, we have a regular 
committer who is directly
in the foundation.

>> On Jan 24, 2024, at 8:50 PM, vic.thac...@fastmail.fm wrote:
>>
>> To clarify, my message represented a genuine exploration of the idea of 
>> envisioning a new release.
>>
>> --vic

9front is exactly what you're envisioning, we keep the system up to date to 
keep it working in the
modern world. Modern hardware support, modern compatibility with software as 
required, all this stuff.

I don't know where you folks think the code is going to come from, there really 
isn't that much activity
outside of 9front. If you want to personally take up the lead and fix 
everything bug-for-bug starting
again from 4e or 9legacy be my guest. But all I see here is asking for others 
to do the work.

- moody


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

Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks]

[Noam Preil]

It might help to believe that if you wrote actual ideas about what
should be done.

- Noam Preil


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

Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks]

[vic . thacker]

To clarify, my message represented a genuine exploration of the idea of 
envisioning a new release.

--vic


On Thu, Jan 25, 2024, at 10:01, Don Bailey wrote:
> Breh. No.
>
>
>
> On Wed, Jan 24, 2024 at 7:45 PM  wrote:
>
>> 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 

Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks]

[Kurt H Maier via 9fans]

On Wed, Jan 24, 2024 at 08:53:30PM -0500, Don A. Bailey wrote:
> Tbf I took it as genuine. 
> 
> One reason I responded with no is that Rob noted that further 9 releases 
> should not be a release at all, but should be fluid updates through the 
> network. I think if 9 lives on it should be that was, as intended. 

might want to focus on advice from people who use plan 9, instead

> I am not a fan of the weird 9front split from the standard repo. I’d prefer 
> the sources to be managed by the foundation and would like to only receive 
> patches through them. 

what is weird about forking unmaintained software?

khm

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

[9fans] Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community.

[noam]

Quoth vic.thac...@fastmail.fm:
> [redacted for sanity]

This is AI-generated spam, right? :P

- Noam Preil


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

Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks]

[Don Bailey]

Breh. No.



On Wed, Jan 24, 2024 at 7:45 PM  wrote:

> 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.
> >

Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks]

[Alex Musolino]

> One reason I responded with no is that Rob noted that further 9
> releases should not be a release at all, but should be fluid updates
> through the network.  I think if 9 lives on it should be that was,
> as intended.

I agree.  Maybe we could use some sort of distributed source control
system.

--
Cheers,
Alex Musolino


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

Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks]

[vic . thacker]

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-Md302c7e36ed5f10a57504bcd
Delivery options: 

Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks]

[Noam Preil]

That seems like a lot of work, though; surely, we can all just share a
rootfs over 9p!!


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

Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks]

[Don A. Bailey]

I use it. It’s also my advice. It wasn’t “advice” from Rob, it was a design 
choice. There’s more value in that than “advice”. 

Not interested in your theoretical discussions or trolling. Thanks.

D

> On Jan 24, 2024, at 10:44 PM, Kurt H Maier via 9fans <9fans@9fans.net> wrote:
> 
> On Wed, Jan 24, 2024 at 08:53:30PM -0500, Don A. Bailey wrote:
>> Tbf I took it as genuine.
>> 
>> One reason I responded with no is that Rob noted that further 9 releases 
>> should not be a release at all, but should be fluid updates through the 
>> network. I think if 9 lives on it should be that was, as intended.
> 
> might want to focus on advice from people who use plan 9, instead
> 
>> I am not a fan of the weird 9front split from the standard repo. I’d prefer 
>> the sources to be managed by the foundation and would like to only receive 
>> patches through them.
> 
> what is weird about forking unmaintained software?
> 
> khm

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

Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks]

[Don Bailey]

I've been posting on 9fans for 20 years, hacking the kernel as long, and
porting it to various chips and SoCs for as long. I don't have to prove
anything to you.



On Wed, Jan 24, 2024 at 10:50 PM Noam Preil  wrote:

> It might help to believe that if you wrote actual ideas about what
> should be done.
> 
> - Noam Preil
> 

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

Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks]

[Noam Preil]

I wasn't talking to you :P

That was a response to the post that looked AI-generated. I sincerely
apologize if I accidentally responded to your post instead, but I don't
think I did

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

Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks]

[vic . thacker]

Thank you for your valuable insight. I appreciate being corrected when wrong. 
The purpose of my query regarding the development of a vision for Plan 9 is to 
deeply understand the collective aspirations and goals of our community. I 
firmly believe that aligning our collective efforts with a mutually recognized 
and understood vision is significantly more effective than proceeding without 
clear objectives. However, I must admit to feeling somewhat adrift, as I have 
yet to encounter specific discussions or documents that clearly outline such a 
vision. My intention is not to challenge or criticize but to seek clarity and 
insight. I am in the process of exploring and seeking to comprehend the 
community's vision to guide my contributions. However, it is challenging for me 
to engage effectively in a community when there's no unified vision to align 
with. Efforts expended in vain are seldom appreciated by anyone.

Thank you. 
-vic

On Thu, Jan 25, 2024, at 13:26, Noam Preil wrote:
> I wasn't talking to you :P
> 
> That was a response to the post that looked AI-generated. I sincerely
> apologize if I accidentally responded to your post instead, but I don't
> think I did

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

Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks]

[Lucio De Re]

On 1/25/24, Noam Preil  wrote:
> I wasn't talking to you :P
>
> That was a response to the post that looked AI-generated. I sincerely
> apologize if I accidentally responded to your post instead, but I don't
> think I did
>
If you find it difficult to quote at least the sender of the message
you are responding to, then it is not surprising that people
misunderstand your intentions.

Lucio.

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

Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks]

[Kurt H Maier via 9fans]

On Wed, Jan 24, 2024 at 10:49:33PM -0500, Don A. Bailey wrote:
> I use it. It’s also my advice. It wasn’t “advice” from Rob, it was a design 
> choice. There’s more value in that than “advice”. 

It's a design choice nobody can implement, because it presumes that the
starting point is correct enough that you never have to break
compatibility.  It's a wonderful design choice to make, for instance,
regarding a system you never intend to touch again.

> Not interested in your theoretical discussions or trolling. Thanks.

You talk about receiving patches from the foundation but *I'm* the one
with theoretical discussions or trolling?

Wild.

khm

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

Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks]

[Kurt H Maier via 9fans]

On Thu, Jan 25, 2024 at 06:17:39AM +0900, vic.thac...@fastmail.fm wrote:
> However, it is challenging for me to engage effectively in a community
> when there's no unified vision to align with.

We all like Plan 9.  Identify the people who like the same things about
Plan 9 that you like about Plan 9, and engage with them.  It might be
easier than taking on the whole community simultaneously.

khm

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