Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
Hello. I'm not quite a newbie, but it's been a while since I've worked with linux consistently.
I'm working on a Billix install to a 16gb Crucial Survivor. I used a gparted bootable USB to set the boot flag(I run CentOS on my dual boot, and could not find a install-mbr repo for it), gunzipped, untarred, and ran syslinux(I've run it both the windows version and the version distributed with CentOS 5.x).
On boot, BIOS recognizes the hardware, and boots to a syslinux CBIOS screen, giving me the error, "Could not find kernel: linux", followed by a boot prompt. Manually entering any of the many kernels on the USB stick still returns a kernel not found error.
I have seen this problem before, and overcome, but I'm not really sure how. I have the same issue with my gparted stick, but after 10-15 seconds gparted loads.
I have checked kernel and initrd paths in syslinux.cfg.
So my question is not necessarily how do I fix it, but why does it happen? I'd like a fix, but I'd prefer if someone could teach me to fish in this case, as the saying goes.
p.s. semi-related question. When editing cfg files in windows, (using notepad or wordpad), what is the ideal encoding to save with?
Ok, weird problem.
I don't know a lot about CBIOS or gparted but i did boot a USB stick once.
Is used grub for booting and created an initial ramdisk (initrd).
An initrd gets loaded in the memory before the root filesystem is started.
That way I bought time to find out where the USB was mounted on the system.
Could it be that you have some problem mounting or otherwise reaching the location of the kernels?
Awesome! I saw the post getting pushed down without many views and got discouraged.
Syslinux version 3.81. Well the windows version anyway. I'm running CentOS 5.2.x. I'll post the syslinux, but they are not fully pathed, as they are sitting at root. I did try adding / to all the DSL entries to see if it would pick that up.
I'm not sure why a bad path would prevent the menu from even coming up. Hoes brings up an interesting question, I'm pretty sure the APPEND tries to mount init to /etc/init, and from what I saw researching this before I posted, that can cause problems as it needs to get loaded in memory, and this may not happen before the kernel not found error.
Linus72, I think you may be the poster who inspired me to work on this, once I get my head around it I plan on customizing it, pulling out some of the netinstalls, adding ophCrack, gparted, kapersky rescue, and a few others. (One at a time )
I had to changed the syslinux file to .cfg.txt to upload it. It is properly saved on the stick.
so, heres the "fixed" syslinux.cfg
ASSUMING the path to syslinux.cfg is /syslinux folder
AND, assuming kernel/initrd are in /syslinux folder too
OR are they simply on the usb as / ??
This is the file structure and the syslinux.cfg that is working for me.
The USB is formated FAT. The OS is MoonOS based on Ubuntu. The only problem that I have with this arrangement is that I ran out of space in the casper-rw file. I'll have to do this on a larger stick.