diff options
Diffstat (limited to 'zarb-ml/mageia-discuss/attachments/20120822/a40b6716/attachment.html')
| -rw-r--r-- | zarb-ml/mageia-discuss/attachments/20120822/a40b6716/attachment.html | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/zarb-ml/mageia-discuss/attachments/20120822/a40b6716/attachment.html b/zarb-ml/mageia-discuss/attachments/20120822/a40b6716/attachment.html new file mode 100644 index 000000000..82b192e8c --- /dev/null +++ b/zarb-ml/mageia-discuss/attachments/20120822/a40b6716/attachment.html @@ -0,0 +1 @@ +<div><div>Just for the records,</div><div><br/></div><div>Im using mga2 in servers</div><div><br/></div><div><font style="color:#333333">Enviado desde mi DROID 4G LTE de Verizon Wireless</font></div></div><br><br>Anne Wilson <annew@kde.org> escribió:<br><br>-----BEGIN PGP SIGNED MESSAGE-----<br>Hash: SHA1<br><br>On 22/08/12 17:40, P. Christeas wrote:<br>> On Wednesday 22 August 2012, Anne Wilson wrote:<br>>> My recent experiences with enterprise distros has been less than <br>>> happy and I'm seriously wondering whether I could use Mageia on<br>>> the server as well as on workstations. ... Has anyone any<br>>> relevant experience?<br>>> <br>> <br>> Been using Mandrake, Mandriva and Mageia for servers, approx.<br>> since 2001. So far, had no reason to move to any other distro<br>> (except for prejudiced admins against a "desktop" / RPM distros).<br>> <br>> On a recent incident, I had to move some service from a RHEL6<br>> server to a humble Mga1 box, in order to gain in performance (rh<br>> did use older, less efficient versions). In a similar tone, vanilla<br>> Debian couldn't install there (because of the firmware for its<br>> NIC).<br>> <br>Thanks, everyone. Most reassuring. The main objection against using<br>a desktop rather than an enterprise distro is that users see the<br>desktop one as more likely to get "broken". My experience has been<br>the opposite. The enterprise distros spread packages over a number of<br>repos, which clash with each other, so that sooner or later an update<br>breaks things catastrophically. I learned through bitter experience,<br>and next time took great care to google for what looked like an<br>authoritative instruction on how to "prioritize" the repos - and my<br>system is once again broken beyond repair, or at least, I'm told that<br>repairing will be so long and painful it's not worth trying.<br><br>I don't aim to get bitten a third time.<br><br>Anne<br>- -- <br>Need KDE help? Try<br>http://userbase.kde.org or<br>http://forum.kde.org<br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v1.4.12 (GNU/Linux)<br>Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/<br><br>iEYEARECAAYFAlA1DrUACgkQj93fyh4cnBdsSACcD5lPpICwIfclk5agp6RPpEIS<br>mRQAn3IbIcgQUJpgVWvPX/14HCANdbjr<br>=NKkn<br>-----END PGP SIGNATURE-----<br>Email Shield provided by NOCWorldWide.com<br>
\ No newline at end of file |