Mailinglist Archive: opensuse (686 mails)

< Previous Next >
Re: [opensuse] How should one make /media a tmpfs under 12.3?
On 6/28/2013 3:20 PM, Anton Aylward wrote:
Carlos E. R. said the following on 06/28/2013 02:38 PM:
Hash: SHA1

On Friday, 2013-06-28 at 12:59 -0400, Anton Aylward wrote:
Andrey Borzenkov said the following on 06/28/2013 06:11 AM:
On Fri, Jun 28, 2013 at 1:50 PM, Carlos E. R. <> wrote:

So long as it is in /etc/tmp*.d/<whatver> or the /usr/lib equivalent
it will
be recreated by systemd-tmpfiles on every boot. As the man page
says, you've
read that, I presume, if you don't want that action you symlink the
filename to /dev/null.

I don't understand this. Symlink /media to dev/null?

Symlink the appropiate /etc/tmp*.d/<whatver> or the /usr/lib equivalent
to /dev/null like it says in thee man page:

If the administrator wants to disable a configuration file supplied by
the vendor the recommended way is to place a symlink to /dev/null in
/etc/tmpfiles.d/ bearing the same file name.


This interface, like most everything else from Poettering/Sievers as usual, is really backwards and terrible and tramples all over principle of least surprise.

It is in no way obvious or the users fault for having the system do unexpected things by default that are not indicated by any of the user-facing config files, and you have to go out of your way to *prevent* it with arcane non-obvious things like creating a file that didn't exist before, and making it a symlink to /dev/null. A more confusing and opaque system is hard to even imagine. Especially for a user-facing interface.

Instead of having it be where some config file always exists, and can always contain a reference to some common action even when disabled, by having a commented out option or by having OPTION=false etc, or failing that, at least having it where things don't happen UNLESS config files that say so exist, like /etc/foo.d directories have, no instead something will happen all by itself unless you go out of your way to prevent it, but you don't know how to do that because, you have no way to know what's doing it in the first place, none of your config files that you know about says to do any such thing.

Then you have the other side of things, say your /dev/null link does exist. Normally any file like that just looks like either an error or the ugliest of ugly hacks to work around something that doesn't provide a proper way do do something you want. Like how you can prevent ssh from saving/comparing/rejecting ssh host fingerprints by symlinking your known_hosts file to /dev/null. It's a complete and utter hack and no way to operate for real.

This is not even slightly a case of blame the user for not rtfm. There wasn't even enough to go on to begin with to indicate which fm to r.


To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >
This Thread
  • No further messages