Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.advocacy > #341323

Re: Linux Tmpfs Virtue

Show all headers | View raw

On 21/01/2016 18:30, owl wrote:
> Desk Rabbit <me@example.com> wrote:
>> On 21/01/2016 13:11, owl wrote:
>>> Desk Rabbit <me@example.com> wrote:
>>>> On 21/01/2016 10:48, owl wrote:
>>>>> Desk Rabbit <me@example.com> wrote:
>>>>>> On 20/01/2016 19:23, owl wrote:
>>>>>>> Desk Rabbit <me@example.com> wrote:
>>>>>>>> On 19/01/2016 09:48, owl wrote:
>>>>>>>>> Desk Rabbit <me@example.com> 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.<type> 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.
>>>>
>>>> Whatever, the name tells you SFA about the function and the fact still
>>>> remains that it was an isolated VM.
>>>>
>>>
>>> Is it a mail server?  Yes or no.
>>>
>>>>>
>>>>>>>
>>>>>>>> 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.
>>>>>
>>>>
>>>> Are you deliberately missing the point just so you can have an argument?
>>>
>>> Are you deliberately being Snittish in your refusal to just admit that
>>> you ran a command as root without understanding what the command does?
>>>
>>
>> I ran a command that I am familiar with as root on an isolated VM system
>
> On a mail server VM.  Your refusal to admit this makes me wonder
> if it really even is a VM.
>
>> to provide a detailed output error to illustrate the incorrect nature of
>> an example given by a poster. Nothing more, nothing less. Everything
>> else is in your imagination or is pure supposition/assumption or a
>> deliberate attempt to miss the point to create conflict where none exists.
>
> You keep claiming the example was "wrong."  The example was not "wrong"
> just because "XG" was used to represent the size.  That's like saying
> that this rsync example:
>
>     rsync -av host:file1 :file2 host:file{3,4} /dest/
>
> "doesn't work" as is on your system and therefore the commandline
> is "wrong."
>
> Your analysis of his example:
>
> <quote>
> And of course, your given example doesn't work
> ...
> It's the size=XG that's wrong, you need to specify a number i.e. 1G for
> one gigabyte.
> </quote>
>
> Funny but it looks like you changed the mount point in his example
> from /mount-point to /mnt/tmpfs, and of course created the /mnt/tmpfs
> directory, or it would not have worked as given anyway.  One wonders why
> after going to all that trouble that you did not also make the change
> from "size=XG" to a value that would work if, as you say, it is a command
> that you "are familiar with."
>

I'm not going to waste any further time arguing with your assumptions.

EOT

Back to comp.os.linux.advocacy | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Re: Linux Tmpfs Virtue John Gohde <john.h.gohde@gmail.com> - 2016-01-13 05:31 -0800
  Re: Linux Tmpfs Virtue Desk Rabbit <me@example.com> - 2016-01-18 10:34 +0000
    Re: Linux Tmpfs Virtue owl <owl@rooftop.invalid> - 2016-01-19 09:48 +0000
      Re: Linux Tmpfs Virtue Desk Rabbit <me@example.com> - 2016-01-20 15:07 +0000
        Re: Linux Tmpfs Virtue owl <owl@rooftop.invalid> - 2016-01-20 19:23 +0000
          Re: Linux Tmpfs Virtue Desk Rabbit <me@example.com> - 2016-01-21 09:44 +0000
            Re: Linux Tmpfs Virtue owl <owl@rooftop.invalid> - 2016-01-21 10:48 +0000
              Re: Linux Tmpfs Virtue Desk Rabbit <me@example.com> - 2016-01-21 11:05 +0000
                Re: Linux Tmpfs Virtue owl <owl@rooftop.invalid> - 2016-01-21 13:11 +0000
                Re: Linux Tmpfs Virtue Desk Rabbit <me@example.com> - 2016-01-21 16:52 +0000
                Re: Linux Tmpfs Virtue owl <owl@rooftop.invalid> - 2016-01-21 18:30 +0000
                Re: Linux Tmpfs Virtue Desk Rabbit <me@example.com> - 2016-01-22 09:47 +0000
                Re: Linux Tmpfs Virtue Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-01-22 14:11 +0100
                Re: Linux Tmpfs Virtue Slimer <.m@nsn.s> - 2016-01-22 12:59 -0500
                Re: Linux Tmpfs Virtue Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-01-22 22:33 +0100
                Re: Linux Tmpfs Virtue GreyCloud <mist@cumulus.com> - 2016-01-22 15:22 -0700
                Re: Linux Tmpfs Virtue Slimer <.m@nsn.s> - 2016-01-23 09:34 -0500
                Re: Linux Tmpfs Virtue chrisv <chrisv@nospam.invalid> - 2016-01-25 07:19 -0600
                Re: Linux Tmpfs Virtue DFS <nospam@dfs.com> - 2016-01-25 08:59 -0500
                Re: Linux Tmpfs Virtue "Ezekiel" <zeke@nosuchemail.com> - 2016-01-25 10:22 -0500
                Re: Linux Tmpfs Virtue Desk Rabbit <me@example.com> - 2016-01-25 14:58 +0000
                Re: Linux Tmpfs Virtue "Ezekiel" <zeke@nosuchemail.com> - 2016-01-25 11:23 -0500
                Re: Linux Tmpfs Virtue Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-01-25 18:38 +0100
                Re: Linux Tmpfs Virtue Slimer <.m@nsn.s> - 2016-01-25 12:52 -0500
                Re: Linux Tmpfs Virtue "Ezekiel" <zeke@nosuchemail.com> - 2016-01-25 16:58 -0500
                Re: Linux Tmpfs Virtue Slimer <.m@nsn.s> - 2016-01-25 17:35 -0500
                Re: Linux Tmpfs Virtue owl <owl@rooftop.invalid> - 2016-01-26 18:39 +0000
                Re: Linux Tmpfs Virtue Snit <usenet@gallopinginsanity.com> - 2016-03-22 11:35 -0700
      Re: Linux Tmpfs Virtue DFS <nospam@dfs.com> - 2016-01-25 10:24 -0500
        Re: Linux Tmpfs Virtue Desk Rabbit <me@example.com> - 2016-01-25 15:36 +0000
          Re: Linux Tmpfs Virtue DFS <nospam@dfs.com> - 2016-01-25 11:18 -0500
            Re: Linux Tmpfs Virtue owl <owl@rooftop.invalid> - 2016-01-26 15:58 +0000
          Re: Linux Tmpfs Virtue owl <owl@rooftop.invalid> - 2016-01-26 17:16 +0000
        Re: Linux Tmpfs Virtue owl <owl@rooftop.invalid> - 2016-01-26 15:54 +0000
          Re: Linux Tmpfs Virtue DFS <nospam@dfs.com> - 2016-01-26 14:09 -0500
            Re: Linux Tmpfs Virtue owl <owl@rooftop.invalid> - 2016-01-26 21:16 +0000
              Re: Linux Tmpfs Virtue Slimer <a.m@unseen.is.invalid> - 2016-01-26 17:17 -0500
                Re: Linux Tmpfs Virtue owl <owl@rooftop.invalid> - 2016-01-26 23:20 +0000
                Re: Linux Tmpfs Virtue GreyCloud <mist@cumulus.com> - 2016-01-27 12:11 -0700
                Re: Linux Tmpfs Virtue owl <owl@rooftop.invalid> - 2016-01-27 21:26 +0000

csiph-web