Another problem I encountered with "mk all; mk install" was that the boot files were not re-created, the kernel, bootsectors and similar: --rw-rw-r-- M 24 sys sys 7960 Jul 18 2021 /386/9bootfat --rw-rw-r-- M 24 sys sys 6472 Jul 18 2021 /386/9boothyb --rw-rw-r-- M 24 sys sys 6496 Jul 18 2021 /386/9bootiso --rw-rw-r-- M 24 sys sys 8004 Jul 18 2021 /386/9bootpxe --rw-rw-r-- M 24 sys sys 11108 Jul 18 2021 /386/bootia32.efi --rw-rw-r-- M 24 sys sys 12356 Jul 18 2021 /386/bootx64.efi --rw-rw-r-- M 24 sys sys 1048576 Jul 18 2021 /386/efiboot.fat --rw-rw-r-- M 24 sys sys 407 Jul 18 2021 /386/mbr --rw-rw-r-- M 24 sys sys 473 Jul 18 2021 /386/pbs --rwxrwxr-x M 24 sys sys 5229573 Jul 18 2021 /amd64/9pc64 Is this expected? To get these compiled and installed, I now do something like: for (d in 9/pc64 boot/efi boot/pc) @{ cd $d mk install } Even that procedure does not re-install them into the 9fat partition. Is there a ready-made script or mkfile target for that? Thanks, benny
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
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
> 11.04.2022 20:19:46 Benjamin Riefenstahl: >> Even that procedure does not re-install them into the 9fat partition. >> Is there a ready-made script or mkfile target for that? sirjofri <sirjofri+ writes: > install only to /$objtype/, and install to 9fat or sdcard manually. Ok. >> Another problem I encountered with "mk all; mk install" was that the >> boot files were not re-created, the kernel, bootsectors and similar: Is there any good reason for this issue though? Or is this just an oversight? "mk all" in "/sys/src" does not go into the directories for kernel and mbr, nor does "mk install" put them into /amd64 and /386 Thanks, benny