op 25-09-14 02:46, Tom Bishop schreef:
On Wed, Sep 24, 2014 at 7:41 PM, mark wrote:
I just updated firefox, here at home... and when I fired it back up, *all*
of my tabs were gone. Every one (all couple dozen...)
mark, CentOS 6.5
___
CentOS
op 25-09-14 09:01, Johan Vermeulen schreef:
op 25-09-14 02:46, Tom Bishop schreef:
On Wed, Sep 24, 2014 at 7:41 PM, mark wrote:
I just updated firefox, here at home... and when I fired it back up,
*all*
of my tabs were gone. Every one (all couple dozen...)
mark, CentOS 6.5
___
On 09/25/14 03:09, Johan Vermeulen wrote:
op 25-09-14 09:01, Johan Vermeulen schreef:
op 25-09-14 02:46, Tom Bishop schreef:
On Wed, Sep 24, 2014 at 7:41 PM, mark wrote:
I just updated firefox, here at home... and when I fired it back up, *all*
of my tabs were gone. Every one (all couple doze
op 25-09-14 13:46, mark schreef:
On 09/25/14 03:09, Johan Vermeulen wrote:
op 25-09-14 09:01, Johan Vermeulen schreef:
op 25-09-14 02:46, Tom Bishop schreef:
On Wed, Sep 24, 2014 at 7:41 PM, mark wrote:
I just updated firefox, here at home... and when I fired it back
up, *all*
of my tabs w
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 09/25/2014 01:07 AM, Michael Schumacher wrote:
> good morning,
>
You should 'yum update' as soon as possible to resolve this issue.
>
> I installed the update on C5 and C6 machines, but I do not see any
> difference in the output of "bash --version". Is that the expected
> behaviour?
>
>
From: Johan Vermeulen
> op 25-09-14 13:46, mark schreef:
>> Yup, forgot that: no tool bar at all, no menus
>>
>> mark
>
> Then maybe you are stuck in full-screen mode? Press f11 to exit that.
>
> grts, Johan
You can press the "Alt" key to show the menu.
JD
_
On Thu, September 25, 2014 8:59 am, John Doe wrote:
> From: Johan Vermeulen
>
>> op 25-09-14 13:46, mark schreef:
>>> Yup, forgot that: no tool bar at all, no menus
>>>
>>> mark
>>
>> Then maybe you are stuck in full-screen mode? Press f11 to exit that.
>>
>> grts, Johan
>
> You can pre
Valeri Galtsev wrote:
> On Thu, September 25, 2014 8:59 am, John Doe wrote:
>> From: Johan Vermeulen
>>> op 25-09-14 13:46, mark schreef:
Yup, forgot that: no tool bar at all, no menus
>>> Then maybe you are stuck in full-screen mode? Press f11 to exit that.
No. 99.44% of the time,
On Thu, Sep 25, 2014 at 09:09:15AM -0500, Valeri Galtsev wrote:
>
> developers to follow this:
>
> Don't change anything unless it is absolutely necessary.
>
> (it was excellent attitude to programming I was doing once: this way you
> diminish the chance to break something that works...)
Probab
On 9/25/2014 8:13 AM, m.r...@5-cent.us wrote:
Valeri Galtsev wrote:
On Thu, September 25, 2014 8:59 am, John Doe wrote:
From: Johan Vermeulen
op 25-09-14 13:46, mark schreef:
Yup, forgot that: no tool bar at all, no menus
Then maybe you are stuck in full-screen mode? Press f11 to exi
On Thu, September 25, 2014 9:13 am, m.r...@5-cent.us wrote:
> Valeri Galtsev wrote:
>> On Thu, September 25, 2014 8:59 am, John Doe wrote:
>>> From: Johan Vermeulen
op 25-09-14 13:46, mark schreef:
> Yup, forgot that: no tool bar at all, no menus
>
Then maybe you are stuck
Steve Lindemann wrote:
> On 9/25/2014 8:13 AM, m.r...@5-cent.us wrote:
>> Valeri Galtsev wrote:
>>> On Thu, September 25, 2014 8:59 am, John Doe wrote:
From: Johan Vermeulen
> op 25-09-14 13:46, mark schreef:
>> Yup, forgot that: no tool bar at all, no menus
>> It is *completel
If I understood correctly, the current fix is incomplete and another fix is
planned?
Also, in the advisory, RH says that after the update, servers need to be
rebooted... Really?
Aside from cgi/php, just closing all shells isn't enough?
Thx,
JD
___
C
On Thu, September 25, 2014 9:42 am, m.r...@5-cent.us wrote:
> Steve Lindemann wrote:
>> On 9/25/2014 8:13 AM, m.r...@5-cent.us wrote:
>>> Valeri Galtsev wrote:
On Thu, September 25, 2014 8:59 am, John Doe wrote:
> From: Johan Vermeulen
>> op 25-09-14 13:46, mark schreef:
>>> Yu
>>
>
> I'm in the same fix... But. When I will find open source, acceptable
> browser which I can predict will last and will have the same great
> attitude late netscape or mozilla had, I will start installing it
> simultaneously with firefox, yet will make it default browser, which users
> can swi
On 9/25/2014 8:42 AM, m.r...@5-cent.us wrote:
Steve Lindemann wrote:
On 9/25/2014 8:13 AM, m.r...@5-cent.us wrote:
Valeri Galtsev wrote:
On Thu, September 25, 2014 8:59 am, John Doe wrote:
From: Johan Vermeulen
op 25-09-14 13:46, mark schreef:
Yup, forgot that: no tool bar at all, no me
m.r...@5-cent.us wrote:
>palemoon looks nice
My concern with Pale Moon is that it's based on the Firefox 24 extended
support release, which is no longer supported. Don't know how that'll
play out.
In the meantime I've added exclude=firefox to my yum configuration and
am sticking with Firefox 24.
John Doe wrote:
If I understood correctly, the current fix is incomplete and another fix is
planned?
Yes. More info here - https://access.redhat.com/security/cve/CVE-2014-7169
Also, in the advisory, RH says that after the update, servers need to be
rebooted... Really?
No. From https://ac
On Thu, September 25, 2014 10:10 am, Ron Yorston wrote:
> m.r...@5-cent.us wrote:
>>palemoon looks nice
>
> My concern with Pale Moon is that it's based on the Firefox 24 extended
> support release,
Sad. If there is no own developers team behind that, it hardly will
survive "enterprise level" len
Tom Bishop wrote:
>>>
>> I'm in the same fix... But. When I will find open source, acceptable
>> browser which I can predict will last and will have the same great
>> attitude late netscape or mozilla had, I will start installing it
>> simultaneously with firefox, yet will make it default browser,
>
> Maybe we can get it into extras? I mentioned something from his repo to my
> manager, who understandably balked at a Russian server (this is a US gov't
> agency (non-DoD) that we work at
>
>mark
>
> ___
> CentOS mailing list
> CentOS@cento
On 09/25/2014 05:49 PM, m.r...@5-cent.us wrote:
Tom Bishop wrote:
I like the look of palemoon, I am going to drop an email to Nux and
see if we can get it added to his repo.
Maybe we can get it into extras? I mentioned something from his repo to my
manager, who understandably balked at a Rus
On 9/25/2014 9:07 AM, Steve Lindemann wrote:
On 9/25/2014 8:42 AM, m.r...@5-cent.us wrote:
Steve Lindemann wrote:
On 9/25/2014 8:13 AM, m.r...@5-cent.us wrote:
Valeri Galtsev wrote:
On Thu, September 25, 2014 8:59 am, John Doe wrote:
From: Johan Vermeulen
op 25-09-14 13:46, mark schreef:
On Thu, September 25, 2014 11:16 am, Nicolas Thierry-Mieg wrote:
>
>
> On 09/25/2014 05:49 PM, m.r...@5-cent.us wrote:
>> Tom Bishop wrote:
>>> I like the look of palemoon, I am going to drop an email to Nux and
>>> see if we can get it added to his repo.
>>
>> Maybe we can get it into extras? I m
On 09/25/2014 04:38 PM, Valeri Galtsev wrote:
Yes, I still didn't find replacement for firefox... so, anyone who has a
any suggestions of decent open source browser, please, let me know.
maybe try seamonkey, I've been using it for ages (basically since
firefox split from mozilla suite ;-) )
Nicolas Thierry-Mieg wrote:
> On 09/25/2014 05:49 PM, m.r...@5-cent.us wrote:
>> Tom Bishop wrote:
>>> I like the look of palemoon, I am going to drop an email to Nux and
>>> see if we can get it added to his repo.
>>
>> Maybe we can get it into extras? I mentioned something from his repo to
>> my
Maybe we can get it into extras? I mentioned something from his repo
to
my manager, who understandably balked at a Russian server (this is a
US
gov't agency (non-DoD) that we work at
li.nux.ro, that's Romania not Russia.
Thanks, I sit (and type) corrected. There was something nagging at
On 25/09/14 17:42, m.r...@5-cent.us wrote:
> Nicolas Thierry-Mieg wrote:
>> On 09/25/2014 05:49 PM, m.r...@5-cent.us wrote:
>>> Tom Bishop wrote:
I like the look of palemoon, I am going to drop an email to
Nux and see if we can get it added to his repo.
>>>
>>> Maybe we can get it into e
Jake Shipton wrote:
> On 25/09/14 17:42, m.r...@5-cent.us wrote:
>> Nicolas Thierry-Mieg wrote:
>>> On 09/25/2014 05:49 PM, m.r...@5-cent.us wrote:
Tom Bishop wrote:
> I like the look of palemoon, I am going to drop an email to
> Nux and see if we can get it added to his repo.
>>>
On Thu, Sep 25, 2014 at 12:18 PM, wrote:
>>>
>> Guess it's the old "if it ain't American, it ain't right" attitude? :-).
>
> Don't be absurd. How 'bout "can we be sure that no one's inserted nasties
> into the code?" How 'bout "who else has looked at and compared the code to
> the project source?
Sorry, missing footnotes to last email:
1] you'll notice I never mention the organization name - I really am not
allowed to speak for my organization, or my company.
2] Partly because I work for a federal contractor
mark
___
CentOS mailing lis
There is a README file on CentOS 7 in /etc/init.d
that says
Note that traditional init scripts continue to function on a systemd
system. An init script /etc/rc.d/init.d/foobar is implicitly mapped
into a service unit foobar.service during system initilization
So I dropped my file in the above dir
On 9/25/2014 11:39 AM, Jerry Geis wrote:
There is a README file on CentOS 7 in /etc/init.d
that says
Note that traditional init scripts continue to function on a systemd
system. An init script /etc/rc.d/init.d/foobar is implicitly mapped
into a service unit foobar.service during system initiliza
Well, I've set up one of our new JetStors. xfs took *seconds* to put a
filesystem on it.
We're talking what df -h shows as 66TB.
(Pardon me, my mind just SEGV'd on that statement)
Using bonnie++, I found that
a) GPT and partitioning gave was insignificantly different than
creating an
>is your init.d script chmod +x ?
>just putting something in init.d isn't sufficient, it has to be linked
>in rc?.d as a S##name ... which chkconfig on (or systemctl) are
>supposed to do
Yes the script is executable... forgot to mention that.
>From the comment in the README file, I thought th
On 9/25/2014 12:41 PM, m.r...@5-cent.us wrote:
I do have a question for the group mind, though: mounting these monstrous
partitions... should I, or, in fact, do I*need* to give, as a mount
option inode64? There will be a*lot* of files on this sucker What are
the pros and cons of that?
yes
Jerry Geis wrote:
>>is your init.d script chmod +x ?
>
>>just putting something in init.d isn't sufficient, it has to be linked
>>in rc?.d as a S##name ... which chkconfig on (or systemctl) are
>>supposed to do
>
> Yes the script is executable... forgot to mention that.
>
> From the comment in th
On 09/24/2014 12:11 PM, Johnny Hughes wrote:
On 09/24/2014 10:26 AM, Jim Perrin wrote:
You should 'yum update' as soon as possible to resolve this issue.
Here's why you should care:
https://securityblog.redhat.com/2014/09/24/bash-specially-crafted-environment-variables-code-injection-attack/
On 09/24/2014 12:11 PM, Johnny Hughes wrote:
On 09/24/2014 10:26 AM, Jim Perrin wrote:
You should 'yum update' as soon as possible to resolve this issue.
Here's why you should care:
https://securityblog.redhat.com/2014/09/24/bash-specially-crafted-environment-variables-code-injection-attack/
On Thu, 25 Sep 2014, John R Pierce wrote:
yes, you need inode64, as without it, it will be unable to create directories
after the first 2TB(?) fills up.
I have recently found that with XFS and inode64, certain applications
won't work properly when the file system is exported w/NFS4 to a 32-bi
In days of old, in Solaris there was a daemon for NFS Client, and NFS
server (actually several including portmap...).
I am unable to find reference to the daemon that runs NFS client
But the RedHat Documentation does not explain the NFS client daemon. Is
this a service or something else.
on
No it is not windows FS, this is a Hitachi Storage array managed by
RedHat storage nodes.
How do I clear client side NFS without a reboot
(sorry about the cross post)
For server side, it is simple service nfs restart.
But it looks like redhat/centos no longer has a nfs client service.
On 9/22
On 9/25/2014 2:01 PM, Steve Thompson wrote:
On Thu, 25 Sep 2014, John R Pierce wrote:
yes, you need inode64, as without it, it will be unable to create
directories after the first 2TB(?) fills up.
I have recently found that with XFS and inode64, certain applications
won't work properly when
Steve Thompson wrote:
> On Thu, 25 Sep 2014, John R Pierce wrote:
>
>> yes, you need inode64, as without it, it will be unable to create
directories
>> after the first 2TB(?) fills up.
>
> I have recently found that with XFS and inode64, certain applications
won't work properly when the file system
Try this:
http://www.databook.bz/?page_id=246
On 09/25/2014 05:13 PM, Dan Hyatt wrote:
In days of old, in Solaris there was a daemon for NFS Client, and NFS server
(actually several including portmap...).
I am unable to find reference to the daemon that runs NFS client
But the RedHat Docume
On Thu, 25 Sep 2014, John R Pierce wrote:
On 9/25/2014 2:01 PM, Steve Thompson wrote:
On Thu, 25 Sep 2014, John R Pierce wrote:
> yes, you need inode64, as without it, it will be unable to create
> directories after the first 2TB(?) fills up.
I have recently found that with XFS and inod
On 2014-09-25, Steve Thompson wrote:
> On Thu, 25 Sep 2014, John R Pierce wrote:
>
>> yes, you need inode64, as without it, it will be unable to create
>> directories
>> after the first 2TB(?) fills up.
Close, it's 1TB. But you won't be able to create *any* new inodes,
directories or files.
h
On 25/09/14 18:18, m.r...@5-cent.us wrote:
> Jake Shipton wrote:
>>
>> Guess it's the old "if it ain't American, it ain't right"
>> attitude? :-).
>
> Don't be absurd. How 'bout "can we be sure that no one's inserted
> nasties into the code?" How 'bout "who else has looked at and
> compared the c
On Thu, 2014-09-25 at 09:09 -0500, Valeri Galtsev wrote:
> Don't change anything unless it is absolutely necessary.
Extremely wise advice. Seems upstream do not always agree :-)
--
Regards,
Paul.
England, EU.
___
CentOS mailing list
CentOS@centos
On Thu, 2014-09-25 at 18:16 +0200, Nicolas Thierry-Mieg wrote:
>
> On 09/25/2014 05:49 PM, m.r...@5-cent.us wrote:
> >
> > Maybe we can get it into extras? I mentioned something from his repo to my
> > manager, who understandably balked at a Russian server (this is a US gov't
> > agency (non-DoD)
On Thu, September 25, 2014 7:32 pm, Always Learning wrote:
>
> On Thu, 2014-09-25 at 18:16 +0200, Nicolas Thierry-Mieg wrote:
>>
>> On 09/25/2014 05:49 PM, m.r...@5-cent.us wrote:
>> >
>> > Maybe we can get it into extras? I mentioned something from his repo
>> to my
>> > manager, who understandab
Take the case of an Apache Bash CGI. This will have been loaded when Apache
started, so Apache will have to be restarted to get the new one. There may
be other similar cases. So the best thing is to reboot.
Cheers,
Cliff
On Fri, Sep 26, 2014 at 2:39 AM, John Doe wrote:
> If I understood correc
I didn't notice you had mentioned CGI. CGI (and PHP) is only one case where
a copy of bash is loaded. There are many other possibilities, eg wrapper
bash scripts, bash shell called from programs. I don't know whether or not
there are any such cases on my machines, or if the exploit can be executed
On 2014-09-26, Cliff Pratt wrote:
> Take the case of an Apache Bash CGI. This will have been loaded when Apache
> started, so Apache will have to be restarted to get the new one.
Based on my (admittedly limited) testing I do not believe this is the
case. Apache exec()'s the interpreter on each r
On 25 Sep 2014 19:39, "Jerry Geis" wrote:
>
> I used to use rc.local and just need a script to run AFTER everything else
> has ran.
> no special start/stop/reload is needed... just a simple script.
>
1) you can still use /etc/rc.d/rc.local
2) read the systemd.service man page and do a little lear
On 26 Sep 2014 05:46, "Cliff Pratt" wrote:
>
> Take the case of an Apache Bash CGI. This will have been loaded when
Apache
> started, so Apache will have to be restarted to get the new one. There may
> be other similar cases. So the best thing is to reboot.
>
This is false and a major misundersta
On 26 September 2014 07:24, James Hogarth wrote:
>
> On 25 Sep 2014 19:39, "Jerry Geis" wrote:
> >
> > I used to use rc.local and just need a script to run AFTER everything
> else
> > has ran.
> > no special start/stop/reload is needed... just a simple script.
> >
>
> 1) you can still use /etc/r
58 matches
Mail list logo
