Difference between revisions of "Talk:Archiso"

From ArchWiki
Jump to: navigation, search
(Archiso doesn't work on non stock kernel)
(9 intermediate revisions by 4 users not shown)
Line 1: Line 1:
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)
==Edit removing mkarchroot references==
I might be misunderstanding the article, but it seems that the edit made on 19th March 2012 was incomplete.
The reasons for the revision was "update according to recent archiso changes (mkarchroot from devtools not used anymore)", so all references to mkarchroot were removed from the section "'''Building a custom Arch Linux live media. (configs/releng)'''", however the end of this section refers readers directly to the section "'''Configure our live medium'''".
In this section it is assumed that you have created a chroot and are working within it.
My concern is that there is no explanation of how to create this chroot in the article, and no indication if the first section is followed that one should have created one.
Please correct me if I have someone misunderstood or misread this article, thanks.
kYd (03/April/2012; 18:33)
Can we get some clarification on this please. Removing the mkarchroot section has rendered the article useless as it seems a pretty vital step.
I used mkarchroot just yesterday and made an iso fine, so it seems to still be applicable.
:: There is no need to use mkarchroot anymore because chroot things are now part of mkarchiso. You can work safe on your system directly, because mkarchiso/build.sh does not use anymore things from "host system". This chroot was needed only if your system differs to much from "standard Arch" or if you want to build an i686-iso on x86_64 host. Another example, long time ago I changed the execution of mkinitcpio from "host system" (using -B BASEDIR) to mkarchiso/mkarchroot (root-image)
:: Now this is managed directly by mkarchiso with run command and also you can directly build an i686-iso on x86_64 host. See for example, the new build mode "all" in releng/build.sh.
:: Maybe in the article should clarify about that when say "chroot" is refering to chroot on "$work_dir/root-image" made by mkarchiso.
:: In other words this what you made previously:
:: mkarchroot (optional but recommended) -> build.sh -> mkarchiso -> mkarchroot [root-image]
:: Now:
:: build.sh -> mkarchiso [root-image]
:: Of course, you can still work on a chroot made by mkarchroot, but you will have issues with pacman signed packages.
:: [[User:Djgera|Djgera]] 15:02, 3 April 2012 (EDT)
==Archiso doesn't work on non stock kernel==
==Archiso doesn't work on non stock kernel==
Line 43: Line 6:
On that note, is it possible to use a kernel other than the stock one within the ISOs we build?   
On that note, is it possible to use a kernel other than the stock one within the ISOs we build?   
[[User:Biltong|Biltong]] ([[User talk:Biltong|talk]]) Sun May 6 2012, 21:47 SAST
==Permission issues==
I have another issue: I have X installed with mate as my DE which works fine, but console kit does not work at all. This means I have no power nor network management from within mate, which is quite annoying. I've found that almost all of my directories on root / have 777 permissions, except for /dev, /proc, /run and /sys. I gather this is because the ISO is built with root privileges (the script asks for it) but this is a problem for me and I have no idea how to fix it.
The exact error I'm getting is "The permission of the setuid helper is not correct".
Is there anything I can do to fix this?
[[User:Biltong|Biltong]] ([[User talk:Biltong|talk]]) Sun May 6 2012, 21:47 SAST
[[User:Biltong|Biltong]] ([[User talk:Biltong|talk]]) Sun May 6 2012, 21:47 SAST

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