From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.5 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_SIGNED,DKIM_VALID,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: from tb-ob21.topicbox.com (tb-ob21.topicbox.com [173.228.157.67]) by inbox.vuxu.org (Postfix) with ESMTP id D967623063 for ; Thu, 25 Jan 2024 02:02:12 +0100 (CET) Received: from tb-mx0.topicbox.com (tb-mx0.nyi.icgroup.com [10.90.30.73]) by tb-ob21.topicbox.com (Postfix) with ESMTP id 000071AA21 for ; Wed, 24 Jan 2024 20:02:10 -0500 (EST) (envelope-from bounce.mMfd6e6e0aa79a3314ba0caaf6.r522be890-2105-11eb-b15e-8d699134e1fa@9fans.bounce.topicbox.com) Received: by tb-mx0.topicbox.com (Postfix, from userid 1132) id A254EB6A8E6; Wed, 24 Jan 2024 20:02:10 -0500 (EST) ARC-Authentication-Results: i=2; topicbox.com; arc=pass; dkim=pass (2048-bit rsa key sha256) header.d=gmail.com header.i=@gmail.com header.b=R3MFCARB header.a=rsa-sha256 header.s=20230601 x-bits=2048; dmarc=pass policy.published-domain-policy=none policy.published-subdomain-policy=quarantine policy.applied-disposition=none policy.evaluated-disposition=none (p=none,sp=quarantine,d=none,d.eval=none) policy.policy-from=p header.from=gmail.com; spf=pass smtp.mailfrom=don.bailey@gmail.com smtp.helo=mail-ot1-f49.google.com; x-internal-arc=fail (as.1.topicbox.com=pass, ams.1.topicbox.com=fail (message has been altered)) (Message modified while forwarding at Topicbox) ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d= topicbox.com; h=mime-version:references:in-reply-to:from:date :message-id:subject:to:content-type:list-help:list-id:list-post :list-subscribe:reply-to:content-transfer-encoding :list-unsubscribe; s=sysmsg-1; t=1706144530; bh=YCiTGcfztHKWKR3L cuABqyuQfitigoA1a9I0geTNrfY=; b=cVOuwLL24sKYXP5mMfqBe49yk0uNSuUY eH44D5UBCyXUZdmdg1UlhzFn+8zqXYu9aU6lqGH7bvd8mEeuXWLZObaRfqQCnKd6 4uSkTjB1glc4vPNslulNtThRtBGmub8/cGjrtkNMxqjEFZ6HLoV3EPh6MQ5AmcpJ Ua7lfS0Z6tc= ARC-Seal: i=2; a=rsa-sha256; cv=pass; d=topicbox.com; s=sysmsg-1; t= 1706144530; b=OaH/FAyivoIveLlHP5G4NcnbMC9SgRtZnfc8AXgK3m+QCakkmu UUzzHY1vw2yLmqS7qY2O5jOXjP6G9w127vChh2gEMifYjRrLxsZV2Tx3yMuvK+Yl I90omf69IBzeAnFS0b1a5ZhQ4haitLD5UM2jaAxk4vhmm+LKOfXVZJRjI= Authentication-Results: topicbox.com; arc=pass; dkim=pass (2048-bit rsa key sha256) header.d=gmail.com header.i=@gmail.com header.b=R3MFCARB header.a=rsa-sha256 header.s=20230601 x-bits=2048; dmarc=pass policy.published-domain-policy=none policy.published-subdomain-policy=quarantine policy.applied-disposition=none policy.evaluated-disposition=none (p=none,sp=quarantine,d=none,d.eval=none) policy.policy-from=p header.from=gmail.com; spf=pass smtp.mailfrom=don.bailey@gmail.com smtp.helo=mail-ot1-f49.google.com; x-internal-arc=fail (as.1.topicbox.com=pass, ams.1.topicbox.com=fail (message has been altered)) (Message modified while forwarding at Topicbox) X-Received-Authentication-Results: tb-mx1.topicbox.com; arc=none (no signatures found); bimi=skipped (DMARC Policy is not at enforcement); dkim=pass (2048-bit rsa key sha256) header.d=gmail.com header.i=@gmail.com header.b=R3MFCARB header.a=rsa-sha256 header.s=20230601 x-bits=2048; dmarc=pass policy.published-domain-policy=none policy.published-subdomain-policy=quarantine policy.applied-disposition=none policy.evaluated-disposition=none (p=none,sp=quarantine,d=none,d.eval=none) policy.policy-from=p header.from=gmail.com; iprev=pass smtp.remote-ip=209.85.210.49 (mail-ot1-f49.google.com); spf=pass smtp.mailfrom=don.bailey@gmail.com smtp.helo=mail-ot1-f49.google.com; x-aligned-from=pass (Address match); x-google-dkim=pass (2048-bit rsa key) header.d=1e100.net header.i=@1e100.net header.b=Ukm48q3c; x-me-sender=none; x-ptr=pass smtp.helo=mail-ot1-f49.google.com policy.ptr=mail-ot1-f49.google.com; x-return-mx=pass header.domain=gmail.com policy.is_org=yes (MX Records found: gmail-smtp-in.l.google.com,alt1.gmail-smtp-in.l.google.com,alt2.gmail-smtp-in.l.google.com,alt4.gmail-smtp-in.l.google.com,alt3.gmail-smtp-in.l.google.com); x-return-mx=pass smtp.domain=gmail.com policy.is_org=yes (MX Records found: gmail-smtp-in.l.google.com,alt1.gmail-smtp-in.l.google.com,alt2.gmail-smtp-in.l.google.com,alt4.gmail-smtp-in.l.google.com,alt3.gmail-smtp-in.l.google.com); x-tls=pass smtp.version=TLSv1.2 smtp.cipher=ECDHE-RSA-AES256-GCM-SHA384 smtp.bits=256/256; x-vs=clean score=0 state=0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=9fans.net; h= mime-version:references:in-reply-to:from:date:message-id:subject :to:content-type:list-help:list-id:list-post:list-subscribe :reply-to:content-transfer-encoding:list-unsubscribe; s=dkim-1; t=1706144530; x=1706230930; bh=PAYWphULW0jFeAURIspJs+yk9WNByPVR afmBq0PLBog=; b=G3L9A5HllIaHh14MmV9AGLEw6De11/H7hXwUfdlN0q66qtyD 5TQlwE0HTsx61NHTm+Ee7C8IYgbrmQpe5OPBP1fHWC6bQOAlL9VJw9gXacw8s2qH YrTZ4iGQDjNa7bn3K/S0OLWfCk0rjSGv/c5Uupm199f3kfuqMJ92qPtSOnU= Received: from tb-mx1.topicbox.com (localhost.local [127.0.0.1]) by tb-mx1.topicbox.com (Postfix) with ESMTP id 40D7DA24863 for <9fans@9fans.net>; Wed, 24 Jan 2024 20:01:39 -0500 (EST) (envelope-from don.bailey@gmail.com) Received: from tb-mx1.topicbox.com (localhost [127.0.0.1]) by tb-mx1.topicbox.com (Authentication Milter) with ESMTP id D0FBF5E010A; Wed, 24 Jan 2024 20:01:39 -0500 ARC-Seal: i=1; a=rsa-sha256; cv=none; d=topicbox.com; s=arcseal; t= 1706144499; b=pKg1XXFM4mBy6UkXxaZow9rvxOSDePqIxkiKB4B7T0bFLsO3uK UU9lIBejpp5g9qzJ9yTlz8jRt5fyGtuzZ6MkpovKrpUMo95O+L8V4/wmfgxEaj+A fhrWico2CUsAaUX5jlrHEI8NrtowWKmgywctqlm8Q0OlwBDHAUkt8BqjVVnexSG2 eRqZxIoypslH9q6RCPIdP6RIUjzXMMMn0sHtAaT0JyDn39sTsSdJ2PKq8BZWJDvj /wgKfTovu3V3RNXAwuGKFaMmY3m5XPPhL37poqTr+1G1goqq2uwXlBctRluXMg06 kvUUZ22ZVfcVgWXH+sSHfVEa5tWFeOrDE52w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d= topicbox.com; h=mime-version:references:in-reply-to:from:date :message-id:subject:to:content-type; s=arcseal; t=1706144499; bh=v17zlypgwSgk7islG3I1t1yaVJELYrIO+A0djaXoV48=; b=Q6b+XXUBRDUP LOtN02VlEByY8Nk+eXMbo9JqMyzkxl49Y0/zJruCnVLI7yQsw0D5Yhiu3xjumhCI KBFttQBUJSoWDJ04jMyqwnzplXc3AUoxJIzqqommGgI6YOS+ymsrbHQ7j71X2Tfb MQUZMW0oMid9f5BTGcAa0aAZDt/0SHWMfG6l35KEaa568HWYKf2dQeAP55RwXVt0 yDnmuSYOR4RCqBscnehvpP8ss+BcMaZ3A6o0TntA4pgyqdq+ZdzAsR7jefU4YlxC 8st4ZEbt0oKUB3pYFvDPXHj7MZfvKR9w4VUgaYdm2L+cvrzC5iYyVPvM7WI1B6F/ tlbIr/m2kg== ARC-Authentication-Results: i=1; tb-mx1.topicbox.com; arc=none (no signatures found); bimi=skipped (DMARC Policy is not at enforcement); dkim=pass (2048-bit rsa key sha256) header.d=gmail.com header.i=@gmail.com header.b=R3MFCARB header.a=rsa-sha256 header.s=20230601 x-bits=2048; dmarc=pass policy.published-domain-policy=none policy.published-subdomain-policy=quarantine policy.applied-disposition=none policy.evaluated-disposition=none (p=none,sp=quarantine,d=none,d.eval=none) policy.policy-from=p header.from=gmail.com; iprev=pass smtp.remote-ip=209.85.210.49 (mail-ot1-f49.google.com); spf=pass smtp.mailfrom=don.bailey@gmail.com smtp.helo=mail-ot1-f49.google.com; x-aligned-from=pass (Address match); x-google-dkim=pass (2048-bit rsa key) header.d=1e100.net header.i=@1e100.net header.b=Ukm48q3c; x-me-sender=none; x-ptr=pass smtp.helo=mail-ot1-f49.google.com policy.ptr=mail-ot1-f49.google.com; x-return-mx=pass header.domain=gmail.com policy.is_org=yes (MX Records found: gmail-smtp-in.l.google.com,alt1.gmail-smtp-in.l.google.com,alt2.gmail-smtp-in.l.google.com,alt4.gmail-smtp-in.l.google.com,alt3.gmail-smtp-in.l.google.com); x-return-mx=pass smtp.domain=gmail.com policy.is_org=yes (MX Records found: gmail-smtp-in.l.google.com,alt1.gmail-smtp-in.l.google.com,alt2.gmail-smtp-in.l.google.com,alt4.gmail-smtp-in.l.google.com,alt3.gmail-smtp-in.l.google.com); x-tls=pass smtp.version=TLSv1.2 smtp.cipher=ECDHE-RSA-AES256-GCM-SHA384 smtp.bits=256/256; x-vs=clean score=0 state=0 X-ME-VSCause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdelvddgvdekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpeggfhgjhf ffkffuvfgtsegrtderredttdejnecuhfhrohhmpeffohhnuceurghilhgvhicuoeguohhn rdgsrghilhgvhiesghhmrghilhdrtghomheqnecuggftrfgrthhtvghrnhepgfejffefge fggfeliefgjeekgefftdejgfeludetuddulefguefgueeuvdfhueetnecuffhomhgrihhn pehtohhpihgtsghogidrtghomhenucfkphepvddtledrkeehrddvuddtrdegleenucevlh hushhtvghrufhiiigvpedtnecurfgrrhgrmhepihhnvghtpedvtdelrdekhedrvddutddr geelpdhhvghlohepmhgrihhlqdhothduqdhfgeelrdhgohhoghhlvgdrtghomhdpmhgrih hlfhhrohhmpeeoughonhdrsggrihhlvgihsehgmhgrihhlrdgtohhmqe X-ME-VSScore: 0 X-ME-VSCategory: clean Received-SPF: pass (gmail.com ... _spf.google.com: Sender is authorized to use 'don.bailey@gmail.com' in 'mfrom' identity (mechanism 'include:_netblocks.google.com' matched)) receiver=tb-mx1.topicbox.com; identity=mailfrom; envelope-from="don.bailey@gmail.com"; helo=mail-ot1-f49.google.com; client-ip=209.85.210.49 Received: from mail-ot1-f49.google.com (mail-ot1-f49.google.com [209.85.210.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tb-mx1.topicbox.com (Postfix) with ESMTPS for <9fans@9fans.net>; Wed, 24 Jan 2024 20:01:38 -0500 (EST) (envelope-from don.bailey@gmail.com) Received: by mail-ot1-f49.google.com with SMTP id 46e09a7af769-6e0eb1cf1f5so2075979a34.3 for <9fans@9fans.net>; Wed, 24 Jan 2024 17:01:38 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706144497; x=1706749297; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=v17zlypgwSgk7islG3I1t1yaVJELYrIO+A0djaXoV48=; b=Ukm48q3cXtahE0R5YXsG/PXTlezQZNZl0vLmbW3gf5ilMIXzEI/prxq2KJCB5XtE1q c5kaby2ENzOjNp5k26k02Zczcn+5voFy2OBXpPtqP1BR2U5YzLZ4Nh6/FO2O4slWE0/k NWvMBvpqRXZuXsqLOvipT60aKBgYnvSRoWOJ6hZ1n3Kg16iL0H9U9u5imMPx7F7EV+Q9 mYXc2FublooPlFYIBjjwpAls0aPQUHb7YZn78BH8YvcA62fVOa5pBO41x6C6kRmrtHLb TaGud3xJKar5fImGsvpCBsHCByOWGOou+x4X9u6rimLPrtuRSOmTeORNvqxX38cE6/+S Fngw== X-Gm-Message-State: AOJu0YyESBlOvamIbyeIbTf6XswTpMwmaFpByxojuTbMhDg4jvetI9+B HyEAsWFk/D1bZeWjuW/HZCzHoaCjdOkj6K5hdh3ES1AUz/EBoMCoc9jv3fZ2E+t2QLNs7Hbha5Y DFUEQLOinh8wocbdPI9V7AGgY9bnibLpS X-Google-Smtp-Source: AGHT+IHj6v//uK96raNI4hohZdCH1j9Nwi0cOYvdB4f0pH3oO+TIT1DPcsLzFmf6eicBuNkp0gGlAEeQWaF1gW07iA8= X-Received: by 2002:a54:4110:0:b0:3bd:a95d:8033 with SMTP id l16-20020a544110000000b003bda95d8033mr77800oic.94.1706144497472; Wed, 24 Jan 2024 17:01:37 -0800 (PST) MIME-Version: 1.0 References: <7FCFB39A-387F-437B-9CE1-874ABAC78C79@gmail.com> In-Reply-To: From: Don Bailey Date: Wed, 24 Jan 2024 20:01:25 -0500 Message-ID: Subject: Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks] To: 9fans <9fans@9fans.net> Content-Type: multipart/alternative; boundary=000000000000b519ee060fbab8cb Topicbox-Policy-Reasoning: allow: sender is a member Topicbox-Message-UUID: 4e7ddd1a-bb1d-11ee-9175-a410856a871e Archived-At: =?UTF-8?B?PGh0dHBzOi8vOWZhbnMudG9waWNib3guY29tL2dyb3Vwcy85?= =?UTF-8?B?ZmFucy9UNDJmMTFlMDI2NWJjZmExOC1NZmQ2ZTZlMGFhNzlhMzMxNGJhMGNh?= =?UTF-8?B?YWY2Pg==?= List-Help: List-Id: "9fans" <9fans.9fans.net> List-Post: List-Software: Topicbox v0 List-Subscribe: Precedence: list Reply-To: 9fans <9fans@9fans.net> Content-Transfer-Encoding: 7bit List-Unsubscribe: , Topicbox-Delivery-ID: 2:9fans:437d30aa-c441-11e9-8a57-d036212d11b0:522be890-2105-11eb-b15e-8d699134e1fa:Mfd6e6e0aa79a3314ba0caaf6:1:DZ4NdHuAyEdpizbO2neGc818pYrjnSS6yuOG1aMlGEs --000000000000b519ee060fbab8cb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Breh. No. On Wed, Jan 24, 2024 at 7:45=E2=80=AFPM 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 enhan= ce > 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=E2=80=99s novel approach to system design and distributed computin= g 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=E2=80=99s 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 adaptabili= ty > 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= =E2=80=99s > 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. B= ut > 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-Mfd6e6= e0aa79a3314ba0caaf6 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription --000000000000b519ee060fbab8cb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Breh. No.



O= n Wed, Jan 24, 2024 at 7:45 PM <vic.thacker@fastmail.fm> wrote:
Dear 9fans, as enthusiasts and experts o= f Plan 9, you are undoubtedly aware of the unique position this operating s= ystem 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 p= reserve 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 evol= ution 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 reali= ty we cannot ignore. It is imperative that Plan 9 evolves to include cuttin= g-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. U= pdating Plan 9 to support these new platforms means not only preserving its= usability but also expanding our horizons to new forms of computing, somet= hing we, as 9fans, have always embraced.

Fostering Innovation

Research and Education:
Plan 9’s novel approach to system design and distributed computing ha= s always been a beacon for academic research and education. A new release w= ould re-energize our academic endeavors, offering a modern platform for con= tinued exploration and learning, pushing the boundaries of what we can achi= eve with Plan 9.

Community Engagement:
A new version of Plan 9 stands to reinvigorate our community. This is an op= portunity to deepen our engagement, attract new talent, and foster a richer= ecosystem around our shared passion. The development of Plan 9 Release 5 c= ould 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 capabili= ties, especially in burgeoning fields like cloud computing, IoT, and distri= buted systems. This is our chance to demonstrate the adaptability and forwa= rd-thinking design of Plan 9 to the wider world.

Practical Considerations

Resource Allocation:
We understand the importance of efficient resource management in bringing P= lan 9 Release 5 to fruition. This means tapping into our collective knowled= ge, drawing on community contributions, and possibly exploring new partners= hips 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 char= ting 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 a= id in adoption and usability, ensuring Plan 9 Release 5 becomes a tool we c= an all be proud of.

Conclusion

The creation of Plan 9 Release 5 is more than a technological update; it&rs= quo;s a reaffirmation of our commitment to a system that has long been at t= he vanguard of computing innovation. This initiative is a step towards ensu= ring Plan 9's continued relevance, security, and functionality in the m= odern era. It's an opportunity to broaden its impact in the realms of r= esearch, education, and beyond. As 9fans, we have the passion, the knowledg= e, 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, shapin= g 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 thin= k that it would be easy to use for porting 9legacy or in fact any system. B= ut 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<= br /> > the compiler, the linker, and
> the kernel then perhaps you could call it "easy". I'll b= elieve it when
> I see it.
>

------------------------------------------
9fans: 9fans
Permalink: https:= //9fans.topicbox.com/groups/9fans/T42f11e0265bcfa18-Md302c7e36ed5f10a57504b= cd
Delivery options: https://9fans.topicbox.com/gro= ups/9fans/subscription
= --000000000000b519ee060fbab8cb--