Changeset dd13e76 for chapter02/creatingpartition.xml

Timestamp:

01/23/2005 07:09:54 AM (19 years ago)

Author:

Jim Gifford <jim@…>

Children:

c4ec9a5

Parents:

5668687

Message:

Added: Alpha arch

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/branches/multi-arch/BOOK@4551 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:

• chapter02/creatingpartition.xml (modified) (1 diff)

chapter02/creatingpartition.xml

@@ -66 +66 @@
 </itemizedlist>
 
+<para arch="alpha">Alphas have one of 2 BIOSes, Alphaboot or SRM. Some models have both
+and you can switch between them at powerup. Each bios has a different
+boot method. Milo is cool because it can be blown into flash for a
+FAST boot, but its built against an older linux kernel and crashes
+with some hardware, like a SCSI controller. aboot is simple if you
+can use it, but needs BSD partitions. aboot doesn't really let you do
+much at boot time that crosses devices. If you load aboot from hda,
+your root needs to be on hda. install aboot on hdb if you want to move
+your root to hdb. Once linux is loaded, you can do whatever you want.
+Milo can handle loading the kernel from one disk and the root on
+another.</para>
+
+<para arch="alpha">If you boot with SRM and aboot, you *MUST* use BSD style partitions.
+You *MUST* also leave the first 2 cylinders unused as they will
+contain your boot loader. I've read that partition 3 should always be
+the full disk even though it overlaps with other partitions, but in my
+experience that doesn't matter.  If you choose to not use an EXT2 or
+EXT3 root filesystem, you'll need to go through some extra hoops to
+install aboot.</para>
+
+<para arch="alpha">If you boot with Milo, use msdos partitions, and make the first
+partition large enough for at least 2 kernels (I would use about
+500Megs) and make it a FAT filesystem.</para>
+
 </sect1>