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