Discuss

discuss@lists.centos.org

2 participants
34758 discussions

Identifying Official CentOS AWS AMIs
by Paul Heinlein 02 Jan '18

02 Jan '18

I'm trying to automate identification of CentOS AWS images. It appears that official CentOS AMIs have an OwnerID value of 410186602215, but I'm not sure if that value is transient or specific to one or more AWS regions. Is there a maintainer lurking here that can confirm or deny? Here's the base query I'm testing: aws ec2 describe-images \ --owners 410186602215 \ --output text \ --query 'reverse(sort_by(Images, &CreationDate))[?starts_with(Description, `CentOS Linux 7`)].[ImageId, CreationDate, Description]' -- Paul Heinlein heinlein(a)madboa.com 45°38' N, 122°6' W

1 0

DHCP timeout and mysteriously dropping IP address
by Jason Edgecombe 02 Jan '18

02 Jan '18

Hi everyone, I'me having trouble with a CentOS 7 guest running on a Hyper-V host. For some reason, the CentOS guest randomly drops its IP address. Running "systemctl restart NetworkManager" on the console will restore IP connectivity without a reboot. I think that DHCP is timing out, but I'm not sure what to do about it. Is there a way to tell NetworkManager to keep trying after a timeout? Here are the versions of the kernel and NetworkManager: Kernel: 3.10.0-693.11.1.el7.x86_64 NetworkManager: 1.8.0-11.el7_4.x86_64 Here are some pertinent logs: Dec 23 03:30:26 myhost kernel: hv_utils: Using TimeSync version 3.0 Dec 23 03:30:27 myhost systemd: Time has been changed Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.3750] device (eth0): link connected Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.3762] device (eth0): DHCPv4 lease renewal requested Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.3889] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 7936 Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.3890] dhcp4 (eth0): state changed bound -> done Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.3899] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.4487] dhcp4 (eth0): dhclient started with pid 33165 Dec 23 03:30:33 myhost dhclient[33165]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 (xid=0x5cb111f1) Dec 23 03:30:33 myhost dhclient[33165]: DHCPACK from xxx.xxx.36.1 (xid=0x5cb111f1) Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5824] dhcp4 (eth0): address xxx.xxx.37.53 Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5825] dhcp4 (eth0): plen 23 (255.255.254.0) Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5826] dhcp4 (eth0): gateway xxx.xxx.36.1 Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5826] dhcp4 (eth0): lease time 7200 Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5826] dhcp4 (eth0): nameserver 'xxx.xxx.0.20' Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5826] dhcp4 (eth0): nameserver 'xxx.xxx.0.30' Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5826] dhcp4 (eth0): domain name 'example.com' Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5826] dhcp (eth0): domain search 'example.com.' Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5827] dhcp (eth0): domain search 'foo.example.com.' Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5827] dhcp (eth0): domain search 'dyn.example.com.' Dec 23 03:30:33 myhost NetworkManager[788]: <info> [1514017833.5827] dhcp4 (eth0): state changed unknown -> bound Dec 23 03:30:33 myhost dhclient[33165]: bound to xxx.xxx.37.53 -- renewal in 3368 seconds. Dec 23 03:30:33 myhost dbus-daemon: dbus[726]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Dec 23 03:30:33 myhost dbus[726]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Dec 23 03:30:33 myhost systemd: Starting Network Manager Script Dispatcher Service... Dec 23 03:30:33 myhost dbus[726]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Dec 23 03:30:33 myhost dbus-daemon: dbus[726]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Dec 23 03:30:33 myhost systemd: Started Network Manager Script Dispatcher Service. Dec 23 03:30:33 myhost nm-dispatcher: req:1 'dhcp4-change' [eth0]: new request (4 scripts) Dec 23 03:30:33 myhost nm-dispatcher: req:1 'dhcp4-change' [eth0]: start running ordered scripts... Dec 23 03:40:42 myhost kernel: hv_utils: Using TimeSync version 3.0 Dec 23 03:40:43 myhost systemd: Time has been changed Dec 23 03:40:49 myhost NetworkManager[788]: <info> [1514018449.4566] device (eth0): link connected Dec 23 03:40:49 myhost NetworkManager[788]: <info> [1514018449.4583] device (eth0): DHCPv4 lease renewal requested Dec 23 03:40:49 myhost NetworkManager[788]: <info> [1514018449.4693] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 33165 Dec 23 03:40:49 myhost NetworkManager[788]: <info> [1514018449.4694] dhcp4 (eth0): state changed bound -> done Dec 23 03:40:49 myhost NetworkManager[788]: <info> [1514018449.4703] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Dec 23 03:40:49 myhost NetworkManager[788]: <info> [1514018449.4781] dhcp4 (eth0): dhclient started with pid 33440 Dec 23 03:40:49 myhost dhclient[33440]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 (xid=0x2f112c1) Dec 23 03:40:52 myhost dhclient[33440]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 (xid=0x2f112c1) Dec 23 03:40:57 myhost dhclient[33440]: DHCPREQUEST on eth0 to 255.255.255.255 port 67 (xid=0x2f112c1) Dec 23 03:41:02 myhost dhclient[33440]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6 (xid=0xe5feb70) Dec 23 03:41:08 myhost dhclient[33440]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10 (xid=0xe5feb70) Dec 23 03:41:18 myhost dhclient[33440]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 (xid=0xe5feb70) Dec 23 03:41:30 myhost dhclient[33440]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16 (xid=0xe5feb70) Dec 23 03:41:34 myhost NetworkManager[788]: <warn> [1514018494.9605] dhcp4 (eth0): request timed out Dec 23 03:41:34 myhost NetworkManager[788]: <info> [1514018494.9612] dhcp4 (eth0): state changed unknown -> timeout Dec 23 03:41:34 myhost NetworkManager[788]: <info> [1514018494.9713] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 33440 Dec 23 03:41:34 myhost NetworkManager[788]: <info> [1514018494.9714] dhcp4 (eth0): state changed timeout -> done Thanks, Jason --------------------------------------------------------------------------- Jason Edgecombe | Linux Administrator UNC Charlotte | The William States Lee College of Engineering 9201 University City Blvd. | Charlotte, NC 28223-0001 Phone: 704-687-1943 jwedgeco(a)uncc.edu | http://engr.uncc.edu | Facebook --------------------------------------------------------------------------- If you are not the intended recipient of this transmission or a person responsible for delivering it to the intended recipient, any disclosure, copying, distribution, or other use of any of the information in this transmission is strictly prohibited. If you have received this transmission in error, please notify me immediately by reply e-mail or by telephone at 704-687-1943. Thank you.

1 0

Re: [CentOS] OpenVPN server and firewalld
by Gianluca Cecchi 30 Dec '17

30 Dec '17

On Fri, Dec 29, 2017 at 10:32 AM, Kenneth Porter <shiva(a)sewingwitch.com> wrote: > How do I insert the iptables rule below using firewalld? > > I'm moving up from CentOS 6 to 7 on an office gateway and I'm trying to > get OpenVPN working to allow home workers to access PCs at the office. I've > got it all working but only by manually inserting an ACCEPT rule in the > FORWARD iptables chain: > > iptables -I FORWARD 3 -i tun+ -j ACCEPT > > This rule was extracted from my iptables firewall under CentOS6. The 3 > puts it after the accepts for established connections and loopback > connections, but before any firewalld sub-chains. With this I can connect > to an internal Windows 10 system with Remote Desktop. > > How can I inject this rule using firewalld, either as a direct rule or as > some more firewalld-approved kind of rule? > > Hello, in case your need is not covered by the "--add-service" and/or the "--add-port" you can still use a direct rule for it. I think it should be something like this to test: firewall-cmd --direct --add-rule ipv4 filter FORWARD 0 -i tun+ -j ACCEPT Manual page and some examples with man firewalld.direct The "iptables like" rule will be added into the pre-built chain named FORWARD_direct The 0 above means it is put at top of FORWARD_direct chain. In your example appears "3" and it is not clear what are lines 1 and 2. With iptables -L command you will see: # iptables -v -L FORWARD_direct Chain FORWARD_direct (1 references) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- tun+ any anywhere anywhere # With firewall-cmd you can see with # firewall-cmd --direct --get-all-rules ipv4 filter FORWARD 0 -i tun+ -j ACCEPT # If it works ok as expected, you can make it permanent with firewall-cmd --permanent --direct --add-rule ipv4 filter FORWARD 0 -i tun+ -j ACCEPT firewall-cmd --reload HIH digging into, Gianluca

2 1

CentOS 7 + KDE : post-installation script
by Nicolas Kovacs 29 Dec '17

29 Dec '17

Hi, I just spent two rainy days writing and fine-tuning a post-installation script for CentOS 7 and KDE. https://github.com/kikinovak/centos-7-desktop-kde I've just tested it on three different machines here, and it works quite nicely. Feel free to give it a spin and make some suggestions. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

2 3

Centos 7 and btrfs
by Matt 28 Dec '17

28 Dec '17

I am setting up a new test server. Doing a fresh install from CD onto a couple 4TB drives. Would like to try btrfs in a RAID 1 format. Are there any how to's on how to do that?

4 4

An rpmbuild spec question
by m.roth＠5-cent.us 28 Dec '17

28 Dec '17

I'm trying to build a package to create a directory and install some files. My rpmbuild keeps failing, unable to cd into the directory, "no such". Now, in the tmpfile, I *see* it cd'ing into BUILD/opt, and the source was unzipped and untared into BUILD/opt/smipmicfg-1.27.0. In the spec file, I've even added a cd $RPM_BUILD_ROOT/opt, and I see it cd to there... and then it says it fails cd'ing into the directory under it. I've been doing a lot of googling, but nothing seems to fix this. Anyone got a clue? mark

5 9

Can't see register value in crash vmcore
by wuzhouhui 28 Dec '17

28 Dec '17

OS: CentOS 6.5 Crash: crash-7.1.0-6.el6.x86_64 Kdump: kexec-tools-2.0.0-273.el6.x86_64 GDB: gdb-7.2-60.el6_4.1.x86_64 /etc/kdump.conf: core_collector makedumpfile -c --message-level 1 -d 31 Kernel crashed by panic("string"), but I can't see any register in vmcore: crash> bt PID: 53331 TASK: ffff880c523ed540 CPU: 2 COMMAND: "bw_sd-ar-7-0_2" #0 [ffff880c4f12f978] machine_kexec at ffffffff81038ed9 #1 [ffff880c4f12f9d8] crash_kexec at ffffffff810c5a82 #2 [ffff880c4f12faa8] panic at ffffffff815113b2 #3 [ffff880c4f12fb28] sd_submit_bio at ffffffffa0747a02 [sd] #4 [ffff880c4f12fb68] submit_clone_bio at ffffffffa0747d2b [sd] #5 [ffff880c4f12fb78] split_and_submit_bio_for_cbd at ffffffffa0747ec9 [sd] #6 [ffff880c4f12fbf8] sd_make_request at ffffffffa074c812 [sd] #7 [ffff880c4f12fc68] sdu_make_request at ffffffffa074ca41 [sd] #8 [ffff880c4f12fc88] generic_make_request at ffffffff81264d70 #9 [ffff880c4f12fd68] submit_bio at ffffffff81265140 #10 [ffff880c4f12fdb8] submit_area_bio at ffffffffa04ade20 [scst_vdisk] #11 [ffff880c4f12fde8] bwraid_submit_bio at ffffffffa04b03b2 [scst_vdisk] #12 [ffff880c4f12fe38] worker_thread at ffffffff81094c50 #13 [ffff880c4f12fee8] kthread at ffffffff8109ae26 #14 [ffff880c4f12ff48] kernel_thread at ffffffff8100c20a crash> Is it normal? Thanks.

1 0

(Dovecot) Package repository now available (fwd)
by Kenneth Porter 27 Dec '17

27 Dec '17

If you use CentOS as a mail server, you can now get the latest version of Dovecot (the IMAP and POP3 server) at the new Dovecot repo. ------------ Forwarded Message ------------ Date: Wednesday, December 27, 2017 5:00 PM +0200 From: aki.tuomi(a)dovecot.fi To: dovecot(a)dovecot.org, dovecot-news(a)dovecot.org Subject: Package repository now available Dovecot now has package repository for Debian, CentOS and Ubuntu available at https://repo.dovecot.org/ Packages are provided for 2.3 series and forward. Please let us know if you run into any trouble with these. --- Aki Tuomi Dovecot oy ---------- End Forwarded Message ----------

1 0

CentOS-announce Digest, Vol 154, Issue 4
by centos-announce-request＠centos.org 22 Dec '17

