kexec-loader rewrite
#1
Posted 05 February 2009 - 03:44 PM
If you press enter in the shell with an empty line it crashes (irony!), this will be fixed in the next image.
rewrite-r478.img.gz
If you need extra modules, the v1.6.2 modules are compatible, any comments?
#2
Posted 05 February 2009 - 03:48 PM
http://www.boot-land...?showtopic=4636
and here:
http://www.boot-land...?showtopic=6709
etc., etc.
jaclaz
#3
Posted 05 February 2009 - 04:05 PM
did you receive my e-mail about the iso version?
#4
Posted 05 February 2009 - 04:13 PM
solemnwarning,
did you receive my e-mail about the iso version?
Yeah, I forgot to respond. I'm not planning on supporting ISOs anytime soon, since them being read-only would make configuring it more tedious, you can fit any sane combination of modules on a floppy anyway.
I doubt I will ever support network booting, if you want to boot from a server, PXE is a better choice.
#6
Posted 08 February 2009 - 12:37 AM
This is from the orignal grub menu.cfg:
title Ubuntu 8.04.2, kernel 2.6.24-23-generic root (hd0,2) kernel /boot/vmlinuz-2.6.24-23-generic root=UUID=2bbadde7-2464-4276-ae55-a1c5079c3e12 ro quiet splash initrd /boot/initrd.img-2.6.24-23-generic quiet
Here is my device list: http://img25.imagesh...08012114og7.png
I've tested so many combinations....
# i did set label ubuntu after the screenshot has been made, it's detected title Ubuntu 8.04.2, kernel 2.6.24-23-generic - root LABEL root LABEL=ubuntu kernel /boot/vmlinuz-2.6.24-23-generic root=UUID=2bbadde7-2464-4276-ae55-a1c5079c3e12 ro quiet splash initrd /boot/initrd.img-2.6.24-23-generic title Ubuntu 8.04.2, kernel 2.6.24-23-generic - root uuid root UUID=2bbadde7-2464-4276-ae55-a1c5079c3e12 kernel /boot/vmlinuz-2.6.24-23-generic root=UUID=2bbadde7-2464-4276-ae55-a1c5079c3e12 ro quiet splash initrd /boot/initrd.img-2.6.24-23-generic title Ubuntu 8.04.2, kernel 2.6.24-23-generic - sda3 root /dev/sda3 kernel /boot/vmlinuz-2.6.24-23-generic root=UUID=2bbadde7-2464-4276-ae55-a1c5079c3e12 ro quiet splash initrd /boot/initrd.img-2.6.24-23-genericalso root (hd0,3), root (sda0,3), etc...
Test environment: VMware and a USB HDD.
I need some help with the configuration files or I must miss something else.
#7
Posted 08 February 2009 - 12:46 AM
[codebox]title Ubuntu 8.04.2, kernel 2.6.24-23-generic - root LABEL root LABEL=ubuntu kernel /boot/vmlinuz-2.6.24-23-generic initrd /boot/initrd.img-2.6.24-23-generic cmdline root=UUID=2bbadde7-2464-4276-ae55-a1c5079c3e12 ro quiet splash title Ubuntu 8.04.2, kernel 2.6.24-23-generic - root uuid root UUID=2bbadde7-2464-4276-ae55-a1c5079c3e12 kernel /boot/vmlinuz-2.6.24-23-generic initrd /boot/initrd.img-2.6.24-23-generic cmdline root=UUID=2bbadde7-2464-4276-ae55-a1c5079c3e12 ro quiet splash title Ubuntu 8.04.2, kernel 2.6.24-23-generic - sda3 root /dev/sda3 kernel /boot/vmlinuz-2.6.24-23-generic initrd /boot/initrd.img-2.6.24-23-generic cmdline root=UUID=2bbadde7-2464-4276-ae55-a1c5079c3e12 ro quiet splash[/codebox] If you read: [url="http://www.solemnwarning.net/notes.txt"]http://www.solemnwarning.net/notes.txt[/url] [code]cmdline <text> Set kernel command line[/code]
#8
Posted 08 February 2009 - 12:52 AM
#9
Posted 08 February 2009 - 01:21 AM
#10
Posted 08 February 2009 - 01:26 AM
- Error mounting LABEL=ubuntu: No such device (Missing module?)
- Error mounting UUIDL=.........: No such device (Missing module?)
- Error mounting /dev/sda3: No such device (Missing module?)
#11
Posted 08 February 2009 - 02:00 AM
As far as the error, have you added all required device/filesystem modules? The base kernel only supports USB, PC floppy and FAT
#12
Posted 08 February 2009 - 02:50 AM
However, I got now the UUID example and the /dev/sda3 example working. Just label is not working.
"prof" for label: http://img18.imagesh...08034434oi2.png
title Ubuntu 8.04.2, kernel 2.6.24-23-generic - root LABEL root LABEL=ubuntu kernel /boot/vmlinuz-2.6.24-23-generic initrd /boot/initrd.img-2.6.24-23-generic cmdline root=UUID=2bbadde7-2464-4276-ae55-a1c5079c3e12 ro quiet splash
It's not very important for me as Ubuntu likes to use uuid anyway, just wanted to report it. But if it's a serious problem I guess someone else might report it.
#13
Posted 08 February 2009 - 02:56 AM
#14
Posted 08 February 2009 - 03:14 AM
#15
Posted 08 February 2009 - 03:50 AM
I thought using grub4dos floppy emulation will not work because the kernel is not using BIOS to read the modules on the floppy disk?
So I did copy the structure of the floppy and made a new folder, additionally I did put all the modules into the modules subdirectory. I used isolinux and mkisofs to create the a bootable iso. It books ok, until...
Searching for bootdisk...
Press a key to abort
Well, I think I will not be able to create a booatble iso without learning the Linux boot process, without hacking and without compiling from source?
#16
Posted 08 February 2009 - 11:37 AM
Once you've done that, kexec-loader searches for a disk with the volume name 'kexecloader' to use as the boot disk
#17
Posted 08 February 2009 - 12:52 PM
If I may , won't it be a nice feature of kexec-loader to have a number of kernels, each with different "levels" (or filesystems understood) to choose among?You will need to compile a kernel with CD and ISO support, the modules are no use since you need to be able to mount the CD to load the modules
Once you've done that, kexec-loader searches for a disk with the volume name 'kexecloader' to use as the boot disk
I mean, most users of the board are not familiar enough with Linux to compile themselves a kernel, it is probable that they will either:
- try nonetheless and fail, then we will have requests for help/fixes and the like
- "abandon" kexec-loader, being it too complex to make it working
jaclaz
#18
Posted 08 February 2009 - 01:50 PM
#19
Posted 08 February 2009 - 03:20 PM
title Ubuntu 8.04.2, kernel 2.6.24-23-generic - root uuid root UUID=2bbadde7-2464-4276-ae55-a1c5079c3e12 kernel /boot/vmlinuz-2.6.24-23-generic initrd /boot/initrd.img-2.6.24-23-generic cmdline root=UUID=2bbadde7-2464-4276-ae55-a1c5079c3e12 ro quiet splash title Ubuntu 8.04.2, kernel 2.6.24-23-generic - root LABEL root LABEL=ubuntu kernel /boot/vmlinuz-2.6.24-23-generic initrd /boot/initrd.img-2.6.24-23-generic cmdline root=UUID=2bbadde7-2464-4276-ae55-a1c5079c3e12 ro quiet splash title Ubuntu 8.04.2, kernel 2.6.24-23-generic - sda3 root /dev/sda3 kernel /boot/vmlinuz-2.6.24-23-generic initrd /boot/initrd.img-2.6.24-23-generic cmdline root=UUID=2bbadde7-2464-4276-ae55-a1c5079c3e12 ro quiet splash
For a USB-HDD with Ubuntu (using /boot/grub) I am using
grub-path (sda3)/boot/grub
Error mounting GRUB device: Unknown device
When I type disks I first see only fd0, some seconds later I see fd0 and sda and even some seconds later I see fd0, sda, sda1, sda2 and so on (everything). I think the error mounting GRUB device error is because the kernel works nonblocking and asynchronous and needs a while until he recognized everything.
In console grub-device is not supported. What can I do to make it to work?
That would be great...I may build more kernels in the future, or possibly write a script to download/build Linux...
Well, maybe it's a question, who does support most devices? It's not a bootloader, it's the linux kernel itself.
In order to support as much as possible devices, why not make a generic kernel with full driver support?
I don't agree with PXE. PXE is extremely limited, mostly for intenral LAN cards. For things like booting from USB WLAN + WPA2 over SSL connection from remote server it's not working, fancy boot devices can be only booted with the full kernel.I doubt I will ever support network booting, if you want to boot from a server, PXE is a better choice.
#20
Posted 08 February 2009 - 03:54 PM
Because it would grow in size, that's why I suggested several different "levels", from the most basic to the most complete, in order to cover "all the range" of possible users, from minimalists to universalists.In order to support as much as possible devices, why not make a generic kernel with full driver support?
jaclaz
#21
Posted 08 February 2009 - 04:10 PM
Sure this is optimal, but it creates a maintenance hell. To much builds needed for a every new version.that's why I suggested several different "levels", from the most basic to the most complete, in order to cover "all the range" of possible users, from minimalists to universalists.
That's why I suggest to keep it simple, a floppy version and a full version.
As there is no magic involved the optimal state kexec-loader could reach is to boot from any BIOS supported boot medium and to chainboot any media supported by the linux kernel.Because it would grow in size,
The question is which BIOS supported boot medium make sense to support?
- floppy (low size)
- harddisk (full grown kernel, no space problem)
- USB (full grownn kernel no problem and 1 GB USB pendrives are cheap)
- SCSI (full gorn kernel, no space problem)
- CD / DVD (full gorn kernel, no space problem)
- cardreader (well, also mostly USB) (full gorn kernel, no space problem as 1 GB cards are also cheap)
- zip (full gorn kernel, no space problem)
- network / internet (full gorn kernel, no space problem)
Still a valid argument is speed, a full blown kernel needs longer to boot then a stripped down. For my boot devices (CD / DVD) it doesn't take long to boot a full blown linux kernel (Live CD), the long taking part are init and gui.
#22
Posted 08 February 2009 - 04:14 PM
People wanting "intermediate" builds may well work their way to build them.
jaclaz
#23
Posted 08 February 2009 - 04:15 PM
In console grub-device is not supported. What can I do to make it to work?
I don't agree with PXE. PXE is extremely limited, mostly for intenral LAN cards. For things like booting from USB WLAN + WPA2 over SSL connection from remote server it's not working, fancy boot devices can be only booted with the full kernel.
You could tell me what you think grub-device is, I've never heard of it
WIFI, SSL, WPA?! AAAAH! RUN! THE WIFI DEMON IS HERE! WE'RE ALL GONNA DIE!!!
I think building a toolchain is more difficult than a kernel, I'm currently trying to write a script which generates an uClibc toolchain for kexec-loader instead of relying on the user creating one, so far I've managed to build binutils, I might get GCC to compile by tonight...
EDIT: The past few releases have initramfs's available on the download page, which can be linked into a kernel without needing to build a toolchain.
#24
Posted 08 February 2009 - 04:28 PM
Will answer later.You could tell me what you think grub-device is, I've never heard of it
What are them supposed to do with? Can them be abused to put further modules inside?EDIT: The past few releases have initramfs's available on the download page, which can be linked into a kernel without needing to build a toolchain.
#25
Posted 08 February 2009 - 04:31 PM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users