Re: [CentOS] man and man-db inconsitency
> Date: Friday, January 29, 2016 21:32:38 -0800 > From: John R Pierce > > On 1/29/2016 9:22 PM, david wrote: >> Is there a reason for this inconsistency? The above algorithm >> works with most other packages. > > what 'algorithm' ? there's no fixed correlation between program > name and package name. > > for example, the package providing 'iostat' and 'sar' is called > sysstat. > > And, some packages change their names in different major releases > of an OS. Some packages are dropped entirely in new releases, and > other packages are added. You might see this as an inconsistency at the command->package mapping level, but it's a consistency/compatibility at the user/system level. Can you imagine having to go through and change every script, program and user's memory every time a package name changed? Look at /etc/alternatives and the symbolic links in /bin and /sbin for a range of remappings. It has been a long time since one looked for a "csh" binary, even if that's the shell in someone's passwd file entry that has been brought forward from an older system. Then there's sendmail->postfix. And, if you want a database, you still enter "mysql", but now get mariadb. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] 7.2: Problem with upgrade and pdns
Hello everybody, I just wanted to upgrade my system and stepped over the following error: --> Finished Dependency Resolution Error: Package: pdns-3.4.7-1.el7.x86_64 (@epel) Requires: libmbedtls.so.9()(64bit) Removing: mbedtls-1.3.14-1.el7.x86_64 (@epel) libmbedtls.so.9()(64bit) Updated By: mbedtls-2.2.1-1.el7.x86_64 (epel) ~libmbedtls.so.10()(64bit) Error: Package: pdns-tools-3.4.7-1.el7.x86_64 (@epel) Requires: libmbedtls.so.9()(64bit) Removing: mbedtls-1.3.14-1.el7.x86_64 (@epel) libmbedtls.so.9()(64bit) Updated By: mbedtls-2.2.1-1.el7.x86_64 (epel) ~libmbedtls.so.10()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Am I the only one with this problem? Any suggestions before I try the proposed solutions? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] 7.2: Problem with upgrade and pdns
Hello Kai, I believe the PowerDNS package in EPEL 7 is currently broken. The PowerDNS twitter feed had this a few days ago: https://twitter.com/powerdns/status/692660687403925504 Please wait until after the weekend for updated packages. Regards, Anand On 30/01/16 14:12, Kai Bojens wrote: > Hello everybody, > I just wanted to upgrade my system and stepped over the following error: > > --> Finished Dependency Resolution > Error: Package: pdns-3.4.7-1.el7.x86_64 (@epel) >Requires: libmbedtls.so.9()(64bit) >Removing: mbedtls-1.3.14-1.el7.x86_64 (@epel) >libmbedtls.so.9()(64bit) >Updated By: mbedtls-2.2.1-1.el7.x86_64 (epel) > ~libmbedtls.so.10()(64bit) > Error: Package: pdns-tools-3.4.7-1.el7.x86_64 (@epel) >Requires: libmbedtls.so.9()(64bit) >Removing: mbedtls-1.3.14-1.el7.x86_64 (@epel) >libmbedtls.so.9()(64bit) >Updated By: mbedtls-2.2.1-1.el7.x86_64 (epel) > ~libmbedtls.so.10()(64bit) > You could try using --skip-broken to work around the problem > You could try running: rpm -Va --nofiles --nodigest > > Am I the only one with this problem? Any suggestions before I try the > proposed solutions? > ___ > 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
[CentOS] CentOS7 changes strike again.
Still in the process of migrating from an old CentOS5 server to a brand new CentOS7. After finally getting Virtualbox-5.0 installed and a new Wondoze10 Pro installed it became time to shift the data from the old server to the new. The old server is headless and I installed the old WindozeXP into the Virtualbox4.x via the command line. To do some of the admin I needed to attach to the windoze via a gui and used rdesktop via an ssh tunnel of port 3389. This "just worked" with my old CentOS6 laptop and workstations. So now I try to connect to the old server via my laptop also running a recent CentOS7 install using rdesktop - no joy. the ssh command is >ssh servername -L 3389:127.0.0.1:3389 and then also from my laptop rdesktop -a 16 -N 127.0.0.1:3389 -u rkampen -p- only to get ERROR: Failed to open display: various google searches offer suggestions prepending DISPLAY=:0.0 gives Xlib: connection to ":0.0" refused by server Xlib: No protocol specified ERROR: Failed to open display: :0.0 tried setting selinux to permissive mode - still no joy. All this just worked with my old CentOS6 laptop and work station, however I no longer have access to that. I guess there have been some "improvements" with the advent of gnome3 that now prevent this from working, however my knowledge of how this rdesktop interacts with the local display manager are sketchy at best. Any suggestions from those of you that understand this stuff way better than I do? TIA Rob ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS7 changes strike again.
On 01/30/2016 09:15 AM, Rob Kampen wrote: So now I try to connect to the old server via my laptop also running a recent CentOS7 install using rdesktop - no joy. the ssh command is >ssh servername -L 3389:127.0.0.1:3389 and then also from my laptop rdesktop -a 16 -N 127.0.0.1:3389 -u rkampen -p- This has nothing to do with changes in CentOS. Read the VirtualBox docs for further setup: https://www.virtualbox.org/manual/ch07.html ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS7 changes strike again.
Rob Kampen wrote: Still in the process of migrating from an old CentOS5 server to a brand new CentOS7. After finally getting Virtualbox-5.0 installed and a new Wondoze10 Pro installed it became time to shift the data from the old server to the new. The old server is headless and I installed the old WindozeXP into the Virtualbox4.x via the command line. To do some of the admin I needed to attach to the windoze via a gui and used rdesktop via an ssh tunnel of port 3389. This "just worked" with my old CentOS6 laptop and workstations. So now I try to connect to the old server via my laptop also running a recent CentOS7 install using rdesktop - no joy. the ssh command is >ssh servername -L 3389:127.0.0.1:3389 and then also from my laptop rdesktop -a 16 -N 127.0.0.1:3389 -u rkampen -p- only to get ERROR: Failed to open display: various google searches offer suggestions prepending DISPLAY=:0.0 gives Xlib: connection to ":0.0" refused by server Xlib: No protocol specified ERROR: Failed to open display: :0.0 tried setting selinux to permissive mode - still no joy. All this just worked with my old CentOS6 laptop and work station, however I no longer have access to that. I guess there have been some "improvements" with the advent of gnome3 that now prevent this from working, however my knowledge of how this rdesktop interacts with the local display manager are sketchy at best. Any suggestions from those of you that understand this stuff way better than I do? TIA Rob When I do this with KVM I need to use the IP that the VM is using on the virtual bit of LAN that KVM emulates so my commands would be something like ssh servername -L 3389:192.168.123.100:3389 and rdesktop -a 16 -N 127.0.0.1:3389 -u rkampen -p- Where 192.168.123.100 is the IP of the VM What happens is that the SSH command produces a tunnel that links port 3389 on the source machine to port 3389 at IP 192.168.123.100 on the destination machine. Then the rdesktop command connects to the tunnel on your source machine on port 3389 which is then tunnelled to the destination at IP 192.168.123.100 port 3389, via what the SSH command did. In the shell you get to on 'servername', as a result of the SSH command, can you telnet 192.168.123.100 3389 and get a connection? Obviously substitute the real IP of the VM. If you can, then the VM is listening and accessible on port 3389. Is the firewall on the virtual host allowing the incoming traffic on 3389 to reach the VM? Hope that helps a little Ken -- 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
