Bug#198158: architecture i386 isn't i386 anymore
On Sun, Jun 22, 2003 at 09:52:17AM +0200, Adam Borowski wrote:
> On Sat, 21 Jun 2003, John Goerzen wrote:
> > On Fri, Jun 20, 2003 at 03:28:02PM +0200, Adam Borowski wrote:
> > > Note that my idea was about patching the kernel that so the newer opcodes
> > > would be emulated in software. Everything would still work even on a 386,
> > > just slower -- and the speed decrease can be removed by running apt-build.
> > I don't see how that suggestion can possibly be taken seriously. Very few
> > i386 machines have the requisite disk space, memory, and swap space to build
> > large applications in Debian today.
> You do have a Pentium 17 10^38Mhz machine nearby, don't you? Apt-build
> doesn't even give the option of avoiding creation of .debs, and the bigger
> machine is one scp (or two mcopys in an extreme case) away.
Our operating system should not be wholly dependant on external factors
(other machines, Internet access, whatever) to run. To make it so makes it
virtually unusable in a number of situations.
In this particular case, no, there is not always another machine
network-reachable, as some of these sit outside the firewall. Not just
that, but forcing that removes most of the benefits of Debian (apt-get
dist-upgrade, etc) and we might as well just to back to Slackware from 1997.