Re: [CentOS] Google Chrome and CentOS 6?

[Sorin Srbu]

> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of Richard
> Sent: den 25 januari 2016 16:19
> To: CentOS mailing list
> Subject: Re: [CentOS] Google Chrome and CentOS 6?
>
> 
> You're just seeing this now on a 6.7 system? I don't believe that
> google-chrome (as provided from the google repositories) has worked
> (been installable) on Centos-6.x machines for 2 years or more. [I
> just tried to install their current stable-48 on a 6.7 machine and
> got the libstdc++.so.6 dependency issue that broke this some time
> ago.]

Correct, on a CentOS 6.7 x64-system, it just started popping up about a week
ago.

The Richard Lloyd-solution (are you The Richard Lloyd providing the
install-script for Chrome?) has been working fine so far for me, flawlessly
even.
I'm just not quite sure what will happen in march, with the provided
solution from http://chrome.richardlloyd.org.uk/.


> With Centos-7 you'll see that warning banner if/when you update to
> 48. That release has been in beta since mid-december:
>  
> 
> and was just pushed out from their "stable" channel late last week.
> 
> My message in mid-december didn't elicit any real solution, but
> maybe that it's now hitting the stable release for Centos-7 there
> might be more interest.

I'd really like an official solution trickling down from RHEL.
The script works fine, but it's, well rather ghetto. 8-)

-- 
//Sorin
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Google Chrome and CentOS 6?

[Sorin Srbu]

> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of Leon Fauster
> Sent: den 25 januari 2016 17:03
> To: CentOS mailing list
> Subject: Re: [CentOS] Google Chrome and CentOS 6?
>
> 
> upstream provide a EL6 supplementary repository with chromium-browser.
> the emphasis lies on upstreams distribution. sources not available.

This wasn't by any chance those that gave an error of some kind?

I believe Richard Lloyd linked to the below (non)solution.
https://access.redhat.com/solutions/523213


-- 
//Sorin
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Just need to vent

[Micky]

Alice, your rant is just whining.
It's open source. If you don't like it, modify it.

You cannot compare something which you basically get for free to what is
funded by for-profit companies.

On Mon, Jan 25, 2016 at 2:32 PM, Alice Wonder  wrote:

> On 01/25/2016 01:28 AM, Kahlil Hodgson wrote:
>
>> I personally love Gnome3 on Fedora. It took me about a week to adjust my
>> mindset though -- I did that over a Xmas break.
>>
>> It did help that I read the release notes first (so I was not surprised at
>> the major change) and went through the tutorial the developers provided.
>>
>> An interesting exercise re-examining and critiquing old workflows and
>> exploring alternatives.  It works really well on the smallish laptop that
>> I
>> use while commuting and which I plug into a couple of monitors when I get
>> to work.  Its great the way it frees up screen real estate and encourages
>> me to focus on "what I am doing" rather than distracting me with "things I
>> might want to do".
>> ​
>> Reading the release notes before installing an OS is a really good idea.​
>> Fedora and RedHat do a really good job with their release notes.
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>>
>>
> Some people adapt to new workflows easily, others do not.
>
> But regardless of the workflow - back to my original point - it's pretty
> damn stupid that choosing a font for a text editor not only includes all
> fonts regardless of variable width or monospace, but doesn't identify which
> fonts in the selection are monospace.
>
> How can something like that be missed by their QA / UI testing?
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Just need to vent

[Chris Adams]

Once upon a time, Peter Duffy  said:
> The thing which always gets me about systemd is not the thing itself,
> but the way it was rolled out. When I first installed Red Hat 7, if a
> window had appeared telling me about systemd and asking me if I wanted
> to use it, or stick with the old init framework, I'd have opted for the
> latter (as I was interested primarily in continuity from the previous
> version.)

That's not really practical for something as core as the init system.
Trying to support two init systems in parallel, especially for as long
as Red Hat supports a RHEL release, would require a massive amount of
work.  A distribution is about making choices and implementing them in
the best way possible; for "leaf" packages like an editor or a web
browser, it is easy to have multiple options (where they don't
conflict), but core stuff like the kernel and init system don't leave
lots of room for choice.

I remember people complaining about SysV-style init too, "what's with
all these scripts" and "why can't I just add a line to /etc/rc".
systemd is a different way of thinking, but it isn't exactly original
(Sun and Mac have similar launchers); practical experience has shown
that this can be a better way of managing services.  daemontools has
been around forever, haphazardly implemented for some things; now that
behavior is where it makes the most since (PID 1 is guaranteed to get
the signal).  systemd makes implementing one-off services much easier,
makes local modifications of service startup better (include another
service and add the line you need), etc.

One note: when I talk about systemd, I mean systemd-the-init-service
that runs as PID 1.  I'm not a big fan of systemd-the-project, that
seems to have unlimited scope creep and reimplements every wheel in
sight (years of work on NetworkManager, decades of work on NTP? we can
do better!).

Nobody is forcing you to run systemd; you can continue to run CentOS 6
and earlier for years.  But if you are a system administrator, your job
is about learning and adapting, not trying to keep a static setup for
life.  systemd is different (just like SELinux was years ago), but I
suggest you learn it.  It can make your admin life easier.  Is it
perfect?  No, nothing ever is; I do think it is a big improvement
though.

-- 
Chris Adams 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS-announce] CESA-2016:0063 Important CentOS 7 ntp Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2016:0063 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0063.html

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

x86_64:
4b606ea94878f359cc016e2fb3545c87af50b77cab65c21ca7daa534c5a49252  
ntp-4.2.6p5-22.el7.centos.1.x86_64.rpm
4a320e7a12cf9b0e662e05a5371df9fe3b8fe3881f8b489ec02fc97769ac8628  
ntpdate-4.2.6p5-22.el7.centos.1.x86_64.rpm
37c9092a5fc997a11dd02bd4748024584c305f691437e4546418e453cec19c7e  
ntp-doc-4.2.6p5-22.el7.centos.1.noarch.rpm
b71ff70a1dfd7ed80ad43c76d651b821b5cdc3cd4360b87f244b4aff154d5387  
ntp-perl-4.2.6p5-22.el7.centos.1.noarch.rpm
71e36f16c2b105c208284bdfc4d08b1e93b0822fa7f08a569043c4cefdccf4f8  
sntp-4.2.6p5-22.el7.centos.1.x86_64.rpm

Source:
207b221dcadaa5ce149bd47258f23eafe973686dfe31030d689850dfe6b4d9ed  
ntp-4.2.6p5-22.el7.centos.1.src.rpm



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

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

Re: [CentOS] Just need to vent

[James B. Byrne]

On Sun, January 24, 2016 11:45, Peter Duffy wrote:

>
> Trouble is that when you go from 6 to 7, you also have the delights of
> systemd and grub 2 to contend with.
> . . .
> Similarly with others who have commented, I simply cannot
> understand why the maintainers of crucial components in
> linux have this thing about making vast changes which impact
> (usually adversely) on users and admins, without (apparently)
> any general discussion or review of the proposed changes.
> What happened to RFCs? Maybe it's a power thing - we
> can do it, so we're gonna do it, and if ya don't like it, tough!
>

Part of it is marketing.  Most of it is ego.

> It would be very interesting to know how many other users are
> still on CentOS/Red Hat 6 as a result of reluctance to enjoy
> all the - erm - improvements in 7. Maybe it's time to fork
> CentOS 6 and make it look and behave like 7 without systemd
> (or even better, with some way of selecting the init methodology
> at install-time and afterwards), and with gnome2 (or a clear
> choice between 2 and 3). Call it DeCentOS.
>


Depending on how the systemd drama plays out CentOS-6 may well be our
last RH derivative, and perhaps our last Linux.  At the moment we are
withholding any judgement on the matter for want of clear empirical
evidence respecting systemd's benefits and risks.

On our test CentOS-7 systems we eventually switched to Mate. That in
itself sorted out most of the most visceral negativity to RHEL7.  But
systemd, rightly or wrongly, remains a controversial issue here.  And,
being more interested in stability than features we will await further
developments on that front.

Maybe someone could convince Linus to embed an init processor into the
kernel in a manner similar to how KVM made its way.

-- 
***  e-Mail is NOT a SECURE channel  ***
Do NOT transmit sensitive data via e-Mail
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
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Google Chrome and CentOS 6?

[Richard]

> Date: Monday, January 25, 2016 07:18:06 +
> From: Sorin Srbu 
>
> Hi all,
> 
> Just recently I started getting the dreaded message about my
> CentOS 6.7  x64-installation wasn't going to be supported anymore
> by Google Chrome.
> 
> "This computer will soon stop receiving Google Chrome updates
> because this  Linux system will no longer be supported."
> 
> Doing some google searches I found this;
> http://superuser.com/questions/1011832/this-computer-will-soon-sto
> p-receiving-google-chrome-updates-because-this-linux
> 
> Which in itself wasn't too uplifting...
> Following the suggestion about installing Chromium instead worked,
> but it  seems to be stuck at an ancient version of the browser.
> 
> Recompiling the available Chromium source is of course an option,
> but not for  me.
> Not unless there are step-by-step guides doing it.
> 
> There was a rather long and somewhat heated discussion regarding
> Chrome on  CentOS a while ago.
> Was there any real conclusion about Google Chrome on CentOS and
> how to get  around this problem?
> Are the views on this matter still infected?
> 
> I'm not looking forward to go back to the sluggish Firefox. 8-/

You're just seeing this now on a 6.7 system? I don't believe that
google-chrome (as provided from the google repositories) has worked
(been installable) on Centos-6.x machines for 2 years or more. [I
just tried to install their current stable-48 on a 6.7 machine and
got the libstdc++.so.6 dependency issue that broke this some time
ago.]

With Centos-7 you'll see that warning banner if/when you update to
48. That release has been in beta since mid-december:
 

and was just pushed out from their "stable" channel late last week.

My message in mid-december didn't elicit any real solution, but
maybe that it's now hitting the stable release for Centos-7 there
might be more interest.


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

Re: [CentOS-es] DRP- Disaster Recovery Plan

[Gerardo Barajas]

Gracias a todos por sus respuestas.
En efecto Isidro: creo que mondo rescue se ve bastante simple y efectivo y
se acerca a lo que quiero.
Angel: pues puedo probar, ya que tengo 3 servers igualitos.

Ya les iré contando.

Gracias a todos.

*Gerardo Barajas Puente*


2016-01-23 20:02 GMT-06:00 angel jauregui :

> Sobre DELL esta utiliza una tarjeta PERC para hacer el RAID, ya que
> generalmente lo hace por hardware, desgraciadamente para que puedas acceder
> a tu RAID desde *otro DELL* deberias contar con la misma PERC, sino no
> podras leer los datos !
>
> Saludos !
>
> El 23 de enero de 2016, 20:01, angel jauregui 
> escribió:
>
> > Yo te recomendaria te hicieras de 3 HDDs:
> >
> > En el HDD1 haces una imagen con "dd" de el sistema (omite home).
> > El HDD2 y HDD3 ponlos como RAID1 y haz un script que cada hora haga un
> > "git add ." de los /home, despues un "git fetch" en el RAID1.
> >
> > Eso si, es importante mencionar que como tal no he visto una solucion que
> > incorpore todo, ya que hay empresas que tienen tanta informacion que
> seria
> > dificil tener replicando por completo la info, lo mejor es generar
> parches,
> > o vaya, a como lo hace git.
> >
> > Saludos !
> >
> > El 22 de enero de 2016, 13:53, Isidro-Gmail 
> > escribió:
> >
> >> Hola Gerardo
> >>
> >> Mira esta solución para ver si te sirve Mondo Rescue
> >> http://www.mondorescue.org
> >>
> >> Saludos
> >>
> >>
> >> Sent from my iPhone
> >>
> >> > On 22 Jan 2016, at 19:47, Gerardo Barajas 
> >> wrote:
> >> >
> >> > Que tal todos.
> >> > Tengo dos servidores con CentOS 6 instalado en un server DELL con
> >> arreglo
> >> > RAID, pero desconozco el tipo de arreglo.
> >> >
> >> > Actualmente estos dos servidores se encuentran replicándo su
> >> configuración
> >> > bajo el esquema de DRBD.
> >> >
> >> > Sin embargo, quisiera implementar un "algo" tipo Plan de Recuperación
> en
> >> > caso de Desastres, para reinstalar cualquier servidor de manera
> "rápida"
> >> > tal y como funciona hoy.
> >> >
> >> > ¿Serían tan amables de apuntarme hacia la dirección correcta para:
> >> >
> >> > a) Crear un CD o USB booteable para reinstalar alguno de los
> servidores
> >> > pero con lo que se tiene actualmente instalado
> >> > así como las configuraciones
> >> > b) Crear una imagen o espejo de la instalación actual y que se
> almacene
> >> en
> >> > algpun lugar fuera de los servidores, así como el proceso para la
> >> > instalación en caso de desastre
> >> > c) Alguna sugerencia?
> >> >
> >> > Muchas gracias y saludos a todos.
> >> >
> >> > *Gerardo Barajas Puente*
> >> > ___
> >> > CentOS-es mailing list
> >> > CentOS-es@centos.org
> >> > https://lists.centos.org/mailman/listinfo/centos-es
> >> ___
> >> CentOS-es mailing list
> >> CentOS-es@centos.org
> >> https://lists.centos.org/mailman/listinfo/centos-es
> >>
> >
> >
> >
> > --
> > M.S.I. Angel Haniel Cantu Jauregui.
> >
> > Celular: (011-52-1)-899-871-17-22
> > E-Mail: angel.ca...@sie-group.net
> > Web: http://www.sie-group.net/
> > Cd. Reynosa Tamaulipas.
> >
>
>
>
> --
> M.S.I. Angel Haniel Cantu Jauregui.
>
> Celular: (011-52-1)-899-871-17-22
> E-Mail: angel.ca...@sie-group.net
> Web: http://www.sie-group.net/
> Cd. Reynosa Tamaulipas.
> ___
> CentOS-es mailing list
> CentOS-es@centos.org
> https://lists.centos.org/mailman/listinfo/centos-es
>
___
CentOS-es mailing list
CentOS-es@centos.org
https://lists.centos.org/mailman/listinfo/centos-es

