Re: [arch-general] [arch-dev-public] [signoff] mkinitcpio 0.5.28-1
On 12/01/2010 11:03 πμ, Thomas Bächler wrote:
I think what we have now in the kill-klibc branch might actually boot in a standard setup (no raid, nfs, lvm, encryption), but I didn't try. I'll keep you posted.
I gave it a try in a VM but it still fails with "Failed to execute /init" like last time (http://i.imgur.com/h6xDu.png). The mkinicpio revision I tried was 54fd032, along with latest mkinitcpio-busybox/trunk. The command used to generate the initramfs image was `./mkinitcpio -g /boot/kernel26.img' from within the cloned Git repository (switched to the kill-klibc branch). Let me know if I can help with further testing.
Am 12.01.2010 15:07, schrieb Evangelos Foutras:
On 12/01/2010 11:03 πμ, Thomas Bächler wrote:
I think what we have now in the kill-klibc branch might actually boot in a standard setup (no raid, nfs, lvm, encryption), but I didn't try. I'll keep you posted.
I gave it a try in a VM but it still fails with "Failed to execute /init" like last time (http://i.imgur.com/h6xDu.png).
The mkinicpio revision I tried was 54fd032, along with latest mkinitcpio-busybox/trunk. The command used to generate the initramfs image was `./mkinitcpio -g /boot/kernel26.img' from within the cloned Git repository (switched to the kill-klibc branch).
Let me know if I can help with further testing.
Okay, that is weird, I guess I will have to try myself this week, when I get to it.
Am 12.01.2010 15:07, schrieb Evangelos Foutras:
On 12/01/2010 11:03 πμ, Thomas Bächler wrote:
I think what we have now in the kill-klibc branch might actually boot in a standard setup (no raid, nfs, lvm, encryption), but I didn't try. I'll keep you posted.
I gave it a try in a VM but it still fails with "Failed to execute /init" like last time (http://i.imgur.com/h6xDu.png).
The mkinicpio revision I tried was 54fd032, along with latest mkinitcpio-busybox/trunk. The command used to generate the initramfs image was `./mkinitcpio -g /boot/kernel26.img' from within the cloned Git repository (switched to the kill-klibc branch).
Let me know if I can help with further testing.
I tried in VirtualBox on Arch i686 and it worked fine here (meaning I didn't have that particular problem). It then paniced due to problems in /init. Rev 93a8be170ff841dd345084b5f5eda66c76e6534f boots fine here on VirtualBox. I don't know why you get "Failed to execute /init". However, I installed mkinitcpio into the system and didn't try to use it from the git directly. We can check that problem later though.
On Tue, Jan 12, 2010 at 10:43 PM, Thomas Bächler <thomas@archlinux.org> wrote:
Am 12.01.2010 15:07, schrieb Evangelos Foutras:
I gave it a try in a VM but it still fails with "Failed to execute /init" like last time (http://i.imgur.com/h6xDu.png).
The mkinicpio revision I tried was 54fd032, along with latest mkinitcpio-busybox/trunk. The command used to generate the initramfs image was `./mkinitcpio -g /boot/kernel26.img' from within the cloned Git repository (switched to the kill-klibc branch).
Let me know if I can help with further testing.
I tried in VirtualBox on Arch i686 and it worked fine here (meaning I didn't have that particular problem).
It then paniced due to problems in /init. Rev 93a8be170ff841dd345084b5f5eda66c76e6534f boots fine here on VirtualBox.
I don't know why you get "Failed to execute /init". However, I installed mkinitcpio into the system and didn't try to use it from the git directly. We can check that problem later though.
That is great news. Nice work! :)
Am 12.01.2010 22:24, schrieb Evangelos Foutras:
I tried in VirtualBox on Arch i686 and it worked fine here (meaning I didn't have that particular problem).
It then paniced due to problems in /init. Rev 93a8be170ff841dd345084b5f5eda66c76e6534f boots fine here on VirtualBox.
I don't know why you get "Failed to execute /init". However, I installed mkinitcpio into the system and didn't try to use it from the git directly. We can check that problem later though.
That is great news. Nice work! :)
Now we also have a keymap hook. LVM, encryption, RAID and NFS are still TODO, while I will only do the first two, I hope tpowa will handle RAID and I think there's some shell code on the bugtracker to replace kinit's NFS handling.
participants (2)
-
Evangelos Foutras
-
Thomas Bächler