On 2022-02-01, Stanislav Vlasov wrote:
> 2022-02-01 17:20 GMT+05:00, Curt :
>> On 2022-01-31, Stefan Monnier wrote:
Technically correct, but Curt's response was good enough for Richard
Owlett to make progress. Richard Owlett is very unlikely to be using
a 64-bit kernel with 32-bit
2022-02-01 17:20 GMT+05:00, Curt :
> On 2022-01-31, Stefan Monnier wrote:
>>> Technically correct, but Curt's response was good enough for Richard
>>> Owlett to make progress. Richard Owlett is very unlikely to be using
>>> a 64-bit kernel with 32-bit userspace.
>>
>> BTW, for the twisted-minded
On Tue, Feb 01, 2022 at 12:32:24AM -0500, Stefan Monnier wrote:
that's not running a 64bit userspace on a 32bit kernel,
Why not? You have a 64bit system on top, a 32bit kernel at the bottom
and whether execution of those 64bit binaries is performed directly by
the CPU or via binfmt + qemu is
On 2022-01-31, Stefan Monnier wrote:
>> Technically correct, but Curt's response was good enough for Richard
>> Owlett to make progress. Richard Owlett is very unlikely to be using
>> a 64-bit kernel with 32-bit userspace.
>
> BTW, for the twisted-minded it's probably possible to run a 64bit
>
On 02/01/2022 12:12 AM, songbird wrote:
Richard Owlett wrote:
...
My hardware can support either 32 or 64 bit OS.
I *ONLY* use one or the other.
My goal is to determine which I chose at installation.
that should be somewhere in:
/var/log/installer
Yes but ;/
"dpkg --print-architecture"
Am Montag, 31. Januar 2022 schrieb Richard Owlett:
> >> 2. As superuser, how can I determine which is installed on a
> >> different partition?
> >> [ My typical installation routine has been a descriptive
> >> label for each root partition. But not always done ;{ ]
> >
> > If the superuser
Richard Owlett wrote:
...
> My hardware can support either 32 or 64 bit OS.
> I *ONLY* use one or the other.
> My goal is to determine which I chose at installation.
that should be somewhere in:
/var/log/installer
songbird
On Mon, Jan 31, 2022 at 04:37:37PM -0500, Stefan Monnier wrote:
> > Technically correct, but Curt's response was good enough for Richard
> > Owlett to make progress. Richard Owlett is very unlikely to be using
> > a 64-bit kernel with 32-bit userspace.
>
> BTW, for the twisted-minded it's
On Mon, Jan 31, 2022 at 09:02:17PM -0500, Stefan Monnier wrote:
Greg Wooledge [2022-01-31 16:45:52] wrote:
On Mon, Jan 31, 2022 at 04:37:37PM -0500, Stefan Monnier wrote:
BTW, for the twisted-minded it's probably possible to run a 64bit
userspace on a 32bit kernel.
No. Or at least, not that
On Mon 31 Jan 2022 at 21:02:17 (-0500), Stefan Monnier wrote:
> Greg Wooledge [2022-01-31 16:45:52] wrote:
> > On Mon, Jan 31, 2022 at 04:37:37PM -0500, Stefan Monnier wrote:
> >> BTW, for the twisted-minded it's probably possible to run a 64bit
> >> userspace on a 32bit kernel.
> > No. Or at
On 01/31/2022 03:37 PM, Stefan Monnier wrote:
Technically correct, but Curt's response was good enough for Richard
Owlett to make progress. Richard Owlett is very unlikely to be using
a 64-bit kernel with 32-bit userspace.
BTW, for the twisted-minded it's probably possible to run a 64bit
On 01/31/2022 02:01 PM, Brian wrote:
On Mon 31 Jan 2022 at 11:38:17 -0500, Greg Wooledge wrote:
uname -m
Are you saying that that doesn't reveal whether I've installed a 64 or a 32
bit release?
It does not. It only reveals which kernel is running.
As I said in another message, you
On Mon, Jan 31, 2022 at 04:37:37PM -0500, Stefan Monnier wrote:
> > Technically correct, but Curt's response was good enough for Richard
> > Owlett to make progress. Richard Owlett is very unlikely to be using
> > a 64-bit kernel with 32-bit userspace.
>
> BTW, for the twisted-minded it's
On Mon 31 Jan 2022 at 11:38:17 -0500, Greg Wooledge wrote:
> > >> uname -m
>
> > Are you saying that that doesn't reveal whether I've installed a 64 or a 32
> > bit release?
>
> It does not. It only reveals which kernel is running.
>
> As I said in another message, you could have a 32-bit
On Mon 31 Jan 2022 at 06:32:23 (-0600), Richard Owlett wrote:
> Due to historical circumstances, I have laptops which multi-boot
> various Debian releases. There be 32 bit and 64 bit versions of the
> same release on a particular machine.
>
> 1. From current console, how can I determine which is
On Mon 31 Jan 2022 at 08:26:35 (-0500), Greg Wooledge wrote:
> On Mon, Jan 31, 2022 at 08:23:45AM -0500, Stefan Monnier wrote:
> > > 1. From current console, how can I determine which is running?
> > >[ equivalent of /etc/debian_version would be ideal ]
> >
> > Depends what you mean. The
> >> uname -m
> Are you saying that that doesn't reveal whether I've installed a 64 or a 32
> bit release?
It does not. It only reveals which kernel is running.
As I said in another message, you could have a 32-bit userspace with
a 64-bit kernel. If that's the case, then uname -m gives you
On 2022-01-31, Richard Owlett wrote:
> On 01/31/2022 06:37 AM, Curt wrote:
>> On 2022-01-31, Richard Owlett wrote:
>>> Due to historical circumstances, I have laptops which multi-boot various
>>> Debian releases. There be 32 bit and 64 bit versions of the same release
>>> on a particular
On 01/31/2022 06:37 AM, Curt wrote:
On 2022-01-31, Richard Owlett wrote:
Due to historical circumstances, I have laptops which multi-boot various
Debian releases. There be 32 bit and 64 bit versions of the same release
on a particular machine.
1. From current console, how can I determine
On Mon, Jan 31, 2022 at 03:24:51PM +0200, Teemu Likonen wrote:
> * 2022-01-31 06:32:23-0600, Richard Owlett wrote:
>
> > Due to historical circumstances, I have laptops which multi-boot
> > various Debian releases. There be 32 bit and 64 bit versions of the
> > same release on a particular
* 2022-01-31 06:32:23-0600, Richard Owlett wrote:
> Due to historical circumstances, I have laptops which multi-boot
> various Debian releases. There be 32 bit and 64 bit versions of the
> same release on a particular machine.
>
> 1. From current console, how can I determine which is running?
>
On Mon, Jan 31, 2022 at 08:23:45AM -0500, Stefan Monnier wrote:
> > 1. From current console, how can I determine which is running?
> >[ equivalent of /etc/debian_version would be ideal ]
>
> Depends what you mean. The answer may also be "both" depending on what
> you care about. E.g. many
On 2022-01-31, Richard Owlett wrote:
> Due to historical circumstances, I have laptops which multi-boot various
> Debian releases. There be 32 bit and 64 bit versions of the same release
> on a particular machine.
>
> 1. From current console, how can I determine which is running?
> [
23 matches
Mail list logo