Aha got it. So then I'll just learn that sector 80 and up are "safe" for "user data", and it's up to all users to take care that any non-UFS/swap/RAID partitions never go below 80.
But how does the behavior of the first added partition by default overlapping the disklabel "save butts" - Does this behavior fill any practical function today, and also when the user (me) makes there be no overlap, could/do I break anything? Just to really understand the practical impact. 2015-10-07 1:21 GMT+08:00 Theo de Raadt <dera...@cvs.openbsd.org>: > > Wait, sorry - so the disklabel tool says that the c partition starts at > > offset 0 , that's logical indeed as data always starts at offset 0. > > > > By some reason, the disklabel tool however doesn't want partitions on the > > first 64 sectors (console dump below), i.e. on the first 32KB (why?). > > Modern disks are showing up with sector sizes > 512 bytes. This is an > alignment strategy, to future proof things.