22 Dec '17

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CEEA-2017:3489 CentOS 7 kmod-redhat-qed Enhancement Update (Johnny Hughes) 2. CEBA-2017:3488 CentOS 7 java-1.8.0-openjdk BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 21 Dec 2017 19:26:02 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEEA-2017:3489 CentOS 7 kmod-redhat-qed Enhancement Update Message-ID: <20171221192602.GA28969(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Enhancement Advisory 2017:3489 Upstream details at : https://access.redhat.com/errata/RHEA-2017:3489 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 9683e58225c1778e171043227dc376241a55ba74aec9f4579cf30f4fa4090dbf kmod-redhat-qed-8.10.10.21_dup7.4-2.el7_4.x86_64.rpm 6c962b2d384c8bf7dd7e8b92e24fa1c1235bbe6212f7be70665ab3f13b66ebf6 kmod-redhat-qede-8.10.10.21_dup7.4-2.el7_4.x86_64.rpm ed6c9515bcfa965d45397f017418f568594046d85a2075316593989275a8b2af kmod-redhat-qedf-8.10.7.0_dup7.4-2.el7_4.x86_64.rpm 01f8ae75160adfac3d286b1c410bd38bca5a2afd99ad2e70536b30dc20f18fdb kmod-redhat-qedi-8.10.4.0_dup7.4-3.el7_4.x86_64.rpm 96ebbaffa522fee78b45e1e4d7ac461314d2d87e585eb1670617808843f9f1ed kmod-redhat-qedr-8.10.10.0_dup7.4-2.el7_4.x86_64.rpm Source: a42ac424ad1fa43269d891ac23bc276cef7bcdd25e7660c9ecf29788f691229c kmod-redhat-qed-8.10.10.21_dup7.4-2.el7_4.src.rpm 25130fca8c3dc270affb3c1d43df0b12e8161924a204edd8db273842ad50f369 kmod-redhat-qede-8.10.10.21_dup7.4-2.el7_4.src.rpm 43bae084122db338174961b0a6b4a7265504f8be486a77db70838f00cc30ded9 kmod-redhat-qedf-8.10.7.0_dup7.4-2.el7_4.src.rpm cc3cbeb63ed45f2598b3ccf8c04344135e5785a0b9be1c84ba8dd0e5ecae559f kmod-redhat-qedi-8.10.4.0_dup7.4-3.el7_4.src.rpm f9c105b0f845d0722618d3eb867e94e26d3b1ae4164522a8727d677a7e998be7 kmod-redhat-qedr-8.10.10.0_dup7.4-2.el7_4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Thu, 21 Dec 2017 19:29:47 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2017:3488 CentOS 7 java-1.8.0-openjdk BugFix Update Message-ID: <20171221192947.GA29174(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2017:3488 Upstream details at : https://access.redhat.com/errata/RHBA-2017:3488 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 88b9407e3fa3e414d3f5c58054436d913a684f2418243d1a80f62360d490b3e1 java-1.8.0-openjdk-1.8.0.151-5.b12.el7_4.i686.rpm 05149beeef9d964630c315fb1f1ef789e6a13f91650b9a5f15512ed7932ce405 java-1.8.0-openjdk-1.8.0.151-5.b12.el7_4.x86_64.rpm fd3402a60e2655776a4f1397a27d0dabe9b6fe1a091a8bd9e26d44904ff95030 java-1.8.0-openjdk-accessibility-1.8.0.151-5.b12.el7_4.i686.rpm 831d088e4c4376526b8fe2b898b640d7d5cc9343ed445a81f63de3a9a73c927f java-1.8.0-openjdk-accessibility-1.8.0.151-5.b12.el7_4.x86_64.rpm 5465474e5f28a5a827559cf1e1d1f50f4c34e786c1d9674e132325cde996dc9d java-1.8.0-openjdk-accessibility-debug-1.8.0.151-5.b12.el7_4.i686.rpm 6e98a2aa798a8d947ce79330ae3d76e17818e88c7387049e3c962f9894c05b6c java-1.8.0-openjdk-accessibility-debug-1.8.0.151-5.b12.el7_4.x86_64.rpm fa0e91cd0ffbe8063798267db48b7539bfd538949f658340c08423b4cd46e3ac java-1.8.0-openjdk-debug-1.8.0.151-5.b12.el7_4.i686.rpm 3abc411f2ef77dff9d4dd9029ba73f2388bc1615b48e36c58fdceef70c27f715 java-1.8.0-openjdk-debug-1.8.0.151-5.b12.el7_4.x86_64.rpm 66a38fbcdd258f4476a763ab78a2521ba8b16bdefac4092c895ffe06a89750ca java-1.8.0-openjdk-demo-1.8.0.151-5.b12.el7_4.i686.rpm fc6f2ad0b5b0cc9f8006b0563318e67ee3b5d946c77164aad7804232e373291a java-1.8.0-openjdk-demo-1.8.0.151-5.b12.el7_4.x86_64.rpm 5ef918b503b2157b884a67afd008a5305318e252763025127aa4f88dbc97dfed java-1.8.0-openjdk-demo-debug-1.8.0.151-5.b12.el7_4.i686.rpm 53b8ae44f13c7a301aec5a86d615d7fe456a1a8b885eeb725f93d859d83a0d01 java-1.8.0-openjdk-demo-debug-1.8.0.151-5.b12.el7_4.x86_64.rpm 69309f73b87778acefd461386e0ec3e38789072062df5d86b948e2002e3fa735 java-1.8.0-openjdk-devel-1.8.0.151-5.b12.el7_4.i686.rpm e000185c393464cef260cf2ad09006dbec57a5d0af3ab07ddf660e63d85d8dcf java-1.8.0-openjdk-devel-1.8.0.151-5.b12.el7_4.x86_64.rpm 8cc915795a1e2c1e5360fb7dee840e1ee313e54ab8478da0b17febb1a8e0223f java-1.8.0-openjdk-devel-debug-1.8.0.151-5.b12.el7_4.i686.rpm 7cf96429bc9ace0baa790e39515a0caa62879d90f1a2c434b559ea91f56ea427 java-1.8.0-openjdk-devel-debug-1.8.0.151-5.b12.el7_4.x86_64.rpm 966737cdc9dbfc16a7ea4fdff949778d166f011b326c86bad319dfd3daf0b200 java-1.8.0-openjdk-headless-1.8.0.151-5.b12.el7_4.i686.rpm 2901045d49e3d933b17ad111999fdbf16b72824f0e56fe99789d944da054a1ac java-1.8.0-openjdk-headless-1.8.0.151-5.b12.el7_4.x86_64.rpm c7efb4aa1a5e2a9011bc943f94a5b4989488436292222dfb6613eafbfe712b1b java-1.8.0-openjdk-headless-debug-1.8.0.151-5.b12.el7_4.i686.rpm 29a773df8073a7f388e6d598c7ca0b7b6373be48b5954b7598bf88d4c4cd6eb9 java-1.8.0-openjdk-headless-debug-1.8.0.151-5.b12.el7_4.x86_64.rpm 2660fdc8dd1ef01bdaef92042cdeff1e9ffb973aae07b1560d72c395eec4c3f4 java-1.8.0-openjdk-javadoc-1.8.0.151-5.b12.el7_4.noarch.rpm 6bf58e3312f317b05b104410814cd75b596a1399d5289dba2c49af3cce8bb89e java-1.8.0-openjdk-javadoc-debug-1.8.0.151-5.b12.el7_4.noarch.rpm e5f9c92f82916404e3755a074a28362ab1504d4b021d259f6b4edc953f9d6926 java-1.8.0-openjdk-javadoc-zip-1.8.0.151-5.b12.el7_4.noarch.rpm fce1b975ec219f230047c87c0bf23262d9065b3a0b9a3c8e6072317c4ec70fc4 java-1.8.0-openjdk-javadoc-zip-debug-1.8.0.151-5.b12.el7_4.noarch.rpm 2e41900e72c7e6740f8a68a5292530473fdc42b820a9c72fc2b889ec55d0e27e java-1.8.0-openjdk-src-1.8.0.151-5.b12.el7_4.i686.rpm f644bf21f724dfe4865a33941710ef78d790bd55710254cce2572b3b35e1f4e8 java-1.8.0-openjdk-src-1.8.0.151-5.b12.el7_4.x86_64.rpm de5140dfbccb73bba874a7c1895f4657e3aac5e5c9c1bbb03e638470eedfafb3 java-1.8.0-openjdk-src-debug-1.8.0.151-5.b12.el7_4.i686.rpm 863b8b64536c0d8ea90367901097d46c3e94fee36c034cca52fb2e1801e2dc02 java-1.8.0-openjdk-src-debug-1.8.0.151-5.b12.el7_4.x86_64.rpm Source: 8439a79f2aa0f8c64fc9dda350fba575c3bb8119e56a2db8b1afcc2f04e4b597 java-1.8.0-openjdk-1.8.0.151-5.b12.el7_4.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 154, Issue 4 ***********************************************

1 0

Does anyone know how to get clipboard and mouse integration in Centos vm?
by Manish Jain 20 Dec '17

20 Dec '17

Hi, I am running a Centos 7 vm under FreeBSD, and it works very well now, with KDE installed from DVD iso. But there's a couple of things missing, which happens only with Centos vm (Virtualbox): 1) Despite clipboard sharing enabled, copy-paste just does not work between host and guest 2) Mouse integration does not work. So I have to repeatedly capture mouse manually both in the host and in the guest. If anyone could provide me tips how to tweak the above, it shall help me a lot. -- Thanks & Regards, Manish Jain

2 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss