|
From: Rick F. <ri...@gr...> - 2006-06-08 03:13:23
|
Been using Devil-Linux 1.2.6 for nearly a year. All of a sudden this month was unable to boot after running save-config. Came across message in mailing list archive with same problem (see original message below), but never saw resolution in subsequent thread: http://sourceforge.net/mailarchive/message.php?msg_id=12196562 Found problem was caused by compressed file created by save-config using bzip2 with "-s" option which prevented busybox tar from being able to decompress the file. If I remove the "-s" option, busybox tar has no problem decompressing file (GNU tar able to decompress fine either way). Since I have plenty of RAM, I use a modified save-config file that uses bzip2 w/o "-s" option that works fine with busybox tar. I do not have any additional large files in /etc or /root. Never had the problem till last month after using 1.2.6 for quite some time. Only changes during that time period (that I can think of) were firewall rules and openvpn config changes. Overall size of etc.tar (before and after compression) is basically same before and after problem. Is this a known bug? Thanks, - Rick P.S. Great work on the devil-linux distro! From: Carl <chdl@se...> boot failure after config changes 2005-06-26 10:49 Hi, I"m having issues saving configuration changes. The boot sequence trips over trying to decompress the new etc.tar.bz2 with the following messages: tar: Decompression failed tar: Unable to read all data tar: Unable to read all data .: 10: can"t open /etc/sysconfig/config |