Log in

No account? Create an account
Linux Community's Journal
[Most Recent Entries] [Calendar View] [Friends View]

Monday, November 4th, 2002

Time Event
I've been thinking of switching to Linux for a while, basically because I don't want to be running Windows anymore. I'm really unfamiliar with the "inner workings" of my computer, and although I really want to switch, I'm scared because I've been using Windows since I was eleven. Is there a way I can kind of test out the OS before I make a complete switch? I don't know anyone with Linux who lives in my country even, and I'd really just like to see for myself if it's worth it. So, if anyone could help, I'd really appreciate it.
hi all...i'm thinking heavily about switching to linux.
i'm not quite sure how easy it would be, but reading up on things, it doesn't seem to be that hard.
i'm gathering you can set up your system your own way.
but i do have a question...
i have a website. i want to have my secondary computer be it's server.
i want to know how would i go about setting that computer up using linux (and what flavor of linux), and have it do "server things" <-- yah i know i'm not up on the lingo yet.
you could either reply here or message me at i will help you
thanks a lot

Current Mood: curious
redhat 7.3 install problem: monitor signal lost?
I can boot from the first 7.3 CD. It gets me to the welcome screen where you choose boot options. But no matter which option I choose -- graphical, lowres, no frame-buffer, noprobe, or even TEXT -- I get the same result:

The installer begins, there's a blue screen, then a message at the bottom:
"Running anaconda - please wait..."
Then the monitor signal dies. I get a black screen with flickering horizontal artifacts. The built-in controls on my monitor claim that it isn't getting a signal from the PC anymore.

I ran `linux medicheck' and the CD passed. Monitor cable has been re-plugged on both ends. Any thoughts? Also, any suggestions for other places where I could look for an answer (besides Google)? Thanks.

(Hardware: Dell Dimension XPS P133c, 96MB RAM; HP Ultra VGA 1280 monitor.)
apache behind coyote router
Here's my setup:

A Coyote Linux machine, called 'router', which is conneccted to my DSL modem and my local network in a normal fashion. Behind this reside two Debian Linux machines each running Apache, called 'inhope' (which is running Apache 1.3.26 under Debian 2.2), and 'nerdcave' (which is running the newest Apache, under Debian 3.0). Both of these computers and their respected webservers work fine from my local network.

Currently, I have my Coyote machine forward port 80 to 'inhope', and it seems to work with no qualms whatsoever and is entirely 'net accessible. I have a dyndns account set up, which seems to work fine. However, I'd like my other Debian machine's webserver to also be 'net accessible, only using a different dyndns account. The problem is that if I try forwarding my other dyndns account to my IP, I'll always get my _other_ Debian computer, since that's where Coyote forwards port 80.

What I wanted to try was something using either VirtualHosts or ProxyPass rules on my first Debian machine, so it'd just see whether or not the request is for the other machine, via the hostname in the HTTP header, and if it is, forward it. However, I'm not entirely sure how this should really be done, and although I've tried quite a few things, I haven't had any luck with it. The second dyndns account still seems to forward to my first Debian computer, which isn't what I want it to be doing.

Does anyone have any ideas as to what the easiest way to accomplish this would be?
Hi - I'm a noob and I just installed YDL 2.3 Dayton release on my iBook and I'm having some problems - like it just sits and blinks at me. Does anyone have any experience with this puppy (NPI)? I need to know if I absolutely have to have it or the boot loader on the first partition - the drive is split 7 ways to sunday. I can run it in single user mode, getting fsck to run was a beast cause I couldn't remember the syntax, but that eventually did get figured out - problem is I can't get it to boot X Windows/Gnome, whatever, and I'm wondering if I have to move things around to make it happy or if I should just ditch and reinstall - I'm not sure if it's a display problem or what (and no, I didn't write any errors down cuz it didn't give me errors, it just sat here flashing the screen). I opted for the GUI logon like a fool. gah.


<< Previous Day 2002/11/04
Next Day >>
About LiveJournal.com