Linux RedHat 7.3 y disco SATA

[Carlos Manuel Duclos Vergara]

>Ya empezo el FUD. Me va a decir ahora que Sarge es 
>"inestable"... O que no tiene soporte de seguridad.... 
>Que pena, hablar con argumentos era mejor...

para los que siguen cantando la misma cancion:

Q: How is security handled in Debian?

A: Once the security team receives a notification of an incident, 
one or more members review it and consider its impact on the 
stable release of Debian (i.e. if it's vulnerable or not). If our 
system is vulnerable, we work on a fix for the problem. The 
package maintainer is contacted as well, if they didn't contact 
the security team already. Finally, the fix is tested and new 
packages are prepared, which are then compiled on all stable 
architectures and uploaded afterwards. After all of that is done, 
an advisory is published.

>PD : Sarge SI TIENE soporte del equipo de Seguridad de Debian. Y en 
>menos de un mes, sera estable. De hecho, Sarge/Testing es bastante 
>alejado de ser inestable.

para que vean la cantidad de cosas que dicen sin darse el trabajo de 
leer primero:

Q: How is security handled for testing and unstable?

A: The short answer is: it's not. Testing and unstable are rapidly moving 
targets and the security team does not have the resources needed to 
properly support those. If you want to have a secure (and stable) server 
you are strongly encouraged to stay with stable. However, the security 
secretaries will try to fix problems in testing and unstable after they are 
fixed in the stable release.

Q: How does testing get security updates?

A: Security updates will migrate into the testing distribution via unstable. 
They are usually uploaded with their priority set to high, which will reduce the 
quarantine time to two days. After this period, the packages will migrate into 
testing automatically, given that they are built for all architectures and their 
dependencies are fulfilled in testing.

Q: How is security handled for contrib and non-free?

A: The short answer is: it's not. Contrib and non-free aren't official parts of the 
Debian Distribution and are not released, and thus not supported by the 
security team. Some non-free packages are distributed without source or without 
a license allowing the distribution of modified versions. In those cases no security 
fixes can be made at all. If it is possible to fix the problem, and the package 
maintainer or someone else provides correct updated packages, then the security 
team will generally process them and release an advisory.

Ahora me van a salir no se con que cosa..... mejor le hago caso a mi jefe y me dejo
de buscar la forma de hacer entender a la gente lo que no quiere entender

Xhau
-- 
Carlos Manuel Duclos Vergara
http://www.elbazaar.cl