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

Groups > linux.debian.user > #226741 > unrolled thread

32 versus 64 bit reading list suggestions

Started byRichard Owlett <rowlett@cloud85.net>
First post2020-09-07 15:50 +0200
Last post2020-09-07 22:30 +0200
Articles 6 on this page of 46 — 17 participants

Back to article view | Back to linux.debian.user

Contents

  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

Page 3 of 3 — ← Prev page 1 2 [3]

#226746

FromFelix Miata <mrmazda@earthlink.net>
Date2020-09-07 17:00 +0200
Message-ID<AMqMG-7mk-13@gated-at.bofh.it>
In reply to#226741
Richard Owlett composed on 2020-09-07 08:44 (UTC-0500):

>    2.What 32 bit utilities are there to identify the hardware capabilities
>      of a particular machine?

inxi

For CPU bits specifically:

	inxi -Cy

For all CPU capabilities:

	inxi -Cay

If these produce any errors, you're using an old inxi version. Upstream version
permits self upgrading thus:

	inxi -U

It's been too long since I last used Debian's inxi package, so don't remember if
it's packaged to override -U capability.

> inxi -V | head -n1
inxi 3.1.06-00 (2020-08-17)

For a more general display of hardware configuration:

	inxi -by

And with more detail:

	inxi -bay

The -y switch produces a format resulting in more lines and shorter line length,
so isn't needed, and isn't available in old inxi versions.
-- 
Evolution as taught in public schools, like religion,
	is based on faith, not on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#226756

FromRichard Owlett <rowlett@cloud85.net>
Date2020-09-07 20:00 +0200
Message-ID<AMtAS-B9-7@gated-at.bofh.it>
In reply to#226746
On 09/07/2020 09:51 AM, Felix Miata wrote:
> Richard Owlett composed on 2020-09-07 08:44 (UTC-0500):
> 
>>     2.What 32 bit utilities are there to identify the hardware capabilities
>>       of a particular machine?
> 
> inxi
> 
> For CPU bits specifically:
> 
> 	inxi -Cy
> 
> For all CPU capabilities:
> 
> 	inxi -Cay
i>
> If these produce any errors, you're using an old inxi version. Upstream version
> permits self upgrading thus:
> 
> 	inxi -U
> 
> It's been too long since I last used Debian's inxi package, so don't remember if
> it's packaged to override -U capability.
> 
>> inxi -V | head -n1
> inxi 3.1.06-00 (2020-08-17)

Running Debian 9.8 I get
root@defaultinstall:/home/richard# inxi -V | head -n1
inxi 2.3.5-00 (2016-12-02)

It didn't like the "a" nor "y" parameters.

I did "apt update" then "apt upgrade" and am now running Debian 9.13
  inxi -V | head -n1 re still reports inxi 2.3.5-00 (2016-12-02)


What should I read before attempting "inxi -U"?

I also have the 64 bit flavor of Debian 10 on a separate partition. I'll 
run them there and see what I'll get.

As time is available I'll attempt to install also the 32 bit Debian 10.

More later.
Thanks






> 
> For a more general display of hardware configuration:
> 
> 	inxi -by
> 
> And with more detail:
> 
> 	inxi -bay
> 
> The -y switch produces a format resulting in more lines and shorter line length,
> so isn't needed, and isn't available in old inxi versions.
>

[toc] | [prev] | [next] | [standalone]

#226761

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2020-09-07 21:10 +0200
Message-ID<AMuGC-1sn-3@gated-at.bofh.it>
In reply to#226756
On Mon 07 Sep 2020 at 12:49:36 (-0500), Richard Owlett wrote:
> On 09/07/2020 09:51 AM, Felix Miata wrote:
> > Richard Owlett composed on 2020-09-07 08:44 (UTC-0500):
> > 
> > >     2.What 32 bit utilities are there to identify the hardware capabilities
> > >       of a particular machine?
> > 
> > inxi
> > 
> > For CPU bits specifically:
> > 
> > 	inxi -Cy
> > 
> > For all CPU capabilities:
> > 
> > 	inxi -Cay
> i>
> > If these produce any errors, you're using an old inxi version. Upstream version
> > permits self upgrading thus:
> > 
> > 	inxi -U
> > 
> > It's been too long since I last used Debian's inxi package, so don't remember if
> > it's packaged to override -U capability.
> > 
> > > inxi -V | head -n1
> > inxi 3.1.06-00 (2020-08-17)
> 
> Running Debian 9.8 I get
> root@defaultinstall:/home/richard# inxi -V | head -n1
> inxi 2.3.5-00 (2016-12-02)
> 
> It didn't like the "a" nor "y" parameters.
> 
> I did "apt update" then "apt upgrade" and am now running Debian 9.13
>  inxi -V | head -n1 re still reports inxi 2.3.5-00 (2016-12-02)
> 
> 
> What should I read before attempting "inxi -U"?

man inxi   on your buster installation. Then forget about manually
upgrading stretch's version: you're interested in what inxi tells
you about the machine hardware.

> I also have the 64 bit flavor of Debian 10 on a separate partition.
> I'll run them there and see what I'll get.
> 
> As time is available I'll attempt to install also the 32 bit Debian 10.

Perfect for the comparison you want.

> > For a more general display of hardware configuration:
> > 
> > 	inxi -by
> > 
> > And with more detail:
> > 
> > 	inxi -bay
> > 
> > The -y switch produces a format resulting in more lines and shorter line length,
> > so isn't needed, and isn't available in old inxi versions.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#226763

FromFelix Miata <mrmazda@earthlink.net>
Date2020-09-07 21:30 +0200
Message-ID<AMuZX-1zr-5@gated-at.bofh.it>
In reply to#226761
David Wright composed on 2020-09-07 14:03 (UTC-0500):

> On Mon 07 Sep 2020 at 12:49:36 (-0500), Richard Owlett wrote:

>> What should I read before attempting "inxi -U"?

> man inxi   on your buster installation. Then forget about manually
> upgrading stretch's version: you're interested in what inxi tells
> you about the machine hardware.

If multibooting, better to put it where the inxi author suggests instead of using
a distro's version, as long as the various installations share that location. It's
merely a script, can go anywhere you please, in $PATH if you want, elsewhere if
you don't mind executing it via fullpathname.

>> I also have the 64 bit flavor of Debian 10 on a separate partition.
>> I'll run them there and see what I'll get.

>> As time is available I'll attempt to install also the 32 bit Debian 10.

> Perfect for the comparison you want.

+1

For more reading, try the author's site:
https://smxi.org/docs/inxi-installation.htm#inxi-manual-install
-- 
Evolution as taught in public schools, like religion,
	is based on faith, not on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

[toc] | [prev] | [next] | [standalone]

#226769

FromRichard Owlett <rowlett@cloud85.net>
Date2020-09-07 23:00 +0200
Message-ID<AMwp3-2iK-1@gated-at.bofh.it>
In reply to#226763
On 09/07/2020 02:19 PM, Felix Miata wrote:
>  
> For more reading, try the author's site:
> https://smxi.org/docs/inxi-installation.htm#inxi-manual-install
> 

I browsed some random pages in smxi.org . I think a more detailed read 
is in order. I suspect the tools there will answer questions I didn't 
have the background to ask properly.


Thank you

[toc] | [prev] | [next] | [standalone]

#226767

FromRichard Owlett <rowlett@cloud85.net>
Date2020-09-07 22:30 +0200
Message-ID<AMvW1-28Y-1@gated-at.bofh.it>
In reply to#226761
On 09/07/2020 02:03 PM, David Wright wrote:
> On Mon 07 Sep 2020 at 12:49:36 (-0500), Richard Owlett wrote:
>> On 09/07/2020 09:51 AM, Felix Miata wrote:
>>> Richard Owlett composed on 2020-09-07 08:44 (UTC-0500):
>>>
>>>>      2.What 32 bit utilities are there to identify the hardware capabilities
>>>>        of a particular machine?
>>>
>>> inxi
>>>
>>> For CPU bits specifically:
>>>
>>> 	inxi -Cy
>>>
>>> For all CPU capabilities:
>>>
>>> 	inxi -Cay
>> i>
>>> If these produce any errors, you're using an old inxi version. Upstream version
>>> permits self upgrading thus:
>>>
>>> 	inxi -U
>>>
>>> It's been too long since I last used Debian's inxi package, so don't remember if
>>> it's packaged to override -U capability.
>>>
>>>> inxi -V | head -n1
>>> inxi 3.1.06-00 (2020-08-17)
>>
>> Running Debian 9.8 I get
>> root@defaultinstall:/home/richard# inxi -V | head -n1
>> inxi 2.3.5-00 (2016-12-02)
>>
>> It didn't like the "a" nor "y" parameters.
>>
>> I did "apt update" then "apt upgrade" and am now running Debian 9.13
>>   inxi -V | head -n1 re still reports inxi 2.3.5-00 (2016-12-02)
>>
>>
>> What should I read before attempting "inxi -U"?
> 
> man inxi   on your buster installation. Then forget about manually
> upgrading stretch's version: you're interested in what inxi tells
> you about the machine hardware.
> 
>> I also have the 64 bit flavor of Debian 10 on a separate partition.
>> I'll run them there and see what I'll get.
>>
>> As time is available I'll attempt to install also the 32 bit Debian 10.
> 
> Perfect for the comparison you want.

I just did a net install of i386 Debian 10. A couple of things that run 
under i386 Debian 9 AND amd64 Debian 10 don't work right under i386 
Debian 10.

I've some trouble shooting to do. Suspect operator error of some sort.


> 
>>> For a more general display of hardware configuration:
>>>
>>> 	inxi -by
>>>
>>> And with more detail:
>>>
>>> 	inxi -bay
>>>
>>> The -y switch produces a format resulting in more lines and shorter line length,
>>> so isn't needed, and isn't available in old inxi versions.
> 
> Cheers,
> David.
> 
> 
>

[toc] | [prev] | [standalone]

Page 3 of 3 — ← Prev page 1 2 [3]

Back to top | Article view | linux.debian.user

csiph-web