carstenw wrote: Bifurcator wrote:
One of the more obvious things for me is the their damaged DB files!
Which DB files are you talking about; could you point me at one?
There\'s the .DS_Store in every single folder. When these go bad and they VERY often do there\'s a whole host of troubles it can cause - like not remembering the display states of folders or your desktop, or not displaying icons properly or at all.
There\'s .bom files for every single app install usually found in /Library/Receipts/. Each .bom file contains a list of files installed for an app by the installer along with the correct permissions for each and every file. These don\'t go bad so often but the actual permissions do and Apple seems unable or unwilling to scan those files and reset permissions as they should be according to the relative .bom files. They kinda try to do it with Apple software but nothing from them AFAIK will clean up your non-apple apps once the permissions get corrupted - and they do quite often!
There\'s ACLs (Access Control Lists) - when ACLs go bad you get problems like finder always asking you for your password even on folders and files it shouldn\'t - as just one example. ACLs go bad quite often! Lots and lots of troubles with them! Especially in later releases of OS X. They can just ruin a server installation!!
The \"LaunchServices\" DB is responsible for the link between documents of a given type and the application that gets executed. It also keeps a list of all installed and previously executed apps. You feed it everytime you open a new type of document and you modify it everytime you select a different default app to open a file or general file type with - in the \"Get Info\" panel. When it goes bad and it VERY often does, you start seeing duplicates in the \"Open With\" menus, you can get wrong or corrupt looking icons, it can keep associations with deleted applications, or simply execute the wrong app on a double click.
The DYLD (DYnamic LoDer) uses a sort of DB known as a shared cache in simpler terms, to load all the frameworks, dylibs, and bundles needed by a given application\'s process - system or other. This DB (shared catch) gets whacked all the time and can cause kernel panics on occasion! Mostly shite just stops working tho. The DB gets rebuilt during Apple\'s \"Monthly Scripts\" execution which happens once a month blind to the end user.
There\'s the MEI which is an indices for all the mail and mail folders on your system. It gets messed up pretty often too and can cause all kinds of troubles with mail reading, display, and searching. If you only have tens of thousands of messages on your system it either doesn\'t corrupt often or the affects of the corruption aren\'t obvious. Using and managing hundreds of thousands of messages over multiple accounts however and the instability becomes both obvious and extremely annoying! In the worst cases you can lose whole message bases. I have! :P
There\'s a Help system DB that\'s responsible for connecting help lookups with the associated app. This goes corrupt a lot. When it goes you get messages stating \"There is no help for this topic.\" when actually there is. Or you can get really really slow look-ups, and I\'ve even seen system crashes from this. Don\'t ask me how tho... <shrug>
And this is just the short list of just one particular weakness in OS X which I thought was the most obvious to end users. I certainly haven\'t met anyone who hasn\'t experienced at least one of these problems. And they\'ve not only been happening from the beginning but they\'ve gotten progressively worse and worse with every release. To the casual user they\'re often little more than an annoyance. They can be a major headache for a workstation user depending on the machine to do actual job related work. And they can be critical in the survival or death of a server installation!
carstenw wrote: Bifurcator wrote:
One of the more obvious things for me is the their damaged DB files!
Which DB files are you talking about; could you point me at one?
There\'s the .DS_Store in every single folder. When these go bad and they VERY often do there\'s a whole host of troubles it can cause - like not remembering the display states of folders or your desktop, or not displaying icons properly or at all.
There\'s .bom files for every single app install usually found in /Library/Receipts/. Each .bom file contains a list of files installed for an app by the installer along with the correct permissions for each and every file. These don\'t go bad so often but the actual permissions do and Apple seems unable or unwilling to scan those files and reset permissions as they should be according to the relative .bom files. They kinda try to do it with Apple software but nothing from them AFAIK will clean up your non-apple apps once the permissions get corrupted - and they do quite often!
There\'s ACLs (Access Control Lists) - when ACLs go bad you get problems like finder always asking you for your password even on folders and files it shouldn\'t - as just one example. ACLs go bad quite often! Lots and lots of troubles with them! Especially in later releases of OS X. They can just ruin a server installation!!
The \"LaunchServices\" DB is responsible for the link between documents of a given type and the application that gets executed. It also keeps a list of all installed and previously executed apps. You feed it everytime you open a new type of document and you modify it everytime you select a different default app to open a file or general file type with - in the \"Get Info\" panel. When it goes bad and it VERY often does, you start seeing duplicates in the \"Open With\" menus, you can get wrong or corrupt looking icons, it can keep associations with deleted applications, or simply execute the wrong app on a double click.
The DYLD (DYnamic LoDer) uses a sort of DB known as a shared cache is simpler terms to load all the frameworks, dylibs, and bundles needed by a given application\'s process - system or other. This DB (shared catch) gets whacked all the time and can cause kernel panics on occasion! Mostly shite just stops working tho. The DB gets rebuilt during Apple\'s \"Monthly Scripts\" execution which happens once a month blind to the end user.
There\'s the MEI which is an indices for all the mail and mail folders on your system. It gets messed up pretty often too and can cause all kinds of troubles with mail reading, display, and searching. If you only have tens of thousands of messages on your system it either doesn\'t corrupt often or the affects of the corruption aren\'t obvious. Using and managing hundreds of thousands of messages over multiple accounts however and the instability becomes both obvious and extremely annoying! In the worst cases you can lose whole message bases. I have! :P
There\'s a Help system DB that\'s responsible for connecting help lookups with the associated app. This goes corrupt a lot. When it goes you get messages stating \"There is no help for this topic.\" when actually there is. Or you can get really really slow look-ups, and I\'ve even seen system crashes from this. Don\'t ask me how tho... <shrug>
And this is just the short list of just one particular weakness in OS X which I thought was the most obvious to end users. I certainly haven\'t met anyone who hasn\'t experienced at least one of these problems. And they\'ve not only been happening from the beginning but they\'ve gotten progressively worse and worse with every release. To the casual user they\'re often little more than an annoyance. They can be a major headache for a workstation user depending on the machine to do actual job related work. And they can be critical in the survival or death of a server installation!
carstenw wrote: Bifurcator wrote:
One of the more obvious things for me is the their damaged DB files!
Which DB files are you talking about; could you point me at one?
There\'s the .DS_Store in every single folder. When these go bad and they VERY often do there\'s a whole host of troubles it can cause - like not remembering the display states of folders or your desktop, or not displaying icons properly or at all.
There\'s .bom files for every single app install usually found in /Library/Receipts/. Each .bom file contains a list of files installed for an app by the installer along with the correct permissions for each and every file. These don\'t go bad so often but the actual permissions do and Apple seems unable or unwilling to scan those files and reset permissions as they should be according to the relative .bom files. They kinda try to do it with Apple software but nothing from them AFAIK will clean up your non-apple apps once the permissions get corrupted - and they do quite often!
There\'s ACLs (Access Control Lists) - when ACLs go bad you get problems like finder always asking you for your password even on folders and files it shouldn\'t - as just one example. ACLs go bad quite often! Lots and lots of troubles with them! Especially in later releases of OS X. They can just ruin a server installation!!
The \"LaunchServices\" DB is responsible for the link between documents of a given type and the application that gets executed. It also keeps a list of all installed and previously executed apps. You feed it everytime you open a new type of document and you modify it everytime you select a different default app to open a file and general file type with - in the \"Get Info\" panel. When it goes bad and it VERY often does, you start seeing duplicates in the \"Open With\" menus, you can get wrong or corrupt looking icons, it can keep associations with deleted applications, or simply execute the wrong app on a double click.
The DYLD (DYnamic LoDer) uses a sort of DB known as a shared cache is simpler terms to load all the frameworks, dylibs, and bundles needed by a given application\'s process - system or other. This DB (shared catch) gets whacked all the time and can cause kernel panics on occasion! Mostly shite just stops working tho. The DB gets rebuilt during Apple\'s \"Monthly Scripts\" execution which happens once a month blind to the end user.
There\'s the MEI which is an indices for all the mail and mail folders on your system. It gets messed up pretty often too and can cause all kinds of troubles with mail reading, display, and searching. If you only have tens of thousands of messages on your system it either doesn\'t corrupt often or the affects of the corruption aren\'t obvious. Using and managing hundreds of thousands of messages over multiple accounts however and the instability becomes both obvious and extremely annoying! In the worst cases you can lose whole message bases. I have! :P
There\'s a Help system DB that\'s responsible for connecting help lookups with the associated app. This goes corrupt a lot. When it goes you get messages stating \"There is no help for this topic.\" when actually there is. Or you can get really really slow look-ups, and I\'ve even seen system crashes from this. Don\'t ask me how tho... <shrug>
And this is just the short list of just one particular weakness in OS X which I thought was the most obvious to end users. I certainly haven\'t met anyone who hasn\'t experienced at least one of these problems. And they\'ve not only been happening from the beginning but they\'ve gotten progressively worse and worse with every release. To the casual user they\'re often little more than an annoyance. They can be a major headache for a workstation user depending on the machine to do actual job related work. And they can be critical in the survival or death of a server installation!
carstenw wrote: Bifurcator wrote:
One of the more obvious things for me is the their damaged DB files!
Which DB files are you talking about; could you point me at one?
There\'s the .DS_Store in every single folder. When these go bad and they VERY often do there\'s a whole host of troubles it can cause - like not remembering the display states of folders or your desktop, or not displaying icons properly or at all.
There\'s .bom files for every single app install usually found in /Library/Receipts/. Each .bom file contains a list of files installed for an app by the installer along with the correct permissions for each and every file. These don\'t go bad so often but the actual permissions do and Apple seems unable or unwilling to scan those files and reset permissions as they should be according to the relative .bom files. They kinda try to do it with Apple software but nothing from them AFAIK will clean up your non-apple apps once the permissions get corrupted - and they do quite often!
There\'s ACLs (Access Control Lists) - when ACLs go bad you get problems like finder always asking you for your password even on folders and files it shouldn\'t - as just one example. ACLs go bad quite often! Lots and lots of troubles with them! Especially in later releases of OS X. They can just ruin a server installation!!
The \"LaunchServices\" DB is responsible for he link between documents of a given type and the application that gets executed. It also keeps a list of all installed and previously executed apps. You feed it everytime you open a new type of document and you modify it everytime you select a different default app to open a file and general file type with - in the \"Get Info\" panel. When it goes bad and it VERY often does, you start seeing duplicates in the \"Open With\" menus, you can get wrong or corrupt looking icons, it can keep associations with deleted applications, or simply execute the wrong app on a double click.
The DYLD (DYnamic LoDer) uses a sort of DB known as a shared cache is simpler terms to load all the frameworks, dylibs, and bundles needed by a given application\'s process - system or other. This DB (shared catch) gets whacked all the time and can cause kernel panics on occasion! Mostly shite just stops working tho. The DB gets rebuilt during Apple\'s \"Monthly Scripts\" execution which happens once a month blind to the end user.
There\'s the MEI which is an indices for all the mail and mail folders on your system. It gets messed up pretty often too and can cause all kinds of troubles with mail reading, display, and searching. If you only have tens of thousands of messages on your system it either doesn\'t corrupt often or the affects of the corruption aren\'t obvious. Using and managing hundreds of thousands of messages over multiple accounts however and the instability becomes both obvious and extremely annoying! In the worst cases you can lose whole message bases. I have! :P
There\'s a Help system DB that\'s responsible for connecting help lookups with the associated app. This goes corrupt a lot. When it goes you get messages stating \"There is no help for this topic.\" when actually there is. Or you can get really really slow look-ups, and I\'ve even seen system crashes from this. Don\'t ask me how tho... <shrug>
And this is just the short list of just one particular weakness in OS X which I thought was the most obvious to end users. I certainly haven\'t met anyone who hasn\'t experienced at least one of these problems. And they\'ve not only been happening from the beginning but they\'ve gotten progressively worse and worse with every release. To the casual user they\'re often little more than an annoyance. They can be a major headache for a workstation user depending on the machine to do actual job related work. And they can be critical in the survival or death of a server installation!
carstenw wrote: Bifurcator wrote:
One of the more obvious things for me is the their damaged DB files!
Which DB files are you talking about; could you point me at one?
There\'s the .DS_Store in every single folder. When these go bad and they VERY often do there\'s a whole host of troubles it can cause - like not remembering the display states of folders or your desktop, or not displaying icons properly or at all.
There\'s .bom files for every single app install usually found in /Library/Receipts/. Each .bom file contains a list of files installed for an app by the installer along with the correct permissions for each and every file. These don\'t go bad so often but the actual permissions do and Apple seems unable or unwilling to scan those files and reset permissions as they should be according to the relative .bom files. They kinda try to do it with Apple software but nothing from them AFAIK will clean up your non-apple apps once the permissions get corrupted - and they do quite often!
There\'s ACLs (Access Control Lists) - when ACLs go bad you get problems like finder always asking you for your password even on folders and files it shouldn\'t - as just one example. ACLs go bad quite often! Lots and lots of troubles with them! Especially in later releases of OS X. They can just ruin a server installation!!
The \"LaunchServices\" DB is responsible for he link between documents of a given type and the application that gets executed. It also keeps a list of all installed and previously executed apps. You feed it everytime you open a new type of document and you modify it everytime you select a different default app to open a file and general file type with - in the \"Get Info\" panel. When it goes bad and it VERY often does, you start seeing duplicates in the \"Open With\" menus, you can get wrong or corrupt looking icons, it can keep associations with deleted applications, or simply execute the wrong app on a double click.
The DYLD (DYnamic LoDer) uses a sort of DB known as a shared cache is simpler terms to load all the frameworks, dylibs, and bundles needed by a given application\'s process - system or other. This DB (shared catch) gets whacked all the time and can cause kernel panics on occasion! Mostly shite just stops working tho. The DB gets rebuilt during Apple\'s \"Monthly Scripts\" execution which happens once a month blind to the end user.
There\'s the MEI which is an indices for all the mail and mail folders on your system. It gets messed up pretty often too and can cause all kinds of troubles with mail reading, display, and searching. If you only have tens of thousands of messages on your system it either doesn\'t corrupt often or the affects of the corruption aren\'t obvious. Using and managing hundreds of thousands of messages over multiple accounts however and the instability becomes both obvious and extremely annoying! In the worst cases you can lose whole message bases. I have! :P
There\'s a Help system DB that\'s responsible for connecting help lookups with the associated app. This goes corrupt a lot. When it goes you get messages stating \"There is no help for this topic.\" when actually there is. Or you can get really really slow look-ups, and I\'ve even seen system crashes from this. Don\'t ask me how tho... <shrug>
And this is just the short list of just one particular weakness in OS X which I thought was the most obvious to end users. I certainly haven\'t met anyone who hasn\'t experienced at least one of these problems. And they\'ve not only been happening from the beginning but they\'ve gotten progressively worse and worse with every release. To the casual user they\'re often little more than an annoyance. They can be a major headache or a workstation user depending on the machine to do actual job related work. And they can be critical in the survival or death of a server installation!
Oct 15, 2012 at 06:38 PM
Previous versions of Bifurcator's message #11044157 « I think i'm going to buy a windows 8 tablet »
