From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Fri, 18 Sep 2020 13:48:19 +0300 From: "Dmitry V. Levin" To: Arseny Maslennikov Message-ID: <20200918104818.GB29951@altlinux.org> References: <9bca7626b593f896de4283cba2d6290ec99eb4f2.1576183643.git.legion@altlinux.org> <20200917131236.GK286846@cello> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200917131236.GK286846@cello> Cc: devel@lists.altlinux.org, Alex Gladkov Subject: Re: [devel] [PATCH hasher-priv v1 1/3] Makefile X-BeenThere: devel@lists.altlinux.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: ALT Linux Team development discussions List-Id: ALT Linux Team development discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2020 10:48:19 -0000 Archived-At: List-Archive: List-Post: On Thu, Sep 17, 2020 at 04:12:36PM +0300, Arseny Maslennikov wrote: > On Fri, Dec 13, 2019 at 12:42:03PM +0100, Alex Gladkov wrote: > > diff --git a/hasher-priv/Makefile b/hasher-priv/Makefile > > index a815e9e..82aa385 100644 > > --- a/hasher-priv/Makefile > > +++ b/hasher-priv/Makefile > > @@ -11,7 +11,7 @@ VERSION = $(shell sed '/^Version: */!d;s///;q' hasher-priv.spec) > > HELPERS = getconf.sh getugid1.sh chrootuid1.sh getugid2.sh chrootuid2.sh > > MAN5PAGES = $(PROJECT).conf.5 > > MAN8PAGES = $(PROJECT).8 hasher-useradd.8 > > -TARGETS = $(PROJECT) hasher-useradd $(HELPERS) $(MAN5PAGES) $(MAN8PAGES) > > +TARGETS = $(PROJECT) hasher-privd hasher-useradd $(HELPERS) $(MAN5PAGES) $(MAN8PAGES) > > To everyone: While the name "hasher-privd" minimises the amount of > renaming we have to do, it is too long a name, given that /proc/%d/comm > for each task is up to 16 bytes long on Linux, Why should we care about /proc/%d/comm limitations? Is this really an issue? -- ldv