From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from duke.felloff.net ([216.126.196.34]) by ewsd; Mon Jun 24 05:36:25 EDT 2019 Message-ID: <45BFA44580EB5E1D05E448F9D5B01B30@felloff.net> Date: Mon, 24 Jun 2019 11:36:04 +0200 From: cinap_lenrek@felloff.net To: 9front@9front.org Subject: Re: [9front] 7c: compile error after sysupdate In-Reply-To: 2cd6ffe2-5acc-4803-a446-02f87863fa14@www.fastmail.com MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: progressive advanced session singleton-scale software content-driven controller yes. this is not a mistake. you need to create these directories manually or use /sys/lib/rootstub. if you have mail history, you might find the 9front announcement for arm64 with build instructions. -- cinap From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 108.95.88.138 ([108.95.88.138]) by ewsd; Mon Jun 24 09:51:32 EDT 2019 Date: Mon, 24 Jun 2019 09:50:02 -0400 From: Stanley Lieber To: 9front@9front.org Message-ID: <2d0fe7f2-36c9-4ecc-a5e7-2556d29be21c@Spark> In-Reply-To: <45BFA44580EB5E1D05E448F9D5B01B30@felloff.net> References: <45BFA44580EB5E1D05E448F9D5B01B30@felloff.net> Subject: Re: [9front] 7c: compile error after sysupdate X-Readdle-Message-ID: 2d0fe7f2-36c9-4ecc-a5e7-2556d29be21c@Spark MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="5d10d524_6b8b4567_4bba" List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: converged proxy method HTML software markup proxy --5d10d524_6b8b4567_4bba Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline http://fqa.9front.org/fqa8.html#8.9.3 sl --5d10d524_6b8b4567_4bba Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline

--5d10d524_6b8b4567_4bba-- From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by ewsd; Mon Jun 24 14:49:16 EDT 2019 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id AA9B74D4 for <9front@9front.org>; Mon, 24 Jun 2019 14:49:14 -0400 (EDT) Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Mon, 24 Jun 2019 14:49:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm3; bh=9egjMXQu0W85fldOlBsR7z71gYONJAj kCbYc5Plo9wo=; b=qCrAC5x2g/uL+qUe/KzkDC9Gd2gdwfEoDvSfi9rBCbPdgGN depbgkirAztoL+QzBq7cuOka2eVgbRvCDZ3TSx1a0QmeS9l7zNZMSsOohmeAXEbC IuRzbwBP7JV9T1YASu4k2a1JPjVhcmMRxt4TxgP9jAgfjls0GxAELenaIf1191Lw VIsWSGlEUO//dBhHNjoJ57/qhx57aYao7UL4Cf94mo2M964UgdQy2vaK8AA/lgQo 8fAyfAPR7ZjapGlt3aeJzxObl/irB2MvKIV1kQy9OWyVjdMDOfnsOjXz4QEgWUkl +drapEJavdyOAq/JyNG9gQZ2pk21RXcdHQusRmg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=9egjMX Qu0W85fldOlBsR7z71gYONJAjkCbYc5Plo9wo=; b=hDRzDmL9DAWmcS24PL44yn EzznC/wyhidw5M7po0KIq7gq6Ru4kN0V3i9eR9Ql7YkHUFz3X1GKwZ5ZWZko6XZh 92/1iYKGwsJb4Ca8C4hsBeDs/17NlLs0ohtx2ZqcOnFXqqAmTLcIpP0B5XoON17F 40kYGtD54LM5Wg13kXt6+zvsMSGri8uyo7KoLlIwCZke8hE0AMsyqy5qj2Ugsemf bQp3JslE3/IvnY9xXRaO6x45W/NFuMyFpBcxAcX8ewnwpTC2bwNp0fxuQHhJSfGm CNS2H+Tpd2aYdhHI8QVO0p/+BGKWJIOoNGaPGjB/P17h6GeW4X8wFvqmfil+z25A == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddruddvgddufeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfgfhthhgrnhcuifgrrhguvghnvghrfdcuoegvvghkvggv heejsehfrghsthhmrghilhdrfhhmqeenucfrrghrrghmpehmrghilhhfrhhomhepvggvkh gvvgehjeesfhgrshhtmhgrihhlrdhfmhenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy:

