Re: [CentOS] C7, removing zoom problem

[Pete Geenhuizen]

I've made to move to Rocky 8 after it was released and there is support 
for MATE and if you prefer lightdm as a window manager.  It has some 
minor quirks, but all in all it works just fine.
I've not tried it yet but there is also a Rocky 9 MATE live image 
available https://docs.rockylinux.org/en/guides/desktop/mate_installation/


Pete

On 2/7/23 23:53, Fred wrote:

ah, that's OK for now, as long as it works.

I'm trying to build up the courage to do a full system upgrade to
Rocky.latest. I hate doing upgrades, it's such a pain in the rear to get
everything working again, and get all my tweaks back into place. I despise
Gnome 3+, and prefer Mate. Someone (EPEL ??)  built Mate for C7, but the
existing binaries for C8 don't work very well, there are none that I know
of for  C9, and AFAIK Rocky is the only Centos clone that supports Mate.
there IS Ubuntu Mate, but I am more comfy with RH-derived systems.

One thing I won't have to do anymore is set up email (used to have my own
domain for email, but moved and can't get a static IP anymore, decided it
was too much bother to do the ddns thing) along with POP3 for my wife to
use. We now just use gmail.

But I see that the time for said upgrade is drawing nearer and nearer.

Fred

On Tue, Feb 7, 2023 at 9:22 PM Ian Mortimer  wrote:


On Mon, 2023-02-06 at 21:13 -0500, Fred wrote:


well, as one of the earlier posters showed how, I did remove the
existing
one then installed the new one (the one that Zoom offers for Centos-
7, not
the one for Centos-8, which has the problem you describe) and voila,
works
like a charm!

Yes but that's the old version - 5.13.4.711 not the latest 5.13.7.683.
"Check for Updates" will tell you there's a new version but you'll be
stuck with that old version until you upgrade from CentOS 7 to
something newer.


--
Ian
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos



--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] LibreOffice on CentOS 7

[Pete Geenhuizen]

Why not simply download the latest and greatest version LibreOffice from 
their we site I've been doing that for several years on both Centos 7 
and now Rocky 8 and it has worked without fail.


On 11/3/22 10:46, H wrote:

On 11/02/2022 03:53 PM,jefflp...@twc.com  wrote:

3.10.0-1160.76.1.el7.x86_64. I check for updates every day.

Jeff

-From: "H"
To: "CentOS mailing list"
Cc:
Sent: Wednesday November 2 2022 6:28:52AM
Subject: Re: [CentOS] LibreOffice on CentOS 7

  On November 1, 2022 5:13:49 PM EDT, Josh Boyer  wrote:
  >On Tue, Nov 1, 2022, 5:05 PM H  wrote:
  >
  >> I am running the default version of LibreOffice 5.3.6.1 on CentOS
7.
  >This
  >> is quite an old version and has a serious bug in Calc, possibly an
  >errant
  >> pointer, that frequently locks up spreadsheets.
  >>
  >> Has anyone installed a later version of LO on CentOS 7? I would
  >prefer a
  >> version that is not flatpak, snap or appimage etc...
  >>
  >
  >Could you elaborate why you would like to avoid those packaging
  >formats?
  >
  >josh
  >___
  >CentOS mailing list
  >CentOS@centos.org
  >https://lists.centos.org/mailman/listinfo/centos
  />
  A general dislike of anything that gets between the operating system
and an application potentially introducing its own complications.

  Does anyone happen to know what the latest native version for CentOS
7 is?
  ___
  CentOS mailing list
  CentOS@centos.org
  https://lists.centos.org/mailman/listinfo/centos
  />
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

That seems to be version 3.10.0, or? As I wrote, I am running 5.3.6.1...

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos



--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Compatible SATA controller needed

[Pete Geenhuizen]

I've gone through the BIOS and tried all the combinations that were 
available but still no joy.  I used ELRepo's method of determining the 
card type, and the result was none yielded a positive result.


After trying all combinations  my only course of action is to fins a 
card that is compatible and ignore the controllers that I currently have.


Thanks

On 3/27/22 16:08, Robert Heller wrote:

At Sun, 27 Mar 2022 12:23:21 -0700 CentOS mailing list  
wrote:


On Sun, Mar 27, 2022 at 11:55 AM Pete Geenhuizen
wrote:


I'm trying to install Centos 8 on an older PC but it fails because the
SATA controller isn't supported.
Anyone have a source for a PCI/ePCI controller card that is compatible
with Centos 8?
Thanks
Pete


Your controller might be supported by one of the ELRepo's kmod packages.
This can be checked if you provide the device ID pairing [:] as
reported by 'lspci -nn'.

Also: what BIOS mode is the SATA controller operating in? The SATA firmware in
some PCs implement various "weird" modes, including "RAID" (no, not really
hardware RAID, just some kind of half BIOS half MS-Windows driver software
RAID hack), Make sure the SATA controller is in AHCI mode and not in some
other mode. If it is in AHCI mode, it might just work out-of-the-box.


Akemi
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos





--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Compatible SATA controller needed

[Pete Geenhuizen]

I've already checked ELRepo for a possible driver and have tried some 
that looked promising but no success.

Thanks

On 3/27/22 15:23, Akemi Yagi wrote:

On Sun, Mar 27, 2022 at 11:55 AM Pete Geenhuizen
wrote:


I'm trying to install Centos 8 on an older PC but it fails because the
SATA controller isn't supported.
Anyone have a source for a PCI/ePCI controller card that is compatible
with Centos 8?
Thanks
Pete


Your controller might be supported by one of the ELRepo's kmod packages.
This can be checked if you provide the device ID pairing [:] as
reported by 'lspci -nn'.

Akemi
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos



--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Compatible SATA controller needed

[Pete Geenhuizen]

I'm trying to install Centos 8 on an older PC but it fails because the 
SATA controller isn't supported.
Anyone have a source for a PCI/ePCI controller card that is compatible 
with Centos 8?

Thanks
Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Warning: No matches found for: clamav on CentOS Linux release 7.9.2009 (Core)

[Pete Geenhuizen]

The latest version in in epel-testing, yum  --enablerepo=epel-testing 
update clam* will do the trick


On 7/19/21 5:04 AM, Kaushal Shriyan wrote:

Hi,

I am running CentOS Linux release 7.9.2009 (Core) and installed epel
repository.

# rpm -qa | grep epel
epel-release-7-13.noarch
# cat /etc/redhat-release
CentOS Linux release 7.9.2009 (Core)
#yum search clamav
Loaded plugins: fastestmirror
Determining fastest mirrors
  * base: mirrors.piconets.webwerks.in
  * extras: mirrors.piconets.webwerks.in
  * updates: mirrors.piconets.webwerks.in
base

 | 3.6 kB  00:00:00
docker-ce-stable

 | 3.5 kB  00:00:00
elastic-7.x

| 1.3 kB  00:00:00
extras

 | 2.9 kB  00:00:00
ius

| 1.3 kB  00:00:00
mariadb

| 2.9 kB  00:00:00
nginx

| 2.9 kB  00:00:00
updates

| 2.9 kB  00:00:00
(1/10): base/7/x86_64/group_gz

 | 153 kB  00:00:00
