We've seen some inconsistent behavior in the rsync excludes in the past. Nobody has been able to pin down the exact problem. If you look hard enough, you can probably find some discussions about it on this forum.
We've messed around with the excludes, and we stop messing if it seems to be working. The way it's supposed to work is that everything to the right of the last slash in the path is affected (copied or excluded, depending on what you told it to do), so you shouldn't need to use an asterisk at the end to remove all files. Just a slash at the end of the last directory in the path should copy the directory but not any of the files inside. Yet you see we have final asterisks in the excludes file. Excluding /usr/share/doc should result in the doc directory not existing on the copied filesystem. Excluding /usr/share/doc/ should copy just an empty directory.
Sorry I can't be more definitive about that. You might get some ideas reading the section on includes and excludes in man rsync. You can do some tricky things with it.
I thought of another way. (untested) At the edit-menu pause, chroot into the filesystem at $work_dir/myfs/, then delete the user and /home/user. Add the word, config, to the boot append line, and live-config will create a user on the fly. Login 'user' password 'live'. And the user's home will be created from etc/skel.
- Code: Select all
chroot /home/work/myfs
deluser user
rm -r /home/user
exit
One thing I'm more sure about is that etc is the only directory that causes the forum software to puke when it starts with a slash. /home, /usr and even /bin are ok.