hi all,
since about february i ditched windows and started exploring different linux distro's.
i checked out lots of reviews and Slackware caught my attention for all the remarks on its overall security, speed and stability. but i was never able to get past the installation, so addicted to the GUI i was...

after more searching i found VectorLinux, Slackware based distro and with lots of extras do all the administrative tasks (VASM).
and thats what i've been using untill now. even though i like Vector a lot, i've got very used to the command line (writing a few bash scripts already), and want to give Slackware 10.2 a try again.

today after a first try i finaly installed it!

i added a new user for myself (adduser), and configured my sound with alsaconf etc, but a lot of tasks that i used to do with VASM i dont have any clue how to do on slackware.

can anyone give me pointers on the following:

-configuring iptables to disable all ports except the ones strictly necessary for browsing the net, using ftp to upload files. also general iptables activating/deactivating ports

-adding extra items to lilo, for chosing tui or gui at the lilo prompt

-changing user/root passwords

-getting my box to power-off after issuing halt. i just hear the hard-drive switching off, but the computer still remains on.

i have also ordered the Slackware Essiensials book from the slackware store, but since i live in Portugal it will probably take a while to arrive and i can't wait that long to get started!

thanks in advance

Welcome aboard

The slackware essentials book is available online
Check that one and post any doubts left on you.
Happy slacking.

Check out http://easyfwgen.morizot.net/gen/. Saves precious time until you are more ready to dig deeper into iptables theory.

I do not use LILO. I use GRUB. But the following mini how-to might provide some insight into the basic procedure, which is basically the same for LILO:

Configuring Slackware for a GUI and a Command Line Startup

Basic GNU/Linux stuff.

Probably need to configure apm daemon. Try this mini how-to:

Configuring the APM Daemon

Here are some foundational links to help you find additional Slackware documentation:

Getting Started

Welcome, you'll be fine in a few weeks, hang on! I tried vector for 2 days after about a year of slackware and i found it gets a lot in the way (nvidia, kernels, etc).
This IS the place to learn slackware, use the search option a lot, check stickys and hang around.
These you could find on your own, but anyway:
http://shilo.is-a-geek.com/slack/
http://www.vcn.bc.ca/~dugan/setting-up-slackware.html
http://slackwiki.org/Main_Page
etc....etc...etc....

thanks for all the replies!
i'm goung to follow up on those threads as soon as i get a chance

Hi,

Might I add that you check out my sig for some good online reference(s)!

edit: BTW, Welcome to Slackware!

yup, all those sites have been handy thanks a lot!
already got X up and running!

about the boot-loader options, i think i will look into using grub. lilo doesn't seem to allow spaces between words or even long names for the labels, not to mention, i can't figure how to add an option without necessarily having to create an initrd file in /boot.

#!/bin/bash
iptables -F INPUT
iptables -P INPUT DROP
iptables -F OUTPUT
iptables -A INPUT -i eth0 -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A INPUT -i lo -j ACCEPT
iptables -A INPUT -p tcp --dport 443 -j ACCEPT
iptables -A INPUT -p tcp --dport 80 -j ACCEPT
iptables -A INPUT -p tcp --dport 2010 -j ACCEPT
iptables -A INPUT -p tcp --dport 9000:9200 -j ACCEPT
iptables -A INPUT -p tcp -s 192.168.1.2 -j ACCEPT
iptables -A INPUT -p tcp -s 192.168.1.3 -j ACCEPT
iptables -A INPUT -p tcp -s 192.168.1.4 -j ACCEPT
iptables -A INPUT -p tcp -s 192.168.1.5 -j ACCEPT

is what i use to close of and stealth ports i dont need - still newish to slack myself - been using it for a while but never really looked into it - it was working so i left it alone so dont know if above is right or not

haven't moved on to trying grub yet, still wanted to try my best with lilo.
i ran the mkinitrd command, and it created an initrd-tree in /boot

i was not quite sure what to do next, so i just copied /etc/inittab to /boot/initrd-tree/etc/
and then modified the inittab to have a default runlevel of 4; ran mkinitrd and it created an initrd.gz file in /boot.
edited lilo.conf to create a new entry for TUI (including a line with initrd = /boot/initrd.gz and then ran lilo; no errors occured.

when i rebooted lilo presented me with the two options i added (Slackware-GUI and Slackware-TUI), but both of them boot slackware into init 3 despite the fact that the inittab file in /boot/initrd-tree/etc was modified so that it was set to init4.
what am i doing wrong? is using a modified inittab in the new initrd.gz file not the right way?

I was used to grub too from previous distros, till i found how simple and stable is lilo.
/etc/inittab is the file to edit for runlevels, also check /boot/README.initrd
I think i'd help to check alienbob's and shilo's sites:
http://alien.slackbook.org/dokuwiki/...kernelbuilding
Post if you have more questions, lots of helpfull people around

Welcome to the best Linux community in the world. It's a very good feeling to be part of this community, you'll realize it in time

thanks for the reply!

i had already read the README.initrd, and it did not mention anything about adding an initrd.gz with the sole intent of having the option of booting slackware to a different runlevel when lilo starts (choice between text-user interface and graphic interface).
do i have to compile my kernel just for that?

EDIT:
i need these lilo options because i don't want to continualy tamper with inittab

Just add a line with append="4" to the kernel you want to run with that runlevel.
ie:
Of course, run lilo after that change to update the loader.

@gbonvehi:

thats exactly what i have been looking for, thnaks man!

it is actualy nice to do the all the configuration manualy, its like driving a car with both hands on the steering wheel!

i guess i'm kind of paranoid about what goes on within an OS, so its reasuring to have Slackware's transparency.

You can also enter the number (for runlevel) manually at the boot: prompt (and other options, too).