Re: x32: a success story, and thanks to you all!
On Fri, Sep 05, 2014 at 11:25:43PM +0100, Ben Hutchings wrote: On Fri, 2014-09-05 at 17:29 +0100, Colin Watson wrote: On Fri, Sep 05, 2014 at 04:43:01PM +0100, Ben Hutchings wrote: No, they should add amd64 as a foreign architecture. Should we do this by default for x32 in d-i? (Yes, I know d-i doesn't support x32 in other ways yet, but we might as well get started at some point.) Yes I think so. Committed to apt-setup. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140906145928.ga10...@riva.ucam.org
x32: a success story, and thanks to you all!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA384 Hi everyone, some might have noticed that, once the Debian Linux Kernel Maintainers activated x32 support in the standard Debian kernels, I cross-graded my machine at work to it. I would like to say thanks to the various maintainers involved in this: • Aurélien for debian-ports, as before with m68k • Daniel for agreeing I could help • the dpkg maintainers for making this possible • the apt maintainers for making it, while not always pain-free, surprisingly well-working (e.g. I had to $ sudo apt-get --purge dist-upgrade libkolabxml1:i386- to upgrade kdepim, but then, being conservative and keeping packages in the arch they are installed for is probably better than overzealously installing them) • Michael Vogt especially for adding the above syntax to apt-get ☺ • various package maintainers and upstreams for quickly adding Multi-Arch annotations (e.g. gettext) or patches to their packages or actively working on it (I just noticed nss/nspr will soon work; I still need them for :i386 too) I’m very impressed with both that cross-grading works well and that running an only partially cross-graded M-A system works amazingly well, modulo the ability to run dselect. And it all works without systemd, even ;-) Thanks to you all! There are a few missing things. klibc builds for amd64 on x32, which I will probably fix myself as it needs porting (upstream is happy about me doing it); grub needs porting (or needs to build for amd64 or i386 on x32) which I may have a look at later; various multimedia stuff needs touching or at least disabling asm code (Daniel looks at it, and I will do so too), and we need src:linux to build linux-image-3.14-2-amd64:x32 so people can run a non-M-A x32 installation eventually (once the bootloader issue is sorted out, but I imagine LOADLIN.EXE would also work), and until then, gcc-4.8:i386 needs to work with binutils:x32 instead of requiring binutils:i386 (which I worked around by hand-editing /var/lib/dpkg/status, yes I know, bad me). But I’ve not heard of anything or anybody that actively stands in the way of the x32 port progressing, now. I just wanted to write a pure-positive port once in a while, and express my gratitude to my fellow Debian Developers. Sending from my work eMail because I consider all my work on the x32 port, even if much is done in my spare time, also a contribution by tarent who are letting me “play around” a bit as long as I get my tasks done (and enjoy the synergy effects). Please consider following up in private to keep the mailing list noise down, unless you feel your response is something you want to share with hundreds or thousands of subscribers. bye, //mirabilos - -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: ☃ ЦΤℱ—８ ☕☂☄ iQIcBAEBCQAGBQJUCZW1AAoJEIlQwYleuNOz0+wP/1cvJq1vAcACK68KJEODTwb5 6A8NEcDo+XV82EkVOhot9RitKXhHz41g1i4eWoSdvU9C6nXPbrtlZoUuxe5fR6td UuV7zzvRGyEbg7GvWBusDVjFqGKMwLNrpwL/guk25V33ZP2UDvJPA9vCHvSFV9YZ tgw+TZFyqcr5M/t8BsgM62Dj4+Z34sDV0jymGU79T9dXChFgvfawXQM6Vy7BFCnD bOceFbq69oyHn5PL9ho+ku0uxwf2fz6lzfkIrcspNnBnuNNslUDUN4zttnAw4O94 3em7UBy0KNhdsgkf/YghTsP6SSkICkRhQDOwM+54tYdT6pYx5nSAhtiEgN1wE+Y+ 4WWUWAF0R+nFNAdSEJOVRsDbRnYptiFFYgJ95bZJbj9Lvr2xWlSQZuXs0QzzOtZW ssx6I18Eyauy9odVVHqjz92xCbXswnRdjo6vOXD46vyvyFR7JT9pI/gigENj/P0S /UDuBqWN7QpMPiIlnpy2TwvDXJcX7+922bEHr46dkxJw/KdJf/2wLlog/Yry/94J t6IXxeR1kcq75/37xNEFIDrt6hY6FA5mlSxhsbIOoLRfOCEw4LQTsamT8LnJCnPL UaeiGCTxC68NeNBr0ppcuXOYB4/+X7Cg+F1QlEKzFKMXRiuZ+y5UVH/fHl1g9vp8 +pr2UQFmIw9jNJsGzUjl =GVDf -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/alpine.deb.2.11.1409051240500.31...@tglase.lan.tarent.de
Re: x32: a success story, and thanks to you all!
On Fri, Sep 05, 2014 at 12:51:41PM +0200, Thorsten Glaser wrote: grub needs porting (or needs to build for amd64 or i386 on x32) which I may have a look at later; Hopefully not difficult: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760428 -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140905124046.ga12...@riva.ucam.org
Re: x32: a success story, and thanks to you all!
On Fri, 2014-09-05 at 12:51 +0200, Thorsten Glaser wrote: [...] There are a few missing things. klibc builds for amd64 on x32, which I will probably fix myself as it needs porting (upstream is happy about me doing it); grub needs porting (or needs to build for amd64 or i386 on x32) which I may have a look at later; various multimedia stuff needs touching or at least disabling asm code (Daniel looks at it, and I will do so too), and we need src:linux to build linux-image-3.14-2-amd64:x32 so people can run a non-M-A x32 installation eventually [...] No, they should add amd64 as a foreign architecture. The wrong- architecture kernel packages are a workaround from pre-multi-arch days that I don't wish to extend. Several things are still broken in kernel support; at least: - Many ioctls https://lkml.org/lkml/2014/8/13/618 - Syscall auditing https://lkml.org/lkml/2014/5/28/789 Ben. -- Ben Hutchings Experience is directly proportional to the value of equipment destroyed. - Carolyn Scheppner signature.asc Description: This is a digitally signed message part
Re: x32: a success story, and thanks to you all!
On Fri, Sep 05, 2014 at 04:43:01PM +0100, Ben Hutchings wrote: No, they should add amd64 as a foreign architecture. Should we do this by default for x32 in d-i? (Yes, I know d-i doesn't support x32 in other ways yet, but we might as well get started at some point.) -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140905162941.ga18...@riva.ucam.org
Re: x32: a success story, and thanks to you all!
On Fri, Sep 05, 2014 at 05:29:41PM +0100, Colin Watson wrote: On Fri, Sep 05, 2014 at 04:43:01PM +0100, Ben Hutchings wrote: No, they should add amd64 as a foreign architecture. Should we do this by default for x32 in d-i? (Yes, I know d-i doesn't support x32 in other ways yet, but we might as well get started at some point.) x32 has the following major use cases: * vserver hosting * underpowered netbooks * get-any-last-percent-of-speed number crunching At least the first two prefer a small installed size, which means a pure system without two sets of binaries. -- // If you believe in so-called intellectual property, please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable and Non-Discriminatory prices. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140905181427.gb25...@angband.pl
Re: x32: a success story, and thanks to you all!
On Fri, Sep 05, 2014 at 08:14:27PM +0200, Adam Borowski wrote: On Fri, Sep 05, 2014 at 05:29:41PM +0100, Colin Watson wrote: On Fri, Sep 05, 2014 at 04:43:01PM +0100, Ben Hutchings wrote: No, they should add amd64 as a foreign architecture. Should we do this by default for x32 in d-i? (Yes, I know d-i doesn't support x32 in other ways yet, but we might as well get started at some point.) x32 has the following major use cases: * vserver hosting * underpowered netbooks * get-any-last-percent-of-speed number crunching At least the first two prefer a small installed size, which means a pure system without two sets of binaries. There's no reason why adding amd64 as a foreign architecture means two sets of binaries. If you don't want foreign-arch packages, don't install them. Adding the architecture just makes them available without messing around. This is especially important if installing the kernel is going to require multiarch, as Ben said upthread. -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140905192301.ga24...@riva.ucam.org
Re: x32: a success story, and thanks to you all!
On Fri, 2014-09-05 at 17:29 +0100, Colin Watson wrote: On Fri, Sep 05, 2014 at 04:43:01PM +0100, Ben Hutchings wrote: No, they should add amd64 as a foreign architecture. Should we do this by default for x32 in d-i? (Yes, I know d-i doesn't support x32 in other ways yet, but we might as well get started at some point.) Yes I think so. Ben. -- Ben Hutchings Experience is directly proportional to the value of equipment destroyed. - Carolyn Scheppner signature.asc Description: This is a digitally signed message part
