jaeger changed the topic of #crux-arm to: CRUX-ARM 3.6 Released! - http://crux-arm.nu/Documentation/ReleaseNotes3-6 | Logs: https://libera.irclog.whitequark.org/crux-arm/
guido_rokepo has joined #crux-arm
frinnst has quit [Ping timeout: 240 seconds]
frinnst has joined #crux-arm
guido_rokepo has quit [Quit: guido_rokepo]
<r0ni> is there a kernel config for booting this on vmware or qemu or does such a config exist?
<beerman> no idea if that works, but maybe something like that might help as a starting point: https://github.com/projg2/fedora-kernel-config-for-gentoo/blob/26/kernel-aarch64.config
<r0ni> I've been trying to pinpoint exactly what is needed to get them booting correctly, without luck
<r0ni> ill check out that link
<beerman> good luck
<r0ni> basically i can boot debian and fedora, but slackware for instance, no dice. comparing kernel configs only goes so far... its way too monolith these days to compare the configs and see what is needed, as each distro is almost completely different with supported things
<r0ni> i'm about to setup crux with debian kernel on a vmware vm tho for shits and giggles
<r0ni> ahh the dreaded e2fsck error
<r0ni> yay got it to boot
<r0ni> triple boot vm: debian, slackware, crux
<r0ni> updated all the ports, yet 'ports -d' shows me things are out-of-sync with the x86 version, so i picked dbus, built the port, but doing a 'pkgadd -u <dbus filename> does nothing
<r0ni> i assume the sig checking knows its from the opt repo and not the core-arm64 repo... a way to force it?
<r0ni> ahh i see -f ;)
<r0ni> still does nothing, ah well
<jaeger> If you're just running in vmware or qemu you can probably use the generic rootfs and a generic kernel config
<jaeger> And yeah, signatures are per-repo
<r0ni> ya i installed the 3.7rc5 rootfs, but there don't seem to be a kernel,config or source included so I assume the arm port is a BYOK situation as of now