date:20150402


On Thu, 2015-04-02 at 16:54 +0100, Karanbir Singh wrote:

...

Why not:

Centos 7.1.1502 

instead of 

Centos 7.1502 ?

on the basis revision 1502 has been applied to Centos 7.1 ?


-- 
Regards,

Paul.
England, EU.  Je suis Charlie.


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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

2015-04-02 Thread Jim Perrin




On 04/02/2015 01:28 PM, Phelps, Matthew wrote:



Soliciting our feedback *before* changing everything regarding release
names would
have been nice.


We did.

http://lists.centos.org/pipermail/centos-devel/2015-February/012873.html



--
Jim Perrin
The CentOS Project | http://www.centos.org
twitter: @BitIntegrity | GPG Key: FA09AD77
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64


On Thu, 2015-04-02 at 17:14 +0100, Karanbir Singh wrote:

 I believe your argument works fine since:
 CentOS-7-x86_64-DVD-1503.iso
 CentOS-7-x86_64-DVD-1507.iso
 CentOS-7-x86_64-DVD-1512.iso
 CentOS-7-x86_64-DVD-1606.iso
 
 note, this is YYmm to indicate age, and not serial numbers.

Being a so-called 'westerner' where people read from Left to Right, it
is illogical to read to the end of a string only to determine the
version number.

Arabs and Jews too (I think) read from right to left, but I am sure they
will also appreciate the simply logic of having

Centos 7-n-x86_64-DVD.iso

or even better

Centos 7-2-n-x86_64-DVD.iso

Why change anything unless the new idea is better than the previous ?


-- 
Regards,

Paul.
England, EU.  Je suis Charlie.


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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64


On 04/02/2015 03:12 PM, m.r...@5-cent.us wrote:
And when you have to talk to Windowsiacs, who know nothing other than 
version and point, it works best to tell them we're on that point, so 
go away, and don't bother us.


They know Service Packs and Build numbers.  Call it CentOS 7 Build 1503 
if you'd like.  They will understand that nomenclature just fine.

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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64


On Thu, 2015-04-02 at 16:12 -0400, Lamar Owen wrote:

 On 04/02/2015 03:55 PM, Always Learning wrote:
  Is there a commercial motive for this 'unwelcome by most' change ?
 
 Do you have data to prove that it is unwelcome by most?

Although most people in the world will privately complain the vast
majority do not complain in public.  Where is your contrary evidence
that this non-beneficial and illogical change is welcome by the majority
of Centos users ?


-- 
Regards,

Paul.
England, EU.  Je suis Charlie.


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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

On Thu, Apr 2, 2015 at 3:23 PM, Steve Thompson s...@vgersoft.com wrote:
 On Thu, 2 Apr 2015, Les Mikesell wrote:

 I didn't see any indication there that you were planning to turn the
 /etc/redhat-release file into a symlink.


 In CentOS, /etc/redhat-release has always been a symlink to
 /etc/centos-release.


Well if you define 'always' as 'for CentOS6 and later...  So I guess I
have redhat-lsb installed on all of my CentOS6 boxes and hadn't
noticed that particular breakage before.   To be fair, I consider it
to be a bug in OCSinventory to not follow a symlink to the contents,
but it does point out that any arbitrary change is going to break
something that trusted your previous version's functionality.

-- 
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] systemctl (again)

2015-04-02 Thread Andrew Holway

It might be SELinux. On a standard system; when we run things as a user
from the command line SELinux rules do not apply. It would explain why it
works manually but not via systemd.

Rather than using an init.d script you might want to try using a systemd
service. I haven't tested but something like this should work.

[Unit]
Description=timidity daemon

[Service]
PIDFile=/var/run/timidity.pid
User=someuser
Group=someuser
WorkingDirectory=/home/someuser
ExecStart=/bin/timidity
ExecReload=/bin/kill -s HUP $MAINPID
ExecStop=/bin/kill -s TERM $MAINPID
PrivateTmp=true





On 2 April 2015 at 23:07, J Martin Rushton martinrushto...@btinternet.com
wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 I've been trying to get the timidity system running as a daemon.  I
 wrote the following init script:

 #!/bin/sh
 #
 # timidity
 #
 ### BEGIN INIT INFO
 # Provides: timidity
 # Required-Start:
 # Required-Stop:
 # Default-Start:  2 3 4 5
 # Default-Stop: 0 1 6
 # Short-Description: Add and remove timidity
 # Description:
 ### END INIT INFO

 . /etc/rc.d/init.d/functions

 RETVAL=0
 PROG=timidity
 EXEC=/bin/$PROG
 PIDFILE=/var/run/timidity.pid

 function start {
 [[ -x $EXEC ]] || exit 5
 echo -n Starting $PROG: 
 $EXEC -iAD
 RETVAL=$?
 echo
 return $RETVAL
 }

 function stop {
 echo -n Stopping $PROG: 
 killproc $EXEC -TERM
 RETVAL=$?
 echo
 return $RETVAL
 }

 case $1 in
 start)  start
 RETVAL=$?
 ;;
 stop)   stop
 RETVAL=$?
 ;;
 status)
 status $PROG
 RETVAL=$?
 ;;
 restart)
 stop
 start
 ;;
 reload)
 stop
 start
 ;;
 *)
 echo $Usage: $prog
  {start|stop|status|restart|reload}
 exit 1
 esac
 exit $RETVAL


 When run through systemctl during startup it fails:

 [root@tamar init.d]# systemctl status timidity
 timidity.service - LSB: Add and remove timidity
Loaded: loaded (/etc/rc.d/init.d/timidity)
Active: active (exited) since Thu ...
   Process: 784 ExecStart=/etc/rc.d/init.d/timidity start
 (code=exited, status=0/SUCCESS)

 ... Starting LSB: Add and remove timidity...
 ... Starting timidity:
 ... jack_client_new: deprecated
 ... Started LSB: Add and remove timidity.
 ... Cannot connect to server socket err = No such file or directory
 ... Cannot connect to server request channel
 ... jack server is not running or cannot be started
 ... Couldn't open output device

 But when run directly is works fine:

 [root@tamar init.d]# ./timidity start
 Starting timidity:
 TiMidity starting in ALSA server mode
 Opening sequencer port: 128:0 128:1 128:2 128:3

 If I use # service timidity start it also fails.

 I _think_ that what is happening is that systemctl is stripping off
 the switch.  I've spent a couple of hours searching for any links or
 explanation and got nowhere.  I even knocked up a script to try and
 separate the two parts:
 #!/bin/sh
 cd /etc/init.d
 ./timidity start
 but to no avail.

 If there is a simple fix could someone point me there, if it's complex
 don't bother, I only need the daemon when running MIDI and can start
 it by hand.
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2.0.22 (GNU/Linux)

 iQIcBAEBAgAGBQJVHa+rAAoJEAF3yXsqtyBlKFUP/0olzOxF44xGa0/b1UI9LyKb
 8LWLJ6XYXQfwJZvZ7N5v/r9g6WPesIuWf/TugXEz20MhrN0BhoqmUrkD9FjVnpFa
 B7zQxRQ/DUXs2Z/w2DCfHRs5QWr3o31EGNPw/cZtqMf2bq+Z0LXXlU6A4QozDFe8
 Aq/ZYduOr5GG6D8DPRCSV2ggFGvs27I7vvp48bvCNZ4jh2dAjBSlygI42Koug2Ga
 UcAGllj4Litdm+O5hUpyPtsJC58umfNy4Lq9Y6HBxIpeZrioxNE+trNQHoZuzoP/
 clLItDMwj990Hs7ft3eyt1oIihuCTsVQ3HOkn0fjZ0OAWPIudq7ZynzfHctMGtP2
 Htx0A3coYxFFZ/fZZfYUkM4FQU6OA6fQ378u9hdxq9+XKayCh4938PZHmKjGHUTH
 DSu+iZVJ8DEc62pfgeLUWMidEgSu5/n5ROGIHed/wwt4nE6rGv/fz0D33ArMwD3t
 Ozybkt+FW2u8XK4qkA/ehgf3SBK4AIHMNg9IDWiWSaF4krQlInhKHGoCp1Xi1ISV
 2C/Lb7exn2CX/Uohdhqy86HNOhHHbZ6mkOL1k8XTIIazjRWJWQ/+gkt6Bj39q+K8
 NDnN03oVYsXgVz2nqFT3eQ001k/pRlkKn11ZYtEZ1fY77nzsOj+J3DD/txn8qTRi
 yNSvbWmxPj24hEVzSKu3
 =CEIq
 -END PGP SIGNATURE-
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] OT: Recommended anti-virus for Windows


On Thu, April 2, 2015 4:11 pm, J Martin Rushton wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Sorry to mention the opposition here, but I have a family member's
 laptop to protect, and I'm not allowed to upgrade it to Linux.  What's
 the current best recommendation?

For privately owned machine I would recommend

free.avg.com

- one free installation per household is permitted by license. I only am
testing (and would rather welcome comments): immunet 3 (based on clamav
which I use for long time on Unix mail servers), I have it installed on a
few machine that unlikely ever will see any visus, hence I do not have
sufficient battle ground experience with immunet 3.

Valeri

 Thanks,
 MArtin
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2.0.22 (GNU/Linux)

 iQIcBAEBAgAGBQJVHbCMAAoJEAF3yXsqtyBl4I8P/AsvH+cyGcG9PDtL8I091WJc
 jaAhT8Z77G8LBTNaCUi1NXaR3zYsxZ1LltS8MyyqpA+TZ5TkwGRI5V0g2h5owrXv
 vmFNHW4DQcnB5D4s5+B50lnjyIWgtLG0BKUwCgLik++U11umHd5sCTqXTaHzlyP8
 Ndz2RAVEm9A8T3My7fKeVF+/c2pt6rKaRoifeTiH+IUnmvuFHPHuQEpLuOx0qKLH
 BCHyg7ZJcpwQEocYMhZu7JkZ/zg5/eCb+0HIq5qOCkeRj64ax0QOMzlvcScBRQDp
 tBzXIAXnFGMNmgE8tvD9Xh2Gi/OKx/bbqRdo8mMzUGUlWSErSt2UMPkpN3Vm3S2C
 wQhSqMoNnxWCypofazmIXH+TKn1/ipUhZXF3GcZsBYDfIb95kvdBrJm//QioI8Fy
 BFGc5Cj9DjXNxIbCfvQuyrG1RDdwHKjt/AMmoB0RXpSwhxRfS2749gyrkGXRUSSd
 IFRpX8Ds0quxx8D9YY96FYX4VbPFhFKIm64OigjLOenedek4A0TpUg7tF5HpyDA7
 SXl/l9wFbqAOIKR+VYHIix9UPqxUkU/6fio1D/RhD+8gulY9Tj4Bx5vjpVkJm4wY
 +Dj0VZ6LyhhkkOTypvENrY2imyxJ+MQ/xKiBQCcvGJIkNcxKr3Xd9D6cFkkkZWR7
 bAaC26I/cC4witLZSC2k
 =1XHp
 -END PGP SIGNATURE-
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos




Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

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

Re: [CentOS] Kernel panic, CentOS 7.1503 fully updated, with executing gkrellm.


On 04/02/2015 10:33 AM, Lamar Owen wrote:
 That's why I still hope it's local to my machine.  But now to try to 
reproduce on other hardware.  (for reference, hardware on which I saw 
the bug is a Dell Precision M6500 with a Core i7-740QM and an AMD/ATI 
Firepro 7820M video, with / on a Samsung PM830 SSD)
Ok, I can't reproduce on my Precision M4300 with a Core 2 Duo T9300 and 
nVidia Quadro 360M video.  However, I do notice some differences between 
my M6500's login screen and the login screen of the M4300, notably the 
CentOS logo at bottom center.  So, to do more digging..


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

[CentOS] Boot Failure [Solved]

2015-04-02 Thread pro alias

I writ:
The latest kernel kernel-3.10.0.229.1.2.el7.x86_64 appears not to like
our Supermicro X9SBAA-F board. It fails on boot with the last message
before panic being apic_timer_interupt  snipped rest

It turned out that only one X9SBAA box was affected.

Deleting and reinstalling the kernel did not fix the issue.
The problem turned out to be the old initrd issue in grub.conf. We have
seen this from time to time on updates in the past. The line:
initrd /initramfs-3.10.0-229.1.2.el7.x86_64.img
was missing from grub.conf. When manually inserted, the new kernel
worked swimmingly. I suspect that this is related to updating grub
either immediately before or after a new kernel is installed. It's just
enough of an annoyance that someone with spare time on their hands
might want to look in it.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

2015-04-02 Thread m . roth

Les Mikesell wrote:
 On Thu, Apr 2, 2015 at 1:08 PM, Johnny Hughes joh...@centos.org wrote:

 If you really _need_ a specific minor release and want to _stay_ on it,
 to my knowledge, that's not something CentOS has _ever_ done anyway.
 You can pay for Red Hat's EUS, or, I think Scientific Linux actually
 does keep the .y releases separate (but I'm not sure of the details
 as to how that's implemented).

 That last paragraph is EXACTLY the message we are trying to put out
 here.  CentOS releases are NOT the same as EUS and have never been ..
 yet that seems to be what people expect.  We want there to be no doubt
 on this issue.

 But you are adding more confusion than you resolve if the designation
 does not indicate that a specified version is 'at least' up to the
 equivalent of some RH minor rev.  Even for the people who might have
 incorrectly thought is was pinned there.   And now there yet another
 arbitrary difference in what you need to know about one major number
 vs. another for the long interval they will co-exist.

Let me also add to Les' argument, in that there *are* point releases -
when we go from x.y to x.z, there are usually on the order of 300 packages
(I believe when I upgraded two servers yesterday from 7.0 to 7.1, there
were 267 or so packages updated, and I think a few installed. That's *not*
the same as yum update, and I get 10 or even 70 packages.

And when you have to talk to Windowsiacs, who know nothing other than
version and point, it works best to tell them we're on that point, so go
away, and don't bother us

  mark

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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

On Thu, Apr 2, 2015 at 2:25 PM, Jim Perrin jper...@centos.org wrote:


 On 04/02/2015 01:28 PM, Phelps, Matthew wrote:


 Soliciting our feedback *before* changing everything regarding release
 names would
 have been nice.


 We did.

 http://lists.centos.org/pipermail/centos-devel/2015-February/012873.html

I didn't see any indication there that you were planning to turn the
/etc/redhat-release file into a symlink.   And even if I had I
probably wouldn't have thought specifically that it was going to break
ocsinventory-ng, although pretty much every unnecessary and arbitrary
change breaks something.

And besides there's not much reason to think that user comments are
ever read on the -devel list.  Like this one, for example:
http://lists.centos.org/pipermail/centos-devel/2014-June/010940.html

-- 
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64


On 04/02/2015 04:16 PM, Always Learning wrote:

Although most people in the world will privately complain the vast
majority do not complain in public.  Where is your contrary evidence
that this non-beneficial and illogical change is welcome by the majority
of Centos users ?


The burden of proof for your statement is on you, not me.  I never said 
it was welcome by most, either.  I might even agree with your statement, 
for that matter; but you made the statement; you have the burden of 
proof of that statement.  I do not need to prove the converse.


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

Re: [CentOS] OT: Recommended anti-virus for Windows

2015-04-02 Thread Александр Кириллов


One thing I forgot to mention: I also always recommend AGAINST using
kasperski. Kasperski is KGB guy (*cough* *cough* retired. You know in 
that

service retirement is only feet first dead, so you do your math).


Is KGB rant still in vogue in your new homeland?

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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64


On Thu, April 2, 2015 2:55 pm, Always Learning wrote:

 On Thu, 2015-04-02 at 13:08 -0500, Johnny Hughes wrote:

 CentOS releases are NOT the same as EUS and have never been .. yet that
  seems to be what people expect.  We want there to be no doubt on this
  issue.

 Is there a commercial motive for this 'unwelcome by most' change ?

 If Centos is the same as RHEL then RH can loose valuable sales income
 because customers, actual and potential, use free Centos. However if
 Centos version numbers are vastly different from RHEL version numbers
 and there is no reliable method of equating Centos sub-versions with
 RHEL sub-versions, RH gains extra sales because of the uncertainty of
 Centos being 'just like' reliable RHEL.

Indeed. And some conspiracy theorist might add this happened after CentOS
marrying RH (well, getting tighter relations that is) ;-)

Just a joke to put down everybody's fighting mood (or likely switching
fire onto myself ;-(

Valeri


 Just a casual thought.


 --
 Regards,

 Paul.
 England, EU.  Je suis Charlie.


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




Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

2015-04-02 Thread Steve Thompson


On Thu, 2 Apr 2015, Les Mikesell wrote:


I didn't see any indication there that you were planning to turn the
/etc/redhat-release file into a symlink.


In CentOS, /etc/redhat-release has always been a symlink to 
/etc/centos-release.


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

[CentOS] systemctl (again)

2015-04-02 Thread J Martin Rushton

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I've been trying to get the timidity system running as a daemon.  I
wrote the following init script:

#!/bin/sh
#
# timidity
#
### BEGIN INIT INFO
# Provides: timidity
# Required-Start:
# Required-Stop:
# Default-Start:  2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Add and remove timidity
# Description:
### END INIT INFO

. /etc/rc.d/init.d/functions

RETVAL=0
PROG=timidity
EXEC=/bin/$PROG
PIDFILE=/var/run/timidity.pid

function start {
[[ -x $EXEC ]] || exit 5
echo -n Starting $PROG: 
$EXEC -iAD
RETVAL=$?
echo
return $RETVAL
}

function stop {
echo -n Stopping $PROG: 
killproc $EXEC -TERM
RETVAL=$?
echo
return $RETVAL
}

case $1 in
start)  start
RETVAL=$?
;;
stop)   stop
RETVAL=$?
;;
status)
status $PROG
RETVAL=$?
;;
restart)
stop
start
;;
reload)
stop
start
;;
*)
echo $Usage: $prog 
{start|stop|status|restart|reload}
exit 1
esac
exit $RETVAL


When run through systemctl during startup it fails:

[root@tamar init.d]# systemctl status timidity
timidity.service - LSB: Add and remove timidity
   Loaded: loaded (/etc/rc.d/init.d/timidity)
   Active: active (exited) since Thu ...
  Process: 784 ExecStart=/etc/rc.d/init.d/timidity start
(code=exited, status=0/SUCCESS)

... Starting LSB: Add and remove timidity...
... Starting timidity:
... jack_client_new: deprecated
... Started LSB: Add and remove timidity.
... Cannot connect to server socket err = No such file or directory
... Cannot connect to server request channel
... jack server is not running or cannot be started
... Couldn't open output device

But when run directly is works fine:

[root@tamar init.d]# ./timidity start
Starting timidity:
TiMidity starting in ALSA server mode
Opening sequencer port: 128:0 128:1 128:2 128:3

If I use # service timidity start it also fails.

I _think_ that what is happening is that systemctl is stripping off
the switch.  I've spent a couple of hours searching for any links or
explanation and got nowhere.  I even knocked up a script to try and
separate the two parts:
#!/bin/sh
cd /etc/init.d
./timidity start
but to no avail.

If there is a simple fix could someone point me there, if it's complex
don't bother, I only need the daemon when running MIDI and can start
it by hand.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJVHa+rAAoJEAF3yXsqtyBlKFUP/0olzOxF44xGa0/b1UI9LyKb
8LWLJ6XYXQfwJZvZ7N5v/r9g6WPesIuWf/TugXEz20MhrN0BhoqmUrkD9FjVnpFa
B7zQxRQ/DUXs2Z/w2DCfHRs5QWr3o31EGNPw/cZtqMf2bq+Z0LXXlU6A4QozDFe8
Aq/ZYduOr5GG6D8DPRCSV2ggFGvs27I7vvp48bvCNZ4jh2dAjBSlygI42Koug2Ga
UcAGllj4Litdm+O5hUpyPtsJC58umfNy4Lq9Y6HBxIpeZrioxNE+trNQHoZuzoP/
clLItDMwj990Hs7ft3eyt1oIihuCTsVQ3HOkn0fjZ0OAWPIudq7ZynzfHctMGtP2
Htx0A3coYxFFZ/fZZfYUkM4FQU6OA6fQ378u9hdxq9+XKayCh4938PZHmKjGHUTH
DSu+iZVJ8DEc62pfgeLUWMidEgSu5/n5ROGIHed/wwt4nE6rGv/fz0D33ArMwD3t
Ozybkt+FW2u8XK4qkA/ehgf3SBK4AIHMNg9IDWiWSaF4krQlInhKHGoCp1Xi1ISV
2C/Lb7exn2CX/Uohdhqy86HNOhHHbZ6mkOL1k8XTIIazjRWJWQ/+gkt6Bj39q+K8
NDnN03oVYsXgVz2nqFT3eQ001k/pRlkKn11ZYtEZ1fY77nzsOj+J3DD/txn8qTRi
yNSvbWmxPj24hEVzSKu3
=CEIq
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64


On Thu, 2015-04-02 at 11:08 -0500, Valeri Galtsev wrote:


 A:
 
 0 1 2 3 4 5 6 ...

That is called an arithmetic progression (from my school days)

 B:
 
 231 2735 2746 3458 5216 ...

does not resemble a geometric progression.

Lets have a LOGICAL numbering system.  How about

Centos 6.6-1503 

derived from {major}{sub}{yymm}.

But what happens when 2 or more revisions occur within the same month ?

Will we have Centos 7.1504 and 7.1504a and 7.1504c or will someone
decide to use 7.1505 (= May 2015) whilst still in April ?

Clarity is important in all things 'computer'.

Valeri


 1. whereas in case A given you have [sub]version number 4 you definitely
 know that adjacent previous is 3 and adjacent following will be 5. Case B
 is different: unless you have the whole row of legal numbers in front of
 you, you will not be able to guess whether 2746 and 3458 are consecutive
 versions, or there is one or more versions between them.
 
 2. comparison of two version in case A easily reveals which is earlier and
 which is higher, in case B it is not quite so (you can try to time
 yourself on comparison of random natural number in 1 range and compare
 that to the case of natural numbers 0-9, you will know what I mean), and
 hence prone to higher chance of error (and don't second guess me: I always
 has A+ in mathematics in school and university ;-). This is just a trivial
 human psychology...

Maths was my favourite school subject too. 


-- 
Regards,

Paul.
England, EU.  Je suis Charlie.


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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64


On Thu, 2015-04-02 at 14:25 -0500, Jim Perrin wrote:
 
 On 04/02/2015 01:28 PM, Phelps, Matthew wrote:
 
 
  Soliciting our feedback *before* changing everything regarding release
  names would
  have been nice.
 
 We did.
 
 http://lists.centos.org/pipermail/centos-devel/2015-February/012873.html


Strange - I thought this mailing list was named Centos Users !


-- 
Regards,

Paul.
England, EU.  Je suis Charlie.


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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64


On 04/02/2015 03:55 PM, Always Learning wrote:

Is there a commercial motive for this 'unwelcome by most' change ?


