public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Philip Webb <purslow@sympatico.ca>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Gentoo Badges
Date: Thu, 4 Aug 2005 13:30:53 -0400	[thread overview]
Message-ID: <20050804173053.GA7100@sympatico.ca> (raw)
In-Reply-To: <200508040903.25072.yeahsowhat@gmail.com>

050804 Chris Cox wrote:
> On Thursday 04 August 2005 08:50 am, Ryan Viljoen sighed:
>> Yeah so you just skipped n00b status?
>> You never asked a stupid question?
>> No I thought not.
>> Thats the spirit lets keep Gentoo to ourselves so it can grow...
> I was of course just kidding.
> I do like Gentoo but hey, it isn't the right choice for everyone.
> Some people I'm sure would prefer hand holding and fancy GUI installers
> that other Distros have a seem to cater to the masses.
> DO you really think Gentoo should be the first Distro
> people new to Linux should turn to?

It's not whether they're new to Linux,
but whether they're new to system administration.
A good sysadmin who's known only Solaris or even M$
should be able to install Gentoo & quickly make it useful;
grannie, who's been using the Mandriva Linux her grandson installed for her,
should be very kindly encouraged to go back to his personal support.

Gentoo is for people who want to manage their own machine in their own way
& the real bouncer at the door is the DIY installation test.

-- 
========================,,============================================
SUPPORT     ___________//___,  Philip Webb : purslow@chass.utoronto.ca
ELECTRIC   /] [] [] [] [] []|  Centre for Urban & Community Studies
TRANSIT    `-O----------O---'  University of Toronto
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2005-08-04 17:36 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03 23:20 [gentoo-user] Gentoo Badges Ryan Viljoen
2005-08-04 13:43 ` Chris Cox
2005-08-04 13:50   ` Ryan Viljoen
2005-08-04 14:03     ` Chris Cox
2005-08-04 14:27       ` Michael Sullivan
2005-08-04 14:37         ` Daniel da Veiga
2005-08-04 14:50           ` Michael Crute
2005-08-04 16:33             ` Willie Wong
2005-08-04 17:19               ` Daniel da Veiga
2005-08-04 14:05                 ` Eddie Mihalow Jr
2005-08-04 17:22             ` Bryan Green
2005-08-04 17:40               ` Luke Albers
2005-08-04 22:20               ` Paul Kain
2005-08-05 20:57                 ` Daevid Vincent
2005-08-04 18:17             ` Jonathan Nichols
2005-08-04 14:43         ` Ryan Viljoen
2005-08-05 13:40         ` Walter Dnes
2005-08-04 17:30       ` Philip Webb [this message]
2005-08-04 19:14         ` kashani
2005-08-04 20:29           ` Ryan Viljoen
2005-08-04 20:57             ` Daniel da Veiga
2005-08-04 21:00             ` Paul Kain
2005-08-05 12:23             ` Holly Bostick
2005-08-04 17:53       ` Craig Zeigler
2005-08-04 22:13         ` George Roberts
2005-08-05  0:41         ` Ciaran McCreesh
2005-08-05  1:08           ` Jamie Dobbs
2005-08-05  1:18           ` Willie Wong
2005-08-04 14:11     ` Michael Sullivan
  -- strict thread matches above, loose matches on Subject: below --
2005-08-09  7:45 Tibdixious, Daiajo

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=20050804173053.GA7100@sympatico.ca \
    --to=purslow@sympatico.ca \
    --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