I mean seriously, a few minutes of quality time spent with Google shows many, many low cost server options.
And almost all of them are worthless unless you already know exactly what you want. Hardware changes so fast that sometimes it's hard to know what the good gear is this month.
I'm replacing a dying server, and for various reasons I'm getting a Dell, probably the PowerEdge 840. My questions:
AMD or Intel? It seems like the ball's back in Intel's court these days, but I don't track hardware news so closely anymore.
Pentium E2180 @2.0GHz (free), Core 2 Duo @2.2GHz ($50), or dual core Xeon at 1.86GHz ($100)? Cycles aren't everything, but I'm guessing that the Core 2 Duo at 18% higher clock speed ought to be the sweet spot.
For RAM: 1GBx2 or 512MBx4? In some systems, more sticks == more interleaving == faster. In others, more sticks == more latency. What's the current thinking?
To those who would tell me (and this story's poster) to Google it: I'd rather get today's recommendations from an interactive forum than try to find a website with the same information from the last year or so. Besides, what geek doesn't want to talk about hardware?
They know they have to address each of them before setting the flag on everything, all the time.
How are you going to address MythTV? No European maintainer is going to deliberately cripple their software for the benefit of NBC and their ilk, and the kind of person who'd install MythTV is the sort that won't mind downloading from videoproject.no instead of videoproject.us.
Since TV is of little value to begin with, analog with no possibility of DRM seems to me to be the perfect value choice. (I certainly could not justify spending more for my TV than I do for my computer monitor, which I spend way more time in front of)
Even better, how many people who were out of the house for American Gladiator are about to be introduced to the world of piracy and bit torrent because of the broadcast flag?
Thanks for the explanation. The ones I'd read before today weren't very exciting, like saying "in this language, you can subtract two numbers!" when they're really talking about distance calculations in GIS functions.
I wonder what it'd take to add new non-RDBMS backends to something like SQLAlchemy?
I used to be a userland purist, but let's face it, back when all we had were 133Mhz Pentiums, fast is good.
I was a junior sysadmin at an ISP in the mid-late 90's, and I remember those days well.:-) We still used Apache for everything, though. We worked around some performance issues by running multiple instances, bound to different IPs, on the same machine. One would host heavyweight processes, like mod_perl, CGI scripts, and PHP 2. Another had an extremely minimal config and it did nothing but serve static files.
By the way, that's still a pretty reasonable setup for performance-crunched machines. Why spend your resources serving favicon.ico from the same fat processes as Wordpress? The same logic holds for moving image files out of Zope and into a regular filesystem.
I would like to avoid ever hearing about or seeing child porn
Don't look for it. I've never, ever, not even once, seen anything resembling child porn in a set of search results.
and would not like my children to have access to easy recipes for explosives and drugs.
Get a filter. Better yet, do your job and teach your kids what's important to you and why. You know, those filters probably won't be around when they get to college.
You can use the same LINQ syntax to deal with data from all kind of data sources, that's what it is all about.
All the usernames on a Unix system:
print [line.split(':')[0] for line in file('/etc/passwd')]
Dates from an SQL table:
sth.execute('select invdte from invoice where invid=%(invid)s', {'invid': 1000090340}) print [row[0] for row in sth]
Search Google for "list comprehensions" and print the text of every "<a href" tag on the page:
import urllib2 import BeautifulSoup
agent = 'Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1;.NET CLR 1.1.4322;.NET CLR 2.0.50727)' url = 'http://www.google.com/search?q=list+comprehensions' google = urllib2.Request(url, headers={'User-Agent': agent}) soup = BeautifulSoup.BeautifulSoup(urllib2.urlopen(google).read()) print [link.contents for link in soup.findAll('a')]
Basically, anything Python can loop across works inside a list comprehension. It's a basic construct of the language.
And where is this mythical utopia where land has never violently changed hands? They won't let you own land in Antarctica, and the North Pole is currently disputed.
It doesn't do much good to transfer your new keys over a channel encrypted with your old, weak key. If someone can guess the old key, then they have the new key, too.
Nope. You're uploading your public key to the remote server, so the only issue is verifying the integrity of that key, eg making sure that a man-in-the-middle attack using your old public key didn't upload the attacker's own key. That example is why it's critically important to remove your old, compromised key from ~/.ssh/authorized_keys leaving only the new one in place.
MP3s in the incoming folder? "Charter put them there."
Child porn in the cache? "Charter put it there."
Nuclear weapon plans in email? "Charter sent it."
Seriously, WTF are they thinking? Do they really want to be named as co-defendants in every criminal or civil case brought against their customers? Because if they modified my incoming data and I was later called in to account for anything, you can bet my first line of defense would be to blame it on them.
Assuming you ship a sufficiently strong random number generator with your software, why even bother with some non-portable system dependent feature like/dev/random?
The one thing that comes to mind there is a hardware entropy source./dev/random might have access to it whereas a userspace program might not. In that case, the portable version might be "good enough", but the native version might be even better. Agreed on the rest of what you said, though.
Why does *everyone* have to get fancy with teh random number generators!?! Why not just use/dev/random and stop the stupid games with reinventing the wheel?
I'm guessing it's because/dev/random isn't good on every system where OpenSS{L,H} runs so they wrote a portable version that's acceptably decent everywhere.
Speaking of which, is this same code (minus the Debian "fixes") present in the OpenBSD-native version of OpenSSL as well, or is it only in the portable version? Not that it should matter much, but I'm wondering if OpenBSD trusts their own/dev/random.
Once the update is applied, weak user keys will be automatically rejected where possible (though they cannot be detected in all cases). If you are using such keys for user authentication, they will immediately stop working and will need to be replaced (see step 3).
The GP poster said the same thing, but this is for the benefit of other readers who were skeptical that any such policy was in place.
So, basically, once you upgrade, you'll have no apparent way to access your other machines [1] to upload your new key. That's just spiffy!
No. "The" whites never were. "Some" whites were. That's not just semantic nitpicking, but a very important difference.
Imagine that I had said that "the Indians are lazy alcoholics". That casts a pretty wide net, doesn't it? Some Indians (and whites and blacks and purples) are lazy alcoholics, but my words just implied that all are. Well, some whites were unremorseful genocides, but you can't generalize that to cover every European descendant.
I'm actually pretty thick-skinned and don't get insulted easily. If you walked into my office and said "hey, paleface", I'd laugh and we'd go eat lunch. Still, what you originally said was pretty offensive to the vast majority of us "whites" who had nothing to do with what happened to your people. It sucks, I feel for you, and understand why you might distrust us, but that doesn't change the fact that it wasn't me or my family who did it.
The "whites" were Europeans that came to the Americas, primarily Spanish, French, British, Dutch, etc etc. They did things like hand out small pox blankets.
Wow! Since my ancestors did none of that, I guess I'm not white.
The one feature you've described that might be useful is a shortcut for getting to the documentation -- because we really would need a lot of documentation here. But that's not worth learning Emacs for, when I already have a keystroke to take me to my browser, where the Rails documentation is, and search "methods" for "has_many" -- which is probably already up anyway.
Well, the one advantage there is that it opens it inside Emacs, so you can copy-and-paste code samples without moving your hands. To each his own; it just works well for me.
Anyway, here's a screencast showing someone using Emacs with Ruby. I don't know Ruby enough to know if this is cool or pointless, but you're probably in a better-position to judge it.
And finally, just a nit -- meta is often mapped to alt, right? Meaning that meta-tab means alt-tab, which usually means something quite different in most window managers.
That depends. I have it mapped to the Windows key on one keyboard, but escape-foo is exactly equal to metakey-foo in Emacs, so you can always get to those functions without hitting alt-tab. At any rate, you can remap any keybindings you want - that's just the default.
Slashdot Mirror
And almost all of them are worthless unless you already know exactly what you want. Hardware changes so fast that sometimes it's hard to know what the good gear is this month.
I'm replacing a dying server, and for various reasons I'm getting a Dell, probably the PowerEdge 840. My questions:
To those who would tell me (and this story's poster) to Google it: I'd rather get today's recommendations from an interactive forum than try to find a website with the same information from the last year or so. Besides, what geek doesn't want to talk about hardware?
In general, I don't like emoticons. What Shakespeare did not write:
I'm clearly not The Bard, but it's a good goal to shoot for.
How are you going to address MythTV? No European maintainer is going to deliberately cripple their software for the benefit of NBC and their ilk, and the kind of person who'd install MythTV is the sort that won't mind downloading from videoproject.no instead of videoproject.us.
There are quite a few people who agree with you.
Me, to friends and family from now on:
"Vista? Only pirates use that."
Thanks for the explanation. The ones I'd read before today weren't very exciting, like saying "in this language, you can subtract two numbers!" when they're really talking about distance calculations in GIS functions.
I wonder what it'd take to add new non-RDBMS backends to something like SQLAlchemy?
I was a junior sysadmin at an ISP in the mid-late 90's, and I remember those days well. :-) We still used Apache for everything, though. We worked around some performance issues by running multiple instances, bound to different IPs, on the same machine. One would host heavyweight processes, like mod_perl, CGI scripts, and PHP 2. Another had an extremely minimal config and it did nothing but serve static files.
By the way, that's still a pretty reasonable setup for performance-crunched machines. Why spend your resources serving favicon.ico from the same fat processes as Wordpress? The same logic holds for moving image files out of Zope and into a regular filesystem.
I guess you cannot appreciate humor.
Like a web server?
Fixed that for you.
You must be new here.
From the government? None.
I would like to avoid ever hearing about or seeing child pornDon't look for it. I've never, ever, not even once, seen anything resembling child porn in a set of search results.
and would not like my children to have access to easy recipes for explosives and drugs.Get a filter. Better yet, do your job and teach your kids what's important to you and why. You know, those filters probably won't be around when they get to college.
All the usernames on a Unix system:
Dates from an SQL table:
Search Google for "list comprehensions" and print the text of every "<a href" tag on the page:
Basically, anything Python can loop across works inside a list comprehension. It's a basic construct of the language.
And where is this mythical utopia where land has never violently changed hands? They won't let you own land in Antarctica, and the North Pole is currently disputed.
Nope. You're uploading your public key to the remote server, so the only issue is verifying the integrity of that key, eg making sure that a man-in-the-middle attack using your old public key didn't upload the attacker's own key. That example is why it's critically important to remove your old, compromised key from ~/.ssh/authorized_keys leaving only the new one in place.
Oops! My bad. You're right, of course.
MP3s in the incoming folder? "Charter put them there."
Child porn in the cache? "Charter put it there."
Nuclear weapon plans in email? "Charter sent it."
Seriously, WTF are they thinking? Do they really want to be named as co-defendants in every criminal or civil case brought against their customers? Because if they modified my incoming data and I was later called in to account for anything, you can bet my first line of defense would be to blame it on them.
The one thing that comes to mind there is a hardware entropy source. /dev/random might have access to it whereas a userspace program might not. In that case, the portable version might be "good enough", but the native version might be even better. Agreed on the rest of what you said, though.
I'm guessing it's because /dev/random isn't good on every system where OpenSS{L,H} runs so they wrote a portable version that's acceptably decent everywhere.
Speaking of which, is this same code (minus the Debian "fixes") present in the OpenBSD-native version of OpenSSL as well, or is it only in the portable version? Not that it should matter much, but I'm wondering if OpenBSD trusts their own /dev/random.
Especially when they won't work anymore:
The GP poster said the same thing, but this is for the benefit of other readers who were skeptical that any such policy was in place.
So, basically, once you upgrade, you'll have no apparent way to access your other machines [1] to upload your new key. That's just spiffy!
[1] Uninstall openssh-blacklist first.
were Past tense amigo.
No. "The" whites never were. "Some" whites were. That's not just semantic nitpicking, but a very important difference.
Imagine that I had said that "the Indians are lazy alcoholics". That casts a pretty wide net, doesn't it? Some Indians (and whites and blacks and purples) are lazy alcoholics, but my words just implied that all are. Well, some whites were unremorseful genocides, but you can't generalize that to cover every European descendant.
I'm actually pretty thick-skinned and don't get insulted easily. If you walked into my office and said "hey, paleface", I'd laugh and we'd go eat lunch. Still, what you originally said was pretty offensive to the vast majority of us "whites" who had nothing to do with what happened to your people. It sucks, I feel for you, and understand why you might distrust us, but that doesn't change the fact that it wasn't me or my family who did it.
Wow! Since my ancestors did none of that, I guess I'm not white.
Give it a rest, you racist jerk.
Umm, that was exactly my point: that visibility and openness are orthogonal.
Well, the one advantage there is that it opens it inside Emacs, so you can copy-and-paste code samples without moving your hands. To each his own; it just works well for me.
Anyway, here's a screencast showing someone using Emacs with Ruby. I don't know Ruby enough to know if this is cool or pointless, but you're probably in a better-position to judge it.
And finally, just a nit -- meta is often mapped to alt, right? Meaning that meta-tab means alt-tab, which usually means something quite different in most window managers.That depends. I have it mapped to the Windows key on one keyboard, but escape-foo is exactly equal to metakey-foo in Emacs, so you can always get to those functions without hitting alt-tab. At any rate, you can remap any keybindings you want - that's just the default.