Slackware This Forum is for the discussion of Slackware Linux.
|
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
09-27-2013, 08:50 AM
|
#1
|
Member
Registered: Jan 2009
Location: Canada
Distribution: slackware, OpenBSD, OSX
Posts: 233
Rep:
|
Apache2.4 on -current
I'm hoping someone is doing something similar and can assist. I have a server that had been running 14 and Apache2.2 and I had it configured to accept connections only from the 192.168.1.0/24 subnet I provide for the use of my students.
Fast forward...after the summer holidays, I just <fool>blindly upgraded</fool> to -current and Apache2.4 was installed and I'm finding the changes to the config files as baffling as if they were written in Martian...
Can anyone point me to some easily digestible howto's that will 'splain it all? or would it be easier to just remove 2.4 and reinstall 2.2?
|
|
|
09-27-2013, 09:40 AM
|
#2
|
Member
Registered: Mar 2012
Distribution: Slackware, Alma, OpenBSD, FreeBSD
Posts: 567
Rep: 
|
You can always revert back to 14.0 if that's what you're looking for? 14.0 is still supported.
|
|
|
09-27-2013, 09:43 AM
|
#3
|
Senior Member
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,639
Rep: 
|
|
|
|
09-27-2013, 10:36 AM
|
#4
|
Member
Registered: Jan 2009
Location: Canada
Distribution: slackware, OpenBSD, OSX
Posts: 233
Original Poster
Rep:
|
Quote:
Originally Posted by BCarey
|
thanks Brian...I've been through that and it appears that the pertinent reading is the page that details mod_authz_core...perhaps when I get this internalized I'll do a howto and publish it for those who want some simpler instructions...'d just rather not downgrade as the easy way out
|
|
|
10-02-2013, 01:46 PM
|
#6
|
Member
Registered: Jan 2009
Location: Canada
Distribution: slackware, OpenBSD, OSX
Posts: 233
Original Poster
Rep:
|
Quote:
Originally Posted by BCarey
|
this was quite helpful...there was one module that needed un-commenting and one extra config file that needed a tweak...thanks very much for the clues.
|
|
|
10-02-2013, 05:28 PM
|
#7
|
Senior Member
Registered: Oct 2005
Location: New Mexico
Distribution: Slackware
Posts: 1,639
Rep: 
|
Glad you got it sorted. I will be doing the same thing soon.
Brian
|
|
|
All times are GMT -5. The time now is 10:25 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|