New 16GB of RAM installed yet I see 15.3 on my system. Why?












6














Just switched 4GBs to 16GBs of RAM. However, when I look at how much memory I have, it says 15.3. I'm just wondering why did my memory drop down when I just installed 16 GBs of RAM.



system details screenshot










share|improve this question
























  • Possible duplicate of Why will Ubuntu no longer measure file size unit as byte, megabyte, gigabyte, etc?
    – dadexix86
    Mar 8 '16 at 23:04






  • 1




    This is not a duplicate of that question. RAM size is reported in base 2 by both manufacturers and Ubuntu. The difference is due to something else.
    – TheSchwa
    Mar 8 '16 at 23:57










  • The other forum does not answer my question as to why I went from 16GB to 15.3. It's not about the changes of the file, I just want to know what happened to the rest of my memory? Is it something that Linux does. Take up a portion, or something in that matter.
    – Geri Sati
    Mar 9 '16 at 0:09










  • That screen show 15.6 for me. But free in terminal shows 16308044 . Is video excluded in one and not other?
    – oldfred
    Mar 9 '16 at 0:32










  • If you claim that all sizes are on base 2, please use a consistent notation. See man units for a convenient reference. To add to the confusion, also note in your screenshot that GiB is used for memory, and GB for disk space
    – XavierStuvw
    Jun 8 '17 at 17:57


















6














Just switched 4GBs to 16GBs of RAM. However, when I look at how much memory I have, it says 15.3. I'm just wondering why did my memory drop down when I just installed 16 GBs of RAM.



system details screenshot










share|improve this question
























  • Possible duplicate of Why will Ubuntu no longer measure file size unit as byte, megabyte, gigabyte, etc?
    – dadexix86
    Mar 8 '16 at 23:04






  • 1




    This is not a duplicate of that question. RAM size is reported in base 2 by both manufacturers and Ubuntu. The difference is due to something else.
    – TheSchwa
    Mar 8 '16 at 23:57










  • The other forum does not answer my question as to why I went from 16GB to 15.3. It's not about the changes of the file, I just want to know what happened to the rest of my memory? Is it something that Linux does. Take up a portion, or something in that matter.
    – Geri Sati
    Mar 9 '16 at 0:09










  • That screen show 15.6 for me. But free in terminal shows 16308044 . Is video excluded in one and not other?
    – oldfred
    Mar 9 '16 at 0:32










  • If you claim that all sizes are on base 2, please use a consistent notation. See man units for a convenient reference. To add to the confusion, also note in your screenshot that GiB is used for memory, and GB for disk space
    – XavierStuvw
    Jun 8 '17 at 17:57
















6












6








6


2





Just switched 4GBs to 16GBs of RAM. However, when I look at how much memory I have, it says 15.3. I'm just wondering why did my memory drop down when I just installed 16 GBs of RAM.



system details screenshot










share|improve this question















Just switched 4GBs to 16GBs of RAM. However, when I look at how much memory I have, it says 15.3. I'm just wondering why did my memory drop down when I just installed 16 GBs of RAM.



system details screenshot







ram






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jun 8 '17 at 13:29









Melebius

4,38251838




4,38251838










asked Mar 8 '16 at 23:00









Geri Sati

435




