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,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 EF531217BF for ; Thu, 25 Jan 2024 23:38:41 +0100 (CET) Received: from tb-mx0.topicbox.com (tb-mx0.nyi.icgroup.com [10.90.30.73]) by tb-ob0.topicbox.com (Postfix) with ESMTP id 1A5EA1C718 for ; Thu, 25 Jan 2024 17:38:41 -0500 (EST) (envelope-from bounce.mMd8bda4d1e7af7ecdfef98b8e.r522be890-2105-11eb-b15e-8d699134e1fa@9fans.bounce.topicbox.com) Received: by tb-mx0.topicbox.com (Postfix, from userid 1132) id 1642ABFE161; Thu, 25 Jan 2024 17:38: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=F2GUEW3U 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-yw1-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=content-type:content-transfer-encoding:from :mime-version:subject:date:message-id:references:in-reply-to:to :list-help:list-id:list-post:list-subscribe:reply-to :list-unsubscribe; s=sysmsg-1; t=1706222320; bh=y2u3TsNePWfbHI+d 749Ipooa/V7i14MkelpcwUn8NXQ=; b=f9uaUsR1vEQhmzZIGhAdBZ9U5jUJpmL+ a5GSArXvt3kCylKny4qHuUA/I6LUGjXnu1eM4pxbsdwZgCG7+/88/zld75zreI9f z1SAciCbzXwOkQwJ2WHmzwunusxcEqDon9icPMUb6VPWDUOYB9aq/Dbw03Awkf8y fuY3qeGzdQo= ARC-Seal: i=2; a=rsa-sha256; cv=pass; d=topicbox.com; s=sysmsg-1; t= 1706222320; b=S3ocYSc6q2HrxtibEBpDcFF8H+79agoOVTUwCVqX2ywpBOoCnQ S0LjeqhAyKZEm31PTzdXaLAvbOjLj7UbYw3jQ/jHsoA74hwiZjr3N9SnosfkKU99 PlmjWeE/2/Bldaj0oZuoyRNSHgTIt971YiiSHp6qxhY2U+21//0DGqFn4= Authentication-Results: topicbox.com; arc=pass; dkim=pass (2048-bit rsa key sha256) header.d=gmail.com header.i=@gmail.com header.b=F2GUEW3U 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-yw1-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-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=F2GUEW3U 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.128.180 (mail-yw1-f180.google.com); spf=pass smtp.mailfrom=don.bailey@gmail.com smtp.helo=mail-yw1-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=sh+2rqKK; x-me-sender=none; x-ptr=pass smtp.helo=mail-yw1-f180.google.com policy.ptr=mail-yw1-f180.google.com; x-return-mx=pass header.domain=gmail.com policy.is_org=yes (MX Records found: alt2.gmail-smtp-in.l.google.com,gmail-smtp-in.l.google.com,alt1.gmail-smtp-in.l.google.com,alt3.gmail-smtp-in.l.google.com,alt4.gmail-smtp-in.l.google.com); x-return-mx=pass smtp.domain=gmail.com policy.is_org=yes (MX Records found: alt2.gmail-smtp-in.l.google.com,gmail-smtp-in.l.google.com,alt1.gmail-smtp-in.l.google.com,alt3.gmail-smtp-in.l.google.com,alt4.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= content-type:content-transfer-encoding:from:mime-version:subject :date:message-id:references:in-reply-to:to:list-help:list-id :list-post:list-subscribe:reply-to:list-unsubscribe; s=dkim-1; t=1706222320; x=1706308720; bh=y2u3TsNePWfbHI+d749Ipooa/V7i14Mk elpcwUn8NXQ=; b=f9ZB72P90kYeKlF2BzKDCw37BYBAdLavkprNVQfegu8j2wOj 2mlOiPmwFsS8e+u/A0Ppz0GVPylvEhEGPGAwmyTWbSzmcQF/CEa0QYjNxKxbSnkT dusz/5ZxWMNr70yA2Jrwpq8zAGxUqjrPhEUPuyfZ05tbXDuWYVfAEymT8+I= Received: from tb-mx1.topicbox.com (localhost.local [127.0.0.1]) by tb-mx1.topicbox.com (Postfix) with ESMTP id B0CED28DC21D for <9fans@9fans.net>; Thu, 25 Jan 2024 17:38:30 -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 5943696067E; Thu, 25 Jan 2024 17:38:30 -0500 ARC-Seal: i=1; a=rsa-sha256; cv=none; d=topicbox.com; s=arcseal; t= 1706222310; b=oDPWUIRlq5XhvUe2DCWGxxF1gACUzLpWB5JSVvBk3Gas4RUvQc +kaHr0txbT778RrRNaw5aMmm+bolOZl5lQ+inoslfH9rAV52IxUDsg/9ZsWGX1bP xKgBsDmXn3sZd7NXn+f6MoGFjb76yKa/9PWkSE2/pjqvvWu6mbxq7zf9g0MNOKVH PPtitI77yaBkJhoXoqZvTV/V/Skh02zAAHVIpuAVaDzkEpXCaVRyA9igO4BiHztF NjsqVTZVNu7bjCnONKC3ayzRvUR0lsCMY2wkrEBko7EIq/cw8qZZ2z0e/wFA9zW+ hq2NpiZwaYf/W5L7fyzda+/Jf8UGYHmnYH3g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d= topicbox.com; h=content-type:content-transfer-encoding:from :mime-version:subject:date:message-id:references:in-reply-to:to; s=arcseal; t=1706222310; bh=yxnmgXqewS2eebQ7K7VomslMiwVmCzBWjTh q0fM6Awk=; b=aw1ZCE+LPzb9Yy5lw+bny0bOLYctjMIp7zN6QkxmydZBgyNwmbb 8vWcOA+tSfqqIrdPS/h0Kf1GgBzZoLDCbZsCAJ+5EJxk/+tb0/E9NuB5hsguAoD7 ThOVscZQqPgGGozI+Hj9N+ogxcM0ibBNKTomWMiO08QkcGEFDyGX/YOnRZt5ASzu 6W+s+yzMo0cVAIpFT50hFOGFT7SlXHkfkXg4heyeUKw1hSpSRT++XdZjwsJjn/58 daIY067Mfhj3jwo78nR5mnnbK/jBeKRnbOqBaYN9JvRRdHbXkZN05UPsPYMvD+3O QMrl/gBGMaQWXSWG3Yv1jfryntONV+Tv5Rw== 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=F2GUEW3U 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.128.180 (mail-yw1-f180.google.com); spf=pass smtp.mailfrom=don.bailey@gmail.com smtp.helo=mail-yw1-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=sh+2rqKK; x-me-sender=none; x-ptr=pass smtp.helo=mail-yw1-f180.google.com policy.ptr=mail-yw1-f180.google.com; x-return-mx=pass header.domain=gmail.com policy.is_org=yes (MX Records found: alt2.gmail-smtp-in.l.google.com,gmail-smtp-in.l.google.com,alt1.gmail-smtp-in.l.google.com,alt3.gmail-smtp-in.l.google.com,alt4.gmail-smtp-in.l.google.com); x-return-mx=pass smtp.domain=gmail.com policy.is_org=yes (MX Records found: alt2.gmail-smtp-in.l.google.com,gmail-smtp-in.l.google.com,alt1.gmail-smtp-in.l.google.com,alt3.gmail-smtp-in.l.google.com,alt4.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: gggruggvucftvghtrhhoucdtuddrgedvkedrvdelhedgjeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpegtgffhgg fufffkfhgjvffosehtqhhmtdhhtdejnecuhfhrohhmpedfffhonhcutedruceurghilhgv hidfuceoughonhdrsggrihhlvgihsehgmhgrihhlrdgtohhmqeenucggtffrrghtthgvrh hnpeeguddvveeiieeufeegueetudegudefgfdvvdeggeeukedvtdeuieehgeelvdetffen ucffohhmrghinhepthhophhitggsohigrdgtohhmnecukfhppedvtdelrdekhedruddvke drudektddpvdeitddtmeefkedvmeeguddumegrudgskeemtgdtrggrmegrgeekvgemugdu sgehmeehlegrtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepihhnvghtpe dvtdelrdekhedruddvkedrudektddphhgvlhhopehmrghilhdqhiifuddqfhdukedtrdhg ohhoghhlvgdrtghomhdpmhgrihhlfhhrohhmpeeoughonhdrsggrihhlvgihsehgmhgrih hlrdgtohhmqe 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-yw1-f180.google.com; client-ip=209.85.128.180 Received: from mail-yw1-f180.google.com (mail-yw1-f180.google.com [209.85.128.180]) (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 17:38:30 -0500 (EST) (envelope-from don.bailey@gmail.com) Received: by mail-yw1-f180.google.com with SMTP id 00721157ae682-5ffd5620247so1753387b3.0 for <9fans@9fans.net>; Thu, 25 Jan 2024 14:38:30 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706222309; x=1706827109; h=to:in-reply-to:references:message-id:date:subject:mime-version:from :content-transfer-encoding:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=yxnmgXqewS2eebQ7K7VomslMiwVmCzBWjThq0fM6Awk=; b=sh+2rqKKW1Q6SVc7SjbUhWv90KMCZgjrqqSCPdSWKn8J/cQjzHjoOyaQKOOGhobptR WVtt7tIww8TK/9F8mzt1uqxDpeoQP5C6vdxrJbfnFwM+jBNDcNDB3x1TK7GiITTtcVxt +/fAw3cjb27gC58y5VCtSYVrgM/lPpR86Wtr2YuSZ76+cayDun5NHQCayhGlvPuWQCel MCzebMoDEwX/gMIRO4cDAcNypTARi1WKit+B+6sX5JQ0TeTQCfHH79mNz436AwCeLx8/ Y1mh6hZY8YFCw2JMpu/x36BKEx5XhXdgyfmciB5wKxPae6Ka8jckooNY2KA9i7mD2hM7 Eq5Q== X-Gm-Message-State: AOJu0YxLgx62dWUQhPfKDRsePj7mQFFMYnuKP3U7USK4AtDQrf9H+bfM rbvWoPnz8+9xOvCEI3DesvJ3dUi30d1ZcZYe6RCqkzTTSAypGXHQe/qM7JqP X-Google-Smtp-Source: AGHT+IFKsL+4G8EpxTujpdxSiRqYH6KjalPVctF+XFXsDQemEHvfnG65ZjTYhA4Hw1NZs5YnuLyGTQ== X-Received: by 2002:a81:498d:0:b0:5ff:9506:ca78 with SMTP id w135-20020a81498d000000b005ff9506ca78mr540857ywa.85.1706222309355; Thu, 25 Jan 2024 14:38:29 -0800 (PST) Received: from smtpclient.apple ([2600:382:411:a1b8:c0aa:a48e:d1b5:59a0]) by smtp.gmail.com with ESMTPSA id fr1-20020a05690c358100b005ebde3cfc12sm946747ywb.17.2024.01.25.14.38.28 for <9fans@9fans.net> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 25 Jan 2024 14:38:28 -0800 (PST) Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable From: "Don A. Bailey" Mime-Version: 1.0 (1.0) Subject: Re: Charting the Future: Envisioning Plan 9 Release 5 for the 9fans Community. [Was:Re: [9fans] Supported Notebooks] Date: Thu, 25 Jan 2024 17:38:18 -0500 Message-Id: References: <2A9D731F59EE68918E3D7E54F21B364A@eigenstate.org> In-Reply-To: <2A9D731F59EE68918E3D7E54F21B364A@eigenstate.org> To: 9fans <9fans@9fans.net> X-Mailer: iPhone Mail (21C66) Topicbox-Policy-Reasoning: allow: sender is a member Topicbox-Message-UUID: 795de2b8-bbd2-11ee-8a85-a2146a325df4 Archived-At: =?UTF-8?B?PGh0dHBzOi8vOWZhbnMudG9waWNib3guY29tL2dyb3Vwcy85?= =?UTF-8?B?ZmFucy9UNDJmMTFlMDI2NWJjZmExOC1NZDhiZGE0ZDFlN2FmN2VjZGZlZjk4?= =?UTF-8?B?YjhlPg==?= 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:Md8bda4d1e7af7ecdfef98b8e:1:8FF53HNUBTr5FEopPEjSNB278gz82MTucOZ_dJKfL4c Last I checked (you) were asking for people to sign up. What=E2=80=99s the = actual attendee count at this point?=20 > On Jan 25, 2024, at 5:33=E2=80=AFPM, ori@eigenstate.org wrote: >=20 > =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. >=20 > Considering submitting some WIP or opinion papers > on the details of how you plan to accomplish this. >=20 > Quoth vic.thacker@fastmail.fm: >> Dear 9fans, as enthusiasts and experts of Plan 9, you are undoubtedly aw= are of the unique position this operating system holds in the world of dist= ributed computing. Its influence on modern computing paradigms is undeniabl= e. 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 bel= oved system. This essay aims to articulate the rationale for Plan 9 Release= 5, focusing on the need for modernization, the potential for innovation, a= nd the practical considerations that align with our shared passions and exp= ertise. >>=20 >> The Need for Modernization >>=20 >> Technological Evolution: >> We've all witnessed the dramatic shifts in technology since Plan 9's las= t 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 advancem= ents in hardware, networking, and programming languages. This evolution is = crucial to ensure that Plan 9 remains an indispensable tool in our modern t= ech toolkit. >>=20 >> Security Enhancements: >> In our ever-connected world, the sophistication of cyber threats is a re= ality we cannot ignore. It is imperative that Plan 9 evolves to include cut= ting-edge security protocols, safeguarding our systems and the unique work = we do from emerging cyber risks. >>=20 >> 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, so= mething we, as 9fans, have always embraced. >>=20 >> Fostering Innovation >>=20 >> Research and Education: >> Plan 9=E2=80=99s 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. >>=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 ric= her 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. >>=20 >> Showcasing Plan 9=E2=80=99s Potential: >> Plan 9 Release 5 would be a powerful statement of our system's capabilit= ies, especially in burgeoning fields like cloud computing, IoT, and distrib= uted systems. This is our chance to demonstrate the adaptability and forwar= d-thinking design of Plan 9 to the wider world. >>=20 >> Practical Considerations >>=20 >> Resource Allocation: >> We understand the importance of efficient resource management in bringin= g Plan 9 Release 5 to fruition. This means tapping into our collective know= ledge, drawing on community contributions, and possibly exploring new partn= erships or funding avenues. >>=20 >> Backward Compatibility: >> Maintaining backward compatibility is essential to honor our past work a= nd ensure a smooth transition. We must respect the legacy of Plan 9 while c= harting a course for its future. >>=20 >> Documentation and Support: >> Enhanced documentation and support are crucial for the success of this n= ew release. As a community, we can collaborate to create resources that wil= l aid in adoption and usability, ensuring Plan 9 Release 5 becomes a tool w= e 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 >>> 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-Md8bda= 4d1e7af7ecdfef98b8e Delivery options: https://9fans.topicbox.com/groups/9fans/subscription