Date: Fri, 20 Dec 2002 14:11:43 +0000 From: Ceri Davies <setantae@submonkey.net> To: Andrew Cutler <andrew@1stelement.com> Cc: freebsd-questions@freebsd.org Subject: Re: chown broken?? Message-ID: <20021220141143.GA6893@submonkey.net> In-Reply-To: <1040392764.921.76.camel@localhost> References: <1040390551.921.36.camel@localhost> <20021220132902.GF22383@pcwin002.win.tue.nl> <1040392764.921.76.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Dec 21, 2002 at 12:59:24AM +1100, Andrew Cutler wrote: > Thanks for everyone's quick responses. I'm not going to delve any deeper > as to why chown, chmod etc match .. for .* when other commands do not. > I'm sure this is ground that has been covered many times before. And I'm > sure its the sort of mistake that you only make once. (In fact now that > I think about it I'm sure there is a discussion of this issue in FreeBSD > Unleashed/SAMS) And in starting this thread I feel like I've just > committed some sort of UNIX newbie fopar. :) > > So without further embarrassment, does anyone have any idea on what is > the quickest and easiest way to correct the file ownership issues that > I'm currently experiencing ? mtree -U [insert other options here] Ceri -- May the ire of my ancestors bring your last day! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021220141143.GA6893>