On Fri, 14 Jun 2024 21:04:23 +0200, Ben Hutchings
wrote:
>But we definitely should
>discourage users from using i386 kernel packages on 64-bit-capable
>hardware, if we don't drop them entirely. I keep meaning to implement
>a boot-time warning about that...
We could build that into the update-gru
On Fri, 2024-06-14 at 14:07 +0200, Maite Gamper wrote:
> Hello,
>
> On 09.06.24 16:21, Ansgar 🙀 wrote:
[...]
> >
> > As I said before
> > (https://lists.debian.org/debian-devel/2024/05/msg00302.html):
> >
> > If you look at https://release.debian.org/testing/arch_qualify.html
> > there is at lea
Hello,
On 09.06.24 16:21, Ansgar 🙀 wrote:
Hi,
On Sun, 2024-06-09 at 08:58 -0500, r...@neoquasar.org wrote:
What it is is functional, and paid for. And likely, already installed
and in use somewhere (like all of my 32-bit systems).
It's not just a matter of "buy something better." That's easy.
On Mon, 10 Jun 2024 at 20:17:27 +0500, Andrey Rakhmatullin wrote:
> On Mon, Jun 10, 2024 at 04:02:54PM +0100, Simon McVittie wrote:
> > several important upstreams no longer consider i386 to be useful (and
> > especially i386-without-SSE2), so so the burden of supporting 32-bit
> > CPUs in modern s
On Mon, Jun 10, 2024 at 04:02:54PM +0100, Simon McVittie wrote:
> On Mon, 10 Jun 2024 at 12:43:27 +, Stefano Rivera wrote:
> > The point here is that the Debian project is not intending to support
> > new hardware on the i386 architecture. The architecture is being kept
> > around primarily to
On Mon, 10 Jun 2024 at 12:43:27 +, Stefano Rivera wrote:
> The point here is that the Debian project is not intending to support
> new hardware on the i386 architecture. The architecture is being kept
> around primarily to support running old i386 binaries.
... and the most appropriate answers
Hi The (2024.06.10_12:22:14_+)
> How to get access to the right parts of the waste stream to be able to
> pull out some working 64-bit hardware is another question, and one where
> I don't have an answer that wouldn't involve spending money (which would
> presumably make the proposed alternativ
On 2024-06-10 at 08:09, rhys wrote:
> On Jun 10, 2024, at 01:44, Andrey Rakhmatullin
> wrote:
>
>> On Sun, Jun 09, 2024 at 08:39:27PM -0500, r...@neoquasar.org
>> wrote:
>>> Reuse is better than recycle for complex things like electronics.
>>>
>> You were suggested to resuse an old amd64 machi
> On Jun 10, 2024, at 01:44, Andrey Rakhmatullin wrote:
>
> On Sun, Jun 09, 2024 at 08:39:27PM -0500, r...@neoquasar.org wrote:
It's not just a matter of "buy something better." That's easy.
>>
>>> Indeed, that is easier and cheaper.
>>
>> Of course, continuing to use a system I alread
On Sun, Jun 09, 2024 at 08:39:27PM -0500, r...@neoquasar.org wrote:
> >> It's not just a matter of "buy something better." That's easy.Â
>
> >Indeed, that is easier and cheaper.
>
> Of course, continuing to use a system I already have is cheaper still.
>
> > What's not easy is that a) that adds
>> It's not just a matter of "buy something better." That's easy.Â
>Indeed, that is easier and cheaper.
Of course, continuing to use a system I already have is cheaper still.
> What's not easy is that a) that adds another machine to the waste
> stream, instead of continuing to get use from it
Hi,
On Sun, 2024-06-09 at 08:58 -0500, r...@neoquasar.org wrote:
> What it is is functional, and paid for. And likely, already installed
> and in use somewhere (like all of my 32-bit systems).Â
>
> It's not just a matter of "buy something better." That's easy.Â
Indeed, that is easier and cheaper
someone to
contact me off list to discuss details - how can I help with support for i386?
I have just enough software training to be dangerous and may be able to help
carry some of the actual load here, instead of just asking for more free
support.Â
Sent from my mobile device.
_
On Sun, 19 May 2024 20:19:12 +0200, Ben Hutchings
wrote:
>The plan is to keep i386 as a partial architecture that can be used as
>a "foreign architecture" on systems where amd64 is the main
>architecture.
Many people using ancient hardware such as a T60 thinkpad say that's
not enough for them. I
On Sun, 2024-05-19 at 07:26 +, defrag mentation wrote:
> I think some of the i386 support policies needs to be reconsidered.
>
> Here are some suggestions:
>
> 1. ​Move Wine-32 to amd64, and Wine-32 may be compiled to 64-bit time_t.
>
> Wine-32 is now in currently dropped i386 DVDs/BDs, not
On Sun, May 19, 2024 at 09:09:10AM +, defrag mentation wrote:
> > What will this solve?
>
> > I don't think this is "needed"? Unless you think all i386 packages will be
>
> removed from Debian, which is not the plan?
>
> Case 1: Debian removed i386 DVDs/BDs, and someone jigdo backed the full
> What will this solve?
> I don't think this is "needed"? Unless you think all i386 packages will be
removed from Debian, which is not the plan?
Case 1: Debian removed i386 DVDs/BDs, and someone jigdo backed the full amd64
DVDs/BDs set will be surprised that it do not contain wine32.
Case 2: W
On Sun, May 19, 2024 at 07:26:28AM +, defrag mentation wrote:
> What will this solve?
> I don't think this is "needed"? Unless you think all i386 packages will be
removed from Debian, which is not the plan?
Case 1: Debian removed i386 DVDs/BDs, and someone jigdo backed the full amd64
DVDs/
On Sun, May 19, 2024 at 07:26:28AM +, defrag mentation wrote:
> I think some of the i386 support policies needs to be reconsidered.
>
> Here are some suggestions:
>
> 1. ​Move Wine-32 to amd64, and Wine-32 may be compiled to 64-bit time_t.
What will this solve?
> Wine-32 is now in currently
I think some of the i386 support policies needs to be reconsidered.
Here are some suggestions:
1. ​Move Wine-32 to amd64, and Wine-32 may be compiled to 64-bit time_t.
Wine-32 is now in currently dropped i386 DVDs/BDs, not in amd64 DVDs/BDs as it
is multiarch-only now, so at least I think movin
20 matches
Mail list logo
