Sponsored Content
Operating Systems Solaris why we need to mount file system other than / file system Post 302312795 by vr_mari on Sunday 3rd of May 2009 12:13:49 PM
Old 05-03-2009
Hi DukeNuke2,

I think you misunderstood my question. My question is if we mount a / file system , all the the other file systems like /etc , /var , /usr will automatically mounted or not because these are all (/usr,/var,/tmp) sub folders of the root file system.

Am i Correct ? I knew that / , /usr , /var file system are in different cylinders of the disk. But how they comes under the / file system. Whether / is the folder or a file system?

Thanks
Maro
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

how to mount a file system of a remote machine to local file system

Hi friends, In my case, there are serveral PCs running Linux in a LAN. I would like to to mount the directory /A_river of machine-A to the file system of another machine machine-B so that I can access files in that directory. I do not know how to do this. The situation is complicated by... (2 Replies)
Discussion started by: cy163
2 Replies

2. Solaris

File system and disc mount

Hello All Well i m using sun fire and I want to view file system on each disc mount then what will be the commands?...like i want to get each disc like c0t0d0s0 and others and i want to see directories and files distributed on each discs.... with heartiest greetings nilanjan (7 Replies)
Discussion started by: ailnilanjan
7 Replies

3. Solaris

Mount a remote file system

Hello, I'm having troubles with sharing a filesystem across 2 machines... Machine A, running Solaris 10, is sharian via NFS the filesystem /sp. Machine B, running Solaris 10, is mounting /sp shared by A in /tm/sp and shares via NFS the /tm folder. Machine C, running HP-UX, is mounting... (4 Replies)
Discussion started by: mirciulicai
4 Replies

4. UNIX and Linux Applications

The usage of mount file system of different servers

There is a file system in server1 which is mounted on different file system on server2. Filesystem kbytes used avail capacity Mounted on server1:/users/user1 7047581 5994192 982914 86% /u01 /data/datafiles/user1 The data in... (1 Reply)
Discussion started by: vamshikrishnab
1 Replies

5. HP-UX

how to mount a file system from a solaris server into an hp-ux system

Hi all I wonder if its possible to mount on a hp-ux server a file system that was previously mounted on a solaris 10 server. The LUN is on NetApp stoarge. The problem on hp-ux I cannot do pvcreate on the lun (disk) because contains data. Any help will be appreciated FR (2 Replies)
Discussion started by: fretagi
2 Replies

6. Solaris

Specifying file system mount order

Does anyone know if it's possible to specify the mount order of local and remote file systems? I'd like to mount a local ZFS file system on top of an NFS mount automatically and have that repeated on every reboot. I've checked man pages and Google, but can't find anything that addresses,... (6 Replies)
Discussion started by: Monty51
6 Replies

7. HP-UX

[Solved] Mount HP-UX File System in Windows 7

Hello, We just got a rx4640 that is running on: HP-UX B.11.31 U ia64 2426088954 unlimited-user license There is a plenty of space in it and we would like to use it for storage. I can access with ftp and place the files in there but i need to mount the file system in every PC that is running... (7 Replies)
Discussion started by: gjk
7 Replies

8. AIX

Cannot mount file system

Hi , We i try to mount aix filesystem i am getting the following error mount: 0506-324 Cannot mount /dev/fslv11 on /testdir: A system call received a parameter that is not valid. Please help me out (2 Replies)
Discussion started by: chidori
2 Replies

9. Red Hat

Unable to mount a clone file system (NetApp)

Hi I have the following difficulty: the NetApp admin has clone one file system from one red hatserver and presented this cloned LUN into another redhat server. I can see the LUN as: fdisk -l Disk /dev/sda: 64.4 GB, 64424509440 bytes 255 heads, 63 sectors/track, 7832 cylinders Units =... (1 Reply)
Discussion started by: fretagi
1 Replies
SYSTEMD-FSTAB-GENERATOR(8)                                    systemd-fstab-generator                                   SYSTEMD-FSTAB-GENERATOR(8)

