最近想学LIUNX，想安装Red Hat Enterprise Liunx5,在书上看说最好自定义分区，但看不懂，不知怎么分，
多谢各位前辈指点了
文章评论
共有 8 条评论
gtsshao 于 2009-06-19 09:00:17发表:
引用:
OpenBSD上介绍分区的一段：
After a little thought, we decide to create just enough partitions to allow the creation of the recommended separate filesystems
(/, /tmp, /var, /usr, /home) along with a s ...
774964107 发表于 2009-6-18 18:57
OpenBSD上介绍分区的一段：
After a little thought, we decide to create just enough partitions to allow the creation of the recommended separate filesystems
(/, /tmp, /var, /usr, /home) along with a swap partition:
Keep the following facts in mind, however:
These are minimum values. Disk space is relatively cheap now, trying to squeeze your system into the smallest possible
q
disk is rarely worth the effort. For special purpose applications, the above numbers can be made smaller, but you will need
to experiment with it.
These numbers do NOT include the ports tree.
q
If you plan to install a significant amount of third party software, make your /usr partition much larger. How large will
q
depend on your applications, of course.
For a system that handles lots of email or web pages (stored, respectively, in /var/mail and /var/www) you will want
q
to make your /var partition significantly larger, or put them on separate partitions.
For a multiuser system which may generate lots of logs, you will want to make your /var partition significantly larger
q
still, or create a separate log partition (/var/log).
If you plan to rebuild the kernel and system from source, you will want to make the /usr partition significantly larger, 4G
q
is not a bad size.
Compiling some ports from source can take huge amounts of space on your /usr and /tmp partitions. This is another
q
reason we suggest using pre-compiled packages instead.
The /tmp partition is used in the compiling of ports, among other things, so how big you make it depends on what you do
q
with it. 50M may be plenty for most people, but some large applications may require 100M or more of /tmp space.
The 'b' partition of your root drive automatically becomes your system swap partition. Many people follow an old rule of
q
thumb that your swap partition should be twice the size of your main system RAM. This rule is nonsense. On a modern
system, that's a LOT of swap, most people prefer that their systems never swap. You don't want your system to ever run out
of RAM+swap, but you usually would rather have enough RAM in the system so it doesn't need to swap. If you are using a
flash device for disk, you probably want no swap partition at all. Use what is appropriate for your needs. If you guess
wrong, you can add another swap partition in /etc/fstab or swap to a file later.
Swap and /var spaces are used to store system core dumps on in the event of a crash(8). If this is a consideration for you,
q
your swap space should be slightly larger than the amount of main memory you are likely to ever have in the system. Upon
reboot, savecore(8) will attempt to save the contents of the swap partition to a file in /var/crash so again, if this is a
priority for you, your /var partition must have enough free space to hold these dump files. Be realistic -- few developers
will want to look at your 1GB dump file, so if you aren't planning on investigating a crash locally, this is probably not a
concern.
At least some editors use /var/tmp for scratch space, and this often needs to be as big or bigger than the largest file you
q
edit. If you plan on editing 500M files, your /var or /var/tmp partition will need to be much larger than you might
have planned on.
There are several reasons for using separate filesystems, instead of shoving everything into one or two filesystems:
Security: You can mark some filesystems as 'nosuid', 'nodev', 'noexec', 'readonly', etc. This is done by the install process, if
q
you use the above described partitions.
Stability: A user, or a misbehaved program, can fill a filesystem with garbage if they have write permissions for it. Your
q
critical programs, which of course run on a different filesystem, do not get interrupted.
Speed: A filesystem which gets written to frequently may get somewhat fragmented. (Luckily, the ffs filesystem that
q
OpenBSD uses is not prone to heavy fragmentation.)
Integrity: If one filesystem is corrupted for some reason then your other filesystems are still OK.
q
Size: Many machines have limits on the area of a disk where the boot ROM can load the kernel from. In some cases, this
q
gtsshao 于 2009-06-19 09:00:17发表:
多谢军长,俺英文水平不好.会不会对学这个有影响.
gtsshao 于 2009-06-19 08:59:02发表:
谢谢,
用的是两个500G硬盘,准备安装RHEL5用作Mail Server用,这种分区模式目前搞不懂
请教一下:
physical volume(LVM)
Vfat
这两个代表什么?
774964107 于 2009-06-18 18:57:25发表:
OpenBSD上介绍分区的一段：
After a little thought, we decide to create just enough partitions to allow the creation of the recommended separate filesystems
(/, /tmp, /var, /usr, /home) along with a swap partition:
Keep the following facts in mind, however:
These are minimum values. Disk space is relatively cheap now, trying to squeeze your system into the smallest possible
q
disk is rarely worth the effort. For special purpose applications, the above numbers can be made smaller, but you will need
to experiment with it.
These numbers do NOT include the ports tree.
q
If you plan to install a significant amount of third party software, make your /usr partition much larger. How large will
q
depend on your applications, of course.
For a system that handles lots of email or web pages (stored, respectively, in /var/mail and /var/www) you will want
q
to make your /var partition significantly larger, or put them on separate partitions.
For a multiuser system which may generate lots of logs, you will want to make your /var partition significantly larger
q
still, or create a separate log partition (/var/log).
If you plan to rebuild the kernel and system from source, you will want to make the /usr partition significantly larger, 4G
q
is not a bad size.
Compiling some ports from source can take huge amounts of space on your /usr and /tmp partitions. This is another
q
reason we suggest using pre-compiled packages instead.
The /tmp partition is used in the compiling of ports, among other things, so how big you make it depends on what you do
q
with it. 50M may be plenty for most people, but some large applications may require 100M or more of /tmp space.
The 'b' partition of your root drive automatically becomes your system swap partition. Many people follow an old rule of
q
thumb that your swap partition should be twice the size of your main system RAM. This rule is nonsense. On a modern
system, that's a LOT of swap, most people prefer that their systems never swap. You don't want your system to ever run out
of RAM+swap, but you usually would rather have enough RAM in the system so it doesn't need to swap. If you are using a
flash device for disk, you probably want no swap partition at all. Use what is appropriate for your needs. If you guess
wrong, you can add another swap partition in /etc/fstab or swap to a file later.
Swap and /var spaces are used to store system core dumps on in the event of a crash(8). If this is a consideration for you,
q
your swap space should be slightly larger than the amount of main memory you are likely to ever have in the system. Upon
reboot, savecore(8) will attempt to save the contents of the swap partition to a file in /var/crash so again, if this is a
priority for you, your /var partition must have enough free space to hold these dump files. Be realistic -- few developers
will want to look at your 1GB dump file, so if you aren't planning on investigating a crash locally, this is probably not a
concern.
At least some editors use /var/tmp for scratch space, and this often needs to be as big or bigger than the largest file you
q
edit. If you plan on editing 500M files, your /var or /var/tmp partition will need to be much larger than you might
have planned on.
There are several reasons for using separate filesystems, instead of shoving everything into one or two filesystems:
Security: You can mark some filesystems as 'nosuid', 'nodev', 'noexec', 'readonly', etc. This is done by the install process, if
q
you use the above described partitions.
Stability: A user, or a misbehaved program, can fill a filesystem with garbage if they have write permissions for it. Your
q
critical programs, which of course run on a different filesystem, do not get interrupted.
Speed: A filesystem which gets written to frequently may get somewhat fragmented. (Luckily, the ffs filesystem that
q
OpenBSD uses is not prone to heavy fragmentation.)
Integrity: If one filesystem is corrupted for some reason then your other filesystems are still OK.
q
Size: Many machines have limits on the area of a disk where the boot ROM can load the kernel from. In some cases, this
q
刘冲 于 2009-06-18 17:09:08发表:
[i=s] 本帖最后由 刘冲 于 2009-6-18 17:10 编辑 [/i]
直接一个swap一个根目录就行了。看你硬盘大小了。
跟分区16G足够你完全安装rhel的，再根据实际情况分个swap，剩下的全分给/home目录。
我自己都是全部给根目录，因为我还有windows的。home都不要，只是分出个500M左右给/tmp，其实个人来言也没有什么用，就是个人爱好。
刘冲 于 2009-06-18 17:07:04发表:
不用做到最好，只是学习，就达不到让分区限制你什么的地步gtsshao 于 2009-06-18 16:31:44发表:
[i=s] 本帖最后由 gtsshao 于 2009-6-18 16:34 编辑 [/i]
多谢多谢，先试看看，能不能再详细点，还有我想建一个分区，用于存放档案资料，怎么分，资料夹名称可以自己名命吗？我在名命一个DATA的资料夹时出现一堆英文，分不了，
S5000 于 2009-06-18 16:12:26发表:
可以先用魔术分区工具在WIN系统中分，那个图形界面运行看就清楚了
S5000 于 2009-06-18 16:12:01发表:
/
swap
/boot
其它的可分可不分