El mar, 16-05-2023 a las 14:40 +0300, nl6720 escribió:
>
> The airootfs image location is hardcoded to
> "/${archisobasedir}/${arch}/", so
> you you need to place airootfs.sfs in a "x86_64" subdirectory.
> Then setting archisobasedir and archisodevice should be enough.
>
This is how the boot wor
On otrdiena, 2023. gada 16. maijs 10:13:51 EEST Óscar García Amor wrote:
> Hello folks,
>
> I am doing a little crazy, I would like to boot the content of Archiso
> but with the extracted files not the ISO image itself.
>
> It is clear to me that to boot I need:
> - amd-ucode.img
> - intel-ucode.
On 16-05-2023 13:09, Óscar García Amor wrote:
El mar, 16-05-2023 a las 09:22 +0200, Uwe Sauter escribió:
Boot the ISO, check /proc/cmdline for the options passed to the
kernel.
That option is not valid as the kernel parameters passed are dependent
on booting from the ISO. The values are:
ar
El mar, 16-05-2023 a las 09:22 +0200, Uwe Sauter escribió:
> Boot the ISO, check /proc/cmdline for the options passed to the
> kernel.
>
That option is not valid as the kernel parameters passed are dependent
on booting from the ISO. The values are:
archisobasedir=arch archisodevice=UUID=2023-05-
Boot the ISO, check /proc/cmdline for the options passed to the kernel.
Am 16.05.23 um 09:13 schrieb Óscar García Amor:
> Hello folks,
>
> I am doing a little crazy, I would like to boot the content of Archiso
> but with the extracted files not the ISO image itself.
>
> It is clear to me that
Hello folks,
I am doing a little crazy, I would like to boot the content of Archiso
but with the extracted files not the ISO image itself.
It is clear to me that to boot I need:
- amd-ucode.img
- intel-ucode.img
- initramfs-linux.img
- vmlinuz-linux
- airootfs.sfs
And that the linux and initrd l
