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.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: from tb-ob0.topicbox.com (tb-ob0.topicbox.com [64.147.108.117]) by inbox.vuxu.org (Postfix) with ESMTP id 1B14A23F19 for ; Thu, 25 Jan 2024 22:15:55 +0100 (CET) Received: from tb-mx1.topicbox.com (tb-mx1.nyi.icgroup.com [10.90.30.61]) by tb-ob0.topicbox.com (Postfix) with ESMTP id 32FCF19C38 for ; Thu, 25 Jan 2024 16:15:55 -0500 (EST) (envelope-from bounce.mM60f64be129dba1a4a40268e7.r522be890-2105-11eb-b15e-8d699134e1fa@9fans.bounce.topicbox.com) Received: by tb-mx1.topicbox.com (Postfix, from userid 1132) id 2CF86A5542E; Thu, 25 Jan 2024 16:15:55 -0500 (EST) ARC-Authentication-Results: i=2; topicbox.com; arc=pass; dkim=pass (1024-bit rsa key sha1) header.d=eigenstate.org header.i=@eigenstate.org header.b=X63LySBN header.a=rsa-sha1 header.s=mail x-bits=1024; dmarc=pass policy.published-domain-policy=none policy.applied-disposition=none policy.evaluated-disposition=none (p=none,d=none,d.eval=none) policy.policy-from=p header.from=eigenstate.org; spf=pass smtp.mailfrom=ori@eigenstate.org smtp.helo=mimir.eigenstate.org; 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=message-id:to:subject:date:from:in-reply-to :mime-version:content-type:content-transfer-encoding:list-help :list-id:list-post:list-subscribe:reply-to:list-unsubscribe; s= sysmsg-1; t=1706217355; bh=3bLce+CE1XG/6DxAnDe5mHuUT4E1lHz38Aka4 OhAB58=; b=EupLCK5XaXvUNZxCxC0u4uT9V0oVaO1ic8qBzIHKGvu5wZdP1eZMG IAfmBsnjoljJQ7KtXWXalSMvygECqevh+SnWWObg6OHHsVYdhby2B17kuiwDQkBk s+IxBOR3aqv9g5Enh2kut08iL01ZXnz7zdMw1h2oSCoakgA/FxNI0c= ARC-Seal: i=2; a=rsa-sha256; cv=pass; d=topicbox.com; s=sysmsg-1; t= 1706217355; b=Y2RIoWDKfwTpBA7DP1F6OvlTzQe47VJjJunhUWfZFaUz3uEs2P vzu4m3b1X24iF+EL5rWKLEJs9GTzoVoaWnncxQLBV6LDIBEoG75kIbQ194xs/TLj ViH6wTrChpMwindApslC1IXiEjzPqlSvayu87jQSI30PWXoE85y3oVews= Authentication-Results: topicbox.com; arc=pass; dkim=pass (1024-bit rsa key sha1) header.d=eigenstate.org header.i=@eigenstate.org header.b=X63LySBN header.a=rsa-sha1 header.s=mail x-bits=1024; dmarc=pass policy.published-domain-policy=none policy.applied-disposition=none policy.evaluated-disposition=none (p=none,d=none,d.eval=none) policy.policy-from=p header.from=eigenstate.org; spf=pass smtp.mailfrom=ori@eigenstate.org smtp.helo=mimir.eigenstate.org; 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 (1024-bit rsa key sha1) header.d=eigenstate.org header.i=@eigenstate.org header.b=X63LySBN header.a=rsa-sha1 header.s=mail x-bits=1024; dmarc=pass policy.published-domain-policy=none policy.applied-disposition=none policy.evaluated-disposition=none (p=none,d=none,d.eval=none) policy.policy-from=p header.from=eigenstate.org; iprev=pass smtp.remote-ip=206.124.132.107 (mimir.eigenstate.org); spf=pass smtp.mailfrom=ori@eigenstate.org smtp.helo=mimir.eigenstate.org; x-aligned-from=pass (Address match); x-me-sender=none; x-ptr=pass smtp.helo=mimir.eigenstate.org policy.ptr=mimir.eigenstate.org; x-return-mx=pass header.domain=eigenstate.org policy.is_org=yes (MX Records found: eigenstate.org,mail.pikopiko.org,kusuri.pikopiko.org,nokogiri.pikopiko.org); x-return-mx=pass smtp.domain=eigenstate.org policy.is_org=yes (MX Records found: eigenstate.org,mail.pikopiko.org,kusuri.pikopiko.org,nokogiri.pikopiko.org); 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=message-id :to:subject:date:from:in-reply-to:mime-version:content-type :content-transfer-encoding:list-help:list-id:list-post :list-subscribe:reply-to:list-unsubscribe; s=dkim-1; t= 1706217354; x=1706303754; bh=3bLce+CE1XG/6DxAnDe5mHuUT4E1lHz38Ak a4OhAB58=; b=K0r3CNpbf3aG1QQuX+gSEMbmn04xja90UwN1g8qIlRvaJjmCjEl fOTjmb5B0w11sB1z6mmCH5/schNZyl0MVkxf3ivE1ueuLE4ZDYscnJgjRgokWr5S jH3odR5st26PcRhrFAtXFxbbQPwVpMINns+QZdcQQkTn1r7dQDt4NxuQ= Received: from tb-mx1.topicbox.com (localhost.local [127.0.0.1]) by tb-mx1.topicbox.com (Postfix) with ESMTP id 3560CA54AFA for <9fans@9fans.net>; Thu, 25 Jan 2024 16:15:43 -0500 (EST) (envelope-from ori@eigenstate.org) Received: from tb-mx1.topicbox.com (localhost [127.0.0.1]) by tb-mx1.topicbox.com (Authentication Milter) with ESMTP id 0E413BB84CB; Thu, 25 Jan 2024 16:15:43 -0500 ARC-Seal: i=1; a=rsa-sha256; cv=none; d=topicbox.com; s=arcseal; t= 1706217343; b=Tb/peFo5/8Gm0AEQ/SImPbkLxJc4c9eqlvwGRMTXwEi3XJnyzA N3Rj9EcKuId29SEPbPfrZX7Pkxl1Hsqb2WmbKHsTEpL9xZcO3Tl6afxJzO3JmyFc KOg7tl5XdKJ1aj3Z5g7FRslvCe7TXE0oRCmRLW+VHW3PqqPXVNOK1a8TpsYtDFpC zUD1wiBoatDqfoWURc4CLtNkLS9qRLL6ZwRtOV5PmWIocb1io4V+3nulAdJi85Zu hSTQD8ebsG+J3HUap36Y7bzPA/PaGXwsOYFLGkFVmXTQ8C/H1YLtw7IjL4RPX2ys q8/xRDSSYXXjpUlKrBmkPhm20dISq2Cu53BA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d= topicbox.com; h=message-id:to:subject:date:from:in-reply-to :mime-version:content-type:content-transfer-encoding; s=arcseal; t=1706217343; bh=3nlhPds5wLkVxraOeBloZmXIVKhmNLGk6foi1g1gshU=; b= ByofrNCb75xv895JDmnsEGGNlyzq/0fxB6+M61JoYdQm50clPUjI3R69XxQcFA1l 1J3dqy0XByFrQ5Vtsf012L4oJBSynqBZc9qRYqqqHk1/GsHYerPf9VzbcNjofRg8 O5W0cMAeOcRB+I3D/I5zhk8DwyjjjyOqYrkoUvg4Cn7g4Xu3z5oXBBPkBGHfrOCG ylahdZs6Z2a3a+Rmh2KCB4JymsAjPwYb5zF0BItXe/LDBjywDTv7iZRi1GjTBAgX wWLtil4MDd8CI0OAT3rRNkP/fwfyJ3pwd5BTo5kHBaoaOSc0msPFGaSLhsan23jz r31x1kVhqxxQC/MZvwCwQA== ARC-Authentication-Results: i=1; tb-mx1.topicbox.com; arc=none (no signatures found); bimi=skipped (DMARC Policy is not at enforcement); dkim=pass (1024-bit rsa key sha1) header.d=eigenstate.org header.i=@eigenstate.org header.b=X63LySBN header.a=rsa-sha1 header.s=mail x-bits=1024; dmarc=pass policy.published-domain-policy=none policy.applied-disposition=none policy.evaluated-disposition=none (p=none,d=none,d.eval=none) policy.policy-from=p header.from=eigenstate.org; iprev=pass smtp.remote-ip=206.124.132.107 (mimir.eigenstate.org); spf=pass smtp.mailfrom=ori@eigenstate.org smtp.helo=mimir.eigenstate.org; x-aligned-from=pass (Address match); x-me-sender=none; x-ptr=pass smtp.helo=mimir.eigenstate.org policy.ptr=mimir.eigenstate.org; x-return-mx=pass header.domain=eigenstate.org policy.is_org=yes (MX Records found: eigenstate.org,mail.pikopiko.org,kusuri.pikopiko.org,nokogiri.pikopiko.org); x-return-mx=pass smtp.domain=eigenstate.org policy.is_org=yes (MX Records found: eigenstate.org,mail.pikopiko.org,kusuri.pikopiko.org,nokogiri.pikopiko.org); 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: gggruggvucftvghtrhhoucdtuddrgedvkedrvdelhedgheegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpefkvffuff fhjgggtgfgsehtkeejtddttdejnecuhfhrohhmpehorhhisegvihhgvghnshhtrghtvgdr ohhrghenucggtffrrghtthgvrhhnpeefgfevieduhfehieduteffveehffehjeejvefhue eghfevffeludejtdevgeegffenucffohhmrghinhepthhophhitggsohigrdgtohhmnecu kfhppedvtdeirdduvdegrddufedvrddutdejpdefjedrieehrdehgedrudegvdenucevlh hushhtvghrufhiiigvpedunecurfgrrhgrmhepihhnvghtpedvtdeirdduvdegrddufedv rddutdejpdhhvghlohepmhhimhhirhdrvghighgvnhhsthgrthgvrdhorhhgpdhmrghilh hfrhhomhepoehorhhisegvihhgvghnshhtrghtvgdrohhrgheq X-ME-VSScore: 0 X-ME-VSCategory: clean Received-SPF: pass (eigenstate.org: 206.124.132.107 is authorized to use 'ori@eigenstate.org' in 'mfrom' identity (mechanism 'ip4:206.124.132.96/28' matched)) receiver=tb-mx1.topicbox.com; identity=mailfrom; envelope-from="ori@eigenstate.org"; helo=mimir.eigenstate.org; client-ip=206.124.132.107 Received: from mimir.eigenstate.org (mimir.eigenstate.org [206.124.132.107]) (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>; Thu, 25 Jan 2024 16:15:42 -0500 (EST) (envelope-from ori@eigenstate.org) Received: from mimir.eigenstate.org (localhost [127.0.0.1]) by mimir.eigenstate.org (OpenSMTPD) with ESMTP id 1bd9379f for <9fans@9fans.net>; Thu, 25 Jan 2024 13:15:40 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=eigenstate.org; h=message-id :to:subject:date:from:in-reply-to:mime-version:content-type :content-transfer-encoding; q=dns; s=mail; b=baR5G8daF2o+nfb1ztB vwlSHl55fGVdf5eCXd6+0cw3Lwuuet0OpYWWJte8ha+jP1UsByCUZUu8TYHm8FbV JCzGTgM85NIXKefVMFFYP/YVP7ICM44qfSmB1VyJKRv4nWkPP7V5vHEZNpirkstU lS3liJ+h5HuVn2V1qYnugQSQ= Received: from stockyard (142.54.65.37.rev.sfr.net [37.65.54.142]) by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id 8231902c (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO) for <9fans@9fans.net>; Thu, 25 Jan 2024 13:15:40 -0800 (PST) Message-ID: <2A9D731F59EE68918E3D7E54F21B364A@eigenstate.org> To: 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 16:15:37 -0500 From: ori@eigenstate.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Topicbox-Policy-Reasoning: allow: sender is a member Topicbox-Message-UUID: e8f4c864-bbc6-11ee-8bd3-c32f0e34932b Archived-At: =?UTF-8?B?PGh0dHBzOi8vOWZhbnMudG9waWNib3guY29tL2dyb3Vwcy85?= =?UTF-8?B?ZmFucy9UNDJmMTFlMDI2NWJjZmExOC1NNjBmNjRiZTEyOWRiYTFhNGE0MDI2?= =?UTF-8?B?OGU3Pg==?= List-Help: List-Id: "9fans" <9fans.9fans.net> List-Post: List-Software: Topicbox v0 List-Subscribe: Precedence: list Reply-To: 9fans <9fans@9fans.net> List-Unsubscribe: , Topicbox-Delivery-ID: 2:9fans:437d30aa-c441-11e9-8a57-d036212d11b0:522be890-2105-11eb-b15e-8d699134e1fa:M60f64be129dba1a4a40268e7:1:IvtQrAsKhKuvAXkgPAjndFB8WZEuN83BztLdzlLO8z4 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 awa= re of the unique position this operating system holds in the world of distr= ibuted 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 belo= ved system. This essay aims to articulate the rationale for Plan 9 Release = 5, focusing on the need for modernization, the potential for innovation, an= d the practical considerations that align with our shared passions and expe= rtise. >=20 > The Need for Modernization >=20 > Technological Evolution:=20 > 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 advanceme= nts in hardware, networking, and programming languages. This evolution is c= rucial to ensure that Plan 9 remains an indispensable tool in our modern te= ch toolkit. >=20 > Security Enhancements:=20 > In our ever-connected world, the sophistication of cyber threats is a rea= lity we cannot ignore. It is imperative that Plan 9 evolves to include cutt= ing-edge security protocols, safeguarding our systems and the unique work w= e do from emerging cyber risks. >=20 > Hardware Compatibility:=20 > The advent of new hardware architectures is an exciting challenge for us.= Updating Plan 9 to support these new platforms means not only preserving i= ts usability but also expanding our horizons to new forms of computing, som= ething we, as 9fans, have always embraced. >=20 > Fostering Innovation >=20 > Research and Education:=20 > 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 relea= se 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. >=20 > 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 rich= er ecosystem around our shared passion. The development of Plan 9 Release 5= could be a rallying point for our community, sparking new collaborations a= nd innovations. >=20 > Showcasing Plan 9=E2=80=99s Potential:=20 > Plan 9 Release 5 would be a powerful statement of our system's capabiliti= es, especially in burgeoning fields like cloud computing, IoT, and distribu= ted systems. This is our chance to demonstrate the adaptability and forward= -thinking design of Plan 9 to the wider world. >=20 > Practical Considerations >=20 > Resource Allocation:=20 > We understand the importance of efficient resource management in bringing= Plan 9 Release 5 to fruition. This means tapping into our collective knowl= edge, drawing on community contributions, and possibly exploring new partne= rships or funding avenues. >=20 > Backward Compatibility: > Maintaining backward compatibility is essential to honor our past work an= d ensure a smooth transition. We must respect the legacy of Plan 9 while ch= arting a course for its future. >=20 > Documentation and Support:=20 > Enhanced documentation and support are crucial for the success of this ne= w 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. >=20 > Conclusion >=20 > 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 rese= arch, 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 whi= le shaping its future. Let's embark on this journey together, shaping the n= ext chapter in the Plan 9 story. >=20 >=20 > Thank you for dedicating your time and attention. > --vic >=20 > 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 th= at it would be easy to use for porting 9legacy or in fact any system. But i= t is more work than a recompile. > >>=20 > >> Michael=20 > >=20 > > 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. > >=20 ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T42f11e0265bcfa18-M60f64= be129dba1a4a40268e7 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription