Date: Fri, 15 Sep 2017 14:58:23 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: Kirk McKusick <mckusick@mckusick.com> Cc: Konstantin Belousov <kostikbel@gmail.com>, freebsd-arch@FreeBSD.org, freebsd-fs <freebsd-fs@FreeBSD.org> Subject: Re: mount / unmount and mountcheckdirs() Message-ID: <8a8e6eb6-2a80-de22-4944-38820c327a76@FreeBSD.org> In-Reply-To: <201709150314.v8F3Ea6B085072@chez.mckusick.com> References: <201709150314.v8F3Ea6B085072@chez.mckusick.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15/09/2017 06:14, Kirk McKusick wrote: > I had to dig back through some *really* old emails to find out what > triggered the addition of mountcheckdirs(). The problem that it was > specifically solving was that as part of the startup script a minimal > root directory was replaced by the real root directory. The shell > running the startup script needed to be moved to the new mounted-on > root so that the rest of the script would not fail. > > That disaster of a hack has been replaced with the much more functional > code that deals with setting up the root and the devfs filesystem on > /dev. So the need for which it was designed no longer exists. But I > still believe that it is the correct thing to do. For example, if you > are using automount code and chdir into your home directory triggering > an auto-mount, you should just be in your home directory after the > mount rather than having to do cd ../$USER to get there. Kirk, thank you very much both for the historical reference and for the auto-mount example. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8a8e6eb6-2a80-de22-4944-38820c327a76>