Can exec.svg entries be deleted with no harm? [SOLVED]

[Sky Aisling]

Are exec.svg files temporary? Can they be deleted with no harm?
Environment: Dell Inspiron Bionicpup(64)
The exec.svg icon shows up in various locations in the system after a session.
For example1: Event sounds in ~/.cache
For example2: /initrd/mntdev_save/

When I delete the event sound entries in ~/.cache and it reduces the save area data according to Graphical Disk Map 0.8.1. which is a good thing.
Can I do the same to the entries in dev_save area without harm?

Thank you in advance for any comments,

Sky

[Phoenix]

Your answer: the exec icons do not necessarily mean they're useless. They can refer to executables (e.g bash), or binary data that file could not match a pattern to.

So do not simply DELETE files with such icons. boot.catalog is a windows thing it appears, and serves as a checksum (?). isolinux.bin is one of the bootloaders (specifically syslinux) that may be needed. vesamenu.c32 if read will reveal its a configuration file for the bootloader. For event-souce-cache-<hexadecimal> you can delete safely. But they'll regenerate.

[mikewalsh]

@Sky Aisling :-

You often find that particular icon assigned to a lot of different types of files, Sky. This usually occurs - or so I understand - because the file-type doesn't have a specific mime-type assigned to it, so Puppy simply assigns one that's the "best fit", as far as it's concerned.

I wouldn't simply delete all those files just on principle, because many of them ARE in fact executables. They're often ones that Puppy needs for background processes, too, so that's a very quick route to breaking your Pups!

Those ones you mentioned in /root/.cache are fine to delete. They'll simply get re-created again anyway; I periodically clear a whole bunch of those out of /root/.cache myself. Doesn't hurt anything.

Mike.

[OscarTalks]

I agree that, in almost all cases, files showing that icon in ROX should NOT be deleted for the reasons explained above.
Those event-sound-cache.tdb files however CAN be deleted.
They appear to be a non-functional (in Puppy) by-product of libcanberra (Ubuntu build)
If you re-compile libcanberra with --disable-tdb those files are no longer produced.
See this thread talking about this in 32bit Bionic:-
http://forum.puppylinux.com/viewtopic.php?t=3581