From owner-freebsd-current Sat Feb 27 6:42:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 021AC150A7 for ; Sat, 27 Feb 1999 06:42:15 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.200]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA15FA; Sat, 27 Feb 1999 15:41:57 +0100 Received: from daemon.ninth-circle.org (abaddon@daemon.ninth-circle.org [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id PAA51408; Sat, 27 Feb 1999 15:42:18 +0100 (CET) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <10314.920123606@verdi.nethelp.no> Date: Sat, 27 Feb 1999 15:42:17 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: sthaug@nethelp.no Subject: Re: Really! strange uid value Cc: current@freebsd.org, mi@kot.ne.mediaone.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Feb-99 sthaug@nethelp.no wrote: >> Jeroen Ruigrok/Asmodai once stated: >> >> => -rw-r--r-- 1 4294967294 wheel 389120 Feb 14 23:54 >> pdksh.core.xclink >> >> =this is exactly what I got when I tried to compile some things over >> NFS. >> =The created directory and files were also like this: >> = >> =1 drwxr-xr-x 3 4294967294 wheel - 512 Feb 15 21:09 aout/ >> = >> =funny, the same value. There is something left out very fundamentally >> =somewhere. >> >> Just FYI. This number is 0xFFFFFFFE in hex... A search for this number >> through the sources does not bring anything under NFS itself, though the >> following may give a clue: > > Remember that the "nobody" user is uid 65534 (0xfffe). The signed > extension of this to 32 bits is 0xfffffffe. Maybe you're seeing uid 0 > being translated to 65534 (due to NFS) and then sign extended. Could be, but that is still not correct behaviour as far as my knowledge goes. It should not get sign extended IMHO. Am I correct in assuming this (call to the more knowledgeable ones)? --- Jeroen Ruigrok van der Werven http://www.freebsdzine.org> asmodai(at)wxs.nl The idea does not replace the work... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message