I've been working with updating the Dachstein pre-release images, and ran
into a problem with the backup scripts when making a new root package. I
don't have time to crawl through the new scripts right now, but perhaps the
symptoms will be easily recognized by someone more familiar with the new BB
tar backup...
I start with the following new /boot directory, which contains it's own etc
and lib/modules directory and gets backed up as part of root. I have
modified linuxrc to load modules from /boot prior to looking for LRP files,
so you can use loadable kernel modules to boot of things like IDE or SCSI
drives w/o requiring a kernel re-compile. Anyway, the directory structure
is as follows (trailing / indicates a directory):
/boot/
/boot/etc/
/boot/etc/modules
/boot/lib/
/boot/lib/modules/
/boot/lib/modules/readme
All well and good, but when I back up root, the boot directory winds up
looking like this:
/boot/
/boot/lib/
Everything in the /boot/etc directory is gone, as is the /boot/lib/modules
directory. This seems a bit suspect, especially since the etc directory and
lib/modules directory should be part of the exclude list (but at the root
level...they shouldn't affect sub-directories).
Any ideas for a quick fix, or do I need to crawl through the backup script
and BB tar file handling code? I guess there's always ctar as a fallback,
but I think we can get BB tar working...
BTW: I noticed the -z switch seems to be working with BB tar, so you can:
tar -xzvf <package>.lrp
Which is quite handy...
Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
