On Mon, 3 Aug 2020 11:51:27 +0200, Bjoern Voigt <bjoernv@arcor.de> wrote:
ub22@gmx.net wrote:
Seams to be an issue with the linked /home (which I use to be able to use the device in my network with mounted /home from Server and stand alone).
If you need a symlink home -> /home.server/ I would suggest to use a bind mount instead of a symlink. Two reasons:
Why did I not think of this for the /tmp - tmpfs issue? Is it plausible to have /tmp = tmpfs with a service that depends on /tmp that mounts /tmp/whatever to /opt/product/workspace on boot? If I can setup such a scheme in a reliable way, I think that I can workaround the problems I mentioned with legacy products wanting to write files to /tmp (and persist there) This would not be possible if tmpfs does not allow bind to harddisk locations Am I being too terse?
* Many programs use files in $HOME and many of them could not deal consistently with symlinks. For instance they write pathes like /home.server/user/some-file1 and /home/user/some-file2 in config files. * Bind mounts will not result in errors like you described. Offline updates (from CDROM, ISO) may still be an issue. I haven't tested, if the Installer uses the bind mounts from /etc/fstab.
Björn
-- H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/ using perl5.00307 .. 5.31 porting perl5 on HP-UX, AIX, and Linux https://useplaintext.email https://tux.nl http://www.test-smoke.org http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/