From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1GxrsT-0003qT-B4 for garchives@archives.gentoo.org; Fri, 22 Dec 2006 21:24:29 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id kBMLLEea010358; Fri, 22 Dec 2006 21:21:14 GMT Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by robin.gentoo.org (8.13.8/8.13.8) with ESMTP id kBMLLDm1012470 for ; Fri, 22 Dec 2006 21:21:14 GMT Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Gxrp3-0005WC-HC for gentoo-amd64@lists.gentoo.org; Fri, 22 Dec 2006 22:20:58 +0100 Received: from ip68-231-13-122.ph.ph.cox.net ([68.231.13.122]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 22 Dec 2006 22:20:57 +0100 Received: from 1i5t5.duncan by ip68-231-13-122.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 22 Dec 2006 22:20:57 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-amd64@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-amd64] Re: Emerging package as both 64 and 32 bit Date: Fri, 22 Dec 2006 21:20:41 +0000 (UTC) Message-ID: References: <458B82F1.2080908@gentoo.org> <200612220854.59448.bss03@volumehost.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-13-122.ph.ph.cox.net User-Agent: pan 0.120 (Plate of Shrimp) Sender: news X-Archives-Salt: 83a2ad35-fca8-49eb-a395-cac5f836db19 X-Archives-Hash: 25ff8347dc315206333a1979e9223598 "Boyd Stephen Smith Jr." posted 200612220854.59448.bss03@volumehost.net, excerpted below, on Fri, 22 Dec 2006 08:54:59 -0600: > Also, it's technically possible for the bootloader to switch into extended > mode before loading the kernel, but not done (in GRUB, at least) for solid > technical reasons. (IIRC, there's some memory mappings that have to be > set up before entering extended mode.) That's something I've actually always wondered, so it's interesting to see a bit on it. Is there anything not /too/ technical* but somewhat more detailed you could point me to? *I'm not a C/C++/ASM coder, but understand the terminology well enough to find many LKML discussions interesting, for instance, and I'd say I follow about half of the LWN kernel page articles, enough to have found myself recently correcting (I think/hope) some inaccuracies in a Linux.com article by Joe Barr, for instance, see the article and comments following here, my comment should be obvious, given its length : http://enterprise.linux.com/article.pl?sid=06/12/14/1910259 -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- gentoo-amd64@gentoo.org mailing list