summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMike Frysinger <vapier@gentoo.org>2004-04-19 21:37:41 +0000
committerMike Frysinger <vapier@gentoo.org>2004-04-19 21:37:41 +0000
commitf995bd2c649e0f8f5ee977b091946c3da5f94b37 (patch)
tree5a3e84f7030652cf2db9dcc07da82cb823e41c67
parentmips manages this (diff)
downloadgentoo-2-f995bd2c649e0f8f5ee977b091946c3da5f94b37.tar.gz
gentoo-2-f995bd2c649e0f8f5ee977b091946c3da5f94b37.tar.bz2
gentoo-2-f995bd2c649e0f8f5ee977b091946c3da5f94b37.zip
alpha manages this
-rw-r--r--sys-boot/milo/metadata.xml11
1 files changed, 8 insertions, 3 deletions
diff --git a/sys-boot/milo/metadata.xml b/sys-boot/milo/metadata.xml
index 1f77966e45f9..1b91e77adc12 100644
--- a/sys-boot/milo/metadata.xml
+++ b/sys-boot/milo/metadata.xml
@@ -1,12 +1,17 @@
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
<pkgmetadata>
-<herd>no-herd</herd>
+<herd>alpha</herd>
<maintainer>
<email>taviso@gentoo.org</email>
- <name>Tavis Ormandy</name>
</maintainer>
<longdescription>
-On Intel based PC systems, the BIOS firmware sets up the system and then loads the image to be run from the boot block of a DOS file system. This is more or less what MILO does on an Alpha based system, however there are several interesting differences between BIOS firmware and MILO, not least of which is that MILO includes and uses standard Linux device drivers unmodified. MILO is firmware, unlike LILO, which relies on the BIOS firmware to get itself loaded.
+On Intel based PC systems, the BIOS firmware sets up the system and
+then loads the image to be run from the boot block of a DOS file
+system. This is more or less what MILO does on an Alpha based system,
+however there are several interesting differences between BIOS firmware
+and MILO, not least of which is that MILO includes and uses standard
+Linux device drivers unmodified. MILO is firmware, unlike LILO, which
+relies on the BIOS firmware to get itself loaded.
</longdescription>
</pkgmetadata>