On Sun, Oct 08, 2017 at 07:43:57PM +0100, Richard Grainger wrote:
> Hi all
>
> I've created a yum repo for 32 bit wine packages on RHEL and CentOS 7:
>
> https://harbottle.gitlab.io/wine32/7/i386/
>
> The Wine packages work on both 32 bit and 64 bit RHEL/CentOS 7. There is no
> 32 bit version of
Hmm, So - I guess the best I can hope for is running the host as a full
workstation GUI with kodi installed - forget about Libreelec - and then
running the rest of appliances as VMs headless?
Many thanks for helping clear my thoughts on this.
M
On 23/01/18 19:01, Nux! wrote:
Running a VM with
On 01/22/2018 05:57 AM, Jerry Geis wrote:
I have virt-manager running just fine currently using NAT.
I want to "change" it to bridged network. The GUI is not letting me change
anything on the network section.
First, create the bridged network device, if you don't have one (where
"eth0" is you
Am 23.01.2018 um 20:23 schrieb H:
I received a rar-archive, probably created on Win10, that I could not extract
with unrar on CentOS 6.
CentOS does not provide unrar. You must have it from a third party
repository and we don't know which version of unrar that is.
Alexander
I received a rar-archive, probably created on Win10, that I could not extract
with unrar on CentOS 6.
Is it possible that the version of unrar available for CentOS 6 does not
support potentially new archiving algorithms used by some newer archiving
program (don't know which one was used) on Win
Running a VM with something graphical on top of something else graphical is one
thing.
What you want is to dedicate the GPU to the Libreelec VM, so it displays
directly to the screen (gpu) so it can properly use hardware acceleration and
so on, but you can't do that without VT-d/AMD-Vi afaik.
Thanks Nux for the follow up!
On 22/01/18 08:54, Nux! wrote:
You'd need to run virt-manager GUI somehow to manage the VMs. If you run Fedora
already on another machine then you can just yum install it and use it from
there.
That's what I figured - I already run an XP and W7 virt machines as we
Thank you for willing to help. It was a coincidence. Just a few hours between
update (including microcode) and server disabled.
The real reason was expired default certificate. I once used httpd. The cert
has been installed by mod_nss a few years ago. I somehow late at night
yesterday missed "e
Thank you. I'm collecting more logs info. Will be back.
Mikhail Utin
From: CentOS on behalf of Richard
Sent: Monday, January 22, 2018 22:28
To: CentOS mailing list
Subject: Re: [CentOS] failure to start httpd after today update
> Date: Tuesday, January 23,
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ.
On 01/22/2018 10:06 AM, Valeri Galtsev wrote:
>
>
> On 01/22/18 09:08, Johnny Hughes wrote:
>> On 01/18/2018 09:42 AM, Valeri Galtsev wrote:
>>>
>>>
>>> On 01/18/18 03:41, Pete Biggs wrote:
> Look at:
>
> https://t.co/6fT61xgtGH
>
> Get the latest microcode.dat file from
11 matches
Mail list logo