NAME
systemd-fstab-generator - Unit generator for /etc/fstab SYNOPSIS
/lib/systemd/system-generators/systemd-fstab-generator DESCRIPTION
systemd-fstab-generator is a generator that translates /etc/fstab (see fstab(5) for details) into native systemd units early at boot and when configuration of the system manager is reloaded. This will instantiate mount and swap units as necessary. The passno field is treated like a simple boolean, and the ordering information is discarded. However, if the root file system is checked, it is checked before all the other file systems. See systemd.mount(5) and systemd.swap(5) for more information about special /etc/fstab mount options this generator understands. One special topic is handling of symbolic links. Historical init implementations supported symlinks in /etc/fstab. Because mount units will refuse mounts where the target is a symbolic link, this generator will resolve any symlinks as far as possible when processing /etc/fstab in order to enhance backwards compatibility. If a symlink target does not exist at the time that this generator runs, it is assumed that the symlink target is the final target of the mount. systemd-fstab-generator implements systemd.generator(7). KERNEL COMMAND LINE
systemd-fstab-generator understands the following kernel command line parameters: fstab=, rd.fstab= Takes a boolean argument. Defaults to "yes". If "no", causes the generator to ignore any mounts or swap devices configured in /etc/fstab. rd.fstab= is honored only by the initial RAM disk (initrd) while fstab= is honored by both the main system and the initrd. root= Takes the root filesystem to mount in the initrd. root= is honored by the initrd. rootfstype= Takes the root filesystem type that will be passed to the mount command. rootfstype= is honored by the initrd. rootflags= Takes the root filesystem mount options to use. rootflags= is honored by the initrd. mount.usr= Takes the /usr filesystem to be mounted by the initrd. If mount.usrfstype= or mount.usrflags= is set, then mount.usr= will default to the value set in root=. Otherwise, this parameter defaults to the /usr entry found in /etc/fstab on the root filesystem. mount.usr= is honored by the initrd. mount.usrfstype= Takes the /usr filesystem type that will be passed to the mount command. If mount.usr= or mount.usrflags= is set, then mount.usrfstype= will default to the value set in rootfstype=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrfstype= is honored by the initrd. mount.usrflags= Takes the /usr filesystem mount options to use. If mount.usr= or mount.usrfstype= is set, then mount.usrflags= will default to the value set in rootflags=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrflags= is honored by the initrd. systemd.volatile= Controls whether the system shall boot up in volatile mode. Takes a boolean argument or the special value state. If false (the default), this generator makes no changes to the mount tree and the system is booted up in normal mode. If true the generator ensures systemd-volatile-root.service(8) is run as part of the initial RAM disk ("initrd"). This service changes the mount table before transitioning to the host system, so that a volatile memory file system ("tmpfs") is used as root directory, with only /usr mounted into it from the configured root file system, in read-only mode. This way the system operates in fully stateless mode, with all configuration and state reset at boot and lost at shutdown, as /etc and /var will be served from the (initially unpopulated) volatile memory file system. If set to state the generator will leave the root directory mount point unaltered, however will mount a "tmpfs" file system to /var. In this mode the normal system configuration (i.e. the contents of "/etc") is in effect (and may be modified during system runtime), however the system state (i.e. the contents of "/var") is reset at boot and lost at shutdown. Note that in none of these modes the root directory, /etc, /var or any other resources stored in the root file system are physically removed. It's thus safe to boot a system that is normally operated in non-volatile mode temporarily into volatile mode, without losing data. Note that enabling this setting will only work correctly on operating systems that can boot up with only /usr mounted, and are able to automatically populate /etc, and also /var in case of "systemd.volatile=yes". SEE ALSO
systemd(1), fstab(5), systemd.mount(5), systemd.swap(5), systemd-cryptsetup-generator(8), kernel-command-line(7) systemd 237 SYSTEMD-FSTAB-GENERATOR(8)
All times are GMT -4. The time now is 08:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy