From owner-freebsd-gnome@FreeBSD.ORG Mon May 10 17:31:56 2004 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE14816A4CE; Mon, 10 May 2004 17:31:56 -0700 (PDT) Received: from lakermmtao12.cox.net (lakermmtao12.cox.net [68.230.240.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2A3543D5A; Mon, 10 May 2004 17:31:55 -0700 (PDT) (envelope-from mezz7@cox.net) Received: from mezz.mezzweb.com ([68.103.32.140]) by lakermmtao12.cox.net (InterMail vM.6.01.03.02 201-2131-111-104-20040324) with ESMTP id <20040511003154.ZXDO164.lakermmtao12.cox.net@mezz.mezzweb.com>; Mon, 10 May 2004 20:31:54 -0400 To: Stacey Roberts References: <200405102310.i4ANAScY040094@freefall.freebsd.org> <20040510231734.GR15500@toxic.magnesium.net> <20040511001224.GP393@crom.vickiandstacey.com> Message-ID: From: Jeremy Messenger Content-Type: text/plain; format=flowed; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Date: Mon, 10 May 2004 19:32:42 -0500 In-Reply-To: <20040511001224.GP393@crom.vickiandstacey.com> User-Agent: Opera7.23/Linux M2 build 518 cc: gnome@freebsd.org Subject: Re: ports/66439: portupgrade -R pilot-link-0.11.8_2 fails with latest cvsup X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 May 2004 00:31:56 -0000 On Tue, 11 May 2004 01:12:24 +0100, Stacey Roberts wrote: > Hello Adam, > Don't get me wrong here Adam.., I'm *not* looking to get into an > argument here on this.., > > ----- Original Message ----- > From: "Adam Weinberger " > To: To Stacey Roberts > Date: Tue, 11 May, 2004 00:17 BST > Subject: Re: ports/66439: portupgrade -R pilot-link-0.11.8_2 fails with > latest cvsup > >> I clearly remember spending over a week going through this exact problem >> with you months and months ago. >> >> After about 10 thousand emails from me saying the same thing over and >> over, you admitted that you may have been creating users with >> /nonexistent as their $HOME because that's what you saw listed in stuff >> for ports. >> >> Ports didn't create that directory. >> >> You did. >> > > Checking the thread that Mezz kindly posted.., I said that the > /nonexistent dir was created when I created machine accounts for samba > which is running on that machine.., > > However, on *every* other FreeBSD machine here including workstations, > /nonexistent is listed in /etc/passwd as the home dir for gdm, nobody, > www and pop. What am I supposed to do for those accounts? I am not sure if you understand. /nonexistent is supposed to be meant 'not exist', get it? It won't hurt your /etc/passwd that has the /nonexistent, they will understand that it is not exist. If I don't explain that well, so others w/ skilled English grammar might/will explain more. Cheers, Mezz > I'm not having a dig at you or anyone else here, but if this is your way > of telling me to go away with my problems, then fair enough. I'd even > withdraw the PR (if possible) if that would make you feel any better.., > > > Regards, > > Stacey > >> The behaviour of the ports is exactly as it should be. It's kindof >> ridiculous to create a directory named /nonexistent, when the name >> clearly implies that it shouldn't exist. >> > >> # Adam >> >> >> -- >> Adam Weinberger >> adamw@magnesium.net || adamw@FreeBSD.org >> adamw@vectors.cx || adamw@gnome.org >> http://www.vectors.cx -- mezz7@cox.net - mezz@FreeBSD.org bsdforums.org 's moderator, mezz.