Hi,
Here's the warning that Yum currently displays:
** Found 3 pre-existing rpmdb problem(s), 'yum check' output follows:
ipa-client-4.4.0-14.el7.centos.7.x86_64 has installed conflicts
freeipa-client: ipa-client-4.4.0-14.el7.centos.7.x86_64
ipa-client-common-4.4.0-14.el7.centos.7.noarch has
On Mon, Jul 3, 2017 at 10:15 AM, Stuart Barkley wrote:
> On Fri, 30 Jun 2017 at 08:00 -, centos-announce-requ...@centos.org wrote:
>
>> Upstream details at : https://rhn.redhat.com/errata/RHBA-2017-1609.html
The following page refers to the same RHBA:
Did my last fixes on Fedora F25,
So we I'm in 1:1 situation of Centos and Fedora with Btrfs Snapshot.
hm...
Sincerely
Andy
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
ken wrote:
> On 07/03/2017 02:41 PM, Gordon Messmer wrote:
>> On 07/03/2017 05:07 AM, Chris Olson wrote:
>>> A progress
>>> bar at the bottom of the start-up screen never reaches completion.
>
>> Press "alt+d" on the keyboard to disable the graphical (or text)
>> progress bar and view the console
On 07/03/2017 02:52 PM, ken wrote:
On 07/03/2017 02:41 PM, Gordon Messmer wrote:
On 07/03/2017 05:07 AM, Chris Olson wrote:
A progress
bar at the bottom of the start-up screen never reaches completion.
Press "alt+d" on the keyboard to disable the graphical (or text)
progress bar and view
On 07/03/2017 02:41 PM, Gordon Messmer wrote:
On 07/03/2017 05:07 AM, Chris Olson wrote:
A progress
bar at the bottom of the start-up screen never reaches completion.
Press "alt+d" on the keyboard to disable the graphical (or text)
progress bar and view the console output of the startup
On 07/03/2017 05:07 AM, Chris Olson wrote:
A progress
bar at the bottom of the start-up screen never reaches completion.
Press "alt+d" on the keyboard to disable the graphical (or text)
progress bar and view the console output of the startup sequence.
On Mon, July 3, 2017 12:15 pm, Stuart Barkley wrote:
> On Fri, 30 Jun 2017 at 08:00 -, centos-announce-requ...@centos.org
> wrote:
>
>> Upstream details at : https://rhn.redhat.com/errata/RHBA-2017-1609.html
>
> For a while now the "upstream details" pointed to in messages from
>
On Jul 1, 2017, at 3:00 AM, Pete Biggs wrote:
>
>> In your experience, what's the "longest" a DNS cache is configured to
>> keep outdated information? A day? A week? A month? Longer?
>>
> That is controlled by the TTL (time to live) entry.
…which is often under your control
On Fri, 30 Jun 2017 at 08:00 -, centos-announce-requ...@centos.org wrote:
> Upstream details at : https://rhn.redhat.com/errata/RHBA-2017-1609.html
For a while now the "upstream details" pointed to in messages from
centos-announce have been saying:
Attention: RHN Hosted will reach the
On 06/29/2017 03:53 PM, Yves Bellefeuille wrote:
> I have a new system with an AMD Ryzen 1600 CPU and I'm trying to run
> CentOS, so far without success. The only information I could find was
> a post reporting that CentOS 7 would crash during installation on a
> Ryzen system:
Mark Haney wrote:
> On 07/03/2017 10:52 AM, m.r...@5-cent.us wrote:
>> Chris Olson wrote:
>>> On Monday, July 3, 2017 5:58 AM, "m.r...@5-cent.us"
>>>
>>> wrote:
>>> Chris Olson wrote:
>>>
I went on vacation right after an update to one of our virtual CentOS
6.9
On 07/03/2017 10:52 AM, m.r...@5-cent.us wrote:
Chris Olson wrote:
On Monday, July 3, 2017 5:58 AM, "m.r...@5-cent.us"
wrote:
Chris Olson wrote:
I went on vacation right after an update to one of our virtual CentOS
6.9 systems so it was not restarted for a period of
Chris Olson wrote:
> On Monday, July 3, 2017 5:58 AM, "m.r...@5-cent.us"
> wrote:
> Chris Olson wrote:
>
>> I went on vacation right after an update to one of our virtual CentOS
>> 6.9 systems so it was not restarted for a period of time. Now it will not
>> complete
>
> Having very little experience with such start-up issues, we are at a loss
> to determine how to salvage the CentOS 6.9 virtual machine. Is there a
> standard way to start up a system without any extras like gnome to see if
> we can get a running system? Would it be wise to attempt using
None of the previous kernels will boot properly.
On Monday, July 3, 2017 5:58 AM, "m.r...@5-cent.us"
wrote:
Chris Olson wrote:
> I went on vacation right after an update to one of our virtual CentOS 6.9
> systems so it was not restarted for a period of time. Now it
Chris Olson wrote:
> I went on vacation right after an update to one of our virtual CentOS 6.9
> systems so it was not restarted for a period of time. Now it will not
> complete boot-up with the gnome display never fully launched. A progress
> bar at the bottom of the start-up screen never
We run several Intel-based CentOS machines. They are all at 6.9 or 7.x.
One of each OS is Oracle VirtualBox hosted on an up to date Windows 7 system.
We use these virtual machines for checkout of new applications before they
are loaded on native CentOS platforms. Regular weekly updates are run
18 matches
Mail list logo