2.4, page 28: As suggested by the arguments, the scenario is supplied to Qemu as an ISO image re- siding at var/run/demo.iso. The ISO image can not only be used with Qemu but also with a real machine. For example, creating a bootable USB stick with the system scenario is as simple as writing the ISO image onto a USB stick: sudo dd if=var/run/demo.iso of=/dev/ bs=8M conv=fsync
I am pretty sure it will not work... iso are for DVD, not USB sticks.
Guess build.conf need to be edited a bit to make it easier to select a .img by just choosing between two comments lines.
Re-bonjour :-)
sudo dd if=var/run/demo.iso of=/dev/ bs=8M conv=fsync
I am pretty sure it will not work... iso are for DVD, not USB sticks.
Well I guess "ISO" should be taken in a generic sense. I, like other Genodians, have been writing "iso" files to USB thumbdrives for years (Genode, Haiku, and others projects do release "iso" images all the time). The key is that the .iso file should be a hybrid (sp?), that is to say, generated with special parameters passed to xorriso or other tools, so as to integrate not only iso9660 machinery but also a GPT or MBR layout so that it can be written equally well to an HDD or USB stick and work correctly.
You can convince yourself of that by downloading a pre-built Sculpt OS iso image and test it... On bare metal or in VirtualBox. It should boot up equally well (or not) as other bootable USB sticks.
Beside .iso's there is also another way to generate .raw or .img files that do *not* have iso9660 compatbility IIRC, so that should work too.
Cédric
---- Le mar., 03 déc. 2024 09:14:03 -0500 Cedric At TTS via users a écrit ----
Re-bonjour :-)
sudo dd if=var/run/demo.iso of=/dev/ bs=8M conv=fsync
When I copied, the <usb-device> part was removed, recopying it now: sudo dd if=var/run/demo.iso of=/dev/<usb-device, likely sdb> bs=8M conv=fsync
I am pretty sure it will not work... iso are for DVD, not USB sticks.
Well I guess "ISO" should be taken in a generic sense. I, like other Genodians, have been writing "iso" files to USB thumbdrives for years (Genode, Haiku, and others projects do release "iso" images all the time). The key is that the .iso file should be a hybrid (sp?), that is to say, generated with special parameters passed to xorriso or other tools, so as to integrate not only iso9660 machinery but also a GPT or MBR layout so that it can be written equally well to an HDD or USB stick and work correctly.
You can convince yourself of that by downloading a pre-built Sculpt OS iso image and test it... On bare metal or in VirtualBox. It should boot up equally well (or not) as other bootable USB sticks.
https://genode.org/download/sculpt seems to have only .img files... and it is in part what convince me that it needs to be an .img file to write on an USB stick.
Beside .iso's there is also another way to generate .raw or .img files that do *not* have iso9660 compatbility IIRC, so that should work too.
You need to change QEMU_RUN_OPT in build/x86_64/etc/build.conf to image/disk instead of image/iso... like Yvan Loskutov said in a previous email. [worked, but then would break the QEMU run I guess... maybe we could boot qemu from a virtual USB stick and have it work in "all" the cases?]
Cédric
I have tried to dd the demo.iso file on my stick USB. At first, I thought I was proving me right because it did not boot. But then I realized I was trying to boot only in UEFI USB mode. So I tried LEGACY USB, and found that it does indeed boot that way.
---- Le mar., 03 déc. 2024 10:43:18 -0500 Paul Dufresne via users a écrit ---- I felt a bit wrong about suggesting to use sdb in a dd command. I know people here are likely to know that they are risking to erase their hard disk by mistake doing this...
At first I wanted to suggest to use: https://docs.fedoraproject.org/en-US/fedora/latest/preparing-boot-media/ but because for Mac and Windows that seems to be a non-clear download....
Guess I am suggesting to use: https://etcher.balena.io/#download-etcher even if at some time I remember some integrated possibly unwanted software was included...
Sure, seems better to suggest than using dd for less advanced users, as it protect agains wrongly erasing hard disks.
Ok, so I was wrong... writing the .iso file on a USB key will work if booted in MBR mode (legacy) rather than UEFI.
Still as I see it, we have the choice between what we do now: -make an .iso that boot on MBR only when written to an USB stick -works as an emulated "CDROM" on QEMU -works on a real CDROM/DVD drive
or to make as default a .img file that: -that boot on an USB stick in MBR or UEFI -would works as an emulated USB stick on QEMU (admittedly, I would have to try that) -would need an over step to make as a .iso for a real CDROM/DVD drive
My argument is that because computers tend to often not have DVD drive anymore, and some computers begin to boot only in UEFI mode, it would be better to produce by default a .img file.