The command sed -i -e 's/foo/bar/' file treats '-e' as being the
suffix for '-i', creating a backup file named 'file-e'.
Fixes: 709c1049fe0c ("GCE: Fix growfs path")
MFC After: 1 day
Differential D57422
GCE: Fix sed command Authored by cperciva on Thu, Jun 4, 12:21 AM. Tags None Referenced Files
Subscribers
Details
The command sed -i -e 's/foo/bar/' file treats '-e' as being the Fixes: 709c1049fe0c ("GCE: Fix growfs path")
Diff Detail
Event TimelineComment Actions Hm, this'll break if building on Linux... don't know if GCE is one of the ones for which that's now supported, probably not, but a bit sad to have this Comment Actions Oh, I didn't know our VM image building code supported cross-building. That would explain why the original patch (which was submitted from Google) was wrong though.
Comment Actions In theory it mostly does thanks to -DNO_ROOT and -DWITHOUT_QEMU, though there might be other missing pieces. I know Brooks has an old branch for CheriBSD somewhere that does it, but there may be things that have yet to be cleaned up and merged (upstream and downstream, we're not building VM images). Comment Actions Actually, this is a completely harmless bug since the GCE images are built with NO_ROOT so the accidental /etc/rc.d/growfs-e file doesn't get distributed anyway. This does need to get fixed properly though -- right now GCE images will stop running growfs the moment there's an update to the FreeBSD-rc package (including upgrading to a new release). | |||||||||||||||||||||||||||||||||||||||||