Re: Why so hard to setup hardware? Control panel?
From: Richard Steiner (rsteiner_at_visi.com)
Date: 02/07/04
- Next message: Matt Webster: "broken packages"
- Previous message: bi-weekly: "A new reader? Welcome to comp.os.linux.setup, read this first if you're new here (FAQ)"
- In reply to: mike: "Why so hard to setup hardware? Control panel?"
- Next in thread: mike: "Re: Why so hard to setup hardware? Control panel?"
- Reply: mike: "Re: Why so hard to setup hardware? Control panel?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 06 Feb 2004 18:10:40 -0600
Here in comp.os.linux.setup, mike <spamme0@juno.com> spake unto us, saying:
>I've been trying to migrate from Windows 98SE to linux on and off
>for three years now without success.
>I've tried about a dozen different distributions.
It would be a lot easier for us to assist if you picked one specific
Linux distribution and version, listed the specific hardware on your
system, and described the specific bad behavior that you're seeing.
Because there are so many unrelated Linux distributions, a centralized
approach to hardware config (such you you suggest) will probably never
happen, at least in a way which will work across all Linux distros.
All Linus and his development team does is provide the kernel.
Most of the stuff related to PC hardware configuration is written and
collected into the various distributions by third parties, and those
third parties are often in serious disagreement when it comes to the
specific set of configuration tools to include.
Some (like Mandrake and SuSE) have written their own, resulting in a
number of similar tools that are distribution-specific. That's the
current trend, and it will likely remain so until some general set of
support tools comes along that the major players can agree on.
All one can do is pick a distro that is commonly used and request help
from those who are familiar with that distro's configuration process.
Linux is not a monolithic entity like Windows. However, each distro
can be treated that way. Success is far more likely if you focus on
a subset (i.e., one distribution) and go from there.
(Yeah, it would be nice in some ways if that weren't the case, but such
is the nature of the decentralized processes currently in vogue).
>If I can't get that much up and running in less than a week, something
>is seriously wrong. I shouldn't need anything more than the release
>notes to get that much up all by myself.
My own suggestion would be to seriously consider replacing the hardware
components that are causing problems for you with ones that others seem
to be using successfully with the flavor of Linux you're interested in.
(It's a lot easier to change hardware than it is to force someone else
to add support to their distro for something you have).
Some of us already get the results you are looking for (Linux just drops
in without a fuss, at least most of the time) because we built our systems
explicitly to be compatible with non-mainstream operating systems.
-- -Rich Steiner >>>---> http://www.visi.com/~rsteiner >>>---> Eden Prairie, MN OS/2 + eCS + Linux + Win95 + DOS + PC/GEOS + Executor = PC Hobbyist Heaven! Applications analyst/designer/developer (14 yrs) seeking employment. See web site above for resume/CV and background.
- Next message: Matt Webster: "broken packages"
- Previous message: bi-weekly: "A new reader? Welcome to comp.os.linux.setup, read this first if you're new here (FAQ)"
- In reply to: mike: "Why so hard to setup hardware? Control panel?"
- Next in thread: mike: "Re: Why so hard to setup hardware? Control panel?"
- Reply: mike: "Re: Why so hard to setup hardware? Control panel?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|