Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I realise this question is a little off the wall but I'm looking for a way to test a kernel without actually installing it.
The reason for this is that I want to make a modification to the existing kernal on my (debian) NAS. The bootloader and kernel are both stored in flash memory on the board but there is no way to write to this except through the opperating system itself (via SSH). The bootloader doesn't have hard disk support. So if I change the kernal and find that it no-longer boots then I'll have bricked my NAS.
I was hoping that there may be a way to get a linux install to act like an oversized bootloader and kick off a seperate kernal.
I realised this a rather odd requirement so any suggestions welcome.
Im assuming it's only a short matter of time before x86_64 will be supported? :fingers crossed:
Good question indeed.. I didn't note how old was the article I linked above, but doing a google for "64 bit kexec" turns up a LOT of hits, particularly for "64bit kexec-tools package".
Hmm, if it isn't supported right now, it could be due to hardware limitations. The following are just assumptions (didn't check that):
- Maybe kexec() on x86 switches the processor back to real mode before exec()ing the bootup code of the kernel
- Maybe there's no (easy) way to get back to real (or even protected) mode from long mode in x86_64 ... edit: But it looks like this isn't really necessary (OR solved) by now
Sadly there are two problems with kexec in my case.
1: It's an ARM chip (Marvell Orion)
2: I dont *think* (havn't checked) that this support is in my current kernel. This creates a sort of catch 22.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.