Discuss

discuss@lists.centos.org

3 participants
34748 discussions

Start a nNew thread

CentOS-announce Digest, Vol 134, Issue 6
by centos-announce-request＠centos.org 08 Apr '16

08 Apr '16

1 0

Openshot 2.x (beta) on C7??
by Fred Smith 08 Apr '16

08 Apr '16

I'm interested in trying out the new OpenShot beta (2.06) on CentOS 7. Openshot requires Python3. so I look at available packages where I find a bunchof python3 packages as well as python34 packages. I'm assuming that python34 is version 3.4 of python, while python3 is some other 3.x version. Can anyone here explain to me what are the differences, any compatibility across these versions, and how to tell which I need for OpenShot? Thanks in adva ce! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- The Lord is like a strong tower. Those who do what is right can run to him for safety. --------------------------- Proverbs 18:10 (niv) -----------------------------

6 17

CentOS 7.2 rootfs for i386
by kavitha bk 07 Apr '16

07 Apr '16

Hi I want to build a small rootfs for 32 bit CentOS to the same I plan to build the entire OS but I see https://wiki.centos.org/HowTos/I_need_the_Kernel_Source kernel_build for 32 bit is not supported . Please let me know anybody has built the same Thanks Kavitha

3 4

CentOS-announce Digest, Vol 134, Issue 5
by centos-announce-request＠centos.org 07 Apr '16

07 Apr '16

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. Release for CentOS Linux 7 Rolling media March 2016 (Karanbir Singh) ---------------------------------------------------------------------- Message: 1 Date: Thu, 7 Apr 2016 02:18:59 +0100 From: Karanbir Singh <kbsingh(a)centos.org> To: CentOS Announcements List <centos-announce(a)centos.org> Subject: [CentOS-announce] Release for CentOS Linux 7 Rolling media March 2016 Message-ID: <5705B583.2030704(a)centos.org> Content-Type: text/plain; charset=utf-8 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am pleased to announce general availability of the March 2016 snapshot for CentOS Linux. This release includes CentOS Linux 7 iso based install media, Generic Cloud images, Atomic Host, Docker containers, Vagrant images, vendor hosted cloud images. This release set is tag'd 1603 and includes all updates released upto the 31st of March 2016. CentOS Linux rolling builds are point in time snapshot media rebuild from original release time, to include all updates pushed to mirror.centos.org's repositories. This includes all security, bugfix, enhancement and general updates for CentOS Linux. Machines installed from this media will have all these updates pre-included and will look no different when compared with machines installed with older media that have been yum updated to the same point in time. All rpm/yum repos remain on mirror.centos.org with no changes in either layout or content. - -------- CentOS Linux 7 / x86_64 install media is available at http://buildlogs.centos.org/rolling/7/isos/x86_64/ File: CentOS-7-x86_64-Minimal-1603-02.iso Sha: 58ee68c3ffae5c4ca629be9b992f97d108165e09726d3e8f80798ac9c7a1821e File: CentOS-7-x86_64-Everything-1603-02.iso Sha: f618b51bbbfbbc5a1d2fe64cb699735057f79df41125bad5be6eef11b4f7c575 File: CentOS-7-x86_64-DVD-1603-02.iso Sha: f78dcd1040afcdbb716c0581a182365ff34b7b37e9c20aa40b521b3c42677744 - -------- CentOS Linux 7 / x86_64 Cloud Images are available at : http://cloud.centos.org/centos/7/images/ Sha: c88230cde563ca29b065d53819586262f79a64769736e014bf6dabaa61a20968 File: CentOS-7-x86_64-GenericCloud-1603.qcow2 Sha:6d17808cf208bee3243f51b84e9bfb10b06f0cd04e2930505d9ea4fba2583bc5 File: CentOS-7-x86_64-GenericCloud-1603.qcow2c Sha: f91e602120a728f144da605baf0d5f4ad59293921bee99cc4aa3a1ab65e6d445 File: CentOS-7-x86_64-GenericCloud-1603.qcow2.xz Sha:5c5cacfc1f0700cc7d48d667933cd730f7443e866caeda94d8e205a8bc8ce511 File: CentOS-7-x86_64-GenericCloud-1603.raw.tar.gz - -------- CentOS Atomic Host is being release announced shortly. - -------- CentOS Linux 7 / x86_64 Vagrant images are updated at https://atlas.hashicorp.com/centos/7 and the backing files can be downloaded for libvirt and virtualbox providers at : Libvirt: http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-x86_64-V agrant-1603_01.LibVirt.box Sha: 4e01796e1afdd8c4bfbe98cffe5966caee227629429657a06c56d93d6e5fadaf Virtualbox: http://cloud.centos.org/centos/7/vagrant/x86_64/images/CentOS-7-x86_64-V agrant-1603_01.VirtualBox.box Sha: 549542fb475a02b7477000dded6dc7d12e7e325e461f029d25831eb9bb208a4b - -------- CentOS Linux 5 / 6 and 7 docker images are updated at https://hub.docker.com/_/centos/ - -------- We welcome all feedback around these rolling builds and media updates at the centos-devel mailing list ( http://lists.centos.org/ ). enjoy! - -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJXBbWDAAoJEI3Oi2Mx7xbtkhQIAKWdQsR+3toahhrc/859kfXW Y3tyvRVU3t/i7i4bs+4jtwT4zih8rEP4DBNYQE/lkv7gusjWANiuvr9FtTrNCj5c 7mGhTOFQtNG7AqGEHfQLKcdkCM4LMUbINhOhAqzymX9Vvj/jznyqenBNBlbwj9Cc yQR0aEeGPKFLhzUQqBBBW7B8UT1GzEr6l3+d+V7zEXdUJkSVaCiM2rMBEdEK41P/ 1sYCcuodBPaTGFVEFPSPZf5sq/fMWQasKfx164xu0Sdi0QQUer7CzwRMlDev649x yXbzF4Fkhs89JomXM6js19IArjA+HSAOWFu+jiHyp14OFGjReEkEfOcm+swIJ9g= =Ob+s -----END PGP SIGNATURE----- ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 134, Issue 5 ***********************************************

