Hi Folks,

Thanks to all who replied on and off List, and yes to confirm the reason I
targeted ports mailing list was to get feedback from those who regularly
develop  on OpenBSD, and have to deal with 3rd party ports / packages,

  my old developer machine gave up the ghost and the legendary Kurtm@ had
helped me set it up years ago and told me all the partition sizes as I was
installing (thanks Kurtm)  but I never really took note of /etc/fstab and
just kept updating over the years...

Thanks again, everyone

Tom Smyth




On Tue, 20 Oct 2026 at 08:33, Stuart Henderson <[email protected]> wrote:

> On 2026/10/19 20:24, Thomas Frohwein wrote:
> > On Tue, 20 Oct 2026 01:24:23 +0100
> > Tom Smyth <[email protected]> wrote:
> >
> > > Folks,
> > >
> > > Just wondering is there any suggested disk layouts / partition sizes
> > > for Open BSD Dev boxes..
> > >
> > > any advice / insights would be very welcome
>
> Since this is ports@ I'll assume a ports focus.
>
> >
> > Hi Tom,
> >
> > If you mean developing ports, I would suggest tweaking the automatic
> > layout to set up a dedicated partition for /usr/ports. Depending on
> > what types of ports and how many, you many need a couple of dozen GB
> > space on it.
> >
> > The defaults for /usr/src and /usr/obj should be sufficient. I think I
> > usually double them when I have plenty of space, just to future-proof,
> > but that may be being overly cautious.
>
> I strongly recommend that your work dir for ports builds (WRKOBJDIR) is
> a partition that doesn't have anything important - there's often a lot
> of churn on it during a build and when you hit a kernel crash it's often
> left in a bad state. I tend to set WRKOBJDIR (in mk.conf) to either
> /usr/obj/ports on an embiggened /usr/obj, or a totally separate /pobj.
>
> For my main dev machine I have 48G /usr/obj with USE_CCACHE=Yes and
> ccache set to allow 5G, and I don't usually run into space problems
> during builds (though if working on huge ports often, more might sense).
>
>

-- 
Kindest regards,
Tom Smyth.

Reply via email to