9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Steve Simon <steve@quintile.net>
To: 9front@9front.org
Subject: Re: [9front] Update system: Boot files not updated
Date: Mon, 11 Apr 2022 20:47:37 +0100	[thread overview]
Message-ID: <BF744723-3EAE-46A7-8490-5E915E8F1AA1@quintile.net> (raw)
In-Reply-To: <6947dc36-79c0-4888-8962-342b60020d60@sirjofri.de>

i always put a mkfile in my 9fat partitions which copies the kernel and mbr (if relevant) onto the 9fat partition. i also copy my venti and fossil configs into /cfg as backups. 

not that it is hard, more to ensure i don't miss a step as i dont do it often.

-Steve


> On 11 Apr 2022, at 7:43 pm, sirjofri <sirjofri+ml-9front@sirjofri.de> wrote:
> 
> 
> 11.04.2022 20:19:46 Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>:
>> Even that procedure does not re-install them into the 9fat partition.
>> Is there a ready-made script or mkfile target for that?
> 
> This procedure is not intended to install the files to 9fat. It's meant for proper tftp/network booting and stuff like that. Whatever you need to run the binaries is up to you and depends on your environment. Installing them to /$objtype/ is the best the system can do for you and intended behavior.
> 
> /sys/src/9/mkfile contains the procedures to create all binaries for all platforms currently supported. At least, as far as I can see. I usually just install pc64 (and my own wip port to pinephone) from their directories manually. Again, install only to /$objtype/, and install to 9fat or sdcard manually.
> 
> sirjofri

  reply	other threads:[~2022-04-11 19:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11 18:19 Benjamin Riefenstahl
2022-04-11 18:42 ` sirjofri
2022-04-11 19:47   ` Steve Simon [this message]
2022-04-20 15:41   ` Benjamin Riefenstahl

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=BF744723-3EAE-46A7-8490-5E915E8F1AA1@quintile.net \
    --to=steve@quintile.net \
    --cc=9front@9front.org \
    --subject='Re: [9front] Update system: Boot files not updated' \
    /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

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).