(2/10): extras/7/x86_64/primary_db

 | 242 kB  00:00:00
(3/10): elastic-7.x/primary

| 288 kB  00:00:00
(4/10): docker-ce-stable/7/x86_64/primary_db

 |  62 kB  00:00:00
(5/10): docker-ce-stable/7/x86_64/updateinfo

 |   55 B  00:00:00
(6/10): ius/x86_64/primary

 | 100 kB  00:00:01
(7/10): updates/7/x86_64/primary_db

| 8.8 MB  00:00:04
(8/10): base/7/x86_64/primary_db

 | 6.1 MB  00:00:05
(9/10): nginx/7/x86_64/primary_db

|  67 kB  00:00:04
(10/10): mariadb/primary_db

|  36 kB  00:00:05
elastic-7.x

   880/880
ius

   467/467
Warning: No matches found for: clamav
No matches found

Am I missing anything? Please suggest further. Thanks in Advance.

Best Regards,

Kaushal
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos



--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Looking for C8 AMD help

[Pete Geenhuizen]

Hmm, I guess that I have something wrong with my kickstart configuration 
because all that I can find is

libsss_autofs-2.2.0-19.el8_1.1.x86_64.

Thanks for the heads up
Pete

On 4/23/20 9:08 PM, Chris Schanzle wrote:

On 4/23/20 4:23 PM, Pete Geenhuizen wrote:
I'm migrating from C7 to C8.  I'm currently using autofs, but alas 
autofs has been dropped in C8 for the AMD automounter.


Nope, it's in there! 
8/BaseOS/x86_64/os/Packages/autofs-5.1.4-35.el8.x86_64.rpm



I have some very ancient knowledge of AMD, I used it when it was 
first introduced many years ago on Solaris and moved to Sun's 
automounter when it was introduced.

So now it's back to square one.
I used automount2amd to convert one of my existing maps, included it 
in the amd.conf file and tried it out.  I don't get any syntax errors 
so I guess that the map syntax is correct, but amd fails to mount the 
remote filesystem and generates these errors  in messages.



Apr 23 16:04:29 localhost.my.domain amd[19389]: matched default 
selectors "type:=nfs;opts:=rw,grpid,nosuid,utimeout=600"
Apr 23 16:04:29 localhost.my.domain amd[19389]: key new: map selector 
host (=localhost) did not match remotehost
Apr 23 16:04:29 localhost.my.domain amd[19389]: merge rem/opts 
"rw,grpid,nosuid,utimeout=600" add "fstype=nfs,vers=4,soft,intr" => 
"rw,grpid,nosuid,utimeout=600,fstype=nfs,vers=4,soft,intr"
Apr 23 16:04:29 localhost.my.domain amd[19389]: Map entry 
host==remotehost;type:=link;fs:=/export/data/& for /repo/new did not 
match
Apr 23 16:04:29 localhost.my.domain amd[19389]: merge rem/opts 
"rw,grpid,nosuid,utimeout=600" add "fstype=nfs,vers=4,soft,intr" => 
"rw,grpid,nosuid,utimeout=600,fstype=nfs,vers=4,soft,intr"
Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version: 
returning NFS(4,tcp) on host remotehost.my.domain
Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version: 
NFS(4,udp) failed for remotehost.my.domain: RPC: Unable to receive
Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version: 
NFS(3,udp) failed for remotehost.my.domain: RPC: Unable to receive
Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version: 
NFS(2,udp) failed for remotehost.my.domain: RPC: Unable to receive
Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version: 
returning NFS(0,udp) on host remotehost.my.domain
Apr 23 16:04:29 localhost.my.domain amd[19389]: Using NFS version 4, 
protocol tcp on host remotehost.my.domain
Apr 23 16:04:29 localhost.my.domain amd[19389]: changing 
remotehost.my.domain's ping value from 30 to 30
Apr 23 16:04:29 localhost.my.domain amd[19389]: Trying mount of 
remotehost:/export/data/& on /.automount/remotehost/export/data/& 
fstype nfs mount_type non-autofs
Apr 23 16:04:31 localhost.my.domain amd[19389]: Trying mount of 
remotehost:/export/data/& on /.automount/remotehost/export/data/& 
fstype nfs mount_type non-autofs
Apr 23 16:04:32 localhost.my.domain amd[19389]: file server 
remotehost.my.domain, type nfs, state starts down
Apr 23 16:04:49 localhost.my.domain amd[19389]: "/repo/new" on 
//nil// timed out (flags 0x20)


I'm using firewalld  on both hosts and allow these services mountd 
nfs rpc-bind and protocols 111/tcp and 111/udp  all of which allow 
autofs to work flawlessly, I've tried turning firewalld off which 
made no difference.


Here's my /etc/amd.remote file looks like
new \
  -addopts:=fstype=nfs,vers=4,soft,intr \
  host==remotehost;type:=link;fs:=/export/data/& \
  rhost:=remotehost;rfs:=/export/data/&

Any assistance in pointing me in the right direction would be greatly 
appreciated.

Pete


sudo dnf -y install autofs # for the win!

consider removing what I think you have is am-utils.





--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Looking for C8 AMD help

[Pete Geenhuizen]

I'm migrating from C7 to C8.  I'm currently using autofs, but alas 
autofs has been dropped in C8 for the AMD automounter.
I have some very ancient knowledge of AMD, I used it when it was first 
introduced many years ago on Solaris and moved to Sun's automounter when 
it was introduced.

So now it's back to square one.
I used automount2amd to convert one of my existing maps, included it in 
the amd.conf file and tried it out.  I don't get any syntax errors so I 
guess that the map syntax is correct, but amd fails to mount the remote 
filesystem and generates these errors  in messages.



Apr 23 16:04:29 localhost.my.domain amd[19389]: matched default 
selectors "type:=nfs;opts:=rw,grpid,nosuid,utimeout=600"
Apr 23 16:04:29 localhost.my.domain amd[19389]: key new: map selector 
host (=localhost) did not match remotehost
Apr 23 16:04:29 localhost.my.domain amd[19389]: merge rem/opts 
"rw,grpid,nosuid,utimeout=600" add "fstype=nfs,vers=4,soft,intr" => 
"rw,grpid,nosuid,utimeout=600,fstype=nfs,vers=4,soft,intr"
Apr 23 16:04:29 localhost.my.domain amd[19389]: Map entry 
host==remotehost;type:=link;fs:=/export/data/& for /repo/new did not match
Apr 23 16:04:29 localhost.my.domain amd[19389]: merge rem/opts 
"rw,grpid,nosuid,utimeout=600" add "fstype=nfs,vers=4,soft,intr" => 
"rw,grpid,nosuid,utimeout=600,fstype=nfs,vers=4,soft,intr"
Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version: 
returning NFS(4,tcp) on host remotehost.my.domain
Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version: 
NFS(4,udp) failed for remotehost.my.domain: RPC: Unable to receive
Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version: 
NFS(3,udp) failed for remotehost.my.domain: RPC: Unable to receive
Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version: 
NFS(2,udp) failed for remotehost.my.domain: RPC: Unable to receive
Apr 23 16:04:29 localhost.my.domain amd[19389]: get_nfs_version: 
returning NFS(0,udp) on host remotehost.my.domain
Apr 23 16:04:29 localhost.my.domain amd[19389]: Using NFS version 4, 
protocol tcp on host remotehost.my.domain
Apr 23 16:04:29 localhost.my.domain amd[19389]: changing 
remotehost.my.domain's ping value from 30 to 30
Apr 23 16:04:29 localhost.my.domain amd[19389]: Trying mount of 
remotehost:/export/data/& on /.automount/remotehost/export/data/& fstype 
nfs mount_type non-autofs
Apr 23 16:04:31 localhost.my.domain amd[19389]: Trying mount of 
remotehost:/export/data/& on /.automount/remotehost/export/data/& fstype 
nfs mount_type non-autofs
Apr 23 16:04:32 localhost.my.domain amd[19389]: file server 
remotehost.my.domain, type nfs, state starts down
Apr 23 16:04:49 localhost.my.domain amd[19389]: "/repo/new" on //nil// 
timed out (flags 0x20)


I'm using firewalld  on both hosts and allow these services mountd nfs 
rpc-bind and protocols 111/tcp and 111/udp  all of which allow autofs to 
work flawlessly, I've tried turning firewalld off which made no difference.


Here's my /etc/amd.remote file looks like
new \
  -addopts:=fstype=nfs,vers=4,soft,intr \
  host==remotehost;type:=link;fs:=/export/data/& \
  rhost:=remotehost;rfs:=/export/data/&

Any assistance in pointing me in the right direction would be greatly 
appreciated.

Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Pidgin fails to connect google

[Pete Geenhuizen]

I recently upgraded to Centos 7.7 and when I rebooted everything seemed 
to be OK except that pidgin failed to  connect to gtalk with the error 
SSL Handshake Failed
After trying several configuration changes with no luck I tried pidgin 
on a host that was still running Centos 7.6 and it had the same error.
Based on that I'm concluding that it doesn't appear to have anything to 
do with Centos 7,7 but that the failure is coincidental.

Does anyone know what the problem is and how to resolve it?
Thanks
Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] nvidia on 7.6

[Pete Geenhuizen]

On 03/07/2019 01:56 AM, Phil Perry wrote:

On 06/03/2019 23:03, Stephen John Smoogen wrote:

Thank you Stephen. I assumed because they were pulling a dependency 
from epel that they were also from epel.




Been out of town, yes I goofed vlc, smplayer, mplayer, and ffmpeg aren't 
in EPEL. and are in rpm-fusion.  I've resolved all of that and got them 
all installed from nux-dextop.


With all that done now when I run update I get the following error

Error: Package: nvidia-x11-drv-340xx-libs-340.107-2.el7_6.elrepo.x86_64 
(@elrepo)

   Requires: nvidia-x11-drv-340xx = 340.107-2.el7_6.elrepo
   Removing: nvidia-x11-drv-340xx-340.107-2.el7_6.elrepo.x86_64 
(@elrepo)

   nvidia-x11-drv-340xx = 340.107-2.el7_6.elrepo
   Updated By: 
nvidia-x11-drv-340xx-340.107-3.el7_6.elrepo.x86_64 (elrepo)

   nvidia-x11-drv-340xx = 340.107-3.el7_6.elrepo

Needless to say I'm a tad confused.

Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] nvidia on 7.6

[Pete Geenhuizen]

On 03/06/2019 04:21 PM, Phil Perry wrote:

On 06/03/2019 19:30, Pete Geenhuizen wrote:


That is all good and well, but my problem is that I now can't install

vlc smplayer mplayer, or  ffmpeg-libs because they need 
ocl-icd-2.2.12-1.el7.x86_64from epel.
I tried to roll back to the previous version via yum history undo but 
previous versions are no longer avaialble.




Do they have a hard coded Requires for the ocl-icd package or just an 
auto-generated Requires for the libOpenCL.so lib?


If it's the former then the packages in epel need fixing. If it's the 
latter then the nvidia package will meet that requirement. You can 
either force uninstall ocl-icd, or uninstall ocl-icd and any 
dependencies, install/update the nvidia packages and then reinstall 
the package you require that depend on libOpenCL.so

Phil,
I don't know if it's a hard coded requires ot auto-generated.
Right now I've removed the rpms that need ocl-icd, updated nvidia but 
when I attempt to install vlc smplayer mplayer, or  ffmpeg-libs it fails 
because it wants to install ocl-icd-2.2.12-1.el7.x86_64 from epel.

I guess that that means that its a hard coded requirement, is that correct?
Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] nvidia on 7.6

[Pete Geenhuizen]

On 03/06/2019 09:59 AM, Fred Smith wrote:



I tried to install this and ran into a conflict

--> Processing Conflict:
nvidia-x11-drv-340xx-340.107-2.el7_6.elrepo.x86_64 conflicts ocl-icd
--> Finished Dependency Resolution
Error: nvidia-x11-drv-340xx conflicts with ocl-icd-2.2.12-1.el7.x86_64

I removed ocl-icd and installed the package, but needless to say I
can't get ocl-icd to install which means that I cant install video
players, vlc smplayer mplayer, or  ffmpeg-libs.

I asked the same question recently and Phil informed me that the
ocl-icd now comes in one of the nvidia  packages, so you no longer
need the one from epel.

That is all good and well, but my problem is that I now can't install

vlc smplayer mplayer, or  ffmpeg-libs because they need 
ocl-icd-2.2.12-1.el7.x86_64from epel.
I tried to roll back to the previous version via yum history undo but previous 
versions are no longer avaialble.

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] nvidia on 7.6

[Pete Geenhuizen]

On 03/02/2019 05:41 AM, Phil Perry wrote:


Hi Gerry,

I've updated the nvidia 340xx legacy package set for el7.6, and 
released the packages to the elrepo testing repository.


Please could you test them and let me know if they work as expected. 
To install:


yum --enablerepo=elrepo-testing install kmod-nvidia-340xx 
nvidia-x11-drv-340xx nvidia-x11-drv-340xx-libs


if you need 32-bit support then you will also need to install the 
corresponding 
nvidia-x11-drv-340xx-libs-340.107-2.el7_6.elrepo.i686.rpm package.


Thinking about it, I'm not sure these packages are going to work as 
the 340 series NVIDIA driver predates the conversion to GLVND (support 
was added in version 361), see here:


https://devtalk.nvidia.com/default/topic/915640/multiple-glx-client-libraries-in-the-nvidia-linux-driver-installer-package/ 



but I have no way to test them so I'll leave that to you.

Phil

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Phil,
I tried to install this and ran into a conflict

--> Processing Conflict: 
nvidia-x11-drv-340xx-340.107-2.el7_6.elrepo.x86_64 conflicts ocl-icd

--> Finished Dependency Resolution
Error: nvidia-x11-drv-340xx conflicts with ocl-icd-2.2.12-1.el7.x86_64

I removed ocl-icd and installed the package, but needless to say I can't 
get ocl-icd to install which means that I cant install video players, 
vlc smplayer mplayer, or  ffmpeg-libs.


Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Centos 7 add-on serial cards

[Pete Geenhuizen]

On 01/29/18 09:19, Fred Smith wrote:

On Mon, Jan 29, 2018 at 07:00:02AM -0500, Pete Geenhuizen wrote:


On 01/28/18 20:15, Fred Smith wrote:
Thanks for the suggestion.

I looked at them with setserial, but I have no familiarity with the
program to know what to change.

setserial -ag /dev/ttyS*
/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
     Baud_base: 115200, close_delay: 50, divisor: 0
     closing_wait: 3000
     Flags: spd_normal skip_test

/dev/ttyS1, Line 1, UART: 16550A, Port: 0x8000, IRQ: 17
     Baud_base: 115200, close_delay: 50, divisor: 0
     closing_wait: none
     Flags: spd_normal skip_test

/dev/ttyS2, Line 2, UART: 16550A, Port: 0x8400, IRQ: 17
     Baud_base: 115200, close_delay: 50, divisor: 0
     closing_wait: none
     Flags: spd_normal skip_test

/dev/ttyS3, Line 3, UART: unknown, Port: 0x02e8, IRQ: 3
     Baud_base: 115200, close_delay: 50, divisor: 0
     closing_wait: 3000
     Flags: spd_normal

I changed the closing_wait: on ttyS1 to match ttyS0, but that didn't
do anything, so there must be more to it.

Pete

it has been so many years since I've fooled with a serial port that I
don't remember any details. however, this page may prove helpful, it
appears to contain a lot of potentially useful info:

http://www.tldp.org/HOWTO/Serial-HOWTO-8.html

and also this one (linked from the document above:

http://www.tldp.org/HOWTO/Serial-HOWTO-16.html#slow_

Fred

It's been many years for me as well.  From C4 to C6 it just worked and I 
thought nothing more of it, but now I'm confronted with this issue.
Thanks for the info and the links hopefully I can glean something out of 
it that will solve my dilemma.


Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Centos 7 add-on serial cards

[Pete Geenhuizen]

On 01/28/18 20:15, Fred Smith wrote:

On Sun, Jan 28, 2018 at 12:10:29PM -0500, Pete Geenhuizen wrote:

I'm upgrading from CentOS6 to CentOS 7.

I run 2 weather stations on C6 and have one of them attached to
ttyS0 which is on the motherboard, and the other to ttyS2 which in
on an add-on PCI serial card.

I'm migrating the weather stations another host running C7 which has
a similar hardware configuration.  When I connect the weather
station to ttyS0 everything works fine, but when I try to use ttyS1
or ttyS2 nothing happens.

The OS identifies all 3 ports, and I've already tried several
different serial cards several of the slots on the motherboard all
have yielded the same result.  I've even gone so far as to try to
get this to work on another computer running C7 with the same
result, success on ttyS0, but nothing nothing when I try ttyS1 or
ttyS2.

I'm thinking that this might be a driver issue, but having used
several different cards I'm just not sure.

Any assistance would be greatly appreciated.

Pete

Wondering if you've tried poking at them with 'setserial'?


Thanks for the suggestion.

I looked at them with setserial, but I have no familiarity with the 
program to know what to change.


setserial -ag /dev/ttyS*
/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
    Baud_base: 115200, close_delay: 50, divisor: 0
    closing_wait: 3000
    Flags: spd_normal skip_test

/dev/ttyS1, Line 1, UART: 16550A, Port: 0x8000, IRQ: 17
    Baud_base: 115200, close_delay: 50, divisor: 0
    closing_wait: none
    Flags: spd_normal skip_test

/dev/ttyS2, Line 2, UART: 16550A, Port: 0x8400, IRQ: 17
    Baud_base: 115200, close_delay: 50, divisor: 0
    closing_wait: none
    Flags: spd_normal skip_test

/dev/ttyS3, Line 3, UART: unknown, Port: 0x02e8, IRQ: 3
    Baud_base: 115200, close_delay: 50, divisor: 0
    closing_wait: 3000
    Flags: spd_normal

I changed the closing_wait: on ttyS1 to match ttyS0, but that didn't do 
anything, so there must be more to it.


Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Centos 7 add-on serial cards

[Pete Geenhuizen]

I'm upgrading from CentOS6 to CentOS 7.

I run 2 weather stations on C6 and have one of them attached to ttyS0 
which is on the motherboard, and the other to ttyS2 which in on an 
add-on PCI serial card.


I'm migrating the weather stations another host running C7 which has a 
similar hardware configuration.  When I connect the weather station to 
ttyS0 everything works fine, but when I try to use ttyS1 or ttyS2 
nothing happens.


The OS identifies all 3 ports, and I've already tried several different 
serial cards several of the slots on the motherboard all have yielded 
the same result.  I've even gone so far as to try to get this to work on 
another computer running C7 with the same result, success on ttyS0, but 
nothing nothing when I try ttyS1 or ttyS2.


I'm thinking that this might be a driver issue, but having used several 
different cards I'm just not sure.


Any assistance would be greatly appreciated.

Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /lib/firmware/microcode.dat update on CentOS 6

[Pete Geenhuizen]

On 01/18/18 11:31, Matthew Miller wrote:

On Thu, Jan 18, 2018 at 11:01:18AM -0500, Pete Geenhuizen wrote:

Do we update the microcode now or do we wait until the latest
microcode_ctl rpm is available and then tackle this issue?

Check with your hardware vendor for BIOS/EFI firmware updates. Apply
those.



Thanks for the reply, but you missed what I was asking.  I've already 
downloaded the appropriate files from the links that Johnny provided in 
a previous posting.
My question is, do we wait until the latest microcode_ctl rpm is 
installed or do it now?  My concern is that if I do it now the new rpm 
might undo what I've done.


Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /lib/firmware/microcode.dat update on CentOS 6

[Pete Geenhuizen]

On 01/18/18 11:31, Matthew Miller wrote:

On Thu, Jan 18, 2018 at 11:01:18AM -0500, Pete Geenhuizen wrote:

Do we update the microcode now or do we wait until the latest
microcode_ctl rpm is available and then tackle this issue?

Check with your hardware vendor for BIOS/EFI firmware updates. Apply
those.



Thanks for the reply, but you missed what I was asking.  I've already 
downloaded the appropriate files from the links that Johnny provided in 
a previous posting.
My question is, do we wait until the latest microcode_ctl rpm is 
installed or do it now?  My concern is that if I do it now the new rpm 
might undo what I've done.


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /lib/firmware/microcode.dat update on CentOS 6

[Pete Geenhuizen]

On 01/18/18 09:01, Johnny Hughes wrote:

On 01/18/2018 07:51 AM, Phelps, Matthew wrote:

On Thu, Jan 18, 2018 at 5:03 AM, Johnny Hughes  wrote:

So, if we applied the previous microcode update, and all our machines
rebooted OK, then we don't need to fallback?

Also, do we know if the updated CentOS microcode RPM reverted the microcode
for *all* Intel CPUs, or just the ones that had issues? In other words, if
I apply the latest microcode update to our 100+ machines (which all have
the previous update, and are OK) will they revert to a vulnerable state?



It reverted for all .. but, your machines may or may not be protected as
only a subset of machines were updated with the original microcode from
Intel.

It is your call as to what you install .. but the correct method is to
install the current microcode_ctl .. and then research your specific
machine, its CPU, chipset, firmware .. go to the vendor and make sure
you get all the things necessary to mitigate the issues.  It will be
different for each CPU vendor (Intel or AMD), each CPU / Chipset combo,
and even each vendor (Dell may have new firmware for x and y but not z
models, etc.)

There is no one size fits all update for this issue.


OK, so color me confused about the timing in all this.

Do we update the microcode now or do we wait until the latest 
microcode_ctl rpm is available and then tackle this issue?


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] SOLVED Centos 7 Mate desk top

[Pete Geenhuizen]

On 09/27/17 18:18, Frank Cox wrote:

On Wed, 27 Sep 2017 17:22:14 -0400
Pete Geenhuizen wrote:

~/.config/user-dirs.dirs


Frank,
Perfect, that was it. thanks a lot.
Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Centos 7 Mate desk top

[Pete Geenhuizen]

I upgraded to C 7.4 from C 6.9 on my laptop and all was well.  As with 
C6 and the other C7 hosts that I have, if launch a terminal from the 
desktop it opens in [ user@host Desktop ]$ which is just fine.


I restored parts of my C 6.9 home into C7.4 and now everything shows up 
on my desktop and when I open a terminal it now opens up in  [ user@host 
~ ]$


Obviously I overwrote the setting, that controls where the terminal 
opens.  I've searched high and low but for the life of me I can't 
determine where that parameter is set.  I've done some searches but 
haven't been able to get the right incantation that would yield an answer


Does anyone know how I can resolve this dilemma?

Thanks

Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] SOLVED upgrade or install to Centos 7.4.1708

[Pete Geenhuizen]

After trying the suggestions offered here and various other suggestions 
that I found through various searches I finally solved the problem by 
ditching the on board graphics and installing a graphics card.



On 09/19/17 11:01, Pete Geenhuizen wrote:
I upgraded from 7.3 to 7.4 over the weekend.  Everything went well 
except that I can't login because the screen is black with a cursor.


If reboot boot the 7.3 kernel 3.10.0-514.26.2.el7.x86_64 kernel 
everything works just fine, so my guess is that there's a kernel issue 
with the hardware, specifically the Skylake processor.


Has anyone else run into this problem and if so can how I resolve the 
problem other than using the previous kernel?


ASUSTeK COMPUTER INC.  Z170M-PLUS
VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz Skylake

Any help with this would be greatly appreciated.

Pete



--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] upgrade or install to Centos 7.4.1708

[Pete Geenhuizen]

On 09/20/17 10:41, Gregory P. Ennis wrote:


I upgraded from 7.3 to 7.4 over the weekend.  Everything went well
except that I can't login because the screen is black with a cursor.

If reboot boot the 7.3 kernel 3.10.0-514.26.2.el7.x86_64 kernel
everything works just fine, so my guess is that there's a kernel issue
with the hardware, specifically the Skylake processor.

Has anyone else run into this problem and if so can how I resolve the
problem other than using the previous kernel?

ASUSTeK COMPUTER INC.  Z170M-PLUS
VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz Skylake

Any help with this would be greatly appreciated.

Pete



Pete,

I have had various assortment of problems with 7.4 to the point that I
quit upgrading the rest of our PC's with 7.4 until the problems are
identified and fixed.  The only work around that I could come up with is
to use the last 7.3 os which at least made each unit usable.

As you know, most of the time these upgrades have been seamless because
the Centos team has done a wonderful job.  However, the upgrade to 7.4
has some problems, and I decided to stop the upgrade of our remaining
units until 7.4 works as well as 7.3.

Greg

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Greg,
I've done 5 upgrades so far without any issues.  This is the first one 
that has a problem and after some experimenting it looks like the kernel 
is identifying both the analog and digital ports and making the digital 
display the primary.  I use a KVM switch and needless to say it's a 
royal pain to have to switch back and forth to accommodate this one 
host.  Like you I settled on using th3 previous perfectly working 7.3 
kernel, not optimum but it does work.


I've also decided to get a graphics card in lieu of the on-board 
graphics card in the hope that that will solve the issue with the 7.4 
kernel.


Agreed you do get used to these upgrades working seamlessly and it's a 
bummer when occasionally things don't work out exactly as planned.


Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] upgrade or install to Centos 7.4.1708

[Pete Geenhuizen]

On 09/19/17 11:58, Richard wrote:




Date: Tuesday, September 19, 2017 11:53:24 -0400
From: Pete Geenhuizen <p...@geenhuizen.net>

On 09/19/17 11:44, m.r...@5-cent.us wrote:

Pete Geenhuizen wrote:

I upgraded from 7.3 to 7.4 over the weekend.  Everything went
well except that I can't login because the screen is black with a
cursor.

If reboot boot the 7.3 kernel 3.10.0-514.26.2.el7.x86_64 kernel
everything works just fine, so my guess is that there's a kernel
issue with the hardware, specifically the Skylake processor.


Video, not the CPU, unless the CPU's also doing video.

  mark, fighting 7.4 and two users who need the 304 NVidia
  drivers



Agreed if I was using an add-on video card, however I'm just using
the no-board video.



I'm using 7.4/Mate on a Dell machine with Skylake i5-7500/Graphics
630, without any issues. I installed 7.3 then did initial updates via
CR, and then the final ones when released the other day. Had to
change my default mate theme (due to gtk2/3 issues) but otherwise all
has been fine.

Hmm I did the same thing other than the Dell and i5-7500, I didn't use 
CR but waited for the official release.  I wonder if I'm experiencing 
the same theme issue with my mate these  If that is the what should I 
look for to verify that gtk2/3 is the issue, or what theme are you using?


Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] upgrade or install to Centos 7.4.1708

[Pete Geenhuizen]

On 09/19/17 11:44, m.r...@5-cent.us wrote:

Pete Geenhuizen wrote:

I upgraded from 7.3 to 7.4 over the weekend.  Everything went well
except that I can't login because the screen is black with a cursor.

If reboot boot the 7.3 kernel 3.10.0-514.26.2.el7.x86_64 kernel
everything works just fine, so my guess is that there's a kernel issue
with the hardware, specifically the Skylake processor.


Video, not the CPU, unless the CPU's also doing video.

 mark, fighting 7.4 and two users who need the 304 NVidia drivers

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Agreed if I was using an add-on video card, however I'm just using the 
no-board video.


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] upgrade or install to Centos 7.4.1708

[Pete Geenhuizen]

I upgraded from 7.3 to 7.4 over the weekend.  Everything went well 
except that I can't login because the screen is black with a cursor.


If reboot boot the 7.3 kernel 3.10.0-514.26.2.el7.x86_64 kernel 
everything works just fine, so my guess is that there's a kernel issue 
with the hardware, specifically the Skylake processor.


Has anyone else run into this problem and if so can how I resolve the 
problem other than using the previous kernel?


ASUSTeK COMPUTER INC.  Z170M-PLUS
VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz Skylake

Any help with this would be greatly appreciated.

Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Gnome weather applet stranded

[Pete Geenhuizen]

Thanks Nux, works just fine on Centos 6.8


On 08/25/16 04:27, Nux! wrote:

I've patched libgweather with the same MATE patch and it seems to be working 
fine.
Give it a try
http://li.nux.ro/download/nux/tmp/libgweather6/

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -

From: "isdtor" 
To: "CentOS mailing list" 
Sent: Wednesday, 24 August, 2016 15:19:20
Subject: [CentOS] Gnome weather applet stranded
The Gnome weather report applet has ceased working on CentOS5/6.
http://weather.noaa.gov/ says "This service is no longer available". Are there
any good alternatives? I liked the applet as it allowed the use of a custom
radar map.

As I just discovered, the weather functionality of the CentOS6 Gnome clock
applet was using the same service.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] update clamav to 0.99.2

[Pete Geenhuizen]

I'm running 6.8 and now it all makes sense.

Thanks

On 07/09/16 09:17, Duncan Brown wrote:

On 09/07/2016 14:15, Walter H. wrote:

On 09.07.2016 14:39, Pete Geenhuizen wrote:

I don't see it either.

On 07/09/16 08:36, Walter H. wrote:

On 07.07.2016 22:19, Helmut Drodofsky wrote:

Helo,

update is in EPEL repository.


strange, here it isn't ...

the reason:  at the moment clamav 0.99.2 is only EL7, EL6 ist at 0.99.1
https://dl.fedoraproject.org/pub/epel/6/x86_64/
https://dl.fedoraproject.org/pub/epel/7/x86_64/c/
so OP has installed at CentOS 7



it's in testing for el6


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] update clamav to 0.99.2

[Pete Geenhuizen]

I don't see it either.

On 07/09/16 08:36, Walter H. wrote:

On 07.07.2016 22:19, Helmut Drodofsky wrote:

Helo,

update is in EPEL repository.


strange, here it isn't ...




___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] Shorewall and the latest kernel problem

[Pete Geenhuizen]

I just installed the latest kernel 2.6.32-573.8.1.el6.x86_64 and when I 
rebooted it shorewall (shorewall-4.5.4-1.el6.noarch) failed with the 
following error


ERROR: a non-empty masq file requires NAT in your kernel and iptables 
/etc/shorewall/masq (line 15)


Question is is this a problem in the kernel or is it a problem in 
Shorewall?


Booting the previous kernel allowed shorewall to start normally.

Any one else seen this error, if so what's the fix?

Any help would be greatly appreciated.

Pete

--
If money can fix it, it's not a problem.
 -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Shorewall and the latest kernel problem

[Pete Geenhuizen]

On 11/12/15 10:46, Marcelo Ricardo Leitner wrote:

Em 12-11-2015 11:12, Pete Geenhuizen escreveu:

That points to something different in kernel. What is your 'previous' 
kernel? Sounds like the nat modules aren't being loaded, for some reason.


  Marcelo

Marcelo,
Thanks for the input, it works fine in 2.6.32-573.7.1.el6.x86_64, and 
yeah I would tend to agree with you that it's more likely as not kernel 
related.  Of course it's possible I suppose that the kernel has changed 
slightly enough that the shorewall rpm needs to be updated.


Thanks
Pete

--
If money can fix it, it's not a problem.
 -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] automounter with users home directories on centos 7.

[Pete Geenhuizen]

Correct nfs is working and there aren't any firewall issues.

The problem is probably related to the way and steps that automountd 
takes to perform the mount, which is probably related to the fact that 
/home exists.
The quickest way to figure that out is to mv /home to /home- and then 
try automountd again.  When and autofs file system is access automountd 
will check that the mount point exists and create it if not and then 
perform the mount.


In all this you might have to restart autofs on the client.

Pete


On 09/10/15 13:10, Jason Welsh wrote:


[root@server2 home]# mount server1:/home/jason /home/jason
[root@server2 home]#
[root@server2 home]# ls /home/jason/
Desktop  Documents  Downloads  Music  mylogfile.txt  Pictures Public  
Templates  Videos

[root@server2 home]# df -h /home/jason/
Filesystem   Size  Used Avail Use% Mounted on
server1:/home/jason  297M   19M  278M   7% /home/jason
[root@server2 home]#

so it works manually, just not with the automounter.

Jason



On 09/09/2015 05:35 PM, James A. Peltier wrote:

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos



--
If money can fix it, it's not a problem.
 -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] automounter with users home directories on centos 7.

[Pete Geenhuizen]

Not tried automount with Centos 7 nor with selinux.

With that said autofs relies on nfs mounting to work, so have you 
started there by attempting to manually mount /home?


Another place to look is at the hostname.  I've had problems where auto 
mount doesn't like the short name and insists on using a FQDN, to get 
around that you could try using the IP address rather than the hostname.


On 09/09/15 16:31, Jason Welsh wrote:

showmount -e


--
If money can fix it, it's not a problem.
 -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] centos 6 - changing resolv.conf by hand gets overwritten by rebooting

[Pete Geenhuizen]

I think that you want to create /etc/dhclient-enter-hooks
with this, for more info do a search on dhclient-enter-hooks

# vi /etc/dhclient-enter-hooks
make_resolv_conf(){
:
}

Pete

On 08/27/15 15:36, George wrote:
given machine with C6 x86_64 (seen on C 6.6 but also before and 
probably still present on C6.7) only 1 interface, there is dhcp on 
this network (for kickstarting) but the machines have static ip's, and 
NO networkmanager installed


contents of resolv.conf
search some.domain.here
nameserver x.x.x.x #dns1
nameserver y.y.y.y #dns2

change resolv.conf to:
search some.newdomain.here
nameserver z.z.z.z #dns3
nameserver a.a.a.a #dns4

reboot machine and the contents of resolv.conf is again:
search some.domain.here
nameserver x.x.x.x #dns1
nameserver y.y.y.y #dns2

change it again to:
search some.newdomain.here
nameserver z.z.z.z #dns3
nameserver a.a.a.a #dns4
reboot again
now it stick to the last update.

Already tried to set /etc/sysconfig/network-scripts/ifcfg-eth0 
NM_controlled=no

with no result
other suggestions around the internet suggest also to set in
/etc/sysconfig/network-scripts/ifcfg-eth0
usepeerdns=no
have not tried this but should check if this fixes stuff.

Question: can someone explain me WHY this would help if it does and if 
this a valid entry in /etc/sysconfig/network ?
since I don't want to go over all my machines (a couple thousand) 
figuring out how many interfaces they have and what their names are to 
reconfigure that for each interface (some even suggest this should be 
done for lo too).


See also dozens of questions like that using google:
https://www.google.com/search?q=centos+6+overwrites+resolv.conf+reboot

G.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos



--
If money can fix it, it's not a problem.
 -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] An odd X question

[Pete Geenhuizen]

On 06/25/15 15:55, m.r...@5-cent.us wrote:

I've got a headless server running CentOS 7. I've got a user who wants to
run some graphical software on it, and view using x forwarding. What I
don't have clear is how to set this up. I've just installed
xorg-x11-server-[Xorg, common]. I assume I need to run X, but I don't see
running this in runlevel 5.

Thoughts?

  mark and why is it called xorg-x11-server, when in X terminology,
   it's the client?*

* Which I always thought was bass-ackward, but...

The easiest way to think of this is that the host on which you are going 
to watch the output needs a running X server, the source just needs the 
client application.  Of course this also presumes that network and 
permissions are all in place.


The test that I've always used is to run a simple xclient on the remote 
host, xclock, xeyes, xterminal and see if it show up, if it does you are 
good to go.


Pete

--
If money can fix it, it's not a problem.
 -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Logwatch and System uptime

[Pete Geenhuizen]

Enable it in /usr/share/logwatch/default.conf/services/zz-runtime.conf

Pete

On 06/15/15 09:58, James B. Byrne wrote:

CentOS-6.6

Can logwatch be configured to display the system uptime as part of the
reporting prologue?  If not then what would be the recommended way of
including this information in a daily logwatch report?




--
If money can fix it, it's not a problem.
 -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Real sh? Or other efficient shell for non-interactive scripts

[Pete Geenhuizen]

On 04/24/15 06:07, E.B. wrote:

I'm sure most people here know about Dash in Debian. Have there
been discussions about providing a more efficient shell in Centos
for use with heavily invoked non-interactive scripts?

With sh being a link to bash in Centos I don't know if it would
explode if the link was changed to something else, but at least
the scripts we made on our own that run certain services could
be changed and tested manually to another shell.

Are there other people who have experience in this and can
provide interesting guidance?
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Why go to that extreme if you tell a script on line 1 which shell to run 
it will do so.

#!/bin/dash
or what ever shell you want it to run in.  I always do that to make sure 
that the script runs as expected, if you leave it out the script will 
run in whatever environment it currently is in.


Pete

--
If money can fix it, it's not a problem.
 -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Real sh? Or other efficient shell for non-interactive scripts

[Pete Geenhuizen]

Initially Bourne was used because it was typically a static binary, 
because the boot process didn't have access to any shared libraries.  
When that changed it became a bit of a moot point, and you started to 
see other interpreters being used.


Even though Solaris started using ksh as the default user environment, 
almost all of the start scrips were either bourne or bash scripts.  With 
Bash having more functionality the scripts typically used the 
environment that suited the requirements best.


Bottom line is use what ever script suits your needs just be sure to 
tell the environment which interpreter to use.  Personally I never write 
a script that doesn't include the interpreter on the first line.


Pete

On 04/24/15 08:42, Eckert, Doug wrote:

It was the mid/late-90s, but I seem to recall Bourne being the default
shell, although sh/ksh/csh were all available with a typical install.

On Fri, Apr 24, 2015 at 8:32 AM, Scott Robbins scot...@nyc.rr.com wrote:





--
If money can fix it, it's not a problem.
 -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Nvidia Mod Update

[Pete Geenhuizen]

On 02/08/15 06:12, Ned Slider wrote:


On 08/02/15 05:09, S.Tindall wrote:
Yes, just to reiterate:

yum erase kmod-nvidia
yum install kmod-nvidia-340xx
reboot

You will then be on the correct driver branch and will get the
appropriate driver updates going forwards, no changes to yum necessary.

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

I went through all this, and now that I have kmod-nvidia-340xx 
installed, but have you executed yum update or yum list updates?
If you do then yum  will want up upgrade you to the latest and greatest 
kmod-nvidia-346xx.
So other than modifying yum to exclude the nvidia driver how do you 
prevent the update in the future?


rpm -qa | grep nvidia
nvidia-detect-346.35-1.el6.elrepo.x86_64
kmod-nvidia-340.65-1.el6.elrepo.x86_64
nvidia-x11-drv-340.65-1.el6.elrepo.x86_64

Output from yum list updates
Updated Packages
kmod-nvidia.x86_64346.35-1.el6.elrepo elrepo
nvidia-x11-drv.x86_64 346.35-1.el6.elrepo elrepo


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Nvidia Mod Update

[Pete Geenhuizen]

On 02/08/15 07:45, Ned Slider wrote:


On 08/02/15 12:33, Pete Geenhuizen wrote:
No, you don't have the package kmod-nvidia-340xx installed. You have
kmod-nvidia VERSION 340.65. In the first example, the package NAME is
kmod-nvidia-340xx (the -340xx is part of the package name, NOT the version).

Please do as I advised:

yum erase kmod-nvidia
yum install kmod-nvidia-340xx
reboot

Because you now no longer have package kmod-nvidia installed, yum will
not try to update you to the latest version. You will stay forever on
the 340.xx branch which is the last version to support your hardware.

Hope that helps
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Oops, yup right you are, kinda missed that small but important detail.

Thx.
Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Nvidia Mod Update

[Pete Geenhuizen]

On 02/08/2015 10:33 AM, Ned Slider wrote:


On 08/02/15 14:24, Pete Geenhuizen wrote:
No problem Pete.

Now you are on the correct branch you will continue to get updates to
that 340.xx driver as and when nvidia release them. IIRC, nvidia said
they would continue to support the 340.xx legacy branch until the end of
2019, so for the best part of another 5 years :-)

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Thanks Ned, perhaps by 2019 I'll have scummed to Centos 7 and all it's 
idiosyncrasies and I might even have newer hardware by then.


--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Upgrade from CentOS 6.x to 7

[Pete Geenhuizen]

I just ran the pre-upgrade, and it said that I couldn't do an in place 
upgrade for the following reason:


/usr directory is on separate partition. In-place Upgrade is NOT possible.

Well that was news to me because I never separate /usr, so what is going 
on?  It apparently turns out that /usr/local is on a separate partition 
and the software isn't smart enough to realize that there's a big 
difference between /usr and /usr/local, so I'm guessing that that is the 
reason.


I sure do hate software that makes lame or at worst incorrect 
assumptions, almost as bad as when you change a config file and comment 
out the default line and add you duplicate the line with changes, and 
the software is too dumb to realize what you did.





On 09/10/14 08:03, Clovis Tristao wrote:

Hi,

Em 09-09-2014 18:16, m.r...@5-cent.us escreveu:
No exist this lines in yum.conf
enabled=1
Yes, exist.

Thanks a lot guys.

Clovis



--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Upgrade from CentOS 6.x to 7

[Pete Geenhuizen]

Sure, I can umount /usr/local and comment it out of fstab, my comment 
was more about the fact that the software confused my configuration more 
that than anything else.  But then again it's probably best that they 
take the most conservative route and make folks aware of any and all 
possible ways that it might fail.


The report also listed a driver for an Ethernet card that was not 
supported in CentOS 7 which does make the software useful for 
identifying things like that.


All in all I think that it's worthwhile to run the software to see what 
it finds so that you can be aware of the types of issues that you might 
run into.


I agree that doing an upgrade using this method would be a bit of a last 
resort, I might try it just to see how it goes, just for the heck of it, 
but ultimately a re-install is best as it get's rid of all the chaff as 
well.


On 09/10/14 14:45, Les Mikesell wrote:

On Wed, Sep 10, 2014 at 1:24 PM, Pete Geenhuizen p...@geenhuizen.net wrote:
You should be able to just unmount /usr/local and take it out of fstab
for the duration of the upgrade then put it back and fix the contents
later.   But, that sort of thing makes a bare-metal reinstall sound
even more sensible since it shows how many options there are and how
many they may not have considered.



--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Removing a file that starts with dashes

[Pete Geenhuizen]

On 04/02/14 10:51, m.r...@5-cent.us wrote:
 Frank M. Ramaekers wrote:
 Method 1: try rm \-\-backup\=numbered
 Method 2, that will *ALWAYS* work:
 ls -i
 then, using the inode number
 find . -inum inode -exec rm {} \;

 The latter method is the one guaranteed to take care of all kinds of
 filenames with weird, or unprintable, stuff in the name.

 mark

 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

Use rm -i *
It will usually catch the file and because it's a special character it 
and many other odd ball file names usually appear in the very beginning 
so you don't have to go through the entire list.

-- 
Unencumbered by the thought process.
  -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] NIS or not?

[Pete Geenhuizen]

On 01/28/2014 04:02 AM, Sorin Srbu wrote:
 Hi all,

 We're getting to a point in our linux environment where it's starting to be
 cumbersome to keep shadow and passwd-files up-to-date for the users to login
 on each computer. Scripts can only get us so far. 8-/

 I've looked a bit into central login systems for linux, and NIS and LDAP seem
 to be prevalent. NIS being the simpler-to-setup solution for small to medium
 networks as I understand it, while LDAP is the more modern and scalable
 solution.
 See eg http://www.yolinux.com/TUTORIALS/NIS.html or
 http://sysadmin-notepad.blogspot.se/2013/06/nis-server-setup-on-rhelcentos.html.

 NIS-wise, what is a small to medium network?
 We have currently about 20-30'ish linux clients and servers, and the
 environment is not likely to increase much beyond this point.
 Is a 30ish-computer setup, a small network?

 The only thing I'm trying to accomplish is a system which will allow me to
 keep user accounts and passwords in one place, with one place only to
 administrate. NIS seems to be able to do that.

 Comments and insights are much appreciated!



 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos
I used NIS for many years while working on Sun Solaris and it worked 
extremely well, although when it breaks it can be a real challenge to 
figure out the problems.
I don't know how well it's implemented in Linux, bound to be a bit 
different than Solaris.  In either case if it's important be aware of 
the potential security issues related to NIS, mainly the clear text 
passing of the password which is what pretty much doomed it.

Depending on how ansi your users get I would recommend a slave server as 
well, you might also consider using autofs to mount the user's homes.

The biggest potential problem that you might run into when you first 
implement NIS is to take a look at the uid of all the users on each 
host, you will need to ensure that they are the same before you start 
NIS or else it will be a mess for the users because they won't own their 
own files.

With all of that said I do think though that LDAP would be a better 
solution although I've not used LDAP.

Good luck with it either way.

Pete


-- 
Unencumbered by the thought process.
  -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] NIS or not?

[Pete Geenhuizen]

Security is  a major consideration, and even though as you say most of 
the traffic is local, most problems are internal as opposed to external.

Pete
On 01/28/2014 08:22 AM, Sorin Srbu wrote:
 Yeah, that last bit made me squirm over here. I don't feel good about that,
 even though the linux machines are all pretty much localized to one spot, so
 that hardly any traffic goes out of the department.


 Thanks. I'll look into LDAP some more.

 //Sorin


 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

-- 
Unencumbered by the thought process.
  -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] what's wrong with dag.wieers?

[Pete Geenhuizen]

On 07/03/2013 08:34 AM, James B. Byrne wrote:
 On Tue, July 2, 2013 17:34, John Hinton wrote:

 Ditto here, and for the same reasons.

 This was our experience as well; changing userids between clam and
 clamav between updates caused us a lot of avoidable headaches.  We
 switched to epel for clamav because of that one issue.  Otherwise we
 have been very pleased with rpmforge.  It will prove a great loss if
 there is a serious possibility that this resource might fade away.


Fading away is a distinct possibility.
David  Hrbac, who is trying to maintain rpmforge had this to say on that 
subject.

And of course, there's still a question about the Repoforge. Do we
really want it? Isn't a time for Epel to replace Repoforge? I still want
to keep Repoforge alive bud have no replies from Dag.

Pete

-- 
Unencumbered by the thought process.
  -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] what's wrong with dag.wieers?

[Pete Geenhuizen]

On 07/02/2013 04:02 PM, Adrian P. van Bloois wrote:
 Hi,
 What happened to dag.wieers? There is an update for clamav but the rpm is
 still not distibuted after 4 weeks or more. :-)
 What's wrong there?

   Adrian


I asked about clamav on the repoforge list, and apparently there are 
some longstanding on-going issues with rpmforge, not sure exactly what 
and that apparently for quite some time some people have been attempting 
to resolve them.

Due to the length of time that these problems have existed there's also 
a fair amount of skepticism that the issues will be resolved.

There are several suggestions on how to resolve the clamav issue, one of 
them was to use the version from epel which is what I opted to do.  
Depending on your point of view I found it to be a relatively easy 
switch, just had to deal with a few ownership issues.

All in all it's a shame that there are issues as I've used rpmforge for 
years and have been pleased with the repo.

Pete

-- 
Unencumbered by the thought process.
  -- Click and Clack the Tappet brothers

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Shearing file systems on the network

[Pete Geenhuizen]

Joshua Baker-LePain wrote:

On Thu, 24 Jan 2008 at 11:01am, Peter Blajev wrote

I have 4 systems and each one of them has a partition I'd like to be 
remotely

accessible on the other 3 systems.

In other words System1 has Partition1. Systems 2,3,4 should be able to
remotely mount Partition1 from System1. Also System2 has Partition2. 
Then
systems 1,3,4 should be able to remotely mount Partition2 from 
System2 and so

on.

I tried NFS and it works but only in the ideal world. If one of the 
systems

goes down the whole NFS cross-mounting makes the other systems somewhat
unstable. It's a known issue and I believe you guys are aware of it 
but I

just had to see it myself.

What would you recommend? What is the best practice for doing that?


NFS and automount.


I what I'm using and it works just fine.

--
Unencumbered by the thought process.  
-- Click and Clack the Tappet brothers


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] /etc/passwd aand /etc/shadow out of sync on 4.6 box

[Pete Geenhuizen]

On Sun, January 6, 2008 23:12, Joe Klemmer wrote:
 On Sun,
2008-01-06 at 00:39 -0800, Garrick Staples wrote:
 

Rock-n-roll, man.  That did the trick.  You know, there would probably
 be use for a tool that checked the files and made sure they weren't
out
 of sync.  Isn't pam supposed to have that capability?  I
have avoided
 reading/learning anything about it for years.  And
I mean YEARS.  Maybe
 I'll take a peek and see what's in there. 
And maybe I'll get off my @$$
 and figure out Bind/DNS.


   Right.  And maybe Microsoft will change the licensing for
Windows to
 GPL.
 
 Anyway, thanks much,
 Joe

man pwck
-- 
Unencumbered by the thought
process.
-- Click and Clack, the Tappet Brothers.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos