Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #226765

Re: 32 versus 64 bit reading list suggestions

From Andrew Cater <amacater@gmail.com>
Newsgroups linux.debian.user
Subject Re: 32 versus 64 bit reading list suggestions
Date 2020-09-07 22:10 +0200
Message-ID <AMvCF-22L-1@gated-at.bofh.it> (permalink)
References (3 earlier) <AMr62-7Ia-7@gated-at.bofh.it> <AMrfH-7Lg-5@gated-at.bofh.it> <AMtAS-B9-3@gated-at.bofh.it> <AMuZX-1zr-1@gated-at.bofh.it> <AMvsZ-1Kh-13@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

32 bit Intel/AMD will likely disappear from the kernel if it becomes too
hard to support. I've just had a quick look at the Fit-PC site - all of
them look to be 64 bit capable. You want something low power - 64 bit ARM?
There does come a point when 32 bit x86 really isn't viable - that's round
about now in my humble estimation, if it wasn't actually two years ago.
Crucially, the boost library is hard to build - Firefox is built on 64 bit
to work on 32 bit - and those are the obvious ones. If you want the
distributions to spend time building on 64 bit for you to run on 32 bit
hardware which is significantly old you do need to show a demonstrable need
and perhaps find sponsors for a toolchain and permanent build at this point.

On Mon, Sep 7, 2020 at 7:52 PM deloptes <deloptes@gmail.com> wrote:

> Charles Curley wrote:
>
> > I hope so. All I need is console capabilities, security software
> > (firewall, etc.) and server software. I don't need an office suite or web
> > browser for those machines.
>
> Same here. So it means we have 2-4years to get ready.
> I guess one needs a bit more in order to compile the code ... you need at
> least the compiler and companions. I now compile only the kernel in chroot
> as it was pointed out because debian moved away from pure 586 and also
> there is a kind of magic combination of features for the Geode board I use,
> so that the stock kernel never worked past 2.13.
>
> So the question is (as we are already on the topic) when debian drops the
> support, what would be required to build the code.
> Are compilers going to stop supporting 386 arch?
> Is it going to disappear from the kernel completely?
> Is it going to get fixes and how?
>
>
>
>
>
>

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

