Re: Can you build your own desktop Client?
- From: Dave Uhring <daveuhring@xxxxxxxxx>
- Date: Mon, 24 Mar 2008 12:17:46 -0500
On Mon, 24 Mar 2008 09:16:43 -0700, Day Brown wrote:
On Mar 24, 2:46 am, Dave Uhring <daveuhr...@xxxxxxxxx> wrote:
You are either a complete idiot or a lying troll. The on-screen
instructions for Slackware clearly recommend the use of *one* kernel and
one only unless you have very specific requirements. There are three,
yes, three, only three kernels available for booting on the installation
media.
Within the directory slackware/a are a total of four kernels available
for installation. Neither three nor four constitutes "a couple of dozen"
except in your warped world.
The slackware 11 CD install I have lists 16 kernels. It suggests some
for scsi drives, and sata.1 for ide, but does not say what the others
are there for, or which to try if sata.1 dont work.
Then install Slackware-12 instead. It will be maintained longer and
provides better support for modern hardware. If you refuse to use a
recent kernel such as shipped with Slackware-12 it will be unable to read
your on-board sensors. Furthermore 16 is still not "a couple of dozen."
As it is, it asks me if I want to add the fat 16 and fat32 partions on
another drive to the fstab. Nice. But then, after the install, the
reboot just locks up on a blank screen. No clue. So, I booted off DOS,
and used PART.EXE to rewrite the MBR. It defaults to dos, but if I'm at
the keybd, I hit linux, and slack comes up.
I guess some people just find it too difficult to read and understand
clearly written instructions provided on the installation media.
There may well be a way to do that, but the newbie Linux user dont know
what they are, and is not going to screw around with command line
scripts. You want more Linux users? do what they expect. You wanna
special club for geeks who get to feel superior to windoze users- you
already got that.
The newbie Linux user has no business messing with Slackware in the first
place. However, even a newbie who bothers to read the instructions could
reasonably expect to succeed in installing Slackware. Never is it
required for anyone to "screw around with command line scripts".
Slackware provides some very nice utilities for system configuration.
Lets face it, sheeple are stupid; and if you want a user base large enuf
to fund development teams, you have to keep it simple. A simple testbed
install of the Linux kerel would help convince sheeple that it will run
on their own desktop.
I personally could not care less about a large user base of people like
you. I have repeatedly turned away jobs involving support of Windows
lusers, although I see you did finally succeed in getting a Linux distro
running.
.
- Follow-Ups:
- Re: Can you build your own desktop Client?
- From: Harold Stevens
- Re: Can you build your own desktop Client?
- References:
- Can you build your own desktop Client?
- From: Day Brown
- Re: Can you build your own desktop Client?
- From: ray
- Re: Can you build your own desktop Client?
- From: Day Brown
- Re: Can you build your own desktop Client?
- From: ray
- Re: Can you build your own desktop Client?
- From: Day Brown
- Re: Can you build your own desktop Client?
- From: ray
- Re: Can you build your own desktop Client?
- From: Day Brown
- Re: Can you build your own desktop Client?
- From: Dave Uhring
- Re: Can you build your own desktop Client?
- From: Day Brown
- Can you build your own desktop Client?
- Prev by Date: Re: Can you build your own desktop Client?
- Next by Date: Re: Can you build your own desktop Client?
- Previous by thread: Re: Can you build your own desktop Client?
- Next by thread: Re: Can you build your own desktop Client?
- Index(es):
Relevant Pages
|