Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
I just compiled a couple of kernels (2.4.23 & 2.6.0) on my Debian Knoppix (2.3) and lilo failed. This apparently doesn't have anything to do with those kernels as lilo also fails with my backup copy (before the compile). Here is the error that lilo gives:
Warning: '/proc/partitions' does not match '/dev' directory structure.
Name change: '/dev/hdk' -> '/dev/hdk'
Fatal: open /dev/hdk: No such file or directory
This is so weird. I searched google for answers and did not find much info. The first and last line of the output was seen often but it was about the devfs kernel option/module (of which I am not using) and what is this about "Name change: '/dev/hdk' -> '/dev/hdk'"? I don't see a change in the name do you? the typical thing that people were seeing on google was similar to:
Name Change: /dev/ide/host0/bus0/target0/lun0/disc --> /dev/hda
A bit more poking around and I think I now know what the problem is, although I do not yet know the solution.
My Mobo has 2 ide controlers and a built-in promise raid controller with 2 ide controlers. I also have a promise TX2 Ultra 133 pci ide controler card in my system to get my 180GB HD to see more than 137GB of storage. All together my system has 6 ide controllers (that is 12 possible drives) but /dev/hd? only shows the following devices:
I have drive with a couple of M$ OS's on hda, hdb is not used, hdc & hdd have a cdrw & and a dvd respectivly, hde hdf & hdh are not used, and I have the 180GB with linux OS's on hdg.
I have 2 more (60GB) drives on the promise raid controller that show up in /proc/partitions as hdi and hdk, but those devices are not found under /dev. I know that there is some way to create these devices, but I haven't a clue how?
Help? insights? RTFM's followed by a link to the M?
And to supplement the mknod man page, I would guess that you want to create a block file, (with major, minor numbers similar to the other drives?). The major, minor numbers for the other drives can be seen with an ls -l /dev/hd*. I think they should be the numbers between the group owner and the date.
For anyone who has this same problem and reads this in the archives:
Similar to mknod, I found a script (it may be Debian specific, not sure though, check Google) called MAKEDEV (yes all uppercase) that doen't make you read through the kernel source to find out what major minor you are supposed to use with mknod.
# note the second line is important I didn't do this first time round
#and it made a bunch of block devices in my home directory.
MAKEDEV -v hdi
MAKEDEV -v hdj
MAKEDEV -v hdk
MAKEDEV -v hdl
That did the trick, lilo ran without a hitch. Unfortunatly my kernels wouldn't boot, but that is a Knoppix specific problem that I have delt with before and just need to remember how to solve it. I think it has something to do with cramfs, as the Knoppix kernel compiles everything possible as modules (including filesystem support). The bugger is when you have it installed to the HD and compile a new kernel for your HD installed distro, something is screwy (this is the part I forgot), and the system can't mount the root partition. Of course I just went off topic, but what the hey, I thought that by typing this out I might remember how to fix it. Oh well it will come to me soon.