fatdog - surveying the layers

[je55eah]

using the sandbox script I used these commands to list the files in the layers of fatdog. It would be cool if the layers could be specified from the command line.

Code: Select all

sandbox.sh

find / \( -path "/dev" -o -path "/sys" -o -path "/proc" -o -path "/tmp" \) -prune -o -name "*" -print | less

find / \( -path "/dev" -o -path "/sys" -o -path "/proc" -o -path "/tmp" \) -prune -o -name "*" -print > /tmp/filelist00.txt

exit 
sandbox.sh

find / \( -path "/dev" -o -path "/sys" -o -path "/proc" -o -path "/tmp" \) -prune -o -name "*" -print | grep -Fxvf /tmp/filelist00.txt > /tmp/filelist01.txt

find / \( -path "/dev" -o -path "/sys" -o -path "/proc" -o -path "/tmp" \) -prune -o -name "*" -print > /tmp/filelist00-01.txt

exit
sandbox.sh

find / \( -path "/dev" -o -path "/sys" -o -path "/proc" -o -path "/tmp" \) -prune -o -name "*" -print | grep -Fxvf /tmp/filelist00-01.txt > /tmp/filelist02.txt

find / \( -path "/dev" -o -path "/sys" -o -path "/proc" -o -path "/tmp" \) -prune -o -name "*" -print > /tmp/filelist00-02.txt

exit
sandbox.sh

find / \( -path "/dev" -o -path "/sys" -o -path "/proc" -o -path "/tmp" \) -prune -o -name "*" -print | grep -Fxvf /tmp/filelist00-02.txt > /tmp/filelist03.txt

find / \( -path "/dev" -o -path "/sys" -o -path "/proc" -o -path "/tmp" \) -prune -o -name "*" -print > /tmp/filelist00-03.txt

exit
sandbox.sh

find / \( -path "/dev" -o -path "/sys" -o -path "/proc" -o -path "/tmp" \) -prune -o -name "*" -print | grep -Fxvf /tmp/filelist00-03.txt > /tmp/filelist04.txt

find / \( -path "/dev" -o -path "/sys" -o -path "/proc" -o -path "/tmp" \) -prune -o -name "*" -print > /tmp/filelist00-04.txt

exit
sandbox.sh

find / \( -path "/dev" -o -path "/sys" -o -path "/proc" -o -path "/tmp" \) -prune -o -name "*" -print | grep -Fxvf /tmp/filelist00-04.txt > /tmp/filelist05.txt

find / \( -path "/dev" -o -path "/sys" -o -path "/proc" -o -path "/tmp" \) -prune -o -name "*" -print > /tmp/filelist00-05.txt

exit

The resulting files are attached, and here is a summary:

filelist00-pup_init = 589 files - unix
filelist01-kernel-moules = 6732 files - drivers
filelist02-pup_ro = 31781 files - X11, flash player, gimp, gtk, jack, lxc, pidgin, ripperX, ADMplugins, libreOffice, seamonkey, vlc, Rox, lxqt,
games, glade3, qt5, slsh, openbox, init.d, and more
filelist03-pup_multi = 21323 files - firefoxESR, wingrid, virtualbox, cache,
filelist04-pup_save = 961 files - new cache
filelist05-pup_rw = 3 files - newest cache

Is there a script that is used to automatically install everything in the pup_ro layer?

[jamesbond]

You don't have to survey. All is documented here.

Is there a script that is used to automatically install everything in the pup_ro layer?

I'm not sure I understand the question. "ro" in pup_ro stands for "read-only", so what exactly do you mean by "installing in pup_ro layer?"

[je55eah]

when you created the pup_ro layer did you use a script to automate the process or is everything installed and configured by hand?

[jamesbond]

Fatdog64 ISO Builder

[je55eah]

The attached filelist is the real list of pup_init contents. The old layer 00 list I posted above included files from the base layer.

[je55eah]

and these are the other files I found earlier...

Code: Select all

mv /mnt/sdc2/notes/filelist00-pup_init.txt /mnt/sdc2/notes/filelist00-pup_init\ and\ base.txt
find /aufs/pup_init/ | cut -c 15- > /mnt/sdc2/notes/filelist00-pup_init.txt
awk 'NR==FNR{a[$0]=1;next}!a[$0]' filelist00-pup_init.txt filelist00-pup_init\ and\ base.txt

output:

Code: Select all

/usr/bin/xwin
/usr/bin/wmexit
/mnt/sb
/mnt/sb/sandbox
/mnt/sb/sandbox/usr
/mnt/sb/sandbox/usr/bin
/mnt/sb/sandbox/usr/bin/xwin
/mnt/sb/sandbox/usr/bin/wmexit
/mnt/sb/sandbox/mnt
/mnt/sb/sandbox/mnt/sb
/mnt/sb/sandbox/mnt/sb/sandbox
/mnt/sb/sandbox/etc
/mnt/sb/sandbox/etc/profile
/mnt/sb/sandbox/etc/shinit
/mnt/sb/sandbox/etc/BOOTSTATE
/mnt/sb/sandbox/.wh..wh.orph
/mnt/sb/sandbox/.wh..wh.plnk
/mnt/sb/sandbox/.wh..wh.aufs
/etc/shinit

They don't look like a base layer, but rather more like something added by the sandbox.

@jamesbond told me that the init layer is almost empty. I'm baffled.