Hmmm
I can not see apache 2.0 in future slackware 10, why?
It is not better or.... ?
Where can I see the list of slack 10 features (iptables version, mysql,...)
thx
Yours sincerely K.
In alt.os.linux.slackware, Krzys-iek dared to utter,
> I can not see apache 2.0 in future slackware 10, why?
> It is not better or.... ?
I've not yet heard a convincing argument to move to apache 2.0 myself,
but I have heard a few horror stories. IIRC, Apache broke compatability
with things like mod_perl (very commonly used) and that might have
factored into Pat's feelings here.
> Where can I see the list of slack 10 features (iptables version, mysql,...)
MANIFEST.bz
- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFA2XpilKR45I6cfKARAm9YAKCX84XsngIu6fwh3ewj2mCarf4N5wCfbBTL
ze+/7PS9sSBStZbxhcAkxKI=
=HT50
-----END PGP SIGNATURE-----
idunno. apache 1.3.31 is included.
but since slackware-10.0 is not released yet, anything
could still change.
> Where can I see the list of slack 10 features (iptables version, mysql,...)
start with files ANNOUNCE.10_0 and RELEASE_NOTES,
from a slackware-current mirror.
find more details in PACKAGES.TXT
--
Fire the Liars - Impeach Bush and Cheney!
Prosecute the criminals - Indict Rumsfeld and Ashcroft!
Corruption starts at the top.
William Hunt, Portland Oregon USA
> I can not see apache 2.0 in future slackware 10, why?
>
> It is not better or.... ?
Simple, Apache 1.3 is still the most used version so why put 2.0 in it?
If you want to use it build it yourself, same goes for kernel 2.6
It's not that hard to upgrade.
--
Alan Hicks <al...@lizella.netWORK> wrote:
> I've not yet heard a convincing argument to move to apache 2.0 myself,
> but I have heard a few horror stories.
I've had annoyances with 2.0, ones that still stop me from making
the transition to 2.0. Things like directories containing .htaccess
files not displaying in index views, and AddDescription not
working for directories. Small things, but they accumulate. These
and other niggles may have been fixed now, but I've yet to see a
compelling reason to upgrade.
- --
George Georgakis geegATtripleg_net_au http://www.tripleg.net.au/
SlackBuild Central - http://slackpack.tripleg.net.au/
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com>
iQA/AwUBQNj/kUlp3nJf7PixEQIHJwCfSkHhYRCNmLv6RhQQ3z/99XTrZ+cAn1yt
lYesurcuq42wL2rHNSCei6JC
=Ni0p
-----END PGP SIGNATURE-----
> find more details in PACKAGES.TXT
ftp://ftp.slackware.at/slackware-current/PACKAGES.TXT
interesting lecture... :)
I hope slack 10 will be ready soooooooooooooooooon :)
thx
Simply put, Apache 2 is not ready for prime time yet.
I've tried it a few times, got burned each time.
Jen
Message posted via:
=====================
www.linuxpackages.net/forum
www.linuxpackages.net
Expanding the world of Slackware
=====================
Same here; I tried setting up an Apache 2.0 server a while ago and
migrating some of my websites over to it, but so many things didn't
work that I switched back to 1.3x. It's not like I do anything
particularly sophisticated or unusual either.
--
soc.singles FAQ [ Nyx Net, free ISP ] Misc.Fitness.Weights page
www.trygve.com/ssfaq.html [ http://www.nyx.net ] www.trygve.com/mfw.html
today's special feature, "ten Warning Signs of Nocturnal Sleepiness Syndrome"
http://www.trygve.com/nocturnalsyndrome.html
I use 2 on a busy production site with no problems
DB
pgp trash troll delete
They've been working on Apache 2.0 for, what seems like ages. Curious
they're having so much trouble with it. I've seen a few hosting companies
offer 2.0, but never got the nerve to take the plunge.
ken
From what I understand (I could be mistaken), the big problems seem to
crop up with the module APIs.
--
Political Correctness is that first refuge of the intellectually
inferior. - The Open Sourcerer's Apprentice
Correct. That's where I ran into trouble anyway.
Jen