Date: Wed, 07 Sep 2016 22:09:47 -0700 From: perryh@pluto.rain.com (Perry Hutchison) To: wblock@wonkity.com Cc: freebsd-questions@freebsd.org Subject: Re: "gpart add" falsely claiming "No space left on device" Message-ID: <57d0f29b.3QNvCze7LJDzs0SU%perryh@pluto.rain.com> In-Reply-To: <alpine.BSF.2.20.1609070643120.24506@wonkity.com> References: <57ce6e64.EITkODjuwy6pZ4L%2B%perryh@pluto.rain.com> <alpine.BSF.2.20.1609060814030.1903@wonkity.com> <57cf9b95.Zj/JGHeshaKL6Zr5%perryh@pluto.rain.com> <alpine.BSF.2.20.1609070643120.24506@wonkity.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Warren Block <wblock@wonkity.com> wrote: > What does the man page need? For starters, default values for -b, -s, -t, and -i in "gpart add". (I guess -i defaults to "lowest not currently in use", but what about the others?) List of what-all "attributes" can be set and what they do. Explanation of when one would use -b vs. -p in "gpart bootcode" since they are apparently different ways of specifying where the bootcode comes from (but then your example uses both?) Description of how to show the current state of the provider vs what it would look like if pending changes were committed. > More examples? > > http://www.wonkity.com/~wblock/docs/html/disksetup.html That could do with some explanations of where the "magic numbers" came from, e.g. the "-b 40" in the gpboot partition and the "-b 1M" in gprootfs. I suppose there must be some reason for leaving those 3.0k and 492k free spaces around gpboot, but it isn't obvious.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57d0f29b.3QNvCze7LJDzs0SU%perryh>