Do you have data to prove that it is unwelcome by most?  It is unwelcome 
by you and a few others I've seen comment; what percentage of the list's 
subscribers do you suppose that might be?  (It is neither welcome nor 
unwelcome by me, as I've said before.)


Feedback on the direction of the distribution's development is taken on 
the -devel list; this list is for questions about using the distribution.

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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

2015-04-02 Thread John R Pierce


On 4/2/2015 1:16 PM, Always Learning wrote:

Although most people in the world will privately complain the vast
majority do not complain in public.  Where is your contrary evidence
that this non-beneficial and illogical change is welcome by the majority
of Centos users ?


you're the one claiming its 'unwelcome by most', qed, the burden of 
proving that statement lies entirely on you.



I for one could care less what the ISO is called.

--
john r pierce, recycling bits in santa cruz

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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

On Thu, Apr 2, 2015 at 4:12 PM, Lamar Owen lo...@pari.edu wrote:

 On 04/02/2015 03:55 PM, Always Learning wrote:

 Is there a commercial motive for this 'unwelcome by most' change ?


 Do you have data to prove that it is unwelcome by most?  It is unwelcome
 by you and a few others I've seen comment; what percentage of the list's
 subscribers do you suppose that might be?  (It is neither welcome nor
 unwelcome by me, as I've said before.)

 Feedback on the direction of the distribution's development is taken on
 the -devel list; this list is for questions about using the distribution.


See my reply earlier. The description of the centos-devel list says this
is strictly about development.

I take that to mean it is for developers. I am not a developer for CentOS.
I don't know this, but I'm guessing there are many many users and admins of
CentOS who are not on that list, like me. Even a Please check out this
thread for an important discussion about the future of CentOS release
names. would have been appreciated.

Now it's too late.

(As I said earlier, it's not just the ISO name either).

-- 
Matt Phelps
System Administrator, Computation Facility
Harvard - Smithsonian Center for Astrophysics
mphe...@cfa.harvard.edu, http://www.cfa.harvard.edu
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Kernel panic, CentOS 7.1503 fully updated, with executing gkrellm.

2015-04-02 Thread Marcelo Ricardo Leitner


On 02-04-2015 17:05, Lamar Owen wrote:

On 04/02/2015 10:33 AM, Lamar Owen wrote:

 That's why I still hope it's local to my machine.  But now to try to
reproduce on other hardware.  (for reference, hardware on which I saw
the bug is a Dell Precision M6500 with a Core i7-740QM and an AMD/ATI
Firepro 7820M video, with / on a Samsung PM830 SSD)

Ok, I can't reproduce on my Precision M4300 with a Core 2 Duo T9300 and
nVidia Quadro 360M video.  However, I do notice some differences between
my M6500's login screen and the login screen of the M4300, notably the
CentOS logo at bottom center.  So, to do more digging..


Thanks for doing all this testing but it's not really necessary in order 
to report the bug.. you know that, right?


If you can share the original backtraces, it already helps and someone 
may even point you to a fix if it's a known issue.


  Marcelo

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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

2015-04-02 Thread centos

On Thu, 02 Apr 2015 20:55:46 +0100
Always Learning cen...@u64.u22.net wrote:

 Is there a commercial motive for this 'unwelcome by most' change ?

I must be part of one the by most. Since I'm one of the mostly
silent majority.

I want to express my thanks to the team that does all of the work.

Thank you guys!

As far as the version numbering, just let me know what you are
calling it (already done) and I'll deal with it. If I am unhappy,
then there is RedHat but there's also SuSE, Ubuntu/Debian, Slack,
Gentoo...

sknahT

vyS

 
 If Centos is the same as RHEL then RH can loose valuable sales
 income because customers, actual and potential, use free Centos.
 However if Centos version numbers are vastly different from RHEL
 version numbers and there is no reliable method of equating Centos
 sub-versions with RHEL sub-versions, RH gains extra sales because
 of the uncertainty of Centos being 'just like' reliable RHEL.
 
 Just a casual thought.
 
 
 -- 
 Regards,
 
 Paul.
 England, EU.  Je suis Charlie.
 
 
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos
 


-- 
sknahT

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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

On Thu, Apr 2, 2015 at 3:25 PM, Jim Perrin jper...@centos.org wrote:



 On 04/02/2015 01:28 PM, Phelps, Matthew wrote:


 Soliciting our feedback *before* changing everything regarding release
 names would
 have been nice.


 We did.

 http://lists.centos.org/pipermail/centos-devel/2015-February/012873.html



WE'RE NOT ON THE DEVEL LIST!

Yes, I'm shouting.



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




-- 
Matt Phelps
System Administrator, Computation Facility
Harvard - Smithsonian Center for Astrophysics
mphe...@cfa.harvard.edu, http://www.cfa.harvard.edu
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Boot Failure Lastest CEntos 7 Kernel on X9SBAA-F Board

2015-04-02 Thread Frank Cox

On Thu, 2 Apr 2015 12:20:57 -0700
pro alias wrote:

  It fails on boot with the last message
 before panic being apic_timer_interupt .

The first thing I would try is to boot using the noapic parameter and see if 
that works.

-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

2015-04-02 Thread Jim Perrin




On 04/02/2015 02:29 PM, Phelps, Matthew wrote:

On Thu, Apr 2, 2015 at 3:25 PM, Jim Perrin jper...@centos.org wrote:




On 04/02/2015 01:28 PM, Phelps, Matthew wrote:



Soliciting our feedback *before* changing everything regarding release
names would
have been nice.



We did.

http://lists.centos.org/pipermail/centos-devel/2015-February/012873.html




WE'RE NOT ON THE DEVEL LIST!


WHY NOT?



Yes, I'm shouting.


I DON'T KNOW WHAT WE'RE YELLING ABOUT


Seriously though, the change was brought up over a month ago on the 
-devel list. When we're asking for feedback about possible changes, it's 
on the -devel list, because it's about the development of the distro. If 
you want to give input for the direction of the distro, that's the place 
to do it. I would encourage anyone who's interested to join.


--
Jim Perrin
The CentOS Project | http://www.centos.org
twitter: @BitIntegrity | GPG Key: FA09AD77
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

On Thu, Apr 2, 2015 at 3:47 PM, Jim Perrin jper...@centos.org wrote:



 On 04/02/2015 02:29 PM, Phelps, Matthew wrote:

 On Thu, Apr 2, 2015 at 3:25 PM, Jim Perrin jper...@centos.org wrote:



 On 04/02/2015 01:28 PM, Phelps, Matthew wrote:


  Soliciting our feedback *before* changing everything regarding release
 names would
 have been nice.


 We did.

 http://lists.centos.org/pipermail/centos-devel/2015-February/012873.html



  WE'RE NOT ON THE DEVEL LIST!


 WHY NOT?


 Yes, I'm shouting.


 I DON'T KNOW WHAT WE'RE YELLING ABOUT


 Seriously though, the change was brought up over a month ago on the -devel
 list. When we're asking for feedback about possible changes, it's on the
 -devel list, because it's about the development of the distro. If you want
 to give input for the direction of the distro, that's the place to do it. I
 would encourage anyone who's interested to join.


From the Community page:


CentOS-devel

This list is a discussion list about the current and further development of
CentOS. If you have questions regarding CentOS, please use the main centos
list - this is strictly about development. 



Most of us are not involved in development of CentOS, and don't have the
time to monitor such a mailing list for possible changes we might want to
be aware of.

Major changes that effect day-to-day operations should be vetted through
the main list, in my opinion.


-- 
Matt Phelps
System Administrator, Computation Facility
Harvard - Smithsonian Center for Astrophysics
mphe...@cfa.harvard.edu, http://www.cfa.harvard.edu
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64


On Thu, 2015-04-02 at 13:08 -0500, Johnny Hughes wrote:

 CentOS releases are NOT the same as EUS and have never been .. yet that
  seems to be what people expect.  We want there to be no doubt on this
  issue.

Is there a commercial motive for this 'unwelcome by most' change ?

If Centos is the same as RHEL then RH can loose valuable sales income
because customers, actual and potential, use free Centos. However if
Centos version numbers are vastly different from RHEL version numbers
and there is no reliable method of equating Centos sub-versions with
RHEL sub-versions, RH gains extra sales because of the uncertainty of
Centos being 'just like' reliable RHEL.

Just a casual thought.


-- 
Regards,

Paul.
England, EU.  Je suis Charlie.


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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

2015-04-02 Thread Ned Slider



On 02/04/15 20:47, Jim Perrin wrote:
 
 
 On 04/02/2015 02:29 PM, Phelps, Matthew wrote:
 On Thu, Apr 2, 2015 at 3:25 PM, Jim Perrin jper...@centos.org wrote:



 On 04/02/2015 01:28 PM, Phelps, Matthew wrote:


 Soliciting our feedback *before* changing everything regarding release
 names would
 have been nice.


 We did.

 http://lists.centos.org/pipermail/centos-devel/2015-February/012873.html



 WE'RE NOT ON THE DEVEL LIST!
 
 WHY NOT?
 

Would it have made a difference? Yes, you asked on that list. And yes,
nearly everyone who responded said no to the change, yet you did it anyway.

If Matthew had been on the list, and had also responded against the
change, would his voice have made the difference?

Seriously, show me a post in that thread from someone not on the CentOS
board speaking strongly in favour of the change. It's a big thread.

The point is, you asked and the community said no (at least those who
were subscribed to the -devel list and took the time to respond). Yet
you did it anyway.

The damage is done now, you can't take it back.



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

[CentOS-docs] Reg: Documentation Toolchain [GSOC]

2015-04-02 Thread kunaal jain

Hi guys,

I have submitted my proposal on google-melange. I have been active in
discussion regarding this on centos-docs as well with Karsten.

I have created a small demo tool chain, to have a clarity on how
process will flow and how site can be generated on git commits and
deploying to hosting platform. You can find the code as well as the
live version at : https://github.com/kunaaljain/test-centos-docs

Please have a look at the proposal and the sample code I have written
and give suggestions on how I can improve the proposal. Please note
that the sample code is written for testing purpose, the actual
toolchain may not use the open source tools I am using in it.

Regards,
Kunal Jain
___
CentOS-docs mailing list
CentOS-docs@centos.org
http://lists.centos.org/mailman/listinfo/centos-docs

Re: [CentOS] OT: Recommended anti-virus for Windows


On Thu, April 2, 2015 4:27 pm, Valeri Galtsev wrote:

 On Thu, April 2, 2015 4:11 pm, J Martin Rushton wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Sorry to mention the opposition here, but I have a family member's
 laptop to protect, and I'm not allowed to upgrade it to Linux.  What's
 the current best recommendation?

 For privately owned machine I would recommend

 free.avg.com

 - one free installation per household is permitted by license. I only am
 testing (and would rather welcome comments): immunet 3 (based on clamav
 which I use for long time on Unix mail servers), I have it installed on a
 few machine that unlikely ever will see any visus, hence I do not have
 sufficient battle ground experience with immunet 3.

One thing I forgot to mention: I also always recommend AGAINST using
kasperski. Kasperski is KGB guy (*cough* *cough* retired. You know in that
service retirement is only feet first dead, so you do your math).

Valeri


 Valeri

 Thanks,
 MArtin
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2.0.22 (GNU/Linux)

 iQIcBAEBAgAGBQJVHbCMAAoJEAF3yXsqtyBl4I8P/AsvH+cyGcG9PDtL8I091WJc
 jaAhT8Z77G8LBTNaCUi1NXaR3zYsxZ1LltS8MyyqpA+TZ5TkwGRI5V0g2h5owrXv
 vmFNHW4DQcnB5D4s5+B50lnjyIWgtLG0BKUwCgLik++U11umHd5sCTqXTaHzlyP8
 Ndz2RAVEm9A8T3My7fKeVF+/c2pt6rKaRoifeTiH+IUnmvuFHPHuQEpLuOx0qKLH
 BCHyg7ZJcpwQEocYMhZu7JkZ/zg5/eCb+0HIq5qOCkeRj64ax0QOMzlvcScBRQDp
 tBzXIAXnFGMNmgE8tvD9Xh2Gi/OKx/bbqRdo8mMzUGUlWSErSt2UMPkpN3Vm3S2C
 wQhSqMoNnxWCypofazmIXH+TKn1/ipUhZXF3GcZsBYDfIb95kvdBrJm//QioI8Fy
 BFGc5Cj9DjXNxIbCfvQuyrG1RDdwHKjt/AMmoB0RXpSwhxRfS2749gyrkGXRUSSd
 IFRpX8Ds0quxx8D9YY96FYX4VbPFhFKIm64OigjLOenedek4A0TpUg7tF5HpyDA7
 SXl/l9wFbqAOIKR+VYHIix9UPqxUkU/6fio1D/RhD+8gulY9Tj4Bx5vjpVkJm4wY
 +Dj0VZ6LyhhkkOTypvENrY2imyxJ+MQ/xKiBQCcvGJIkNcxKr3Xd9D6cFkkkZWR7
 bAaC26I/cC4witLZSC2k
 =1XHp
 -END PGP SIGNATURE-
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos



 
 Valeri Galtsev
 Sr System Administrator
 Department of Astronomy and Astrophysics
 Kavli Institute for Cosmological Physics
 University of Chicago
 Phone: 773-702-4247
 
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos




Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

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

[CentOS] OT: Recommended anti-virus for Windows

2015-04-02 Thread J Martin Rushton

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Sorry to mention the opposition here, but I have a family member's
laptop to protect, and I'm not allowed to upgrade it to Linux.  What's
the current best recommendation?
Thanks,
MArtin
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJVHbCMAAoJEAF3yXsqtyBl4I8P/AsvH+cyGcG9PDtL8I091WJc
jaAhT8Z77G8LBTNaCUi1NXaR3zYsxZ1LltS8MyyqpA+TZ5TkwGRI5V0g2h5owrXv
vmFNHW4DQcnB5D4s5+B50lnjyIWgtLG0BKUwCgLik++U11umHd5sCTqXTaHzlyP8
Ndz2RAVEm9A8T3My7fKeVF+/c2pt6rKaRoifeTiH+IUnmvuFHPHuQEpLuOx0qKLH
BCHyg7ZJcpwQEocYMhZu7JkZ/zg5/eCb+0HIq5qOCkeRj64ax0QOMzlvcScBRQDp
tBzXIAXnFGMNmgE8tvD9Xh2Gi/OKx/bbqRdo8mMzUGUlWSErSt2UMPkpN3Vm3S2C
wQhSqMoNnxWCypofazmIXH+TKn1/ipUhZXF3GcZsBYDfIb95kvdBrJm//QioI8Fy
BFGc5Cj9DjXNxIbCfvQuyrG1RDdwHKjt/AMmoB0RXpSwhxRfS2749gyrkGXRUSSd
IFRpX8Ds0quxx8D9YY96FYX4VbPFhFKIm64OigjLOenedek4A0TpUg7tF5HpyDA7
SXl/l9wFbqAOIKR+VYHIix9UPqxUkU/6fio1D/RhD+8gulY9Tj4Bx5vjpVkJm4wY
+Dj0VZ6LyhhkkOTypvENrY2imyxJ+MQ/xKiBQCcvGJIkNcxKr3Xd9D6cFkkkZWR7
bAaC26I/cC4witLZSC2k
=1XHp
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] OT: Recommended anti-virus for Windows

2015-04-02 Thread m . roth

J Martin Rushton wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Sorry to mention the opposition here, but I have a family member's
 laptop to protect, and I'm not allowed to upgrade it to Linux.  What's
 the current best recommendation?
 Thanks,

I think I've seen Avast mentioned by some trustworthy friends on a techie
mailing list I'm on.

 mark

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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

2015-04-02 Thread Steve Thompson


On Thu, 2 Apr 2015, Les Mikesell wrote:


Well if you define 'always' as 'for CentOS6 and later...


Yes, you are right. I was relying on my obviously faulty and aged memory, 
so I checked on my two remaining CentOS 5 boxes. There is no 
/etc/centos-release file there at all, only an /etc/redhat-release, so 
obviously not a symlink at all. More coffee.


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

Re: [CentOS] emailing plain text to exchange/outlook

2015-04-02 Thread Steven Tardy

 On Mar 31, 2015, at 2:06 PM, Les Mikesell lesmikes...@gmail.com wrote:
 
 outlook will remove line breaks.
 
 Is there something you can do to make a plain text list show up
 correctly short of converting it to html with br's?


Prefix every line in the list with a space like:
 space thing1
 space thing2
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Kernel panic, CentOS 7.1503 fully updated, with executing gkrellm.


On 04/02/2015 07:52 PM, Karanbir Singh wrote:

On 03/04/15 00:18, Lamar Owen wrote:
Ok, I have the vmcore, but the debuginfo for kernel 
3.10.0-229.1.2.el7.x86_64 I can't find. Found and installed for 
kernel 3.10.0-123.13.2.el7.x86_64 but that doesn't help me 
troubleshoot the -229.1.2 kernel. 

debuginfo's should be on their way, I know Johnny was working on that today.

Thanks for the update.  When they are available, I'll try it out.

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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64


 On Thu, 2015-04-02 at 13:08 -0500, Johnny Hughes wrote:
 
  CentOS releases are NOT the same as EUS and have never been .. yet that
   seems to be what people expect.  We want there to be no doubt on this
   issue.


 On Thu, April 2, 2015 2:55 pm, Always Learning wrote:
 
  Is there a commercial motive for this 'unwelcome by most' change ?
 
  If Centos is the same as RHEL then RH can loose valuable sales income
  because customers, actual and potential, use free Centos. However if
  Centos version numbers are vastly different from RHEL version numbers
  and there is no reliable method of equating Centos sub-versions with
  RHEL sub-versions, RH gains extra sales because of the uncertainty of
  Centos being 'just like' reliable RHEL.


On Thu, 2015-04-02 at 16:07 -0500, Valeri Galtsev wrote:

 Indeed. And some conspiracy theorist might add this happened after CentOS
 marrying RH (well, getting tighter relations that is) ;-)

I also noticed it happened after the take-over of Centos by RH, the
funding of Centos people by RH, the legal 'ownership' of Centos branding
by RH's legal department, the surprising increased interest on this list
by Red Hat people (some using non-RH email addresses), ditto Fedora
people.

In business when one pays money, one inevitably expects a reward greater
than the sum of money paid or invested.

Like everyone else I am grateful for the efforts of the Centos team
which brings us a reliable Centos product.


-- 
Regards,

Paul.
England, EU.  Je suis Charlie.


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

Re: [CentOS] OT: Recommended anti-virus for Windows


On Fri, 2015-04-03 at 00:57 +0300, Александр Кириллов wrote:

  One thing I forgot to mention: I also always recommend AGAINST using
  kasperski. Kasperski is KGB guy (*cough* *cough* retired. You know in 
  that
  service retirement is only feet first dead, so you do your math).
 
 Is KGB rant still in vogue in your new homeland?

Isn't it the FSB these days ?  Anyone ever in an intelligence service
never ever completely retires. They do tasks when asked and voluntarily
pass information to their organisation.

Intelligence services do things most people would never ever imagine -
its their job. So Kasperski is definitely suspect software despite UK
bank Barclays giving it freely to their Windoze customers.

With Putin rearming and expanding military forces for about the last 10
years, authorising probing flights by military aircraft, incursions by
submarines, invasion of Ukraine, shooting-down the civilian flight above
Ukraine, vetoing UN intervention in Syria because of the Russian naval
base in Syria ...

Don't forget Putin was the 'resident' Russian spy in Germany and a
senior officer in the Russian spies, who has many links to the Russian
mafia especially to the Russian mafia in Cyprus and more recently in
southern Spain.

Perhaps those in the west have better access to information ?

To avoid upsetting Centos bosses please send any responses off-list.

Thank you.





-- 
Regards,

Paul.
England, EU.  Je suis Charlie.


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

Re: [CentOS] systemctl (again)

2015-04-02 Thread J Martin Rushton

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

SELinux certainly was causing fun and games.  I copied your suggestion
to /etc/systemd/user/timidity.service (mode 750) but it's still not happy:

[root@tamar user]# systemctl status timidity
timidity.service
   Loaded: not-found (Reason: No such file or directory)
   Active: failed (Result: exit-code) since Th...

... Starting LSB: Add and remove timidity...
... timidity.service: control process exited, code=exited status=203
... Failed to start LSB: Add and remove timidity.
... Unit timidity.service entered failed state.
... Stopped timidity.service.

I've wasted way too much time on this, I've put it in my .profile.
The weirdness of systemctl will have to wait!

Thanks all

On 02/04/15 22:16, Andrew Holway wrote:
 It might be SELinux. On a standard system; when we run things as a
 user from the command line SELinux rules do not apply. It would
 explain why it works manually but not via systemd.
 
 Rather than using an init.d script you might want to try using a
 systemd service. I haven't tested but something like this should
 work.
 
 [Unit] Description=timidity daemon
 
 [Service] PIDFile=/var/run/timidity.pid User=someuser 
 Group=someuser WorkingDirectory=/home/someuser 
 ExecStart=/bin/timidity ExecReload=/bin/kill -s HUP $MAINPID 
 ExecStop=/bin/kill -s TERM $MAINPID PrivateTmp=true
 
 
 
 
 
 On 2 April 2015 at 23:07, J Martin Rushton
 martinrushto...@btinternet.com wrote:
 
 I've been trying to get the timidity system running as a daemon.
 I wrote the following init script:
 
 #!/bin/sh # # timidity # ### BEGIN INIT INFO # Provides: timidity #
 Required-Start: # Required-Stop: # Default-Start:  2 3 4 5 #
 Default-Stop: 0 1 6 # Short-Description: Add and remove timidity #
 Description: ### END INIT INFO
 
 . /etc/rc.d/init.d/functions
 
 RETVAL=0 PROG=timidity EXEC=/bin/$PROG 
 PIDFILE=/var/run/timidity.pid
 
 function start { [[ -x $EXEC ]] || exit 5 echo -n Starting $PROG:
  $EXEC -iAD RETVAL=$? echo return $RETVAL }
 
 function stop { echo -n Stopping $PROG:  killproc $EXEC -TERM 
 RETVAL=$? echo return $RETVAL }
 
 case $1 in start)  start RETVAL=$? ;; stop)   stop RETVAL=$? ;; 
 status) status $PROG RETVAL=$? ;; restart) stop start ;; reload) 
 stop start ;; *) echo $Usage: $prog 
 {start|stop|status|restart|reload} exit 1 esac exit $RETVAL
 
 
 When run through systemctl during startup it fails:
 
 [root@tamar init.d]# systemctl status timidity timidity.service -
 LSB: Add and remove timidity Loaded: loaded
 (/etc/rc.d/init.d/timidity) Active: active (exited) since Thu ... 
 Process: 784 ExecStart=/etc/rc.d/init.d/timidity start 
 (code=exited, status=0/SUCCESS)
 
 ... Starting LSB: Add and remove timidity... ... Starting
 timidity: ... jack_client_new: deprecated ... Started LSB: Add and
 remove timidity. ... Cannot connect to server socket err = No such
 file or directory ... Cannot connect to server request channel ...
 jack server is not running or cannot be started ... Couldn't open
 output device
 
 But when run directly is works fine:
 
 [root@tamar init.d]# ./timidity start Starting timidity: TiMidity
 starting in ALSA server mode Opening sequencer port: 128:0 128:1
 128:2 128:3
 
 If I use # service timidity start it also fails.
 
 I _think_ that what is happening is that systemctl is stripping
 off the switch.  I've spent a couple of hours searching for any
 links or explanation and got nowhere.  I even knocked up a script
 to try and separate the two parts: #!/bin/sh cd /etc/init.d 
 ./timidity start but to no avail.
 
 If there is a simple fix could someone point me there, if it's
 complex don't bother, I only need the daemon when running MIDI and
 can start it by hand.
 ___ CentOS mailing
 list CentOS@centos.org 
 http://lists.centos.org/mailman/listinfo/centos
 
 ___ CentOS mailing
 list CentOS@centos.org 
 http://lists.centos.org/mailman/listinfo/centos
 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJVHcVWAAoJEAF3yXsqtyBlHDcP/2VULTDUzhuWefhRm1pqhMpi
S/bOjeNIuhhmpnyPhnCg4xm5jYXFa1ix6q4RCxv70HAGXkv/dZpFOZ63/ni+nKnD
5xyjez0TLpvlYGg3sGJhbtatenwYMlCy4KdZt+JnuWNce/9cgPy8/oALxSOQfmp/
Comfk2d3BN/g7TxpNs1zPetFEW2fytbzh0IMjF7pOe5OtOPe+FMI8Y8wZSbkzd73
6I/5bmL6nWEHelI65dB4KaXDsWfGoc9ZkVbXJ2lHrx70avbuyKu9o+jD9MVYxa83
AgGUGlt7oZuuYGVLy4oR+T6c6O+LdLXgSuI79RsSBwwdwSkTLGOIT5ljDV53krum
2g93QtJyGtPL2+oCNqvcqKhkO8RVJ/i9B9huHvRYT0s9TcJ6+54nrCbv54y6zXc2
eonvwyuFtGkRPG2spOotK342dx63cus1T+vQU+d4ohBTANvSkh6NVFb0nbAbADJy
FLRx3IdFRbe05Ehsb6hTTEnTZMTLNXx1EruvPJdTpA4c6j2eU35LwF/vEeOC+5Kq
XESUSr6kSSgFHmZB40rt03lPcMameqIpWBVBgQln7KTkxxVY5yb/zjm7Cz9HdsUm
TK96Gf+Xxf/iV6E/fZAsBLQmqbHL/6WeteF0t8qa7YcET1Y68xkJ/8Rbn1/Ers/C
/DE83/mqV3dz2SQO6Di+
=iFvP
-END PGP SIGNATURE-
___
CentOS mailing list
CentOS@centos.org

Re: [CentOS] Kernel panic, CentOS 7.1503 fully updated, with executing gkrellm.


On 04/02/2015 04:05 PM, Lamar Owen wrote:

On 04/02/2015 10:33 AM, Lamar Owen wrote:
 That's why I still hope it's local to my machine.  But now to try to 
reproduce on other hardware.  (for reference, hardware on which I saw 
the bug is a Dell Precision M6500 with a Core i7-740QM and an AMD/ATI 
Firepro 7820M video, with / on a Samsung PM830 SSD)
Ok, I can't reproduce on my Precision M4300 with a Core 2 Duo T9300 
and nVidia Quadro 360M video.  However, I do notice some differences 
between my M6500's login screen and the login screen of the M4300, 
notably the CentOS logo at bottom center.  So, to do more digging..


It does reproduce on the M6500, but at least no corrupted libs this 
time.  Karanbir, Johnny, where might I find the -229.1.2 kernel's 
debuginfo package to get a backtrace from the vmcore I have from the panic?


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

Re: [CentOS] Kernel panic, CentOS 7.1503 fully updated, with executing gkrellm.

On 03/04/15 00:18, Lamar Owen wrote:
 On 04/02/2015 04:35 PM, Marcelo Ricardo Leitner wrote:

 If you can share the original backtraces, it already helps and someone
 may even point you to a fix if it's a known issue.


 
 Ok, I have the vmcore, but the debuginfo for kernel
 3.10.0-229.1.2.el7.x86_64 I can't find.  Found and installed for kernel
 3.10.0-123.13.2.el7.x86_64 but that doesn't help me troubleshoot the
 -229.1.2 kernel.

debuginfo's should be on their way, I know Johnny was working on that today.


-- 
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] OT: Recommended anti-virus for Windows

2015-04-02 Thread Brian Bernard

Well them plus CIA, NSA, Barney the Dinosaur and Teletubbies.

Brian Bernard
On Apr 2, 2015 5:58 PM, Александр Кириллов nevis...@infoline.su wrote:

 One thing I forgot to mention: I also always recommend AGAINST using
 kasperski. Kasperski is KGB guy (*cough* *cough* retired. You know in that
 service retirement is only feet first dead, so you do your math).


 Is KGB rant still in vogue in your new homeland?

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

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

Re: [CentOS] OT: Recommended anti-virus for Windows




On 04/02/15 17:35, Brian Bernard wrote:

Well them plus CIA, NSA, Barney the Dinosaur and Teletubbies.

Brian Bernard
On Apr 2, 2015 5:58 PM, Александр Кириллов nevis...@infoline.su wrote:


One thing I forgot to mention: I also always recommend AGAINST using

kasperski. Kasperski is KGB guy (*cough* *cough* retired. You know in that
service retirement is only feet first dead, so you do your math).



Is KGB rant still in vogue in your new homeland?



I dislike KGB, NSA, CIA, and all other similar services and dirty trick 
divisions alike. Whichever country they work for. Always did. Never 
considered myself any sort of fighter against them. But I do advise my 
users to stay away from the ones I personally am certain about 
(kasperski antivirus in this case). And I do assume everyone who listens 
to my advise uses one's own brain to either take an advise or not. And 
come to ones own conclusion about either kasperski (in this case) or 
about me, - as you, Alexandr, did. Either is fine by me.


Sorry, Alexandr, it didn't mean to sound personal. And I know Russians 
often take anything said about anything else Russia related personally. 
But I do feel obliged to warn people whenever appropriate. Even taking 
chance stepping on other people toes (good people as well which I'm sure 
you are) if the last may be to sensitive about the subject.


My apology I'm answering somebody's else message, yours somehow didn't 
show up in my e-mail, but I'm sure there is no harm in that.


Valeri


Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247

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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64


On Thu, 2015-04-02 at 22:22 +0100, Ned Slider wrote:

 Would it have made a difference? Yes, you asked on that list. And yes,
 nearly everyone who responded said no to the change, yet you did it anyway.

..

 The damage is done now, you can't take it back.

But they can revert to the normal system appreciated by the overwhelming
quantity of Centos users all around the world.  Everyone makes mistakes
and one one here wants grovelling apologies, just a change to the
original and better system - even with dates,

Example  Centos-7-1-1504 ...


-- 
Regards,

Paul.
England, EU.  Je suis Charlie.


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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64


On Thu, 2015-04-02 at 17:37 -0400, Lamar Owen wrote:

 On 04/02/2015 04:16 PM, Always Learning wrote:
  Although most people in the world will privately complain the vast
  majority do not complain in public.  Where is your contrary evidence
  that this non-beneficial and illogical change is welcome by the majority
  of Centos users ?
 
 The burden of proof for your statement is on you, not me.  I never said 
 it was welcome by most, either.  I might even agree with your statement, 
 for that matter; but you made the statement; you have the burden of 
 proof of that statement.  I do not need to prove the converse.

Lamar,

You are a really great guy. Earlier you admitted the change was not
beneficial and now you seem to agree the change was NOT welcome by most.

Query  why did Centos bosses make the change ?


-- 
Regards,

Paul.
England, EU.  Je suis Charlie.


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

Re: [CentOS] Kernel panic, CentOS 7.1503 fully updated, with executing gkrellm.


On 04/02/2015 04:35 PM, Marcelo Ricardo Leitner wrote:


If you can share the original backtraces, it already helps and someone 
may even point you to a fix if it's a known issue.





Ok, I have the vmcore, but the debuginfo for kernel 
3.10.0-229.1.2.el7.x86_64 I can't find.  Found and installed for kernel 
3.10.0-123.13.2.el7.x86_64 but that doesn't help me troubleshoot the 
-229.1.2 kernel.


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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

On 02/04/15 21:35, Phelps, Matthew wrote:

 See my reply earlier. The description of the centos-devel list says this
 is strictly about development.


Matt, come join the contributor base - be a commnuity communication
liason ( or, I am sure we can find a title to quantify this ).

stretching this a bit futher : lets see if we can find 10 people who
might be considered 'community beacons', who could / would act as
commnuity comms and liason to make sure we are driving in the right
directions and communicating things in the most impactful manner.

I am willing to lobby the board to then allow this group to spectate and
feedback into Board Meetings ( we meet once a month ).

One data point I want to drop in here is that less than 0.1 % of the
CentOS user base has any contact with the project ( wherein I imply,
lists + forums + irc + bugs + wiki ), so we might need to spread the net
wide to find a reasonable representation.

thoughts ?


-- 
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Boot Failure [Solved]

2015-04-02 Thread Nux!

Grub2 comes with a whole load of fails.

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

- Original Message -
 From: pro alias proa...@gmail.com
 To: centos@centos.org
 Sent: Thursday, 2 April, 2015 21:44:59
 Subject: [CentOS] Boot Failure [Solved]

 I writ:
 The latest kernel kernel-3.10.0.229.1.2.el7.x86_64 appears not to like
 our Supermicro X9SBAA-F board. It fails on boot with the last message
 before panic being apic_timer_interupt  snipped rest
 
 It turned out that only one X9SBAA box was affected.
 
 Deleting and reinstalling the kernel did not fix the issue.
 The problem turned out to be the old initrd issue in grub.conf. We have
 seen this from time to time on updates in the past. The line:
initrd /initramfs-3.10.0-229.1.2.el7.x86_64.img
 was missing from grub.conf. When manually inserted, the new kernel
 worked swimmingly. I suspect that this is related to updating grub
 either immediately before or after a new kernel is installed. It's just
 enough of an annoyance that someone with spare time on their hands
 might want to look in it.
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64


On Thu, 2015-04-02 at 18:40 -0400, Steve Thompson wrote:

 Yes, you are right. I was relying on my obviously faulty and aged memory, 
 so I checked on my two remaining CentOS 5 boxes. There is no 
 /etc/centos-release file there at all, only an /etc/redhat-release, so 
 obviously not a symlink at all. More coffee.

I prefer tea. On my C5 I have

.l /etc/redhat-release 
-rw-r--r-- 1 root root 28 Sep 19  2014 /etc/redhat-release

However on C6

.l /etc|.g release
-rw-r--r--.  1 root root   27 Oct 23 12:41 centos-release
lrwxrwxrwx.  1 root root   14 Dec 14 18:08 redhat-release - centos-release
lrwxrwxrwx.  1 root root   14 Dec 14 18:08 system-release - centos-release


-- 
Regards,

Paul.
England, EU.  Je suis Charlie.


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

[CentOS] Openssl C6 distro tag different from upstream

2015-04-02 Thread Leonard den Ottolander

Hi,

Just noticed that the distro tag used in openssl is different from
upstream. Upstream and the last update (openssl-1.0.1e-30.el6_6.7) use
el6_6 where as the latest update (openssl-1.0.1e-30.el6.8) uses
el_6. Any reason for this discrepancy?

Regards,
Leonard.

-- 
mount -t life -o ro /dev/dna /genetic/research


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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

2015-04-02 Thread mark


On 04/02/15 00:51, Lamar Owen wrote:

On 04/01/2015 08:12 PM, Always Learning wrote:

1. What is the logically reason for this alleged improvement ?


I never said it was an improvement.  I just said that I didn't think it was
that big of a deal, and it boggles my mind that people are calling a change of
an ISO's file name 'unwise' and even comparing it to a Microsoft move.  I just
don't see it as being that big of a problem. Nor do I see it as an
improvement.  But the question was asked about where such a change might have
been discussed, and I pointed to the long and drawn out centos-devel thread in
which the background for the date-based numbering was beaten to death (and
beyond).  The CentOS devs have stated that the CentOS Board voted on it, and
they have the decision-making power to do so.  And they are all reasonable
people.


But only those on the devel list ever saw the discussion. Those of us whose 
job it is to be sysadmins, and run many systems, don't tend to be on that list 
also.


Had you, for example, made it release.subrelease.date (7.1.1503), it would 
have been less disruptive and annoying.


mark



2. How are users of all types, from all around the world, benefiting
from this change ?

This change makes it unequivocally clear that CentOS 7.1503 is not exactly the
same as upstream RHEL 7.1, although it is functionally equivalent (where the
meaning of functionally equivalent has been hashed to death, too, but it
basically means binary-compatible but not necessarily binary-identical).
Whether you consider that a benefit or not is up to you.  I'm personally
neutral on the issue.

Consolidating two replies:
On 04/01/2015 07:58 PM, Always Learning wrote:

On Wed, 2015-04-01 at 16:15 -0400, Lamar Owen wrote:


On 04/01/2015 03:33 PM, Always Learning wrote:
(1) removing sub-version numbers is wrong; and ...


That is a matter of opinion.  In my opinion, assigning sub-version numbers to
what was originally intended to be, by Red Hat, quarterly updates (almost
Service Packs, if you will, much like SGI's numbering of their Foundation and
ProPack products for the Altix server line) is what is illogical.  Of course,
the updates aren't quarterly any more, and other aspects of the versioning
have morphed and changed over the years since the RHAS days (well, even back
in certain branches of RHL 6.2, for that matter).

So you could read '7.1' as 'version 7 service pack 1.'  My opinion is that
sub-version numbers give a mistaken impression that the update number is a
real 'version' when it was not originally so. Further, in reality the update
number is meaningless for compatibility checks, as it is more than possible to
have a fully updated CentOS x system that claims to be x.0 but has all the
packages, save centos-release, of the latest x.y; further, it is easily
possible to install the CentOS x.6 centos-release package on a completely
unpatched x.0 system, making the contents of andy of the /etc/*-release files
not terribly useful for strict versioning.

It is my opinion, although it's not a vehement opinion, that beginning the x.y
practice is what was illogical.  But it was done, and it is over, and I have
more important things to do than gripe over semantics such as that.


Creating confusion where there was originally none is essentially silly.


I am not so easily confused by the new numbering; what the ISO is named is
orthogonal to what it contains, at least in my mind.


How many times has Johnny and others asserted that Centos is the same as
RHEL ?

The assertion is that CentOS is functionally equivalent to the upstream
product.  It is not 'the same as' nor can it be and still remove the
trademarked branding of the upstream release.  It is binary compatible without
being binary identical. And as the meaning of 'binary compatible' has also
been hashed to death, I'll not further clutter the traffic on this list about
what it means.  It's easy enough to read the centos-devel archives to see for
yourself.


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



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

Re: [CentOS] Centos7: start job running for dev/mapper-centos\x2dhome.device

2015-04-02 Thread johan . vermeulen7



- Oorspronkelijk bericht -
Van: johan vermeulen7 johan.vermeul...@telenet.be
Aan: CentOS mailing list centos@centos.org
Verzonden: Donderdag 2 april 2015 12:08:18
Onderwerp: [CentOS] Centos7: start job running for  
dev/mapper-centos\x2dhome.device

Hello All, 

I have this Centos7 machine thats dualbooted with Win7. 
It's Centos7 with Mate desktop. 
The upgrade to Centos7.1 was interrupted. I ssh-d into the machine and finished 
it manualy, 
by issuing the command 
package-cleanup --cleandupes and 
yum update 

Now I' missing some packages, after some reïnstalling, I can boot again. 

However, I can not log in. 

EM:apr 02 13:58:25 jvanbaekel lightdm[1596]: ** (process:2903): WARNING **: 
Failed to open CK session: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.ConsoleKit was not provided by any .service files 

So far I was not able to find out which pakages I'm missing for lightdm. 

Can anyone help me with this? 

greetings, Johan 


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

My apologies for the confusing title; that was the original EM.
At first the machine would not boot.
After searching, I got as far as not being able to log on.

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

Re: [CentOS] Kernel panic, CentOS 7.1503 fully updated, with executing gkrellm.

2015-04-02 Thread Marcelo Ricardo Leitner


On 02-04-2015 02:04, Lamar Owen wrote:

Just a heads up, since I know gkrellm is in EPEL and not in the main
CentOS repos.  However, something fairly fundamental has changed, as
prior to updating, gkrellm worked fine, but now every time I execute
gkrellm the kernel panics.

I'm going to triage on a different machine, as the panic corrupted at
least one system library used by nautilus, but rpm -Va is your friend in
these situations, and yum reinstall is its close kin.  So I would prefer
to duplicate on a burner machine, and I'll try to get a snapshot of the
panic.

If anyone else wants to try to reproduce, simply try installing the
current gkrellm from EPEL on a fully updated CentOS 7 machine and see if
it panics on you.  I kindof hope it's local to my machine and its
configuration (/home is LUKS, for instance), and it would be great if
someone could verify that.


If it's that easy to reproduce, please grab the panic message or 
generate a vmcore through crashdump and report it at bugzilla.redhat.com 
against kernel component.


You may be using an EPEL application but kernel shouldn't be panicking 
like that, specially if you're running it as an user.


  Marcelo

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

[CentOS] CentOS-announce Digest, Vol 122, Issue 2

2015-04-02 Thread centos-announce-request

Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@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. CESA-2015:0771 Important CentOS 7 thunderbird Security Update
  (Johnny Hughes)
   2. CEEA-2015:0717 CentOS 7 tzdata Enhancement Update (Johnny Hughes)
   3. CEBA-2015:0769  CentOS 6 libvirt BugFix Update (Johnny Hughes)
   4. CEBA-2015:0772  CentOS 6 openssl BugFix Update (Johnny Hughes)
   5. CESA-2015:0771 Important CentOS 7 thunderbird Security Update
  (Johnny Hughes)
   6. CESA-2015:0771 Important CentOS 5 thunderbird Security Update
  (Johnny Hughes)


--

Message: 1
Date: Wed, 1 Apr 2015 14:33:26 +
From: Johnny Hughes joh...@centos.org
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2015:0771 Important CentOS 7
thunderbird Security Update
Message-ID: 20150401143326.ga46...@n04.lon1.karan.org
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2015:0771 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-0771.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
7ebfced7a86fc0807143f90dbf4ca28fdd63b38d2cfe442fffbc8ca3d9395394  
thunderbird-31.6.0-1.el7.centos.x86_64.rpm

Source:
61228bdaf11280dbf4a5f9360fc668b3460f5f9cc8ec981a3efb808384207d86  
thunderbird-31.6.0-1.el7.centos.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net



--

Message: 2
Date: Wed, 1 Apr 2015 14:33:03 +
From: Johnny Hughes joh...@centos.org
To: centos-annou...@centos.org
Subject: [CentOS-announce] CEEA-2015:0717 CentOS 7 tzdata Enhancement
Update
Message-ID: 20150401143303.ga46...@n04.lon1.karan.org
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Enhancement Advisory 2015:0717 

Upstream details at : https://rhn.redhat.com/errata/RHEA-2015-0717.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
818c1d17d5adb9ab3d6757430050e8070e06e2af4ee54a1d8bdfb0cb460722ee  
tzdata-2015b-1.el7.noarch.rpm
71e6f2749ec0de934123278410f5df6209a4190d6e11081b47704930818abed5  
tzdata-java-2015b-1.el7.noarch.rpm

Source:
8ec69e7d73b7f0cd4cbef055142adf3c5098070bfdb2720e7c6a94614c66ab63  
tzdata-2015b-1.el7.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net



--

Message: 3
Date: Wed, 1 Apr 2015 13:37:08 +
From: Johnny Hughes joh...@centos.org
To: centos-annou...@centos.org
Subject: [CentOS-announce] CEBA-2015:0769  CentOS 6 libvirt BugFix
Update
Message-ID: 20150401133708.ga41...@n04.lon1.karan.org
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Bugfix Advisory 2015:0769 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-0769.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

i386:
4ad971b924283fbc82dae8448ee1b66ecbc848ef04db26678c076ce7212f2170  
libvirt-0.10.2-46.el6_6.4.i686.rpm
2c11678643a4b451f39126892d4760c819e2d10e17b7665438e5535710ad0821  
libvirt-client-0.10.2-46.el6_6.4.i686.rpm
23285525bead07faa02d923eb7524ae5f5869b1dd87c4a1d3c44c9b3c3ed4102  
libvirt-devel-0.10.2-46.el6_6.4.i686.rpm
b04c0f7edbd1554eb510efc2974a7b4ba5207230c5b6697433eafbd677c19fd1  
libvirt-python-0.10.2-46.el6_6.4.i686.rpm

x86_64:
1c73ef3ecea2073fe7159f92c475c1332dbd54824897382304f520c8a33aed28  
libvirt-0.10.2-46.el6_6.4.x86_64.rpm
2c11678643a4b451f39126892d4760c819e2d10e17b7665438e5535710ad0821  
libvirt-client-0.10.2-46.el6_6.4.i686.rpm
653aa707dbcf4df2bba46c2324d5cbb98354d1b987eb67a7b1d26bea63e37601  
libvirt-client-0.10.2-46.el6_6.4.x86_64.rpm
23285525bead07faa02d923eb7524ae5f5869b1dd87c4a1d3c44c9b3c3ed4102  
libvirt-devel-0.10.2-46.el6_6.4.i686.rpm
0756926b4fd386e5ffc83182ef87cefc1aa9430c72514480ba6157cdc4a0f9b9  
libvirt-devel-0.10.2-46.el6_6.4.x86_64.rpm
8a67dfcba8fe5f0cca99698b19241b84b31167ecb233644e70b81461e219981a  
libvirt-lock-sanlock-0.10.2-46.el6_6.4.x86_64.rpm
90c1e5d9057e403e2f351f0448c564e6e66958e7d8d0a8306854fb65fafc29f7  
libvirt-python-0.10.2-46.el6_6.4.x86_64.rpm

Source:
4a3e98c3a2c0e26729f92c5a5b14df9eb01ca9e2b485a512598a0ecce653ac30  
libvirt-0.10.2-46.el6_6.4.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net

[CentOS] Centos7: start job running for dev/mapper-centos\x2dhome.device

2015-04-02 Thread johan . vermeulen7

Hello All, 

I have this Centos7 machine thats dualbooted with Win7. 
It's Centos7 with Mate desktop. 
The upgrade to Centos7.1 was interrupted. I ssh-d into the machine and finished 
it manualy, 
by issuing the command 
package-cleanup --cleandupes and 
yum update 

Now I' missing some packages, after some reïnstalling, I can boot again. 

However, I can not log in. 

EM:apr 02 13:58:25 jvanbaekel lightdm[1596]: ** (process:2903): WARNING **: 
Failed to open CK session: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.ConsoleKit was not provided by any .service files 

So far I was not able to find out which pakages I'm missing for lightdm. 

Can anyone help me with this? 

greetings, Johan 


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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

2015-04-02 Thread Leon Fauster


thought minor version vs rolling Everything - this implies that the origin 
base has one root - but thats not the case (pragmatically speaking). There is 
still a rebase or at least a incompatibility between the minor versions 
(as shown recently 7.0-7.1 for kernel modules) and stated in the list by 
Johnny (different context, for EL6):

   quoteAs far as what kernel is designed for which release ... every point
   release (minor version) will have its own kernel branch associated with
   it.../quote

There exists more examples where this borders are important. So, breaking the 
borders between the minor releases will make the things more intransparent. 
Rolling it within a minor release is still great. /thought

--
LF


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

Re: [CentOS-es] consulta de instalación servidor web

2015-04-02 Thread Alexis Espinoza

buenos dias a todos, y gracias por sus consejos, finalmente pude instalar
Centos en un netbook NP N100 Samsung, instale version minimal con desktop,
despues pude instalar lamp, lo extraño es que solo activa la red
inalambrica y eth0 pese a que la reconoce no la activa.

les adjunto lo que me indica lspci y ifconfig, reinicie el servicio y no
hay caso con que conecte a internet con eth0.

[murdok@halcon ~]$ lspci
00:00.0 Host bridge: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx
DMI Bridge
00:02.0 VGA compatible controller: Intel Corporation Atom Processor
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
00:02.1 Display controller: Intel Corporation Atom Processor
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition
Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1
(rev 02)
00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2
(rev 02)
00:1c.2 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 3
(rev 02)
00:1c.3 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 4
(rev 02)
00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI
Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI
Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI
Controller #3 (rev 02)
00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI
Controller #4 (rev 02)
00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI
Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation NM10 Family LPC Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation NM10/ICH7 Family SATA Controller
[AHCI mode] (rev 02)
00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 02)
05:00.0 Network controller: Intel Corporation Centrino Wireless-N 100
09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 05)
[murdok@halcon ~]$ ifconfig
eth0  Link encap:Ethernet  HWaddr E8:11:32:5F:7E:F9
  inet6 addr: fe80::ea11:32ff:fe5f:7ef9/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:6279 errors:0 dropped:0 overruns:0 frame:0
  TX packets:598 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:2057469 (1.9 MiB)  TX bytes:72568 (70.8 KiB)

loLink encap:Local Loopback
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:36 errors:0 dropped:0 overruns:0 frame:0
  TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:2122 (2.0 KiB)  TX bytes:2122 (2.0 KiB)

[murdok@halcon ~]$ su
Contraseña:
[root@halcon murdok]# /etc/init.d/network restart
Interrupción de la interfaz eth0:  [  OK  ]
Interrupción de la interfaz de loopback:   [  OK  ]
Activación de la interfaz de loopback: [  OK  ]
Activando interfaz eth0:  Estado de conexión activa: activando
Ruta de conexión activa: /org/freedesktop/NetworkManager/ActiveConnection/86

** (process:2138): WARNING **: _nm_object_get_property: Error getting
'State' for /org/freedesktop/NetworkManager/ActiveConnection/86: (19)
Method Get with signature ss on interface
org.freedesktop.DBus.Properties doesn't exist


estado: desconocido
Error: Activación de conexión falló.
   [FALLÓ]
[root@halcon murdok]#


alguna sugerencia para conectarme por medio de eth0???

atte.


Alexis

El 1 de abril de 2015, 11:39, Robyir Antonio Loreto Ruiz 
robyirlor...@gmail.com escribió:

 Otra cosa... el xampp no inicia al arrancar el sistema operativo... debes
 crear un enlace simbólico en /etc/init.d que apunte hacia /opt/lampp/lampp
 y agregarlo con el chkconfig --add lampp y queda listo para iniciar al
 arrancar el sistema operativo

 El 1 de abril de 2015, 10:05 a. m., Robyir Antonio Loreto Ruiz
 robyirlor...@gmail.com escribió:

  Saludos desde Venezuela... Te recomiendo el XAMPP que no es instalador
  sino el que viene comprimido en un .tar.gz ...es para sistemas de 32bits
  ... si lo necesitas montar en un sistema de 64bits hay que instalar una
  libreria que no recuerdo como se llama pero queda bien es excelente
 por
  su portabilidad solo lo descomprimes en /opt y lo ejecutas con
  /opt/lampp/lampp start ... luego lo configuras con /opt/lampp/lampp
  security para establecer las contraseñas de los diversos productos que
 trae
  mysql proFTPD etc 
 
  El 1 de abril de 2015, 7:37 a. m., José Luis Respeto Alvarez
  joseluisresp...@gmail.com escribió:
 
  Puedes instalar la distribución que quieras, yo lo tengo

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

On Thu, Apr 2, 2015 at 12:54 AM, John R Pierce pie...@hogranch.com wrote:
 you guys sure get your panties in a bunch over something as silly as the iso
 file name.

 if you don't like the name, rename it... sheesh.


I'm not bothered so much by the actual name as by the justification of
it having been discussed on the -devel list - where in fact pretty
much all of the discussion was that the minor rev number was important
and should stay in.

-- 
  Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] NFS Stale file handle drives me crazy (Centos 6)

2015-04-02 Thread Götz Reinicke - IT Koordinator

Hi folks,

I have a Centos 6 NFS server, which dirves me crazy.

The directory I try to export cant be accessed by different clients.

I tried a centos 7, centos 6 and a pool of vmware esxi 5.5 systems.

At the client side I get errors like:

mount.nfs: Stale file handle

or Sysinfo set operation VSI_MODULE_NODE_mount failed with the tatus
Unable to query remote mount point's attributes.


On the server I get messages in the log like

svc: 172.17.252.35, port=851: unknown version (0 for prog 13, nfsd)

rpc.mountd[1927]: authenticated mount request from 


The curious thing is, that other directories exported on the same
filesysten can be exported.


so /home/stuff works /home/students fails. chmode 777 is set,
/etc/exports is double checked. nfs/rpc/etc is up and running. selinux 
firewall for debugging off.

I use xfs on all shared filesystems.

Googling for VMWARE and native NFS suggestions did not help so far :-/

Any hint or suggestion is very very welcome! Regard  thanks . Götz

-- 
Götz Reinicke
IT-Koordinator

Tel. +49 7141 969 82 420
E-Mail goetz.reini...@filmakademie.de

Filmakademie Baden-Württemberg GmbH
Akademiehof 10
71638 Ludwigsburg
www.filmakademie.de

Eintragung Amtsgericht Stuttgart HRB 205016

Vorsitzender des Aufsichtsrats: Jürgen Walter MdL
Staatssekretär im Ministerium für Wissenschaft,
Forschung und Kunst Baden-Württemberg

Geschäftsführer: Prof. Thomas Schadt

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

[CentOS] Iptables config removed with 7.1 update

2015-04-02 Thread Paul R. Ganci

I had turned off firewalld and was using iptables when I originally 
installed CentOS 7.0. Two days ago I upgraded my CentOS 7.0 to 7.1. 
Everything seemed to be fine. Today I discovered that my iptables 
configuration was removed with the update. Has anyone else experienced 
this on doing upgrade? Literally the /etc/sysconfig/iptables is gone and 
the /etc/sysconfig/iptables-config is the blank template that comes with 
the distribution. This seems to me to be a serious bug with the upgrade.


--
Paul (ga...@nurdog.com)
(303)257-5208

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

Re: [CentOS] Iptables config removed with 7.1 update

2015-04-02 Thread Frank Cox

On Thu, 02 Apr 2015 22:42:02 -0600
Paul R. Ganci wrote:

 Literally the /etc/sysconfig/iptables is gone and 
 the /etc/sysconfig/iptables-config is the blank template that comes with 
 the distribution. This seems to me to be a serious bug with the upgrade.

Do you have a .rpmsave file in that directory?  If so, that's your old 
configuration and the new version has different options or settings available.

-- 
MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] Boot Failure Lastest CEntos 7 Kernel on X9SBAA-F Board

2015-04-02 Thread pro alias

 The latest kernel kernel-3.10.0.229.1.2.el7.x86_64 appears not to like
our Supermicro X9SBAA-F board. It fails on boot with the last message
before panic being apic_timer_interupt . Previous kernels load very well.
We erased and reinstalled the kernel, it verifies good as does everything
else using rpm- qaV.
Anyone have any ideas?? Pretty hard to troubleshoot when you just get the
last few lines on the screen.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

It's not just the name of the ISO file. c.f. the VERSION_ID variable in
/etc/os-release

On Thu, Apr 2, 2015 at 10:52 AM, Always Learning cen...@u64.u22.net wrote:


 On Wed, 2015-04-01 at 22:54 -0700, John R Pierce wrote:

  you guys sure get your panties in a bunch over something as silly as the
  iso file name.

 You may wear them, many of us don't :-)

  if you don't like the name, rename it... sheesh.

 Its about a consistent and logical approach to identifying versions,
 revisions and differences between changes.

 How is the latest numbering system an improvement ? Marks idea of

 {major version}-{sub version}-{mmdd} ..

 is clearly a good proposal

 --
 Regards,

 Paul.
 England, EU.  Je suis Charlie.


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




-- 
Matt Phelps
System Administrator, Computation Facility
Harvard - Smithsonian Center for Astrophysics
mphe...@cfa.harvard.edu, http://www.cfa.harvard.edu
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64


On 04/02/2015 10:59 AM, Phelps, Matthew wrote:

It's not just the name of the ISO file. c.f. the VERSION_ID variable in
/etc/os-release
In that particular place it is actually rather important, but that is 
orthogonal to the ISO name.

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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

On Thu, Apr 2, 2015 at 11:19 AM, Lamar Owen lo...@pari.edu wrote:

 On 04/02/2015 10:59 AM, Phelps, Matthew wrote:

 It's not just the name of the ISO file. c.f. the VERSION_ID variable in
 /etc/os-release

 In that particular place it is actually rather important, but that is
 orthogonal to the ISO name.


I agree, but this thread started off with a more general discussion of
release/version numbering.

-- 
Matt Phelps
System Administrator, Computation Facility
Harvard - Smithsonian Center for Astrophysics
mphe...@cfa.harvard.edu, http://www.cfa.harvard.edu
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] SEmodule dependency hell.

2015-04-02 Thread Andrew Holway

File a bug!!!

On 2 April 2015 at 16:20, James B. Byrne byrn...@harte-lyne.ca wrote:


 On Wed, April 1, 2015 16:09, Andrew Holway wrote:
  I used the command: semanage port -m -t http_port_t -p tcp 8000
  to relabel a port. perhaps you could try:
  semanage port -m -t unconfined_t -p tcp 8000
  Failing that; would it work to run your application in the httpd_t
  domain?
 

 I ended up having to create a custom policy to allow the other
 application to have access to the http_port_t context.  Which is not
 an issue given that no httpd service is, or will ever be, installed on
 that host.

 However, it seems a rather dangerous hole in the logical design of
 SELinux that one cannot explicitly remove and reassign contexts to
 ports.  In order to accomplish this on a system running httpd but
 attached to non-standard ports one perforce is required to cross link
 permissions between all of the affected processes.  Which I cannot
 conceive as a security enhancement.


 --
 ***  E-Mail is NOT a SECURE channel  ***
 James B. Byrnemailto:byrn...@harte-lyne.ca
 Harte  Lyne Limited  http://www.harte-lyne.ca
 9 Brockley Drive  vox: +1 905 561 1241
 Hamilton, Ontario fax: +1 905 561 0757
 Canada  L8E 3C3

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

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

Re: [CentOS] low latency kernel?

On 04/02/2015 10:46 AM, Les Mikesell wrote:

Someone recently posted on the x2go list that he had a problem with
jerky videos playing remotely on Ubuntu, but solved it by installing a
low latency kernel that was available as an alternative. That made me
curious as to whether CentOS has an equivalent - or a way to build
something similar.

You want the kernel-rt package. This is a part of the MRG packaging.
The source RPM for the latest version for EL6 is at
ftp://ftp.redhat.com/redhat/linux/enterprise/6Server/en/RHEMRG-RHEL6/SRPMS/kernel-rt-3.10.58-rt62.60.el6rt.src.rpm
(and while looking in this area, I found some very interesting things in
the 7 trees..). I don't see a kernel-rt package in any of the C7
repos, but sources are in the kernel-rt git at git.centos.org. Just
need to build it and its dependencies. Karanbir, Johnny, et al: are
there any plans to build this at some point?

And then you'll want to read
https://rt.wiki.kernel.org/index.php/RT_PREEMPT_HOWTO as the RT
preemptable kernel has some differences in behaviors you need to be
aware of.

I have used the RT_PREEMPT kernel, when dealing with multitrack audio
setups where you need to do overdubbing and punchins/outs. Every
millisecond counts when you have a musician or vocalist listening to a
mix of 16 tracks, their own previously recorded track, and they need to
punch in and perform (with pre-roll) a new take of a section then punch
out to return to the previously recorded material.

Currently I use AVLinux for that task, but CentOS 7 plus the RT kernel
(with all the tools needed for said kernel) would be fantastic; the
software I use, Harrison Consoles' Mixbus (based on Ardour), runs very
well on C7, but the latency is a bit too high (and far too
nondeterministic thanks to clock scaling) for 16 channel overdubs with
punchins/outs. AVLinux works well for this.

Years ago, the way to get this on Red Hat Linux and later Fedora and
CentOS was to install the kernel-rt from PlanetCCRMA; it's been a while
since I looked for it there. But Red Hat has the MRG product.

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

Re: [CentOS] OpenSSL vulnerability fix

2015-04-02 Thread Nataraj

On 03/30/2015 11:57 PM, Venkateswara Rao Dokku wrote:
 just for my curiosity, How can we make sure that its not affected?

 Is there any script to check whether its vulnerable or not (as in bash
 shell shock vulnerability test)?

You can run both client and server tests from:
https://www.ssllabs.com/

Nataraj


 On Tue, Mar 31, 2015 at 12:25 PM, Eero Volotinen eero.voloti...@iki.fi
 wrote:

 Centos 5 is not affected by this bug, so fix is not available.

 Eero
 31.3.2015 9.48 ap. kirjoitti Venkateswara Rao Dokku dvrao@gmail.com
 :
 Hi All,

 I wanted to fix the openssl vulnerabilities (CVE-2014-3569,
 CVE-2014-3570,
 CVE-2014-3571, CVE-2014-3572) in my CentOS 5.5 and found out that 0.9.8zd
 has the fixes I am looking for (from the
 https://www.openssl.org/news/vulnerabilities.html link).

 But, When I tried to find the openssl-0.9.8zd rpm package, I did not find
 it in http://mirror.centos.org/centos/5/updates/x86_64/RPMS/.

 The latest that I could find was 0.9.8e-31-el5.

 Can you please help me on how can I find the rpm I am looking for or How
 can I fix the vulnerabilities.?

 Thanks for your help.

 --
 Thanks  Regards,
 Venkateswara Rao Dokku.
 ___
 CentOS mailing list
 CentOS@centos.org
 http://lists.centos.org/mailman/listinfo/centos

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




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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

On 04/02/2015 04:43 PM, Phelps, Matthew wrote:
 On Thu, Apr 2, 2015 at 11:19 AM, Lamar Owen lo...@pari.edu wrote:
 
 On 04/02/2015 10:59 AM, Phelps, Matthew wrote:

 It's not just the name of the ISO file. c.f. the VERSION_ID variable in
 /etc/os-release

 In that particular place it is actually rather important, but that is
 orthogonal to the ISO name.


 I agree, but this thread started off with a more general discussion of
 release/version numbering.
 

os-release has been at /7/ since the first CentOS 7 release - what extra
value does having 7.1 in there bring ? At best it just says that your
centos-release rpm has not been updated and/or there is no system level
state change that required metadata in that file.

Note that any CentOS machine, updated to the same point in time,
regardless of where and how it was privisioned should give you the same
functional package set. This is an important thing.

-- 
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

On Thu, April 2, 2015 9:52 am, Always Learning wrote:

 On Wed, 2015-04-01 at 22:54 -0700, John R Pierce wrote:

 you guys sure get your panties in a bunch over something as silly as
the
 iso file name.

 You may wear them, many of us don't :-)

 if you don't like the name, rename it... sheesh.

 Its about a consistent and logical approach to identifying versions,
revisions and differences between changes.

 How is the latest numbering system an improvement ? Marks idea of

 {major version}-{sub version}-{mmdd} ..

 is clearly a good proposal


After all I decide to add rant tag at the very beginning of my message
instead of just assuming it. Bu before that:

Thanks a lot to CentOS team for the great job you guys are doing!

rant

My guess is the lack of understanding of (and sympathy to) your, Mr.
Always Learning, point stems from people missing the very basic thing.
I'll try to explain what I mean.

Us, human, usually do consecutive counting as follows:

A:

0 1 2 3 4 5 6 ...

Now, as portion of version identifier doesn't follow this way of counting
anymore, it is akin counting like:

B:

231 2735 2746 3458 5216 ...

This is still in ascending order, still:

1. whereas in case A given you have [sub]version number 4 you definitely
know that adjacent previous is 3 and adjacent following will be 5. Case B
is different: unless you have the whole row of legal numbers in front of
you, you will not be able to guess whether 2746 and 3458 are consecutive
versions, or there is one or more versions between them.

2. comparison of two version in case A easily reveals which is earlier and
which is higher, in case B it is not quite so (you can try to time
yourself on comparison of random natural number in 1 range and compare
that to the case of natural numbers 0-9, you will know what I mean), and
hence prone to higher chance of error (and don't second guess me: I always
has A+ in mathematics in school and university ;-). This is just a trivial
human psychology...

Valeri

PS I do realize that these big numbers are quite likely just a subset of
indeed consecutive natural numbers, say, counting builds, and only the
ones that are good enough to be released for public use are visible to
public. Still, developers usually have their magic way to keep track of
their consecutive builds and relation to still consecutively numbers
good build released to public. Abandoning that is not wise at the very
least. It converts product from being transparent to getting obscure for
everybody. Which only serves the goal of diverting people to much poorer
IMHO alternatives, MS Windows to name one (the only OS of many I know
whose vendor tells you it is unsafe to use it without 3rd party software -
antivirus).

/rant

You should guess all I say is ran, so I decided to drop resemblig tag at
the beginning ;-)



Valeri Galtsev
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
Phone: 773-702-4247





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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

On 04/01/2015 10:10 PM, Lamar Owen wrote:
 Yes, not very wise... Karanbir corrected very quickly the content of
 the redhat-release file, because it was totally different from 7.0,
 and broke a lot of scripts and applications.
 The issue of the content of redhat-release was a serious and valid one
 that actually broke stuff; the ISO name being different from expected
 doesn't break stuff. If the ISO name broke stuff, then that would be
 different, and it would have already been fixed.

This is the key bit here - were not trying to break anything - we are
trying to keep things sane for folks who are already invested in the
platform while also allowing other people to do interesting things.

You brought up the rolling builds, and yes - we've been doing it. Its
been immense value ( over 100K downloads for the 2015 Feb builds as a
point of reference ). for other process's like the Atomic builds,
needing the nightly, weekly builds has been key to their ability to get
the technology moving. There are a lot of such examples around, but I
will admit many of them are silo'd away slightly from this list - eg.
the docker traction we have does not typically feedback here to this
list and perhaps not into this audience. But should you want to move
into container space, CentOS today represents one of the best all around
experiences either on host or instance side.

The story is similar on the Cloud side of things, we have a ver large
cloud instance base - if i were to fancy a guess, I'd say 20% of the
centos install base is today in cloud ( and this is largely only
offprem, including onprem the numbers might go higher, but there is no
way to tell since they could just be real machine instances ).

Putting all that aside, the baseline assumption that we should all be
mindful of is that in real terms there is no CentOS point release : any
centos install, regardless of where it originated from, yum updated to
the same point in time will have the same package manifest, and should
deliver the same feature set ( with some exceptions, like environ
specific workloads might have local flavour - you wouldnt expect cups on
an GCE instance for example ).

So what the changesets have done ( and lets be fair, these changes like
the iso name changing to line up a date stream rather an an arbitary
point in time isnt a huge deal, you can just rename the file locally if
you so wish ), effectively line up and help deliver on that.

Let me highlight this with two examples:
- the Amazon instances we provide  have been updated out of band, to
cover for the security issues that have wider impact, heartbleed and
poodle and all that stuff : labelling those as 7.0 makes no sense since
it does not deliver on a 7.0 feature set, it delivers a CentOS-7/Dec
2014 update set.

- Second example is that when you look at a machine and it says 5.5 its
hard to explain to the user that his machine might be 5 years out of
date, there is a baseline cultural expectation that a release is either
maintained or not - and having the conversations around CentOS-5 being
maintained but not 5.5 isnt easy. Remember that this list represents the
folks who really know, and know well, both the ecosystem and platform as
well as their workloads and userbase - there are a lot ( a majority ? )
of CentOS user who dont get this. For them to line up with a
CentOS-7/2014-06 and CentOS-7/2015-03 immediately makes sense. it makes
it easier for us to communicate the delta in security and bugfix that
they dont have on there.

And I think the overall solution we have in place right now, really does
this well in that we clearly communicate the upstream relationship,
while still being able to deliver the common message on and around the
centos-release spec. If there are tangiable situations where this change
causes harm, then I am very willing to reach out and help find a
solution : dont want to break existing installs nor reduce the info
available.

The other thing here in this conversation is also that there is a large
emotional resistance to change. Folks expect the numbers to line up in a
specific manner, and they dont - the contents of the images however
still give you the metadata you need ( both ways, they should give you
point in time, and release from rhel that we derived/built from ).

Happy to pickup and work through individual concerns people might have
around this. But in real terms, please note that there is no change in
the content being delivered. We are only opening up options to line up
various media and point-in-time images.

-- 
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Kernel panic, CentOS 7.1503 fully updated, with executing gkrellm.


On 04/02/2015 07:29 AM, Marcelo Ricardo Leitner wrote:
If it's that easy to reproduce, please grab the panic message or 
generate a vmcore through crashdump and report it at 
bugzilla.redhat.com against kernel component.




Thanks for the pointer with some details.  I see that I have a bit to 
learn.  The first thing I need to do is reproduce it on other hardware.


I will say that I have experienced the same bug twice, but the first 
time I thought it was a botched yum update with CR enabled (and me 
having several packages installed from a mixed set of repos as well as 
some hand-built RPMs in there), and that was with / on ext4. This 
happened with / on xfs and an almost pristine install of the 20150228 
rolling ISO updated to 1503.  I use gkrellm as a quick visual dashboard 
of system load, and it is useful in that context. I also have it in my 
startup applications, so the kp happens immediately after logging in.  
(Both times with the same /home on ext4 over LUKS.)  The second time, 
nautilus would not start on a reboot/re-login due to corruption of one 
of its libraries (found in the 'tracker' package).  So I am a bit loath 
to hit this one again on my main machine, as I just don't have time this 
week for another reinstall.


You may be using an EPEL application but kernel shouldn't be panicking 
like that, specially if you're running it as an user.


Yeah, if gkrellm (run as a non-privileged user) can panic the kernel, a 
non-gui app hitting the same bits can too (unless it's related to the 
video card's driver).  Pairing a non-privileged userland kp witha a 
remote arbitrary code execution bug could be nasty.  That's why I still 
hope it's local to my machine.  But now to try to reproduce on other 
hardware.  (for reference, hardware on which I saw the bug is a Dell 
Precision M6500 with a Core i7-740QM and an AMD/ATI Firepro 7820M video, 
with / on a Samsung PM830 SSD)


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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64


On Thu, 2015-04-02 at 07:09 -0400, mark wrote:

 Had you, for example, made it release.subrelease.date (7.1.1503), it would 
 have been less disruptive and annoying.

An excellent suggestion that everyone can live-with.  Bravo.


-- 
Regards,

Paul.
England, EU.  Je suis Charlie.


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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64


On Wed, 2015-04-01 at 22:54 -0700, John R Pierce wrote:

 you guys sure get your panties in a bunch over something as silly as the 
 iso file name.

You may wear them, many of us don't :-)

 if you don't like the name, rename it... sheesh.

Its about a consistent and logical approach to identifying versions,
revisions and differences between changes.

How is the latest numbering system an improvement ? Marks idea of 

{major version}-{sub version}-{mmdd} ..

is clearly a good proposal

-- 
Regards,

Paul.
England, EU.  Je suis Charlie.


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

Re: [CentOS] SEmodule dependency hell.

2015-04-02 Thread James B. Byrne


On Wed, April 1, 2015 16:09, Andrew Holway wrote:
 I used the command: semanage port -m -t http_port_t -p tcp 8000
 to relabel a port. perhaps you could try:
 semanage port -m -t unconfined_t -p tcp 8000
 Failing that; would it work to run your application in the httpd_t
 domain?


I ended up having to create a custom policy to allow the other
application to have access to the http_port_t context.  Which is not
an issue given that no httpd service is, or will ever be, installed on
that host.

However, it seems a rather dangerous hole in the logical design of
SELinux that one cannot explicitly remove and reassign contexts to
ports.  In order to accomplish this on a system running httpd but
attached to non-standard ports one perforce is required to cross link
permissions between all of the affected processes.  Which I cannot
conceive as a security enhancement.


-- 
***  E-Mail is NOT a SECURE channel  ***
James B. Byrnemailto:byrn...@harte-lyne.ca
Harte  Lyne Limited  http://www.harte-lyne.ca
9 Brockley Drive  vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada  L8E 3C3

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

Re: [CentOS] Openssl C6 distro tag different from upstream

On 04/02/2015 11:45 AM, Leonard den Ottolander wrote:
 Hi,
 
 Just noticed that the distro tag used in openssl is different from
 upstream. Upstream and the last update (openssl-1.0.1e-30.el6_6.7) use
 el6_6 where as the latest update (openssl-1.0.1e-30.el6.8) uses
 el_6. Any reason for this discrepancy?

could you please file this as a bug report at bugs.centos.org


-- 
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] low latency kernel?

Someone recently posted on the x2go list that he had a problem with
jerky videos playing remotely on Ubuntu, but solved it by installing a
low latency kernel that was available as an alternative.  That made me
curious as to whether CentOS has an equivalent - or a way to build
something similar.

-- 
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

On Thu, Apr 2, 2015 at 11:14 AM, Karanbir Singh mail-li...@karan.org wrote:
  231 2735 2746 3458 5216 ...

 I believe your argument works fine since:
 CentOS-7-x86_64-DVD-1503.iso
 CentOS-7-x86_64-DVD-1507.iso
 CentOS-7-x86_64-DVD-1512.iso
 CentOS-7-x86_64-DVD-1606.iso

 note, this is YYmm to indicate age, and not serial numbers.

But none of us tells us at a glance how these relate to the 'when it
is ready' status of the CentOS port of RHEL 7.1.  Without additional
information I wouldn't know if any/all were done before/after.

And I'm curious as to why the reasoning is different for the iso names
and the directory in vault.centos.org.

-- 
   Les Mikesell
lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

2015-04-02 Thread Alain Péan


Le 02/04/2015 18:41, Johnny Hughes a écrit :

Notice that a new minor release includes new drivers for new servers, so
it is important to know if you can install at all the system on your
server, before any updates !

what does that have to do with an ISO name?


If you use the iso that does not include the correct drivers for your 
new server, it could be impossible to install the server. And with the 
confusing naming, it could be difficult to know if the iso you have at 
hand has indeed have the drivers you need...


Alain

--
Administrateur Système/Réseau
Laboratoire de Photonique et Nanostructures (LPN/CNRS - UPR20)
Centre de Recherche Alcatel Data IV - Marcoussis
route de Nozay - 91460 Marcoussis
Tel : 01-69-63-61-34

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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

2015-04-02 Thread Matthew Miller

On Thu, Apr 02, 2015 at 11:57:23AM -0500, Les Mikesell wrote:
  How, without a cross reference of some sort, do you know if a given
  CentOS iso will install on hardware where you know that the needed
  driver was added in an RH minor rev?
  always use the latest one.
 Which, combined with the possibility of releasing multiples per minor
 rev and no determinate time frame for the actual initial Centos minor
 release, really means nothing.

Well... 

Always use latest one *plus* look for the latest release
announcement. 

Like
http://lists.centos.org/pipermail/centos-announce/2015-March/021005.html

A cross-reference doesn't really seem necessary because usually
hardware enablement is additive. Either CentOS is up to the version you
need, or it isn't yet.


If you really _need_ a specific minor release and want to _stay_ on it,
to my knowledge, that's not something CentOS has _ever_ done anyway.
You can pay for Red Hat's EUS, or, I think Scientific Linux actually
does keep the .y releases separate (but I'm not sure of the details
as to how that's implemented).

-- 
Matthew Miller
mat...@fedoraproject.org
Fedora Project Leader
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

On 04/02/2015 05:08 PM, Valeri Galtsev wrote:
 Us, human, usually do consecutive counting as follows:
 
 A:
 
 0 1 2 3 4 5 6 ...
 
 Now, as portion of version identifier doesn't follow this way of counting
 anymore, it is akin counting like:
 
 B:
 
 231 2735 2746 3458 5216 ...

I believe your argument works fine since:
CentOS-7-x86_64-DVD-1503.iso
CentOS-7-x86_64-DVD-1507.iso
CentOS-7-x86_64-DVD-1512.iso
CentOS-7-x86_64-DVD-1606.iso

note, this is YYmm to indicate age, and not serial numbers.


-- 
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

2015-04-02 Thread Alain Péan


Le 02/04/2015 18:22, Les Mikesell a écrit :

Note that any CentOS machine, updated to the same point in time,
regardless of where and how it was privisioned should give you the same
functional package set. This is an important thing.

Yes, but how do you explain that relationship to someone who only has
a summary of the RH releases or where the Centos release stands
compared to it.  For example, what would you have said a few days ago?


Notice that a new minor release includes new drivers for new servers, so 
it is important to know if you can install at all the system on your 
server, before any updates !


Alain

--
Administrateur Système/Réseau
Laboratoire de Photonique et Nanostructures (LPN/CNRS - UPR20)
Centre de Recherche Alcatel Data IV - Marcoussis
route de Nozay - 91460 Marcoussis
Tel : 01-69-63-61-34

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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

On Thu, Apr 2, 2015 at 11:41 AM, Johnny Hughes joh...@centos.org wrote:
 On 04/02/2015 11:30 AM, Alain Péan wrote:

 Notice that a new minor release includes new drivers for new servers, so
 it is important to know if you can install at all the system on your
 server, before any updates !

 what does that have to do with an ISO name?

How, without a cross reference of some sort, do you know if a given
CentOS iso will install on hardware where you know that the needed
driver was added in an RH minor rev?

-- 
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

[CentOS] mounted NFS does not show in df -h

2015-04-02 Thread Tim Dunphy

Hey guys,

 This is kind of odd, so I wanted to do a sanity check.

 I mounted an NFS share like so:

[root@web1:~] #mount -t nfs nfs1.jokefire.com:/home /mnt/home

Seemed to go ok. Then I took a look at the output of df -h and didn't see
it!


[root@web1:~] #df -h
Filesystem  Size  Used Avail Use% Mounted on
/dev/vda 40G   24G   14G  64% /
devtmpfs996M 0  996M   0% /dev
tmpfs  1001M 0 1001M   0% /dev/shm
tmpfs  1001M  101M  901M  11% /run
tmpfs  1001M 0 1001M   0% /sys/fs/cgroup
s3fs256T 0  256T   0% /backup/cassandradb
s3fs256T 0  256T   0% /backup/mysql
nfs1.jokefire.com:/var/www   20G  3.1G   16G  17% /var/www


Yet, when I do a df -h on the directory I mounted the NFS share on, I see
that it's mounted via NFS as expected:

[root@web1:~] #df -h /mnt/home
Filesystem   Size  Used Avail Use% Mounted on
nfs1.jokefire.com:/home   20G  3.1G   16G  17% /mnt/home

So, what do you think could be happening? Why is it that I can't see the
output I'm expecting just by going df -h???

Thanks!!
Tim

-- 
GPG me!!

gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

On Thu, Apr 2, 2015 at 10:56 AM, Karanbir Singh mail-li...@karan.org wrote:

 os-release has been at /7/ since the first CentOS 7 release - what extra
 value does having 7.1 in there bring ? At best it just says that your
 centos-release rpm has not been updated and/or there is no system level
 state change that required metadata in that file.

If you know that some feature was added or bug fixed in RH 7.1,  or
more relevant, your boss or security officer or application developer
knows that, there is very much value in being able to say that  CentOS
7.1-whatever includes the same features/fixes, and that your automated
inventory database will show which machines have been updated to that
version.   Otherwise you'll spend the rest of the day discussing how
fix x is done in package-revs-n1 fix y is in package-rev-n2 and how to
check for it.   Sometimes you need the latter detail, but mostly not,
especially for the application guys.

 Note that any CentOS machine, updated to the same point in time,
 regardless of where and how it was privisioned should give you the same
 functional package set. This is an important thing.

Yes, but how do you explain that relationship to someone who only has
a summary of the RH releases or where the Centos release stands
compared to it.  For example, what would you have said a few days ago?

-- 
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

2015-04-02 Thread Johnny Hughes

On 04/02/2015 11:30 AM, Alain Péan wrote:
 Le 02/04/2015 18:22, Les Mikesell a écrit :
 Note that any CentOS machine, updated to the same point in time,
 regardless of where and how it was privisioned should give you the same
 functional package set. This is an important thing.
 Yes, but how do you explain that relationship to someone who only has
 a summary of the RH releases or where the Centos release stands
 compared to it.  For example, what would you have said a few days ago?
 
 Notice that a new minor release includes new drivers for new servers, so
 it is important to know if you can install at all the system on your
 server, before any updates !

what does that have to do with an ISO name?  Updates are not done via
ISO except for some very small number of off line servers.  Updates
usually happen from the tree.  And the default setup point to /7/ for
updates.  We have been going that for 10 years (pointing updates to /4/,
/5/, /6/, /7/, and not 6.1 or 6.2 or 6.3, etc.

Here is the default mirrorlist and baseurl info from CentOS-5:

===
mirrorlist=http://mirrorlist.centos.org/?release=$releaseverarch=$basearchrepo=os

#baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
===

It is the same for CentOS-5, CentOS-6, and CentOS-7 ... if someone has
something different, then they are making changes that they want to
make.  The name on the ISO has no impact on updates.





signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

2015-04-02 Thread John R Pierce


On 4/2/2015 9:49 AM, Les Mikesell wrote:

How, without a cross reference of some sort, do you know if a given
CentOS iso will install on hardware where you know that the needed
driver was added in an RH minor rev?


always use the latest one.



--
john r pierce, recycling bits in santa cruz

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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

On Thu, Apr 2, 2015 at 11:51 AM, John R Pierce pie...@hogranch.com wrote:
 On 4/2/2015 9:49 AM, Les Mikesell wrote:

 How, without a cross reference of some sort, do you know if a given
 CentOS iso will install on hardware where you know that the needed
 driver was added in an RH minor rev?


 always use the latest one.

Which, combined with the possibility of releasing multiples per minor
rev and no determinate time frame for the actual initial Centos minor
release, really means nothing.

-- 
  Les Mikesell
lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

2015-04-02 Thread Stephen Harris

On Thu, Apr 02, 2015 at 04:56:45PM +0100, Karanbir Singh wrote:
 os-release has been at /7/ since the first CentOS 7 release - what extra
 value does having 7.1 in there bring ? At best it just says that your

Compatibility with RedHat, that says 7.1 ?

-- 

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

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

2015-04-02 Thread Johnny Hughes

On 04/02/2015 12:14 PM, Matthew Miller wrote:
 On Thu, Apr 02, 2015 at 11:57:23AM -0500, Les Mikesell wrote:
 How, without a cross reference of some sort, do you know if a given
 CentOS iso will install on hardware where you know that the needed
 driver was added in an RH minor rev?
 always use the latest one.
 Which, combined with the possibility of releasing multiples per minor
 rev and no determinate time frame for the actual initial Centos minor
 release, really means nothing.
 
 Well... 
 
 Always use latest one *plus* look for the latest release
 announcement. 
 
 Like
 http://lists.centos.org/pipermail/centos-announce/2015-March/021005.html
 
 A cross-reference doesn't really seem necessary because usually
 hardware enablement is additive. Either CentOS is up to the version you
 need, or it isn't yet.
 
 
 If you really _need_ a specific minor release and want to _stay_ on it,
 to my knowledge, that's not something CentOS has _ever_ done anyway.
 You can pay for Red Hat's EUS, or, I think Scientific Linux actually
 does keep the .y releases separate (but I'm not sure of the details
 as to how that's implemented).
 

That last paragraph is EXACTLY the message we are trying to put out
here.  CentOS releases are NOT the same as EUS and have never been ..
yet that seems to be what people expect.  We want there to be no doubt
on this issue.



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

On Thu, Apr 2, 2015 at 1:08 PM, Johnny Hughes joh...@centos.org wrote:

 If you really _need_ a specific minor release and want to _stay_ on it,
 to my knowledge, that's not something CentOS has _ever_ done anyway.
 You can pay for Red Hat's EUS, or, I think Scientific Linux actually
 does keep the .y releases separate (but I'm not sure of the details
 as to how that's implemented).


 That last paragraph is EXACTLY the message we are trying to put out
 here.  CentOS releases are NOT the same as EUS and have never been ..
 yet that seems to be what people expect.  We want there to be no doubt
 on this issue.

But you are adding more confusion than you resolve if the designation
does not indicate that a specified version is 'at least' up to the
equivalent of some RH minor rev.  Even for the people who might have
incorrectly thought is was pinned there.   And now there yet another
arbitrary difference in what you need to know about one major number
vs. another for the long interval they will co-exist.

-- 
Les Mikesell
  lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64

On Thu, Apr 2, 2015 at 12:22 PM, Les Mikesell lesmikes...@gmail.com wrote:

 On Thu, Apr 2, 2015 at 10:56 AM, Karanbir Singh mail-li...@karan.org
 wrote:
 
  os-release has been at /7/ since the first CentOS 7 release - what extra
  value does having 7.1 in there bring ? At best it just says that your
  centos-release rpm has not been updated and/or there is no system level
  state change that required metadata in that file.

 If you know that some feature was added or bug fixed in RH 7.1,  or
 more relevant, your boss or security officer or application developer
 knows that, there is very much value in being able to say that  CentOS
 7.1-whatever includes the same features/fixes, and that your automated
 inventory database will show which machines have been updated to that
 version.   Otherwise you'll spend the rest of the day discussing how
 fix x is done in package-revs-n1 fix y is in package-rev-n2 and how to
 check for it.   Sometimes you need the latter detail, but mostly not,
 especially for the application guys.


This is the crux of the issue in my mind. The complete departure from the
upstream
naming conventions, weather they are correct or relevant or not, is a
major change
and is becoming a major hassle, maybe not from an engineering point of
view, but from
a practical, day-to-day one.

Change is fine, but it requires work to deal with. And most of us don't
have time to deal
with major changes. This is a major change from past practice for CentOS,
and there are
many operational implications of it that apparently haven't been
considered.


-- 
Matt Phelps
System Administrator, Computation Facility
Harvard - Smithsonian Center for Astrophysics
mphe...@cfa.harvard.edu, http://www.cfa.harvard.edu
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on x86_64