Hey all, I've been working on implementing fsck support for mkinitcpio, and I'm at the point where I think I need some feedback. There's a lot of cleanup that leads up to the fsck, and you're welcome to disagree with any of that as well, but what I'm looking at the moment is a few questions regarding the actual fsck work: 1) How much do we want to try to repair automatically? Currently I'm passing similar flags to what we pass in the initscripts, but maybe there's a reason to do things differently here. 2) What return codes should we be bailing to a rescue shell on and forcing user intervention? Give it a whirl. I've probably broken something, but my VMs seem happy with it so far. d Dave Reisner (11): Makefile: install binaries to /usr/bin install/ide: remove install hook init: don't tell the kernel about the path to modprobe init: create /run/initramfs after mounting /run init_functions: refactor poll_device autodetect: store rootfstype for use by other hooks init: use util-linux's /bin/mount init_functions: move root resolution to separate function init_functions: generalize resolve_device fsck: implement basic fsck support install/fsck: new install hook to add fsck and helpers Makefile | 9 ++-- init | 18 ++++++- init_functions | 142 +++++++++++++++++++++++++++++----------------------- install/autodetect | 2 +- install/base | 3 + install/fsck | 28 ++++++++++ install/ide | 17 ------ 7 files changed, 131 insertions(+), 88 deletions(-) create mode 100644 install/fsck delete mode 100644 install/ide -- 1.7.7.2