Well, it was a few years ago, maybe M$ finally made it functional, but
originally WSL had no network support. WTF would I want a modern OS, even
linux in emulation, to NOT have networking? Even using vbox under windoze
running ubuntu linux was very destructive to performance, I was hoping WSL
to
On a whim I rolled back to my kernel from when It was last running 16.04
successfully (for some reason I thought this would not work) and the server
is up and running. Now to find out what was not included to load my disk
subsystem.
On Tue, Dec 10, 2019 at 3:48 PM Stephen Partington
wrote:
> wei
weird. I currently have no issues with networking. and technically it is
not an emulation layer. It is supposed to be an api set or something that
runs a Linux kernel under windows natively.
On Tue, Dec 10, 2019 at 2:42 PM Michael Butash wrote:
> Last time I tried WSL was with getting this lapto
Last time I tried WSL was with getting this laptop a few years ago. As a
network guy, I sort of just sat there stunned that the frigging thing
couldn't network. Why the hell would you make a linux emulation layer that
couldn't network? Is this still Ballmer-hate?
What the hell is good in this d
well microsoft has made good improvements with WSL and you can do some neat
things like that
On Tue, Dec 10, 2019 at 8:27 AM Michael Butash wrote:
> Upgrading to 18.04 broke like everything for me (kde, wm, graphics
> drivers), it's what single-handedly drove me to arch, so ymmv.
>
> My experie
Upgrading to 18.04 broke like everything for me (kde, wm, graphics
drivers), it's what single-handedly drove me to arch, so ymmv.
My experience with arch hasn't been much better of late, so take it for
what you will. Arch updates blew up my desktop, and my laptop I'm afraid
to reboot as my last w
It is most definitely 64 bit. I had 64 bit 16.04 running like a champ until
the 18.04 upgrade was done.
It also ran vmware 6.7 well also.
On Mon, Dec 9, 2019, 9:02 PM Thomas Scott wrote:
> I know I had a legacy install on a Proliant I supported that was installed
> upside down and burnt out it'
I know I had a legacy install on a Proliant I supported that was installed
upside down and burnt out it's drives after a few years (surprised it
lasted that long). When I came on-site to reinstall it, I tried to install
16.04 since I already had the install media on me, I couldn't as it had
issues
I suspect it may be 32Bit computer but it should give you a i386 hardware
error during installation.
while 18.04 is only 64 bit you can use the net install at
http://cdimage.ubuntu.com/netboot/bionic/
it has a community supported 32 bit version available
On Mon, Dec 9, 2019 at 12:24 PM Stephen Par
I have an older Proliant server I am trying to make use of at home. The
hardware is fully functional, and aside from needing some spare drive
sleds, It is ready to go.
However, I cannot run 18.04 on the server and I suspect it is related to
changes in the kernel and I am trying to map those.
The
10 matches
Mail list logo
