Am 16.07.2011 00:07, schrieb Trevour Crow: > --- On Thu, 7/14/11, Michael Biebl <[email protected]> wrote: > >> From: Michael Biebl <[email protected]> >> Subject: Re: Bug#633886: systemd chokes when /tmp is symlinked to /run/tmp >> To: "Trevour Crow" <[email protected]>, [email protected] >> Date: Thursday, July 14, 2011, 3:42 PM > >> Imho symlinking /tmp to /run/tmp is a stupid idea for various reasons. >> If you want /tmp to be on a tmpfs, then make it a separate tmpfs. >> That said, if you want the /run/tmp directory created automatically by >> systemd, >> you can drop a file in /etc/tmpfiles.d [1]. >> I don't think such a file should be shipped by default in systemd though, but >> leave it up to Tollef to decide. >> > My main concern is the fact that systemd breaks on a system sysvinit supports > without any warning(and initscripts's README.Debian gives no hint the > configuration is anything but perfectly acceptable). Is there any reason that > automating the workaround in systemd's postinst would be unacceptable? > Something like this should catch most cases where the bug would manifest: > > if [ -h /tmp ]; then > echo d $(readlink /tmp) 1777 root root - > /etc/tmpfiles.d/tmp-target.conf > fi
Hi Roger, I'm wondering, what was the rationale behind introducing the /tmp → /run/tmp symlink in sysvinit? Isn't that potentially dangerous, as /tmp is writable by everyone thus making /run vulnerable to DoS? While I can see the merit of a /tmp-on-tmpfs, the value behind /run/tmp is not obvious to me. Imho we shouldn't go overboard and stuff everything in /run now that we have it. Unless there is a really good reason for /run/tmp, would you be willing to drop /run/tmp from sysvinit, so that we don't have to add any quirks in systemd to deal with that? Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
