[CentOS] Can't boot into GUI: Centos 7 "Server with GUI" option
I'm setting up a new server on Centos 7, running x86_64. Motherboard is a MITAC PD11BICC, running Indian Bay Trail, with a i915 chipset. I installed "Server with GUI", but when it boots I get the "blank screen with a cursor" issue. Decided to see about disabling the i915 driver, by blacklisting it. but I don't think I have the right commands, as when I did that, it appeared on the reboot the i915 driver was still active. vi /etc/modprobe.d/blacklist_i915.conf added the following line to that file blacklist i915 Saved the file. Rebooted. The driver seemed to active upon the reboot. Can someone tell me if this is the correct and full procedure to get rid of this driver. Thanks, Jay ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Okular
On 08/08/2018 10:35 AM, mark wrote: Does anyone know what Magical configuration file determines whether okular give measurements, in the properties of a .pdf, in millimeters, rather than, say, inches or cm or furlongs? mark -- Measurements will always be given in the least convenient units, such as the speed of light in furlongs per fortnight = 1.7998848e+12 Or there abouts. I once in awhile use okular, but never had paid attention to units used. And then on Fedora ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] Okular
Does anyone know what Magical configuration file determines whether okular give measurements, in the properties of a .pdf, in millimeters, rather than, say, inches or cm or furlongs? mark -- Measurements will always be given in the least convenient units, such as the speed of light in furlongs per fortnight ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] systemd equivalent of xinetd 'only_from' and 'banner_fail' attributes
On Wed, 8 Aug 2018 12:59:09 + James Pearson wrote: > James Pearson wrote: > > > > I'm attempting to port an existing xinetd service from CentOS 6 to > > something equivalent with systemd for CentOS 7 > > > > The existing xinetd config uses the attributes 'only_from' to limit > > connections from a limited set of remote hosts and 'banner_fail' to > > print a suitable error message when access is denied > > > > However, I can't find suitable 'equivalents' with systemd > > socket/service files on CentOS 7 > > > > It appears later versions of systemd supports the option > > IPAddressAllow= (which is what I think I need ?) > > > > Does anyone know how to limit the remote hosts that can connect to a > > port with CentOS 7's systemd ? > > > > Also, how to implement the equivalent of 'banner_fail' ? (not > > absolutely required, but nice to have) > > I managed to do what is needed by creating a simple ExecStartPre > script that checks if the $REMOTE_ADDR env var is in a list of my > 'only_from' IP addresses - and exits with zero if it is or exits with > non-zero if not > > The non-zero status from the ExecStartPre script causes the whole > service instance to fail > > The ExecStartPre script also writes my 'banner_fail' message to > stdout when it fails - which is what I want Thanks for taking time to tell us about the solution. /Peter ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] systemd equivalent of xinetd 'only_from' and 'banner_fail' attributes
James Pearson wrote: > > I'm attempting to port an existing xinetd service from CentOS 6 to > something equivalent with systemd for CentOS 7 > > The existing xinetd config uses the attributes 'only_from' to limit > connections from a limited set of remote hosts and 'banner_fail' to > print a suitable error message when access is denied > > However, I can't find suitable 'equivalents' with systemd socket/service > files on CentOS 7 > > It appears later versions of systemd supports the option IPAddressAllow= > (which is what I think I need ?) > > Does anyone know how to limit the remote hosts that can connect to a > port with CentOS 7's systemd ? > > Also, how to implement the equivalent of 'banner_fail' ? (not absolutely > required, but nice to have) I managed to do what is needed by creating a simple ExecStartPre script that checks if the $REMOTE_ADDR env var is in a list of my 'only_from' IP addresses - and exits with zero if it is or exits with non-zero if not The non-zero status from the ExecStartPre script causes the whole service instance to fail The ExecStartPre script also writes my 'banner_fail' message to stdout when it fails - which is what I want James Pearson ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
