Tiny Core Linux

Tiny Core Extensions => TCE Talk => Topic started by: as on November 08, 2015, 02:54:36 AM

Title: How to identify what files have changed after installing new software?
Post by: as on November 08, 2015, 02:54:36 AM

I want to create an overlay initramfs containing the files required for a new application.

So first step is to create a clean tinycore install
Second step is to install the software and make sure it is configured properly
Third step is to identify exactly what files have changed to I can copy them onto an initramfs.

What's the most effective way to carry out step 3 - i.e. to identify exactly which files changed when I installed my application?

thanks!

Title: Re: How to identify what files have changed after installing new software?
Post by: Rich on November 08, 2015, 09:30:14 AM

Hi as
Have you looked at the extension creation section of the Wiki? Check the  "When DESTDIR Fails"  paragraph.

Title: Re: How to identify what files have changed after installing new software?
Post by: as on November 08, 2015, 03:02:22 PM

Thanks!

For those who come after here is the link: http://wiki.tinycorelinux.net/wiki:creating_extensions#when_destdir_fails

Title: Re: How to identify what files have changed after installing new software?
Post by: CentralWare on November 08, 2015, 11:48:53 PM

NOTE: If you automate the build (in a script) be sure to add sleep 1 otherwise you may find you're missing files if the BUILD is quick

• Create your time-stamp file
• Sleep 1 (ensures ALL of your new files are OLDER than the time stamp)
• BUILD your project
• sync (helps ensure files are actually WRITTEN, thus found)
• Sleep 1 (for safety, probably not needed)
• Run Find (and filter unneeded directories/files!)

Title: Re: How to identify what files have changed after installing new software?
Post by: Rich on November 09, 2015, 12:12:10 AM

Hi centralware
The second  sleep  is not needed,  sync  does not return until all file have been written.

Title: Re: How to identify what files have changed after installing new software?
Post by: bmarkus on November 09, 2015, 12:15:00 AM

Timestamping may not find all newly installed files. There may be files (e.g. config, doc, etc.) just copied with their original date. Add them manually to your build script.
 

Title: Re: How to identify what files have changed after installing new software?
Post by: netnomad on November 09, 2015, 01:41:12 AM

hi friends,

perhaps the filetool inotify ccould help you to monitor changes of files and dirs:
f.e. inotifywait -r -e create -m $HOME

keep on hacking :-)

Title: Re: How to identify what files have changed after installing new software?
Post by: CentralWare on November 09, 2015, 04:24:11 AM

Quote from: Rich on November 09, 2015, 12:12:10 AM

The second  sleep  is not needed,  sync  does not return until all file have been written.

I figured as much, but tend to take the safe route :)
I remember back in the day where a machine was "too fast" running a task (time-stamped) so I've been scripting the before and after as a precaution for over a decade now.