lol, of course not -- it's YOUR thread, so we'll allow you some leeway

And as your post is long, and I'm in the middle of something else here at the moment, I'll read the entire thing a bit later and reply as necessary.

Sasha

yes, I do tend to be a tad long-winded ... need to work on that ...

I DO however plan to hold u on the 'will read and get back later' bit ...

btw, stupid question, but since u are a mod and all ... my entire LAMP exercise right now revolves around setting up a 'discussion forum' ... An internal one for me and a bunch of others, I am trying to get my hands on php/mysql based forum source code in the open source arena ... Any chance linuxquestions uses some kind of 'engine' that I can download somewhere? Dont need 80% of the features seen in this place, just a very basic forum ... Too lazy to LEARN php, prefer to download source code, READ UP and mod as per my requirements! Just a shot in the dark ...

Yes - Slackware 13 (not 64). Although looking at Slackware 64 it's adjusted the directories correctly. Well this if from /etc/httpd/mod_php.conf which is included when uncommenting the line in /etc/httpd/httpd.conf.
- which points to the right place for the module.
Perhaps tag files may interest you. They're basically the files the installer uses to know what to install. Here's a reference Slackware Tagiles

And I will, but I think you've made a good evaluation of the situation anyhow. I'll comment further, later.
Being a mod implies, among other things, decent communication skills, objectivity, relative friendliness, and spending a lot of time here!

My being a mod doesn't imply that I know anything about anything in particular regarding software or whatever and I've never set up a LAMP system. However, many/most of the other mods, and certainly lots of other members, have been using Linux, LAMP, and LQ for much longer than I, and may have a good answer to what you're asking wrt the forum engine, and experience with L/LAMP/P that they will share with you.

Failing that, you might inquire of the forum Admin (Jeremy) about particulars of the backends behind all LQ's features and systems, though if I'm not mistaken, there exist several (old) threads on the subject of how LQ works, and why it works so well. Try to locate them first, and see if your question is answered there.

Sasha

Have a look at Yabb. It should do what you want and is open source. I've played with it a bit but am no expert.

