diff options
Diffstat (limited to 'sys-boot/milo/metadata.xml')
| -rw-r--r-- | sys-boot/milo/metadata.xml | 23 |
1 files changed, 10 insertions, 13 deletions
diff --git a/sys-boot/milo/metadata.xml b/sys-boot/milo/metadata.xml index 1b91e77adc12..1b9d222defaf 100644 --- a/sys-boot/milo/metadata.xml +++ b/sys-boot/milo/metadata.xml @@ -1,17 +1,14 @@ <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd"> <pkgmetadata> -<herd>alpha</herd> -<maintainer> - <email>taviso@gentoo.org</email> -</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. -</longdescription> + <herd>alpha</herd> + <longdescription lang="en"> + 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> |