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!
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.
Is there an advantage in the way a lot of standard Linux installation utilities split the root file-system and the home file-system on two separate but relatively equal-sized partitions?
For example, when I put fedora on an 80GB disk, it automatically gave the root file-system 32GB and home 30GB and the swap 8GB of space.
However, since my home file-system has a directory with 28GB of files in it, why is my root file-system reading 100% usage?
Is the home FS overlaid on top of the root FS?
Is there an advantage to doing this?
Traditionally, over the years I just made a boot partition (50mb or so), a root partition (90% of the disk space) and a swap (4%-5% disk space). I don't know whether my speculation makes you nauseous, but I think it may have to do with the way fragmentation accumulates over time or the number of redundant disk accesses are made... not sure...
(a) Because if you reinstall, you don't have to wipe out /home, only /.
(b) The 28GB in /home is unrelated to the space used in /
(c) Assuming they're separate mount points like you say, no, /home is not overlaid on /
Please post output of the following commands (use code tags):
The upgrade / backup considerations are key, but there are other good reasons.
By making the home folders their own partition you avoid having to use quotas to prevent a user from crashing the system by filling up disk space required for service operation, logging, etc.
My personal preference on servers is to have partitions for boot, root / , tmp, home, and var. If there is a primary data, application, or virtualization area then a partition for that. For a desktop this scheme is overkill, and the specific details depend upon what I am using the server for, what the risk factors are, and what my OS and hardware restrictions are.
The installation standards are there because they are a reasonable compromise for the average user who does not want to mess with custom partitioning and server tuning. The major developers for each distribution must make some reasonable guesses based upon their target market and the properties of the basic application load: I think that they generally do a pretty good job.
As you learn more and have more need to tune, you use the defaults less. If you do not NEED to tune your space, you use the defaults.
/dev/mapper/VolGroup-lv_root on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw,rootcontext="system_u:object_r:tmpfs_t:s0")
/dev/sda1 on /boot type ext4 (rw)
/dev/mapper/VolGroup-lv_home on /home type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
gvfs-fuse-daemon on /home/pneeko/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=pneeko)
du -skx /*
du: cannot access `/home/pneeko/.gvfs': Permission denied
du: cannot access `/proc/5744/task/5744/fd/4': No such file or directory
du: cannot access `/proc/5744/task/5744/fdinfo/4': No such file or directory
du: cannot access `/proc/5744/fd/4': No such file or directory
du: cannot access `/proc/5744/fdinfo/4': No such file or directory
If say for example I do a re-installation, and most of my files are in /home, and /home is already on its own partition, will disk druid know to install around it without having to back everything up?
Thanks for your replies, puts it into much better perspective for me.
All right, I was just going by this utility's report:
This is from a dedicated Linux installation (Not a VM). Earlier, I ran into a problem where I increased the size of the /home partition, and copied a big file into it, and I got an error saying that the root file-system was full.
I booted off a Gparted ISO to make the changes.
I was doing all the file operations in gnome using nautilus. Is that my problem? Should I go back and try it from the virtual console?
Both were fedora distros (versions 13 & 14).