public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Franklin Wang <touch21st@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fwd: How about the gentoo server or cluster in production environment?
Date: Thu, 20 Feb 2014 09:17:00 +0800	[thread overview]
Message-ID: <5305578C.9060903@gmail.com> (raw)
In-Reply-To: <CABxff59aw8X3vNCWJdGHcfTMc-azy9BRfZH0XOutU5V3p301rw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2965 bytes --]

Debian's powerful and stable, and I like apt very much. Gentoo and arch
can be used for soho. Google uses red hat in datacenter with a
customized kernel, and facebook started the project of open compute. are
several RISC processors going to die?

On 2014年02月20日 08:53, Facundo Curti wrote:
> I think a "more stable" distro is better for production. My choice is
> debian. I think you cant find nothing more stable that debian...
>
> >Gentoo makes the best server os because it's a custom built os where
> the admin knows each and every aspect of the os.
>
> This is true, but gentoo is a little unstable to use on production.
> The system must be on 365 days/year. ¿and when you need to update the
> system? This will use all the processor and the system will be
> overloaded. This means users can't use the system when this is updating...
>
> I think the best for a server is debian. I didn't try red hat but I
> see this like a commercial distro :/ Any way, red hat is very used as
> server. And if you choice to pay, you will have official support
> (Other wise, you are alone :/)
>
> P.D: I'm sorry if my english is not perfect, i speak spanish
>
>
> 2014-02-19 21:36 GMT-03:00 Franklin Wang <touch21st@gmail.com
> <mailto:touch21st@gmail.com>>:
>
>     Maybe it's intresting, although I prefer to use red hat, suse or
>     ubuntu in datacenter as Google. Slackware servers're not very
>     poppular here
>
>     On 2014年02月20日 08:14, Nilesh Govindrajan wrote:
>>
>>     On 20 Feb 2014 05:12, "Franklin Wang" <touch21st@gmail.com
>>     <mailto:touch21st@gmail.com>> wrote:
>>     >
>>     > and what about slackware for server?
>>     >
>>     >
>>     > -------- Original Message --------
>>     > Subject:
>>     > How about the gentoo server or cluster in production environment?
>>     > Date:
>>     > Fri, 29 Nov 2013 09:41:28 +0800
>>     > From:
>>     > Franklin Wang <touch21st@gmail.com <mailto:touch21st@gmail.com>>
>>     > To:
>>     > gentoo-server@lists.gentoo.org
>>     <mailto:gentoo-server@lists.gentoo.org>,
>>     gentoo-cluster@lists.gentoo.org
>>     <mailto:gentoo-cluster@lists.gentoo.org>
>>     >
>>     >
>>     > Hi all,
>>     >
>>     > I'm not familiar with gentoo server and cluster. So could you
>>     tell me
>>     > the experience about them? Thanks.
>>     >
>>     >
>>     >
>>     >
>>     > Franklin Wang
>>     >
>>     >
>>     >
>>
>>     Gentoo makes the best server os because it's a custom built os
>>     where the admin knows each and every aspect of the os. Security
>>     wise, there are no unwanted or unused stuff, so lesser bugs to
>>     deal with.
>>
>>     Clustering, well, you can do that using glusterfs
>>
>
>     -- 
>     skype:touch21st, Gtalk:touch21st, Yahoo/MSN:franklinwang36@yahoo.com <mailto:Yahoo/MSN:franklinwang36@yahoo.com>,
>     Xing/Linkedin:Franklin Wang
>
>

-- 
skype:touch21st, Gtalk:touch21st, Yahoo/MSN:franklinwang36@yahoo.com,
Xing/Linkedin:Franklin Wang


[-- Attachment #2.1: Type: text/html, Size: 6076 bytes --]

[-- Attachment #2.2: Type: image/gif, Size: 912 bytes --]

  parent reply	other threads:[~2014-02-20  1:17 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5297F0C8.3060403@gmail.com>
2014-02-19 23:40 ` [gentoo-user] Fwd: How about the gentoo server or cluster in production environment? Franklin Wang
2014-02-20  0:14   ` Nilesh Govindrajan
2014-02-20  0:36     ` Franklin Wang
2014-02-20  0:53       ` Facundo Curti
2014-02-20  1:06         ` Nilesh Govindrajan
2014-02-20  1:17         ` Franklin Wang [this message]
2014-02-20  9:28         ` thegeezer
2014-02-20 12:04         ` Tanstaafl
2014-02-20 12:24           ` Tanstaafl
2014-02-21  1:03           ` Facundo Curti
2014-02-21  1:39             ` Nilesh Govindrajan
2014-02-21 13:49             ` Tanstaafl
2014-02-27 13:09       ` Nick Cameo
2014-02-27 17:53         ` Facundo Curti
2014-03-21 13:37           ` Tom Wijsman
2014-02-20 10:29     ` [gentoo-user] Re: Fwd:How " Nicolas Sebrecht
2014-02-20 16:52       ` Andrew Savchenko
2014-02-20 20:41         ` Nicolas Sebrecht
2014-02-20 20:59           ` Alan McKinnon
2014-02-21 12:39             ` Andrew Savchenko
2014-02-26 11:44               ` Nicolas Sebrecht
2014-02-21 14:15             ` hasufell
2014-02-22  8:28               ` Alan McKinnon
2014-02-26 15:02                 ` hasufell
2014-02-26 10:55               ` Nicolas Sebrecht
2014-02-26 14:05                 ` Poison BL.
2014-02-26 15:03                 ` hasufell
2014-02-26 15:26                   ` Nicolas Sebrecht
2014-02-27  1:05                     ` hasufell
2014-02-21 11:16           ` Andrew Savchenko
2014-02-26 10:51             ` Nicolas Sebrecht
2014-02-20 14:35   ` [gentoo-user] Fwd: How " Andrew Savchenko
2014-02-21  7:35     ` Franklin Wang
2014-02-20 18:41   ` Andreas K. Huettel
2014-02-21  7:40     ` Franklin Wang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5305578C.9060903@gmail.com \
    --to=touch21st@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox