[opensuse] /tmp as tmpfs
Hey! I installed openSUSE 13.2 with btrfs as root and tried to move /tmp into RAM by using the old systemd trick that Christian told me last year: http://lists.opensuse.org/opensuse/2013-07/msg00141.html However, that does not work anymore. Maybe because /tmp is now a btrfs sub- volume and explicitly mentioned in fstab. So, what is the best and cleanest way to use tmpfs for /tmp on 13.2? Gruß Jab -- The lack of money is the root of all evil. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Sat, 15 Nov 2014 15:08:33 +0100
Jan Ritzerfeld
Hey!
I installed openSUSE 13.2 with btrfs as root and tried to move /tmp into RAM by using the old systemd trick that Christian told me last year: http://lists.opensuse.org/opensuse/2013-07/msg00141.html However, that does not work anymore. Maybe because /tmp is now a btrfs sub- volume and explicitly mentioned in fstab.
Did you try to remove it from /etc/fstab?
So, what is the best and cleanest way to use tmpfs for /tmp on 13.2?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Samstag, 15. November 2014, 17:46:15 schrieb Andrei Borzenkov:
В Sat, 15 Nov 2014 15:08:33 +0100
Jan Ritzerfeld
пишет: Hey!
I installed openSUSE 13.2 with btrfs as root and tried to move /tmp into RAM by using the old systemd trick that Christian told me last year: http://lists.opensuse.org/opensuse/2013-07/msg00141.html However, that does not work anymore. Maybe because /tmp is now a btrfs sub- volume and explicitly mentioned in fstab.
Did you try to remove it from /etc/fstab?
No, not yet, because I am not completely sure whether some tool, like YaST, will put it back there. If this happens today or tomorrow, I will notice it. But in a few days... So I just wanted to check out whether there is a "correct" way that should not break in the future (in contrast to changing files owned by rpm packages). Gruß Jan -- Experience enables you to recognize a mistake when you make it again. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Sat, 15 Nov 2014 17:31:14 +0100
Jan Ritzerfeld
Am Samstag, 15. November 2014, 17:46:15 schrieb Andrei Borzenkov:
В Sat, 15 Nov 2014 15:08:33 +0100
Jan Ritzerfeld
пишет: Hey!
I installed openSUSE 13.2 with btrfs as root and tried to move /tmp into RAM by using the old systemd trick that Christian told me last year: http://lists.opensuse.org/opensuse/2013-07/msg00141.html However, that does not work anymore. Maybe because /tmp is now a btrfs sub- volume and explicitly mentioned in fstab.
Did you try to remove it from /etc/fstab?
No, not yet, because I am not completely sure whether some tool, like YaST, will put it back there.
I do not expect it. If it happens, it sure warrants bug report.
If this happens today or tomorrow, I will notice it. But in a few days... So I just wanted to check out whether there is a "correct" way that should not break in the future (in contrast to changing files owned by rpm packages).
Gruß Jan
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/15/2014 11:31 AM, Jan Ritzerfeld wrote:
Did you try to remove it from /etc/fstab? No, not yet, because I am not completely sure whether some tool, like YaST, will put it back there.
How would it do that? Yast is not a daemon. It doesn't run in the background. It only runs when you invoke it; and I try to use it as little as possible; for example I use zypper on the command line to install packages and updates. But then I'm a old-fogie type of control freak who is not enamoured with GUIs and was doing system administration long before Microsoft Windows. A lot of the time the GUI doesn't do what I want or just gets in the way. A lot of the time I can type the command faster .... I'd add that Yast has many modules, its almost biblical in that![1] If you don't run the one that fiddles with the file system/partitioning why should it alter the fstab? [1] John 14:2 -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Samstag, 15. November 2014, 14:00:25 schrieb Anton Aylward:
On 11/15/2014 11:31 AM, Jan Ritzerfeld wrote:
Did you try to remove it from /etc/fstab?
No, not yet, because I am not completely sure whether some tool, like YaST, will put it back there.
How would it do that? Yast is not a daemon. It doesn't run in the background. It only runs when you invoke it; and I try to use it as little as possible; for example I use zypper on the command line to install packages and updates.
I plan to use the YaST partitioner later in order to add the existing encrypted home partition of 13.1.Thus, it will have to modify fstab and crypttab. Besides, I use YaST for the initial configuration, e.g., for adding users, network printers, iscsi targets, ntp servers, and repositories. However, enabling services and finding packages that I had installed on the previous openSUSE seems to be easier by terminal. But searching for some software package is done by YaST here.
But then I'm a old-fogie type of control freak who is not enamoured with GUIs and was doing system administration long before Microsoft Windows.
When I do I modify most config files via terminal, too. By keeping the original file as .orig, I can easily apply the diff-patch to the files of a new openSUSE version. And starting services via terminal makes it easier to add these lines to my UPDATE file that reminds me of doing it on the next update.
A lot of the time the GUI doesn't do what I want or just gets in the way. A lot of the time I can type the command faster ....
Or graphical text editors modify config files just because of reasons (wrong encoding, tabs, spaces, line endings, file endings, binary content).
I'd add that Yast has many modules, its almost biblical in that![1] If you don't run the one that fiddles with the file system/partitioning why should it alter the fstab?
Because I will use exactly the one that fiddles with the file system/partitioning! :-D Gruß Jan -- Old programmers never die. They just branch to a new address. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/16/2014 08:34 AM, Jan Ritzerfeld wrote:
Am Samstag, 15. November 2014, 14:00:25 schrieb Anton Aylward:
On 11/15/2014 11:31 AM, Jan Ritzerfeld wrote:
Did you try to remove it from /etc/fstab?
No, not yet, because I am not completely sure whether some tool, like YaST, will put it back there.
How would it do that? Yast is not a daemon. It doesn't run in the background. It only runs when you invoke it; and I try to use it as little as possible; for example I use zypper on the command line to install packages and updates.
I plan to use the YaST partitioner later in order to add the existing encrypted home partition of 13.1.Thus, it will have to modify fstab and crypttab.
I've always done that 'by hand', no least of all because I want to see exactly what's being done. As for partitioning, I set up LVM to start with and use that onwards. It lets me do encryption at a more basic level. LVM operates below the filesystem, so whatever it does, it does so at the disk level. So yes, indeed, when LVM implements encryption this is "full-disk encryption" (or, more accurately, "full-partition encryption").
Besides, I use YaST for the initial configuration, e.g., for adding users, network printers, iscsi targets, ntp servers, and repositories.
I don't, but that's beside the point. Such activities don't alter the disk partition.
However, enabling services and finding packages that I had installed on the previous openSUSE seems to be easier by terminal.
But searching for some software package is done by YaST here.
# zypper search
But then I'm a old-fogie type of control freak who is not enamoured with GUIs and was doing system administration long before Microsoft Windows.
When I do I modify most config files via terminal, too. By keeping the original file as .orig, I can easily apply the diff-patch to the files of a new openSUSE version. And starting services via terminal makes it easier to add these lines to my UPDATE file that reminds me of doing it on the next update.
A lot of the time the GUI doesn't do what I want or just gets in the way. A lot of the time I can type the command faster ....
Or graphical text editors modify config files just because of reasons (wrong encoding, tabs, spaces, line endings, file endings, binary content).
I'd add that Yast has many modules, its almost biblical in that![1] If you don't run the one that fiddles with the file system/partitioning why should it alter the fstab?
Because I will use exactly the one that fiddles with the file system/partitioning! :-D
You mean accidentally? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Sonntag, 16. November 2014, 08:58:37 schrieb Anton Aylward:
On 11/16/2014 08:34 AM, Jan Ritzerfeld wrote:
Am Samstag, 15. November 2014, 14:00:25 schrieb Anton Aylward: [...] I plan to use the YaST partitioner later in order to add the existing encrypted home partition of 13.1.Thus, it will have to modify fstab and crypttab.
I've always done that 'by hand', no least of all because I want to see exactly what's being done.
Sure, I fully encrypted some external USB disks and my remote iscsi target. Because I do not need them to mount on boot, in contrast to my home. And I manually resize the iscsi target when needed (not that easy).
As for partitioning, I set up LVM to start with and use that onwards. It lets me do encryption at a more basic level. LVM operates below the filesystem, so whatever it does, it does so at the disk level. So yes, indeed, when LVM implements encryption this is "full-disk encryption" (or, more accurately, "full-partition encryption").
I did that with YaST, without the LVM stuff: a separate fully encrypted home partition via dm-crypt.
[...]
But searching for some software package is done by YaST here.
# zypper search
Nice, especially when adding "-s".
[...]
I'd add that Yast has many modules, its almost biblical in that![1] If you don't run the one that fiddles with the file system/partitioning why should it alter the fstab?
Because I will use exactly the one that fiddles with the file system/partitioning! :-D
You mean accidentally?
No, on purpose, to add my old fully encrypted home partition to fstab and crypttab. Gruß Jan -- When all else fails, read the instructions. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/16/2014 09:23 AM, Jan Ritzerfeld wrote:
You mean accidentally? No, on purpose, to add my old fully encrypted home partition to fstab and crypttab.
surely that is just a one0off occurrence? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Sonntag, 16. November 2014, 10:39:27 schrieb Anton Aylward:
On 11/16/2014 09:23 AM, Jan Ritzerfeld wrote:
You mean accidentally?
No, on purpose, to add my old fully encrypted home partition to fstab and crypttab.
surely that is just a one0off occurrence?
Sure, if it works the first time. If not, I will have other problems than tmpfs and probably forget to check it after fixing all the mess. :) The 13.1 way was clean and easy because I had just to link a file to somewhere in /etc/. I was happy with that because in older releases I had to modify fstab. And this was error-prone, e.g., on 11.0 Beta 2: https://bugzilla.opensuse.org/show_bug.cgi?id=388327 So, I was hoping just not having to touch fstab. Nothing more, nothing less. Gruß Jan -- The greatest American superstition is the belief in facts. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-11-16 14:34, Jan Ritzerfeld wrote:
Am Samstag, 15. November 2014, 14:00:25 schrieb Anton Aylward:
But then I'm a old-fogie type of control freak who is not enamoured with GUIs and was doing system administration long before Microsoft Windows.
When I do I modify most config files via terminal, too. By keeping the original file as .orig, I can easily apply the diff-patch to the files of a new openSUSE version. And starting services via terminal makes it easier to add these lines to my UPDATE file that reminds me of doing it on the next update.
AFAIK, only the YaST partitioner and the NFS (server/client) setups change fstab. Probably also the samba (server/client). Ah, crypto too. The NFS module messes the formatting, so back the file, restore, and edit it yourself. If you are a control freak, setup a weekly cron job: - make a backup copy. - compare the previous backup with the original. - if changed, mail you the diff. No reason I can figure why any yast module should change your setting about tmpfs. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Am Sonntag, 16. November 2014, 15:04:06 schrieb Carlos E. R.: [...]
AFAIK, only the YaST partitioner and the NFS (server/client) setups change fstab. Probably also the samba (server/client). Ah, crypto too.
Exactly. And I will add my fully encrypted home partition later via the YaST partitioner.
The NFS module messes the formatting, so back the file, restore, and edit it yourself.
Ah, okay. I do not use that module, I used autofs to mount NFS shares.
If you are a control freak, setup a weekly cron job:
- make a backup copy. - compare the previous backup with the original. - if changed, mail you the diff.
Haha! No, that would not be reasonable if no one here ever experienced such a problem. I will be able to cope with it if it ever happens.
No reason I can figure why any yast module should change your setting about tmpfs.
Well, I wanted to rule out that any module will put the btrfs tmp subvolume entry back in fstab if I remove it manually. Gruß Jan -- Never let hold of what you've got, until you've got hold of something else. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/15/2014 04:08 PM, Jan Ritzerfeld wrote:
Hey!
I installed openSUSE 13.2 with btrfs as root and tried to move /tmp into RAM by using the old systemd trick that Christian told me last year: http://lists.opensuse.org/opensuse/2013-07/msg00141.html However, that does not work anymore. Maybe because /tmp is now a btrfs sub- volume and explicitly mentioned in fstab. So, what is the best and cleanest way to use tmpfs for /tmp on 13.2?
Gruß Jab
- with TWeed oSUSE 13.2 : using ext4 file system . . . in total ignorance, i stuck a line in /etc/fstab : tmpfs /tmp tmpfs defaults 0 0 ............... - seems to work ok .............. regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Saturday 15 November 2014 17:08:14 ellanios82 wrote:
- with TWeed oSUSE 13.2 : using ext4 file system . . . in total ignorance, i stuck a line in /etc/fstab :
tmpfs /tmp tmpfs defaults 0 0
...............
- seems to work ok
I did the same, commenting out brtfs subvolume for tmp. Works great so far. -- Regards, Stas -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 15/11/14 a las 11:08, Jan Ritzerfeld escribió:
Hey!
I installed openSUSE 13.2 with btrfs as root and tried to move /tmp into RAM by using the old systemd trick that Christian told me last year: http://lists.opensuse.org/opensuse/2013-07/msg00141.html However, that does not work anymore. Maybe because /tmp is now a btrfs sub- volume and explicitly mentioned in fstab. So, what is the best and cleanest way to use tmpfs for /tmp on 13.2?
Should still work that way as long you remove any conflicting fstab entry, this is because fstab takes priority over mount units. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Samstag, 15. November 2014, 15:08:33 schrieb Jan Ritzerfeld:
[...] So, what is the best and cleanest way to use tmpfs for /tmp on 13.2? [...]
Many thanks for your help, Andrei, ellanios82, Stanislav, and Cristian. And sorry for misspelling your name in my first post, Cristian. Gruß Jan -- Enough research will tend to support your theory. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (7)
-
Andrei Borzenkov
-
Anton Aylward
-
Carlos E. R.
-
Cristian Rodríguez
-
ellanios82
-
Jan Ritzerfeld
-
Stanislav Baiduzhyi