Sponsored Content
Full Discussion: Hard Disk Prep From Shell
Operating Systems Linux Fedora Hard Disk Prep From Shell Post 302611785 by Corona688 on Friday 23rd of March 2012 01:18:51 PM
Old 03-23-2012
The linux operating system automatically recognizes when disks are attached*, including USB disks and the like, and the corresponding devices under /dev/ ought to appear automatically too. But the only disk Linux automatically mounts is the root partition, right when it boots. From there on out, the kernel only ever mounts the disks it's told to mount.

So, automounting hotplugged drives is something done by application software, not Linux itself. The GNOME window manager tries to automount external disks for instance. Other times, the pmount suite is used to automount, and can also decide who's allowed to automount what.

And quite a few systems don't automount at all. Automount is useful for plugging in flash drives, but there are many situations you do not want disks to be automounted. A system with a software RAID for instance -- you want the RAID to control the disks itself, instead of them being grabbed by the automounter. Or a secure server, which would have no business mounting a strange drive unasked. Or a system being used for data-recovery on a spotty drive which is simply unable to be mounted. And so forth.

* The hardware has to support it of course. Any modern SATA port is technically supposed to be hotswap, but the feature isn't always implemented properly.
This User Gave Thanks to Corona688 For This Post:
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Divvy a hard disk

What is the general rule for a divvy of a hard disk, I know that the boot is 20 megs swap is times 2 of ram. I am learning unix for the first time and at work i cant get this divvy thing down pat yet. boot 1 to 19999 swap 20000 to 122499 (512 megs of ram) root 122500 to ? u ? u2 ? ... (1 Reply)
Discussion started by: DjWolfman
1 Replies

2. UNIX for Dummies Questions & Answers

Divvy a hard disk

What is the general rule for a divvy of a hard disk, I know that the boot is 20 megs swap is times 2 of ram. I am learning unix :) for the first time and at work i cant get this divvy thing down pat yet. boot 1 to 19999 swap 20000 to 122499 (512 megs of ram) root ... (2 Replies)
Discussion started by: DjWolfman
2 Replies

3. Filesystems, Disks and Memory

hard disk meltdown

I had an issue with a second hard disk in my machine. I have a sparc station running solaris 7. It was working fine but now it wont mount on boot up and when you try to mount it manually it gives an I/O error. I tried a different disk as a control which was fine. What I want to know is if my... (3 Replies)
Discussion started by: Henrik
3 Replies

4. Filesystems, Disks and Memory

Adding hard Disk

Hi all, I am using SCO Openserver V and I want to add one more harddisk (/dev/hd1) Hw can I do it? (1 Reply)
Discussion started by: skant
1 Replies

5. Filesystems, Disks and Memory

hard disk problems

i have recently recieved a new hard drive which i needed for lack of space. i installed a newer version of my previous operating system, suse 8.2. i saved my old drive just in case. anyway this thing only boots sporadically. the person who gave it to me forgot to tell me there was problems with... (2 Replies)
Discussion started by: norsk hedensk
2 Replies

6. UNIX Desktop Questions & Answers

Hard Disk

I have a cuestion. How Can I to add other hard disk to my computer? I need to configurate anyone? (4 Replies)
Discussion started by: hmaraver
4 Replies

7. UNIX for Dummies Questions & Answers

Hard Disk at 99% Help!

:eek: I use this Solaris to run CMS a call acounting software package for my job. No one could run reports today because it said the this when you logged on "The following file systems are low, and could adversely affect server performance: File system /: 99%full" Can some one please explain... (9 Replies)
Discussion started by: mannyisme
9 Replies

8. SCO

declare disk driver for IDE hard disk

hi I've a fresh installation of SCO 5.0.7 on the IDE hard disk. For SCSI hard disk I can declare, for example blc disk driver using: # mkdev hd 0 SCSI-0 0 blc 0but it works for IDE hard disk? (3 Replies)
Discussion started by: ccc
3 Replies

9. Linux

C++ Code to Access Linux Hard Disk Sectors (with a LoopBack Virtual Hard Disk)

Hi all, I'm kind of new to programming in Linux & c/c++. I'm currently writing a FileManager using Ubuntu Linux(10.10) for Learning Purposes. I've got started on this project by creating a loopback device to be used as my virtual hard disk. After creating the loop back hard disk and mounting it... (23 Replies)
Discussion started by: shen747
23 Replies

10. BSD

Migrate a Hard Disk

hi Has anyone already tried to migrate a hard disk with FreeBSD using recoverdisk? (1 Reply)
Discussion started by: ccc
1 Replies
SYSTEMD.AUTOMOUNT(5)						 systemd.automount					      SYSTEMD.AUTOMOUNT(5)

NAME
systemd.automount - Automount unit configuration SYNOPSIS
automount.automount DESCRIPTION
A unit configuration file whose name ends in ".automount" encodes information about a file system automount point controlled and supervised by systemd. This man page lists the configuration options specific to this unit type. See systemd.unit(5) for the common options of all unit configuration files. The common configuration items are configured in the generic [Unit] and [Install] sections. The automount specific configuration options are configured in the [Automount] section. Automount units must be named after the automount directories they control. Example: the automount point /home/lennart must be configured in a unit file home-lennart.automount. For details about the escaping logic used to convert a file system path to a unit name see systemd.unit(5). For each automount unit file a matching mount unit file (see systemd.mount(5) for details) must exist which is activated when the automount path is accessed. Example: if an automount unit home-lennart.automount is active and the user accesses /home/lennart the mount unit home-lennart.mount will be activated. Automount units may be used to implement on-demand mounting as well as parallelized mounting of file systems. If an automount point is beneath another mount point in the file system hierarchy, a dependency between both units is created automatically. FSTAB
Automount units may either be configured via unit files, or via /etc/fstab (see fstab(5) for details). For details how systemd parses /etc/fstab see systemd.mount(5). If an automount point is configured in both /etc/fstab and a unit file, the configuration in the latter takes precedence. OPTIONS
Automount files must include an [Automount] section, which carries information about the file system automount points it supervises. The options specific to the [Automount] section of automount units are the following: Where= Takes an absolute path of a directory of the automount point. If the automount point does not exist at time that the automount point is installed, it is created. This string must be reflected in the unit filename. (See above.) This option is mandatory. DirectoryMode= Directories of automount points (and any parent directories) are automatically created if needed. This option specifies the file system access mode used when creating these directories. Takes an access mode in octal notation. Defaults to 0755. SEE ALSO
systemd(1), systemctl(8), systemd.unit(5), systemd.mount(5), mount(8), automount(8), systemd.directives(7) systemd 208 SYSTEMD.AUTOMOUNT(5)
All times are GMT -4. The time now is 09:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy