You are confusing "disinterested" for "uninterested". If a judge hears a case, being only concerned with rendering justice, then she is disinterested. On the other hand, if she wants the proceedings to end so that she can make her 3 o'clock appointment, then she is uninterested.
Are UNIX configurations files more prone to error than a registry? Otherwise, why should anyone believe that a registry is an improvement? Yeah, I've mistyped config data (in postgresql.conf), but is that worse than having a registry?
As for staying on topic, are you saying that the registry is not a security hole?
Prolonging the inevitable what? How often do UNIX/Linux/BSD boxes fail at all, let alone because of an error in typing a configuration file? Do you have data on how often UNIX sysadmins edit configuration files, or are you just guessing? Are there particular files that admins must frequently edit, or is the sheer number of such files?
If editing text files is such an "inferior" way to maintain computers, then why do UNIX/Linux sysadmins manage more computers than their Windows counterparts? How many person hours a day could one save by automating configuration?
As for preventing the sysadmins from manually changing settings, maybe you (or Microsoft) should try to prevent unauthorized parties from changing the settings.
If the first thing happens once every year, that's a little more than one tenth of one percent downtime. If the second thing happens once a month, that's less than one percent downtime. Three percent downtime still looks bad to me.
Isaac Newton was bullied in school until one of his teachers suggested that Newton confront the bully in a fair fight. Newton won the fight, and improved academically so much that he became famous for it. Maybe Rockstar should include that.
It may not have the automatic "transactionality" of a fully transcational data base, but it is something.
To what extent is maintaing configuration files a "common" activity? To what extent can one automate the maintenance of configuration files? Should system administrators be able to maintain the system manually if need be?
As for having a common API, historically, UNIX configuration data were text-based for ease of manipualtion.
As for letting you shoot yourself in the foot, yes, that's possible. Does a Lamborghini prevent you from exceeding the speed limit? No. Is a Lamborghini badly engineered?
Would you recommend any operating systems as having a good configuration database?
Data files may be coarse, but few Linux configuration files are so large that this a problem. Same for security.
Transactional? Hmm. . .
cp foo.conf savefoo.conf edit foo.conf
Oops!
mv savefoo.conf foo.conf
Do you believe that system administrators are so mistake prone that they can't be trusted to edit text files? Or do you allow ordinary users to edit system files?
What justification do you have for your claim that changes should be made via a centralized, standardized interface? Isn't this just more of the "One True Way" mantra from Microsoft?
Changing wallpaper in KDE: Start -> Control Center -> Appearance and Themes -> Background. Select the desktop whose wallpaper is to be changed. Under background, check Picture, choose Picture. Then choose options (centered, scaled, tiled, etc).
I'm not sure what the GP meant by running with command options, but I have a response to your question: Namely, in Linux, the the default is for executables to be stored in a few well-known directories. This requires fewer directories in the path than would be the case with an "each app gets its own directory" approach. The same holds true for shared libraries (how do apps share libraries in the "each app gets its own directory" approach?).
Why do you believe that the concept of editing text files for configuration is "broken" in the first place? Repairing an incorrect text file only requires a text editor. Even if the system is unbootable, one needs only a LiveCD with a text editor. And "backing it into some human readable format like XML", hmmm . . . What nontext files are human readable?
What does the structure of an image file is stored have to do with assembler? One could make that optimization merely by knowing the image format. Also, what would assembler tell you of the image format?
And how well does it draw the curve to the points? Pstricks automatically calculates the values, so it's somewhat easier there. One problem it may have is that it will draw outside of the box.
Where are the screenshots? Also, how easy is it to paste? With pstricks, the graph (and axes, etc) are simply part of the file, with no pasting necessary.
Slashdot Mirror
And what alternative medicine do you believe should threaten the revenue of pharmaceutical companies?
How about .lxix?
But (as has been discussed here before) what if it references the numeric IP address, and not the domain name?
They might choose to edit certain articles because they have knowledge in the area. Unless you are saying that having knowledge is a bias.
You are confusing "disinterested" for "uninterested". If a judge hears a case, being only concerned with rendering justice, then she is disinterested. On the other hand, if she wants the proceedings to end so that she can make her 3 o'clock appointment, then she is uninterested.
And what is the marginal cost of burning a Freeduc CD?
But what does it cost per user? A $10,000,000 program used by 10,000,00 people would be a dollar a head.
Are UNIX configurations files more prone to error than a registry? Otherwise, why should anyone believe that a registry is an improvement? Yeah, I've mistyped config data (in postgresql.conf), but is that worse than having a registry?
As for staying on topic, are you saying that the registry is not a security hole?
Perhaps the GP was asking if MyISAM supports transactions yet?
Prolonging the inevitable what? How often do UNIX/Linux/BSD boxes fail at all, let alone because of an error in typing a configuration file? Do you have data on how often UNIX sysadmins edit configuration files, or are you just guessing? Are there particular files that admins must frequently edit, or is the sheer number of such files?
If editing text files is such an "inferior" way to maintain computers, then why do UNIX/Linux sysadmins manage more computers than their Windows counterparts? How many person hours a day could one save by automating configuration?
As for preventing the sysadmins from manually changing settings, maybe you (or Microsoft) should try to prevent unauthorized parties from changing the settings.
If the first thing happens once every year, that's a little more than one tenth of one percent downtime. If the second thing happens once a month, that's less than one percent downtime. Three percent downtime still looks bad to me.
Isaac Newton was bullied in school until one of his teachers suggested that Newton confront the bully in a fair fight. Newton won the fight, and improved academically so much that he became famous for it. Maybe Rockstar should include that.
It may not have the automatic "transactionality" of a fully transcational data base, but it is something.
To what extent is maintaing configuration files a "common" activity? To what extent can one automate the maintenance of configuration files? Should system administrators be able to maintain the system manually if need be?
As for having a common API, historically, UNIX configuration data were text-based for ease of manipualtion.
As for letting you shoot yourself in the foot, yes, that's possible. Does a Lamborghini prevent you from exceeding the speed limit? No. Is a Lamborghini badly engineered?
Would you recommend any operating systems as having a good configuration database?
Data files may be coarse, but few Linux configuration files are so large that this a problem. Same for security.
Transactional? Hmm. . .
cp foo.conf savefoo.conf
edit foo.conf
Oops!
mv savefoo.conf foo.conf
Do you believe that system administrators are so mistake prone that they can't be trusted to edit text files? Or do you allow ordinary users to edit system files?
What justification do you have for your claim that changes should be made via a centralized, standardized interface? Isn't this just more of the "One True Way" mantra from Microsoft?
Auto updaters pretty much determine any dependencies automatically. And Best Buy already sells boxed SUSE.
Changing wallpaper in KDE: Start -> Control Center -> Appearance and Themes -> Background. Select the desktop whose wallpaper is to be changed. Under background, check Picture, choose Picture. Then choose options (centered, scaled, tiled, etc).
I'm not sure what the GP meant by running with command options, but I have a response to your question: Namely, in Linux, the the default is for executables to be stored in a few well-known directories. This requires fewer directories in the path than would be the case with an "each app gets its own directory" approach. The same holds true for shared libraries (how do apps share libraries in the "each app gets its own directory" approach?).
But if those "stupid third-party programmers" don't even bother porting their applications to Linux, is that Linux's fault?
Why do you believe that the concept of editing text files for configuration is "broken" in the first place? Repairing an incorrect text file only requires a text editor. Even if the system is unbootable, one needs only a LiveCD with a text editor. And "backing it into some human readable format like
XML", hmmm . . . What nontext files are human readable?
Only 97% uptime? That's 14 minutes of downtime per 8 hours. Is that acceptable?
Because it's spelled "Halliburton"?
I guess the latest "TCO [of] Microsoft is great" checks failed to appear this week.
What does the structure of an image file is stored have to do with assembler? One could make that optimization merely by knowing the image format. Also, what would assembler tell you of the image format?
And how well does it draw the curve to the points? Pstricks automatically calculates the values, so it's somewhat easier there. One problem it may have is that it will draw outside of the box.
Where are the screenshots? Also, how easy is it to paste? With pstricks, the graph (and axes, etc) are simply part of the file, with no pasting necessary.
Also, is PowerCalc available for Linux?