I'm on the fence about this one. I build a static bash and someother static tools of which vim is one of them, for recovery needs, but I'm not sure if the book should recommend that or install vim in /bin in the first place. A somewhat valid argument would be sed for emergency purposes.
Yep a good reason to get familiar with sed. And for an emergency like what you mentioned, where you're just editing a standard config file, likely it's a case of a simple typo. So you cat /etc/fstab , find your typo and swap the mistake out:
sed -i 's@/dev/hda4@/dev/hdb4@' /etc/fstab
Of course, as Archaic mentioned, for your own systems, if you want vim in /bin that's entirely up to you, but for LFS, I'm not so sure it's necessary.
Another nice thing to have lying around for cases like that is a livecd... ;)
-- Jeremy H. -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
