Hello im thinking about using etch as a file/lamp server. and got some questions:

1) Using apt-get am I able to get the latest php/apache/mysql or if i remember correctly there is an option to install a LAMP server during the install?

2) Manual tar.gz installs, on slackware 11 the ./configure, make, make install never seemed to work. Seemingly it didnt appear to work, but when using installpkg worked fine. Hows using this approach in debian

3) I noticed the discs required for etch is 14. whats the minimum of discs i need for an install.

Thanks

1) Yes, there is a selection opportunity available during the installation process.
2) Debian also has a program to help you build .deb files: module-assistant. If you install the build-essential package you can also install files with ./configure && make && make install.
3) If the machine has a (wired!) network connection: 1. Use the netinstall cd and get the latest packages directly from the internet. Otherwise: grab the DVD

ouch, no way am i burning 14 cds lol. netinstall its lol.

also another question is there a root user? or do i have to do sudo's

debian has root user. none of that sudo nonsense

Of course you can still install the 'sudo' package if you want to use it....I find it rather convenient myself. None of that starting new root sessions nonsense.

Actually, with the current Etch installer (at least with the expert install), you are given the option of setting up the traditional root account or going with sudo.

I hate that sudo garbage, ill take a root account anyway. sudo feels like your begging for trouble.

I like sudo myself.

Hmmm ... at the risk of igniting a flame war, I'd say that you would be wiser using sudo. Just set it up using visudo, add the user's name under where it says root and then copy the rest of the root line into the user's line and save.
Then whenever you want to do anything that requires root permissions, even temporarily, you just type in sudo and command and type in your own passwd and you're off. Often, if there's a lot of work you need to do then sudo will remember your passwd and not ask you. It is ane extra layer of security and to use a root account as your main user a/c is not only a security risk, it is just plain foolish.

yea i agree using root as a your main account is foolish. I typical will su into root do what i need to do and jump out. But i do agree sudo has its place, if i needed to create a new user, su'ing into root for that can be excessive. I personally disabled using root to login with ssh, so thats a layer of security in itself. But i also think sudo is optimal for someone new to linux and doesnt understand the trouble they can cause.

As for a flame war, i think the linux community is mature enough to understand that everyone has their own way they like to do things and go with the distro that fits that preference. Im not bashing people that use sudo, i just prefer using su for what i need.

I used to do this on Slackware - but on Debian it is just so straightforward and is different from su'ing (?) in that sudo means that the user is restricted to that one command, whereas su is pretty open-ended. The knack would be to limit su explicitly, for example, su -c "make install" is a typical case in point.

sudo does that for one, so that it would be a case of sudo make install and the user installs using their own passwd. When one su's (??), the root passwd is exposed. If the system is compromised, any packet sniffer would pick this up and then the keys to the kingdom have been sacrificed.

Not sure if I understand this tehfatal. Are you saying that sudo is best for those who don't know what trouble su could cause or - shock, horror - use root as their user a/c?
If so, then I'd agree with you. I'd also suggest that good habits should die hard. God knows how many times I have been frantically banging away at the keys deep into the night in order to undo something that I thought was a good thing at the time using su!

You'd think wouldn't you!

Ditto - but reversed

ha yea man, i deleted mysql.sock somehow trying to remove my mysql install, but reinstalling it didnt put a fresh one on my system, so thats my pain-in-the-ass experience using root.

You're new around her arn't you

1. I think there is option of postgresql and apache during install. But it's not some problem to install it later.
2. AFAIK, Slack is very good for compiling and very rarely happen failures. But you will very rarely need this on Debian, since apt-get is very good and there are more binary packages than for Slack.
3. Get first 1-4 disks, depending on your internet connection and wm (KDE should be on CD2).