9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Update system: Files not updated
Date: Mon, 11 Apr 2022 16:00:47 -0400	[thread overview]
Message-ID: <093A40A7B0284BB66AEC390EDD1686B2@eigenstate.org> (raw)
In-Reply-To: <871qy3wmgq.fsf@turtle-trading.net>

Quoth Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>:
> Hi all,
> 
> I have a script to create a QEMU image of 9front for
> <https://builds.sr.ht>.  One target is to produce a current snapshot
> from Git.  So I do
> 
>    sysupdate
>    cd /sys/src
>    mk nuke
>    mk all
>    mk install
> 
> The result creates a number of questions, here is one:
> 
> The procedure does not re-create these binaries:
> 
>         --rwxrwxr-x  116923 Jul 18  2021 /amd64/bin/import
>         --rwxrwxr-x  175444 Jul 18  2021 /amd64/bin/oexportfs
>         --rwxrwxr-x   64485 May 24  2020 /amd64/bin/ape/cp
>         --rwxrwxr-x   68120 May 24  2020 /amd64/bin/ape/mv
>         --rwxrwxr-x  298263 Apr  3  2021 /amd64/bin/games/jukebox
>         --rwxrwxr-x  182430 Apr  3  2021 /amd64/bin/games/jukefs
>         --rwxrwxr-x  162044 Apr  3  2021 /amd64/bin/games/playlistfs
> 
> These are leftovers from older versions or 9front, it seems.  Should
> they just be deleted?  Are they missing from "mk all" by accident?  Or
> do they serve some other purpose?
> 

Yes -- they've been removed.

	c613382caf1c0bffa38dc09f113d8c11dbc47628	-- removes juke
	407cf4ac6e59556b65d29b3c0de6ada6fdcc3cc7	-- removes cp, mv
	7efbea82c63846a281db36d3854e13d3ab5498d2	-- removes import, oexportfs


  reply	other threads:[~2022-04-11 20:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 17:37 Benjamin Riefenstahl
2022-04-11 20:00 ` ori [this message]
2022-04-20 15:36   ` Benjamin Riefenstahl
2022-04-20 15:54     ` Steve Simon
2022-04-12  1:32 ` Alex Musolino

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=093A40A7B0284BB66AEC390EDD1686B2@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).