On 8/13/23 04:55, John Levine wrote:
> According to J.O. Aho <
us...@example.net>:
>> Maybe it's the wrong architecture you installed it for, seems you may
>> need to install both the x86 version and amd64 (by ms called x64) version.
>
> I'm reasonably sure I installed the x64 version of both, but I'll check again.
I wouldn't be surprised if it's the x86 version that is needed and it
don't seem to be that both the 32 and 64 bit versions are bundled
together in one package as some on the net seems to think.
> I was hoping that someone was actually using Alpine on Windows and
> could tell us how to make it work. Who knows, maybe it doesn't work,
> nobody's using it, so nobody's noticed.
I have seen people ask windows related questions, but not sure if those
people stay around after got their issue solved or not (from the high
number of replies, I guess not).
One alternative would be using WSL, then you can use the Linux native
one, I do also recommend to install Windows Terminal, you get the feel
and power from konsole (part of KDE/Plasma desktop). Also gsudo is quite
great, if you want to open a terminal as administrator and have that as
one of the options. That are tools I tend to install is I have to use
ms-windows on a work computer. Sure it's a bit more work than just using
it native. If you use VPN, then you need manually to change the mtu in
the WSL:
sudo ifconfig eth0 mtu [size]
The size most likely will be 1350, but setting it to a smaller number
will ensure packages will not be too big.
--
//Aho