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.
I'm installing RedHat 7.2 onto a laptop hard disk in a USB caddy with the intention of subsequently installing the drive into a laptop that has no floppy or CD ROM drive, however I'm having a problem getting the destination machine to boot.
I've tried both Lilo and Grub and they both hang almost immedately (or errors just a flashing cursor) and I believe the problem is due to the fact that the install has configured the boot sequence for the USB caddy drive and not for the primary master IDE controller that the drive ends up being attached to.
The default kernal parameters during the install are...
I've been able to work out that sda1 is the first scsi drive in the system (I'm assuming its treating the external USB caddy as a scsi device) and ide-scsi is an instruction to use scsi emulation for this device, assuming I'm right the problem I have is translating this into what it _should_ be for the destination machine.
Since its going to be the primary master IDE drive in the target system I _believe_ I need to change sda1 to hda however I am unclear if I should retain the ide-scsi or replace it with 'something else' (and if so what the 'something else' needs to be)
Originally posted by win32sux well, you wouldn't need any "ide-scsi", and you'd have to make sure your bootloader is pointing to the correct root device, for example, /dev/hda...
you might want to post your /etc/lilo.conf for discussion...
See thats the problem I cant get at it because the system wont boot once I've moved the drive to the target system, and if I booted it in the install system then I know it would be wrong (because its an external USB drive on that system)
Basically I need to know what I should be putting in the kernel parameters box instead of sda1=ide-scsi during installation to get it to boot from the primary master IDE device
Please be aware that any instance of hda was originally sda1 and has been manually modified by me since being able to access the drive. I have also made the same modifications where applicable in the fstab and device.map files.
My partition layout is as follows
/ (rest of disk space)
The system hangs at boot displaying 'L' (presumably the start of 'Lilo') and a flashing cursor
if you post your exact and working /etc/lilo.conf and /etc/fstab (do a copy/paste), as they are on the source system, someone here might be able to show you exactly what you need to change so that when you put the disk on the target system, it'll work right away...
I dont have an exact and working lilo.conf because neither the install system nor the target system will boot from this disk (the install system wont boot from an external drive, and the target system hangs with 'L' as I have already explained).
I've only been able to get this info by attaching the drive to a 3rd system which is running linux and has the neccessary USB support to read the external caddy.