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!
Notices
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.
please give me the full definition of mount.what do you mean by mounting a filesystem .why we are using it in linux. i googled but not get an appropriate answer please give it full descriptions and example(if any)
with regards
ajay
Last edited by ajay06081993; 10-12-2012 at 09:55 AM.
Distribution: K/Ubuntu 18.04-14.04, Scientific Linux 6.3-6.4, Android-x86, Pretty much all distros at one point...
Posts: 1,802
Rep:
Basically to mount a file system means to attach it to the system at a directory location. You can kind of think of it like you would "mount" a horse to ride it... If a file system is unmounted, it is separated from the directory structure. The attachment address is called the "mount point." For instance, a separate user-space/user account partition's mount point would be /home .
You cannot browse an unmounted file system, nor save or modify files on it. However, you cannot format or modify partitions on a mounted file system (normally, anyway). Unmounted file systems are identified by their udev name (i.e.: /dev/sda1, /dev/sda2, etc.).
there is a set of manuals that come with unix type systems
you have the ability to get to a command line
it may be a function called "terminal"
go to the command line
then type man mount
and it will display the manual for the mount command
or
info mount
will give you more detail
Hi Ajay,
Let's take an example, suppose you have a big house surrounded by strong walls and it has no gate or windows at all. If you want to enter into the house, you will definately need a gate. Similarly, in Unix, in order to access the storage i.e. hard disks or any other storage media from your Unix system, you will need a gate i.e. some entry point or some access point. So your storage is the "house" and your mount point the "gate", which means you can access or enter into the house though that gate. In Unix, we create a directory, which is called "mount point", and attach it to the storage device, so we can access the storage though that directory by keeping our data into it. This processs of creating a directory to access storage is called "mounting" or simply "mount".
Hope it will clear your doubts. :-)
Distribution: Arch, Ubuntu Server 12.04, Slack64-14.1
Posts: 86
Rep:
i'm running ubuntu server on one 2TB drive (will add another once i figure out how to move my media from my win7 machine to my new server)
where should mount the HD?
is there a standard that i should stick to?
What do you mean with "where to mount the drive". If the OS is on it it is already mounted.
You can see which partition is mounted at which mountpoint with just launching the mount command without any parameters.
I like to explain to people that a filesystem is structured like an upside-down tree, with the leaves being all of the files, and the branches like directories (or, probably 'folders' for the Windows oriented). Mounting a new filesystem is then like grafting a branch onto the tree. Not too surprisingly, it is performed using the mount command
It is also somewhat confusing to Windows oriented people that Linux has no concept of 'drives', and uses a single filesystem with a single root. This is distinct from DOS/Windows, where each partition is seen as a distinct drive with it's own root directory. By mounting a partition, it's contents become part of the one and only filesystem on a Linux host, and are therefore addressable within the filesystem.
In general, it is possible to mount a partition at any point in the filesystem (although there are fewer places where it actually makes sense to do so), just as you could generally graft a branch onto a tree wherever you want.
Also confusing is the way the term filesystem is used in multiple but different ways. There is 'the filesystem' as alluded to above. Then, there is the filesystem that constitutes an individual partition, which we build when we 'format' a partition. Then, there is a filesystem type, which we refer to as simply a 'filesystem', such as ext2, ext3, xfs, jffs2, fat, NFS, SMB/CIFS, etc. Usually, it is easy to tell from context which usage is implied, but to the newbie, it can be confusing.
Just to add even more confusion to the uninitiated, Linux likes to treat all devices like files. They even show up in the filesystem under the /dev directory. While they obey most of the semantics of files, they are really just access points to allow software to access physical or logical hardware devices. Same goes for the /proc pseudo filesystem (note the use of a filesystem type, here), which is a convenient entry point into some kernel internals, allowing for standard tools to access those internals. Even though it looks like a filesystem, it occupies no storage on any physical media; it is a virtual filesystem.
Confused enough yet?
--- rod.
Distribution: K/Ubuntu 18.04-14.04, Scientific Linux 6.3-6.4, Android-x86, Pretty much all distros at one point...
Posts: 1,802
Rep:
That was a very nice explanation Rod,... very newbie friendly ...
By the way, I should point out that in my own post above, it reads as though the file system only shows up under its udev name (like; /dev/sda1) when it is not mounted. That is clearly not the case. Hardware shows up under /dev regardless of whether it has been given a user-friendly mounting point or not. Another area where you'll likely need udev names for things is with cameras, sound output and input, and USB (and other serial ports).
My understanding is that the term "mount" comes from the early days of mainframes when the "drives" were actually honking great tape drives. To place a memory tape on a spindle, the operators had to physically lift the spool of tape up to the drive and "mount" it on the spindle.
This may be simply geek legend, but it makes sense and does explain the term.
My understanding is that the term "mount" comes from the early days of mainframes when the "drives" were actually honking great tape drives. To place a memory tape on a spindle, the operators had to physically lift the spool of tape up to the drive and "mount" it on the spindle.
This may be simply geek legend, but it makes sense and does explain the term.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.