I'm trying to build an amd64 netboot2 image using catalyst-2.0.4. pre-kmerge.sh is trying to create files in /usr/share/genkernel/${clst_hostarch}; for subarch amd64, that directory does not exist, thus the pre-kmerge.sh script fails. /usr/share/genkernel/x86_64, on the other hand, *does* exist. This was reported on the gentoo-catalyst mailing list; a bug report was requested. Reproducible: Always Steps to Reproduce:
Created attachment 121523 [details, diff] Proposed fix
Well, it looks good, but my python stinks. No offense to you (it is my own lack of python skills) but I'm going to need a second opinion from my local python whipping boy. Andrew, does this look like it resolves the issue at hand?
There's no need to CC me on catalyst/genkernel stuff. I'm on the aliases now. This patch should work fine as long as there isn't any catalyst arch that can have multiple kernel arches. However, catalyst would have previously barfed in that case with this code as well. Do we have any arches like that? At first glance, it looks like we might have this problem with ppc (powerpc, ppc), sh (sh, sh64), and arm (arm, arm26). This just means we need to extend the patch a bit to allow an arch module to define a set of mappings instead of just a single one.
OK. Does anyone want to work on the extended patch in the next couple weeks? I am planning on rolling catalyst 2.0.5 somewhere around that time frame and there won't be another catalyst release until 2.1, which hasn't even been started yet.
Well, this hack won't be necessary in the 2.1 branch, since a lot of the netboot kernel/initramfs generation logic will move to genkernel where it belongs instead of this weird crap with catalyst screwing around in /usr/share/genkernel before calling genkernel. IMO, it's a waste of time to do the extended patch now when it won't even be needed in the next release. I'd also rather not include the attached patch, since it only solves the problem for amd64, although, I don't think anyone is using catalyst's netboot support on any of the other affected arches. It's up to you if you want to include the above patch, although, I bet the reporter is the only person trying to generate amd64 netboot images right now, so he can just as easily patch 2.0.5 locally.
*** Bug 209379 has been marked as a duplicate of this bug. ***
hi there. the same stuff happens with HPPA. I'm trying to build a netboot2 image and catalyst tries to create files in /usr/share/genkernel/hppa which doesn't exist (genkernel has parisc and parisc64). Re comment #3, if I understood it correctly, it also affects hppa. There are some hppa machines that can only boot 32bit (hppa-1.1, parisc) kernels, others that can only boot 64bit (hppa-2.0, parisc64) kernels, and others that can boot both. But as far as I know (didn't check it, yet) we can only put one kernel at a time in a lifimage (that's what we use to netboot on hppa) so if your problem concerns netboot images with more than one kernel we are already out of that. We'll have to build two different netboot images with the two different kernels (userland doesn't change).
This issue will be fixed when I move the majority of the netboot code to genkernel. Just be patient.
I've just removed all the ugly netboot hacks from catalyst and added proper code for it into genkernel. This is in git for both.
This was released long ago.
