Re: [CentOS] kickstart: dracut-initqueue fails due to unresolvable hostname even though network config looks perfectly ok

On Mon, 15 May 2017 at 20:05 zulu, Frank Thommen wrote: > lustre driver https://downloads.hpdd.intel.com/public/lustre/latest-feature-release/el7.3.1611/ ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] kickstart: dracut-initqueue fails due to unresolvable hostname even though network config looks perfectly ok

Hi On 15/05/17 19:30, Tru Huynh wrote: Hi, On Mon, May 15, 2017 at 03:04:03PM +0200, Frank Thommen wrote: This problem still bites us. I've tried to play around with DHCP settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail. I'm happy about /any/ hint. 1) ip route seems ok, but

Re: [CentOS] kickstart: dracut-initqueue fails due to unresolvable hostname even though network config looks perfectly ok

Hi, On Mon, May 15, 2017 at 03:04:03PM +0200, Frank Thommen wrote: > This problem still bites us. I've tried to play around with DHCP > settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail. > > I'm happy about /any/ hint. 1) ip route seems ok, but what does your /etc/resolv.conf looks

Re: [CentOS] centos 7- boot doesn't wait for startup script to complete

On Mon, May 15, 2017 at 04:07:35PM +, KM wrote: > Hello,Nothing I have found has solved this issue.  the service > starts on boot, but the booting process continues.  When I log in my > startup script is still running and finishes up.  that is good at > least, but I'd still like to know how to

[CentOS-announce] CESA-2017:1208 Important CentOS 7 jasper Security Update

CentOS Errata and Security Advisory 2017:1208 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-1208.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64:

[CentOS-announce] CESA-2017:1230 Important CentOS 7 ghostscript Security Update

CentOS Errata and Security Advisory 2017:1230 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-1230.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64:

[CentOS-announce] CESA-2017:1230 Important CentOS 6 ghostscript Security Update

CentOS Errata and Security Advisory 2017:1230 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-1230.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386:

[CentOS-announce] CESA-2017:1208 Important CentOS 6 jasper Security Update

CentOS Errata and Security Advisory 2017:1208 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2017-1208.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386:

[CentOS] plymouth themes problem

Hi all! I was playing with plymouth themes on a c7 box. I found a page on redhat, in their rhel7 documentation that describes how to change to a different plymouth screen: plymouth-set-default-theme --list to find out what themes are installed. then I installed the remaining bunch the yum had

[CentOS] How can kickstart be (re)started manually from the dracut emergency shell?

Hi, this is a side question to my other thread regarding dracut-initqueue network issues. Once I'm thrown into a dracut emergency shell (PXE booted system): How can I restart the kickstart installation process manually from there? Can I at all? Background is, that I'd like to add some

Re: [CentOS] kickstart: dracut-initqueue fails due to unresolvable hostname even though network config looks perfectly ok

This problem still bites us. I've tried to play around with DHCP settings (rd.net.timeout.dhcp, rd.net.dhcp.retry) to no avail. I'm happy about /any/ hint. Cheers frank On 04/24/2017 11:57 PM, Frank Thommen wrote: Hi, kickstarting fails due to problems with host resolution, even though

[CentOS] Supersize io operations (IO block size more than 4KiB) is split in to number of 4KiB blocks

Concern: Supersize io operations (IO block size more than 4KiB) is split in to number of 4KiB blocks Supersize io operations (IO block size more than 4KiB) is split in to number of 4KiB blocks OS: CentOS 7.3 kernel Version: 3.10.0-514.el7.x86_64 Any IO (write) block size more than 4KiB is

Re: [CentOS] Mini PCs

Hello Walter, On Mon, 15 May 2017 09:22:54 +0200 "Walter H." wrote: > On Sun, May 14, 2017 11:00, wwp wrote: > > On Sat, 13 May 2017 13:08:17 +0200 "Walter H." > > wrote: > > > >> On 13.05.2017 00:29, Robert Moskowitz wrote: > >> >

Re: [CentOS] Mini PCs

On Sun, May 14, 2017 11:00, wwp wrote: > On Sat, 13 May 2017 13:08:17 +0200 "Walter H." > wrote: > >> On 13.05.2017 00:29, Robert Moskowitz wrote: >> > I have been working, for the past few years, with armv7 SOCs and have >> > a number of servers working. >> > >> >