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 no longer need /dev/sde1 and /dev/sdf1 so I want to physically remove them but I haven't done it yet because I don;t know if /dev/sh1 and /dev/sdg will become /dev/sde and /dev/sdf after a server reboot and if that's the case I need to change the fstab entries for these devices. Because thsi is a production server, I don't wan tto do this unless I kno wfor sure what's going to happen.
A quick workaround without changing your fstab would be to create a symbolic link to the new device in a startup script. ln -s /dev/sde1 /dev/sdg1 would create a device sdg1 that would do nothing but point to sde1, so you'd have both present. I don't know how it would work if you added more drives afterwards though.
Changing the fstab is definitely a better solution (and one I was previously unaware of), but wanted to post this in case that doesn't work out for some reason.
Changing the fstab is definitely a better solution
I whole-heartedly agree. The symbolic link thing seems incredibly messy to me. The UUID is a unique fingerprint for a partition/device and is the best way to assure you are using the right thing. There is no standard (AFAIK) about the order in which your devices are recognized. For example, you could be running Debian and have drive A as /dev/sda drive B as /dev/sdb and drive C as /dev/sdc, but then boot the same computer with the same hardware from Knoppix and have drive A = /dev/sda, B = /dev/sdc, and C = /dev/sdb, or even more dramatic, switch to the /dev/hd* scheme
The UUID is a unique fingerprint for a partition/device
Not entirely true, as the UUID is cloned if you use dd to duplicate a drive. (Yeah, I know I'm being picky. ) I have run into it before though; used dd to clone a thumb drive and then couldn't figure out what was going on later. In my experience, all the distros I've used have recognized drives in the same order, though you're right in that there's no guarantee of this.