Hi all,
# mylivecd --gzip --resolution 800x600 --md5sum --nodir ^/tmp/ --nodir ^/vbox/ --nodir ^/u/ /tmp/as.iso 2>&1
mylivecd, version 0.9.4, http://pclinuxos.com/
Copyright (C) 2010, Texstar <texstar at gmail.com>
This program is free software; you can redistribute it and/or
modify it under the terms of the GNU General Public License
as published by the Free Software Foundation; either version 2
of the License, or (at your option) any later version.
Disabling Services not needed on the LiveCD
running: /sbin/chkconfig --list
running: /sbin/chkconfig --list
running: /sbin/chkconfig --list
running: /sbin/chkconfig --list
running: /sbin/chkconfig --list
Creating initrd: [100.00% 00:00:05/00:00:05]
Setting filesystem parameters: [100.00% 00:00:02/00:00:02]
Creating compressed image: [ 79.43% 00:32:34/00:41:15]^C
FATAL: Interrupted.
I'm experiencing some bad behavior using mylivecd, some details:
Usually my ISO will include the '/' filesystem + '/boot' and create a correct ISO image of approx 4 Gib, the whole process take approx 12 minutes.
Instead of unmounting the /vbox and /u filesystems, this time I've used the --nodir option, as reported above, but something has gone wrong, the progress counter stop at 79.43% while the temporary files continue to grow indefinitely, after half an hour the whole /tmp filesystem is filled and the only thing to do is to kill the mylivecd process.
I have performed a filesystem check on all filesystems, all filesystems were already OK. (used fsck -f ...)
The only thing I can note is that the /u filesystem actually contains a lot of small files, exactly 42652, implicitly mylivecd create a large list of excluded files.
Is this a known issue ? Am I doing something wrong ?
Clearly unmonting the /u filesystem allow me to create the correct image.iso, but
I need to know if the --nodir option used on a mounted filesystem could be considered equivalent to unmounting the same filesystem or not.
Or eventually if there are known limits while using --nodir --nofiles options.
Thanks for reading.
AS