Discuss November 2015

discuss@lists.centos.org

130 participants
113 discussions

CentOS-announce Digest, Vol 129, Issue 5
by centos-announce-request＠centos.org 12 Nov '15

12 Nov '15

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. Announcing release for Vagrant 1.7.4 on CentOS Linux 7 x86_64 SCL (Honza Horak) ---------------------------------------------------------------------- Message: 1 Date: Wed, 11 Nov 2015 18:10:30 +0100 From: Honza Horak <hhorak(a)redhat.com> To: centos-announce(a)centos.org Subject: [CentOS-announce] Announcing release for Vagrant 1.7.4 on CentOS Linux 7 x86_64 SCL Message-ID: <56437686.6090009(a)redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed I am pleased to announce the immediate availability of Vagrant 1.7.4 on CentOS Linux 7 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo) QuickStart ---------- You can get started in three easy steps: $ sudo yum install centos-release-scl $ sudo yum install sclo-vagrant1 $ scl enable sclo-vagrant1 bash At this point you should be able to use vagrant just as a normal application. An example work-flow might be: $ vagrant init centos/7 $ vagrant up $ vagrant ssh In order to view the individual components included in this collection, including additional vagrant plugins, you can run : $ sudo yum list sclo-vagrant\* About Software Collections -------------------------- Software Collections give you the power to build, install, and use multiple versions of software on the same system, without affecting system-wide installed packages. Each collection is delivered as a group of RPMs, with the grouping being done using the name of the collection as a prefix of all packages that are part of the software collection. The collection sclo-vagrant1 delivers a Vagrant tool in version 1.x that allows to create and configure virtual development environments. Some of the most common plugins are also included in the collection as RPMs. The sclo-vagrant1 collection relies on the following additional collections which will also be installed: rh-ruby22, rh-ror41 For more on the Vagrant tool and other plugins, see https://www.vagrantup.com. The SCLo SIG in CentOS ---------------------- The Software Collections SIG group is an open community group co-ordinating the development of the SCL technology, and helping curate a reference set of collections. In addition to the Vagrant collection being released here, we also build and deliver databases, web servers, and language stacks including multiple versions of PostgreSQL, MariaDB, Apache HTTP Server, Ruby, NodeJS, Python and others. Software Collections SIG release was announced at https://lists.centos.org/pipermail/centos-announce/2015-October/021446.html You can learn more about Software Collections concepts at: http://softwarecollections.org/ You can find information on the SIG at https://wiki.centos.org/SpecialInterestGroup/SCLo ; this includes howto get involved and help with the effort. We meet every Wednesday at 16:00 UTC in #centos-devel (ref: https://www.centos.org/community/calendar) for an informal open forum open to anyone who might have comments, concerns or wants to get started with SCL's in CentOS. Enjoy! Honza SCLo SIG member ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 129, Issue 5 ***********************************************

1 0

Samsung evo 840 fixes
by Christer Solskogen 11 Nov '15

11 Nov '15

Queued TRIM seems to be a problem with this kind of drive (with the latest firmware), and a "recent" kernel (4.1.x) seems to have this fixed this without disabling NCQ completely. Is that patch backported to the "mainline" CentOS 6 or CentOS7 kernel? -- chs

4 7

OT: bacula question
by m.roth＠5-cent.us 10 Nov '15

10 Nov '15

Hi, folks, Question, for those that use/have used bacula: I've been setting up backups for one team, the server on CentOS 6, but they're on Windows. If we install the director on Windows, is it possible for the users to restore files from the server to their own machine? mark

4 9

centos 6 and super jumbo frames
by Steve Clark 10 Nov '15

10 Nov '15

Hi, Has anyone using CentOS 6 been able to successfully set an mtu larger than 9710 on an interface. I am seeing super jumbo frames with length > 10000. ... IP 10.79.4.53.64327 > 10.79.2.53.24294: Flags [.], seq 16060:29200, ack 1, win 32767, length 13140 ... CentOS release 6.7 (Final) Thanks, -- Stephen Clark *NetWolves Managed Services, LLC.* Director of Technology Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.clark(a)netwolves.com http://www.netwolves.com

4 5

CentOS6: missing kernel module?
by Benjamin Smith 10 Nov '15

10 Nov '15

Testing out tipc for cluster development, and running into an immediate snag. tipcutils was found in EPEL but despite having a "compatible" kernel, it doesn't seem to actually work. It's a completely updated system, Intel i5 with 16 GB of RAM, nothing remarkable. Any ideas? [root@backup2 ~]# tipc-config -netid=1234 -a=1.1.1 -be=eth:eth0 TIPC module not installed [root@backup2 ~]# modprobe -l | grep -i ipc kernel/sound/pci/snd-cmipci.ko kernel/net/ipv4/ipcomp.ko kernel/net/xfrm/xfrm_ipcomp.ko kernel/net/ipv6/ipcomp6.ko [root@backup2 ~]# uname -a Linux backup2.schoolpathways.com 2.6.32-573.7.1.el6.x86_64 #1 SMP Tue Sep 22 22:00:00 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux [root@backup2 ~]# yum repolist Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * epel: mirror.csclub.uwaterloo.ca * extras: mirror.san.fastserv.com * updates: mirrors.usc.edu repo id repo name status base CentOS-6 - Base 6,560+15 epel Extra Packages for Enterprise Linux 6 - x86_64 11,749 extras CentOS-6 - Extras 44 pgdg94 PostgreSQL 9.4 6 - x86_64 306 updates CentOS-6 - Updates 475+13 repolist: 19,134

3 2

Re: [CentOS] Rsync and differential Backups
by Ole Holm Nielsen 10 Nov '15

10 Nov '15

Alessandro Baggi <alessandro.baggi(a)gmail.com> wrote: > how to perform a differential backup using rsync? > > On web there is a great confusion about diff backup concept when > searched with rsync. I think the answer to this question is Rsnapshot, which is an old and well proven tool: http://rsnapshot.org/. To quote the homepage: > rsnapshot is a filesystem snapshot utility based on rsync. rsnapshot makes it easy to make periodic snapshots of local machines, and remote machines over ssh. The code makes extensive use of hard links whenever possible, to greatly reduce the disk space required. It's very easy to set up Rsnapshot with a simple configuration file. You can define hourly, daily, weekly and monthly backups. You run Rsnapshot from crontab and it's all automatic. We run Rsnapshot on the backup server which NFS-mounts the source file system as read-only (NFS read operations are low overhead). You may also use SSH. The backup server has XFS filesystems with the inode64 mount option (no inode problems :-). Our backup filesystems varies from 1-40 TB in size with 100k to 25M inodes. For very large source filesystems you may want to use 10 Gbit/s links to speed up the backups. The only issue I see is with source filesystems containing tens of millions of files, since new inodes have to be allocated on the backup server to "snapshot" a filesystem. The time for Rsnapshot to do "snapshots" can become substantial, depending on the speed of the underlying filesystem. -- Ole Holm Nielsen Department of Physics, Technical University of Denmark,

1 0

CentOS7 and "ip link alias"
by Mike - st257 09 Nov '15

09 Nov '15

Hello List, After demystifying the cause for my /sbin/ifup-local not being executed by network scripts for an Ethernet interface (don't let NetworkManager control it or ifup-local won't be executed)... ... I have a question with hopefully a simple answer: I placed an alias/description on my interface during testing and now I want to remove it. But when I try to remove it, I'm either trying to do something _actually_ not supported or I don't have the proper syntax to accomplish what I want. ~]# ip link set dev eno1 alias "hit" ~]# ip link show eno1 2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT qlen 1000 link/ether 00:22:19:1e:a2:5b brd ff:ff:ff:ff:ff:ff alias hit ~]# ip link delete dev eno1 alias "hit" RTNETLINK answers: Operation not supported Thoughts? It's mildly annoying at most. -- ---~~.~~--- Mike // SilverTip257 //

4 6

librhythmbox-itms-detection-plugin.so
by Alice Wonder 08 Nov '15

08 Nov '15

I'm looking at ways to potentially reduce tracking via browser fingerprints. https://panopticlick.eff.org/ When I go to that url in CentOS FireFox - my browser is very distinct. For me I believe this is largely caused by gstreamer. I run a modern gstreamer, not the CentOS packages gstreamer. My modern gstreamer also includes a lot of the patent-encumbered codecs, and on that eff project page, I can see them being reported by the GStreamer plugin as supported, making my firefox very unique and subject to tracking via browser fingerprint. I'm not sure there is anything I can do about that, other than going back to stock gstreamer which I can't do because I need gstreamer support for some codecs not supported by stock CentOS gstreamer. I think for anything that is a plugin, I think the browser should ask the user. That would make browser fingerprinting more difficult. One of the plugins though that is detected is from rhythmbox. I didn't even know there was a rhytmbox plugin for firefox. /usr/lib64/mozilla/plugins/librhythmbox-itms-detection-plugin.so It is part of the core rhythmbox package. I certainly have no need for it, and I doubt very many people do. It seems to me that maybe that plugin should be part of a sub-package to rhythmbox rather than rhythmbox itself, strictly from a security perspective so that if there is an exploitable bug in it, it will only be a vector for those who actually want that plugin. Does anyone actually use that plugin for anything? Maybe it should just be removed from the Fedora / RHEL / CentOS world.

1 0

safest way to grow a LV under VMware ESXi5.5
by Boris Epstein 08 Nov '15

08 Nov '15

Hello all, In your view, what is the most reliable and safe way to increase an LV housing the root filesystem of a Centos 6 VM. I am thinking either growing the virtual HD virtual device, or creating a new device and adding it as a PV to the VM, or perhaps migrating the whole FS to a new virtual disk. Any input on how best to proceed would be appreciated. Cheers, Boris.

5 7

NetworkManager and network service
by Sergio Belkin 06 Nov '15

06 Nov '15

Hi, folks, I 've created interfaces files with the NM_CONTROLLED=no statement and I've found that even after restarting network services changes are not commited. Only it worked after running ```` nmcli connection reload ```` restart of the network service worked. I wonder if it's either a feature or a bug... Could you help me? Thanks in advance! -- -- Sergio Belkin LPIC-2 Certified - http://www.lpi.org

1 0

← Newer
1
...
6
7
8
9
10
11
12
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss November 2015