3 ms·
> When something does not work in Linuxland the answer is still "open the terminal, enter a bunch of cryptic commands" and/or manually edit text-based config fi
by _delirium 13y ago
> When something does not work in Linuxland the answer is still "open the terminal, enter a bunch of cryptic commands" and/or manually edit text-based config files.
That's true in OSX too, though. After upgrading to 10.9 ("Mavericks") I had a 'systemstats' process taking up 100% CPU and >3GB of RAM at random points. Did some googling and reading through forum threads, and the solution was to muck with some BerkeleyDB files in a terminal. Is OSX an acceptable modern desktop OS?
Windows in my experience has been even worse, in that for OSX there at least usually exists some arcane way of fixing your problem, while in Windows it's just "wipe and reinstall", because the problems are totally opaque. (I don't have great memories of the registry editor, either.)
- jotm 13y agoNah, the new solution in Windows is "do a system restore", which is way easier than reinstalling everything. Works pretty well, too...
- jmhain 13y agoBeen managing a large Windows network for ~8 years; never once yet seen system restore fix a problem. It also seems to frequently introduce new ones.