> OK, how about this as an idea then: > > Parse mount output to see if anything is mounted to /boot/efi directly? > > if mount -p | cut -f 2 | grep '^/boot/efi$'; then > .... > fi
What am I missing here? One place I am being told this is run in an environment that may not even be an EFI booted system, and in another place it is being used as a test if something is mounted on it, which should only be true on an EFI booted system. Using the existance of a directory or something mounted on that directory is probably one of the worse ways to make a decsiion about if the system is or is not EFI capable, or if it needs or doesnt need EFI support stuff. I often boot from a MBR sd card or usb memstick and install an EFI system on another type of media. I am sure there is stuff in the release process that has to make EFI related platform issues, and that should probably be controled by a platform specific MK_foo knob, and not by these "exists" tests. > Brandon Bergren > bdra...@freebsd.org -- Rod Grimes rgri...@freebsd.org _______________________________________________ dev-commits-src-all@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/dev-commits-src-all To unsubscribe, send any mail to "dev-commits-src-all-unsubscr...@freebsd.org"
