Re: Debian for x86-64 (AMD Opteron) and migration?
Ok, a bit late in this thread, but just a small remark on the future Opteron port : we have to take a *great* care of the migration process. The main difference betweek Intel-64 and AMD-64, if I am correct, is that administrators can unplug their ix86 disk from the server, and replug it on a opteron box, swicth the power button, and that's it. You'll get almost the same machine, and the you can start the upgrade process to 64-bit for all applications that needs them, and them finish the migration. This is a process that takes time (and for some servers that will take months or years) Therefore you can migrate smoothly machines from the 32-bit world to the 64-bit world witout having to do a painful migration from a 32-bit server to a full 64-bit one ; this is, IMHO, the greatest advantage of Opteron. Many people will not switch to Itanium for this reason: you have to break everything, including production application that sill are 32-bit. Then, a nice thing would be on Debian, for a regular user/administrator: - switch the disks to a Opteron box - update the APT sources to a Opteron source, or to a Opteron migration source - then, use something like : apt-get install base-64 to install the essential system files for 64-bit apt-get install libc6-64 .. essential libraries and elements for 64-bit code apt-get kernel-image..-64 64-bit kernel for Opteron I'm not sure that all remarks are wise, but I did not see this (migration) point clearly emerging from the Debian for x86-64 (AMD Opteron) previous discussion (My 2 euro cents remark)
Re: Debian for x86-64 (AMD Opteron) and migration?
Hi, On Mon, Jun 16, 2003 at 07:33:35AM +0200, Xavier Roche wrote: Then, a nice thing would be on Debian, for a regular user/administrator: - switch the disks to a Opteron box - update the APT sources to a Opteron source, or to a Opteron migration source - then, use something like : apt-get install base-64 to install the essential system files for 64-bit apt-get install libc6-64 .. essential libraries and elements for 64-bit code apt-get kernel-image..-64 64-bit kernel for Opteron I'm not sure that all remarks are wise, but I did not see this (migration) point clearly emerging from the Debian for x86-64 (AMD Opteron) previous discussion Well, to some extent is was mentioned in the subthread by Wichert about dpkg being changed to allow multiple architectures at the same time, so that it's a matter of # echo x86-64 /etc/dpkg/legal-archs or, if ordering matters, # echo x86-64 /etc/dpkg/legal-archs.new # cat /etc/dpkg/legal-archs /etc/dpkg/legal-archs.new # mv /etc/dpkg/legal-archs.new /etc/dpkg/legal-archs and suddenly an # apt-get install fvwm2 will fetch pool/main/f/fvwm/fvwm_2.4.6-2_x86-64.deb from the archive, and pull in packages such as lib64c6, lib64readline4, lib64gtk1.2. In this example, only one version (32 or 64 bit) of an application such as fvwm can exist on the system (package name is the same, only architecture field is different), whereas both libreadline4 and lib64readline4 can exist (package name is different too, and one installs its files in /usr/lib, the other in /usr/lib64 as per the AMD64 ABI). Of course, this may be different for other programs, which do require the '64' in the package name because some other program explicitly depends on a 64 bit version. But in general, this will only be true for libraries because they go in the same address space. Interfaces between programs and other programs will hopefully mostly be 64-bit clean. The biggest objection that was raised is that it will be necessary to make the source package for libreadline4 generate two packages, libreadline4 and lib64readline4. Same for all other libraries. IOW, there's no automatic way to create all these lib64* packages from source. Have I summarised this correctly? Cheers, Emile. -- E-Advies - Emile van Bergen [EMAIL PROTECTED] tel. +31 (0)70 3906153 http://www.e-advies.nl pgp7VIRUBBmvE.pgp Description: PGP signature
Re: Debian for x86-64 (AMD Opteron) and migration?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 16 June 2003 09:12, Emile van Bergen wrote: # echo x86-64 /etc/dpkg/legal-archs or, if ordering matters, # echo x86-64 /etc/dpkg/legal-archs.new # cat /etc/dpkg/legal-archs /etc/dpkg/legal-archs.new # mv /etc/dpkg/legal-archs.new /etc/dpkg/legal-archs AFAICS, ordering should not matter for dpkg, it will simply install any legal package when asked to. I have currently hardcoded the check for i386 packages into my amd64 dpkg... The biggest objection that was raised is that it will be necessary to make the source package for libreadline4 generate two packages, libreadline4 and lib64readline4. Same for all other libraries. IOW, there's no automatic way to create all these lib64* packages from source. Currently, we are using a set of patches from Gerhard Tonn to build libraries on amd64 and on s390x that minimize the necessary source changes. Unfortunately, there has been no word about it from any dpkg or debhelper maintainer. See Bug #197117 and http://people.debian.org/~gt/lib64/. Arnd -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+7eql5t5GS2LDRf4RAkwZAKCPAzwoeCHpDdBTFlZKlKvExqy3gwCbBzzW qS7btl9/G/tJeH7sNmVmaJg= =PV0Q -END PGP SIGNATURE-
