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-ob1.topicbox.com (tb-ob1.topicbox.com [64.147.108.173]) by inbox.vuxu.org (Postfix) with ESMTP id AA9462427F for ; Fri, 26 Jan 2024 07:23:11 +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 7ED133DEAF for ; Fri, 26 Jan 2024 01:23:10 -0500 (EST) (envelope-from bounce.mMa49c23ba2008bef8dd489ac1.r522be890-2105-11eb-b15e-8d699134e1fa@9fans.bounce.topicbox.com) Received: by tb-mx1.topicbox.com (Postfix, from userid 1132) id 7D19328E9DFD; Fri, 26 Jan 2024 01:23:10 -0500 (EST) ARC-Authentication-Results: i=3; topicbox.com; arc=pass (as.1.zohomail.eu=pass, ams.1.zohomail.eu=pass) smtp.remote-ip=136.143.169.10; dkim=pass (2048-bit rsa key sha256) header.d=rdklein.fr header.i=edou@rdklein.fr header.b=hFxfIoKW header.a=rsa-sha256 header.s=zoho x-bits=2048; dmarc=none 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=rdklein.fr; spf=pass smtp.mailfrom=edou@rdklein.fr smtp.helo=sender-op-o10.zoho.eu; x-internal-arc=fail (as.2.topicbox.com=pass, ams.2.topicbox.com=fail (message has been altered), as.1.zohomail.eu=pass, ams.1.zohomail.eu=fail (message has been altered)) (Message modified while forwarding at Topicbox) ARC-Message-Signature: i=3; a=rsa-sha256; c=relaxed/relaxed; d= topicbox.com; h=references:from:to:cc:subject:date:in-reply-to :message-id:mime-version:content-type:content-transfer-encoding :list-help:list-id:list-post:list-subscribe:reply-to :list-unsubscribe; s=sysmsg-1; t=1706250190; bh=bldjD+hnaw/iN1X9 JzV95Cc1SlI8cYqDv/hQzA2wnFs=; b=Q/nsqXMLzPaHM2YP4olFzwE0pqO7qcpK YY3ZpYhEnBCylXaFMOqMGtp2mZttOdDEMQZCfc59cF9V+i5wV6rZjqgoQ0sytMA7 PlLdTICmgs8b8uErQP4LmYfHcpN8BfGILFNbO4IBcZoHSCaUWmvEVw3gqveoXTXU xIoN5IEy0Yc= ARC-Seal: i=3; a=rsa-sha256; cv=pass; d=topicbox.com; s=sysmsg-1; t= 1706250190; b=b+NmsHcEqapq9I3rkg18G77J57YbCQwSTO/V4WLuvXPgV7d87Y eN0vLfDU7MOViYMYHjRZ12XZElhW8OnWjm5du8y0BZR2wiJfQBhztLqRolcUJPPR JaB8IKrJt1n7i+oj+3FWtNUc9FRO/DKZMUFg4rFm8N4XZjySlLlVfsUTU= Authentication-Results: topicbox.com; arc=pass (as.1.zohomail.eu=pass, ams.1.zohomail.eu=pass) smtp.remote-ip=136.143.169.10; dkim=pass (2048-bit rsa key sha256) header.d=rdklein.fr header.i=edou@rdklein.fr header.b=hFxfIoKW header.a=rsa-sha256 header.s=zoho x-bits=2048; dmarc=none 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=rdklein.fr; spf=pass smtp.mailfrom=edou@rdklein.fr smtp.helo=sender-op-o10.zoho.eu; x-internal-arc=fail (as.2.topicbox.com=pass, ams.2.topicbox.com=fail (message has been altered), as.1.zohomail.eu=pass, ams.1.zohomail.eu=fail (message has been altered)) (Message modified while forwarding at Topicbox) X-Received-Authentication-Results: tb-mx1.topicbox.com; arc=pass (as.1.zohomail.eu=pass, ams.1.zohomail.eu=pass) smtp.remote-ip=136.143.169.10; bimi=skipped (DMARC did not pass); dkim=pass (2048-bit rsa key sha256) header.d=rdklein.fr header.i=edou@rdklein.fr header.b=hFxfIoKW header.a=rsa-sha256 header.s=zoho x-bits=2048; dmarc=none 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=rdklein.fr; iprev=pass smtp.remote-ip=136.143.169.10 (sender-op-o10.zoho.eu); spf=pass smtp.mailfrom=edou@rdklein.fr smtp.helo=sender-op-o10.zoho.eu; x-aligned-from=pass (Address match); x-me-sender=none; x-ptr=pass smtp.helo=sender-op-o10.zoho.eu policy.ptr=sender-op-o10.zoho.eu; x-return-mx=pass header.domain=rdklein.fr policy.is_org=yes (MX Records found: mx2.zoho.eu,mx3.zoho.eu,mx.zoho.eu); x-return-mx=pass smtp.domain=rdklein.fr policy.is_org=yes (MX Records found: mx2.zoho.eu,mx3.zoho.eu,mx.zoho.eu); x-tls=pass smtp.version=TLSv1.2 smtp.cipher=ECDHE-RSA-AES256-GCM-SHA384 smtp.bits=256/256; x-vs=clean score=-100 state=0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=9fans.net; h=references :from:to:cc:subject:date:in-reply-to:message-id:mime-version :content-type:content-transfer-encoding:list-help:list-id :list-post:list-subscribe:reply-to:list-unsubscribe; s=dkim-1; t=1706250190; x=1706336590; bh=bldjD+hnaw/iN1X9JzV95Cc1SlI8cYqD v/hQzA2wnFs=; b=AAdhfGu2vNrtqgJUkTFr8xjul8FfMLFptvfrBMFEf9fiVFlf jWhSkrUoTen4Ly7ZNYTlw3ehSa4mvS08FV3eef4mdQtpgLeujB+0iGoSnJLR24ng 8Nwu1Phg6pTqpFvZQiXnGZnUvTjEfay8DrYm3DoyWGXk9ypPne/Ea6A3zSM= Received: from tb-mx1.topicbox.com (localhost.local [127.0.0.1]) by tb-mx1.topicbox.com (Postfix) with ESMTP id 0FF2528E99CC for <9fans@9fans.net>; Fri, 26 Jan 2024 01:22:58 -0500 (EST) (envelope-from edou@rdklein.fr) Received: from tb-mx1.topicbox.com (localhost [127.0.0.1]) by tb-mx1.topicbox.com (Authentication Milter) with ESMTP id CB7777E8E6E; Fri, 26 Jan 2024 01:22:58 -0500 ARC-Seal: i=2; a=rsa-sha256; cv=pass; d=topicbox.com; s=arcseal; t= 1706250178; b=KQwBNyW6xC3LkaKw9Wy5jTKZKw9qgjpa4DN2LYJzDkWf3AbyK6 BJnxu7zJ5XSEk6qpsndsGJP09WYfWewYSi7rr2XdZrmUbBCijYrmy6qdLps1BK81 FFkkG6oEJOqWdA40LCAOWMIyibcsaVe/oly2ncDQh+aFxSleMfzA4/7wE6yZZAq8 jZ+Uku0FsntqUWdOEFBFToQTxP7odtVrYxhkwr37Gtf+kXjhB3vXho3aEKQMDGwG X97EX+RwRZhfSBGcLCdCQcaP+JFAdUSDXLZunZUfSNGXHhw2tAIcBu7Ygm8jwUBG upPOF66f1ZYky/vxdB8ekTN3WY0X02QR7IKQ== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d= topicbox.com; h=references:from:to:cc:subject:date:in-reply-to :message-id:mime-version:content-type:content-transfer-encoding; s=arcseal; t=1706250178; bh=N1cW8Fylasxg5sHIQumM6IIDGGeB7QeTDtn TbvAHa2w=; b=BuUW6MxIqRgV15dcjXDagTM1L8liNyGByqffHhGO59dx7OeOJ3C Qi+6d1rs3r1ah73unuhJ/Aq+6VqGhijLedh3aZnvyoOqDsbFolyBPanbq176UsYC ETwULmbMmTfjVMvZNDN45ZVFM+qAtAWP4IBR39rBvy+fH2V0p+AQGI1CrXy+Sgt3 wGKOlnP8abQGwwnZUMm1Hawl9MyuCNyy2LeBuc8OwAIQSYX1Ui2R6GFfLGSm058T ok9LtYr1USTqVkQHXsoFrcU7rYajlYZZynFKFd3yZiIeY6GtbKVosuFniWnZU1kW mbxTykZhkW1BG7ej1jYLYn+bMF4k6b0Y+iw== ARC-Authentication-Results: i=2; tb-mx1.topicbox.com; arc=pass (as.1.zohomail.eu=pass, ams.1.zohomail.eu=pass) smtp.remote-ip=136.143.169.10; bimi=skipped (DMARC did not pass); dkim=pass (2048-bit rsa key sha256) header.d=rdklein.fr header.i=edou@rdklein.fr header.b=hFxfIoKW header.a=rsa-sha256 header.s=zoho x-bits=2048; dmarc=none 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=rdklein.fr; iprev=pass smtp.remote-ip=136.143.169.10 (sender-op-o10.zoho.eu); spf=pass smtp.mailfrom=edou@rdklein.fr smtp.helo=sender-op-o10.zoho.eu; x-aligned-from=pass (Address match); x-me-sender=none; x-ptr=pass smtp.helo=sender-op-o10.zoho.eu policy.ptr=sender-op-o10.zoho.eu; x-return-mx=pass header.domain=rdklein.fr policy.is_org=yes (MX Records found: mx2.zoho.eu,mx3.zoho.eu,mx.zoho.eu); x-return-mx=pass smtp.domain=rdklein.fr policy.is_org=yes (MX Records found: mx2.zoho.eu,mx3.zoho.eu,mx.zoho.eu); x-tls=pass smtp.version=TLSv1.2 smtp.cipher=ECDHE-RSA-AES256-GCM-SHA384 smtp.bits=256/256; x-vs=clean score=-100 state=0 X-ME-VSCause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdeliedgleduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnh htshculddquddttddmnecujfgurhepfhgfhffvvefuffgjkfggtgfgsehtqhertddtreej necuhfhrohhmpefgughouhgrrhguucfmlhgvihhnuceovgguohhusehrughklhgvihhnrd hfrheqnecuggftrfgrthhtvghrnhepiedtjedtteegtdehjeekudegkeduudffleehgeff kedugfeuieelveeuueetjefhnecuffhomhgrihhnpehtohhpihgtsghogidrtghomhenuc fkphepudefiedrudegfedrudeiledruddtpdejjedrudefiedrieejrddutddtnecuvehl uhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgvthepudefiedrudegfedrudeile druddtpdhhvghlohepshgvnhguvghrqdhophdqohdutddriihohhhordgvuhdpmhgrihhl fhhrohhmpeeovgguohhusehrughklhgvihhnrdhfrheq X-ME-VSScore: -100 X-ME-VSCategory: clean Received-SPF: pass (rdklein.fr: Sender is authorized to use 'edou@rdklein.fr' in 'mfrom' identity (mechanism 'include:zoho.eu' matched)) receiver=tb-mx1.topicbox.com; identity=mailfrom; envelope-from="edou@rdklein.fr"; helo=sender-op-o10.zoho.eu; client-ip=136.143.169.10 Received: from sender-op-o10.zoho.eu (sender-op-o10.zoho.eu [136.143.169.10]) (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>; Fri, 26 Jan 2024 01:22:55 -0500 (EST) (envelope-from edou@rdklein.fr) ARC-Seal: i=1; a=rsa-sha256; t=1706250171; cv=none; d=zohomail.eu; s=zohoarc; b=E3YFvWowH67GuwaoszGjqy/Pe0mh30kSDsSamvDW/RXKJ4nrzVnnt/GzdfLUtGWBarM+T+8fJTvSDx7WtayFfOROSpEJTPJQmwdQvg9eeE3PbBXPsQ5PgVTdTGf9d0oYRnoKKsAObY6q1ui6HS0yf06R/4ACgGWryhAr3R6fTCs= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.eu; s=zohoarc; t=1706250171; h=Content-Type:Content-Transfer-Encoding:Cc:Cc:Date:Date:From:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:Subject:To:To:Message-Id:Reply-To; bh=N1cW8Fylasxg5sHIQumM6IIDGGeB7QeTDtnTbvAHa2w=; b=NTn4prESiABGmz0oxgcdWIRdeQHSeTZchEz17KO/IQpoA4ag8b6LJXthogzzGX2y+8Kt/Ocl4WgAweRRse1juSuJZa4lg2KeE4L0ECUp3qCPFV4nF3a3ol9mOfLAmlhD9wP4niPI5Hk2RDyPmUwbyGFskNYT0vJB7TlgmaacZf8= ARC-Authentication-Results: i=1; mx.zohomail.eu; dkim=pass header.i=rdklein.fr; spf=pass smtp.mailfrom=edou@rdklein.fr; dmarc=pass header.from= Received: from venerable (100.67.136.77.rev.sfr.net [77.136.67.100]) by mx.zoho.eu with SMTPS id 1706250168119364.29947314432536; Fri, 26 Jan 2024 07:22:48 +0100 (CET) References: <2A9D731F59EE68918E3D7E54F21B364A@eigenstate.org> User-agent: mu4e 1.8.9; emacs 28.2 From: Edouard Klein To: 9fans <9fans@9fans.net> Cc: "Don A. Bailey" Subject: Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks] Date: Fri, 26 Jan 2024 07:20:57 +0100 In-reply-to: Message-ID: <87cytowr4k.fsf@rdklein.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-ZohoMailClient: External Topicbox-Policy-Reasoning: allow: sender is a member Topicbox-Message-UUID: 5c08fc7a-bc13-11ee-ae00-cf7019eea76d Archived-At: =?UTF-8?B?PGh0dHBzOi8vOWZhbnMudG9waWNib3guY29tL2dyb3Vwcy85?= =?UTF-8?B?ZmFucy9UNDJmMTFlMDI2NWJjZmExOC1NYTQ5YzIzYmEyMDA4YmVmOGRkNDg5?= =?UTF-8?B?YWMxPg==?= 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:Ma49c23ba2008bef8dd489ac1:1:HZujec_zBUZzGKVGsMYPcXR1YYbNSMLxobCbMKx4UVo I, for one, will attend, barring any incident. I will send my submission in a frenzy panic minutes before the deadline, as one usually does. "Don A. Bailey" writes: > Last I checked (you) were asking for people to sign up. What=E2=80=99s th= e actual attendee count at this point? > > >> On Jan 25, 2024, at 5:33=E2=80=AFPM, ori@eigenstate.org wrote: >> >> =EF=BB=BFAlso: 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 a= ware >>> 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 Pl= an 9 >>> Release 5 beckons, offering a pathway to not just preserve but also enh= ance >>> our beloved system. This essay aims to articulate the rationale for Pla= n 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 la= st >>> iteration. To keep Plan 9 at the forefront of utility and innovation, i= t's >>> essential to adapt and update our system in line with the latest advanc= ements >>> in hardware, networking, and programming languages. This evolution is c= rucial >>> 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 r= eality >>> we cannot ignore. It is imperative that Plan 9 evolves to include >>> cutting-edge security protocols, safeguarding our systems and the uniqu= e work >>> we do from emerging cyber risks. >>> >>> Hardware Compatibility: >>> The advent of new hardware architectures is an exciting challenge for u= s. >>> 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=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 cont= inued >>> 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 collaboration= s and >>> innovations. >>> >>> Showcasing Plan 9=E2=80=99s 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 distribu= ted >>> 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 bringi= ng >>> Plan 9 Release 5 to fruition. This means tapping into our collective >>> knowledge, drawing on community contributions, and possibly exploring n= ew >>> 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 wi= ll 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; i= t=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 ens= uring >>> 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, an= d the >>> community to make this a reality, honoring the legacy of Plan 9 while s= haping >>> its future. Let's embark on this journey together, shaping the next cha= pter >>> 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 t= hat it >>>>> would be easy to use for porting 9legacy or in fact any system. But i= t 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-Ma49c2= 3ba2008bef8dd489ac1 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription