[EMAIL PROTECTED] wrote: > > Andrea, > > Find below the autoinstallscript.conf. > > What appears to have happended is that /selinux was imaged and then > propagated to the > new machine. By removing /selinux files, creating /.autorelabel and > rebooting /selinux was > properly mounted and 'fixfiles relabel' was run.
Hi all, I think that we should add some common unwanted patters to the exclusions automatically made by systemimager during image retrieval by si_getimage. In some recent distributions some pseudo-filesystem are not reported with mount. On the other looking in /proc/mounts doesn't resolve, because there are also the filesystems mounted *under* others (usually rootfs, initramfs, etc). Here is a list of patterns that we could always exclude: # selinux stuff /selinux/* # eventfs in SuSE /lib/klibc/events/* # mounted media devices not reported by mount /media/* # NFS stuff /var/lib/nfs/* # LVM caches and backups (automatically re-created at the first boot) /etc/lvm/.cache /etc/lvm/backup/* /etc/lvm/archive/* What do you think? Do you know other patterns that should be automatically excluded? Regards, -Andrea PS for David: have you tried to remove /selinux/* from your image and try to repeat the installation? this is equivalent to run si_getimage with --exclude '/selinux/*'. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ sisuite-devel mailing list sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
