Date: Mon, 30 Apr 2007 15:10:11 -0400 From: Kris Kennaway <kris@obsecurity.org> To: "[LoN]Kamikaze" <LoN_Kamikaze@gmx.de> Cc: freebsd-ports@freebsd.org Subject: Re: install fails because / is not writeable Message-ID: <20070430191011.GA66625@xor.obsecurity.org> In-Reply-To: <4635907D.3020201@gmx.de> References: <4635907D.3020201@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Apr 30, 2007 at 08:45:17AM +0200, [LoN]Kamikaze wrote: > Once in a while a port fails to upgrade, because it wants to write something in /etc. E.g. perl into /etc/make.conf or other ports into /etc/group. > > On my systems / is normally a read only mount. These ports build fine during a portupgrade and fail during install, leaving most of the port installed, but unregistered (i.e. the package database is broken). > > I think such ports should set something like USE_WRITE_SLASH=yes and refuse to install if / is not writeable. I don't think this is something we should support in ports - that way lies madness (what about systems with non-writable /var? What about systems with /etc on a md? etc). Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070430191011.GA66625>