This.
The var file is 223Mb
I specified 10Gb total for linux, isn that enough?
That should be enough, I guess. But as you see, a couple of movies takes more disk space than all your programs taken together.
BTW, you did a 'du -sh *' on your home directory. Ducky had asked that you first r files do a 'cd /', which takes you to the 'root directory', which is the top directory of your entire filesystem.
Let's first look at how Windows organizes it. When you open the Windows Explorer, you can click on an icon for drive "C". Then you get a window with the list of files and folders (=directories) in the top directory of drive C. One of them is "Program Files". If you click on that one, you get another window with the files and folders in that one: say, "Adobe", "Office", etc. In effect, the files on drive "C" are organized like a tree, where every branch in your tree is a folder, and a sub-branch of that a sub-folder. On the command-line, you separate all folder names by a backslash, like
Code:
> del "C:\Program Files\Adobe\Reader.exe"
Now, in Linux it mostly works the same, only the separator for the directory (=folder) names is a forward slash / instead of a backslash \. The top directory in Linux is '/'. If you look at it with, e.g.,
you'll see its contents are largely again directories named 'bin', 'home', 'var', etc. The directory 'home' contains on its turn a directory 'toke', which is the directory where your personal stuff resides. The full name of that directory toke is then
in which you can see the whole path from the top directory.
The second difference is that Windows keeps a separate tree for every drive or partition. That's why you see the "drive letters", in the above example C, at the start of filenames in Windows. Linux makes them into one big tree.
Suppose you wanted more disk space and you put a second disk into your machine. You partition that disk and you want to use its first partition to put all your own documents on. What you'd then do is first to "format" the partition:
This is the equivalent of "format" under Windows. It puts all necessary administration on the partition, like making an (empty) top directory. So far, no surprises. However, just doing a 'mkfs' doesn't make the files visible to Linux. But then comes the magic; the second command you'd do is
This now hangs the whole tree of directories and files on this second partition under the directory /home. So, when you want to play the movie with the name "/home/toke/Movies/mymovie.avi", Linux looks at that name and sees it starts with "/home", so it knows he should look on that new partition /dev/sdb1. There, he looks for a directory 'toke', and in that directory for the subdirectory 'Movies', and finally in that directory for a file named 'mymovie.avi'. Of course now, the contents of the directory '/home' on your original partition are invisible, so if you already had stuff there you'd have to mount the new partition elsewhere (e.g., under /mnt), move the stuff, then unmount the new partition and mount it again on the intended spot.
Most Linux installers nowadays offer to make one big partition for all Linux stuff. However, conventional wisdom among Linux/Unix specialists says to make several partitions; in particular to make separate partitions for:
/home: this is where the users' home directories go. You don't want a user taking up all your disk space (at least when you're administering a multi-user machine)
/var: this is where the logfiles go, and where all kinds of temporary files go, like the file you sent to the printer, or the emails you've just downloaded from your ISP, or the extra software packages you want to install.
/tmp: this is where the really temporary stuff goes. This directory gets cleaned between reboots (or at least, can get cleaned).
These three are the places most likely to have unexpected growth.
GodMark2 above mentioned the file /etc/fstab - that's where you write down which partitions should go where in the big tree of the Linux filesystem. It could look like this:
Code:
/dev/sda3 /
/dev/sda2 /usr
/dev/sda1 /var
/dev/sdb1 /home
/dev/sdb2 /tmp
/dev/hda /media/cdrom
and then on startup, Linux automatically makes those partitions visible in the big filesystem tree. Yes, when you look at the actual file you'll see it has a couple of more columns, which I've now left out. Actually, one of those columns says it shouldn't automatically try to mount your CD-ROM drive.
I have found a program called Gparted
The grafic indicate that linux is on /dev/sda3, which is divided into /dev/sda5
and /dev/sda6
they are 9.49Gb with 424.92Mb free, and 478.47Mb (swapfile)
Looks like I can change /dev/sda1 (partition_1) but not the others as I cant dismount them.
If you want more disk space for Linux, look at the
gparted live disk.Then you can boot off that live disk and it can change the size of all your partitions. It rocks. I bought a new laptop a month ago, with Vista on it, and Vista's own tool refused to resize its partition smaller than 100GB - although there was "only" 60GB installed on it. Gparted did the job
