how to install slackware 10
5ky123d
i'am newbie in linux(i just know windows OS) in my office, many user
used linux, so... i try to learn it.. but, i don't how to install it to
my pc.. then i hope.. had can help me.. and explain to me about
slackware...
thank's
Dan C
Slackware is not for you. Stick with Windoze.
Anything else you need to know?
--
If you're not on the edge, you're taking up too much space.
Linux Registered User #327951
Douglas Mayne
The title of your post alludes to Slackware 10. Have you already
downloaded that, or otherwise obtained the discs? If not, then this
explains how to get Slackware:
http://www.slackware.com/getslack/
Version 10.2 is the latest released version of Slackware.
If you want to learn about GNU/Linux, then there's no substitute for hands
on experience. But you should probably do a little homework before
jumping right in. Lucky for you, you're not the first person to switch to
GNU/Linux, and the documentation is quite mature at this point. Here is
some good introductory material about GNU/Linux:
http://en.wikipedia.org/wiki/Linux
http://en.wikipedia.org/wiki/Slackware
One way of getting a feel for what Linux is all about is trying a live CD,
such as Slax or Knoppix:
http://en.wikipedia.org/wiki/Livecd
http://slax.linux-live.org/
http://www.knoppix.com/
Hopefully, that gives you some initial pointers about where to look for
more specific information. Part of getting started is knowing where to
begin and what questions to ask. Unfortunately, a lot of the knowledge
you may have from using Windows is not directly applicable in GNU/Linux.
They're two separate worlds.
--
REG: ...We need doers in our movement, Brian, but...before you join us,
know this: there is not one of us here who would not gladly suffer death...
COMMANDO: Uhh. Well, one.
REG: Oh, yeah. Yeah, there's one, but otherwise, we're solid. Are you with us?
ANC
> On Sun, 26 Feb 2006 18:23:56 -0800, 5ky123d wrote:
>
>> hi.. there
>> i'am newbie in linux(i just know windows OS) in my office, many user
>> used linux, so... i try to learn it.. but, i don't how to install it to
>> my pc.. then i hope.. had can help me.. and explain to me about
>> slackware...
>
> Slackware is not for you. Stick with Windoze.
>
Dan is correct. Go to either mepis.com or kanotix.com and download a live CD
iso and burn it (they have instructions on said sites) and run Linux from
the CD and see how you like it. If you think it is for you, then you can
install either one along side Windows and have a dual-boot machine. Very
simple.
Slackware is for advanced users who know what they are doing or for newbies
willing to spend a lot of time and energy to find out. Feel free to read up
on Slackware and how to install it, but if that becomes too daunting, go
the liveCD route, learn a few things about Linux, and in six months or so,
come back and get Slackware.
anc
prodigal1
> Dan C wrote:
>> Slackware is not for you. Stick with Windoze.
> Dan is correct.
plonk^2
assholes
No_One
Contary to what anyone may tell you Slackware is not complex or difficult to
install or manage. There are some who will claim otherwise...it's just not
true.
Slackware only requires some gray cells, the ability to use a keyboard and
the ability to read and think for yourself.
There are good docs that come with Slack about installing and you can also
find solid install info in the slackware book edited by Hicks....there
should be a link at slackware for this tutorial.
It's really very simple.
Avoid the nay-sayers.....
ken
richard
Some relevant links for installation.
The Slackware Book (Revised)
http://www.slackbook.org/
Installation section from that
http://www.slackbook.org/html/installation.html
The Slackware-HOWTO
ftp://ftp.slackware.com/pub/slackware/slackware-10.2/Slackware-HOWTO
Richard :)
Grant
>Slackware only requires some gray cells, the ability to use a keyboard and
>the ability to read and think for yourself.
Dare I suggest also the willingness to start over rather than to
attempt recovery during install?
Pat's install attitude seems to me: "do it right, or do it over",
as well, one learns immensely from the install / setup --> is why I
got stuck on slackware since mid '04 (me redhat refugee).
>Avoid the nay-sayers.....
Yay!
Grant.
--
... The computer scientist, who had listened to all of this said,
"Yes, but where do you think the chaos came from?"
olive
First, please don't pay attention to some insulting (like "stick with
windows") messages I have just seen as replies; these people does not
represent the linux users.
A Linux system is in his basis based on configuration files. Some
distribution make nice GUI tools in order to help you to make the
configuration files. This might be easier as a first approach; but if
you want to really understand how the system works or to make advanced
modification; you will need to modify the files anyway and the GUI will
not help you. Slackware does not ship such GUI tools but ship well
commented configuration files. Also almost all other distributions have
a huge software database that you can install with their tools; managing
dependencies of software, etc... Slackware has quite a lot of packages
but do not ship every software and does not manage dependencies (the
standard install is to install all of Slackware: this take about 2 Giga
of hard disk; modern computer have more than enough space for that). The
reason why users of Slackware prefer Slackware is that these automated
tools will conflict with your manual installation (which is however
always possible) of some softwares: I personnally don't like the idea of
being stick to what the distribution provides without the ability to
install and manage the system myself.
Now you have to make a choice: if you want a distro that just work
without worrying of to know how it works and if you don't like the idea
of compiliong software yourself then Slackware is not the good choice
for you: in this case I would suggest you Mandriva
(http://www.mandriva.com): you can just insert the CD and follow the
instructions to install it.
If you want to know how the system works Slackware is a good choice and
is not so difficult to install anyway. Insert the Slackware CD and
follow the instructions (you will need to partition your harddisk and
add a swap partition yourself): if there is something that is unclear
check the Slackware book: http://www.slackbook.org/#book) (there are
maybe also instructions on the CD). If you still don't understand ask a
question to this list.
Olive
Olive
No_One
> On Mon, 27 Feb 2006 05:01:06 GMT, No_One <no_one@no_where.com> wrote:
>
>>Slackware only requires some gray cells, the ability to use a keyboard and
>>the ability to read and think for yourself.
>
> Dare I suggest also the willingness to start over rather than to
> attempt recovery during install?
>
> Pat's install attitude seems to me: "do it right, or do it over",
> as well, one learns immensely from the install / setup --> is why I
> got stuck on slackware since mid '04 (me redhat refugee).
On my first install of Slack, I fouled it up...badly, however, the advise I
got from eveyone was to just fix it....re-installing is for whimps. Well, I
whimped out and glad I did. Good learning experience.
ken
Leo
Good advice Olive
--
Leo in Canada:
A computer without Microsoft is like a chocolate cake without mustard.
< running Slackware 10.1 Linux >
Ronald Matthews
> 5ky123d wrote:
> > hi.. there
> > i'am newbie in linux(i just know windows OS) in my office, many
> > user used linux, so... i try to learn it.. but, i don't how to
> > install it to my pc.. then i hope.. had can help me.. and
> > explain to me about slackware...
> First, please don't pay attention to some insulting (like "stick with
> windows") messages I have just seen as replies; these people does not
> represent the linux users.
The key is not to be a "linux user." The key is to be a computer
user. You use the OS that is necessary to match the computer with
the software that you want to run. The first thing you need to
choose is the software you want to run. Then you pick the OS you
need to run that software on your computer. If that software
requires windoze, then so be it. If that software requires linux,
then so be it. But you _don't_ pick the OS first and then look for
software to run on it. That is what the amateurs and trashy little
zealots, like Coward Hicks, does. And this ng has more amateurs and
trash like the Coward than any group I've seen.
Remember, pick your software first. It doesn't matter which OS you
use, as long as it supports your software.
cordially, as always,
rm
eeeeee eeeeeeee
> On my first install of Slack, I fouled it up...badly, however, the
> advise I got from eveyone was to just fix it....re-installing is
> for whimps. Well, I whimped out and glad I did. Good learning
> experience.
Re-installing is not for wimps. Often re-installing is the easiest
and fastest way to correct a problem. And that is always the goal -
to use the easiest and fastest way to correct a problem.
There are others who will tell you that it is somehow superior to
spend days and weeks looking for files to edit, and figuring out how
to edit those files. This is the kind of nonsense proffered by
trash like the Coward Hicks. We shit directly in the face of Coward
Hicks. We grind that shit into every facial orifice with our boots.
And we do it again, and again, and again.
And again.
cordially, as always,
rm
eeeeee eeeeeeee
> > 5ky123d wrote:
> >
> >> hi.. there
> >> i'am newbie in linux(i just know windows OS) in my office, many user
> >> used linux, so... i try to learn it.. but, i don't how to install it to
> >> my pc.. then i hope.. had can help me.. and explain to me about
> >> slackware...
> >
> >
> > First, please don't pay attention to some insulting (like "stick
> > with windows") messages I have just seen as replies; these
> > people does not represent the linux users.
> >
> > A Linux system is in his basis based on configuration files. Some
> > distribution make nice GUI tools in order to help you to make the
> > configuration files. This might be easier as a first approach; but if
> > you want to really understand how the system works or to make advanced
> > modification; you will need to modify the files anyway and the GUI will
> > not help you. Slackware does not ship such GUI tools but ship well
This is false. You can learn the complete configuration of any
system, using the tools that system provides. Systems that provide
gui setup tools, offer tools that are easier to use than the basic
shell that slackware offers. This is a plus.
You don't learn anything about the system from using the shell. All
you learn about is how to use the shell. But if you don't need to
use the shell, and on many systems, there are gui tools to replace
the shell, then you are further ahead to use the gui tools.
Remember, the goal is to spend your time learning about the
application software, not the OS. The OS should be invisible and
the less time you have to waste "learning" the OS, the better off
you will be. Using gui tools that some linux OS offer gives you
more time to be productive. Time spent on the OS is unproductive
time.
> > commented configuration files. Also almost all other
> > distributions have a huge software database that you can install
> > with their tools; managing dependencies of software, etc...
> > Slackware has quite a lot of packages but do not ship every
> > software and does not manage dependencies (the standard install
> > is to install all of Slackware: this take about 2 Giga of hard
> > disk; modern computer have more than enough space for that). The
> > reason why users of Slackware prefer Slackware is that these
> > automated tools will conflict with your manual installation
> > (which is however always possible) of some softwares: I
> > personnally don't like the idea of being stick to what the
> > distribution provides without the ability to install and manage
> > the system myself.
You can install and manage any linux system yourself. You can
compile and install software on any linux system. There is no
advantage to doing this on a slackware system. Other systems use
much more sophisticated packaging systems than slackware, and these
are good to use as well. They are good to use because they save
time. And the less time spent admining your OS the more time you
have to be productive. As I said above, fussing with your OS is
counter-productive.
> > Now you have to make a choice: if you want a distro that just
> > work without worrying of to know how it works and if you don't
> > like the idea of compiliong software yourself then Slackware is
> > not the good choice for you: in this case I would suggest you
> > Mandriva (http://www.mandriva.com): you can just insert the CD
> > and follow the instructions to install it.
You have to know just as much about how it works to run Mandrake as
you do slackware. The difference is that mandrake has more
sophisticated gui tools and slackware does not. This means that
with slackware you have to spend more time fussing with the OS,
while learning nothing more about the OS, than you do fussing with
Mandrake. And fussing with the OS is a waste of time. Fussing with
the OS strictly through the bash shell is a _huge_ waste of time.
Shells like the bash shell have been around for 30 years. They are
primitive and when you learn to do things with the bash shell, you
are learning very little about the OS and a great deal about the
bash shell. And learning about the bash shell is a tremendous waste
of time.
> > If you want to know how the system works Slackware is a good choice and
> > is not so difficult to install anyway. Insert the Slackware CD and
Actually slackware is not a good system if you want to know how the
system works because you are spending all your time learning about
the bash shell, and not the system itself. By using a gui, and
bypassing the bash shell, you are learning just as much about the
OS, and you are learning it a lot faster. And this gives you more
time to be productive with the applications that you want to run.
Ignore slackware zealots. They don't run software that doesn't come
with the distro. They just sit there and watch the prompt and
pretend that they are doing something.
cordially, as always,
rm
Niki Kovacs
Hi,
I see the psychopaths in this NG have already introduced themselves and done
their best to get you out of here. Never mind them.
1) Get the first two Slackware 10.2 CDs.
2) Get the basic doc: http://www.slackbook.org/
3) Read it (I mean: every single line of it)
4) Read it again. Print it out, keep a copy.
5) Play around, experiment. Find an old Pentium II or III box to learn
Slackware. (Older ones are OK too, but if you're a newbie, avoid too old
hardware)
6) Come back to ask questions.
Cheers,
Niki Kovacs
PS: started like you in 2001. Was glad then folks were kind.
>
> thank's
boricua
agree slack is the distro to learn linux. and trust me its a 100% easier
than what some people say
Melissa Danforth
: hi.. there
If you have administrator access on that Windows PC, then one of the
easiest ways to play around with Linux is to use a Virtual Machine. There
are a couple of options. If you have the money, you can buy MS Virtual PC
or VMWare Workstation. VMWare is the superior product IMO, but it is more
expensive. VMWare also offers a completely free product that you can use
to run existing virtual machines called VMWare Player:
http://www.vmware.com/products/player/
You can download several VMWare Player images from their image collection
at: http://www.vmware.com/vmtn/appliances/
There isn't a Slackware image there, but there are many other distributions
and even some of the BSDs to try. If you do a search on Slackware VMWare
Player, you might find a virtual machine image that hasn't been put on the
VMWare site yet or instructions on how to install Slackware on a VMWare
Player image.
Stanislaw Flatto
> Slackware is for advanced users who know what they are doing or for newbies
> willing to spend a lot of time and energy to find out.
Oh my younger days!
Have not seen so much bullshit since working on farm.
To the OP, do what you want! That is THE Linux way.
Stanislaw
Slack user from Ulladulla.
FWB
> Contary to what anyone may tell you Slackware is not complex or
> difficult to
> install or manage. There are some who will claim otherwise...it's just
> not
> true.
Being a relative newbie to Linux and Slackware, I will echo this.
I read the installation instructions in the Slackbook
(http://www.slackbook.org/), took my time, used google a lot, and got my
webserver up and running. Then I installed it on my laptop.
I just bought "Slackware Linux Essentials"
(http://store.slackware.com/cgi-bin/store/slackbook?id=V9UqqjKx:mv_pc=29)
from the Slackware store and am re-reading it (it is the Slackbook in
published form).
What I have found is that there is a lot of help out there for someone who
wants to learn about Linux, as long as that someone is willing to a little
research on his or her own before doing something like posting to a
newsgroup or forum.
Here's a little information about my own experiences setting up Linux on
my laptop: http://frankwbell.no-ip.info/weblog/?p=225
--
Blogging from Pine View Farm--http://frankwbell.no-ip.info/weblog
Updates daily. Worthwhile updates occasionally.
fwb2355 is a spam trap. Email frankwbell at comcast.net
Slackware (http://www.slackware.com) and Opera (http//:www.opera.com):
the ultimate internet experience./
FWB
wrote:
> A Linux system is in his basis based on configuration files. Some
> distribution make nice GUI tools in order to help you to make the
> configuration files.
Bravo!! Well said!!! to your entire post.
Peter Chant
> This is false. You can learn the complete configuration of any
> system, using the tools that system provides. Systems that provide
> gui setup tools, offer tools that are easier to use than the basic
> shell that slackware offers. This is a plus.
>
> You don't learn anything about the system from using the shell. All
> you learn about is how to use the shell. But if you don't need to
> use the shell, and on many systems, there are gui tools to replace
> the shell, then you are further ahead to use the gui tools.
>
That's rubbish, I've been using Slackware for years and am useless at
bash programming.
> Remember, the goal is to spend your time learning about the
> application software, not the OS. The OS should be invisible and
> the less time you have to waste "learning" the OS, the better off
> you will be. Using gui tools that some linux OS offer gives you
> more time to be productive. Time spent on the OS is unproductive
> time.
>
However, you can find that the you spend time hunting down the settings in
the gui tools. No OS is invisible. Slackware is not invisible. Windows
is not invisible. For all OSes from time to time you will need to adjust
things.
> Ignore slackware zealots. They don't run software that doesn't come
> with the distro. They just sit there and watch the prompt and
> pretend that they are doing something.
>
> cordially, as always,
>
> rm
If this is meant to be a sock puppet you are not meant to sign with your
usual user id!
Ronald Matthews
> > This is false. You can learn the complete configuration of any
> > system, using the tools that system provides. Systems that provide
> > gui setup tools, offer tools that are easier to use than the basic
> > shell that slackware offers. This is a plus.
> > You don't learn anything about the system from using the shell. All
> > you learn about is how to use the shell. But if you don't need to
> > use the shell, and on many systems, there are gui tools to replace
> > the shell, then you are further ahead to use the gui tools.
> >
> That's rubbish, I've been using Slackware for years and am useless at
> bash programming.
There is a lot more to using the shell than bash programming.
> > Remember, the goal is to spend your time learning about the
> > application software, not the OS. The OS should be invisible
> > and the less time you have to waste "learning" the OS, the
> > better off you will be. Using gui tools that some linux OS
> > offer gives you more time to be productive. Time spent on the
> > OS is unproductive time.
> However, you can find that the you spend time hunting down the
> settings in the gui tools.
Usually a click on a menu(s) gives you all the options available in a
well designed gui. You don't have to waste time hunting down the
settings in howtos or unreadable man pages.
> No OS is invisible. Slackware is not invisible. Windows is not
> invisible. For all OSes from time to time you will need to adjust
> things.
That's true. But the ideal OS is invisible. The aim of being
productive is to use the application software, not the OS.
> > Ignore slackware zealots. They don't run software that doesn't
> > come with the distro. They just sit there and watch the prompt
> > and pretend that they are doing something.
> If this is meant to be a sock puppet you are not meant to sign
> with your usual user id!
I don't know what you mean. I do not have a "usual user id."
cordially, as always,
rm
Roel
> On Sun, 26 Feb 2006 18:23:56 -0800, 5ky123d wrote:
>
>> hi.. there
>> i'am newbie in linux(i just know windows OS) in my office, many user
>> used linux, so... i try to learn it.. but, i don't how to install it to
>> my pc.. then i hope.. had can help me.. and explain to me about
>> slackware...
>
> Slackware is not for you. Stick with Windoze.
Little words, and mean without reason. Just worth as little.
> Anything else you need to know?
Just speak a little less.
Roel
Sylvain Robitaille
> Remember, pick your software first. It doesn't matter which OS you
> use, as long as it supports your software.
Correction: first define what you want to do with the computer, *then*
find software that will let you do those things. You can't
pick the software until you know what you want to accomplish.
It isn't useful to define what you want to do with the computer as "I
want to run ${software}", since that's picking the software first. "What
do you want to DO with ${software}" is the question that needs to be
answered.
If there isn't any software available for Linux that will let you
accomplish what you want, you're stuck operating on a system with which
ever operating system such software is available for, but then you are
likely in a very small, very specific "niche" market ...
--
----------------------------------------------------------------------
Sylvain Robitaille s...@alcor.concordia.ca
Systems and Network analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------