1 0

Re: [CentOS] KVM Virtualization Network VLAN CentOS7 (resolve)
by FrancisM 07 Apr '16

07 Apr '16

On Thu, Apr 7, 2016 at 4:20 PM, FrancisM <francis(a)mytechrepublic.com> wrote: > > > On Thu, Apr 7, 2016 at 1:51 PM, FrancisM <francis(a)mytechrepublic.com> > wrote: > >> >> >> On Thu, Apr 7, 2016 at 1:26 PM, Subscriber <ml-lists(a)agoris.net.ua> >> wrote: >> >>> Hello FrancisM, >>> >>> Thursday, April 7, 2016, 8:03:38 AM, you wrote: >>> >>> >>> > I tried last night and it seems like the vlans that I created is >>> failing to >>> > bring-up. So this is what Im doing >>> >>> > in my DATA trunk port at my HomeLab Im doing this >>> >>> > 2 port configured for teaming1 (set as link only port) -> Create Bridge >>> > (br0 port) on top of the teaming1 -> create slave vlan10,20,30,40 and >>> the >>> > parent is br0. Am I doing this correctly? Thanks >>> >>> not exactly. >>> >>> nmcli connection add con-name br10 ifname br10 type bridge stp no >>> nmcli connection down br10 >>> nmcli connection edit br10 >>> set ipv4.method disabled >>> set ipv6.method ignore >>> save >>> quit >>> nmcli connection up br10 >>> >>> nmcli connection add con-name vlan10 ifname vlan10 type vlan dev >>> teaming1 id 10 >>> nmcli connection down vlan10 >>> nmcli connection edit vlan10 >>> set connection.master br10 >>> set connection.slave-type bridge >>> verify fix >>> save >>> exit >>> nmcli connection up vlan10 >>> >>> similarly for br20+vlan20, br30+vlan30, br40+vlan40 >>> >>> _______________________________________________ >>> CentOS mailing list >>> CentOS(a)centos.org >>> https://lists.centos.org/mailman/listinfo/centos >>> >> >> Thanks for providing the command I will definitely try this method. >> >> > Hi, > > After trying the method using the 'nmcli' its the same error result as > what I encountered in using the 'nmtui' by the way after configuring then > check it in the nmtui its the same configuration as what I have done > earlier. > > [root@server network-scripts]# systemctl status network.service -l > ● network.service - LSB: Bring up/down networking > Loaded: loaded (/etc/rc.d/init.d/network) > Active: failed (Result: exit-code) since Tue 2015-04-07 17:19:00 SGT; > 1min 13s ago > Docs: man:systemd-sysv-generator(8) > Process: 48732 ExecStop=/etc/rc.d/init.d/network stop (code=exited, > status=0/SUCCESS) > Process: 49302 ExecStart=/etc/rc.d/init.d/network start (code=exited, > status=1/FAILURE) > > Apr 07 17:17:28 server network[49302]: [ OK ] > Apr 07 17:17:29 server network[49302]: Bringing up interface > team1_slave_enp5s0f1: Connection successfully activated (D-Bus active > path: /org/freedesktop/NetworkManager/ActiveConnection/69) > Apr 07 17:17:29 server network[49302]: [ OK ] > Apr 07 17:19:00 server network[49302]: *Bringing up interface vlan247: > Error: Timeout 90 sec expired.* > Apr 07 17:19:00 server network[49302]: *[FAILED]* > Apr 07 17:19:00 server network[49302]: Bringing up interface br247: [ > OK ] > Apr 07 17:19:00 server systemd[1]: network.service: control process > exited, code=exited status=1 > Apr 07 17:19:00 server systemd[1]: Failed to start LSB: Bring up/down > networking. > Apr 07 17:19:00 server systemd[1]: Unit network.service entered failed > state. > Apr 07 17:19:00 server systemd[1]: network.service failed. > [root@server network-scripts]# > > I will try to use other configuration on this bridge. Does it matter if I > use TEAMING and not BONDING on this bridging configuration because the two > nic card that is trunk is configured as TEAMING in my CentOS7 > Thanks all I already figure it out its due to the *ipv4.method link-only* it shoud be *ipv4.method disabled* in my teaming1 configuration

