I have update on my issue. Only way to make custom iso of fedora because i am using it would be using mock and pungi and doing it same way fedora developers do when they're building testing images prior to release or set it up and use clonzilla to make recovery usb so i can recover it all. Mock and pungi seem to make system based on installation of fedora. I will play around with mock and pungi and see what happens. This seems viable because you don't need to make kickstart file.
You jumped from the kickstart file to "Now finally we need to package the image up". How did you unpackage it? When did you run all those other commands? I'm using Fedora but when I mount my iso there is no isolinux directory. I'm looked in the netinstall iso, full workstation iso, full server iso. It's in my debian iso but I'm trying to do this with Fedora now. Is there some other file I need to download from somewhere?
Hi Rob. I've never tried it with a Fedora image. The one I mount in this video is a RedHat Enterprise Linux drive. And as it's connected to their cloud, I guess they have made it hard/impossible to do with other distributions. The isolinux.bin file is pretty much the boot drive, so perhaps there is something similar in a Fedora image. Maybe it has a different name, or the file structure is completely different. Have not planned to do any videos in the RedHat community because they are a bit hostile at the moment, and we don't really know the fallout yet. But if the distribution survives, I might look into an automatic Fedora install in the future, currently my next objective is an automated Ubuntu server install as that is something I do more frequently. I hope this helps. Thank you for watching my videos. Best regards Daniel
EL Torito, actually... It is the name of restaurant, where guys from IBM and Phoenix (those who created the bootable ISO specification) used to meet...
No matter where i look it always truns out that if i want to make kickstart file i have to make by hand because nobody bothered to make simple tool to scan existing instalation of for me fedora and generate kickstart file based on that or some tool to make it easier as if nobody gives a damn about it. All i can do when i'm done is back up configuration files somwhere where i can get them if i have to reinstall fedora. if there is helpfull tool for kickstart files please tell me because i don't know where to look.
Thanks for this tutorial will have to try this out, especially your genisoimage command! I am jumping directly from RHEL 7 to RHEL 9 and some of the ISO commands I used seem to be slightly different. When I last tried recompiling with all RHEL 9 content with just some very minor tweaks, ISO would boot up virtually (VMware Workstation Pro) at the splashscreen but weirdly couldn't select anything on the initial boot screen. I wasn't even at the point of doing a customized embedded kickstart reference in the isolinux.cfg, but rather just customizing some splashscreen titles and backgrounds so thought that was weird, when my usual RHEL 7 geniso commands have been working consistently. Will have to try again though maybe there are some specific rpms/dependencies that are affecting it, no idea at this point but previously it seemed all my isolinux cfgs and specific parameters seemed to be correct. I'll definitely follow what you have specified in your genisoimage command though so thanks!
tried this method , still .cfg file is not working . kickstart not started using the answer file . do we need to update the cfg file anywhere to tell Kickstart to use the .cfg file ? FYI I tried to use this for Alma9 Kickstart
Hi Eswaran I think Kickstart is connected to Redhat for some of their operations. Maybe the Alma9 system aren't supported by the Redhat corporation. I have never tried so I can't really help. I'm sorry, thank you for watching my videos. Best regards Daniel
Hi Daniel, great vid - thank you. I would however would like to know how you overcame including the ks in your image to automatically run and not having to specify it at the boot menu and the new requirement to have the ISO written in dd mode, say from a rufus point of view. I have added the ks to the grub conf, written the iso created in the tutorial to flash drive using dd but then get error started cancel waiting for multipath siblings of sda, even if the ks is set to use the boot label as suggested on the Rocky group inst.ks=hd:LABEL=Rocky-8-7-x86_64 :/isolinux/my-ks.cfg - of course the LABEL is set differently. If the image is written in iso mode, the local installation source for packages are not seen and gives Error setting up base repository
Hi. To my knowledge, nothing. I probably only looked at the file to see if there was something I needed to mention about it. The default values should suffice. Thank you for watching my videos. Best regards Daniel
This is great. I need to use kickstart files more.
I have update on my issue. Only way to make custom iso of fedora because i am using it would be using mock and pungi and doing it same way fedora developers do when they're building testing images prior to release or set it up and use clonzilla to make recovery usb so i can recover it all. Mock and pungi seem to make system based on installation of fedora. I will play around with mock and pungi and see what happens. This seems viable because you don't need to make kickstart file.
Very useful, thank you!!
You jumped from the kickstart file to "Now finally we need to package the image up". How did you unpackage it? When did you run all those other commands? I'm using Fedora but when I mount my iso there is no isolinux directory. I'm looked in the netinstall iso, full workstation iso, full server iso. It's in my debian iso but I'm trying to do this with Fedora now. Is there some other file I need to download from somewhere?
Hi Rob.
I've never tried it with a Fedora image. The one I mount in this video is a RedHat Enterprise Linux drive. And as it's connected to their cloud, I guess they have made it hard/impossible to do with other distributions.
The isolinux.bin file is pretty much the boot drive, so perhaps there is something similar in a Fedora image. Maybe it has a different name, or the file structure is completely different.
Have not planned to do any videos in the RedHat community because they are a bit hostile at the moment, and we don't really know the fallout yet. But if the distribution survives, I might look into an automatic Fedora install in the future, currently my next objective is an automated Ubuntu server install as that is something I do more frequently.
I hope this helps. Thank you for watching my videos.
Best regards
Daniel
EL Torito, actually... It is the name of restaurant, where guys from IBM and Phoenix (those who created the bootable ISO specification) used to meet...
Yup, El Torito, a restaurant, Also translates to the "little bull".
No matter where i look it always truns out that if i want to make kickstart file i have to make by hand because nobody bothered to make simple tool to scan existing instalation of for me fedora and generate kickstart file based on that or some tool to make it easier as if nobody gives a damn about it. All i can do when i'm done is back up configuration files somwhere where i can get them if i have to reinstall fedora. if there is helpfull tool for kickstart files please tell me because i don't know where to look.
Thanks for this tutorial will have to try this out, especially your genisoimage command! I am jumping directly from RHEL 7 to RHEL 9 and some of the ISO commands I used seem to be slightly different. When I last tried recompiling with all RHEL 9 content with just some very minor tweaks, ISO would boot up virtually (VMware Workstation Pro) at the splashscreen but weirdly couldn't select anything on the initial boot screen. I wasn't even at the point of doing a customized embedded kickstart reference in the isolinux.cfg, but rather just customizing some splashscreen titles and backgrounds so thought that was weird, when my usual RHEL 7 geniso commands have been working consistently. Will have to try again though maybe there are some specific rpms/dependencies that are affecting it, no idea at this point but previously it seemed all my isolinux cfgs and specific parameters seemed to be correct. I'll definitely follow what you have specified in your genisoimage command though so thanks!
tried this method , still .cfg file is not working . kickstart not started using the answer file . do we need to update the cfg file anywhere to tell Kickstart to use the .cfg file ? FYI I tried to use this for Alma9 Kickstart
Hi Eswaran
I think Kickstart is connected to Redhat for some of their operations. Maybe the Alma9 system aren't supported by the Redhat corporation. I have never tried so I can't really help.
I'm sorry, thank you for watching my videos.
Best regards
Daniel
Hi Daniel, great vid - thank you. I would however would like to know how you overcame including the ks in your image to automatically run and not having to specify it at the boot menu and the new requirement to have the ISO written in dd mode, say from a rufus point of view. I have added the ks to the grub conf, written the iso created in the tutorial to flash drive using dd but then get error started cancel waiting for multipath siblings of sda, even if the ks is set to use the boot label as suggested on the Rocky group inst.ks=hd:LABEL=Rocky-8-7-x86_64 :/isolinux/my-ks.cfg - of course the LABEL is set differently.
If the image is written in iso mode, the local installation source for packages are not seen and gives Error setting up base repository
Hi Jan Kosie
Sorry, but I don't really understand the question. If it requires a lot of explanation you could send me an email.
Best regards
Daniel
What did you do with isolinux/isolinux.cfg ?
Hi.
To my knowledge, nothing. I probably only looked at the file to see if there was something I needed to mention about it. The default values should suffice.
Thank you for watching my videos.
Best regards
Daniel
@@DanielPersson Thank you old Swede.