[CentOS-announce] CESA-2016:0063 Important CentOS 6 ntp Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2016:0063 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0063.html

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

i386:
b172e4c9936ba6db7e7df9a611f2ba305b0682bb0545c03ba23bc501ae7833f8  
ntp-4.2.6p5-5.el6.centos.4.i686.rpm
0cbe654866db67e07ba4dbea484f6eea8136a0a23e5123dfebf1ac097162dfb4  
ntpdate-4.2.6p5-5.el6.centos.4.i686.rpm
9a0cbc08c20ee5b43fd8518a2ccd0a13a274b0464a688fef4cc10b940c848993  
ntp-doc-4.2.6p5-5.el6.centos.4.noarch.rpm
4fdf6a42d2a1178394d328832e70284d631a0b14535af97ffa94d659b545d4b8  
ntp-perl-4.2.6p5-5.el6.centos.4.i686.rpm

x86_64:
c9bcbc789b84223a297f54197d407520f56d0d4d4775787dd0f746426d2e8866  
ntp-4.2.6p5-5.el6.centos.4.x86_64.rpm
07fcdccf4e98b884fc6e99bf568fb037547d7340083ba913d598d0b53cc162d7  
ntpdate-4.2.6p5-5.el6.centos.4.x86_64.rpm
9a0cbc08c20ee5b43fd8518a2ccd0a13a274b0464a688fef4cc10b940c848993  
ntp-doc-4.2.6p5-5.el6.centos.4.noarch.rpm
c2069c233875863df714450ba095380586746768fab379e7fe737c915e27721f  
ntp-perl-4.2.6p5-5.el6.centos.4.x86_64.rpm

Source:
7a3f04e3f4c7402309a5a7cbf9a7997778298cd1dbac24efd2ca98b9d75eacec  
ntp-4.2.6p5-5.el6.centos.4.src.rpm



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

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce

Re: [CentOS] Just need to vent

[Sylvain CANOINE]

> I believe that RHEL7 (and CentOS7) both have systemd integrated into them 
> enough
> that it isn’t as simple as “choose init system” on install.

That's because of systemd. Even if most of the linux distros don't, giving the 
choice is a bit less difficult with any other init system.

The main problem is systemd makes (often badly) more and more things that, as a 
"simple" init system, it should not do (login, and "su-ing" now, journaling, 
device management via udev, and so on), violating the KISS principle. If you 
use systemd, you have to use all the systemd tentacles, even if you don't want. 
Worse, more and more programs hardly depend on systemd now. Gnome 3 is an 
example, and that's why I don't, and won't, use Gnome 3.

