I got it now, confused I was.
Grep is not the culprit.
FWIW, grep -s -i -E (\t|\s)fastboot($|\t|\s)'
should be just fine.
printf ' i915.fastboot=1' | grep -s -i -E '(\t|\s)fastboot($|\t|\s)'
echo $?
1
$ printf ' fastboot' | grep -s -i -E (\t|\s)fastboot($|\t|\s)'
fastboot
$ printf '
an even CPU-cycles optimized manner,
grep -s -i -E '(\s|\t)fastboot(\s|$|\t)'
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Am 13.01.2014 01:15, schrieb Henrique de Moraes Holschuh:
severity 734901 grave
found 734901 sysvinit/2.88dsf-13
notfound 734901 sysvinit/2.88dsf-45
thanks
[...]Ack.
All other uses of grep -w to check the kernel command line are likewise
buggy, and could use some pro-active fixing. Another
3 matches
Mail list logo
