ff12a7954c
As in2a5fcfae02and in3e67e5c992using /usr/bin/env allows bash to be looked up in PATH rather than being hard-coded. As with the previous changes the same arguments apply - distributions have scripts to rewrite shebangs on installation and they know what locations to rely on. - For tests/compilation we should rather rely on the user to have setup there PATH correctly. In particular this makes testing from git easier on NixOS where do not provide /bin/bash to improve compose-ability.
28 lines
482 B
Bash
Executable file
28 lines
482 B
Bash
Executable file
#!/usr/bin/env bash
|
|
fd=0
|
|
|
|
OPTIND=1
|
|
while getopts "C:aTlM" opt; do
|
|
case "$opt" in
|
|
C)
|
|
fd=$OPTARG
|
|
;;
|
|
\?);;
|
|
esac
|
|
done
|
|
|
|
shift "$((OPTIND-1))"
|
|
device=$1
|
|
|
|
echo "Running fake fsck on $device"
|
|
|
|
declare -a maxpass=(30 5 2 30 60)
|
|
|
|
for pass in {1..5}; do
|
|
maxprogress=${maxpass[$((pass-1))]}
|
|
for (( current=0; current<=${maxprogress}; current++)); do
|
|
echo "$pass $current $maxprogress $device">&$fd
|
|
sleep 0.1
|
|
done
|
|
done
|