Need slackware configuration docs

Kocil · 05-24-2003, 04:15 AM

Hi all.

I'm not so newbie on Linux, at least at Redhat.
But when I have to configure a slackware based server,
I'm a little bit lost inside the /etc.

Would you please tell me where to find
online documentation about slackware low level
configuration (directly editing something in /etc),
especially on networking, firewalling and service management ?

Thank you.

quietguy47 · 05-24-2003, 07:37 AM

If you are looking for an editor. There is, vi, vim, joe, jove, pico, emacs and many more.
To use one of these editor's from the command line, just type
#vim /etc/filename

itsjustme · 05-24-2003, 12:47 PM

Have a look in :

/usr/share/doc/Linux-HOWTOs

Don't know that these are specific to slackware, however.

Also, have you looked here:

http://www.slackware.org/book/

regards...

Allen614 · 05-24-2003, 04:43 PM

GNU Midnight Commander "mc" is an excellent CLI filemanager with a built in text editor "mcedit".

itsjustme · 05-24-2003, 04:48 PM

Am I confused??

I don't think Kocil is looking for an editor.

Quote:

Would you please tell me where to find
online documentation about slackware low level
configuration

Kocil · 05-24-2003, 06:15 PM

Yes, I'm not looking for an editor.
I'm looking for :
* what file should I edit if I want to configure something
* what command to start/stop a service.

For example on Redhat,
To change network setting I would do :
# vi /etc/sysconfig/network

If I want to add a service,
I would make a script at /etc/rc.d/init.d then
# chkconfig add the_service
# service the_service start

But I could not do the same thing on slackware.
Does slackware support sysinitv ???

Kocil · 05-24-2003, 06:25 PM

Itsjustme, your link help me a lot

http://www.slackware.org/book/index....urce=c623.html

It said slack uses BSD style init, and only support inisysv since 7.0.

I can understand which file to look for configuration now, but still a little bit confused about the content (long script inside).
Is there another documentation about this ?

Thank you.

figadiablo · 05-24-2003, 11:04 PM

Go into /etc/rc.d and read all of the rc.* script files. They are pretty self explanatory. The most importants I think are rc.inet1, rc.modules for example. Also in the /etc/ check inetd.conf, services and identd.conf for example. Just keep on reading and use google.com/linux a lot.

Good luck,
Figa

Alan Hicks · 05-26-2003, 03:12 PM

Quote:

Also, have you looked here:

http://www.slackware.org/book/

slackware.org is currently a CNAME to slackware.com, and has no direct affiliation with The Slackware Linux Project. Please do not make references to slackware.org, as this may not always point to the desired location. Some cyber-squatters took it before Pat and Co. could, and refuse to relenish it, even though they forward it all to slackware.com.

itsjustme · 05-26-2003, 06:42 PM

I did not know that.

I compared the .com to the .org, and they appear to be exactly the same.

What's a CNAME and what are the implications?

What does this mean:

Quote:

...even though they forward it all to slackware.com.

Thanks...

MasterC · 06-18-2003, 11:47 AM

Quote:

Originally noted by ZoneEdit FAQ
# What is a "CNAME" record?

"CNAME" records, short for "Canonical Name", create an alias from a domain name to another. You could create an alias from "yahoo.mydomain.com" to "www.yahoo.com", and every reference to "yahoo.mydomain.com" would go to the other location, regardless how yahoo changed their IP addresses! Be careful, however; CNAMEs won't work everywhere. If you create an MX record, and the name used for the mail server was defined using a CNAME, you might lose e-mail!

HTH

Cool