435












  • Possible duplicate of Why will Ubuntu no longer measure file size unit as byte, megabyte, gigabyte, etc?
    – dadexix86
    Mar 8 '16 at 23:04






  • 1




    This is not a duplicate of that question. RAM size is reported in base 2 by both manufacturers and Ubuntu. The difference is due to something else.
    – TheSchwa
    Mar 8 '16 at 23:57










  • The other forum does not answer my question as to why I went from 16GB to 15.3. It's not about the changes of the file, I just want to know what happened to the rest of my memory? Is it something that Linux does. Take up a portion, or something in that matter.
    – Geri Sati
    Mar 9 '16 at 0:09










  • That screen show 15.6 for me. But free in terminal shows 16308044 . Is video excluded in one and not other?
    – oldfred
    Mar 9 '16 at 0:32










  • If you claim that all sizes are on base 2, please use a consistent notation. See man units for a convenient reference. To add to the confusion, also note in your screenshot that GiB is used for memory, and GB for disk space
    – XavierStuvw
    Jun 8 '17 at 17:57




















  • Possible duplicate of Why will Ubuntu no longer measure file size unit as byte, megabyte, gigabyte, etc?
    – dadexix86
    Mar 8 '16 at 23:04






  • 1




    This is not a duplicate of that question. RAM size is reported in base 2 by both manufacturers and Ubuntu. The difference is due to something else.
    – TheSchwa
    Mar 8 '16 at 23:57










  • The other forum does not answer my question as to why I went from 16GB to 15.3. It's not about the changes of the file, I just want to know what happened to the rest of my memory? Is it something that Linux does. Take up a portion, or something in that matter.
    – Geri Sati
    Mar 9 '16 at 0:09










  • That screen show 15.6 for me. But free in terminal shows 16308044 . Is video excluded in one and not other?
    – oldfred
    Mar 9 '16 at 0:32










  • If you claim that all sizes are on base 2, please use a consistent notation. See man units for a convenient reference. To add to the confusion, also note in your screenshot that GiB is used for memory, and GB for disk space
    – XavierStuvw
    Jun 8 '17 at 17:57


















Possible duplicate of Why will Ubuntu no longer measure file size unit as byte, megabyte, gigabyte, etc?
– dadexix86
Mar 8 '16 at 23:04




Possible duplicate of Why will Ubuntu no longer measure file size unit as byte, megabyte, gigabyte, etc?
– dadexix86
Mar 8 '16 at 23:04




1




1




This is not a duplicate of that question. RAM size is reported in base 2 by both manufacturers and Ubuntu. The difference is due to something else.
– TheSchwa
Mar 8 '16 at 23:57




This is not a duplicate of that question. RAM size is reported in base 2 by both manufacturers and Ubuntu. The difference is due to something else.
– TheSchwa
Mar 8 '16 at 23:57












The other forum does not answer my question as to why I went from 16GB to 15.3. It's not about the changes of the file, I just want to know what happened to the rest of my memory? Is it something that Linux does. Take up a portion, or something in that matter.
– Geri Sati
Mar 9 '16 at 0:09




The other forum does not answer my question as to why I went from 16GB to 15.3. It's not about the changes of the file, I just want to know what happened to the rest of my memory? Is it something that Linux does. Take up a portion, or something in that matter.
– Geri Sati
Mar 9 '16 at 0:09












That screen show 15.6 for me. But free in terminal shows 16308044 . Is video excluded in one and not other?
– oldfred
Mar 9 '16 at 0:32




That screen show 15.6 for me. But free in terminal shows 16308044 . Is video excluded in one and not other?
– oldfred
Mar 9 '16 at 0:32












If you claim that all sizes are on base 2, please use a consistent notation. See man units for a convenient reference. To add to the confusion, also note in your screenshot that GiB is used for memory, and GB for disk space
– XavierStuvw
Jun 8 '17 at 17:57






If you claim that all sizes are on base 2, please use a consistent notation. See man units for a convenient reference. To add to the confusion, also note in your screenshot that GiB is used for memory, and GB for disk space
– XavierStuvw
Jun 8 '17 at 17:57












1 Answer
1






active

oldest

votes


















13














Short Answer



It's probably just the kernel using memory. Instead of reporting kernel memory usage, Ubuntu instead subtracts form the total available. This is simply to let you know that the kernel memory cannot be freed in most cases. That memory is being used for things that are absolutely necessary, and so it will never be available.



Diagnostic Commands



I don't expect you to run all of these, but I've included them here for reference and completeness. Most relevant are commands 3 and 4. Also please note that all sizes are going to be in base 2 (e.g. GiB) and not in base 10 (e.g. GB) despite what the unit abbreviations might be.





  1. You can check how big your RAM sticks are claiming to be with:



    sudo dmidecode | grep Size | grep MB



  2. You can check how much RAM is available for general use with (look for Mem and total):



    free -h



  3. You can estimate how much memory the kernel is using with:



    cat /proc/meminfo | grep Slab



  4. You can check for "stolen" graphics card memory with:



    dmesg | grep stolen



  5. You can look for specific hardware reserved memory by looking through:



    dmesg | grep e820


  6. You can test to make certain all of your memory works by running memtest



Explanation



The most likely explanation is simply that the extra space is being used by either your graphics card or the kernel itself. If you're not familiar, the kernel is the lowest-level part of the operating system, and any memory that it's using will not be available to you and so is not reported as free. The memory might be used for any number of reasons, such as the virtual memory tables, memory-mapped I/O, kernel processes, certain caches, shared graphics memory, etc.



Example: Looking at My Laptop



It is very likely that adding the output of command 3 to your 15.3GiB will result in almost exactly 16GiB. This was the case in my system:




  • Installed RAM: 6GiB

  • Reported in System Settings > Details: 5.6GiB

  • Output of cat /proc/meminfo | grep Slab: 316652 kB

  • Converted to GiB: 316652/2^20 = 0.3GiB

  • Output of dmesg | grep stolen: 32768K

  • Converted to GiB: 32768/2^20 = 0.03GiB

  • Adding them together: 5.6 + 0.3 + 0.03 = 5.93GiB


Since the Slab memory is not comprehensive, we can assume that the kernel is using the remaining 0.07GiB in places we can't see, and so this is a very satisfying result.



See Also




  • How much RAM does the kernel use? (Unix & Linux)

  • Reducing reserved RAM (Arch forums)

  • Why is some RAM marked as hardware reserved in Windows 7? (Superuser)

  • Why does my system show 3.2GiB of RAM? (Unix & Linux)

  • Ubuntu units policy (Ubuntu wiki)






share|improve this answer



















  • 1




    Kernel slab memory is counted as part of "used memory" and does not reduce the "total" memory. You can see that quite easily by checking the system when it has a lot of slab in use, and again when it is little.
    – psusi
    Jun 8 '17 at 13:40






  • 1




    cat | grep is a useless use of cat: grep itself accepts filenames as parameters.
    – Ruslan
    Jun 8 '17 at 16:44










  • @Ruslan Lol, thanks. I still haven't trained myself out of that one. Albeit it's less "correct" in some sense, I still like it for readability and it flows better with the other commands in the post.
    – TheSchwa
    Jun 8 '17 at 19:00













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f743649%2fnew-16gb-of-ram-installed-yet-i-see-15-3-on-my-system-why%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









13














Short Answer



It's probably just the kernel using memory. Instead of reporting kernel memory usage, Ubuntu instead subtracts form the total available. This is simply to let you know that the kernel memory cannot be freed in most cases. That memory is being used for things that are absolutely necessary, and so it will never be available.



Diagnostic Commands



I don't expect you to run all of these, but I've included them here for reference and completeness. Most relevant are commands 3 and 4. Also please note that all sizes are going to be in base 2 (e.g. GiB) and not in base 10 (e.g. GB) despite what the unit abbreviations might be.





  1. You can check how big your RAM sticks are claiming to be with:



    sudo dmidecode | grep Size | grep MB



  2. You can check how much RAM is available for general use with (look for Mem and total):



    free -h



  3. You can estimate how much memory the kernel is using with:



    cat /proc/meminfo | grep Slab



  4. You can check for "stolen" graphics card memory with:



    dmesg | grep stolen



  5. You can look for specific hardware reserved memory by looking through:



    dmesg | grep e820


  6. You can test to make certain all of your memory works by running memtest



Explanation



The most likely explanation is simply that the extra space is being used by either your graphics card or the kernel itself. If you're not familiar, the kernel is the lowest-level part of the operating system, and any memory that it's using will not be available to you and so is not reported as free. The memory might be used for any number of reasons, such as the virtual memory tables, memory-mapped I/O, kernel processes, certain caches, shared graphics memory, etc.



Example: Looking at My Laptop



It is very likely that adding the output of command 3 to your 15.3GiB will result in almost exactly 16GiB. This was the case in my system:




  • Installed RAM: 6GiB

  • Reported in System Settings > Details: 5.6GiB

  • Output of cat /proc/meminfo | grep Slab: 316652 kB

  • Converted to GiB: 316652/2^20 = 0.3GiB

  • Output of dmesg | grep stolen: 32768K

  • Converted to GiB: 32768/2^20 = 0.03GiB

  • Adding them together: 5.6 + 0.3 + 0.03 = 5.93GiB


Since the Slab memory is not comprehensive, we can assume that the kernel is using the remaining 0.07GiB in places we can't see, and so this is a very satisfying result.



See Also




  • How much RAM does the kernel use? (Unix & Linux)

  • Reducing reserved RAM (Arch forums)

  • Why is some RAM marked as hardware reserved in Windows 7? (Superuser)

  • Why does my system show 3.2GiB of RAM? (Unix & Linux)

  • Ubuntu units policy (Ubuntu wiki)






share|improve this answer



















  • 1




    Kernel slab memory is counted as part of "used memory" and does not reduce the "total" memory. You can see that quite easily by checking the system when it has a lot of slab in use, and again when it is little.
    – psusi
    Jun 8 '17 at 13:40






  • 1




    cat | grep is a useless use of cat: grep itself accepts filenames as parameters.
    – Ruslan
    Jun 8 '17 at 16:44










  • @Ruslan Lol, thanks. I still haven't trained myself out of that one. Albeit it's less "correct" in some sense, I still like it for readability and it flows better with the other commands in the post.
    – TheSchwa
    Jun 8 '17 at 19:00


















13














Short Answer



It's probably just the kernel using memory. Instead of reporting kernel memory usage, Ubuntu instead subtracts form the total available. This is simply to let you know that the kernel memory cannot be freed in most cases. That memory is being used for things that are absolutely necessary, and so it will never be available.



Diagnostic Commands



I don't expect you to run all of these, but I've included them here for reference and completeness. Most relevant are commands 3 and 4. Also please note that all sizes are going to be in base 2 (e.g. GiB) and not in base 10 (e.g. GB) despite what the unit abbreviations might be.





  1. You can check how big your RAM sticks are claiming to be with:



    sudo dmidecode | grep Size | grep MB



  2. You can check how much RAM is available for general use with (look for Mem and total):



    free -h



  3. You can estimate how much memory the kernel is using with:



    cat /proc/meminfo | grep Slab



  4. You can check for "stolen" graphics card memory with:



    dmesg | grep stolen



  5. You can look for specific hardware reserved memory by looking through:



    dmesg | grep e820


  6. You can test to make certain all of your memory works by running memtest



Explanation



The most likely explanation is simply that the extra space is being used by either your graphics card or the kernel itself. If you're not familiar, the kernel is the lowest-level part of the operating system, and any memory that it's using will not be available to you and so is not reported as free. The memory might be used for any number of reasons, such as the virtual memory tables, memory-mapped I/O, kernel processes, certain caches, shared graphics memory, etc.



Example: Looking at My Laptop



It is very likely that adding the output of command 3 to your 15.3GiB will result in almost exactly 16GiB. This was the case in my system:




  • Installed RAM: 6GiB

  • Reported in System Settings > Details: 5.6GiB

  • Output of cat /proc/meminfo | grep Slab: 316652 kB

  • Converted to GiB: 316652/2^20 = 0.3GiB

  • Output of dmesg | grep stolen: 32768K

  • Converted to GiB: 32768/2^20 = 0.03GiB

  • Adding them together: 5.6 + 0.3 + 0.03 = 5.93GiB


Since the Slab memory is not comprehensive, we can assume that the kernel is using the remaining 0.07GiB in places we can't see, and so this is a very satisfying result.



See Also




  • How much RAM does the kernel use? (Unix & Linux)

  • Reducing reserved RAM (Arch forums)

  • Why is some RAM marked as hardware reserved in Windows 7? (Superuser)

  • Why does my system show 3.2GiB of RAM? (Unix & Linux)

  • Ubuntu units policy (Ubuntu wiki)






share|improve this answer



















  • 1




    Kernel slab memory is counted as part of "used memory" and does not reduce the "total" memory. You can see that quite easily by checking the system when it has a lot of slab in use, and again when it is little.
    – psusi
    Jun 8 '17 at 13:40






  • 1




    cat | grep is a useless use of cat: grep itself accepts filenames as parameters.
    – Ruslan
    Jun 8 '17 at 16:44










  • @Ruslan Lol, thanks. I still haven't trained myself out of that one. Albeit it's less "correct" in some sense, I still like it for readability and it flows better with the other commands in the post.
    – TheSchwa
    Jun 8 '17 at 19:00
















13












13








13






Short Answer



It's probably just the kernel using memory. Instead of reporting kernel memory usage, Ubuntu instead subtracts form the total available. This is simply to let you know that the kernel memory cannot be freed in most cases. That memory is being used for things that are absolutely necessary, and so it will never be available.



Diagnostic Commands



I don't expect you to run all of these, but I've included them here for reference and completeness. Most relevant are commands 3 and 4. Also please note that all sizes are going to be in base 2 (e.g. GiB) and not in base 10 (e.g. GB) despite what the unit abbreviations might be.





  1. You can check how big your RAM sticks are claiming to be with:



    sudo dmidecode | grep Size | grep MB



  2. You can check how much RAM is available for general use with (look for Mem and total):



    free -h



  3. You can estimate how much memory the kernel is using with:



    cat /proc/meminfo | grep Slab



  4. You can check for "stolen" graphics card memory with:



    dmesg | grep stolen



  5. You can look for specific hardware reserved memory by looking through:



    dmesg | grep e820


  6. You can test to make certain all of your memory works by running memtest



Explanation



The most likely explanation is simply that the extra space is being used by either your graphics card or the kernel itself. If you're not familiar, the kernel is the lowest-level part of the operating system, and any memory that it's using will not be available to you and so is not reported as free. The memory might be used for any number of reasons, such as the virtual memory tables, memory-mapped I/O, kernel processes, certain caches, shared graphics memory, etc.



Example: Looking at My Laptop



It is very likely that adding the output of command 3 to your 15.3GiB will result in almost exactly 16GiB. This was the case in my system:




  • Installed RAM: 6GiB

  • Reported in System Settings > Details: 5.6GiB

  • Output of cat /proc/meminfo | grep Slab: 316652 kB

  • Converted to GiB: 316652/2^20 = 0.3GiB

  • Output of dmesg | grep stolen: 32768K

  • Converted to GiB: 32768/2^20 = 0.03GiB

  • Adding them together: 5.6 + 0.3 + 0.03 = 5.93GiB


Since the Slab memory is not comprehensive, we can assume that the kernel is using the remaining 0.07GiB in places we can't see, and so this is a very satisfying result.



See Also




  • How much RAM does the kernel use? (Unix & Linux)

  • Reducing reserved RAM (Arch forums)

  • Why is some RAM marked as hardware reserved in Windows 7? (Superuser)

  • Why does my system show 3.2GiB of RAM? (Unix & Linux)

  • Ubuntu units policy (Ubuntu wiki)






share|improve this answer














Short Answer



It's probably just the kernel using memory. Instead of reporting kernel memory usage, Ubuntu instead subtracts form the total available. This is simply to let you know that the kernel memory cannot be freed in most cases. That memory is being used for things that are absolutely necessary, and so it will never be available.



Diagnostic Commands



I don't expect you to run all of these, but I've included them here for reference and completeness. Most relevant are commands 3 and 4. Also please note that all sizes are going to be in base 2 (e.g. GiB) and not in base 10 (e.g. GB) despite what the unit abbreviations might be.





  1. You can check how big your RAM sticks are claiming to be with:



    sudo dmidecode | grep Size | grep MB



  2. You can check how much RAM is available for general use with (look for Mem and total):



    free -h



  3. You can estimate how much memory the kernel is using with:



    cat /proc/meminfo | grep Slab



  4. You can check for "stolen" graphics card memory with:



    dmesg | grep stolen



  5. You can look for specific hardware reserved memory by looking through:



    dmesg | grep e820


  6. You can test to make certain all of your memory works by running memtest



Explanation



