Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
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.
Hi everyone,
I've installed RHEL 5 for my server and configured kernel 2.6.18-8.el5 as a Monolithic kernel (loadable modules aren't supported). Now I need to create a rescue CD. I put the new CD to the driver and use this command: cp /boot/vmlinux-2.6.18-8.el5 /dev/cdrom
But it announces that: Cannot create a file in /dev/cdrom, it is a read-only file system.
Could you please give me the way to create a rescue CD?
Thank you!
Why don't you just add the new kernel to your grub boot list?
I've already done that.
But I need a rescue CD so that whenever my server goes down by attackers or by my bad configuration, I can reboot the server with the expected kernel.
I wasn't angry, I simply don't see why you bother posting when you clearly don't follow the thread, or apparently understand the fairly obvious intent of the OP.
I wasn't angry, I simply don't see why you bother posting when you clearly don't follow the thread, or apparently understand the fairly obvious intent of the OP.
So every emergency case requires a boot CD? How about if your computer just didn't start after recompiling the kernel and nothing was wrong with grub or any other part of the operating system?
And I didn't understand the thread? What was my original response, wiseguy?
Yes, but it's a good place to start by telling someone they need to burn the CD when they're trying to copy a file to a CD device using the cp command. And pull my head in? I never said anything about your posts.
Yes, I need a rescue CD to reboot the machine with my configured kernel in emergency cases.
There are three utilities I've used, with great success. Check out the mkcdrec, systemimager, and mondoarchive utilities. All of them can make bootable images, suitable for either network or DVD/CD booting and recovery from a 'bare metal' situation.
IMHO, it's best to make a bootable CD with a kernel, custom-suited to your hardware. That way, if you boot from it, you know you'll have all the hardware modules needed to get disk drives/network adapters/video, etc., working right off the bat. From there, you can (at least with mondoarchive), pull an ISO from a network resource. That'll let you have an aged recovery CD in the drive, with a current 'snapshot' (created with CRON or other scheduled job), on a network resource elsewhere.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.