sucks for you, i get 12.0/1.5 up/down at home, for around $50 a month. It is a cable modem, so I get blocked ports 25 and 80, but who cares, i'm not hosting anything from home anyways.
Just because something is supported doesn't mean it's best practice, or even good practice. Citrix is really good about supporting a lot of things. Their mentality is "you paid for our product, we'll help you get it to work as best we can." But again, that doesn't always mean it's the best way to go... or even a good way...
Citrix is a virtual computing environment. Users are given virtual workspaces on top of their own workspace. You're wanting to put two virtual workspace servers, inside of an already virtual environment. Doubling up layers of something aren't always a good thing. Think double nat'ing - yeah, you can access resources on the other side of your double nat, but it will always cause problems eventually.
I was working with someone who wanted to do this very same thing recently and the answer from both myself, and Citrix was "no, what the hell is wrong with you.":-P I was also working with a Citrix engineer about a month ago who was testing out the same very thing you are talking about (stress tested to be a production environment not just "oh yeah, it boots, connects, NEXT") and his findings were basically "yes, it is possible, is it worth it? will it continue to work well? will performance be maintained?" The answers were all no. This was tested on both 32 and 64-bit environments all with large ammounts of RAM.
I know that worms are ridiculous and all, but at least this thing won't be hammering millions of unaffected ip adresses and I don't have to see this crap hitting my snort/log files!
I've only been working in the IT field for about 1.5 years now, but in that time I have never, ever had to call Redhat support. (Everything Just Works(tm))
I have spent about 2 hours or less on the phone with Sun support.
I have spent a whopping 20+ hours alone on the phone with Microsoft support.
Unfortunately here for Microsoft they can't use the argument that it's because they have a dominating market and the ratio of support calls to them is therefore higher. Not in my client's server rooms. The ratio of the MS to "other" operating systems installed on the servers is dead near 50/50.
Yes, it's a bit of damn overkill for a home setup, but you can never be too safe.:)
-cable modem->linux 2.4 kernel router running iptables
-norton antivirus corporate edition
-Microsoft Software Update Services for the Windows boxes
-iptables for the Linux boxes
-ntop and snort for traffic monitoring
-I have a WRT54G that I don't use for routing anymore, just as a bridge. Anything that I use over wireless is done over ssh. Host connection, bank account checking, email, vpn to work, etc.
-various other utilities to monitor tcp/ip traffic
-good old fashioned obsessive tailing of logfiles along with vgrep :)
At one of my clients, there are about 9 solaris servers that run headless, but have a few applications that are X based. All of the windows servers are hooked up to a KVM, so I put cygwin on one of the windows boxes, set it up to auto-login and start the X server (prodiving you are at the console, and not thorugh terminal services) and start acceptings connections from the defined servers.
Not quite the same situation as yours, but I think if it can handle running an X server (stable, for the past several months) it should be able to handle some bash/perl scripts.
I'm sorry, but you have GOT to be kidding me. You just can't realistically find that in your price range. Sure, you can skimp out on HD space, or maybe drop the pre-installed software, but as soon as you sacrafice a brand name, you lose things like a decent warranty, and quality parts.
Slashdot Mirror
Way to kill the guy's joke. Just let him enjoy his +2 funny. :-P
sucks for you, i get 12.0/1.5 up/down at home, for around $50 a month. It is a cable modem, so I get blocked ports 25 and 80, but who cares, i'm not hosting anything from home anyways.
same reiser time, same reiser channel!
Just because something is supported doesn't mean it's best practice, or even good practice. Citrix is really good about supporting a lot of things. Their mentality is "you paid for our product, we'll help you get it to work as best we can." But again, that doesn't always mean it's the best way to go... or even a good way...
Citrix is a virtual computing environment. Users are given virtual workspaces on top of their own workspace. You're wanting to put two virtual workspace servers, inside of an already virtual environment. Doubling up layers of something aren't always a good thing. Think double nat'ing - yeah, you can access resources on the other side of your double nat, but it will always cause problems eventually.
:-P I was also working with a Citrix engineer about a month ago who was testing out the same very thing you are talking about (stress tested to be a production environment not just "oh yeah, it boots, connects, NEXT") and his findings were basically "yes, it is possible, is it worth it? will it continue to work well? will performance be maintained?" The answers were all no. This was tested on both 32 and 64-bit environments all with large ammounts of RAM.
I was working with someone who wanted to do this very same thing recently and the answer from both myself, and Citrix was "no, what the hell is wrong with you."
The WONDERFUL extensions to LDAP, DNS, DHCP, and many more? UGH
Quit being a douche bag you stupid mod, this whole article is fucking flame bait. EAT ME
I think that's what he was getting at...just give all these catch phrases the AAX... chop chop :-P
Where's my spanking? :(
14/f/cali
yeah, but it's all about looking 1337, and 2 just ain't as h4x0rish as 3 ;-)
I know that worms are ridiculous and all, but at least this thing won't be hammering millions of unaffected ip adresses and I don't have to see this crap hitting my snort/log files!
How's that sh*t for efficiency?
I've only been working in the IT field for about 1.5 years now, but in that time I have never, ever had to call Redhat support. (Everything Just Works(tm))
I have spent about 2 hours or less on the phone with Sun support.
I have spent a whopping 20+ hours alone on the phone with Microsoft support.
Unfortunately here for Microsoft they can't use the argument that it's because they have a dominating market and the ratio of support calls to them is therefore higher. Not in my client's server rooms. The ratio of the MS to "other" operating systems installed on the servers is dead near 50/50.
Just my personal experience.
Set your standards a little lower, and see how that works out for you. ;-)
Yes, it's a bit of damn overkill for a home setup, but you can never be too safe. :)
:)
-cable modem->linux 2.4 kernel router running iptables
-norton antivirus corporate edition
-Microsoft Software Update Services for the Windows boxes
-iptables for the Linux boxes
-ntop and snort for traffic monitoring
-I have a WRT54G that I don't use for routing anymore, just as a bridge. Anything that I use over wireless is done over ssh. Host connection, bank account checking, email, vpn to work, etc.
-various other utilities to monitor tcp/ip traffic
-good old fashioned obsessive tailing of logfiles along with vgrep
I have a Zaurus SL5600 with Linksys wifi card. Email me if you are interested...
I too remember this. A friend of mine showed it to me about 6 or 7 years ago. The site seems to be down, so here's a google cache:
: www.thepalace.com/+the+palace&hl=en
http://64.233.161.104/search?q=cache:m_0nMPwQS2AJ
And a link to a download page. (With linux support it seems now?)
http://practice.chatserve.com/
appending the - to the su command will create the environment as if the user had logged in directly from a login prompt.
haha, how random. I love it!
Lunix?
:)
You're obviously a BSD astroturfer.
Damn! and in 0.16 seconds!
To hell with fuzzy cable porn!
At one of my clients, there are about 9 solaris servers that run headless, but have a few applications that are X based. All of the windows servers are hooked up to a KVM, so I put cygwin on one of the windows boxes, set it up to auto-login and start the X server (prodiving you are at the console, and not thorugh terminal services) and start acceptings connections from the defined servers.
Not quite the same situation as yours, but I think if it can handle running an X server (stable, for the past several months) it should be able to handle some bash/perl scripts.
Good luck.
because of the last part of your quoted phrase:
...if you break this agreement.
My love for you is ticking bomb,
BERZERKER
Would you like some making fuck?
BERZERKER
I'm sorry, but you have GOT to be kidding me. You just can't realistically find that in your price range. Sure, you can skimp out on HD space, or maybe drop the pre-installed software, but as soon as you sacrafice a brand name, you lose things like a decent warranty, and quality parts.
Bottom line.