On Thu, Feb 12, 2009 at 11:20:18AM +0100, Alexander De Sousa wrote:
Ok, here are my reports:
Tests: As for other images + manual network configuration. Machines: As for other images (VirtualBox machines, VMware machines, real machines).
Images tested (SHA-1 sums verified):
archlinux-2009.02-RC2-core-i686.iso 16A77C07C252A21379D057DEB5D6F4D75039B946 archlinux-2009.02-RC2-core-x86_64.iso C730DC90FEF25EAA6BDD0A5431BCBB5935B3B613 archlinux-2009.02-RC2-ftp-i686.iso 6ABA5F14B6BAC9E8DD7962EE4544D8F5FBFCA7C5 archlinux-2009.02-RC2-ftp-i686-isolinux.iso 763971A32554ADA562906707BC70E3C5DD45814F archlinux-2009.02-RC2-ftp-x86_64.iso 3C7D8697AC1CAB71FC23B0060B726EB6CFF67050 archlinux-2009.02-RC2-ftp-x84_64-isolinux.iso 2135A6AEAEE9C359A9D523660BDA767CADACA152
Bugs:
http://bugs.archlinux.org/task/12896 : Couldn't test, it's for USB images. http://bugs.archlinux.org/task/12949 : Corrected, it was also corrected in RC1 by the way. (disc capacity) http://bugs.archlinux.org/task/13038 : Corrected. (vc/n typo) http://bugs.archlinux.org/task/13057 : "Corrected" as grub-gfx is up to date with patches. (grub-install from outside the installed system) http://bugs.archlinux.org/task/13068 : Corrected "long" ago. (updated grub-gfx for x86_64) http://bugs.archlinux.org/task/13070 : Corrected, it was also corrected in RC1 by the way. (grub-gfx installed instead of grub) http://bugs.archlinux.org/task/13101 : Corrected. (timezone not written in rc.conf) http://bugs.archlinux.org/task/13102 : Corrected, /etc/localtime does exist and no "last mount time is in the future message". () http://bugs.archlinux.org/task/13140 : "Corrected" I guess, it looks good to me; though I've never used it. (documentation)
http://bugs.archlinux.org/task/13237 : This one is new:
If you choose to configure network manually (by entering IP, net mask, broadcast IP, ...) and then you choose to use that settings in the installed system, the setup script may not update correctly the broadcast IP and even give an invalid one. This happens when use any IP with at least one of the bytes different from the default one (e.g. 192.168.8.2, which would give an incorrect broadcast IP) or with more than 8 digits (e.g. 192.168.0.27, would give an invalid broadcast IP). I attach a patch to the setup script to solve it.
See also http://bugs.archlinux.org/task/13192 -- Greg what to do and what not to do in public :o) http://linux.sgms-centre.com/misc/netiquette.php