On Mon, Jun 11, 2018 at 12:01:34AM -0400, Gong S____ wrote: > Package: initscripts > Version: 2.88dsf-59.10 > > The current version used `logsave` to save `fsck` results. > When `logsave` is not present, the script will fail regardless of the actual > FS state. > /etc/init.d/checkfs.sh line 101 and 121: > logsave -s $FSCK_LOGFILE fsck $spinner -M -A $fix $force $FSCKTYPES_OPT > `logsave` is a part of `e2fsprogs`. If I do not use EXT filesystems (I use > JFS on my PC) I can purge this package. > > My suggestion: > 1. Do not use `logsave`. The process is not there in previous versions.or: > 2. If `logsave` is not found just check the FS without using `logsave`.
Or 3. copy or move logsave to the initscripts package (it's arch:any so can take compiled code). This is a stand-alone tool that makes no use of any part of e2fsprogs nor of its build system. All autoconfage is bogus, too, re-checking things that are mandated by POSIX. As for fsck: isn't jfs one of the remaining filesystems that still do fsck at boot? Most others (xfs, btrfs, reiserfs, ...) have long since dropped this, as in-kernel recovery is good enough. I guess jfs and ext3/4 can likewise drop fsck this way. We'd need fsck and thus logsave only for ancient stuff like ext2 or minix. Not sure if you can even install Debian to minix fs; I wish ext2 was gone but Hurd still doesn't support anything better. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ I've read an article about how lively happy music boosts ⣾⠁⢰⠒⠀⣿⡁ productivity. You can read it, too, you just need the ⢿⡄⠘⠷⠚⠋⠀ right music while doing so. I recommend Skepticism ⠈⠳⣄⠀⠀⠀⠀ (funeral doom metal).