Yes, that scrolling thing hadn't occurred to me regarding 13 vs. all previous versions, because right from the get-go, since installing 64-current, I have been using an xorg.conf just as I always have. Therefore, I both didn't realize, AND wouldn't have known anyway, if/whether or not the scrolling worked out-of-the-box, without an xorg.conf. I have HAL disabled from my input devices.
Well, I think you sort of answered your own question here; the GPM is set up to run, I suppose because it's installed, period. Nobody (that I can see) said "there is a reasonable chance there will be no mouse/keyboard/display hooked up" -- I just suggested that this *might* be the case, and that scrolling would probably not be needed in that application of Slack. I guess it's two sides of the same coin:
side1) it's easy to set up, so why not just set it up.
side2) it's easy to set up, so why not leave it to the user to set it up?
We could argue that point all day, but to no benefit.
Correct, it was just some two-cents worth of speculation
Yes, you may be out on a limb, but I believe it's the *right* limb. HAL takes care of input-device hotplugging and whatnot, so scrolling's both a side effect (of HAL being installed) AND an intentional functioning behavior (of HAL itself, which by extension, means of Slack13 itself)
I am in the same boat with regards to all the above, except I started (on Linux) with Slackware 11, around December 2006. Slack & Linux, for me, is an ongoing learning process, and is FUN at the same time. Computing is mainly a hobby for me-- I don't run anything "mission critical", though my roommate calls my 'computer corner' the "nuclear reactor control room" because of all the hardware I've got connected up here
I've learned to enjoy the CLI, and I (didn't used to) also enjoy discovering a new kernel release, reading the ChangeLog, and updating my kernel to the latest version. I like poking around and tailoring stuff to my exact specs, and a lot of the time, I don't use Slackbuilds or SBO packages, because I actually *like* building my own packages
I cannot argue with those points, but of course, many people could argue with both, depending on their own experience with Slack.
I daresay you're totally right: Making Slack (especially 13) act like Ubuntu, would be much easier IMO than making Ubuntu act like Slack ;-)
As mentioned, (though I'll rephrase), "we'll cut you some Slack" this time!

Best regards,
Sasha

eddy,

my system, I needed to search for the php module! Anyways, I ended up reinstalling slack, so everything is back to the defaults now, so I can actually tell you exactly where the default points and where the files actually are ...
As for the tagfiles and the YABB links, will take a look at both. Thanks.

Sasha,

seems we are in agreement, so I guess no point typing more pages just to agree some more!

--------------
back to the original problem I had, I decided to first try putting an nVidia card in, before trying the other things mentioned here ... Had an old Riva TNT2 on hand, 32MB RAM! I don't know if the problem was because the card was TOO old, but the minute I stuck that card in and tried to boot, I just got PAGES AND PAGES of continuous errors!!! All involving udev ... The screen just goes nuts, churning out line after line of errors, and finally freezes with all kinds of modprobe and udev lines!!! Never reaches the login!

I was probably stupid to try this, but having hung around Windows too much, I ended up re-installing linux with the new card inserted ... was hoping that a fresh install with this card would allow it to be detected and configured or whatever!!! After sittin thru the entire installation process, boom, same junk all over again!!!

Pulled the card out and switched back to onboard, it booted up alright ... Immediately did the removing of the old and installing of the new, tried the 2.5.1 alternative ... hit startx ... and all I got was a mouse, it never went any further, not even the loading screen!!! Funny, the first day, gave me about 30 minutes each session, then yesterday, about 5 mins each session, and today it wont even START a session!!! I had some other stuff to take care of, so I had to bail without trying the other alternative drivers or checking the log files!!!

I DO have a nVidia 6600GT in another system, perhaps I ought to try using that card? The reason I didnt pull that was coz the GT needs a second power source, and I am not too sure if this old system's SMPS can handle it!

Can anybody shed some light on why the udev thing went nuts with the TNT2 card? The last slack I used did not have the udev thingy, so I am absolutely clueless, all I know is that its ... well, I THINK its the way Slack does its hardware shite now?

did upgradepkg and moved straight to the 2.8.1 alternate driver, instead of the 2.5.1 that I installed yesterday ... took quite a bit of time to load KDE, but its been about 10 minutes since it loaded, and so far so good. *fingers crossed*

@eddy.
Checked apache conf just now ... Uncommenting the php line in httpd.conf doesnt do anything, it only opens the .php files if I click on them, and parses them as though they are txt files! The problem is that the mod_php.conf file points to /lib/httpd/modules/libphp5.so while the actual module is in /usr/lib/httpd/modules/libphp5.so ... I did suspect that perhaps since the serverroot has been defined as /usr, MAYBE it would prefix it, but it didnt ... Gonna go change the path myself now to see if it works. I havent touched any of the other lines in the conf files!

BAH! the system died when I hit POST! lasted 16 minutes! Tried the other drivers, nothing below 2.8.1 would even LOAD KDE! back on 2.8.1 now, and firefox somehow saved even the post I was typing, so thats good!

oh yes, php now works, after changing the path in mod_php.conf!!!

did a new kernel compile to enable rivafb support, thought maybe THAT would help ... apparently it had SOME effect, booting up the new image gave me a MUCH lower resolution bootup console (still FB, but with a single tux logo instead of 2, and resolution so low that it seemed to be the 'normal' console and not FB) ... Weirdly, the new kernel ends with a kernel panic!!! Says 'unable to mount root fs on unknown block' blah blah ...

Now, logic would immediately tell you that I buggered the kernel compile and messed up the filesystems section ... unfortunately, the new kernel boots up with the ONBOARD graphics just fine, though X wont work on that because I removed all the intel drivers, leaving only nvidia riva support! The minute the TNT2 is inserted, I have filesystem errors!!! What on earth is the connection between the AGP and FS?!?!

booted the stock kernel yet again, this time did startx, waited for KDE to load, and left the room. some 90 minutes later, the system is still running! Disabled all the fancy stuff in KDE and opened Seamonkey ... So far, so good ... Both firefox and konqueror led to a freeze, but I have a feeling that a common factor in EACH of those cases was that the freeze happened JUST as I moved the mouse over a button, like the post button on this forum, or whatever else similar entity!

Im hoping that its not going to happen again ... One possibility being that the fancy stuff was creating a problem, perhaps the system was trying to maybe look for a tooltip or something? For example I got some weird 'ksnapshot' thing popping up a couple times when I opened Seamonkey, so there IS something running thats looking at where my mouse is pointing!

Both the TNT2 card as well as the 6600GT card now no longer work on their original systems!!! Leads me to believe that the motherboard on this system is faulty!

In anycase, dumped that machine an installed Slack 13 on another machine, nForce2 mobo with integrated graphics, due to my 6600GT being MURDERED by that psycho system!!!

Hope this works ... Thanks for all the help ...