This document contains only my personal opinions and calls of judgement, and where any comment is made as to the quality of anybody's work, the comment is an opinion, in my judgement.
[file this blog page at: digg del.icio.us Technorati]
.desktopfiles which because of the Microsoft cultural hegemony laughably parrots that of MS-DOS
.inifiles, and I felt the usual outrage and sadness. It may be worthwhile to show how a less moronic format might have been like, by using the example in that page:
[Desktop Entry] Version=1.0 Type=Application Name=Foo Viewer Comment=The best viewer for Foo objects available! TryExec=fooview Exec=fooview %F Icon=fooview.png MimeType=image/x-foo; X-KDE-Library=libfooview X-KDE-FactoryName=fooviewfactory X-KDE-ServiceType=FooServiceWhat's wrong with this ridiculous layout? Well, mostly that is not good for processing with pipelines of UNIX-style commands, in other words that it is not tabular, and never mind the presence of gratuitous spaces. Consider an alternative:
entry:1.0:application:image/x-foo:fooview:fooview $F:fooview.png:Foo Viewer:The best viewer for Foowith perhaps lines of this shape to express the KDE-specific stuff:
entryext:1.0:application:image/x-foo:fooview:KDE:libfooview:fooviewfactory:FooServiceMy alternative version is briefer, easier to process in a pipeline, easy to sort (the order of fields has been chosen somewhat advisedly), easy to parse. Enough said.
auto-raisefor windows, precisely because I like the ability to keep the window that has focus (partially) under one that does not (for example when the top window has a list of files and the focused window under it has a shell. In this common case, that the unfocused window on top be translucent helps a bit.
Compositeextension acceleration; but the card I am using is an NVIDIA 6800LE and there is a known issue with the GNU/Linux NVIDIA drivers and speed of rendering antialiased characters, which uses the
RENDERextension, so perhaps it is just that. However CPU usage is very high even for operations on the active window, which is 100% opaque, which suggests some less optimal coding of compositing.
Also the "Turn off hard disks" setting in the Power Schemes functions.In other words, power management works for external SATA as well as for internal SATA. As to the hotswap topic, it sort of mostly works under GNU Linux too, if one can remove and then reinsert the relevant SATA HA driver module. The hotswap discussion above makes indirectly a good point as to the difference between eSATA and SATA hot swapping:
Why Windows totally hangs up after the drive is powered?Now that should not happen because when a drive starts it draws a lot more power than during normal operation but this should not cause trouble on the other lines sharing the same rail. Anyhow eSATA is designed to avoid these issues by using an external power supply. Conversely there are quite a few systems where regular internal SATA connectors and Berg power connectors are exposed externally, and that's a much less good idea.
It is confirmed to happen when the internal hard drive and the drive are sharing the same power cable. Looks like the internal hard drive restarts and reinitializes if the power becomes unstable, and therefore Windows totally hangs up accessing it. This can be resolved by connecting individual power cable to the drive which is being powered.