|
From: Bruce S. <bw...@ar...> - 2008-04-24 00:58:29
|
Is it possible your config media is full? That's the only problem I've run into with save-config. I'm using an floppy image in VMware. 1.3.5 saves the new config under a different name and leaves the old config alone. If there aren't room for both, then save-config will fail. I don't remember the exact error message, as most of the time there is room for both configs on a single floppy. Once you are comfortable 1.3.5 works, you can delete the old config file. Or you can backup the old config somewhere else and delete it from your primary media to make room for the new config. - BS > Hi! > > I just installed the new 1.3.5 DL with the new aufs feature. > Everything started like normal. > So i decided to do a save-config > but i've got: > > ---> > > Found configuration file location used by boot: /dev/sda1 > using device /dev/sda1 > listing difference > > bzip2: Compressed file ends unexpectedly; > perhaps it is corrupted? *Possible* reason follows. > bzip2: Inappropriate ioctl for device > Input file = (stdin), output file = (stdout) > > It is possible that the compressed file(s) have become corrupted. > You can use the -tvv option to test integrity of such files. > > You can use the `bzip2recover' program to attempt to recover > data from undamaged sections of corrupted files. > > tar: Child returned status 2 > tar: etc-mods: Not found in archive > tar: Error exit delayed from previous errors > Do you still want to save? > (y/n) > > <---- > > Has anyone similar problems to migrate his "old" config file to the > "new" one?? > > ---- > Oliver |