Local HTTP Server: Best OS?

[Chronic19]

Which Linux distribution do you guys feel is the best for a local HTTP server. I tried compiling my own distribution and it didn't work out how I though it would. I have experience with Linux so ease of use should not prevail over functionality. I'm thinking Redhat or Slackware, any ideas?

 

[BlitzRommel]

My thumbs up for SuSE, although there's a lot of apps you wouldn't need.

D/L the Redhat 7.2 iso's.

 

[MentalAtrophy]

Slackware or Gentoo

 

[freebsddude]

I would stick with RH.

 

[Sunner]

Slackware or Debian.

I'd say Debian if anything cause there doesn't seem to be much development going on with Slack these days.

Besides, Slack uses BSD init, which sucks

 

[thornc]

Slackware, Debian or LinuxFromScratch!

They should give you the smallest most customizable installations...

And Sunner the Slack current is being updated very often... in fact almost all of the
new goodies are there...

 

[Sunner]

Thornc, I'll be damned, had a look-see on their site, and indeed, updated several times lately

Haven't been keeping in touch much since 8.0 was released.

 

[Ludootje]

Hmmm why do you ask 'which OS' in the topic to then ask 'which linux distribution'?

Anyway, the best thing to do is OpenBSD (VERY secure) otherwise FreeBSD.
If you want to use a linux distribution: use gentoo or slackware.
Those distros who have the base, not the config thing like SuSe, Mandrake or RH are usually better, not desktop-oriented though server-oriented.

Why RH if I may ask? I haven't used it yet, but heard so many negative things about it that I don't even want to try it out.

If you only want slack or RH, go for slack.

 

[Nothinman]

Debian all the way, once you get the hang of it you'll never look back.

 

[BlackOmen]

Since you have experience, I'd put my vote in Debian or Slack. I'm a Slackware man myself, however I'm also in the minority here.

 

[n0cmonkey]

<< Debian all the way, once you get the hang of it you'll never look back. >>



No, Nothinman, Ludootje is not another screen name for me

Sunner, surprised that such a quiet distro has so much work going on?

If you want Linux, go with Debian (which is possibly the best distro I have ever used) or Slackware (which has a preferable init).

 

[Sunner]

<< Sunner, surprised that such a quiet distro has so much work going on? >>


Well I did use it fulltime before I started using Debian, but there hardly seemed to be any activity, and there were even a few rumors that is was gonna be closed down for a while.

And BSD init still sucks compared to SysV

 

[thornc]

...hehe
almost forgot about Sorcerer and Rock linux...very customizable....

 

[n0cmonkey]

<<

<< Sunner, surprised that such a quiet distro has so much work going on? >>

Well I did use it fulltime before I started using Debian, but there hardly seemed to be any activity, and there were even a few rumors that is was gonna be closed down for a while.And BSD init still sucks compared to SysV >>



Prove it.

 

[MGMorden]

I say to go Slack. I've used Debian. I've used the whole apt-get thing. It's cool for a while. I went back to Slackware eventually though and felt right at home again. It's just a lot cleaner to me (largely due to the BSD-style inits that Sunner has been bashing. I'd take them over the SysV crap any day).

 

[Sunner]

<< Prove it. >>


I dont like it, cause I use all Solaris and Debian at work, therefore it sucks

 

[n0cmonkey]

<<

<< Prove it. >>


I dont like it, cause I use all Solaris and Debian at work, therefore it sucks >>



Still not definite proof.

BSD style init has a longer tradition in UNIX systems than SysV. Long live this tradition. And hell, if BSD init was so bad you would think the rest of it was pretty bad too, and where did the SysV people get their ideas?

BTW, Solaris was the SysV version of SunOS which was BSD styled. Good stuff

 

[Sunner]

Well, on a more serious note, it seems to me like both have advantages and disadvantages, and both work, so in the end, it's what you're most used to

 

[n0cmonkey]

<< Well, on a more serious note, it seems to me like both have advantages and disadvantages, and both work, so in the end, it's what you're most used to >>



Which was what I meant by prove it.

 

[Sunner]

BAH!

 

[Nothinman]

How would you go about restarting a service with bsd init? With SysV you just '/etc/init.d/service restart'

 

[n0cmonkey]

<< How would you go about restarting a service with bsd init? With SysV you just '/etc/init.d/service restart' >>



kill -HUP PID

 

[fivepesos]

to address the thread, go with whatever linux/bsd makes you comfy. slackware is a good choice but ive used it extensively and im a little biased. and for the record, i love the init scripts. debian is a good choice because of its excellent apt utility which slackware should incorporate IMO. but theres still something convenient about compiling everything from source (but that does add time it takes to setup the system). openbsd would be a good choice also, its ubber secure but i doubt you need that on your lan (unless your roomates/family are of the blackhat variety).

go with whatever u r comfortable with.

 

[DaHitman]

<<
And BSD init still sucks compared to SysV >>



They both suck compared to HP/UX's version of modified (and cooler) SysV init.

 

[Nothinman]

kill -HUP PID

If that worked for all daemons I would agree.