Hello,
I recently upgraded from Fedora 29 to Fedora 30.
I am unable to bring up a Vagrant guest.
vagrant up
Bringing machine 'default' up with 'libvirt' provider...
Name `centos7_default` of domain about to create is already taken.
Please try to run
`vagrant up` command again.
I launched
On Wed, 2019-08-14 at 18:23 +0800, Ed Greshko wrote:
> On 8/14/19 6:07 PM, Patrick O'Callaghan wrote:
> > I have a small F29 Server VM (KVM/QEMU) which has not changed recently
> > and has worked consistently for several months. Now when I try to boot
> > it I get:
> >
> > Requested operation is
On 8/14/19 8:13 PM, Patrick O'Callaghan wrote:
> Yes, I forgot to mention I did that. 'lsof' returns nothing.
I see.
Well, I'm not having any problems. But I did notice you've changed the
"default" location
for your images.
Would it be possible to move it to the default location to see if the
I have a small F29 Server VM (KVM/QEMU) which has not changed recently
and has worked consistently for several months. Now when I try to boot
it I get:
Requested operation is not valid: Setting different SELinux label on
/home/poc/VM/vm-f29b.qcow2 which is already in use
I haven't touched any
On 8/14/19 6:07 PM, Patrick O'Callaghan wrote:
> I have a small F29 Server VM (KVM/QEMU) which has not changed recently
> and has worked consistently for several months. Now when I try to boot
> it I get:
>
> Requested operation is not valid: Setting different SELinux label on
>
vagrant up
Bringing machine 'default' up with 'libvirt' provider...
Name `centos7_default` of domain about to create is already taken.
Please try to run
`vagrant up` command again.
I launched the Virtual Machine Manager GUI and the guest is not listed
there.
I try to find it via virsh:
Dear Fedora Community Members,
I am a master student based in the University of Leeds (UK), currently
conducting a research in regards to investigating how open source software
community culture, governance and structure, motivation of participation
influence the innovation capability of OSS
https://www.port389.org/docs/389ds/howto/howto-install-389.html appears to be
geared toward 389-*-1.4.x
while https://www.port389.org/docs/389ds/legacy/install-guide.html does not
seem to reference anything past RHEL 4
I was told that v1.4.x is targeted for RHEL 8 and CentOS 8 is not yet
You do not install centos7 389 1.4.x and cockpit. Because you might gcclib
upgrade and gcc module upgrade. So You can install at rhel8 or coming
forward centos 8(?).
2019년 8월 14일 (수) 오후 8:56, Dan White 님이 작성:
> https://www.port389.org/docs/389ds/howto/howto-install-389.html appears
> to be
You can find at google.
unixmen.con/install-and-configure-ldap-server-in-centos-7
2019년 8월 14일 (수) 오후 9:22, Dan White 님이 작성:
> Sorry, but RHEL 8/waiting for CentOS 8 is not an option at this time.
>
> How do I install 389 v1.3.x on CentOS 7, please ?
>
> On Aug 14, 2019, at 8:10 AM, sang jun
Sorry, but RHEL 8/waiting for CentOS 8 is not an option at this time.
How do I install 389 v1.3.x on CentOS 7, please ?
> On Aug 14, 2019, at 8:10 AM, sang jun Song wrote:
>
> You do not install centos7 389 1.4.x and cockpit. Because you might gcclib
> upgrade and gcc module upgrade. So You
Hello,
On Wed, Aug 14, 2019 at 1:56 PM Dan White wrote:
> https://www.port389.org/docs/389ds/howto/howto-install-389.html appears
> to be geared toward 389-*-1.4.x
> while https://www.port389.org/docs/389ds/legacy/install-guide.html does
> not seem to reference anything past RHEL 4
>
> I was
Thank you for the details, Viktor
On August 14, 2019 at 10:11 AM, Viktor Ashirov wrote:
Hello,
On Wed, Aug 14, 2019 at 1:56 PM Dan White wrote:
https://www.port389.org/docs/389ds/howto/howto-install-389.html appears to be
geared toward 389-*-1.4.x
while
13 matches
Mail list logo
