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-ob1.topicbox.com (tb-ob1.topicbox.com [64.147.108.173]) by inbox.vuxu.org (Postfix) with ESMTP id 77512238E7 for ; Thu, 25 Jan 2024 16:35:42 +0100 (CET) Received: from tb-mx1.topicbox.com (tb-mx1.nyi.icgroup.com [10.90.30.61]) by tb-ob1.topicbox.com (Postfix) with ESMTP id 8F71B2C44E for ; Thu, 25 Jan 2024 10:35:41 -0500 (EST) (envelope-from bounce.mMa1c3a5392521b3f3bea77223.r522be890-2105-11eb-b15e-8d699134e1fa@9fans.bounce.topicbox.com) Received: by tb-mx1.topicbox.com (Postfix, from userid 1132) id 8FA64A2C215; Thu, 25 Jan 2024 10:35:41 -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=YpoR5bpU 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-qt1-f180.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=1706196941; bh=j6i/UMrqULFdUQnm /rDHJvzG7qApy9/2uVyQ74ye8qA=; b=J3dQiynGvFZrRC1wAZRA2ECzKYRd/wuV 0znCUk47S/EYBmrkXu4zX965SAhwnthdF50SF7VdfvV7P/WJ3l9CIBQXGyT7ShZG BkWze+Bdq+QMBGSag95OWPNFdX1LG8dvn0d+PevZTFDuh2QCCNEC6tYkNxzlHlaW DvinERhM6yw= ARC-Seal: i=2; a=rsa-sha256; cv=pass; d=topicbox.com; s=sysmsg-1; t= 1706196941; b=QWtdAMgmUjaDbrj1YYYhVPC/3DG6yr29T2h64QIkoExQrVkbDW SPNs3HIjBwhh1zBrOGgURZLBjK5niNVZdHKu+8tfoIWWhloQ30AtF1vYxhOOcOzQ rryvkSOlDlEYUVYdieWluZkEuu+9a5J3bPWsUjKl3HmeNS/lPd1DTB0p4= Authentication-Results: topicbox.com; arc=pass; dkim=pass (2048-bit rsa key sha256) header.d=gmail.com header.i=@gmail.com header.b=YpoR5bpU 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-qt1-f180.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-mx0.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=YpoR5bpU 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.160.180 (mail-qt1-f180.google.com); spf=pass smtp.mailfrom=don.bailey@gmail.com smtp.helo=mail-qt1-f180.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=Vdi3h6WR; x-me-sender=none; x-ptr=pass smtp.helo=mail-qt1-f180.google.com policy.ptr=mail-qt1-f180.google.com; x-return-mx=pass header.domain=gmail.com policy.is_org=yes (MX Records found: alt4.gmail-smtp-in.l.google.com,gmail-smtp-in.l.google.com,alt2.gmail-smtp-in.l.google.com,alt3.gmail-smtp-in.l.google.com,alt1.gmail-smtp-in.l.google.com); x-return-mx=pass smtp.domain=gmail.com policy.is_org=yes (MX Records found: alt4.gmail-smtp-in.l.google.com,gmail-smtp-in.l.google.com,alt2.gmail-smtp-in.l.google.com,alt3.gmail-smtp-in.l.google.com,alt1.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=1706196941; x=1706283341; bh=hG65maQ5KeKbEsIYHVvISD6LUlS+VHZU 5+ggwB9/f94=; b=D3JQDnRafC2abz26kBHE/Ctk9r7THHU62rFIT4FOe5DJ0KxE nTJgvQssTZklgRzQabtDtjf/iDIlzzVJhjFggekLdzanQmFUwgni9Nrg8JPJ6UML /OwPlCuNNiyVc17Vb3VUxT4EIRv26sRhsqXrTIo83ox3Dhktb62Kp9j1LSE= Received: from tb-mx0.topicbox.com (localhost.local [127.0.0.1]) by tb-mx0.topicbox.com (Postfix) with ESMTP id 58B2C2F024EA for <9fans@9fans.net>; Thu, 25 Jan 2024 10:35:23 -0500 (EST) (envelope-from don.bailey@gmail.com) Received: from tb-mx0.topicbox.com (localhost [127.0.0.1]) by tb-mx0.topicbox.com (Authentication Milter) with ESMTP id 023EA1F170A; Thu, 25 Jan 2024 10:35:23 -0500 ARC-Seal: i=1; a=rsa-sha256; cv=none; d=topicbox.com; s=arcseal; t= 1706196923; b=A6btYu1iihyCCAVHDzwdPnsXgClMlAcstrkbB0BqG55IIFurva gv9Gits9XEtkmZ8HU0vnyCARvAjN6fvKadhPzqA4YbpmgoPvd4TqF8RyT/nszjha taEEz16CWEiYwSJsa2asul5IRLYcipcUSgUNWnek2S4SIaIl64uwrDZB8aYBSg07 moIzqOonltFhnG6kE/wVvH+n/5rjjbHxUGszuKwrpQW9QKIqWkqS6oi86u4xDcY8 ouR7xgs7vJu2tk0UBJpDOlhm0+Lg+XFH0nHiPUCK8jIDjyXmwOvtwppyLZjPcz5k CWmsk8rZ0jiubdYRzziRLlaWDfYMwYHvyEUg== 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=1706196923; bh=4LN4p6gtr+3jd1ZEGESdEaGNswB9yCaqsM67B+XMFow=; b=ClWsXLtfhYwq O6JuO6m353QS0f3AqZ346xV4xBjtSmejCBXBWYaharfiU+FE5VJc5gB5LlsolSNJ eiJkF1pLm/Dv7V9X6CF9gvW4/KOOWM5eQkj4lwGCxfS+W7Cm8nUvRgxXCXOW8liF ZpZCcnc0K8fFRFP6tsv2Ri0cqtJJ9UWDU28IOGsEZiDmEulDB2rwDyFv2WbkgzQV AQ/VSukzOMMOdoWbh4Mp/U3sMbMcsPHRgJ0YI+RY4Pxn3AbBTvDGV+9ERA3pWUPb 6BXczNpbDOFgPA9z/KFsHJmYT8wMq9x64Md9VK12nzWRA3VfRjgHdUEDousYTro/ OYBQJWfDfA== ARC-Authentication-Results: i=1; tb-mx0.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=YpoR5bpU 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.160.180 (mail-qt1-f180.google.com); spf=pass smtp.mailfrom=don.bailey@gmail.com smtp.helo=mail-qt1-f180.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=Vdi3h6WR; x-me-sender=none; x-ptr=pass smtp.helo=mail-qt1-f180.google.com policy.ptr=mail-qt1-f180.google.com; x-return-mx=pass header.domain=gmail.com policy.is_org=yes (MX Records found: alt4.gmail-smtp-in.l.google.com,gmail-smtp-in.l.google.com,alt2.gmail-smtp-in.l.google.com,alt3.gmail-smtp-in.l.google.com,alt1.gmail-smtp-in.l.google.com); x-return-mx=pass smtp.domain=gmail.com policy.is_org=yes (MX Records found: alt4.gmail-smtp-in.l.google.com,gmail-smtp-in.l.google.com,alt2.gmail-smtp-in.l.google.com,alt3.gmail-smtp-in.l.google.com,alt1.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: gggruggvucftvghtrhhoucdtuddrgedvkedrvdelgedgheduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpeggfhgjhf ffkffuvfgtsegrtderredttdejnecuhfhrohhmpeffohhnuceurghilhgvhicuoeguohhn rdgsrghilhgvhiesghhmrghilhdrtghomheqnecuggftrfgrthhtvghrnhepgfejffefge fggfeliefgjeekgefftdejgfeludetuddulefguefgueeuvdfhueetnecuffhomhgrihhn pehtohhpihgtsghogidrtghomhenucfkphepvddtledrkeehrdduiedtrddukedtnecuve hluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgvthepvddtledrkeehrdduiedt rddukedtpdhhvghlohepmhgrihhlqdhqthduqdhfudektddrghhoohhglhgvrdgtohhmpd hmrghilhhfrhhomhepoeguohhnrdgsrghilhgvhiesghhmrghilhdrtghomheq 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-mx0.topicbox.com; identity=mailfrom; envelope-from="don.bailey@gmail.com"; helo=mail-qt1-f180.google.com; client-ip=209.85.160.180 Received: from mail-qt1-f180.google.com (mail-qt1-f180.google.com [209.85.160.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tb-mx0.topicbox.com (Postfix) with ESMTPS for <9fans@9fans.net>; Thu, 25 Jan 2024 10:35:22 -0500 (EST) (envelope-from don.bailey@gmail.com) Received: by mail-qt1-f180.google.com with SMTP id d75a77b69052e-42a0454899dso54116651cf.0 for <9fans@9fans.net>; Thu, 25 Jan 2024 07:35:22 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706196922; x=1706801722; 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=4LN4p6gtr+3jd1ZEGESdEaGNswB9yCaqsM67B+XMFow=; b=Vdi3h6WRaO9sTInEENvm5AtP183UMSbxHmykQwKXKSA7Urp9RSYUi8N3tcm+/oPN97 tB/XVCB4jI8ddCzhmmipv1EwgNwG1gKb2t/+/b2m6LPAdmCZrF95R/VYKKjWv5+cclLQ eaB5+F34E7CF0Chr1WKOA7Hxrs9Ux3B/3NKgQBa278l0qcqNnQHyOo0bCdLrvUAmB309 AxRX9z7GDwHmi8KBsekqh5dJxV9ePflUanq3LASczoJg1psOIKP4+Cq7VcCTLjyE0T82 I5fckMrOD5grlgUV9qd5vmkcp6D83GWOM1wNL6YOPiZXxU1ggwDv0MU4LgR823me3KO3 iAsQ== X-Gm-Message-State: AOJu0Yyx2G17E5GMBUOdZtLKeI0E7V5ZFS91jtbjHgKJ2SQwEhcZN0KL Fb8nVlSwENZSzIYIv+0C3KftKh8/NbWm+yumHc8Q6cFr+HBiFEHvYS13r8wQzAiwEcNamvVIj6/ MzpUH40g3QE4dlqfZhRIQ1ih1NXTxjvfq X-Google-Smtp-Source: AGHT+IHrEuwWhSoFSRdSCRfSZtUBfwOzNNUinJdI1/8mgg4vgSvIskaiXfcoK5QVG+s418N11g1zoEy0rdIbHzzJS+Y= X-Received: by 2002:ac8:5850:0:b0:42a:52c4:7f07 with SMTP id h16-20020ac85850000000b0042a52c47f07mr1467440qth.104.1706196922035; Thu, 25 Jan 2024 07:35:22 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Don Bailey Date: Thu, 25 Jan 2024 10:35:10 -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=000000000000747121060fc6ed10 Topicbox-Policy-Reasoning: allow: sender is a member Topicbox-Message-UUID: 5d735424-bb97-11ee-9e64-981d018c7b06 Archived-At: =?UTF-8?B?PGh0dHBzOi8vOWZhbnMudG9waWNib3guY29tL2dyb3Vwcy85?= =?UTF-8?B?ZmFucy9UNDJmMTFlMDI2NWJjZmExOC1NYTFjM2E1MzkyNTIxYjNmM2JlYTc3?= =?UTF-8?B?MjIzPg==?= 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:Ma1c3a5392521b3f3bea77223:1:xpydg9e5qEQCAh7yPmdyl4r4yQgXb4PIoRAXtlNhtRk --000000000000747121060fc6ed10 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Direction comes from people writing code... but you write code for 9front, yes? What does that have to do with mainline Plan 9? And what does that have to do with the direction set forth by the people that actually designed it? On Thu, Jan 25, 2024 at 7:20=E2=80=AFAM wrote: > This email suffers from a lack of semicolons; > > Bell labs is extremely dead at this point, and > direction comes from people writing code; once > the work begins, people are sometimes willing to > help -- but only once work begins. > > 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 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 comput= ing 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-Ma1c3a= 5392521b3f3bea77223 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription --000000000000747121060fc6ed10 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Direction comes from people writing code.= .. but you write code for 9front, yes? What does that have to do with mainl= ine Plan 9? And what does that have to do with the direction set forth by t= he people that actually designed it? 



On Thu, Jan 25, 2024 at 7:20 AM <ori@eigenstate.org> wrote:
This email suffers from a lack of semicolons;<= br />
Bell labs is extremely dead at this point, and
direction comes from people writing code; once
the work begins, people are sometimes willing to
help -- but only once work begins.

Quoth vic.thac= ker@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 di= stributed computing. Its influence on modern computing paradigms is undenia= ble. In the spirit of continuing this legacy, the prospect of Plan 9 Releas= e 5 beckons, offering a pathway to not just preserve but also enhance our b= eloved system. This essay aims to articulate the rationale for Plan 9 Relea= se 5, focusing on the need for modernization, the potential for innovation,= and the practical considerations that align with our shared passions and e= xpertise.
>
> 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 innov= ation, it's essential to adapt and update our system in line with the l= atest advancements in hardware, networking, and programming languages. This= evolution is crucial to ensure that Plan 9 remains an indispensable tool i= n 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 c= utting-edge security protocols, safeguarding our systems and the unique wor= k 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 preservin= g 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 computi= ng has always been a beacon for academic research and education. A new rele= ase would re-energize our academic endeavors, offering a modern platform fo= r 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 r= icher ecosystem around our shared passion. The development of Plan 9 Releas= e 5 could be a rallying point for our community, sparking new collaboration= s and innovations.
>
> Showcasing Plan 9’s Potential:
> Plan 9 Release 5 would be a powerful statement of our system's cap= abilities, especially in burgeoning fields like cloud computing, IoT, and d= istributed 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 bring= ing Plan 9 Release 5 to fruition. This means tapping into our collective kn= owledge, drawing on community contributions, and possibly exploring new par= tnerships 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 w= ill 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 kno= wledge, and the community to make this a reality, honoring the legacy of Pl= an 9 while shaping its future. Let's embark on this journey together, s= haping 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 syst= em. 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 d= ebug
> > 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-M0c2b725f078b954990ba13= ff
Delivery options: https://9fans.topicbox.com/gro= ups/9fans/subscription
= --000000000000747121060fc6ed10--