Handbook:MIPS/Blocks/Disks/ko

공간 분할
이론적으로는 리눅스 시스템을 전체 디스크에 넣을 수 있지만, 실제론 거의 불가능합니다. 대신 전체 블록 장치를 작게 나누어 더욱 관리하기 쉬운 블록 장치를 만들 수 있습니다. 이를 파티션이라고 부릅니다.

SGI 머신: SGI 디스크 레이블 만들기
All disks in an SGI System require an SGI Disk Label, which serves a similar function as Sun & MS-DOS disklabels -- It stores information about the disk partitions. Creating a new SGI Disk Label will create two special partitions on the disk:
 * SGI Volume Header (9th partition): This partition is important. It is where the bootloader will reside, and in some cases, it will also contain the kernel images.
 * SGI Volume (11th partition): This partition is similar in purpose to the Sun Disklabel's third partition of "Whole Disk". This partition spans the entire disk, and should be left untouched. It serves no special purpose other than to assist the PROM in some undocumented fashion (or it is used by IRIX in some way).

The following is an example excerpt from an fdisk session. Read and tailor it to personal preference...

전문가 모드로 전환하십시오:

을 눌러 전체 메뉴 옵션을 표시하십시오:

SGI 디스크 레이블을 만드십시오:

메인 메뉴로 돌아가십시오:

현재 파티션 배치를 살펴보십시오:

SGI 볼륨 헤더 크기 조절
Now that an SGI Disklabel is created, partitions may now be defined. In the above example, there are already two partitions defined. These are the special partitions mentioned above and should not normally be altered. However, for installing Gentoo, we'll need to load a bootloader, and possibly multiple kernel images (depending on system type) directly into the volume header. The volume header itself can hold up to eight images of any size, with each image allowed eight-character names.

The process of making the volume header larger isn't exactly straight-forward; there's a bit of a trick to it. One cannot simply delete and re-add the volume header due to odd fdisk behavior. In the example provided below, we'll create a 50MB Volume header in conjunction with a 50MB partition. The actual layout of a disk may vary, but this is for illustrative purposes only.

새 파티션을 만드십시오:

Notice how fdisk only allows Partition #1 to be re-created starting at a minimum of cylinder 5? If we attempted to delete & re-create the SGI Volume Header this way, this is the same issue we would have encountered. In our example, we want to be 50MB, so we start it at cylinder 51 (the Volume Header needs to start at cylinder 0, remember?), and set its ending cylinder to 101, which will roughly be 50MB (+/- 1-5MB).

파티션을 삭제하십시오:

이제 다시 만드십시오:

If unsure how to use fdisk have a look down further at the instructions for partitioning on Cobalts. The concepts are exactly the same -- just remember to leave the volume header and whole disk partitions alone.

이 과정을 끝내면 필요한만큼 나머지 파티션을 만듭니다. 나머지 모든 파티션을 배치하고나면 스왑 파티션의 파티션 ID를 리눅스 스왑 82번으로 설정했는지 확인하십시오. 기본적으로, 리눅스 네이티브 83번입니다.

Cobalt 드라이브 공간 분할
On Cobalt machines, the BOOTROM expects to see a MS-DOS MBR, so partitioning the drive is relatively straightforward -- in fact, it's done the same way as done for an Intel x86 machine. However there are some things you need to bear in mind.
 * Cobalt firmware will expect to be a Linux partition formatted EXT2 Revision 0. EXT2 Revision 1 partitions will NOT WORK! (The Cobalt BOOTROM only understands EXT2r0)
 * The above said partition must contain a gzipped ELF image, vmlinux.gz in the root of that partition, which it loads as the kernel

For that reason, it is recommended to create a ~20MB partition formatted EXT2r0 upon which to install CoLo & kernels. This allows the user to run a modern filesystem (EXT3 or ReiserFS) for the root filesystem.

In the example, it is assumed that is created to mount later as a  partition. To make this /, keep the PROM's expectations in mind.

So, continuing on... To create the partitions type  at the prompt. The main commands to know are these:

중요한 fdisk 명령 목록

기존 파티션을 지우는걸로 시작합니다:

명령으로 파티션 테이블을 비웠는지 확인하십시오:

/boot 파티션을 만드십시오:

파티션 내용을 표시할 때, 새로 만든 파티션을 확인하십시오:

이제 나머지 디스크 영역을 차지하는 확장 파티션을 만들겠습니다. 확장 파티션에서 나머지 파티션(논리 파티션)을 만들겠습니다:

이제, , 등의 파티션을 만들겠습니다.

필요한 만큼 반복하십시오.

마지막일지 모르겠지만 이걸로 끝이 아닌 스왑 영역입니다. 최소한 250MB의 스왑 공간이 필요하며 1GB 정도면 충분합니다:

파티션 테이블을 확인하면, 이미 확인했지만 모든 사항이 준비상태가 되어야합니다.

이제 #10 스왑 파티션이 여전히 83번 형식으로 되어 있지요? 적당한 형식으로 바꾸겠습니다.

이제 확인해보겠습니다:

새 파티션 테이블을 기록하겠습니다: