Debian 3.0r6 Released
Polkan Garcia writes "The Debian group has released an update to the 'Woody' distribution of the popular GNU/Linux OS. From the site: 'This is the sixth and final update of Debian GNU/Linux 3.0 (codename 'woody') which mainly adds security updates to the stable release, along with a few corrections to serious problems. Those who frequently update from security.debian.org won't have to update many packages and most updates from security.debian.org are included in this update.' More good news: r6 is the final update of woody, the new stable release is coming."
On another note, I get the Debian bit and I know what linux is, but what's this GNU prefix ?
MP3 Search Engine
Sure in theory we should all contribute before criticizing. However this is not practical. Want to criticise MS, go work for them. You hate SCO, go work for them too. BSD not what you want, go fix it. In my opinion it is OK to criticize something that you aren't a part of, as long as you make reasonable points.
Philosophy.
As much heat as Woody gets from the Slashdot crowd, I think it is a good idea to have a stable release that doesn't update very quickly. Keep in mind that, as "old" as Debian is, it was released in 2002. It is no older than Windows XP (2001-2002 release) and is a good deal younger than Windows 2000 (1999 release). One of the servers I have an account on is a RedHat 7.2 machine, which is of the same era as the first Woody release. While I develop on Fedora Core three, I make sure my software compiles as is on a RedHat 6.2 system (2000 era).
For servers and corporate desktops, an update every three years is a frequent update. I am glad that Debian has been current with security updates on this three-year-old release; I would rather have that than the updgrade treadmill Fedora has me on. (The Fedora Legacy project seems to be comatose) In fact, I'm going off of the treadmill--my next Linux will be CentOS (a no-cost generic clone of Red Hat Enterprise Linux) which will allow me to have sane updates--once a year or two instead of once every six months.
That sounds good, but I hope that they're not just succumbing to deadline pressure and shoving this thing out the door half baked.
I thought that apt-get had was unable to handle multiple architectures on a single system, which prevented a fully integrated 64 & 32 bit version of Debian. Has that problem with apt-get been solved yet?
Yes and no. The "biarch" system has been working for several years to support both 32 and 64 bit Sparc software. That same technology could be used now to support mixed 32/64-bit code for AMD64 processors, but Debian developers have opted not to do that. Instead, the new multiarch system will support an arbitrary number of architectures, very flexibly. That will not only address the AMD64 issue but it will also make handling of other x86 subarchitectures easier.
Currently, there are some Debian packages that come in multiple flavors because they benefit significantly from processor-specific optimizations. The kernel, for example, comes compiled for 386, 586, 686, K6, K7, amd64-generic, amd64-k8 and em64t, plus SMP versions of most of those. Mplayer also comes in multiple versions, though not as many. This is handled by having a big list of kernel-image and mplayer packages. With multiarch, you'll be able to specify that you have, say, an AMD64 processor, and then apt-get will understand which subarchitectures will and will not run on your system, and which subarchitectures are preferred. Then you can just pick generic packages and the system will install the best version. It will also handle situations like mozilla and flashplayer. If you install mozilla on an AMD64 box, you should probably get a 64-bit version for best performance. However, if you want flash to work, you have to install the Macromedia plugin and it's 32-bit, so you have to install a 32-bit version of mozilla so that it can use the 32-bit plugin. The new multiarch system will handle all of those dependencies for you.
So apt-get is perfectly capable of handling a mixed 32 and 64-bit system now, but only if the package maintainers set things up carefully (which is what most other distros must do). Debian has opted to forego such a "manual" solution and instead wait until the elegant and flexible general solution is done.
Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.