On Fri, 18 Sep 2020 13:48:19 +0300 Dmitry V. Levin wrote:
> 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?

I agree. hasher-privd is readable and understandable name also
featuring less renames.

Best regards,
Andrew Savchenko