Accessing disks on your own machine
You can access the Unix home directory
/home/login and the
/data/login directory on your own or another machine in several ways - via Samba (CIFS), NFS, or SSHFS. Autofs can be used to simplify mounting. In the section on Samba, you will also find a way to mount the Windows home directory.
The tutorials below are targeted at Unix OSes. If you want to access your home directory on a Windows OS machine, the necessary procedure can be found here.
umount are used for connecting and disconnecting, for example, see the man pages for more information about them. The directory where you want to access the remote directory is called mountpoint. The mountpoint is not created by calling the mount command - it must exist beforehand (exception: Autofs can create it automatically). All mounted (mounted) directories can be displayed by using the
mount command without parameters.
Access via Samba is only possible for machines on the FI network and allows access to the home directory or the
/data/login directory. The Samba protocol is generally blocked on the Internet due to its frequent abuse. You need root access and the
mount.cifs tool on your machine (for example, under Debian, available in the
cifs-utils package). Samba directory export is enabled automatically for the entire FI network. Connection requires authentication credentials. For security reasons, it is best to store them in a file that only root has access to, as it contains the faculty password in clear form. The file can be created in, for example,
/etc/samba/fi_cred.conf, set its access rights to 600, and its contents should be as follows:
username=login password=heslo domain=NTFI
The actual accessing of the home directory to
/mnt/fi-home can be done with the command
muj_stroj# mount -t cifs //home.fi.muni.cz/login /mnt/fi-home \ -o uid=muj_login,gid=skup,credentials=/etc/samba/fi_cred.conf
The parameters uid and gid are the login and primary group on your machine (can be found by running the command
id). Also, the above parameters can be placed in
one line of the file
//home.fi.muni.cz/login /mnt/fi-home cifs uid=muj_login,gid=skup,credentials=/etc/samba/fi_cred.conf 0 0
and then just use the command to connect
muj_stroj# mount /mnt/fi-home
Disconnection can be done with the umount command:
muj_stroj# umount /mnt/fi-home
/data/login directory will be done similarly, but the path to the remote directory will be of the form
In case of problems with the Samba configuration, you can test the functionality of the connection with the
smbclient command (in Debian, you can find it in the package of the same name). After a successful connection, you should see a prompt
Connecting the home directory of Windows machines (H:)
mount command can also be used to mount the home directory and faculty profile folder of Windows machines. Specify
//ad.fi.muni.cz/DFS/home/login as the remote directory or one of the
Windows disks, for example:
mount -t cifs //ad.fi.muni.cz/DFS/home/login /mnt/fi-win-home \ -o uid=muj_login,gid=skup,credentials=/etc/samba/fi_cred.conf
Mounting the home directory on Nymph
Mounting the home directory is also possible without superuser privileges thanks to GVFS, and thus also on Nymphs.
We mount our home directory and authenticate with the faculty password when prompted:
nymfe$ gio mount "smb://NTFI;$USER@ad.fi.muni.cz/dfs/home/$USER"
It is then possible to access this directory via the Unix file system:
nymfe$ cd /run/user/$UID/gvfs/smb-share*/profiles/$USER/ nymfe$ ls
Other Windows volumes can be accessed in a similar way; see the paths listed there.
After the session is over, the directory will be unmounted automatically, or you can manually trigger the unmount with this command:
nymfe$ gio mount -u "smb://NTFI;$USER@ad.fi.muni.cz/dfs/home/$USER"
This access method is only available from Nymfe machines, not from Aisa.
NFS access is only available for machines on the FI network and allows access to the home directory and the
/data/login directory. However, the version 3 of the NFS protocol currently in use requires that the UID and primary GID of the user under which you will be working with the directories on your machine be the same as the UID and primary GID of the faculty Unix account (this information can be obtained by running the command
id). This usage is therefore preferable for the time being for new installations of the system, where these identifiers can be easily influenced. Alternatively, a new user can be created with the required identifiers and then work with the attached files under that user. Due to another NFS specificity, the set file permissions are fully applied to access these files; thus, if you do not have the files made available to others, you will not be able to access them even under the root user on your machine.
Again, you need root access and the
mount.nfs tool on your machine (for example, under Debian, available in the
nfs-common package). You also need to have NFS
export of your home directory and
/data/login enabled (the change will take effect within two hours). The connection does not require authentication, so you need to consider the risk associated with the export. Accessing the home directory in the
/mnt/fi-home mountpoint can be done with the
mount command with the following options:
muj_stroj# mount -t nfs home.fi.muni.cz:/export/home/login /mnt/fi-home \ -o rw,noatime,soft,actimeo=30,vers=3,sloppy,addr=22.214.171.124
muj_stroj# mount -t nfs home.fi.muni.cz:/export/usrdata/login /mnt/fi-data \ -o rw,noatime,soft,actimeo=30,vers=3,sloppy,addr=126.96.36.199
Again, note that the files in the mountpoint are accessible under a user with the same UID and GID, so authentication of the connection needs to be done under that user, not root.
These parameters can also be specified in the
/etc/fstab file (see information in the section on Samba). Alternatively, the
user option can be added so that a normal user can mount/unmount the directory (if you want to run programs from the mountpoint, you need to add the
user option - the
user option automatically disables it):
home.fi.muni.cz:/export/home/login /mnt/fi-home nfs rw,user,exec,noatime,soft,actimeo=30,vers=3,sloppy,addr=188.8.131.52 0 0
You need to have
sshfs installed on your machine. Depending on the distribution, you may then need to add your account to a group that allows
FUSE connections (see information below). This procedure can be used without any further restrictions; the only requirement is a functional login to a faculty machine (Aisa, Anxur, Nymfe, ...). You can mount any directory within your faculty home directory or the
/data/login directory. For example, connecting the faculty directory
/home/login/mail to the
~/fi-mail directory can be done as follows:
muj_stroj$ sshfs -o idmap=user firstname.lastname@example.org:/home/login/mail ~/fi-mail
If this command results in an error accessing the file
/etc/fuse.conf, you need to add the user to the
fuse group, for example with the command
muj_stroj# usermod muj_login -aG fuse).
Once connected, the sshfs command remains running in the background and secures access to remote files. Disconnection can be accomplished with the command
muj_stroj$ fusermount -u ~/fi-mail
Autofs can ensure that a directory is mounted as needed when it is accessed, and then dismounted if not used for a certain period of time.
To install it, you need root access to the machine and the package
autofs. After installation, you need to edit the contents of the files
/etc/auto.master with the main autofs configuration and
/etc/auto.data with the configuration for the machine with shared directories home.fi.muni.cz. When mounting the home directory, add the line
and add a line to the newly created
/etc/auto.home according to the protocol used, the content of which is derived from the fstab lines for that protocol:
# pro pripojovani pres Sambu fi-home-smb -fstype=cifs,uid=muj_login,gid=skup,credentials=/etc/samba/fi_cred.conf ://home.fi.muni.cz/login # pro pripojovani pres NFS fi-home-nfs -rw,user,noatime,soft,actimeo=30,vers=3,sloppy home.fi.muni.cz:/export/home/login
/data/login, only the path to the remote volume will be different: in the case of Samba it will be
//home.fi.muni.cz/data-login, in the case of NFS
The contents of both lines are broken due to their length; the file must contain all parameters for each connection in a single line. Then you still need to reload the autofs configuration, for example with
systemctl reload autofs or another command specific to your distribution, and autofs should be working.
The mountpoint to which the directory is automatically mounted must not exist. However, attempts to access it will cause it to be created and mounted as configured, i.e., when you access
/mnt/net you will not see any directory in the listing of its contents, but the
cd fi-home-smb command will succeed if configured correctly and the subsequent listing of contents will show the files in the remote directory. After a period of inactivity, the remote directory is disconnected and the mountpoint is deleted.
Mounting the remote directory to the file system causes the contents of the directory we are using as a mountpoint to be overlaid. The original directory still exists, but is simply not accessible until the remote directory is unmounted. However, programs that already have that directory or subdirectory open will see the original contents. Therefore, if you were at the mountpoint, mounted the remote directory and dumped its contents, seemingly nothing would change. In that case, switching to that directory again will help.
When mounting directories over a network, it is a good idea to be aware of the risk of losing network connectivity. In such a case, working with the mounted directory will of course cease. Also, programs that work with the contents of this directory may freeze (go into an uninterruptible sleep state; state D in the output of
top ) and these programs may not respond to the SIGKILL signal (
kill -9). Also, directory unmounting for Samba and NFS using
umount may fail. Sometimes this problem can be partially solved by a forced lazy disconnect:
umount -lf; see the manual page for the
umount command for more information.
It is also not a good idea to forcefully terminate a running sshfs, as it may not be possible to correctly unmount the mounted directory.