[no subject]
Apologies to everyone who will get this e-mail twice. My previuos attempt usig different email account has been bounced back by hub.freebsd.org. I reported this bug to Julian and he promised to fix it soon. Unfortunately, that didn't happen yet. In a meantime, I am using the patch attached. Of course I cannot be sure that we are seeing the same bug because you didn't provide any details. _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp nfs.diff Description: Binary data
RE: NFS crash in -current
My previos mail a) is missing a Subject b) contains typo in the patch, (td ? td-td_proc : NULLi)^ Unwanted 'i' is here :( Apologies to everyone again. I was in a bit of a hurry when sending previos messages. _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cp -d dir patch for review (or 'xargs'?)
On 21-Apr-2001 Sheldon Hearn wrote: On Sat, 21 Apr 2001 14:06:04 +0100, Brian Somers wrote: How do you do this in a script: cd /topdir; find . -type f | xargs -i {} cp {} /otherdir/. for i in `find /path/to/source -type f`; do cp $i /path/to/dest/ done What's all the fuss about? It looks like above construct will fail horribly if any of the files in /topdir have names with spaces in them. Think MP3 collections :) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- E-Mail: Alexander Kabaev [EMAIL PROTECTED] Date: 21-Apr-2001 Time: 10:49:59 -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cp -d dir patch for review (or 'xargs'?)
Your comments have nothing to do with the issue at hand. Just wrap the first argument to cp in double-quotes, i.e. cp "$i" The point is, why bastardize tools to cope with areas beyond their focus and well within the focus of other tools? Ciao, Sheldon. Sorry for butting in. Adding new non-portable functionality to solve the problem which could be adequitely taken care of using existing and well known techniquies is not appropriate, I completely agree with you on that. -- E-Mail: Alexander Kabaev [EMAIL PROTECTED] Date: 21-Apr-2001 Time: 11:08:13 -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message