Slashdot Mirror

← Back to Stories (view on slashdot.org)

Debian Votes on AMD64 in Sarge

Posted by michael on from the vote-the-party-line dept.

JayBonci writes "According to a message sent to debian-vote, there is now a GR on the table as to whether or not to include AMD64 into the upcoming sarge release, even though it violates part of the LSB (Linux Standards Base). The debian-vote list has more discussion on it. Does this best meet the needs of the users?"

7 of 55 comments (clear)

  1. Re:If LSB can't support AMD64... by Cecil · · Score: 5, Informative

    No, IA32 machines will give way to AMD64 machines. IA64 died with Itanium.

    Additionally, LSB 2.0 sets out specifications for AMD64 ports. However, it is still in public review, and is not the current standard. This is a problem for Debian, which has (up until now) always gone out of their way to do things "by the book".

    --
    Random and weird software I've written.
  2. What is the Violation? by Neon+Spiral+Injector · · Score: 4, Insightful

    I'm guessing the violation of the LSB deals with the default system libs. Where does Debian put the 64-bit libs? Where does the LSB say to put them?

    I think the LSB says to put them in /lib64, which I find totally broken. Sure it allows for a 64-bit install to be built on top of an already existing 32-bit install. But what about when 128-bit processors come out? Will we have a /lib, /lib64, and /lib128? How about when there is no longer need for 32-bit support? The /lib directory would be deprecated, so the /lib64 would exist alone?

    What should have been done is on 64-bit distros which wish to offer 32-bit backward compatiblity, the default 64-bit libs should be in /lib and the compatibility libs should have been moved to /lib32. The dynamic linker shouldn't have any problem figuring out what libs are needed, and load the right ones.

    So what road did Debian take? If they have the default system libs in /lib, hear's to them, forget the LSB, it is broken.

    1. Re:What is the Violation? by Sesse · · Score: 4, Interesting

      The solution that probably will be taken, after sarge, is multiarch; forget /usr/lib32 and /usr/lib64, think /usr/i486-linux/lib and /usr/x64_64-linux/lib. Solves the problem of both two and more (remember, the IA64 can both emulate IA32 and stuff like HPPA, for instance) architectures, but requires some work that most people probably won't let delay sarge.

      /* Steinar */

      --
      (This comment is of course GPLed.)
    2. Re:What is the Violation? by Stephen+Williams · · Score: 4, Interesting

      I think the LSB says to put them in /lib64, which I find totally broken. Sure it allows for a 64-bit install to be built on top of an already existing 32-bit install.

      I agree, it's hideous, for all the reasons you state. I'd go as far as saying that I don't think that "upgrading" an IA-32 installation to an AMD64 installation should even be supported. Backwards compatibility aside, they're separate architectures, and should thus require reinstallation. It's a small amount of short-term pain to avoid masses of legacy cruft building up afterwards.

      What should have been done is on 64-bit distros which wish to offer 32-bit backward compatiblity, the default 64-bit libs should be in /lib and the compatibility libs should have been moved to /lib32.

      Absolutely Right(tm). The 64-bit distro is in charge, so it gets dibs on /lib. 32-bit legacy compatibility is just that -- legacy compatibility, and can fit in wherever. Maybe not even /lib32; perhaps demote it to /usr/lib32: no legacy binaries should be required to bring the system up, especially before /usr has been mounted.

      I'm also pleased that Debian has decided to call the architecture "amd64". "x86-64" looks and sounds ugly, IMHO.

      -Stephen

  3. Re:Outdated already. by MarsDefenseMinister · · Score: 5, Funny

    I'll get it sponsored, if Chris won't do it.

    But first, I've got to ask a couple questions: how do I become a Debian developer? And what is Debian? And finally, what is Linux? Thanks.

    --
    No weapon in the arsenals of the world is so formidable as the will and moral courage of free men.-Ronald Reagan
  4. Re:What's wrong with the LSB? by Jahf · · Score: 4, Informative

    Yes and no.

    Yes, the AMD64 chips can run 32bit code even when the kernel is 64bit. But to run an app in 64bit mode you must have 64bit compiled libraries.

    Example ... 64bit kernel wants to run 32bit XFree86 binaries ... it must use 32bit versions of all the Xfree libraries. On the other hand, 64bit kernel wants to run 64bit Xfree86 binaries ... the XFree libraries must be compiled for 64bit usage.

    Therefore you have to have 64bit libraries and 32bit libraries. You can't run a 32bit application with the 64bit libraries and you most definitely can't run 64bit applications with 32bit libraries.

    The 64bit kernel in all the above cases would still be a 64bit kernel, but there are app dependencies.

    --
    It is more productive to voice thoughtful opinions (reply) than to judge (moderate) others.
  5. Re:Choose Debian!!! by magnum3065 · · Score: 4, Insightful

    Well, you're just looking at what's public. Most distros the debate is going to be kept within the company. So, you could look at the debates over Debian as a bad thing, or you could realize that this is just indicative of the fact that the community gets more say in the direction of their distribution.