32 versus 64 bit reading list suggestions Richard Owlett <rowlett@cloud85.net> - 2020-09-07 15:50 +0200
  Re: 32 versus 64 bit reading list suggestions Reco <recoverym4n@enotuniq.net> - 2020-09-07 16:20 +0200
    Re: 32 versus 64 bit reading list suggestions David Wright <deblis@lionunicorn.co.uk> - 2020-09-07 16:50 +0200
    Re: 32 versus 64 bit reading list suggestions Richard Owlett <rowlett@cloud85.net> - 2020-09-07 17:10 +0200
      Re: 32 versus 64 bit reading list suggestions Reco <recoverym4n@enotuniq.net> - 2020-09-07 17:20 +0200
        Re: 32 versus 64 bit reading list suggestions Richard Owlett <rowlett@cloud85.net> - 2020-09-07 17:50 +0200
  Re: 32 versus 64 bit reading list suggestions Jonathan Dowland <jon+debian-user@dow.land> - 2020-09-07 16:30 +0200
    Re: 32 versus 64 bit reading list suggestions Richard Owlett <rowlett@cloud85.net> - 2020-09-07 17:20 +0200
      Re: 32 versus 64 bit reading list suggestions Andrew Cater <amacater@gmail.com> - 2020-09-07 17:30 +0200
        Re: 32 versus 64 bit reading list suggestions deloptes <deloptes@gmail.com> - 2020-09-07 20:00 +0200
          Re: 32 versus 64 bit reading list suggestions Andrew Cater <amacater@gmail.com> - 2020-09-07 20:10 +0200
            Re: 32 versus 64 bit reading list suggestions deloptes <deloptes@gmail.com> - 2020-09-07 20:30 +0200
          Re: 32 versus 64 bit reading list suggestions Charles Curley <charlescurley@charlescurley.com> - 2020-09-07 21:30 +0200
            Re: 32 versus 64 bit reading list suggestions deloptes <deloptes@gmail.com> - 2020-09-07 22:00 +0200
              Re: 32 versus 64 bit reading list suggestions Andrew Cater <amacater@gmail.com> - 2020-09-07 22:10 +0200
                Re: 32 versus 64 bit reading list suggestions deloptes <deloptes@gmail.com> - 2020-09-08 07:50 +0200
                Re: 32 versus 64 bit reading list suggestions Michael Stone <mstone@debian.org> - 2020-09-08 14:30 +0200
                Re: 32 versus 64 bit reading list suggestions deloptes <deloptes@gmail.com> - 2020-09-08 19:30 +0200
                Re: 32 versus 64 bit reading list suggestions Michael Stone <mstone@debian.org> - 2020-09-08 21:30 +0200
                Re: 32 versus 64 bit reading list suggestions deloptes <deloptes@gmail.com> - 2020-09-08 22:00 +0200
                Re: 32 versus 64 bit reading list suggestions Charles Curley <charlescurley@charlescurley.com> - 2020-09-08 17:20 +0200
                Re: 32 versus 64 bit reading list suggestions deloptes <deloptes@gmail.com> - 2020-09-08 19:40 +0200
                Re: 32 versus 64 bit reading list suggestions Richard Hector <richard@walnut.gen.nz> - 2020-09-09 07:50 +0200
                Re: 32 versus 64 bit reading list suggestions John Hasler <jhasler@newsguy.com> - 2020-09-09 14:20 +0200
                Re: 32 versus 64 bit reading list suggestions deloptes <deloptes@gmail.com> - 2020-09-09 14:30 +0200
                Re: 32 versus 64 bit reading list suggestions John Hasler <jhasler@newsguy.com> - 2020-09-09 14:50 +0200
                Re: 32 versus 64 bit reading list suggestions deloptes <deloptes@gmail.com> - 2020-09-09 20:50 +0200
              Re: 32 versus 64 bit reading list suggestions Kenneth Parker <sea7kenp@gmail.com> - 2020-09-08 00:00 +0200
            Re: 32 versus 64 bit reading list suggestions Andrei POPESCU <andreimpopescu@gmail.com> - 2020-09-08 10:50 +0200
              Re: 32 versus 64 bit reading list suggestions deloptes <deloptes@gmail.com> - 2020-09-08 19:40 +0200
                Re: 32 versus 64 bit reading list suggestions Andrei POPESCU <andreimpopescu@gmail.com> - 2020-09-09 07:40 +0200
                Re: 32 versus 64 bit reading list suggestions John Hasler <jhasler@newsguy.com> - 2020-09-09 14:20 +0200
      Re: 32 versus 64 bit reading list suggestions Joe <joe@jretrading.com> - 2020-09-07 21:00 +0200
        Re: 32 versus 64 bit reading list suggestions Richard Owlett <rowlett@cloud85.net> - 2020-09-07 22:20 +0200
        Re: 32 versus 64 bit reading list suggestions Andy Smith <andy@strugglers.net> - 2020-09-07 23:40 +0200
          Re: 32 versus 64 bit reading list suggestions Andy Smith <andy@strugglers.net> - 2020-09-08 00:10 +0200
            Re: 32 versus 64 bit reading list suggestions deloptes <deloptes@gmail.com> - 2020-09-08 08:10 +0200
      Re: 32 versus 64 bit reading list suggestions David Wright <deblis@lionunicorn.co.uk> - 2020-09-07 21:00 +0200
        Printed page vs. computer screen (was: Re: 32 versus 64 bit reading list suggestions) rhkramer@gmail.com - 2020-09-08 01:20 +0200
  Re: 32 versus 64 bit reading list suggestions Georgi Naplatanov <gosho@oles.biz> - 2020-09-07 16:30 +0200
  Re: 32 versus 64 bit reading list suggestions Felix Miata <mrmazda@earthlink.net> - 2020-09-07 17:00 +0200
    Re: 32 versus 64 bit reading list suggestions Richard Owlett <rowlett@cloud85.net> - 2020-09-07 20:00 +0200
      Re: 32 versus 64 bit reading list suggestions David Wright <deblis@lionunicorn.co.uk> - 2020-09-07 21:10 +0200
        Re: 32 versus 64 bit reading list suggestions Felix Miata <mrmazda@earthlink.net> - 2020-09-07 21:30 +0200
          Re: 32 versus 64 bit reading list suggestions Richard Owlett <rowlett@cloud85.net> - 2020-09-07 23:00 +0200
        Re: 32 versus 64 bit reading list suggestions Richard Owlett <rowlett@cloud85.net> - 2020-09-07 22:30 +0200

csiph-web