Re: arches and etch

2006-12-18 Thread Tim Cutts
On 3 Nov 2006, at 5:30 pm, Steinar H. Gunderson wrote: On Fri, Nov 03, 2006 at 04:55:04PM +, Tim Cutts wrote: The 486 was the first CPU in the X86 family to have an integral FPU. Only the 486DX; the 486SX didn't. Being thoroughly pedantic, yes it did, but it was disabled in the hardw

Re: arches and etch

2006-11-03 Thread Steinar H. Gunderson
On Fri, Nov 03, 2006 at 04:55:04PM +, Tim Cutts wrote: > The 486 was the first CPU in the X86 family to have an integral FPU. Only the 486DX; the 486SX didn't. (Are we offtopic now? :-) ) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with

Re: arches and etch

2006-11-03 Thread Ron Johnson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/03/06 10:55, Tim Cutts wrote: > On 31 Oct 2006, at 3:07 am, Ron Johnson wrote: >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA1 >>> On 10/30/06 14:43, Bill Allombert wrote: On Sat, Oct 28, 2006 at 01:04:28PM +0100, Neil McGovern wrote:

Re: arches and etch

2006-11-03 Thread Tim Cutts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 31 Oct 2006, at 3:07 am, Ron Johnson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/30/06 14:43, Bill Allombert wrote: On Sat, Oct 28, 2006 at 01:04:28PM +0100, Neil McGovern wrote: [snip] Because we never had ? We have dropped

Re: arches and etch

2006-10-30 Thread Ron Johnson
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/30/06 14:43, Bill Allombert wrote: > On Sat, Oct 28, 2006 at 01:04:28PM +0100, Neil McGovern wrote: [snip] > Because we never had ? We have dropped support for i386, but only > a fraction of i386 had a MMU and so were able to run Linux, and this

Re: arches and etch

2006-10-30 Thread Hamish Moffatt
On Mon, Oct 30, 2006 at 08:43:06PM +, Bill Allombert wrote: > On Sat, Oct 28, 2006 at 01:04:28PM +0100, Neil McGovern wrote: > > So why aren't we sill shipping on 286 machines? > > Because we never had ? We have dropped support for i386, but only > a fraction of i386 had a MMU and so were abl

Re: arches and etch

2006-10-30 Thread Bill Allombert
On Sat, Oct 28, 2006 at 01:04:28PM +0100, Neil McGovern wrote: > > 7) Perhaps we should consider the balance between making debian just > >another glitzy quick-release plaything for mass consumption and > >minimal user contribution, and a system designed to give users who > >care and co

Re: arches and etch

2006-10-28 Thread Neil McGovern
On Sat, Oct 21, 2006 at 03:54:02PM -0400, Camm Maguire wrote: > Greetings, and thank you all so much for your usual fantastic work on > Debian! > > I just wanted to make a few observations about the recent decision to > scrap m68k from etch: > [snip reasons which are complaining about other arc

Re: arches and etch

2006-10-25 Thread Raphael Hertzog
On Tue, 24 Oct 2006, Reinhard Tartler wrote: > The only clean way to do this is IMO a dedicated upgrader tool. This > tool could then have special rules for the following issues: I don't know if we need such a tool, but it would be definitely helpful if we had a mechanism to give "hints" to aptitu

Re: arches and etch

2006-10-24 Thread Goswin von Brederlow
Petter Reinholdtsen <[EMAIL PROTECTED]> writes: > [Brian Morris] >> if there is a way to deal with all this i welcome suggestions, >> especially if it is amenable to automation. > > The default submission method for popularity-contest is now HTTP. It > might make it easier for your setup. Also,

Re: arches and etch

2006-10-24 Thread Petter Reinholdtsen
[Brian Morris] > if there is a way to deal with all this i welcome suggestions, > especially if it is amenable to automation. The default submission method for popularity-contest is now HTTP. It might make it easier for your setup. Also, it is possible for popcon submit its report somewhere else

Re: arches and etch

2006-10-24 Thread Brian Morris
although i have installed debian on 5 machines in the last two years and multiple times for testing on a couple of them, i don't think i have been counted on popcon and most likely never will be. the reasons, multiply: 3 of the five have never gone outside of local network, and in fact only rec

Re: arches and etch

2006-10-24 Thread Reinhard Tartler
Goswin von Brederlow <[EMAIL PROTECTED]> writes: > So to see a difference for the smaller archs the upgrade should > ask. The only clean way to do this is IMO a dedicated upgrader tool. This tool could then have special rules for the following issues: * known strange dependency changes like

Re: arches and etch

2006-10-23 Thread Riccardo
Hello, On Monday, October 23, 2006, at 06:46 PM, Goswin von Brederlow wrote: I doubt it will change noticably for the non mainstream architectures. Those that have their trusty old hardware running Debian for years and years now aren't the people that reinstall their system on every release.

Re: arches and etch

2006-10-23 Thread Goswin von Brederlow
Petter Reinholdtsen <[EMAIL PROTECTED]> writes: > One exciting thing with the next etch release is that the default > installer will ask if the machine should submit information to > popcon.debian.org. I look forward to see how that will affect the > number of machines submitting, as well as how

Re: arches and etch

2006-10-22 Thread Petter Reinholdtsen
[Camm Maguire] > I just wanted to make a few observations about the recent decision to > scrap m68k from etch: [several archs have problems at the moment] I guess this is as good opportunity as possible to report the current architecture distribution as collected by popularity-contest: 1 0

arches and etch

2006-10-21 Thread Camm Maguire
Greetings, and thank you all so much for your usual fantastic work on Debian! I just wanted to make a few observations about the recent decision to scrap m68k from etch: 1) The 4.x C compiler and hppa and apparently arm are currently much worse. 2) kernel and/or libc bugs preventing any prof