Hi all,
Im kinda new to linux and I wanna get more familiar with it. I have some questions now, I'll find more later, but let's start.

Here they are:

1) Where do I see all applications installed on my linux?
(So I can see if any is not useful and remove it. Like add/remove programs over windows )

2) How do I know what applications and DAEMONs are running? How do I kill them?

3) Where do I see what hardware is installed on my system? And where should I start when wanting to make my system recognize a new one.


-------
I think that's all for now.

Thanks in advance for any thought.

1) depends on where u install that, if you install at /opt, then there's where you found it.
by default, i believe most applications come w/ the distro are store in /usr/local

2) type: ps
then if you found pid you don't want, type: kill [pid number]

3)u should be able to find what hardware are in ur computer by looking at a "control panel" like program under ur X, if u use kde, go click kde configure
if kernel is already enable certain hardware, plug right in will do the trick, (if it loads as module, then u need to start the modules) otherwise u may need to re-compile kernel.

p.s: if i were u, i will start by reading most of your doc that come with slackware, there's a lot of howtos in there will help u get around

1) Where do I see all applications installed on my Linux?
if your using slackware 9, then its as easy as typing "pkgtool" at the on a terminal as root.


2) How do I know what applications and DAEMONs are running? How do I kill them?
type "ps -ax" at the command prompt and that will list all the running processes with their process ID number (PID), then if you don't like something just type "kill ####" like "kill 1338" (thats If I wanted to kill mozilla while I was typing this reply)


3) Where do I see what hardware is installed on my system?
first type "lsmod" at the terminal to see what modules are being used by what, that sometimes helps in seeing what hardware your using (provided that the hardware your using requires modules, rather than being compiled into the kernel) (theres probably a better answer to this question)


And where should I start when wanting to make my system recognize a new one.
first put the hardware in and try to use it, if that doesn't work do a google search on {"hardware device" "Linux driver"} or something of the sort, and that will usually help you figure out what kernel module you need, then just type "modprobe {name-of-module}" and the hardware should work (although you'll probably have to add that module to your startup somehow)

All the default installed packages/programs will be listed in /var/log/packages

If you continue to install your apps with Slackware specific ( tgz's ), they will continue to be listed in that directory, etc.

........ as a follow-on from killing processes - you'll probably eventually want to stop certain services/daemons/scripts from starting/executing at boot-up.

In Slack - as Root user from an xterm, cd into /etc/rc.d

then (for example)

chmod a-x rc.sendmail

chmod a-x rc.samba

for more control again you can just comment out blocks in files like rc.inet2 ( be careful though, back-up and read up on the services themselves before stopping any)

First, thanks everyone.
Second and on:

>"p.s: if i were u, i will start by reading most of your doc that come with
> slackware, there's a lot of howtos in there will help u get around "
1) Where's that?

--
I understood everything but that module thing related to hardware: "provided that the hardware your using requires modules".

2) What are these modules? It is the way Linux treats hardware? If so, how come a hardware not require a module?
As you can see, I'm kinda lost..
---
And...
3) What are those rc.* files on /etc/rc.d ? What am I exactly doing when I do "chmod a-x rc.samba" ?


--
Again thank you all very much.

u know, i'm new to slackware myself (just starting to install)
but this is what i would do,
login as root by type: su
then password
type: slocate -u
type: slocate howto

it will show all the howto you have in your computer and tells you where they located

the newbie way...heheh

1) and 2) in win, hardware talk to OS through drivers, in linux hardware talk to OS through kernel, the so call (window language) drivers are store in kernel. but if kernel size too big, it takes long time to load, so here comes "modules". say for example, if you have a tape modules, you only use once a week, you don't want that load all the time. so you load it as modules, (which means you only load as you need),

and for example, cdrom, if u use it all the time, you want that built unto kernel, so everytime you turn on the computer, cdrom is there for you.

3) rc is a startup commands . rc has 0 to 6, it tells your computer what level to run. diff number represent diff startup, (or shut down) [correct me if i'm wrong here, i think 6 is shut down, and 5 is run X with mutip user mode] ...etc
kindda like press F5 when start window, u can start with safe mode and stuff like that.

here's a book i brought few yrs back to learn linux from. you may wanna check that out at barns n nobles.

is call: Running Linux, from O'Reilly i think this is a very good book to get you start

thanks sirpelidor, I understood 1 and 2, but I still don't get the 3, can you explain me again?

thanks!

The system initialization files are stored in the /etc/rc.d directory. The first program to run besides the Linux kernel is init. This program reads the /etc/inittab file to see how to run the system.

After system initialization is complete, init moves on to runlevel initialization. A runlevel describes the state that your machine will be running in. the runlevel tells init if you will be accepting multiuser logins or just a single user, whether or not you want network services, and if you will be using the X Window System to handle logins.

this time, i wrote down what level does what:
rc.0 is to halt (it links to rc6 also)
rc.4 Multiuser startup,
rc.6 Reboot the system
rc.k startup in single user mode
rc.M Multiuser mode w/ standard text based login