Announcement

Collapse
No announcement yet.

Fedora 18 Will Stick To Using Tmpfs

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Fedora 18 Will Stick To Using Tmpfs

    Phoronix: Fedora 18 Will Stick To Using Tmpfs

    It was decided at today's FESCo meeting to not disable the mounting of /tmp as a tmpfs file-system by default for the forthcoming Fedora 18 Linux release...

    http://www.phoronix.com/vr.php?view=MTI0MzY

  • #2
    Yeah, those two bugs are VERY much corner-cases. About VM's; you don't design your operating system for the purpose of being subservient to something else. You design it for the bare metal and just to not be exceedingly incompatible with VM's. It is definitely up to the user shoehorning it in to a VM to make trivial adjustments like this. The Fedora installer still provides configuration options for handling /tmp, its just set to DEFAULT to tmpfs.

    Regarding the other case, installation process with a bajillion repos, I don't think that one even applies to begin with, since you can't use a /tmp on disk before the disk has been partitioned/formatted. The installation process, by definition, MUST have /tmp in RAM.

    Comment


    • #3
      Originally posted by droidhacker View Post
      Regarding the other case, installation process with a bajillion repos, I don't think that one even applies to begin with, since you can't use a /tmp on disk before the disk has been partitioned/formatted. The installation process, by definition, MUST have /tmp in RAM.
      This also confused me, and according to the irc logs not even they really knew what that bug report was about.

      Comment


      • #4
        Been using /tmp on tmpfs since 2006. Glad to see Fedora finally catching up

        Comment


        • #5
          Adobe Flash player misbehaves in this regard

          Adobe Flash easily stuffs 300MB+ files inside /tmp/, the files are called flash-* (if I remember correctly). Took me 10 minutes to figure out why my parents computer (512MB of RAM) kept crashing once they were watching the national tv archive.

          Every 20 minutes the darned thing would crash because Adobe puts temporary files inside /tmp whenever it is streaming over RTMP (I think). Youtube vids don't suffer from this problem. The size of these things can go over 700MB easily (high quality video).

          I'm really suprised no one ever mentioned this before!

          Comment


          • #6
            Originally posted by Rexilion View Post
            Adobe Flash easily stuffs 300MB+ files inside /tmp/, the files are called flash-* (if I remember correctly). Took me 10 minutes to figure out why my parents computer (512MB of RAM) kept crashing once they were watching the national tv archive.

            Every 20 minutes the darned thing would crash because Adobe puts temporary files inside /tmp whenever it is streaming over RTMP (I think). Youtube vids don't suffer from this problem. The size of these things can go over 700MB easily (high quality video).

            I'm really suprised no one ever mentioned this before!
            My AMD netbook, from 1.5 years ago, has 4GB RAM... actual my telephone has 512MB memory. Yes, it will happen that older hardware is not running smoothly with newer software.

            Linux distributions have usually a much better support for older hardware, but at some stage it is better to use the more performant solution for most currently used hardware. There are lots of distribution which even still ship i386 binaries... maybe looking into something like that helps.

            Comment


            • #7
              Originally posted by disi View Post
              My AMD netbook, from 1.5 years ago, has 4GB RAM... actual my telephone has 512MB memory. Yes, it will happen that older hardware is not running smoothly with newer software.

              Linux distributions have usually a much better support for older hardware, but at some stage it is better to use the more performant solution for most currently used hardware. There are lots of distribution which even still ship i386 binaries... maybe looking into something like that helps.
              You are right that it's old hardware which should be replaced in the near future. Fun fact: Next year, there will be tablets that are faster than this box.

              But, this post does not have the intention to say: You should support really old hardware. In fact, Adobe already effectively stopped releasing Adobe Flash for this generation of hardware by including SSE2 instruction that are not supported by it's CPU.

              My post was about the fact that *none* of the objections are about misbehaving pieces of software. It is mentioned as an argument that there *could* be misbehaving software. But no one is mentioning Flash Player, and THAT suprises me.

              I'm just saying that Adobe is (apparently) placing the files in an incorrect location. Using tmpfs as /tmp makes matters much worse for misbehaving software.

              Still, as a response to your post, I'm against replacing perfectly working computer hardware to accomodate misdesigned software! And if I was a REAL laggard and wanted to stick with whatever I had, I would have had a typewriter. It's state of the art: Printer and screen IN ONE! :P .
              Last edited by Rexilion; 12-07-2012, 11:27 AM. Reason: Giving explicit reason for my previous post

              Comment


              • #8
                Simpler English

                Originally posted by phoronix View Post
                Phoronix: Fedora 18 Will Stick To Using Tmpfs

                It was decided at today's FESCo meeting to not disable the mounting of /tmp as a tmpfs file-system by default for the forthcoming Fedora 18 Linux release...

                http://www.phoronix.com/vr.php?view=MTI0MzY
                ==
                If I understand this, tmpfs is ram, /tmp will be mounted to ram (as does Debian) /tmp contents will be erased after each boot. It is a scratch pad area.

                Comment


                • #9
                  Originally posted by Rexilion View Post
                  Still, as a response to your post, I'm against replacing perfectly working computer hardware to accomodate misdesigned software! And if I was a REAL laggard and wanted to stick with whatever I had, I would have had a typewriter. It's state of the art: Printer and screen IN ONE! :P .
                  Wait, so you're against replacing Adobe Flash (the "misdesigned software"), and against replacing the hardware. I'm afraid there are no other options left...

                  Comment


                  • #10
                    Originally posted by GreatEmerald View Post
                    Wait, so you're against replacing Adobe Flash (the "misdesigned software"), and against replacing the hardware. I'm afraid there are no other options left...
                    Nooo, if I can replace Adobe Flash I will gladly do. I'am against replacing a functioning machine to accomodate Adobe Flash misbehaving in tmpfs. A bigger RAM would mitigate the problem, while it's not really necessary.

                    Comment


                    • #11
                      Originally posted by Rexilion View Post
                      Nooo, if I can replace Adobe Flash I will gladly do. I'am against replacing a functioning machine to accomodate Adobe Flash misbehaving in tmpfs. A bigger RAM would mitigate the problem, while it's not really necessary.
                      And there is always the option to, you know, not to mount /tmp as tmpfs. The /etc/fstab file and all.

                      Comment


                      • #12
                        Originally posted by GreatEmerald View Post
                        And there is always the option to, you know, not to mount /tmp as tmpfs. The /etc/fstab file and all.
                        That is exactly what I did. However, I expected that Adobe Flash misbehaving in this regard would be a prime argument. And I'm suprised this was not (explicitly) mentioned.

                        Like it or not, it's still integrated in many sites :/ . And most of the time, the functionality it provides can be replaced by a gif file (like ads). Or a somewhat more advanced webpage using JS and the like. The fact that YouTube is migrating to html5 is a really good thing, I hope that many will follow soon. That will effectively extend the lifetime of my old HW since HTML5 is accelerated by the GPU whilst Flash generally is not...

                        As a sidenote, I find it very inconvenient that this plugin won't listen to TMP or TMPDIR variables (last time I checked). Then I could have fixed it whilst keeping /tmp as a tmpfs filesystem...
                        Last edited by Rexilion; 12-08-2012, 08:57 AM.

                        Comment


                        • #13
                          Originally posted by Rexilion View Post
                          As a sidenote, I find it very inconvenient that this plugin won't listen to TMP or TMPDIR variables (last time I checked). Then I could have fixed it whilst keeping /tmp as a tmpfs filesystem...
                          That's interesting, wouldn't it be possible to do it the other way round, then - export TMP or TMPDIR as /tmp/tmp and set /tmp/tmp as tmpfs, while leaving /tmp as regular space for all those poorly designed programs out there?

                          Comment


                          • #14
                            Originally posted by GreatEmerald View Post
                            That's interesting, wouldn't it be possible to do it the other way round, then - export TMP or TMPDIR as /tmp/tmp and set /tmp/tmp as tmpfs, while leaving /tmp as regular space for all those poorly designed programs out there?
                            that's insane, reread what you just typed

                            Comment


                            • #15
                              Originally posted by Rexilion View Post
                              that's insane, reread what you just typed
                              Actually not that insane, confusing yes since theyre both named tmp but the idea works for those program who break FHS by storing large files in /tmp AND also dont respect $TMPDIR

                              Comment

                              Working...
                              X