Path: csiph.com!xmission!news.alt.net!not-for-mail From: owl Newsgroups: comp.os.linux.advocacy Subject: Re: Linux Tmpfs Virtue Date: Thu, 21 Jan 2016 10:48:54 +0000 (UTC) Organization: O.W.L. Lines: 89 Message-ID: References: <4150ecf6-8562-4f49-be9f-c5ecbda17c94@googlegroups.com> NNTP-Posting-Host: boom.rooftop.invalid User-Agent: tin/2.2.1-20140504 ("Tober an Righ") (UNIX) (Linux/3.16.0-4-amd64 (x86_64)) Xref: csiph.com comp.os.linux.advocacy:341221 Desk Rabbit wrote: > On 20/01/2016 19:23, owl wrote: >> Desk Rabbit wrote: >>> On 19/01/2016 09:48, owl wrote: >>>> Desk Rabbit wrote: >>>>> On 13/01/2016 13:31, John Gohde wrote: >>>>>> On Tuesday, January 5, 2016 at 6:51:01 AM UTC-5, Desk Rabbit wrote: >>>>>>> On 04/01/2016 19:58, Vile Strong wrote: >>>>>>>> One of the highly useful capabilities of the Linux OS is >>>>>>>> the tmpfs, which is a temporary file system located entirely >>>>>>>> in RAM. >>>>>>>> >>>>>>>> The user can invoke a tmpfs any time and of any size with >>>>>>>> the command: >>>>>>>> >>>>>>>> mount -t tmpfs -o size=XG,mode=0777 tmpfs /mount-point >>>>>>>> >>>>>>>> A tmpfs can be used for a variety of purposes, such as the speedy >>>>>>>> compile of a large program or a very quick "scratch" storage >>>>>>>> for very large data processing. >>>>>>>> >>>>>>>> Does Microsoft Windows have this capability? >>>>>>>> >>>>>>>> FUCK NO!!!! >>>>>>>> >>>>>>>> That's another testament to the superiority of Linux over >>>>>>>> Microsoft. >>>>>>>> >>>>>>> >>>>>>> And of course, your given example doesn't work >>>>>>> >>>>>>> [root@mail ~]# mount -t tmpfs -o size=XG,mode=0777 tmpfs /mnt/tmpfs >>>>>>> mount: wrong fs type, bad option, bad superblock on tmpfs, >>>>>>> missing codepage or helper program, or other error >>>>>>> (for several filesystems (e.g. nfs, cifs) you might >>>>>>> need a /sbin/mount. helper program) >>>>>>> In some cases useful info is found in syslog - try >>>>>>> dmesg | tail or so >>>>>>> >>>>>>> >>>>>>> It's the size=XG that's wrong, you need to specify a number i.e. 1G for >>>>>>> one gigabyte. >>>>>> >>>>>> >>>>>> OR IF YOU HAD A BRAIN, rodent, the ue of an "X" script should have been self-explanatory. >>>>> >>>>> Oh do explain what an "X" script is in this context great Linux master. >>>>> >>>>> This should be good........ >>>>> >>>>> :-) >>>>> >>>> >>>> It can't possibly be as good as you running a command as root without >>>> scrutinizing it first. :) >>>> >>> >>> On a throw away isolated VM based system? You find that entertaining? >>> How odd. >>> >> >> I find it entertaining that you did this on what appears to be a mail >> server. Even if it's just a lab VM for testing, it's probably more >> important than a "throw away," and you shouldn't just blindly run >> a command on it as root if you don't understand what the command does. > > Calling a machine "bigdick" doesn't make it a dildo. > You gave a hostname of "mail" to a machine that is not a mail server? Yeah, sure you did. LOL. >> >>> How else could I display the error without running the command??? >> >> You wouldn't get the error message if you had read the man page. >> Or did you think that size was given in Roman numerals? >> > > Reading the man page doesn't give a error output to illustrate an > incorrect command line. Do you really expect a man page to illustrate the myriad ways a command might be mistyped? The program itself gave you an error output. The man page describes the return codes, which you can check with `echo $?`. Most importantly to this case though, the man page also tells you how the "size=" option is used. No mention of Roman numerals though.