I can't duplicate this, but I'm also on 4.0.0-0.rc6.el7.elrepo.x86_64 which may
make a difference.
Will try it on the stock kernel, too when I reboot next time.
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "Lamar Owen"
> To
Le 01/04/2015 20:23, Stephen Harris a écrit :
On a fully patched C7 machine...
% cat /etc/redhat-release
CentOS Linux release 7.1.1503 (Core)
% cat /etc/os-release
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="Cen
Hello All,
I have this Centos7 machine that"s 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,
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
- Oorspronkelijk bericht -
Van: "johan vermeulen7"
Aan: "CentOS mailing list"
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 that"s dualbooted with Win7.
It's
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/
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
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
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..
On Thu, Apr 2, 2015 at 12:54 AM, John R Pierce 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
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 V
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 t
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
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
le
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.
_
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.
--
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 identif
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 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
File a bug!!!
On 2 April 2015 at 16:20, James B. Byrne 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 tha
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 equival
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
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.ssllab
On Thu, Apr 2, 2015 at 11:19 AM, Lamar Owen 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 na
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 val
On 04/02/2015 04:43 PM, Phelps, Matthew wrote:
> On Thu, Apr 2, 2015 at 11:19 AM, Lamar Owen 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
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...
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
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 belie
On Thu, Apr 2, 2015 at 10:56 AM, 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
> centos-release rpm has not been updated and/or there is no system level
> state change that
On Thu, Apr 2, 2015 at 11:14 AM, Karanbir Singh 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,
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
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,
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
On Thu, Apr 2, 2015 at 11:41 AM, Johnny Hughes 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 tha
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
On Thu, Apr 2, 2015 at 11:51 AM, John R Pierce 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
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 w
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
_
On Thu, Apr 2, 2015 at 12:22 PM, Les Mikesell wrote:
> On Thu, Apr 2, 2015 at 10:56 AM, 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
> > centos-release rpm has no
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?
>>
On Thu, Apr 2, 2015 at 2:08 PM, Johnny Hughes wrote:
> 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 kn
On Thu, Apr 2, 2015 at 1:08 PM, Johnny Hughes 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"
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 usin
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.
__
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
twi
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.melvilletheatr
On Thu, Apr 2, 2015 at 3:25 PM, 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/01
Les Mikesell wrote:
> On Thu, Apr 2, 2015 at 1:08 PM, Johnny Hughes 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 actu
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
Cento
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
On 04/02/2015 02:29 PM, Phelps, Matthew wrote:
On Thu, Apr 2, 2015 at 3:25 PM, 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/pipermai
On Thu, Apr 2, 2015 at 2:25 PM, 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/012
On Thu, Apr 2, 2015 at 3:47 PM, Jim Perrin wrote:
>
>
> On 04/02/2015 02:29 PM, Phelps, Matthew wrote:
>
>> On Thu, Apr 2, 2015 at 3:25 PM, Jim Perrin wrote:
>>
>>
>>>
>>> On 04/02/2015 01:28 PM, Phelps, Matthew wrote:
>>>
>>>
>>> Soliciting our feedback *before* changing everything regarding r
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 th
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-Febru
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 PM
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 m
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
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
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
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
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
Firep
On Thu, Apr 2, 2015 at 4:12 PM, 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? It is unwelcome
> by you and a few others I've seen comment; w
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 "
It turned out that only one X9SBAA box was affected.
Deleting and reinstalling the kernel did not fix
On Thu, Apr 2, 2015 at 3:23 PM, Steve Thompson 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-rele
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 commerc
-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:
#
On Thu, 02 Apr 2015 20:55:46 +0100
Always Learning 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!
A
-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)
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 lik
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 wrote:
>>
>>>
>>>
>>> On 04/02/2015 01:28 PM, Phelps, Matthew wrote:
>>>
>>>
Soliciting our feedback *before* changing everything regarding release
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 private
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
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 f
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
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?
__
http://www.bitdefender.com/solutions/free.html
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "J Martin Rushton"
> To: centos@centos.org
> Sent: Thursday, 2 April, 2015 22:11:40
> Subject: [CentOS] OT: Recommended anti-virus for Windo
Well them plus CIA, NSA, Barney the Dinosaur and Teletubbies.
Brian Bernard
On Apr 2, 2015 5:58 PM, "Александр Кириллов" 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 retireme
-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-foun
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-r
> 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
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 t
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
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, "Александр Кириллов" wrote:
One thing I forgot to mention: I also always recommend AGAINST using
kasperski. Kasperski is KGB guy (*cough* *cough* reti
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 i
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
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 K
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"
> To: centos@centos.org
> Sent: Thursday, 2 April, 2015 21:44:59
> Subject: [CentOS] Boot Failure [Solved]
> I writ:
> "The latest ker
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
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
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-22
> On Mar 31, 2015, at 2:06 PM, Les Mikesell 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 's?
Prefix every line in the list with a like:
thing1
thing2
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
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?
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 d
Hello all,
Any Vietnamese are on this list?
How about creating a dedicated mailing list, for Vietnamese, in
Vietnamese[1] for the community?
Looking the the list of existing mailing list, I see that there are some
language-specific communities already there[2]
Ref.
[1] http://lists.cent
> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of Karanbir Singh
> Sent: 03 April 2015 01:00
> To: centos@centos.org
> Subject: Re: [CentOS] [CentOS-announce] Release for CentOS Linux 7 (1503 ) on
> x86_64
>
> On 02/04/15 21:35, Phelps
Hi,
On Thu, Apr 2, 2015 at 1:40 AM, Dave Stevens wrote:
> I have a degraded raid array (originally raid-10, now only two drives)
> that contains an LVM volume. I can see in the appended text that the Xen
> domains are there but I don't see how to mount them. No doubt this is just
> ignorance on
98 matches
Mail list logo