The most likely explanation is simply that the extra space is being used by either your graphics card or the kernel itself. If you're not familiar, the kernel is the lowest-level part of the operating system, and any memory that it's using will not be available to you and so is not reported as free. The memory might be used for any number of reasons, such as the virtual memory tables, memory-mapped I/O, kernel processes, certain caches, shared graphics memory, etc.



Example: Looking at My Laptop



It is very likely that adding the output of command 3 to your 15.3GiB will result in almost exactly 16GiB. This was the case in my system:




  • Installed RAM: 6GiB

  • Reported in System Settings > Details: 5.6GiB

  • Output of cat /proc/meminfo | grep Slab: 316652 kB

  • Converted to GiB: 316652/2^20 = 0.3GiB

  • Output of dmesg | grep stolen: 32768K

  • Converted to GiB: 32768/2^20 = 0.03GiB

  • Adding them together: 5.6 + 0.3 + 0.03 = 5.93GiB


Since the Slab memory is not comprehensive, we can assume that the kernel is using the remaining 0.07GiB in places we can't see, and so this is a very satisfying result.



See Also




  • How much RAM does the kernel use? (Unix & Linux)

  • Reducing reserved RAM (Arch forums)

  • Why is some RAM marked as hardware reserved in Windows 7? (Superuser)

  • Why does my system show 3.2GiB of RAM? (Unix & Linux)

  • Ubuntu units policy (Ubuntu wiki)







share|improve this answer














share|improve this answer



share|improve this answer








edited Apr 13 '17 at 12:37









Community

1




1










answered Mar 9 '16 at 0:53









TheSchwa

3,12711735




3,12711735








  • 1




    Kernel slab memory is counted as part of "used memory" and does not reduce the "total" memory. You can see that quite easily by checking the system when it has a lot of slab in use, and again when it is little.
    – psusi
    Jun 8 '17 at 13:40






  • 1




    cat | grep is a useless use of cat: grep itself accepts filenames as parameters.
    – Ruslan
    Jun 8 '17 at 16:44










  • @Ruslan Lol, thanks. I still haven't trained myself out of that one. Albeit it's less "correct" in some sense, I still like it for readability and it flows better with the other commands in the post.
    – TheSchwa
    Jun 8 '17 at 19:00
















  • 1




    Kernel slab memory is counted as part of "used memory" and does not reduce the "total" memory. You can see that quite easily by checking the system when it has a lot of slab in use, and again when it is little.
    – psusi
    Jun 8 '17 at 13:40






  • 1




    cat | grep is a useless use of cat: grep itself accepts filenames as parameters.
    – Ruslan
    Jun 8 '17 at 16:44










  • @Ruslan Lol, thanks. I still haven't trained myself out of that one. Albeit it's less "correct" in some sense, I still like it for readability and it flows better with the other commands in the post.
    – TheSchwa
    Jun 8 '17 at 19:00










1




1




Kernel slab memory is counted as part of "used memory" and does not reduce the "total" memory. You can see that quite easily by checking the system when it has a lot of slab in use, and again when it is little.
– psusi
Jun 8 '17 at 13:40




Kernel slab memory is counted as part of "used memory" and does not reduce the "total" memory. You can see that quite easily by checking the system when it has a lot of slab in use, and again when it is little.
– psusi
Jun 8 '17 at 13:40




1




1




cat | grep is a useless use of cat: grep itself accepts filenames as parameters.
– Ruslan
Jun 8 '17 at 16:44




cat | grep is a useless use of cat: grep itself accepts filenames as parameters.
– Ruslan
Jun 8 '17 at 16:44












@Ruslan Lol, thanks. I still haven't trained myself out of that one. Albeit it's less "correct" in some sense, I still like it for readability and it flows better with the other commands in the post.
– TheSchwa
Jun 8 '17 at 19:00






@Ruslan Lol, thanks. I still haven't trained myself out of that one. Albeit it's less "correct" in some sense, I still like it for readability and it flows better with the other commands in the post.
– TheSchwa
Jun 8 '17 at 19:00




















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f743649%2fnew-16gb-of-ram-installed-yet-i-see-15-3-on-my-system-why%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

How did Captain America manage to do this?

迪纳利

南乌拉尔铁路局