Unfortunately for you, these new systems have a limitation on the size of the vessels in question; there is a definable limit on the smallest region that can be captured and interpolated by the scanner. This is not suitable for individuals of your - ahem - stature.
While partimage is excellent software for cloning/backing partitions at a high level, it does have its drawbacks. Specifically, it can't restore to a larger partition directly - you'd first have to restore to the same size partition and resize it (while not a big problem, it is still a hindrance for me at least). This makes it a little tricky for when your old disk fails and you want to upgrade capacity when you restore.
I live in the U.S. Yes, cost is the argument that most often wins me management support with open source apps, but it also serves as a huge eye-opener for them when they've seen what it can do (visibility, quality, responsiveness of the community, etc).
I present to you the newest incarnation of what once was the Python programming language: something.
What can you use for your rapid application development needs? something. What about handling those tricky image manipulations? Give something a try. Terrified of Mr. Bean quotes? something will lead you to a better pasture!
In my 25 years of problem solving in an IT environment, I find that something would have solved it.
Why are surrogate keys a pain in the ass for DBAs? My guess is their difficulty in high-availability or disaster-recovery scenarios. When most application frameworks create autoincrementing surrogate keys, it is tough to get them synced over to a disaster recovery site and maintain consistency. Inserting explicit values into a sequenced table in Sybase, for example, requires table-owner intervention (usually the DBA) and not just access to insert into the table. Ever had to do asynchronous, multi-master'ed data correction with lots of these keys hanging around? Didn't think so.
Surrogate keys, by definition, also replace a table's naturally identifying characteristics. This means that you'll be creating additional indexes if some natural search columns are present. With those additional indexes come additional data storage to house them. There's also the chance that the surrogate key will be used by the query optimizer anyway, sometimes resulting in horribly inefficient joins.
Memory usage: Over 300 individual memory leaks have been plugged, and a new XPCOM cycle collector completely eliminates many more. Developers are continuing to work on optimizing memory use (by releasing cached objects more quickly) and reducing fragmentation.
They are the changes mentioned here, I think. I guess the changes will be ported to MySQL 6 (if any porting needs to be done at all...who knows at this point).
Who's to say that any name is lame or not? More importantly, who cares? A cursory glance beyond whatever moniker a distribution has is really needed before a decision is made to adopt it. If you judge based on a name, you probably shouldn't be in a position to decide anyway!
If you are really worried about the name as it relates to non-geek circles, use their numbering scheme instead. Gutsy Gibbon is Ubuntu 7.10 (https://wiki.ubuntu.com/GutsyGibbon). Personally, as long as the Ubuntu guys continue to churn out an excellent product, I could not care less about the name.
I've been using my MythTV box as my primary media center for over a year and a half now. While I love to make the occasional configuration changes to meet the ever-changing needs of my family, I NEVER update unless I have a very, very good reason. Why? Because at this point I don't want a weekend troubleshooting session because I triggered incompatibilities. I guess that is just me being paranoid, though. I've never had drastic problems with Myth, but I can also attribute that to the fact that I wrote up my requirements, built the machine to them, and left it that way. No surprises!
So there are some tradeoffs when using a media distribution like KnoppMyth to build out your MythTV, but sometimes they are really blessings in disguise.
My distribution is Monkey Ballsack Linux, thank you very much. How am I suppose to gain market share in the Fortune 500 when people can't even get the name right? Geez.
Great, and I'd like to hear more...
on
A Geek On Everest
·
· Score: 3, Interesting
I liked the article, but I really wanted to hear more about the particular problems he experienced with the equipment, and what (if any) type of workaround he used to get them back into shape. In such extreme weather, he HAD to have more failures or problems other than that one hard drive.
On the other hand, he didn't go above a certain altitude, and maybe everything was fine and dandy. For that, I can think of the ads now: "ABC Corp's hard disks survived EVEREST - put them to work in your demanding data center today!"
What part of my comment demanded anything from Nvidia? They have every right to do exactly what they are doing, and I respect that. They have excellent support with their proprietary drivers, and I use them whenever I can.
I expected TFA to have some trinket of _news_. I was sadly disappointed, that's all.
I tried your command, but it gave me these problems... someone help!
apt-get new-tyres
The following packages have unmet dependencies:
new-tyres: Depends: pit-crew (>= 5.0) but it is not going to be installed
Depends: community-awareness (>=.01) but it is not going to be installed
Depends: community-donations (>=.01) but it is not going to be installed
Clarification: MySQL provides tons of services (http://mysql.com/support/). It is just that they are only for their "Enterprise" products. Of course, those are under the commercial license...
Slashdot Mirror
Unfortunately for you, these new systems have a limitation on the size of the vessels in question; there is a definable limit on the smallest region that can be captured and interpolated by the scanner. This is not suitable for individuals of your - ahem - stature.
While partimage is excellent software for cloning/backing partitions at a high level, it does have its drawbacks. Specifically, it can't restore to a larger partition directly - you'd first have to restore to the same size partition and resize it (while not a big problem, it is still a hindrance for me at least). This makes it a little tricky for when your old disk fails and you want to upgrade capacity when you restore.
Take a look at DAR for your purposes.
Don't blame him - he couldn't understand on account of the accent.
I live in the U.S. Yes, cost is the argument that most often wins me management support with open source apps, but it also serves as a huge eye-opener for them when they've seen what it can do (visibility, quality, responsiveness of the community, etc).
I just got laid last night.
My apologies, but if I'm not mistaken, you said /the/ island. You also made no mention of Taiwan or Japan.
It also doesn't take Sherlock Holmes to figure out that China isn't on an island.
I present to you the newest incarnation of what once was the Python programming language: something.
What can you use for your rapid application development needs? something. What about handling those tricky image manipulations? Give something a try. Terrified of Mr. Bean quotes? something will lead you to a better pasture!
In my 25 years of problem solving in an IT environment, I find that something would have solved it.
Why are surrogate keys a pain in the ass for DBAs? My guess is their difficulty in high-availability or disaster-recovery scenarios. When most application frameworks create autoincrementing surrogate keys, it is tough to get them synced over to a disaster recovery site and maintain consistency. Inserting explicit values into a sequenced table in Sybase, for example, requires table-owner intervention (usually the DBA) and not just access to insert into the table. Ever had to do asynchronous, multi-master'ed data correction with lots of these keys hanging around? Didn't think so.
Surrogate keys, by definition, also replace a table's naturally identifying characteristics. This means that you'll be creating additional indexes if some natural search columns are present. With those additional indexes come additional data storage to house them. There's also the chance that the surrogate key will be used by the query optimizer anyway, sometimes resulting in horribly inefficient joins.
Or you could refer him to Scilab, which is a FOSS scientific package just like MATLAB.
From the release notes:
I'm optimistic, but we'll see in time...
They are the changes mentioned here, I think. I guess the changes will be ported to MySQL 6 (if any porting needs to be done at all...who knows at this point).
I second that! The EFF could net more $s that way.
the site is slashdotted. Here is the PDF'ed version of the article.
Who's to say that any name is lame or not? More importantly, who cares? A cursory glance beyond whatever moniker a distribution has is really needed before a decision is made to adopt it. If you judge based on a name, you probably shouldn't be in a position to decide anyway!
If you are really worried about the name as it relates to non-geek circles, use their numbering scheme instead. Gutsy Gibbon is Ubuntu 7.10 (https://wiki.ubuntu.com/GutsyGibbon).
Personally, as long as the Ubuntu guys continue to churn out an excellent product, I could not care less about the name.
Probably doesn't meet all of your requirements, but it is close: http://www.monolithmc.com/features.php.
I've been using my MythTV box as my primary media center for over a year and a half now. While I love to make the occasional configuration changes to meet the ever-changing needs of my family, I NEVER update unless I have a very, very good reason. Why? Because at this point I don't want a weekend troubleshooting session because I triggered incompatibilities. I guess that is just me being paranoid, though. I've never had drastic problems with Myth, but I can also attribute that to the fact that I wrote up my requirements, built the machine to them, and left it that way. No surprises! So there are some tradeoffs when using a media distribution like KnoppMyth to build out your MythTV, but sometimes they are really blessings in disguise.
I really don't think Chuck Norris is going to go for that.
My distribution is Monkey Ballsack Linux, thank you very much. How am I suppose to gain market share in the Fortune 500 when people can't even get the name right? Geez.
I liked the article, but I really wanted to hear more about the particular problems he experienced with the equipment, and what (if any) type of workaround he used to get them back into shape. In such extreme weather, he HAD to have more failures or problems other than that one hard drive. On the other hand, he didn't go above a certain altitude, and maybe everything was fine and dandy. For that, I can think of the ads now: "ABC Corp's hard disks survived EVEREST - put them to work in your demanding data center today!"
What part of my comment demanded anything from Nvidia? They have every right to do exactly what they are doing, and I respect that. They have excellent support with their proprietary drivers, and I use them whenever I can. I expected TFA to have some trinket of _news_. I was sadly disappointed, that's all.
Still no 3D support without having to use a proprietary (closed) driver. Wake me up when that changes.
Clarification: MySQL provides tons of services (http://mysql.com/support/). It is just that they are only for their "Enterprise" products. Of course, those are under the commercial license...
Wiki for the patch here: http://code.google.com/p/google-mysql-tools/wiki/M ysql4Patches