Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I'm compiling mythtv that I got from https://github.com/MythTV/mythtv on a fedora 20 64 bit machine with 1Gb ram, 60Gb hard drive. The 'make install' command stops with "virtual memory exhausted: Cannot allocate memory". I've googled around but I can't see a solution to this problem. If I do # ulimit-a I get
Quote:
# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 7761
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 7761
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
I don't know what to do with these figures. I tried #ulimit -v 60000 but make install still gave the same error. I also tried #free -m
Agreed - cheap and simple.
Also looks like F20 assigns /tmp to tmpfs which would likely put more pressure on the RAM - maybe make /tmp disk-resident for the duration of the compile.
Mind you, a Gig is probably "minimal" these days for something like gnome or KDE.
A GB of memory should be enough... but not when using tmpfs (which takes up to half the physical memory by default). The problem is that the working files for the compiler are in /tmp... causing a double hit on memory.
A GB of memory should be enough... but not when using tmpfs (which takes up to half the physical memory by default). The problem is that the working files for the compiler are in /tmp... causing a double hit on memory.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
