On Tue, Feb 2, 2010 at 10:38 AM, Orvar Korvar
wrote:
> Argh, I have to move several TB of data back and forth, and I dont have more
> disk space. There are many people out there, not knowing this. We should tell
> them somehow, in the man page for CIFS or something similar. This is not easy
> t
In sh or ksh or bash:
f6=`echo "\0366\c"` # 0366 is 0xf6 converted to octal
find . -type f \( -name "*${f6}*" -o -name ".*${f6}*" \) -print
should find them, I think...
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
o
On 02/ 2/10 09:38 PM, Orvar Korvar wrote:
ls -b
shows My\344Document\366.doc¨which seems better. I tried to find "*\344*" but
that didnt work.
Some ways I've used in the past:
1) Shell completion (personally, I use tcsh) has helped me out
here. If the name starts with a unique let
On 2 Feb 2010, at 23:08, Calum Benson wrote:
> Would the File System Examiner utility (SUNWfsexam in /release and /dev) help
> in any way here?
(Actually, official name seems to be 'File Encoding Examiner' these days,
despite the historical 'fsexam' package and binary name...)
Cheeri,
Calum.
On 2 Feb 2010, at 15:17, Orvar Korvar wrote:
> I tried find, but couldnt figure out the correct syntax.
>
> Rename them manually, you mean? It is many files. I rather avoid that.
Would the File System Examiner utility (SUNWfsexam in /release and /dev) help
in any way here? Haven't used it fo
ls -b
shows My\344Document\366.doc¨which seems better. I tried to find "*\344*" but
that didnt work.
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
> So I have lots of files with weird characters in the
> name. Those , , etc characters are listed as
> "?", for instance "Making?Food?Recipe.doc". The
> version of CIFS I use, (b125) does not allow listing
> of files with those characters in WinXP clients. I
> must stay with b125 because of issues
>
> This dont work. The "find" outputs nothing at all. Is it possible to
> search for etc? If I search for '\?' there will be no match.
Does ls -b do the trick?
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
This dont work. The "find" outputs nothing at all. Is it possible to search for
etc? If I search for '\?' there will be no match.
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Argh, I have to move several TB of data back and forth, and I dont have more
disk space. There are many people out there, not knowing this. We should tell
them somehow, in the man page for CIFS or something similar. This is not easy
to know if you just want to setup an OpenSolaris server for hom
On Tue, Feb 2, 2010 at 5:32 AM, Orvar Korvar
wrote:
> So I have lots of files with weird characters in the name. Those , ,
> etc characters are listed as "?", for instance "Making?Food?Recipe.doc". The
> version of CIFS I use, (b125) does not allow listing of files with those
> characters in Wi
for i in `find . -name '*\?*' -print` ; do
src=$i;
dst=`echo $i | sed 's;?;-;g'`;
echo mv \'$src\' \'$dst\'
done
you could reduce it to single liner using xargs and sed. above one replaces ?
with - . for safely i inserted echo infront of mv command.
--
This message posted from opensolari
I tried find, but couldnt figure out the correct syntax.
Rename them manually, you mean? It is many files. I rather avoid that.
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
>So I have lots of files with weird characters in the name. Those ,
>, etc characters are listed as "?", for instance
>"Making?Food?Recipe.doc". The version of CIFS I use, (b125) does not
>allow listing of files with those characters in WinXP clients. I must
>stay with b125 because of issues in la
So I have lots of files with weird characters in the name. Those , ,
etc characters are listed as "?", for instance "Making?Food?Recipe.doc". The
version of CIFS I use, (b125) does not allow listing of files with those
characters in WinXP clients. I must stay with b125 because of issues in later
15 matches
Mail list logo