Its worth noting you should also go for GPT layout and have a 100meg or so
partition provisioned as well so you can do a uefi boot. Even if you arent
going to use it right now.
On 30 January 2017 at 03:41, Aristedes Maniatis wrote:
> On 30/1/17 2:20pm, Freddie Cash wrote:
> > And, you may be ab
Well, 100mb might be relevant if you ever want to dual-boot. The relevant
efi file seems to be < 100k
It may go up in size, but I doubt we will see a 100x increase.
/A
On Tue, Jan 31, 2017 at 1:03 PM, krad wrote:
> Its worth noting you should also go for GPT layout and have a 100meg or so
> p
The UEFI standard suggests something large like 100MB. There are a
number of firmware updating programs that run as .efi images. It
would be prudent to allow more than the bare minimum in case you wind
up needing them down the line. boot1.efi is likely to grow
significantly in the future. Maybe no
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Using a fresh install of FreeBSD 11.0-RELEASE-p1, I was trying to use
/usr/bin/svnlite as a ports upgrade.
I've set SVN_UPDATE=yes and SVN=/usr/bin/svnlite in /etc/make.conf IAW the
manfile for make.conf, but running 'make update' within /usr/ports seems to try
portsnap regardless.
I haven't
