Re: New Kernel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



g wrote:
Ed Warner wrote:
Is there a way to run a new kernel other than restart the machine?

years back, there was a 'coldboot', 'reboot' and 'warmboot'.

I think the PCs version of WARM BOOT was the 3 fingered salute....

now, there is just 'coldboot', ie from power up and thru bios. 'reboot',
ie, restart from bios with out power down.

Ah yes, the RESET button....

'warmboot' reloaded default kernel to 'memory page zero', or other
'jump to' and reinstalled.

'warmboot' could also be passed a kernel name, which it would load to
'memory page zero', or other 'jump to' and ran as new.

because of what is needed for 'warmboot', i believe it was dropped,
because it was not that much time to reboot bios and new kernel can
be passed as an argument to 'boot prompt'.

Actually, there was some "bad" hardware produced back in the early days.
I once had a video controller that when it hung, it had to have a power-on-reset to clear it up. That kinda puts the kabosh on the other types of boots or use of the RESET button. Even though there are separate lines on the PC bus for RESET and PWRonRST, you kinda have to program to the worst hardware level to ensure that it all works right.

somewhere out in cyber, you may find some al programmer has written
a short 'warmboot'. maybe even in c.

I used to work on Prime Computers. When a process hung the whole computer, you could interrupt the system from the console and execute a WARM BOOT. It would reset the active process list and hopefully, the system would continue from where it left off. Kinda like re-starting the kernel, but without destroying the active process lists or resetting the system data structures. If that didn't work, there was always the RST and BOOT 14114 to restart everything from scratch.

if you are meaning 'new kernel' as in rebuild of active kernel,
you may be able to use 'chroot' if you make some changes to files
in /boot and change /boot/grub/grub.conf to recover from bad build.

all in all, easier to just add new kernel to grub.conf and reboot.

--
Kevin J. Cummings
kjchome@xxxxxxx
cummings@xxxxxxxxxxxxxxxxxx
cummings@xxxxxxxxxxxxxxxxxxxxxxx
Registered Linux User #1232 (http://counter.li.org)

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux