From owner-freebsd-questions@FreeBSD.ORG Sat Oct 11 15:14:46 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7FE71065693 for ; Sat, 11 Oct 2008 15:14:46 +0000 (UTC) (envelope-from smohideen@mx2.labs.rootshell.ws) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.184]) by mx1.freebsd.org (Postfix) with ESMTP id 5972F8FC20 for ; Sat, 11 Oct 2008 15:14:46 +0000 (UTC) (envelope-from smohideen@mx2.labs.rootshell.ws) Received: by ti-out-0910.google.com with SMTP id d27so502546tid.3 for ; Sat, 11 Oct 2008 08:14:45 -0700 (PDT) Received: by 10.110.49.6 with SMTP id w6mr3081335tiw.9.1223738084651; Sat, 11 Oct 2008 08:14:44 -0700 (PDT) Received: from localhost ([123.236.53.245]) by mx.google.com with ESMTPS id 14sm6544373tim.17.2008.10.11.08.14.40 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 11 Oct 2008 08:14:43 -0700 (PDT) Date: Sun, 12 Oct 2008 02:20:52 +0530 From: Shakul M Hameed To: Jeremy Chadwick Message-ID: <20081011205052.GA6318@freebsdbox> References: <20081011173613.GA7326@freebsdbox> <20081011180308.GA7094@freebsdbox> <20081011123826.GA62390@icarus.home.lan> <20081011195131.GA931@freebsdbox> <20081011144711.GA64861@icarus.home.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081011144711.GA64861@icarus.home.lan> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: cvsup 7.0 STABLE checkout failure X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Oct 2008 15:14:46 -0000 On Sat, Oct 11, 2008 at 07:47:11AM -0700, Jeremy Chadwick wrote: > On Sun, Oct 12, 2008 at 01:21:31AM +0530, Shakul M Hameed wrote: > > > 1) Your setup looks very custom. I see SMB/CIFS in use, and you're > > > using a non-standard directory for the cvsup CVS data (the default is > > Yes, I am using mount_smbfs to mount a network harddrive to store all my devel code. > > I don't want to overcrowd the the root disk > > I'm left wondering if there are some permissions or ownership issues as > a result of this. > > > I am using X11 cvsup stable-supfile. This is the snapshot of my modified cvsup file > > ------------------------------------------------ > > # Defaults that apply to all the collections > > # > > # IMPORTANT: Change the next line to use one of the CVSup mirror sites > > # listed at http://www.freebsd.org/doc/handbook/mirrors.html. > > *default host=cvsup3.de.FreeBSD.org > > *default base=/usr/home/moin/smbmount/code/SUPDB/ > > *default prefix=/usr/home/moin/smbmount/code/src/ > > # The following line is for 7-stable. If you want 6-stable, 5-stable, > > # 4-stable, 3-stable, or 2.2-stable, change to "RELENG_6", "RELENG_5", > > # "RELENG_4", "RELENG_3", or "RELENG_2_2" respectively. > > *default release=cvs tag=RELENG_7 > > *default delete use-rel-suffix > > > > # If you seem to be limited by CPU rather than network or disk bandwidth, try > > # commenting out the following line. (Normally, today's CPUs are fast enough > > # that you want to run compression.) > > *default compress > > > > ## Main Source Tree. > > # > > # The easiest way to get the main source tree is to use the "src-all" > > # mega-collection. It includes all of the individual "src-*" collections. > > # Please note: If you want to track -STABLE, leave this uncommented. > > src-all > > ------------------------------------------------ > > I have no idea what an "X11 cvsup stable-supfile" is, so I assume you > mean you've used /usr/share/examples/cvsup/stable-supfile as a template > supfile, but have your own somewhere else. > > The reason I was confused: you first stated you're using the ones in > /usr/share/examples/cvsup, and I assumed that mean you were using it > directly. You shouldn't modify any files in /usr/share/examples, as > they will be replaced/overwritten during installworld. > > Your pasted supfile looks fine, however. > > > > 2) Check permissions and ownership of all directories leading up to > > > /usr/home/moin/smbmount/code/SUPDB/sup/src-all. Yes, check every single > > > one. > > Please do this. > > > > 3) Ensure your umask is 022 before starting cvsup. This could be a side > > > result of item #2. > > umask is 0022 > > > > > > 4) I'm not sure why you're using cvsup on a 7.x box when csup comes with > > > the base system. > > > > I don't know why ? :-) . But I did as it was listed in the FreeBSD handbook. > > Are you sure? http://www.freebsd.org/doc/en/books/handbook/cvsup.html -- see > the first "Note:" paragraph. As a newbie to FreeBSD, I would rather like to have a single Code Versioning system. Several methods put newbies in dilemma to decide upon the best suitable procedure. I feel there should be one unique source code management system. > > > > I would also try doing this as a last resort: > > > > > > rm -fr /usr/home/moin/smbmount/code/SUPDB/sup/src-all > > > rm -fr /usr/src/* > > > csup -h -L 2 /usr/share/examples/cvsup/stable-supfile > > > > > As a lost resort, I did a "cvsup -g -L2 stable-supfile", with just > > changing the HOST part without changing other entries in > > stable-supfile, and I was successful to download the code. > > I don't see how that would fix or change anything. In fact, I'm fairly > certain it doesn't. > > The error you are receiving from cvsup is telling you "I tried to rename > a file, but couldn't". This often implies a permissions or ownership > thing. Since the directory you're storing stuff in is on an SMB/CIFS > share, I cannot help but wonder if that's the cause of the problem > (somehow). Jeremy, as pointed by "N.J. Mann" recently in a reply in this thread, there is a semicolon in the filename where the rename faliure happened. Because the file "checkouts.cvs:RELENG_7" had ":" in it, which was not created subsequently due to SMB limitation for ":"-based filenames. Because this the cvsup checked-out halted at this point. Morever, as indicated by "Sean " the case-insensitiveness would lead to missing files. I think, I should format my Network drive to NFS to make it really UNIX friendly. "N.J. Mann" quoted .... >>>>> Does the file system that you are using support colons (:) in file names? If it is FAT, HPFS or NTFS, or a derivative of one of those, it probably doesn't and I suspect that is your problem. Of course I could be very wrong. ;-) >>>>> - Moin > > > Currently, I am trying out to figure why the customised way is failing. > > I see nothing wrong with your supfile. > > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | -- - Moin