On Wed, 16 Jun 2010 13:38:12 +0200 Marc Espie <[email protected]> wrote:
>
> Historically, I did leave LOCKDIR empty in bsd.port.mk.
> Now, I'm wondering if I should define it to something such as
> /tmp/portslocks ?
>
> My assumption was that it would be difficult to be certain that
> dotlocks could be created anywhere. But it seems that most machines
> have local /tmp/ these days. And anyways, those that don't could
> define LOCKDIR =
> to remove the locking mechanism anyways...
>
It might be an uneducated question, but why not place it under pobj?
Do we really want automatic purging on reboot/7-days/whatever?
Do we really want to make an exception to daily for LOCKDIR?
I can't say it's a great idea, but I've been experimenting with a disk
layout like:
a 1G /
b 12G [swap]
c
d 12G /tmp
e 24G /var
f 2G /usr
g 2G /usr/X11R6
h 24G /usr/local
i 2G /usr/src
j 2G /usr/obj
k 32G /usr/pobj
l 2G /usr/ports
m 2G /usr/xenocara
n 2G /usr/xobj
o 128G /home
p 128G /arc
disfiles and built packages get saved to /arc/OpenBSD/... and get
regularly archived/backed-up. If something goes wrong, or I do something
stupid (most likely the latter), the /usr/pobj partition has at least a
fighting chance of saving my ass.
Stuffing the LOCKDIR under pobj (where ever you keep pobj) seems to
make more sense and requires fewer changes.
jcr
--
The OpenBSD Journal - http://www.undeadly.org
