Date: Sat, 22 Jan 2005 01:41:45 +0100 From: Jeremie Le Hen <jeremie@le-hen.org> To: Peter Jeremy <PeterJeremy@optushome.com.au> Cc: Jeremie Le Hen <jeremie@le-hen.org> Subject: Re: Cannot install kernel as user Message-ID: <20050122004145.GF36660@obiwan.tataz.chchile.org> In-Reply-To: <20050121233221.GE36660@obiwan.tataz.chchile.org> References: <20050121151747.GA36660@obiwan.tataz.chchile.org> <50158.208.4.77.66.1106323175.squirrel@208.4.77.66> <20050121183546.GC68808@cirb503493.alcatel.com.au> <20050121233221.GE36660@obiwan.tataz.chchile.org>
index | next in thread | previous in thread | raw e-mail
> Well, firstly I wanted to introduced the NO_INSTALLCHOWN variable as I
> said in my previous mail, preventing install(8) from doing a chown(2)
> on the installed file (kernel or module). But I finally decided to
> use a variable named INSTALLCHOWN which will contain "-o user -g group".
> This is more flexible and reduces the patch to its simplest form.
Sorry I'm quite tired, I realize I didn't give a good explanation.
INSTALLCHOWN will default to
o "-o root -g wheel" when installing kernel,
o "-o ${KMODOWN} -g {KMODGRP}" when installing module.
It can be overrided to whatever you want and in particular, it may
be set to nothing when you want to install as user (no chown(2)
performed).
--
Jeremie Le Hen
jeremie@le-hen.org
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050122004145.GF36660>