Received: by mailuser.nyi.internal (Postfix, from userid 501) id F24B6E00A2; Mon, 24 Jun 2019 14:49:13 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.6-730-g63f2c3b-fmstable-20190622v1 Mime-Version: 1.0 Message-Id: In-Reply-To: <45BFA44580EB5E1D05E448F9D5B01B30@felloff.net> References: <45BFA44580EB5E1D05E448F9D5B01B30@felloff.net> Date: Mon, 24 Jun 2019 19:48:18 +0100 From: "Ethan Gardener" To: 9front@9front.org Subject: Re: [9front] 7c: compile error after sysupdate Content-Type: text/plain List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: polling just-in-time factory descriptor controller On Mon, Jun 24, 2019, at 10:36 AM, cinap_lenrek@felloff.net wrote: > yes. this is not a mistake. you need to create these directories manually > or use /sys/lib/rootstub. okay. /arm64/include is missing from rootstub, resulting in: 7.c:10 6c: '/arm64/include' does not exist: /arm64/include/ureg.h mk: 6c -FTVw -I/sys/src/cmd 7.c : exit status=rc 18153: 6c 18158: error mk: date for (i ... : exit status=rc 15951: rc 18100: mk 18101: error term% lc /arm64 bin/ lib/ it doesn't make any include dirs. ah-ha!: term% lc /dist/plan9front/ .hg/ .hgignore arm64/ remove; bind; hg up -C; unmount; lc /arm64/include ape/ u.h ureg.h good! userspace and kernel builds now complete without error. > > if you have mail history, you might find the 9front announcement for arm64 > with build instructions. just checking, you know all this is happening when i'm not trying to do anything with arm64? term% whatis cputype objtype cputype=amd64 objtype=amd64 would it be a good idea to have sysupdate source rootstub? don't sleep-sysadmin, kids. i've got to clean up after running rootstub in $home . From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wr1-f45.google.com ([209.85.221.45]) by ewsd; Mon Jun 24 15:01:03 EDT 2019 Received: by mail-wr1-f45.google.com with SMTP id x4so15041067wrt.6 for <9front@9front.org>; Mon, 24 Jun 2019 12:00:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=g5ZEBs2SF1MtQfLZxi65MGeSmlZan9G8pMZ9dqlxHY4=; b=f1c36HtTNYHMGI1auhZd3dBWLRoU9PhMoUKgtHLTHLHpQdRJ0ROBBgSseSxy8U17WX 7V/svRC3r5u5t9VcisABMzcnpS3jIYiQlq9LwuvwZ5Weyc5GfDiGYmQ7N/P8rsdtOj8V NGAxtgpsU9hD7dzVeenp/HRTIN5OL8jQIX8fq6r2vP39d4ddpC3M5w8w6Re2DMTH+pWw ITty9sVI8upg/XOxYC/kErWOu4YSh5EGUK+DmlybXr5w/TmRG+RxIpI6DpB3dPEaK1zk XGk+reOjpYzAo4l+I9d/FMl/HvSe/EFx3ZLURXj6ze00xXtPVCN4X/kxN1wCXu+eThYh b0PQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=g5ZEBs2SF1MtQfLZxi65MGeSmlZan9G8pMZ9dqlxHY4=; b=TJddXCxEGjXC3pvYo0VBPA4j8NIwdXFiFfyuyGUaCRvH3+VsHtsnz4kPfr9vAGJJ21 RTDuXzgO8GE9O0Ui+G9K6F2Qr0C24ZHETZuhid4TkigS4D9jgJTCov/V2nKp5CN5bh0n Sr07o3rUU2aswA7R866LaQWKUzl+VTEoKKDLB07GeRDsTv/pfW9WBgsNkQuDdCSNNzdO OGK0kihJ6lxnLgF+/fYBznzIGNcfmT4/uKl0JZHiKXA7nQhy91uPxiZ9zK/pH0BKm8mQ +N/SsATxbyFK3hc9+exO+blE7zp9qcrVKrLUG03hlUxJ8a+cLerJLM7EciI76iS/wwe4 v+fw== X-Gm-Message-State: APjAAAVySAKlyzClqCB+X1BmINBJzm4BTa8BTNMa7AXUWOqDuWt2o642 fHS6taAAWxoWppBuSjI+xRVYVJ8OQ/qLdUEYlG+2BA== X-Google-Smtp-Source: APXvYqzRB6MPCydJYS1yPgnnefMD7G8IqQIYxNcTvj8NCamk8fSDAE8Wd6aUzcTFn/3kwVy0HFeou1tIIyd1VnopWnI= X-Received: by 2002:adf:efcb:: with SMTP id i11mr10384499wrp.188.1561402849973; Mon, 24 Jun 2019 12:00:49 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:adf:fac8:0:0:0:0:0 with HTTP; Mon, 24 Jun 2019 12:00:48 -0700 (PDT) In-Reply-To: References: <45BFA44580EB5E1D05E448F9D5B01B30@felloff.net> From: hiro <23hiro@gmail.com> Date: Mon, 24 Jun 2019 21:00:48 +0200 Message-ID: Subject: Re: [9front] 7c: compile error after sysupdate To: 9front@9front.org Content-Type: text/plain; charset="UTF-8" List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: encrypted mobile core realtime-aware service > got to clean up just time travel back to before you made the mess. that's what we have fs dumps for :) From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from duke.felloff.net ([216.126.196.34]) by ewsd; Mon Jun 24 15:04:51 EDT 2019 Message-ID: <021E44EDB2CBC6D1026A5D0D2A63D92F@felloff.net> Date: Mon, 24 Jun 2019 21:04:42 +0200 From: cinap_lenrek@felloff.net To: 9front@9front.org Subject: Re: [9front] 7c: compile error after sysupdate In-Reply-To: d61436a5-5036-4e57-846d-25f0d74f2e92@www.fastmail.com MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: blockchain core controller > would it be a good idea to have sysupdate source rootstub? i worked on this for a day and then gave up. its too hard and too complicated. sysupdate would need some check to update itself in case there needs to be stuff like this. but how do you deploy THAT change? the only way is to fork everything. have a thumbstone commit with the sysupdate change. and then the next sysupdate goes to a new repository. on the other hand, its not so easy to automate creating stuff in the root. initially, the root of the fileserver was readonly and the only way to create directories there was console command. what if you don't run sysupdate on the fileserver but from a cpu server? then you can't access the fileserver console. -- cinap From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by ewsd; Mon Jun 24 15:18:05 EDT 2019 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id DAC7A4DF for <9front@9front.org>; Mon, 24 Jun 2019 15:18:03 -0400 (EDT) Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Mon, 24 Jun 2019 15:18:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm3; bh=F9hqbvb7dfTTk49lpQS3qR2SBqmTusl v2bIzjoRX8JQ=; b=WFw+Q8kAvow1QB2CZNhWf3a2yLONnCDkatGjfDhVYybkobk BmA7f7mlr+2jhEwKjDF2dHrn/WofpAnfI/JNyWiAt+UNGqZ/+3eKlg/07ps53oF8 bLvcUdCO1EgygbySfIU+cEiLyadGHIazMsFzgIFeEip/a6eq05ZJdVPeMPY5g4Qh KbcR7HA+y/qfOAVRhKqelWtXjYEaJr+sjK4f8rvx6dq8F2tMpW3XL6ys9Owpcp4J slAq/UNb3xcyOlktEGSHvqRTm2WFVDbeGcjMP70kDBRzAaXVBhtBWr8ncOh42B3v TTM4j8IYeJehMkQtYZCkSgk6bLbL+23/zFb2Uww== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=F9hqbv b7dfTTk49lpQS3qR2SBqmTuslv2bIzjoRX8JQ=; b=hOtq5N0EHTmkFgeQBiXm9h PL1GYl3vgAG+LPm3kpb3Rb3umngMQ3yyEksa8szhDafiJs5Oyqfn13ttdut6H0CF xG/f/ZCmo0V1PMFLXgMPSzk5ZUyEM2GLMZPPC7C3JoKznXpUu8YFOYWvpIycwA9e xIw+XR5DsWM1ccUlduWL+SMXaMcKq8x4gc0Biqse6P8F3djHaJv/NExipg5nvLNT sqDJVYAGDs0d0/VjvsG7yGUnqvvv2J7ftear/RJ+T87bB0ko1hTgr3nsmVAf34A3 CPlYYC7uaKQdBDoI/SQ8hoNs16dMrYx6/3dTJNOqNM0CXREAhhMawF43xX8flxiA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddruddvgddufeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfgfhthhgrnhcuifgrrhguvghnvghrfdcuoegvvghkvggv heejsehfrghsthhmrghilhdrfhhmqeenucfrrghrrghmpehmrghilhhfrhhomhepvggvkh gvvgehjeesfhgrshhtmhgrihhlrdhfmhenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id 148A5E00A2; Mon, 24 Jun 2019 15:18:03 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.6-730-g63f2c3b-fmstable-20190622v1 Mime-Version: 1.0 Message-Id: <3d247913-b0ce-49e7-a87f-0140da712d6b@www.fastmail.com> In-Reply-To: References: <45BFA44580EB5E1D05E448F9D5B01B30@felloff.net>

Date: Mon, 24 Jun 2019 20:18:02 +0100 From: "Ethan Gardener" To: 9front@9front.org Subject: Re: [9front] 7c: compile error after sysupdate Content-Type: text/plain List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: structured NoSQL-scale lifecycle grid property backend On Mon, Jun 24, 2019, at 8:01 PM, hiro wrote: > > got to clean up > just time travel back to before you made the mess. > that's what we have fs dumps for :) > it certainly crossed my mind! :) From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wout3-smtp.messagingengine.com ([64.147.123.19]) by ewsd; Mon Jun 24 15:48:14 EDT 2019 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 42880536 for <9front@9front.org>; Mon, 24 Jun 2019 15:48:12 -0400 (EDT) Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Mon, 24 Jun 2019 15:48:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.fm; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm3; bh=/gUzzhhoPlPIKxHfg8i+zuOBl93AWXa 0pDxnAh95Qd4=; b=iIPmlcO8Qlv1d5cHNh0kuQOoFyOjCeEpK7y99+C3n0EglJd 1tgMLFMgA5xaGHHYeWmPNFrgyzyfls+s2pT9S7C6EctchfIOWjxEoFzvRyj7JmSg gnnynmBv8fKd1IU1T4PBZqJdy7io56buXs6ZcPUcr1vYmovIdJm677H7Ow6gII+5 ZwZNy1MHrabh1r/LzH84HZHBAAKGRy6LjV6NuvXdPGPr1cZQbH6vD0N+VuRuA7YY V3KyHNWQHtclJGwwVsCjZUdUIFWhwpkvLyDccJH8V4YmlCDx/sRznzt6ujwauZng VSsH+1CG+k1ooPrar6/+MrbBUbkCf7JznISMYog== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=/gUzzh hoPlPIKxHfg8i+zuOBl93AWXa0pDxnAh95Qd4=; b=o96sUhk0ewV75MiGFgzgAw O3JwxioZmLjrukeSvhJ6RaU3jhdESuNmBv6Y44hQyts9NgpP8TAazrbYYwRPkWWy Cml+uQTEsn7UKwLnFnPsierqW1W9Dpa8TRbZPnIhVLS/UpZx8RWbXJZ51xpKMK/f wkkYN0RsJO94FMC/M7RJw2JKQtnXp83fC/OHs9TY5wJzGwyUhukGs9shUm18MuWw se5k8CdAFKe4sCdeyAK5GZ8lLIaRDFzFgZUO+/n30KhxaqAP7XaC4ZKOmDvnacQd sMYtdgFnd+k/cxN9iFyGCC/kr6FnqR8pNkvQWp/R9pRaA4K9FjxMJD19Y7yiZNYw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddruddvgddugeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfgfhthhgrnhcuifgrrhguvghnvghrfdcuoegvvghkvggv heejsehfrghsthhmrghilhdrfhhmqeenucfrrghrrghmpehmrghilhhfrhhomhepvggvkh gvvgehjeesfhgrshhtmhgrihhlrdhfmhenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy:

Received: by mailuser.nyi.internal (Postfix, from userid 501) id 5E445E00A2; Mon, 24 Jun 2019 15:48:11 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.1.6-730-g63f2c3b-fmstable-20190622v1 Mime-Version: 1.0 Message-Id: <42f586ab-07a3-4d42-a7d3-e9e2971aa207@www.fastmail.com> In-Reply-To: <021E44EDB2CBC6D1026A5D0D2A63D92F@felloff.net> References: <021E44EDB2CBC6D1026A5D0D2A63D92F@felloff.net> Date: Mon, 24 Jun 2019 20:48:11 +0100 From: "Ethan Gardener" To: 9front@9front.org Subject: Re: [9front] 7c: compile error after sysupdate Content-Type: text/plain List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: non-blocking ISO-certified base template API STM frontend On Mon, Jun 24, 2019, at 8:05 PM, cinap_lenrek@felloff.net wrote: > > would it be a good idea to have sysupdate source rootstub? > > i worked on this for a day and then gave up. its too hard and > too complicated. > > sysupdate would need some check to update itself in case > there needs to be stuff like this. but how do you deploy > THAT change? the only way is to fork everything. have > a thumbstone commit with the sysupdate change. and then > the next sysupdate goes to a new repository. hmm... i've got an idea. as you say below, it won't help with adding dirs to /, but just for fun: i don't think you'd need a new repository, but you would need a way for sysupdate to check and update itself first. the first update would be trouble, you're right there. after that, it wouldn't be complex with one or two helper scripts. sysupdate could have just 2 lines (plus #!), the first running sysupdate-updater, the second execs sysupdate-doit. sysupdate-updater updates sysupdate-doit, but sysupdate and sysupdate-updater would be updated by hg as normal, because they're not running when hg is. not that the 2-line sysupdate would ever need updating. i could code this, if you'd like it. > on the other hand, its not so easy to automate creating > stuff in the root. initially, the root of the fileserver > was readonly and the only way to create directories there > was console command. what if you don't run sysupdate on > the fileserver but from a cpu server? then you can't > access the fileserver console. oh yes, of course.