As announced on the list (http://archives.gentoo.org/gentoo-doc/msg_e721be404c6a5ae8ce5c5bf02f45381c.xml), assume all arches are using the libata framework, so sd* everywhere. includes updating block device and partition descriptions. also added a new included file for boot config (starting sshd, hdparm, etc). synced up several wayward files, including sparc. also changed/dropped usage of some now useless keys, since everyone's using sd*. lots of intensive, invasive changes. and i never even used sed once.

uhh, looks like i backed up too many directories when i made that gnome/metadoc 2.22 commit, so the x86 and amd64 commits went in at the same time. that's okay though, as the filesizes for 2008.0_beta1 were fixed. so now here's the (missed) version bump for that change. :)

some edits for the gnome 2.22 upgrade guide as requested by leio. i hardly had to make any; those gnome guys are getting quite good at GuideXML, so kudos to them. :) also replaced the gnome 2.20 upgrade guide in our metadata.xml with the new guide.

release time. note that since this is beta1, the release dir and stage/media names have been adjusted accordingly. also, the handbooks are marked with a disclaimer=draft, so once the final is out, that will be removed and the release names adjusted. in the mean time, these are live. the beta is officially released. no, it's not april fools, but it is april 1st. :)

Fix typo; also move my own name on top of the author listing since users tend to mail the top author for questions/feedback and daniel just forwards them on to me anyway -- plus that Im the main author anyway ~ Daniel, Chris and Jerry are the authors of the previous installation instructions from which the handbook emerged

Okay, turning back to the "old" profile system. The thread on -dev@ doesn't give
me a good feeling about cascading profiles (pvdabeel sais that it needs some
updates, beejay sais it needs testing, solar sais the old one is obsoleted and
should be removed, zhen sais an updated catalyst needs to be pushed).
So this doesn't feel like "yes, switch them all over" just yet (especially since
this is a arch-wide part of our installation instructions).

#50773 - Use links2 only (to not confuse users too much)
I've mailed gentoo-releng and asked if there were any architectures that don't
have links2 (well, not exactly in those words, but arches that don't have it
should have replyed anyway). Only beejay answered and said all LiveCDs have
links2 ("at least x86 has") and none of the other arches replied.
So I'm not going to ask it over and over again. I'll just commit and watch the
bugs flow in :p They've had their chance.

We don't have to env-update && source /etc/profile after editing
/mnt/gentoo/etc/make.conf's CHOST setting as we aren't inside our chrooted
environment yet.
The command itself is ran anyway right after chrooting, so this can be removed
from the handbook. We had this previously when editing /etc/make.conf was inside
the chrooted environment.

The md5sum checking command in the handbooks is an example for the x86
architecture while the other architectures use the same file (i.e. others see
the same example). I made it prominent that this is merely an example.

The use of "he/she" and "his/her" isn't recommended. It's ugly and better ways
are known such as the use of "they" and "their" (even if it's not plural). Okay,
English is a weird language, but I'm learning :)
Thanks to Xavier for the information

Mental note: never listen to original authors when they suggest to change our
installation instructions. Apparently the use of "grub-install" for Gentoo just
doesn't work period. The forum is filled with people telling that it doesn't
work and I've got mails too. I've mailed the GRUB ppl about this. Anyway, this
reverts the instructions back to the old instructions -- translators can just
run "cvs update -j rev1 -j rev2 hb-install-x86-bootloader.xml" with rev1 and
rev2 the latest and one-before latest revision to revert their changes. Same for
hb-install-amd64-bootloader.xml. I did keep the links to the GRUB manual and FAQ
though so you'll have to readd it after reverting.

This form allows you to request diffs between any two revisions of this file.
For each of the two "sides" of the diff,
select a symbolic revision name using the selection box, or choose
'Use Text Field' and enter a numeric revision.