From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: [PATCH v1] tools/hotplug: convert proc-xen.mount to proc-xen.service Date: Thu, 26 Oct 2017 19:05:38 +0200 Message-ID: <20171026170538.GH4555@aepfle.de> References: <20171026152536.17072-1-olaf@aepfle.de> <20171026155940.GG4555@aepfle.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3971549814710575763==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: Andrew Cooper Cc: Wei Liu , Ian Jackson , Vasilis Liaskovitis , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org --===============3971549814710575763== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="j+MD90OnwjQyWNYt" Content-Disposition: inline --j+MD90OnwjQyWNYt Content-Type: text/plain; charset=utf-8 Content-Disposition: inline On Thu, Oct 26, Andrew Cooper wrote: > I've never really understood why xenfs exists in the first place > (although I expect the answer is "Because that is how someone did it in > the past"), and I'm not aware of any other project which needs its own > custom filesystem driver for device nodes. Perhaps in the early days, before udev, new nodes would not magically appear in /dev. It was likely easy to be compatible that way, just like claiming /dev/hda to please existing installation programs. > Is it possible to express a dependency on proc-xen.mount || > proc-xen.service? As ordering yes, an additional After=proc-xen.service line is needed. An existing Requires=proc-xen.mount can not be used anymore, I have not verified that. > If not, then out-of-tree packages are going to have compatibility > problems with this change. Only if they use Requires=proc-xen.mount. > Right, but ISTR that Systemd deals with /etc/fstab by auto-generating > *.mount targets, and from what is said here, it is the proc-xen.mount > target which is now broken by the change in systemd behaviour. No, existing fstab entries will continue to work. /dev/shm is automounted, and my own fstab entry for /dev/shm always worked. Olaf --j+MD90OnwjQyWNYt Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iFwEARECAB0WIQSkRyP6Rn//f03pRUBdQqD6ppg2fgUCWfIV3wAKCRBdQqD6ppg2 fsklAJ91lXPYChF8qAEnk1csxQmv4l0JcgCY60ZJo3AFCcUABtZg5RdoCfuDpg== =L7Jk -----END PGP SIGNATURE----- --j+MD90OnwjQyWNYt-- --===============3971549814710575763== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwczovL2xpc3RzLnhlbi5v cmcveGVuLWRldmVsCg== --===============3971549814710575763==--