From 0a2ba75df4d3d7a258085de4bc95eed7f739bff2 Mon Sep 17 00:00:00 2001 From: Vasudev Kamath Date: Sun, 10 Jan 2016 22:56:50 +0530 Subject: Mount ordering post for Jessie --- content/devops/mount_ordering_jessie.rst | 36 ++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 content/devops/mount_ordering_jessie.rst (limited to 'content/devops') diff --git a/content/devops/mount_ordering_jessie.rst b/content/devops/mount_ordering_jessie.rst new file mode 100644 index 0000000..c7e92fc --- /dev/null +++ b/content/devops/mount_ordering_jessie.rst @@ -0,0 +1,36 @@ +Ordering mount points in Jessie (systemd < 220) +############################################### + +:date: 2015-12-14 22:26 +:slug: ordering_mount_in_jessie +:author: copyninja +:tags: debian, systemd, mount, fstab +:summary: Describes on how to achieve mount ordering in Jessie where + x-systemd.requires is not present. + +In the previous `post +`_ I had +mentioned that I didn't figure out how to add dependency on mount +points so as to achieve correct ordering of mount points. After a lot +of search today I finally figured it out thanks to the `bug report +`_ and the `patch +`_ +which adds *x-systemd.requires* and other option to systemd. + +So basically you can add additional ordering information to the +*.mount* files generated by *systemd-fstab-generator* by adding a +*ordering.conf* file to path +*/etc/systemd/system/usr-local-bin.mount.d/* path with following +contents. + +.. code-block:: ini + + [Unit] + After=home.mount + +And that is it, now *usr-local-bin.mount* will be mounted after +*home.mount* is activated. + +I couldn't find this information directly in related manpages like +*systemd.mount* or *systemd.automount*. Also this information is not +directly available in search results!. -- cgit v1.2.3