[opensuse-factory] How to modify .iso snapshots and make the result bootable?
Hi. I'd like to modify one of the packages of .iso snapshots in order to test one package. There is a bug related with that package, so it cannot be submitted to Factoy and if it's not submitted I can't test a change I've made. It's not possible to install the package after the OS is installed because the bug is exposed only in the first boot after the installation. So I think that by replacing the offending package directly in the snapshot .iso I can make my tests. When I look at the content of the image with Dolphin there are three folders: El Torito Boot El Torito BootJoliet level 3 ISO9660 I don't know how to make a bootable media from that. Any help is welcome. If the change works I think that we could get rid of ConsoleKit too because as far as I know this is the only package using it. Thanks in advance. Greetings. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wednesday 2015-05-20 11:23, jcsl wrote:
It's not possible to install the package after the OS is installed because the bug is exposed only in the first boot after the installation. So I think that by replacing the offending package directly in the snapshot .iso I can make my tests.
You could just change your system so that the package thinks it is a first boot. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El Miércoles, 20 de mayo de 2015 11:32:18 Jan Engelhardt escribió:
On Wednesday 2015-05-20 11:23, jcsl wrote:
It's not possible to install the package after the OS is installed because the bug is exposed only in the first boot after the installation. So I think that by replacing the offending package directly in the snapshot .iso I can make my tests.
You could just change your system so that the package thinks it is a first boot.
Hi. I don't think that's gonna work. Right after the first boot (you have to reboot because desktop doesn't start in the very first boot after the installation finishes) something happens and from then on it boots perfectly. Even if I trick the system to make it think it's the first boot, the changes will be already done. Greetings. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
jcsl wrote:
El Miércoles, 20 de mayo de 2015 11:32:18 Jan Engelhardt escribió:
On Wednesday 2015-05-20 11:23, jcsl wrote:
It's not possible to install the package after the OS is installed because the bug is exposed only in the first boot after the installation. So I think that by replacing the offending package directly in the snapshot .iso I can make my tests.
You could just change your system so that the package thinks it is a first boot.
I don't think that's gonna work. Right after the first boot (you have to reboot because desktop doesn't start in the very first boot after the installation finishes) something happens and from then on it boots perfectly. Even if I trick the system to make it think it's the first boot, the changes will be already done.
Maybe a driver update disk can help you there: https://github.com/openSUSE/mkdud cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El Miércoles, 20 de mayo de 2015 12:00:49 Ludwig Nussel escribió:
jcsl wrote:
El Miércoles, 20 de mayo de 2015 11:32:18 Jan Engelhardt escribió:
On Wednesday 2015-05-20 11:23, jcsl wrote:
It's not possible to install the package after the OS is installed because the bug is exposed only in the first boot after the installation. So I think that by replacing the offending package directly in the snapshot .iso I can make my tests.
You could just change your system so that the package thinks it is a first boot.
I don't think that's gonna work. Right after the first boot (you have to reboot because desktop doesn't start in the very first boot after the installation finishes) something happens and from then on it boots perfectly. Even if I trick the system to make it think it's the first boot, the changes will be already done.
Maybe a driver update disk can help you there: https://github.com/openSUSE/mkdud
Hi, I agree that is the way to go. You can find more information about using the DUD at linuxrc[1] documentation. On the other hand, you could take a look at this code[2] from AutoYaST Integration Tests where the DUD is included in the ISO. It's Ruby code but it's not that hard to understand. Regards, Imobach [1] https://en.opensuse.org/SDB:Linuxrc#p_dud [2] https://github.com/yast/autoyast-integration-test/blob/master/build_iso/sles... -- Imobach González Sosa YaST Team at SUSE LINUX GmbH
On 2015-05-20 11:23, jcsl wrote:
When I look at the content of the image with Dolphin there are three folders:
El Torito Boot El Torito BootJoliet level 3 ISO9660
I don't know how to make a bootable media from that.
Guessing. You have to extract the three components. Then expand the ISO9660 section, do the modification there, and make the iso again (mkisofs), giving it the el torito images for booting. However, that there are two el torito components confuses me. If you can find out exactly how the original image is built... I have not seen a description anywhere. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Wed, 20 May 2015, Carlos E. R. wrote:
On 2015-05-20 11:23, jcsl wrote:
When I look at the content of the image with Dolphin there are three folders:
El Torito Boot El Torito BootJoliet level 3 ISO9660
I don't know how to make a bootable media from that.
Guessing.
You have to extract the three components. Then expand the ISO9660 section, do the modification there, and make the iso again (mkisofs), giving it the el torito images for booting.
However, that there are two el torito components confuses me.
If you can find out exactly how the original image is built... I have not seen a description anywhere.
There is mksusecd on software.opensuse.org that lets you rebuild the iso with small modifications. Steffen -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (6)
-
Carlos E. R. -
Imobach González Sosa -
Jan Engelhardt -
jcsl -
Ludwig Nussel -
Steffen Winterfeldt