|(43 intermediate revisions by 10 users not shown)|
|−|Hi thar! If you guys have any questions or trouble when following this guide, please do post it here, I will come back to you! |+|
| || |
[[User:Svenstaro|Svenstaro]] 19:14, 3 June 2009 (EDT) |+|
| || |
|−|== Confussion with some aspects. == |+|
| || |
|−|I'm a little confussed as to some of the explanations on the wiki page. |+|
, to the one we ?
|−|When editing the mkinitcpio.conf, do we need to do this inside the chroot, or create a seperate one ? If so where do we put this? ( As I'm sure was the case with the previous version of archiso), and the same with packages.list. |+|
() , :
|−|Thank you. | |
|−|kYd - Aug 23 (00: 44 BST) | |
Revision as of 15:24, 27 February 2013
Archiso doesn't work on non stock kernel
I've been having on and off issues when building ISOs with archiso and the other day when I was working on one I did a pacman -Syu before working but didn't reboot. I was running on the stock kernel at that point because the linux-ck kernel had not updated yet. My ISO built fine. Later that day I rebooted and was now running on the updated linux-ck kernel and suddenly the build process would simply die without any errors, even with the -v option. Right after installing all the custom packages, a dd output appears and then a mkfs.vfat version message appears and that's where it dies. Rebooting back to the stock arch kernel fixed the issue. I'm guessing it has something to do with hardcoded names or something like that in the build scripts.
Is this normal behaviour? I don't mind using the stock kernel on the ISOs I build but I figured I'd at least be able to build them on a different one.
On that note, is it possible to use a kernel other than the stock one within the ISOs we build?
Biltong (talk) Sun May 6 2012, 21:47 SAST