Nuke strings(1). It isn't used by anything, and we just recently switched
the userland strings(1) to the binutils version. Well, crunchgen(8) links all the stuff together ... can you say: "GPL pollution"? If anyone knows a good reason to have strings(1) on an install disk, I can resurrect a BSD-licensed strings. "Send me email". (ross@netbsd.org)
This commit is contained in:
parent
b3f966c92a
commit
d51c5fbcfc
@ -1,4 +1,4 @@
|
||||
# $NetBSD: md_install.conf,v 1.2 1997/12/22 00:39:37 cjs Exp $
|
||||
# $NetBSD: md_install.conf,v 1.3 1998/09/22 01:15:53 ross Exp $
|
||||
#
|
||||
# ramdiskbin.conf - unified binary for the install ramdisk
|
||||
#
|
||||
@ -14,7 +14,7 @@ progs cat chmod chown chroot cp df disklabel ed
|
||||
progs fsck fsck_ffs gzip ln mkdir mknod
|
||||
progs mount mount_cd9660 mount_ffs mount_kernfs mount_msdos mount_nfs
|
||||
progs mt mv newfs ping pwd reboot rm sed shutdown slattach
|
||||
progs strings stty sync tar test tip umount update
|
||||
progs stty sync tar test tip umount update
|
||||
progs installboot
|
||||
|
||||
ln chown chgrp
|
||||
|
Loading…
Reference in New Issue
Block a user