1 0

KVM Virtualization Network VLAN CentOS7
by Francis Mendoza 07 Apr '16

07 Apr '16

Im configuring my KVM and in my network configuration I have 4 Network lancard 2 nic = using teaming0 for management with access port configured in the switch side 2 nic = using teaming1 for guest VM DATA ports. and in the switch is configured for LACP with trunk allowing vlan 10,20,30,40,50 and configured in the CentOS7 the vlan 10, vlan 20,30,40,50 im sure its already working because I tried to use one vlan and ping was successful. my question is can I assigned directly the 'team1_vlan10, team1_vlan20.. and so on to directly use in my guest VM instead of bridging the network config in the VM.xml file? I tried to google and found only about bridging it first and could not find the direct connection in the DATA port Teaming1 Thank you in advance

5 12

CentOS 7, selinux issue
by m.roth＠5-cent.us 07 Apr '16

07 Apr '16

I'm seeing a lot of noise in the logs, to the effect of: setroubleshoot: SELinux is preventing /bin/ksh93 from write access on the directory /var/lib/ssh-x509-auth as well as others related to find, cat, etc on .pem's in that directory. Is this a policy bug, or just no policy covering this? mark

2 1

CentOS 7 annoyances
by m.roth＠5-cent.us 07 Apr '16

07 Apr '16

So, tell me folks, when you've got a system that isn't coming all the way up, and you get to the grub2? dracut? shell, and you tell it to reboot, and it responds by telling you I'm sorry, Dave, I can't do that, "target is destructive", what are you *expected* to do, other than power cycle the damn thing? mark

1 0

password
by Joe Smithian 06 Apr '16

06 Apr '16

3 3

systemd-run does not start scope in the specified slice
by Alexander Brand 06 Apr '16

06 Apr '16

It seems that systemd-run does not start the process in the specified slice when starting a transient scope instead of a service. I have created a test.slice, and started it: # systemctl status test.slice ● test.slice - Test slice Loaded: loaded (/usr/lib/systemd/system/test.slice; static; vendor preset: disabled) Active: active since Tue 2016-04-05 16:50:26 EDT; 2min 27s ago Memory: 0B Apr 05 16:50:26 abrand04 systemd[1]: Created slice Test slice. Apr 05 16:50:26 abrand04 systemd[1]: Starting Test slice. When running a process using systemd-run, # systemd-run --scope --slice=test --unit=test sleep 60 & [1] 52359 # Running scope as unit test.scope. the process is placed in the system.slice (see CGroup) instead of the test.slice as specified in the systemd-run command. # systemctl status test.scope ● test.scope - /usr/bin/sleep 60 Loaded: loaded (/run/systemd/system/test.scope; static; vendor preset: disabled) Drop-In: /run/systemd/system/test.scope.d └─50-Description.conf Active: active (running) since Tue 2016-04-05 16:56:04 EDT; 11s ago Memory: 92.0K CGroup: /system.slice/test.scope └─52359 /usr/bin/sleep 60 Apr 05 16:56:04 abrand04 systemd[1]: Started /usr/bin/sleep 60. Apr 05 16:56:04 abrand04 systemd[1]: Starting /usr/bin/sleep 60. CentOS Linux release 7.2.1511 (Core) systemd 219 Am I doing something wrong here? When starting the process as a service, and not a transient scope, the process is correctly placed in the specified slice.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss