public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Keith Hinton" <keithint1234@gmail.com>
To: <speakup@braille.uwo.ca>
Subject: Arch Linux celling points
Date: Thu, 18 Nov 2010 11:01:20 -0700	[thread overview]
Message-ID: <8F7DA029AB294F10B79C434B77215A81@KeithPC> (raw)

Steve, I was curious what you meant recently when you said: "What surprises
me about it is it resembles Debian Unstable but yet mostly production
versions of applications are used and it very rarely breaks."
I believe you use Arch yourself, right..so why should that surprise you?
Also, the Arch Linux wiki has a lot of documentation that is well-written if
you ask me.
Arch has an installation process that I find to be a lot easier in most
cases than other installations.
I mean..the number of steps to installing Gentoo is far more than Arch, if
you ask me.
I also like how Arch doesn't cause a lot of stuff you don't need running
even on the LiveCD environment. So many LiveCDs I find are running ssh, and
a billion of other services that you don't even require in a live
environment. The other big point I'd like to make is that not only do other
services run on most CDs I've tested, but so many of them try to
automatically probe for Eth0 and activate it. I don't like that. In my case,
I couldn't have that happening in any case because I use a wireless network
over here. While I find Ethernet a more simpol technology in general with
Linux or anything else as a dhcpcd eth0 is required the number of connected
cables poses an issue.
What about yourself?
As for handeling wireless on my laptop when I'm in a hurry I store all my
configuration settings in a network profile for that particular network.


Regards, --Keith
Skype: skypedude1234
Twitter/AIM/Yahoo: keithint1234
MSN: keithint37@hotmail.com
Facebook: http://facebook.com/keith.hinton1
Website: http://www.keithnet.us 


             reply	other threads:[~ UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Keith Hinton [this message]
 ` Steve Holmes

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=8F7DA029AB294F10B79C434B77215A81@KeithPC \
    --to=keithint1234@gmail.com \
    --cc=speakup@braille.uwo.ca \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).