Yes, nothing says you can't put an extension in /opt. I'm just saying it's not a good idea unless you have to. I'm pretty sure /usr/local is the preferred location when possible. I have an extension for the MS Sql Server ODBC driver for Linux which installs into /opt because the paths are hard coded in the binaries from Microsoft. Yes, I checked with the strings command. Given where files on a typical C: drive can wind up it's no surprise that they think nothing of filesystem management. In this case it serves as an example of why making a tcz that requires /opt should be avoided if possible. An extension that requires manually editing /opt/.xfiletool.lst is probably not for the masses. That's one of the reasons I haven't submitted my msodbcsql.tcz extension. As for chrome settings, fortunately they get saved in the user home dir.