On Tuesday 24 November 2009 04:55:52 pm Jesse Keating wrote:
On Tue, 2009-11-24 at 16:48 -0500, Adam Jackson wrote:
> On Tue, 2009-11-24 at 13:50 -0600, Dennis Gilmore wrote:
> > syslinux would need to be able to detect the arch to install and likely
> > also have a flag to force 32 bit we could easily implement the 64 bit
> > kernel and 32 bit userland idea that was put forward a few releases
> > ago. pungi will need to learn how to make the new iso. but i think it
> > is achievable.
>
> As I'm actually trying this on one of the laptops on my desk, I'd point
> out that this almost certainly requires yum changes to work well. yum
> gets its idea of arch from uname, which reports what the kernel is, not
> what the current glibc is.
>
> Not that it's not a good idea - it seems to work surprisingly well - but
> it's not turnkey yet.
>
> - ajax
From what I understand, this isn't about delivering a 64bit kernel and a
32bit userland. That's a different ball of fun. This is about having
one single piece of media that can serve as either a 32bit install
media, or a 64bit install media, and which you get would depend on the
syslinux menu item you boot, which would be driven by what arch CPU you
have (or forced by the user). That shouldn't require any yum hackery at
all.
the goal for F-13 is to have unified media, for F-14 and beyond we could look
at other options like having a 64 bit kernel and 32 bit userland. i should
have stated that a bit more clearly
Dennis