I don't use any systemd-based distro personally. Sadly, professionally, I have 
to, since RedHat/CentOS and Debian adopted it (and Ubuntu LTS will do soon). 
And systemd makes my job uselessly more complicated. For exemple, why must I 
deal with journald and its fancies when I setup a syslog server (and I have to, 
because journald don't even know what are centralized logs...) on my servers ? 
Why systemd maintainers continuously change big parts of its behaviour, without 
any consideration of major-minor versionning, and why RedHat/CentOS maintainers 
dismiss this fact (the CentOS 7.1 to 7.2 update is painful, because systemd 
switched from 208 to 219) ? Why, more generally, the answer is often "systemd" 
when I encounter a problem on a server ?

Sylvain.
Pensez ENVIRONNEMENT : n'imprimer que si ncessaire

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

Re: [CentOS] Just need to vent

[Sylvain CANOINE]

> If that is the case, why do you run CentOS 7 on the server? You can stay
> with CentOS 6 for now and either wait till Linux systemd-free distribution
> mature enough to be run on server is available. Which it almost is: Devuan
> (systemd-free fork of Debian) has released "alpha" version about half a
> year ago. If you feel "married" to Linux, maybe it is a good idea to play
> with Devuan, provide them feedback thus helping them to become system-free
> Linux acceptable for servers. Simultaneously you can explore other options
> which would be to migrate away from Linux (Open Solaris, FreeBSD, NetBSD,
> OpenBSD will be much smaller step than stepping up to CentOS 7 - that is
> my experience, though FreeBSD migration of servers I started came much
> earlier than CentOS 7 and for different reason).
If I had the choice... The OS and the version are decreed by the contractor, 
I'm just a maintainer.

Sylvain.
Pensez ENVIRONNEMENT : n'imprimer que si ncessaire

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

Re: [CentOS] Just need to vent

[Matthew Miller]

On Mon, Jan 25, 2016 at 10:15:47AM -0800, Alice Wonder wrote:
> >>It's a fricken text editor, that should be the default - meaning you
> >>have to do something special to get fonts shown that aren't
> >>monospace.
> >The default _is_ monospace (specifically, the monospace system font).
> Yes and I needed a larger font size but only in gedit and the only
> way to change the font size is to select the font itself.

And, I can see that filtering the font selection would be a nice
filter, there. It seems like a reasonable request. But of all the
things to demand that someone be fired over

-- 
Matthew Miller

Fedora Project Leader
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Just need to vent

[Valeri Galtsev]

On Mon, January 25, 2016 7:59 am, Sylvain CANOINE wrote:
>
>> I believe that RHEL7 (and CentOS7) both have systemd integrated into
>> them enough
>> that it isn’t as simple as “choose init system” on install.
>
> That's because of systemd. Even if most of the linux distros don't, giving
> the choice is a bit less difficult with any other init system.
>
> The main problem is systemd makes (often badly) more and more things that,
> as a "simple" init system, it should not do (login, and "su-ing" now,
> journaling, device management via udev, and so on), violating the KISS
> principle. If you use systemd, you have to use all the systemd tentacles,
> even if you don't want. Worse, more and more programs hardly depend on
> systemd now. Gnome 3 is an example, and that's why I don't, and won't, use
> Gnome 3.
>
> I don't use any systemd-based distro personally. Sadly, professionally, I
> have to, since RedHat/CentOS and Debian adopted it (and Ubuntu LTS will do
> soon). And systemd makes my job uselessly more complicated. For exemple,
> why must I deal with journald and its fancies when I setup a syslog server
> (and I have to, because journald don't even know what are centralized
> logs...) on my servers ? Why systemd maintainers continuously change big
> parts of its behaviour, without any consideration of major-minor
> versionning, and why RedHat/CentOS maintainers dismiss this fact (the
> CentOS 7.1 to 7.2 update is painful, because systemd switched from 208 to
> 219) ? Why, more generally, the answer is often "systemd" when I encounter
> a problem on a server ?

If that is the case, why do you run CentOS 7 on the server? You can stay
with CentOS 6 for now and either wait till Linux systemd-free distribution
mature enough to be run on server is available. Which it almost is: Devuan
(systemd-free fork of Debian) has released "alpha" version about half a
year ago. If you feel "married" to Linux, maybe it is a good idea to play
with Devuan, provide them feedback thus helping them to become system-free
Linux acceptable for servers. Simultaneously you can explore other options
which would be to migrate away from Linux (Open Solaris, FreeBSD, NetBSD,
OpenBSD will be much smaller step than stepping up to CentOS 7 - that is
my experience, though FreeBSD migration of servers I started came much
earlier than CentOS 7 and for different reason).

Good Luck!

Valeri

>
> Sylvain.
> Pensez ENVIRONNEMENT : n'imprimer que si ncessaire
>

+++
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
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Just need to vent

[Robert Nichols]

On 01/24/2016 10:45 AM, Peter Duffy wrote:

It would be very interesting to know how many other users are still on
CentOS/Red Hat 6 as a result of reluctance to enjoy all the - erm -
improvements in 7.


That's were I am, CentOS 6.7 with a 3.18 LTS kernel from the Xen4CentOS
repo on machines with hardware too new for a 2.6 kernel. I plan to stay
there until CentOS 6 goes EOL (and if my past history is any guide,
probably quite a while beyond that -- I'd been running a patched-up
Fedora 12 until late 2014, 4 years past its EOL).

--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.

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

Re: [CentOS] Just need to vent

[Richard Mann]

> -Original Message-
> From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On
> Behalf Of Jonathan Billings
> Sent: Monday, January 25, 2016 11:47 AM
> To: centos@centos.org
> Subject: Re: [CentOS] Just need to vent
> 
> On Mon, Jan 25, 2016 at 03:56:21PM +, Always Learning wrote:
> > Of course Alice can. All of us can. Hopefully it is constructive
> > criticism.  Seeing good software being replaced by less good, less
> > useful and more awkward software usually provoke the software's users to
> > protest.
> 
> Complaining on the CentOS list is probably not that productive, though.
> 

+1.  To be constructive, the criticism would need to be done ELSEWHERE.  On 
this list, it is just whining.

> --
> Jonathan Billings 
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Just need to vent

[Always Learning]

On Mon, 2016-01-25 at 11:46 -0500, Jonathan Billings wrote:
> On Mon, Jan 25, 2016 at 03:56:21PM +, Always Learning wrote:
> > Of course Alice can. All of us can. Hopefully it is constructive
> > criticism.  Seeing good software being replaced by less good, less
> > useful and more awkward software usually provoke the software's users to
> > protest.
> 
> Complaining on the CentOS list is probably not that productive, though.

I concur :-)
-- 
Regards,

Paul.
England, EU.  England's place is in the European Union.

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

Re: [CentOS] Google Chrome and CentOS 6?

[Александр Кириллов]

Was there any real conclusion about Google Chrome on CentOS and how to 
get

around this problem?


http://chrome.richardlloyd.org.uk

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

Re: [CentOS] Google Chrome and CentOS 6?

[Leon Fauster]

Am 25.01.2016 um 16:19 schrieb Richard :
> 
> 
>> Date: Monday, January 25, 2016 07:18:06 +
>> From: Sorin Srbu 
>> 
>> Hi all,
>> 
>> Just recently I started getting the dreaded message about my
>> CentOS 6.7  x64-installation wasn't going to be supported anymore
>> by Google Chrome.
>> 
>> "This computer will soon stop receiving Google Chrome updates
>> because this  Linux system will no longer be supported."
>> 
>> Doing some google searches I found this;
>> http://superuser.com/questions/1011832/this-computer-will-soon-sto
>> p-receiving-google-chrome-updates-because-this-linux
>> 
>> Which in itself wasn't too uplifting...
>> Following the suggestion about installing Chromium instead worked,
>> but it  seems to be stuck at an ancient version of the browser.
>> 
>> Recompiling the available Chromium source is of course an option,
>> but not for  me.
>> Not unless there are step-by-step guides doing it.
>> 
>> There was a rather long and somewhat heated discussion regarding
>> Chrome on  CentOS a while ago.
>> Was there any real conclusion about Google Chrome on CentOS and
>> how to get  around this problem?
>> Are the views on this matter still infected?
>> 
>> I'm not looking forward to go back to the sluggish Firefox. 8-/
> 
> You're just seeing this now on a 6.7 system? I don't believe that
> google-chrome (as provided from the google repositories) has worked
> (been installable) on Centos-6.x machines for 2 years or more. [I
> just tried to install their current stable-48 on a 6.7 machine and
> got the libstdc++.so.6 dependency issue that broke this some time
> ago.]
> 
> With Centos-7 you'll see that warning banner if/when you update to
> 48. That release has been in beta since mid-december:
> 
> 
> and was just pushed out from their "stable" channel late last week.
> 
> My message in mid-december didn't elicit any real solution, but
> maybe that it's now hitting the stable release for Centos-7 there
> might be more interest.


upstream provide a EL6 supplementary repository with chromium-browser. 
the emphasis lies on upstreams distribution. sources not available. 

--
LF

 












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

Re: [CentOS] Just need to vent

[Matthew Miller]

On Sat, Jan 23, 2016 at 03:20:35PM -0800, Alice Wonder wrote:
> It's a fricken text editor, that should be the default - meaning you
> have to do something special to get fonts shown that aren't
> monospace.

The default _is_ monospace (specifically, the monospace system font).
You _are_ doing something special by changing the font - and gedit
happens to work just fine with proportional-spaced fonts, which someone
might even prefer for whatever they're doing.

Having another option to filter the font list might be a nice
enhancement, but I think it's pretty easy to see why it wasn't a
priority.

> Seriously, who is in charge with the UI design in gnome?
> Whoever it is needs to be fired.

This isn't the way GNOME works, or open source in general. Nor is this
an effective way to create change. I recommend, instead, filing an RFE
at  -- although
leaving the hyperbolic rhetoric and simply presenting the case is a lot
more likely to be effective. (Bonus effectiveness: provide a patch!)


-- 
Matthew Miller

Fedora Project Leader
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Just need to vent

[Always Learning]

On Mon, 2016-01-25 at 18:41 +0500, Micky wrote:

> Alice, your rant is just whining.

It is pertinent. It is lucidly expressed and many concur.

> It's open source. If you don't like it, modify it.

That can be an onerous burden especially when one lacks knowledge and
time.

> You cannot compare something which you basically get for free to what is
> funded by for-profit companies.

Of course Alice can. All of us can. Hopefully it is constructive
criticism.  Seeing good software being replaced by less good, less
useful and more awkward software usually provoke the software's users to
protest.

Free software should be funded. In the European Union (28 member states)
funding could easily be provided by the EU to support Open Source
Software. Just consider how much government cash M$ has received (USD
billions). A few million Euros to OSS is certainly desirable.

As a C5 Gnome 2 user I dread G3 when I move my desktop to C6. Mate seems
an alternative.  Anyone know more about the G2 folk ?



-- 
Regards,

Paul.
England, EU.  England's place is in the European Union.

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

Re: [CentOS] Just need to vent

[Jonathan Billings]

On Mon, Jan 25, 2016 at 03:56:21PM +, Always Learning wrote:
> Of course Alice can. All of us can. Hopefully it is constructive
> criticism.  Seeing good software being replaced by less good, less
> useful and more awkward software usually provoke the software's users to
> protest.

Complaining on the CentOS list is probably not that productive, though.

-- 
Jonathan Billings 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] What to do when you've been hacked?

[Valeri Galtsev]

On Mon, January 25, 2016 12:04 pm, Benjamin Smith wrote:
> No, we haven't been hacked. ;)
> We have a prospective client who is asking us what our policy is in the
> event
> of unauthorized access. Obviously you fix the system(s) that have been
> compromised, but what steps do you take to mitigate the effects of a
> breach?
> What is industry best practice? So far, searches haven't produced anything
> that looks consistent, except maybe identity monitoring for financial
> data.
> (EG: Target breach)
> We host a significant amount of educational data, but no financial
> information.
> How would we even respond to this question?
> I've also posted this question at
> https://www.reddit.com/r/linuxadmin/comments/42mi1r/what_to_do_when_youve_been_hacked/

Of course, mine will by no means be comprehensive or detailed. The order
may change when you start investigatinge it. But just in general:

1. It already happened, do not rush to do anything, change anything,
reboot, kill processes. If you can keep it for some time connected to the
network, you have chance to have more leak or deeper damage, but
simultaneously you may loose some of the tracks if you disconnect (thing
self sweeping up malicious things when network connection is lost). They
usually suggest yank from network, but it is your decision. Rebooting will
wipe content of /dev/shm and similar places used by bad guys to an
advantage of disappearing tracks

2. You should have backups, but you may need to make a copy of stuff that
might have changed after last backup

3. damage check

4. finding out level of compromise and the way compromise happened. Was it
root compromise and they got the whole system? Or some regular user
account was compromised (password or secret key was stolen). In last case:
were then attempts of elevation of privileges (they usually are)? Were
these attempts successful? (this is why you keep your system patched - it
is rare that there is hole on fully patched system known to bad guys, but
not software developers/system vendors). Was it through some service?

5. what have they done to come back or use your system otherwise? This
usually is parallel to investigating potential system level compromise.
Namely: scan open ports internally, and compare to scan from external box
(though some malicious may listen to their master box only, so this may
not necessarily reveal everything). Check if any of binaries or libraries
were modified (you should be prepared for that, look for integrity tools
like afick, eics, I used tripwire before it went commercial).

6. Preserve hacked system drive(s) (or their images) for further
forensics, which may take two weeks and longer... Build new system, patch,
enable the services you need and restore, make sure you don't open the
hole they came through. Restore files.

7. If it was system level compromise (root) sysadmin is obliged to contact
all users about it, stressing that their secret keys and passwords to
machines they were logging from compromised machine should be considered
compromised.

8. After you feel you recovered from compromise, and have freshly build
system with all necessary services running, do not drop forensics, it is
tedious but necessary thing.

Process accounting may be awfully helpful (you do have process accounting
enabled, right?)

SANS is one of great resources everybody will probably mention.

But the best is to avoid system level compromise, so: patch, patch,
patch... (or: update, update, update...).

As far as user level compromises are concerned: with 100+ users it is just
a question of time when someone's account will be compromised (often in a
system compromise elsewhere where user has an account). The best you can
do is to run your systems with an assumption that bad guys are already
inside. Make sure they can not do damage (even DOS, not to mention
elevation of privileges).


I hope, this helps.

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
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Just need to vent

[Warren Young]

On Jan 23, 2016, at 4:32 PM, Yamaban  wrote:
> 
> On Sun, 24 Jan 2016 00:20, Alice Wonder wrote:
> 
>> For example, when selecting a font for the gedit text editor - there is no 
>> way to ask it to only show monospace fonts.
> 
> IMHO the gnome UI devs played to much with MacOS X and Tablets.

I’d say they played too *little* with OS X.  That, or they tried to clone it 
without grokking it first.

The standard Mac OS X font picker *does* have a Fixed Width option.

The only GUI text editors on my Mac OS X box that don’t use this mechanism to 
select fonts are cross-platform apps that make you edit a JSON file to change 
fonts.  (Sublime Text and Visual Studio Code.)

And ironically, editing a config file to change fonts is more Unixy than Mac OS 
X.

> For me switching to XFCE as DE helped enormously in getting work
> done, not getting angry at the UI all the time was a nice plus.

CentOS has a GUI?  Since when?

My CentOS GUI is called SecureCRT. :)
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Just need to vent

[Warren Young]

On Jan 24, 2016, at 4:47 AM, John Hodrien  wrote:
> 
> You can start
> applications, move windows around, and manage files.  What do people really
> want from a DE?

Given a choice between Helix GNOME [*] and GNOME 3, I’ll certainly pick Gnome 3.

However, it is also a fact that GNOME has some longstanding design misfeatures 
that should have been fixed long ago.

Take GNOME Terminal.  (Please!)

Its biggest problem is its nonstandard settings mechanism, called Profiles.  
Every other standard GNOME app puts this under Edit > Preferences, but this one 
weird oddball app calls it Edit > Current Profile.  What are profiles, and why 
should I care about them?  Yes, I know they have a purpose, but forcing the 
user to operate through this abstraction layer amounts to exposed plumbing.

Compare Terminal on OS X, where essentially the same dialog is available from 
the standard Preferences menu.  OS X’s terminal program also has profiles, but 
it takes you right to the current default profile, rather than give you two 
different paths to the same configuration screen.

I wouldn’t even care about this if GNOME Terminal had better defaults.  Its 500 
line default scrollback limit is a joke in 2016.  OS X’s Terminal has a much 
smarter default: available memory.  You can limit it to a fixed number of 
lines, but you have to go out of your way to do that now.

I ask you, seriously now, when was the last time your system ran out of RAM due 
to GNOME Terminal?

> gedit broken for offering you fonts that aren't monospace?  I think that's a
> really weak criticism, considering it defaults to monospace.

The standard GNOME monospace font is not the only good monospace font in the 
world.

That said, I wonder if the complainers know how good they have it?  I wonder 
how they’d fare if sent back to the days of xfs, blocky fixed-size pixel fonts, 
and X font strings?

Buncha spoiled brats not appreciating their antialiased resizable 
sensibly-named fonts, installed by default and working out of the box. :)
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] What to do when you've been hacked?

[Warren Young]

On Jan 25, 2016, at 11:04 AM, Benjamin Smith  wrote:
> 
> We have a prospective client who is asking us what our policy is in the event 
> of unauthorized access.

Tell them you use the Mr. Miyagi defense: “Don’t get hit.”

Your prospective client sounds like they’re expecting someone to have 
established procedures to deal with breaches.  You know who has established 
procedures?  Organizations that see the same problems again and again.

Selecting an information service provider based on which one is best at 
recovering from a hack attack is like hiring a football coach based on how 
skilled he is at setting bones or selecting a cargo ship captain based on how 
good he is at patching hull breaches.

Why is “We’ve been at this for 20 years and have never *had* to clean up after 
a hacking incident” not an excellent rejoinder?

> what steps do you take to mitigate the effects of a breach? 
> What is industry best practice?

You should not have to ask this.  You should know it, because you are a 
professional and have been in this industry long enough.

Since you don’t, maybe you shouldn’t be bidding on this job.

I don’t mean to make this sound cabalistic, where only insiders know the secret 
handshakes, but rather exactly the opposite: this is information you should 
have been slowly absorbing for years:

 - SSH instead of telnet and FTP
 - HTTPS wherever possible over HTTP
 - Always enable SELinux
 - Prefer to surf default SELinux policies rather than override or custom-craft
 - Know in your heart that deny-by-default firewalls are a good thing
 - Turn off unnecessary services…
 - …then run “netstat -na | grep LISTEN” and justify each output line
 - Understand chown and chmod effects implicitly
 - Be able to read ls -l output at a blink

And much more.

All of this will be covered in any decent text on Unix/Linux security.  Sorry, 
I can’t give recommendations since I got past the book learnin’ stage long ago, 
and have been accreting such things ever since.

Coming back to martial arts, at some point you get past the point of conscious 
action and react implicitly.  The equivalent in security is recognizing risks 
and mitigating against them before they become NY Times headlines.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Just need to vent

[Liam O'Toole]

On 2016-01-25, Always Learning
 wrote:

[...]

> As a C5 Gnome 2 user I dread G3 when I move my desktop to C6. Mate seems
> an alternative.  Anyone know more about the G2 folk ?

C6 features G2. Nothing to dread.

-- 

Liam


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

[CentOS] What to do when you've been hacked?

[Benjamin Smith]

No, we haven't been hacked. ;) 
We have a prospective client who is asking us what our policy is in the event 
of unauthorized access. Obviously you fix the system(s) that have been 
compromised, but what steps do you take to mitigate the effects of a breach? 
What is industry best practice? So far, searches haven't produced anything 
that looks consistent, except maybe identity monitoring for financial data. 
(EG: Target breach) 
We host a significant amount of educational data, but no financial information. 
How would we even respond to this question? 
I've also posted this question at 
https://www.reddit.com/r/linuxadmin/comments/42mi1r/what_to_do_when_youve_been_hacked/
Thanks,
Ben 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Just need to vent

[Always Learning]

On Mon, 2016-01-25 at 17:28 +, Liam O'Toole wrote:

> C6 features G2. Nothing to dread.

Wonderful. Thanks :-)


-- 
Regards,

Paul.
England, EU.  England's place is in the European Union.

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

Re: [CentOS] Just need to vent

[Alice Wonder]

On 01/25/2016 09:07 AM, Matthew Miller wrote:

On Sat, Jan 23, 2016 at 03:20:35PM -0800, Alice Wonder wrote:

It's a fricken text editor, that should be the default - meaning you
have to do something special to get fonts shown that aren't
monospace.


The default _is_ monospace (specifically, the monospace system font).


Yes and I needed a larger font size but only in gedit and the only way 
to change the font size is to select the font itself.


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

Re: [CentOS] Just need to vent

[Kay Schenk]

On 01/24/2016 11:46 PM, Alice Wonder wrote:
> On 01/24/2016 11:31 PM, Sorin Srbu wrote:
>>> -Original Message-
>>> From: centos-boun...@centos.org
>>> [mailto:centos-boun...@centos.org] On
>>> Behalf Of John Hodrien
>>> Sent: den 24 januari 2016 12:47
>>> To: CentOS mailing list
>>> Cc: Mark LaPierre
>>> Subject: Re: [CentOS] Just need to vent
>>>
>>> My opinion is that there's a silent majority who don't hate
>>> Gnome3, and that
>>> it's not half as terrible as people seem to make out.  You can start
>>> applications, move windows around, and manage files.  What do
>>> people really
>>> want from a DE?  Being able to just type winkey-texmaker and have
>>> texmaker
>>> start up is suddenly a bad thing?
>>
>> Spot on.
>>
>> I don't hate Gnome3 enough to get irritated, not when it's as easy
>> as changing
>> the desktop environment.
>> This is what linux is about for me, if I don't like something -
>> I'm pretty
>> much free to search for other solutions and use those instead.
>>
>> I do understand Alice's rant though.
>> It mirrored my sentiments with CentOS 7 just when it came out. 8-)
> 
> I tried to like gnome3 but there were several things that I just
> could not accept.
> 
> Totem - which they insist on calling Movie Player now. I could not
> figure out how to get to not be full screen. I use it for playing
> audio clips I am working on, and don't want it full screen. In Gnome
> 2 it was easy.
> 
> Vertical Scroll Bar Sliders. They took away the scroll bars from my
> applications. No configuration option to turn it on, after searching
> and asking I found out the only way to turn them back on was with CSS.
> 
> But after doing that, it only came back for some applications.
> 
> On my desktop it isn't a big deal, I scroll with the scroll wheel.
> But on my laptops (Thinpad T Series) I don't have a scroll wheel, I
> like to grab the slider.
> 
> Those are the reasons I switched to Mate.
> 
> But even in Mate, applications like gedit pull in more Gnome 3 UI
> crap I don't like. Like no file menu on the left hand side of the
> window, instead horizontal bars all the way at the right hand hand
> side of the window - yet a save box all the way on the left hand.
> 
> And the Calculator app - Every damn time I grab the window to move
> it, the mode selector gets triggered because instead of being in a
> file menu like it use to be - it is now dead center in the top bar
> of the window, where I am use to grabbing windows to drag them.
> 
> Gnome3 UI is a disaster that needs to be fixed.
> 
> It's also rather annoying that I can no longer use my favorite
> spreadsheet, gnumeric, in CentOS because only old versions without
> bug fixes build. It use to be that current versions of gnome
> applications like gnumeric didn't require the most bleeding edge
> libraries to build them, but now they do.

I appreciate this "venting" thread. I am still on 6.7 with plans to
move to CentOS 7 in a few months.

I know CentOS 7 is systemd -- ok, maybe I can deal with that having
had some exposure to it, though I'm VERY fond of good ole system V
init scripts. And I actually had been looking forward to gnome3, but
now I'm not too sure about that. Well I could go back to KDE in any
case. But -- grub2 ?! Oh boy -- no joy from that in my previous
experience! :( I'm hoping I can stick with grub 1 some way if I DO
migrate to CentOS 7.

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

-- 

MzK

"Though no one can go back and make a brand new start,
 anyone can start from now and make a brand new ending."
-- Carl Bard
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Just need to vent

[Matthew Miller]

On Mon, Jan 25, 2016 at 03:26:51PM -0800, Kay Schenk wrote:
> I know CentOS 7 is systemd -- ok, maybe I can deal with that having
> had some exposure to it, though I'm VERY fond of good ole system V
> init scripts. And I actually had been looking forward to gnome3, but
> now I'm not too sure about that. Well I could go back to KDE in any
> case. But -- grub2 ?! Oh boy -- no joy from that in my previous
> experience! :( I'm hoping I can stick with grub 1 some way if I DO
> migrate to CentOS 7.

It's not like there's a lot of love for grub 2, but bootloaders are
really pretty hard, and no one is maintaining grub 1, and it doesn't
handle UEFI, so I'm not sure it's worth your trouble.

If you really want something lightweight (and don't need UEFI), you can
replace grub with extlinux/syslinux.

-- 
Matthew Miller

Fedora Project Leader
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] What to do when you've been hacked?

[Benjamin Smith]

On Monday, January 25, 2016 11:56:19 AM Warren Young wrote:
> On Jan 25, 2016, at 11:04 AM, Benjamin Smith  
wrote:
> > We have a prospective client who is asking us what our policy is in the
> > event of unauthorized access.
> 
> Tell them you use the Mr. Miyagi defense: “Don’t get hit.”
> 
> Your prospective client sounds like they’re expecting someone to have
> established procedures to deal with breaches.  You know who has established
> procedures?  Organizations that see the same problems again and again.
> 
> Selecting an information service provider based on which one is best at
> recovering from a hack attack is like hiring a football coach based on how
> skilled he is at setting bones or selecting a cargo ship captain based on
> how good he is at patching hull breaches.
> 
> Why is “We’ve been at this for 20 years and have never *had* to clean up
> after a hacking incident” not an excellent rejoinder?

Agreed! (although for us it has been 15 years.

> > what steps do you take to mitigate the effects of a breach?
> > What is industry best practice?
> 
> You should not have to ask this.  You should know it, because you are a
> professional and have been in this industry long enough.
> 
> Since you don’t, maybe you shouldn’t be bidding on this job.
> 
> I don’t mean to make this sound cabalistic, where only insiders know the
> secret handshakes, but rather exactly the opposite: this is information you
> should have been slowly absorbing for years:
> 
>  - SSH instead of telnet and FTP
>  - HTTPS wherever possible over HTTP
>  - Always enable SELinux
>  - Prefer to surf default SELinux policies rather than override or
> custom-craft - Know in your heart that deny-by-default firewalls are a good
> thing - Turn off unnecessary services…
>  - …then run “netstat -na | grep LISTEN” and justify each output line
>  - Understand chown and chmod effects implicitly
>  - Be able to read ls -l output at a blink
> 
> And much more.

Which I'd consider "best practices" and we do them. They are specifically 
asking about what to do *after* a breach. Despite all the best practices in 
place, there's *still* some risk. 
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] What to do when you've been hacked?

[Valeri Galtsev]

On Mon, January 25, 2016 6:12 pm, Benjamin Smith wrote:
> On Monday, January 25, 2016 11:56:19 AM Warren Young wrote:
>> On Jan 25, 2016, at 11:04 AM, Benjamin Smith 



>> And much more.
>
> Which I'd consider "best practices" and we do them. They are specifically
> asking about what to do *after* a breach.

Start looking for new job, maybe ;-)

Valeri

> Despite all the best practices
> in
> place, there's *still* some risk.




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
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Just need to vent

[Kahlil Hodgson]

I personally love Gnome3 on Fedora. It took me about a week to adjust my
mindset though -- I did that over a Xmas break.

It did help that I read the release notes first (so I was not surprised at
the major change) and went through the tutorial the developers provided.

An interesting exercise re-examining and critiquing old workflows and
exploring alternatives.  It works really well on the smallish laptop that I
use while commuting and which I plug into a couple of monitors when I get
to work.  Its great the way it frees up screen real estate and encourages
me to focus on "what I am doing" rather than distracting me with "things I
might want to do".
​
Reading the release notes before installing an OS is a really good idea.​
Fedora and RedHat do a really good job with their release notes.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Just need to vent

[Alice Wonder]

On 01/25/2016 01:28 AM, Kahlil Hodgson wrote:

I personally love Gnome3 on Fedora. It took me about a week to adjust my
mindset though -- I did that over a Xmas break.

It did help that I read the release notes first (so I was not surprised at
the major change) and went through the tutorial the developers provided.

An interesting exercise re-examining and critiquing old workflows and
exploring alternatives.  It works really well on the smallish laptop that I
use while commuting and which I plug into a couple of monitors when I get
to work.  Its great the way it frees up screen real estate and encourages
me to focus on "what I am doing" rather than distracting me with "things I
might want to do".
​
Reading the release notes before installing an OS is a really good idea.​
Fedora and RedHat do a really good job with their release notes.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos



Some people adapt to new workflows easily, others do not.

But regardless of the workflow - back to my original point - it's pretty 
damn stupid that choosing a font for a text editor not only includes all 
fonts regardless of variable width or monospace, but doesn't identify 
which fonts in the selection are monospace.


How can something like that be missed by their QA / UI testing?
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Just need to vent

[Scott Robbins]

On Sun, Jan 24, 2016 at 11:55:54PM -0800, Alice Wonder wrote:
> 
> Oh and as far as a silent majority that prefers Gnome 3 -
> 
> Ubuntu was by far the most common distribution for desktop users.
> 
> It is quickly being overtaken by Mint - with the Cinnamon and Mate
> builds, not the Gnome 3 build.

Ubuntu switched to their Unity interface, which seemed to aggravate a lot
of people. To me, who uses neither, it seemed rather similar to Gnome 3. 

I think a large part of Mint's popularity was less because of the desktop
and more because it included a bunch of proprietary drivers and codecs out
of the box (although these days, it won't play libx265 encoded video
without adding a ppa.

I prefer different desktops, so never got involved in the argument--it does
seem, judging from Fedora forums that avoiding Gnome (and this goes back to
the days when it was Gnome 2) saved me from a great many problems I saw and
see on their forums.

-- 
Scott Robbins
PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver pgp.mit.edu --recv-keys EB3467D6

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

[CentOS-announce] CESA-2016:0064 Important CentOS 7 kernel Security Update

[Johnny Hughes]

CentOS Errata and Security Advisory 2016:0064 Important

Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0064.html

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

x86_64:
29350967bf2d01358deaf9a99e1520eeb0af7bedae1d1cde8fdc73bf80731d4c  
kernel-3.10.0-327.4.5.el7.x86_64.rpm
674d565da50e81500b2b7fc49fc5a8005e2819b07acbd1d405078e7bc605036a  
kernel-abi-whitelists-3.10.0-327.4.5.el7.noarch.rpm
3c412b021fdab6881f46d0d7a09e9a2f2e3ffb33a93fb4f365f508e8e35b5b2d  
kernel-debug-3.10.0-327.4.5.el7.x86_64.rpm
21b228926c50ffcf49e55ed47bab7012d7cb55b495e84934138089cc1595933b  
kernel-debug-devel-3.10.0-327.4.5.el7.x86_64.rpm
0e2b4c67a11169566fa3d14818dbfa96454a1ddf204d574e102d4f340cbb415c  
kernel-devel-3.10.0-327.4.5.el7.x86_64.rpm
1d345ee1527bdbf3aacbf97b39ce22fba2c9ba0c76e511970090b7a52c45b246  
kernel-doc-3.10.0-327.4.5.el7.noarch.rpm
ad1cdc0d750914db690dfd58b0b58a16b09d0cadbd68281c26bbf4a31ef06f85  
kernel-headers-3.10.0-327.4.5.el7.x86_64.rpm
128d4dec4b6fd338ad2974140d4ac1e79737539324669c2d9135dd338817a653  
kernel-tools-3.10.0-327.4.5.el7.x86_64.rpm
6210ac1a8f1f0d783b8ea0ce617475eb124ce1163f51d5aba6988be8319e4bd7  
kernel-tools-libs-3.10.0-327.4.5.el7.x86_64.rpm
d826d7458ffed75e9fcb1b3ec86977c1593044a9b54336819d5caf507be8f8e1  
kernel-tools-libs-devel-3.10.0-327.4.5.el7.x86_64.rpm
8fa80deb6de526b395a35c4d49e2c9ac669397a954452bf454f87a0b182ba20d  
perf-3.10.0-327.4.5.el7.x86_64.rpm
4d65609eec974b3172035c5a0eacf470c565145cda94d6c6d4399766714d9ea6  
python-perf-3.10.0-327.4.5.el7.x86_64.rpm

Source:
ad702b51357600291eededf7c8d8b83bbfca93c106fcb0515aa3040110a4199c  
kernel-3.10.0-327.4.5.el7.src.rpm



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

___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce