Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Is there another way to make a CD bootable other than the "el torrito" method? The problem I am having is this:
Basically I am creating a liveCD (or trying to) and am getting a bunch of errors that all point to the fact that I don't have certain things statically compiled into my kernel, and since it is burried in an .img file, it can't get to any modules (because they are on a disk that isn't mounted yet!). What I am wondering is if there is some other way to make the CD bootable so I don't have to use the .img file?
I had a look at the knoppix documentation as suggested. It appears that they are creating a compressed filesystem image to format the CD with. Does that sound close to correct? I am going to give it a try and see what I can do with it!
'Nother question about the ISOLinux method. Here's a quote from their site:
"To create an image, create a directory called "isolinux" (or, if you prefer, "boot/isolinux") underneath the root directory of your ISO image master file tree. Copy isolinux.bin, a config file called "isolinux.cfg" (see syslinux.doc for details on the configuration file), and all necessary files (kernels, initrd, display files, etc.) into this directory, then use the following command to create your ISO image (add additional options as appropriate, such as -J or -R):
Sorry I know this is a terribly newbie question to ask, but I am not entirely sure what they mean by "root-of-iso-tree." Obviously I am supposed to specify a path there, but wouldn't the path to the root of the iso tree be the same thing "/" every time? Can someone give me a couple of good examples of how that should look? Sorry for all the fuss here, this stuff is fairly new to me.
That's the folder where your cdbuild is located.
You could also cd into that directory and use the period ( . )
mkisofs -o output.iso -b isolinux/isolinux.bin -c isolinux/boot.cat \
-no-emul-boot -boot-load-size 4 -boot-info-table .
Alrighty, isolinux booted as advertized, but it didn't resolve the problem. Here is the error I get:
kmod: failed to exec /sbin/modprobe -s -k ide-cd, errno = 2
VFS: Cannot open root device "hdc" or 16:00
Please append correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 16:00
Any ideas? I was wondering if it is possible to load a generic kernel just to bring the devices up, and show a LILO screen, then use that to boot into another kernel somehow? Maybe that is too convoluted . . . Maybe there is an easier way. Any suggestions?
This is great advice, and it worked. I had to compile the IDE-CD driver in instead of as a module. Once I did that, it fired up. There were plenty of other errors, but all that had to do with having a read-only filesystem.