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've got a 300GB WD that I use for my UBUNTU OS, and my TB Drive for storage. I have to manually mount the drive every time I boot up. It's considered as removable media by my system. What's the easiest way to have this drive auto-mount and show on my desktop at boot up? (I'm such a greenhorn newbie!)
Thanks in advance for any help, or solutions.
As you said can manually mount that device, after doing that.
Just type in "more /etc/mtab" to find the line for your device.
devpts /dev/pts devpts rw,gid=5,mode=620 0 0
And then copy paste that line to file /etc/fstab (using vi or other tools)
save and reboot
(if you don't know how to manually mount that device, need to use fdisk -l or view /var/log/messages or /var/log/dmesg to find the device name, like sdb1,sdc1)
well using third-party solutions is certainly an option, but getting this done did not require more than just an additional line in your fstab file. when i posted my initial tip i was at work and did not have time to elaborate (figured someone else would), but all you had to add to fstab was something like:
/dev/hdd1 /media/hd ext3 defaults 0 0
where /dev/hdd1 is the physical drive partition i am mounting and /media/hd is the folder i want to access this drive partition through. ext3 is of course the filesystem, defaults covers all the extraneous stuff and 0 0 only comes into play if i want the drive backed up and fsck-ed.
a line like that is all it should have taken to do what your program did there.
Yeah, when I checked what the program had entered into my fstab, I was shocked at the ease of it all. All I needed to do was to enter this simple line:
/dev/sdb1 /media/sdb1 ntfs defaults 0 0
What I still don't understand though, is why linux needs theses incredibly long spaces between the commands & definitions. When I posted this, the servers word processor took out most of the spaces. I was told that just two to three spaces were all that were needed for the system to differentiate between source & target command protocols, like the way it looks in this post. In my fstab file, there are at least 15-20 spaces between /dev/sdb1 & /media/sdb1, and at least 5 spaces between ntfs, defaults, and the first 0. My books never explain why it's done that way, they just say this is the way it should be done. You live and you learn. Please explain why command line does it like this, if you can.