> I've encountered a few problems I thought I should report. > > One is that the L option on the lrcfg backup menu seems to include the > ramlog package. Changing > > l|L) PKGn="/^log=/!" ;; > > to > > l|L) PKGn="/^ramlog=/!" ;; > > in lrcfg.back.script seems to take care of this.
This is intentional. Backing up ramlog does *NOT* backup the log files (just the ramlog scripts & config files), which is why ramlog is included in the "everything but logs" backup...in fact, it's basically impossible to cleanly backup the log files when using ramlog, due to limitations in the current packaging scheme (primarily related to using multiple mount-points...if you've got one big ramdisk, everything is OK, but your whole ramdisk can fillup with logged garbage, and kill your system). This is one of the big problems I want to fix, but it will likely require major changes to the existing packaging system or system init scripts (or both) to cleanly support multiple mount-points when building the root filesystem image. FYI: There was a long discussion thread about backing up log packages a while ago...you might search the mail archives. A few kludgy but workable solutions were discussed, IIRC. <excellent description of backup flaws snipped> Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
