Date: Wed, 24 Jan 2007 16:23:25 -0600 From: "illoai@gmail.com" <illoai@gmail.com> To: "Stevan Tiefert" <stevan-tiefert@t-online.de> Cc: =?ISO-8859-1?Q?Peter_Ankerst=E5l?= <peter@pean.org>, freebsd-questions@freebsd.org Subject: Re: cp to infinity. Message-ID: <d7195cff0701241423l747abcb4x358521aa4e01cc81@mail.gmail.com> In-Reply-To: <200701241306.36527.stevan-tiefert@t-online.de> References: <45B7346F.7090701@pean.org> <cb5206420701240345g6c40735emf5e9287c7e6da6c2@mail.gmail.com> <45B74805.9070802@pean.org> <200701241306.36527.stevan-tiefert@t-online.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24/01/07, Stevan Tiefert <stevan-tiefert@t-online.de> wrote: > Am Mittwoch, 24. Januar 2007 12:50 schrieb Peter Ankerst=E5l: > > > Sure, just don't copy directories into themselves > > > recursively. > > > > How hard could it be to make cp avoid this problem? > > GNU cp does not have any problems with this action. > You need only to write a patch and send it to the developers and voil=E0 > you have what you want! > I doubt it. "name too long (not copied)" Seems a lot more hand-holdy than just consuming all of your inodes and crashing in an undignified manner (which is what I would have bet on). The lesson is: be more careful with your wildcards, this is OS, not AI*. *Doing stupid things just as quickly and efficiently as smart things is proper operating system design, if you ask me. --=20 --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d7195cff0701241423l747abcb4x358521aa4e01cc81>