summaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authormarcel <marcel@FreeBSD.org>2010-01-09 22:54:29 +0000
committermarcel <marcel@FreeBSD.org>2010-01-09 22:54:29 +0000
commite1c64beebc41d28b21e9e6b120a7a361bd6acd52 (patch)
tree10075f9ec03989accec7e9481bd42bccf1d14068 /tools
parent8a9b761eedfbc1dde4efb8333b61da39c37e9af0 (diff)
downloadFreeBSD-src-e1c64beebc41d28b21e9e6b120a7a361bd6acd52.zip
FreeBSD-src-e1c64beebc41d28b21e9e6b120a7a361bd6acd52.tar.gz
Remove file system support based on the simple file system protocol
as this only allows us to access file systems that EFI knows about. With a loader that can only use EFI-supported file systems, we're forced to put /boot on the EFI system partition. This is suboptimal in the following ways: 1. With /boot a symlink to /efi/boot, mergemaster complains about the mismatch and there's no quick solution. 2. The EFI loader can only boot a single version of FreeBSD. There's no way to install multiple versions of FreeBSD and select one at the loader prompt. 3. ZFS maintains /boot/zfs/zpool.cache and with /boot a symlink we end up with the file on a MSDOS file system. ZFS does not have proper handling of file systems that are under Giant. Implement a disk device based on the block I/O protocol instead and pull in file system code from libstand. The disk devices are really the partitions that EFI knows about. This change is backward compatible. MFC after: 1 week
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud