That /var cleaning is no longer correct. In 700 (or may be in late 600s, I can't recall), the only /vars cleaned out are: /var/cache /var/lock /var/locks and /var/run; others are kept, because this is what LSB actually says (and a lot of programs keep their "variable data" stuff in /var). "keepvar" still exists, and prevent even those above from being cleaned out.Wognath wrote:jamesbond wrote hereThe system will automatically clean out everything inside /var during restart unless [kernel parameter "keepvar"] is set. It works fine for Fatdog, but slackware keeps a lot of stuff in /var (e.g - list of installed packages), so if you don't keep the content of var, well - lotsa things will break sooner or later (e.g. can't uninstall packages).
Indeed, that directory is the "downloaded package cache" for slapt-get/gslapt. Feel free to remove anything inside there, either manually or by running "slapt-get --clean"./var/slapt-get contains a lot of txz packages, even from apps I have removed. Does "it works fine for Fatdog" mean I can delete these? (I'm cleaning house to reduce long "running auchk" delay during bootup)
No, it is okay and it is appropriate. It is actually better than shipping the "updated" MIME files in the SFS itself, because the same MIME files on pupsave can always override them. Note you run it as "update-mime-data /usr/share/mime".step wrote:I'm making an SFS file for an app that needs to add new MIME types to the system. That calls for automatically running:
update-mime-database /usr/share/mime/packages
when the SFS file is loaded. I will place that command inside tmp/sfs/autorun.sh in the SFS source folder.
1) Is it appropriate for an SFS file to update MIME types, or will it break something in the existing MIME types and/or menus?
It is run after SFS is loaded, and before SFS is unloaded (while the SFS has been/still being merged into the root filesystem). When it runs you have access to the SFS itself. You've got a parameter $1 that tells you what action is being done on the sfs (load/unload/systemload/systemunload) and the $2 tells you the path of the SFS (/aufs/pup_roxxxx) in case you need it.2) Does /tmp/sfs/autorun.sh fire before or after the SFS filesystem is loaded? I need it to fire after.