OT: File Server at home
Guest
Posts: n/a
Re: OT: File Server at home
Jim85CJ proclaimed:
> FreeBSD is "linux" based on the Berkley kernel; Redhat is based on the
> System V kernel.
Neither is based on SVR4... Solaris, HockeypUX, Irix, etc. are 64 bit
variants of SVR4.
FreeBSD isn't based on Linux whatsoever. It would be a neat trick if
it were since FreeBSD predated Linux by a decade or so. FreeBSD is
derived from the 4.4 Berkeley Systems Unix, with full BSD unix style
server support for a number of different CPU architectures.
See http://www.freebsd.org/features.html
Redhat is a Linux based operating system, not unix.
> FreeBSD is "linux" based on the Berkley kernel; Redhat is based on the
> System V kernel.
Neither is based on SVR4... Solaris, HockeypUX, Irix, etc. are 64 bit
variants of SVR4.
FreeBSD isn't based on Linux whatsoever. It would be a neat trick if
it were since FreeBSD predated Linux by a decade or so. FreeBSD is
derived from the 4.4 Berkeley Systems Unix, with full BSD unix style
server support for a number of different CPU architectures.
See http://www.freebsd.org/features.html
Redhat is a Linux based operating system, not unix.
Guest
Posts: n/a
Re: OT: File Server at home
Jim85CJ proclaimed:
> i was close... i hate linux personally... bunch of free crap duct-taped
> together. Give me solaris, hp-ux or even AIX any day.
>
Linux works--and is fairly easy to imbed along with free journaling
file systems, high availability clustering, realtime support, etc.
For a non-geek, much easier to install and bring up than Solaris,
HockeypUX, AIX, Irix, DC/OSx, Sinix, etc.
> i was close... i hate linux personally... bunch of free crap duct-taped
> together. Give me solaris, hp-ux or even AIX any day.
>
Linux works--and is fairly easy to imbed along with free journaling
file systems, high availability clustering, realtime support, etc.
For a non-geek, much easier to install and bring up than Solaris,
HockeypUX, AIX, Irix, DC/OSx, Sinix, etc.
Guest
Posts: n/a
Re: OT: File Server at home
Jim85CJ proclaimed:
> i was close... i hate linux personally... bunch of free crap duct-taped
> together. Give me solaris, hp-ux or even AIX any day.
>
Linux works--and is fairly easy to imbed along with free journaling
file systems, high availability clustering, realtime support, etc.
For a non-geek, much easier to install and bring up than Solaris,
HockeypUX, AIX, Irix, DC/OSx, Sinix, etc.
> i was close... i hate linux personally... bunch of free crap duct-taped
> together. Give me solaris, hp-ux or even AIX any day.
>
Linux works--and is fairly easy to imbed along with free journaling
file systems, high availability clustering, realtime support, etc.
For a non-geek, much easier to install and bring up than Solaris,
HockeypUX, AIX, Irix, DC/OSx, Sinix, etc.
Guest
Posts: n/a
Re: OT: File Server at home
Jim85CJ proclaimed:
> i was close... i hate linux personally... bunch of free crap duct-taped
> together. Give me solaris, hp-ux or even AIX any day.
>
Linux works--and is fairly easy to imbed along with free journaling
file systems, high availability clustering, realtime support, etc.
For a non-geek, much easier to install and bring up than Solaris,
HockeypUX, AIX, Irix, DC/OSx, Sinix, etc.
> i was close... i hate linux personally... bunch of free crap duct-taped
> together. Give me solaris, hp-ux or even AIX any day.
>
Linux works--and is fairly easy to imbed along with free journaling
file systems, high availability clustering, realtime support, etc.
For a non-geek, much easier to install and bring up than Solaris,
HockeypUX, AIX, Irix, DC/OSx, Sinix, etc.
Guest
Posts: n/a
Re: OT: File Server at home
Jim85CJ proclaimed:
> i was close... i hate linux personally... bunch of free crap duct-taped
> together. Give me solaris, hp-ux or even AIX any day.
>
Linux works--and is fairly easy to imbed along with free journaling
file systems, high availability clustering, realtime support, etc.
For a non-geek, much easier to install and bring up than Solaris,
HockeypUX, AIX, Irix, DC/OSx, Sinix, etc.
> i was close... i hate linux personally... bunch of free crap duct-taped
> together. Give me solaris, hp-ux or even AIX any day.
>
Linux works--and is fairly easy to imbed along with free journaling
file systems, high availability clustering, realtime support, etc.
For a non-geek, much easier to install and bring up than Solaris,
HockeypUX, AIX, Irix, DC/OSx, Sinix, etc.
Guest
Posts: n/a
Re: OT: File Server at home
hi,
im not sure if any of this has been addressed already because i havent read the
entire thread, but perhaps i can help a little here.
im currently running a half dozen websites, an IRC chat server, my own email
server, and a file server out of my home on my qwest 1.5/896 DSL backbone.
qwest has the most awesome TOS ive ever read so if theyre available in your
area i highly recommend them. bottom line, they dont care _what_ you do with
your bandwidth so long as you arent violating any laws. they dont care if you
run websites or file servers from your home. they dont care if you run
commercial sites from your home. just stay within the law and pay your bill
and youll never hear from qwest on anything you do.
ive set up a small tutorial that explains the process of setting up a server to
operate from your home. this is done using a Windows 2000 Server server and a
linksys befsr41 home DSL/Cable router/switch. ive since upgraded to their
wireless setup but its all basically the same. see
http://7slotgrille.com/webtech/router for that tutorial. if you need further
help please feel free to contact me privately.
you _could_ have local loopback issues depending upon the cable/dsl modem
issued by your broadband provider. some modems are able to pass internal
requests and others arent. basically that means that everyone outside your LAN
will be able to access your servers but you wont. if this happens, a simple
HOSTS file edit (in notepad) will fix it. for example, my crappy DLS modem
does not support local loopback. for me to access my sites from within my LAN
i must add this line to my HOSTS file:
192.168.1.18 7slotgrille.com
that tells the computer im using to resolve to my local IP instead of through
DNS. the only downside to this is that youll never know if your server access
is down due to DNS issues but thats rare anyway.
btw, will you be using DNS or direct IP access?
im not sure if any of this has been addressed already because i havent read the
entire thread, but perhaps i can help a little here.
im currently running a half dozen websites, an IRC chat server, my own email
server, and a file server out of my home on my qwest 1.5/896 DSL backbone.
qwest has the most awesome TOS ive ever read so if theyre available in your
area i highly recommend them. bottom line, they dont care _what_ you do with
your bandwidth so long as you arent violating any laws. they dont care if you
run websites or file servers from your home. they dont care if you run
commercial sites from your home. just stay within the law and pay your bill
and youll never hear from qwest on anything you do.
ive set up a small tutorial that explains the process of setting up a server to
operate from your home. this is done using a Windows 2000 Server server and a
linksys befsr41 home DSL/Cable router/switch. ive since upgraded to their
wireless setup but its all basically the same. see
http://7slotgrille.com/webtech/router for that tutorial. if you need further
help please feel free to contact me privately.
you _could_ have local loopback issues depending upon the cable/dsl modem
issued by your broadband provider. some modems are able to pass internal
requests and others arent. basically that means that everyone outside your LAN
will be able to access your servers but you wont. if this happens, a simple
HOSTS file edit (in notepad) will fix it. for example, my crappy DLS modem
does not support local loopback. for me to access my sites from within my LAN
i must add this line to my HOSTS file:
192.168.1.18 7slotgrille.com
that tells the computer im using to resolve to my local IP instead of through
DNS. the only downside to this is that youll never know if your server access
is down due to DNS issues but thats rare anyway.
btw, will you be using DNS or direct IP access?
Guest
Posts: n/a
Re: OT: File Server at home
hi,
im not sure if any of this has been addressed already because i havent read the
entire thread, but perhaps i can help a little here.
im currently running a half dozen websites, an IRC chat server, my own email
server, and a file server out of my home on my qwest 1.5/896 DSL backbone.
qwest has the most awesome TOS ive ever read so if theyre available in your
area i highly recommend them. bottom line, they dont care _what_ you do with
your bandwidth so long as you arent violating any laws. they dont care if you
run websites or file servers from your home. they dont care if you run
commercial sites from your home. just stay within the law and pay your bill
and youll never hear from qwest on anything you do.
ive set up a small tutorial that explains the process of setting up a server to
operate from your home. this is done using a Windows 2000 Server server and a
linksys befsr41 home DSL/Cable router/switch. ive since upgraded to their
wireless setup but its all basically the same. see
http://7slotgrille.com/webtech/router for that tutorial. if you need further
help please feel free to contact me privately.
you _could_ have local loopback issues depending upon the cable/dsl modem
issued by your broadband provider. some modems are able to pass internal
requests and others arent. basically that means that everyone outside your LAN
will be able to access your servers but you wont. if this happens, a simple
HOSTS file edit (in notepad) will fix it. for example, my crappy DLS modem
does not support local loopback. for me to access my sites from within my LAN
i must add this line to my HOSTS file:
192.168.1.18 7slotgrille.com
that tells the computer im using to resolve to my local IP instead of through
DNS. the only downside to this is that youll never know if your server access
is down due to DNS issues but thats rare anyway.
btw, will you be using DNS or direct IP access?
im not sure if any of this has been addressed already because i havent read the
entire thread, but perhaps i can help a little here.
im currently running a half dozen websites, an IRC chat server, my own email
server, and a file server out of my home on my qwest 1.5/896 DSL backbone.
qwest has the most awesome TOS ive ever read so if theyre available in your
area i highly recommend them. bottom line, they dont care _what_ you do with
your bandwidth so long as you arent violating any laws. they dont care if you
run websites or file servers from your home. they dont care if you run
commercial sites from your home. just stay within the law and pay your bill
and youll never hear from qwest on anything you do.
ive set up a small tutorial that explains the process of setting up a server to
operate from your home. this is done using a Windows 2000 Server server and a
linksys befsr41 home DSL/Cable router/switch. ive since upgraded to their
wireless setup but its all basically the same. see
http://7slotgrille.com/webtech/router for that tutorial. if you need further
help please feel free to contact me privately.
you _could_ have local loopback issues depending upon the cable/dsl modem
issued by your broadband provider. some modems are able to pass internal
requests and others arent. basically that means that everyone outside your LAN
will be able to access your servers but you wont. if this happens, a simple
HOSTS file edit (in notepad) will fix it. for example, my crappy DLS modem
does not support local loopback. for me to access my sites from within my LAN
i must add this line to my HOSTS file:
192.168.1.18 7slotgrille.com
that tells the computer im using to resolve to my local IP instead of through
DNS. the only downside to this is that youll never know if your server access
is down due to DNS issues but thats rare anyway.
btw, will you be using DNS or direct IP access?
Guest
Posts: n/a
Re: OT: File Server at home
hi,
im not sure if any of this has been addressed already because i havent read the
entire thread, but perhaps i can help a little here.
im currently running a half dozen websites, an IRC chat server, my own email
server, and a file server out of my home on my qwest 1.5/896 DSL backbone.
qwest has the most awesome TOS ive ever read so if theyre available in your
area i highly recommend them. bottom line, they dont care _what_ you do with
your bandwidth so long as you arent violating any laws. they dont care if you
run websites or file servers from your home. they dont care if you run
commercial sites from your home. just stay within the law and pay your bill
and youll never hear from qwest on anything you do.
ive set up a small tutorial that explains the process of setting up a server to
operate from your home. this is done using a Windows 2000 Server server and a
linksys befsr41 home DSL/Cable router/switch. ive since upgraded to their
wireless setup but its all basically the same. see
http://7slotgrille.com/webtech/router for that tutorial. if you need further
help please feel free to contact me privately.
you _could_ have local loopback issues depending upon the cable/dsl modem
issued by your broadband provider. some modems are able to pass internal
requests and others arent. basically that means that everyone outside your LAN
will be able to access your servers but you wont. if this happens, a simple
HOSTS file edit (in notepad) will fix it. for example, my crappy DLS modem
does not support local loopback. for me to access my sites from within my LAN
i must add this line to my HOSTS file:
192.168.1.18 7slotgrille.com
that tells the computer im using to resolve to my local IP instead of through
DNS. the only downside to this is that youll never know if your server access
is down due to DNS issues but thats rare anyway.
btw, will you be using DNS or direct IP access?
im not sure if any of this has been addressed already because i havent read the
entire thread, but perhaps i can help a little here.
im currently running a half dozen websites, an IRC chat server, my own email
server, and a file server out of my home on my qwest 1.5/896 DSL backbone.
qwest has the most awesome TOS ive ever read so if theyre available in your
area i highly recommend them. bottom line, they dont care _what_ you do with
your bandwidth so long as you arent violating any laws. they dont care if you
run websites or file servers from your home. they dont care if you run
commercial sites from your home. just stay within the law and pay your bill
and youll never hear from qwest on anything you do.
ive set up a small tutorial that explains the process of setting up a server to
operate from your home. this is done using a Windows 2000 Server server and a
linksys befsr41 home DSL/Cable router/switch. ive since upgraded to their
wireless setup but its all basically the same. see
http://7slotgrille.com/webtech/router for that tutorial. if you need further
help please feel free to contact me privately.
you _could_ have local loopback issues depending upon the cable/dsl modem
issued by your broadband provider. some modems are able to pass internal
requests and others arent. basically that means that everyone outside your LAN
will be able to access your servers but you wont. if this happens, a simple
HOSTS file edit (in notepad) will fix it. for example, my crappy DLS modem
does not support local loopback. for me to access my sites from within my LAN
i must add this line to my HOSTS file:
192.168.1.18 7slotgrille.com
that tells the computer im using to resolve to my local IP instead of through
DNS. the only downside to this is that youll never know if your server access
is down due to DNS issues but thats rare anyway.
btw, will you be using DNS or direct IP access?
Guest
Posts: n/a
Re: OT: File Server at home
hi,
im not sure if any of this has been addressed already because i havent read the
entire thread, but perhaps i can help a little here.
im currently running a half dozen websites, an IRC chat server, my own email
server, and a file server out of my home on my qwest 1.5/896 DSL backbone.
qwest has the most awesome TOS ive ever read so if theyre available in your
area i highly recommend them. bottom line, they dont care _what_ you do with
your bandwidth so long as you arent violating any laws. they dont care if you
run websites or file servers from your home. they dont care if you run
commercial sites from your home. just stay within the law and pay your bill
and youll never hear from qwest on anything you do.
ive set up a small tutorial that explains the process of setting up a server to
operate from your home. this is done using a Windows 2000 Server server and a
linksys befsr41 home DSL/Cable router/switch. ive since upgraded to their
wireless setup but its all basically the same. see
http://7slotgrille.com/webtech/router for that tutorial. if you need further
help please feel free to contact me privately.
you _could_ have local loopback issues depending upon the cable/dsl modem
issued by your broadband provider. some modems are able to pass internal
requests and others arent. basically that means that everyone outside your LAN
will be able to access your servers but you wont. if this happens, a simple
HOSTS file edit (in notepad) will fix it. for example, my crappy DLS modem
does not support local loopback. for me to access my sites from within my LAN
i must add this line to my HOSTS file:
192.168.1.18 7slotgrille.com
that tells the computer im using to resolve to my local IP instead of through
DNS. the only downside to this is that youll never know if your server access
is down due to DNS issues but thats rare anyway.
btw, will you be using DNS or direct IP access?
im not sure if any of this has been addressed already because i havent read the
entire thread, but perhaps i can help a little here.
im currently running a half dozen websites, an IRC chat server, my own email
server, and a file server out of my home on my qwest 1.5/896 DSL backbone.
qwest has the most awesome TOS ive ever read so if theyre available in your
area i highly recommend them. bottom line, they dont care _what_ you do with
your bandwidth so long as you arent violating any laws. they dont care if you
run websites or file servers from your home. they dont care if you run
commercial sites from your home. just stay within the law and pay your bill
and youll never hear from qwest on anything you do.
ive set up a small tutorial that explains the process of setting up a server to
operate from your home. this is done using a Windows 2000 Server server and a
linksys befsr41 home DSL/Cable router/switch. ive since upgraded to their
wireless setup but its all basically the same. see
http://7slotgrille.com/webtech/router for that tutorial. if you need further
help please feel free to contact me privately.
you _could_ have local loopback issues depending upon the cable/dsl modem
issued by your broadband provider. some modems are able to pass internal
requests and others arent. basically that means that everyone outside your LAN
will be able to access your servers but you wont. if this happens, a simple
HOSTS file edit (in notepad) will fix it. for example, my crappy DLS modem
does not support local loopback. for me to access my sites from within my LAN
i must add this line to my HOSTS file:
192.168.1.18 7slotgrille.com
that tells the computer im using to resolve to my local IP instead of through
DNS. the only downside to this is that youll never know if your server access
is down due to DNS issues but thats rare anyway.
btw, will you be using DNS or direct IP access?
Guest
Posts: n/a
Re: OT: File Server at home
Jim85CJ proclaimed:
> "Linux is certainly not ducked taped togrther"
> I admit it is much better than it was in the early 90s but it still is
> nowhere near solaris/aix/hp-ux. As for Linux vs Windows? No
> comparison, Linux kicks windows ***; that's not saying much.
For ease of use even in loosely coupled or massively parallel clusters
Linux can outscale pretty much everything except AIX. Personally I
prefer Solaris as well but to use it effectively you need some serious
VM internals, IO Subsystem, and Solaris networking background.
> "Linux is certainly not ducked taped togrther"
> I admit it is much better than it was in the early 90s but it still is
> nowhere near solaris/aix/hp-ux. As for Linux vs Windows? No
> comparison, Linux kicks windows ***; that's not saying much.
For ease of use even in loosely coupled or massively parallel clusters
Linux can outscale pretty much everything except AIX. Personally I
prefer Solaris as well but to use it effectively you need some serious
VM internals, IO Subsystem, and Solaris networking background.
