Date: Thu, 08 Sep 2016 16:18:33 -0500 From: Brandon J. Wandersee <brandon.wandersee@gmail.com> To: Perry Hutchison <perryh@pluto.rain.com> Cc: wblock@wonkity.com, freebsd-questions@freebsd.org Subject: Re: "gpart add" falsely claiming "No space left on device" Message-ID: <86wpimm6om.fsf@WorkBox.Home> In-Reply-To: <57d0f29b.3QNvCze7LJDzs0SU%perryh@pluto.rain.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> <57d0f29b.3QNvCze7LJDzs0SU%perryh@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Perry Hutchison writes: > 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?) The defaults are exactly what you'd expect them to be. '-b' defaults to the start of the disk. '-i' defaults to the lowest available integer. '-s' defaults to everything available. '-t' default to nothing, because it would be senseless to assume the type of a partition; gpart(8) will exit with an error if you don't provide it. > List of what-all "attributes" can be set and what they > do. See "ATTRIBUTES." > 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?) '-b' and '-p' specify different values. '-b' specifies what is written; '-p' specifies how and where. How they're used depends on your partition scheme and motherboard. See "BOOTSTRAPPING." > Description of how to show the current state of the provider vs what > it would look like if pending changes were committed. I don't know if this is possible. I believe it's assumed that the user/administrator has---or at least *should* have---a good idea of what state the disk is in before they start messing with the existing (presumably good) partition table. > I suppose there must be some reason for leaving those > 3.0k and 492k free spaces around gpboot, but it isn't obvious. Partition alignment. -- :: Brandon J. Wandersee :: brandon.wandersee@gmail.com :: -------------------------------------------------- :: 'The best design is as little design as possible.' :: --- Dieter Rams ----------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86wpimm6om.fsf>