All,
I have several boxes kobbled together along with my web server living
happily behind my firewall. In order to get windows (IE, NETSCAP et al) to
see the sites served up on the web server I have to adjust the hosts file in
/WINDOWS/system32/drivers/etc/ telling the specific local IP address fo
On Thu, Dec 09, 2004 at 12:49:29PM -0500, jason wrote:
> All,
>
> I have several boxes kobbled together along with my web server living
> happily behind my firewall. In order to get windows (IE, NETSCAP et al) to
> see the sites served up on the web server I have to adjust the hosts file in
> /WIN
/etc/hosts
On Thu, 9 Dec 2004 12:49:29 -0500, jason <[EMAIL PROTECTED]> wrote:
> All,
>
> I have several boxes kobbled together along with my web server living
> happily behind my firewall. In order to get windows (IE, NETSCAP et al) to
> see the sites served up on the web server I have to adjus
The naming scheme on NT based machines always amuses me: I'm pretty sure
that /etc/ started out being a *nix thing, which MS then took up.
Or they could have borrowed it from their own Unix project:
http://en.wikipedia.org/wiki/Xenix
___
gnhlug-discuss
On Thu, 9 Dec 2004 12:49:29 -0500
"jason" <[EMAIL PROTECTED]> wrote:
> All,
>
> I have several boxes kobbled together along with my web server living
> happily behind my firewall. In order to get windows (IE, NETSCAP et al) to
> see the sites served up on the web server I have to adjust the hosts
Hi Jason,
Adding to Bill's good example, I usually develop on my local machine
("liberty"), having a local webserver on the same machine setup. This
way I can test stuff locally without ever moving it to the 'production'
server ("brie"), or before checking it in to CVS. Of course my real
webs
An alternative to using host files, especially if you have many machines
on your LAN you want to point to your LAN web server is to set up a name
server on one of your Linux boxes.
You can manage your name server by installing Webmin, which makes this
almost painless. Then you have to configure al
