Ubuntu 18.04 on (Really) Old HP Proliant

Wed Dec 11 10:01:46 MST 2019

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 be a decent medium.

At some point I'll boot over to the original windoze partition, maybe
sooner than later with this laptop being a hot mess and everything else on
Arch I own.  I probably should update the win os, bios, and things on it at
least.

-mb

On Tue, Dec 10, 2019 at 3:48 PM Stephen Partington <cryptworks at gmail.com>
wrote:

> 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 <michael at butash.net> wrote:
>
>> 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 day and age without networking?  I don't
>> see how they even shipped it as a thing without network support.
>>
>> This and other major things like I said visual lag in the gui, with
>> up-to-date os, drivers, etc shipped from dell, was utter shite, and just
>> angered me.  It was graphically unusable to me.  I gave windoze a solid 2
>> weeks as a trial, just to see, and it was garbage to try and be
>> productive.  It really didn't like when I was layer on VM's in vbox, which
>> usually I have 5-8 vm's at a time running in my main system, and it fell
>> apart.
>>
>> People ask why I bother with linux.  Because windoze can't do the things
>> I do in linux, like run 10 vm's of different os's and still game on steam.
>> I've ran linux on a desktop as my main rig since 2006, as well as dealing
>> with entirely windoze enterprise worlds, so I like to think I have some
>> knowledge of this.
>>
>> -mb
>>
>>
>> On Tue, Dec 10, 2019 at 8:44 AM Stephen Partington <cryptworks at gmail.com>
>> wrote:
>>
>>> 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 <michael at butash.net>
>>> 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 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 working device.  If I didn't hate windoze so much, I
>>>> might actually try it again, but it's performance on my xps15 was absolute
>>>> shite with the 4k display.  Like mouse lag randomly just to screw with me
>>>> and slow down everything working.
>>>>
>>>> -mb
>>>>
>>>>
>>>> On Mon, Dec 9, 2019 at 9:13 PM Stephen Partington <cryptworks at gmail.com>
>>>> wrote:
>>>>
>>>>> 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 <mr.thomas.scott at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> 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 with the RAID array controller. I had to roll
>>>>>> back to 14.04 and then upgrade it to maintain compatibility. I had a
>>>>>> similar issue with CentOS6/7 a bout a year ago as well, also on HP servers.
>>>>>> In my experience, both times it was the RAID controller.
>>>>>>
>>>>>> <https://about.me/thomas.scott?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=edit_panel&utm_content=thumb>
>>>>>> Thomas Scott
>>>>>> about.me/thomas.scott
>>>>>> <https://about.me/thomas.scott?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=edit_panel&utm_content=thumb>
>>>>>> <http://about.me/thomas.scott>
>>>>>>
>>>>>>
>>>>>> On Mon, Dec 9, 2019 at 9:47 PM Todd Cole <toddc at azloco.com> wrote:
>>>>>>
>>>>>>> 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 Partington <
>>>>>>> cryptworks at gmail.com> wrote:
>>>>>>>
>>>>>>>> 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 Architecture is Dual Opteron quad-core Processors and DDR2 ECC
>>>>>>>> Registered memory. I think it is a DL 365 Gen 1 (would have to look to make
>>>>>>>> sure)
>>>>>>>>
>>>>>>>> Does anyone have thoughts on how I could gracefully get this
>>>>>>>> hardware to a current kernel?
>>>>>>>>
>>>>>>>> --
>>>>>>>> A mouse trap, placed on top of your alarm clock, will prevent you
>>>>>>>> from rolling over and going back to sleep after you hit the snooze button.
>>>>>>>>
>>>>>>>> Stephen
>>>>>>>>
>>>>>>>> ---------------------------------------------------
>>>>>>>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>>>>>>>> To subscribe, unsubscribe, or to change your mail settings:
>>>>>>>> https://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> ---------------------------------------------------
>>>>>>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>>>>>>> To subscribe, unsubscribe, or to change your mail settings:
>>>>>>> https://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>>>>>
>>>>>> ---------------------------------------------------
>>>>>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>>>>>> To subscribe, unsubscribe, or to change your mail settings:
>>>>>> https://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>>>>
>>>>> ---------------------------------------------------
>>>>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>>>>> To subscribe, unsubscribe, or to change your mail settings:
>>>>> https://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>>>
>>>> ---------------------------------------------------
>>>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>>>> To subscribe, unsubscribe, or to change your mail settings:
>>>> https://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>>
>>>
>>>
>>> --
>>> A mouse trap, placed on top of your alarm clock, will prevent you from
>>> rolling over and going back to sleep after you hit the snooze button.
>>>
>>> Stephen
>>>
>>> ---------------------------------------------------
>>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>>> To subscribe, unsubscribe, or to change your mail settings:
>>> https://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>
>> ---------------------------------------------------
>> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
>> To subscribe, unsubscribe, or to change your mail settings:
>> https://lists.phxlinux.org/mailman/listinfo/plug-discuss
>
>
>
> --
> A mouse trap, placed on top of your alarm clock, will prevent you from
> rolling over and going back to sleep after you hit the snooze button.
>
> Stephen
>
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss at lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> https://lists.phxlinux.org/mailman/listinfo/plug-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.phxlinux.org/pipermail/plug-discuss/attachments/20191211/1eeda099/attachment.html>