Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am planning on setting up a webserver for my own home use. Problem is I dont want ANYTHING extra. Plan on it being headless, have PHP, CGI, Perl & ASP support. SQL server so I can run a DB if I need toand maybe an FTP just to get into the thing (or SMB would be better).
So...... does anybody have a barebone setup similar to the one I am describing? I keep getting all the extra crap but I just dont want it.
Plenty of setups like that exist, only safe way to run a server. You haven't said what distros you've tried - those such as Debian, Slackware, Gentoo, etc. are perfect for those environments as they only install a base system by default and nothing else. You then install Apache, PHP, MySQL or whatever and you don't have unneccessary stuff such as NFS servers, Samba services, X servers, etc. running.
Fedora is often used by webhosts, but you need to pull it apart guite heavily to get what you want. If you're comfortable with Fedora, it's a good base to work from and very easy to install/uninstall packages. Otherwise: Debian, Slackware and Gentoo. As for howto's, check out the Tutorials section on this website, look over Linux Home Networking and become friendly with Google. Have fun
i use debian for pretty much the exact same thing. although i'm far from an expert in debian (or any linux for that matter ), and overall find it harder to work with than slack-type distributions, apt-get is enough of a "killer app" to keep me sticking with it. ssh + apt = nice combo for managing your box. i can't see gentoo on a production/server box with all that compile time. with debian you can do a fast base installation, and then you can install packages pretty much on command (no pun intended ) with apt, which is really convenient for testing out programs. if you don't like or need something, just remove it, and you haven't wasted a lot of time and resources compiling something you ended up not wanting anyway.
The point is you don't have anything you don't want on Gentoo. I haven't put in on a server yet, but know others that have, and since the request for a basic distro with nothing else to bloat it, thought i'd stick it in Can be a tinker sometimes. Once Gentoo is compiled though, it shouldn't be so much of a difference. You're not going to installing new software, just patches. You'd schedule downtime for this anyway. Unless you're running old hardware, even a complete recompile of Apache + PHP + MySQL isn't going to leave you tearing you hair out and clock watching.
As a majority of reference to servers I hear Debian come up alot in the past I think I'll give it a go. Its only a small P2 tower anyway so we'll see what we can get to going.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.