Apache + Extras, need install advice
I wanna set up a web server w/ Debian, and I wanted to get some quick advice about that packages to grab and install. Basically, I want Apache, with SSL, PHP, and MySQL support. Also, I would like to have MySQL (obviously), and SSH (for secure access). Not really much else I want installed right now, just that, a secure, full featured web server. Can anyone point me to the exact packages? I noticed browsing the ftp directories that most of the stuff is there, but I notice some versions of apache have like one feature but not the others... And I would like to do it out of recent binaries for x86 rather than build it from source (just to save time). And, in addition to a list of the specific packages I would want to grab, any advice as to the specific places to grab them (which mirror for fast access in mid-west USA, and which directories if you happen to know), and which specific order to install them... I'm still digging, it shouldn't be all that hard, but I figure someone has probably done exactly this recently and might have a bit of advice. Thanks, Rob
Packaging Software
Hi, Can one of the Debian developers (or anyone willing to help) please contact Herng-Jeng Jou at <[EMAIL PROTECTED]> about packaging. It is my understanding that there was an intent to package some of the software he has organized at SAL (Scientific Applications for LINUX at http://SAL.KachinaTech.COM/). He is interested in helping organize, and it should be very beneficial to the LINUX community if it happens. He needs help with the task, and anyone willing to lend a hand in the work would be greatly appreciated. I understand this is a huge task that needs discussion first, but Herng-Jeng Jou would like to be contacted soon just to find out the potential reality of approaching this huge task, and what ideas are being put forward at this point. Herng-Jeng Jou wrote: > > Yes, we really need to centralize the packaging stuff. > Even some non-GPL, but free or public-domain, software, should also be > packaged, like some numerical software package (SLATEC, ODEPACK, eg) in > netlib. As SAL covers quite a wide area of applications, it might be good > idea to have several section leaders help organizing (and testing) the > packaging. > Whom should I contact regarding to their plan of Debian packaging? > Personally, I don't have a strong preference toward which packaging > schemes, but a unified way is certainly better than multiple ways. > > Jou -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
IP_Masq and Modem Help Needed
Hi, I just installed Debian by floppy on an old 386SX20 that I plan to make the gateway to my home LAN. (right now my gateway is a P60 that dual boots, so it's a pain in the butt for others in the house if it is in the wrong OS ;-) Anyhow, I used the setup app "pppconfig" to get everything configured, that's fine ;-) it connects ok. I have an ethernet card configured for the box on my home LAN, and it sees all the other boxes fine (can telnet in and out and stuff). So, that's good. The "pon" thing works fine, it connects when I run it. But that's as far as I have gotten. So, the stuff I need to figure out how to do now are the following: 1) get pon to come run from the time the box boots, and redial/reconnect if it looses carrier or get's a busy signal, etc... If this box is on, I want the modem connected. Not sure what to do here, anyone got a script or two I could use, and tell me where they go? 2) change the default gateway in this box to be ppp0 instead of eth0 (I routed it through my current LAN and other gateway to grab a couple packages) Not sure where this is exactly, what should I be looking at/for? 3) Stick the following in some rc.d somewhere to run at boot time: echo "ip_masq 192.128.1.4" echo "1" > /proc/sys/net/ipv4/ip_forward /sbin/depmod -a /sbin/modprobe ip_masq_ftp.o /sbin/modprobe ip_masq_raudio.o /sbin/modprobe ip_masq_irc.o /sbin/ipfwadm -F -p deny /sbin/ipfwadm -F -a m -S 192.168.1.0/24 -D 0.0.0.0/0 /sbin/ifconfig eth0 192.168.1.4 /sbin/route add -net 192.168.1.0 /sbin/ipfwadm -A in -i -S 0.0.0.0/0 /sbin/ipfwadm -A out -i -D 0.0.0.0/0 But where should that go? the rc.d stuff looks a little different in Debian that what I am use to. I think that's it.. After that I should be able to set the default gateway on all my boxes over from 192.128.1.2 to 192.138.1.4 and be all set... Any help greatly appreciated! ;-) -- "Robert W. Current" <[EMAIL PROTECTED]> - email http://chem20.chem.und.nodak.edu - work stuff http://www.current.nu- personal web site http://freshmeat.net - editorial coordinator "Hey mister, turn it on, turn it up, and turn me loose." - Dwight Yoakam
Re: Desktop normalization
On Mon, 23 Nov 1998, Marcin Krol wrote: > Probably E and GNUStep are. However, it is not important which desktop is > most popular *right now*. KDE would be very important even if it were not > very ergonomic or aesthetic. It's NOT. KDE is ugly as sin. Following Motif'ish styling clues to create an "environment" from which users get the impression of running a "blocky, clunky, slow" system. Even some of KDE's biggest supporters will admit that it's "bloated/slow" and the styling is not for everyone. If LINUX were to consider KDE it's base, I sware to god, I will go back to using IRIX. I agree with Alan, and would even go so far as to say, a file somewhere placed which included such things as: NAME Large Icon Small Icon Command Line MAIN-- Netscape netscape.xpm netscape-mini.xpm /usr/local/netscape/netscape EMACSemacs.xpmemacs-mini.xpm/usr/bin/emacs SUBMENU1- etc.. Now, little shit like that would be a rocking idea if standardized, and slowly all existing windowmanagers could evolve to read the standard menu structure that was simple, easy to edit, and be universally read in the end. But, beyond that, the Window Manager "race" is something that is a strength of GNU software in general, and to pick one before any of them are mature (with the exception of fvwm and maybe *step), would be a big misake. X itself has a ways to go, like it or not, user interface is a very personal thing, a rapidly developing thing, and something that "isn't there yet." If one UI was for everyone, people would have never bought Macs, If UI mattered to evryone, no one would have ran UNIX over the last 20 years. Starting to lay out some X standards to which all WindowManagers could start to conform is a nobal idea. But, just how much do you want to have a LSB? I mean, it's going to hard enough to get the base down, and keep it maintained (as libs versions get newer and basic applications get better). CDE as the standard, and how that all came about could have killed all of UNIX, let's not do that... Maybe if you feel strongly about it, work on/with something to do with a "XSB" where X is the focus, not Linux. Believe it or not, Linux has a large user base who run "headless" boxes, and just don't care about X at all. I dunno, I am going to shut up now. No wait. WINDOWMAKER RULES!!! KDE MUST DIE! Ok, done now. (^^But think, that is what emotions your going to envoke in millions of people if you choose to pick and push some standard X). Out... Rob C.
