On Fri, Jul 24, 2020 at 09:52:29AM -0400, Greg Wooledge wrote:
[...]
> I don't know of any specific term for a directory's physical
> manifestation, other than "directory".
>
> In the olden days, a directory was basically a series of 16-byte
> records (14 bytes for the filename, 2 bytes for the
On Fri, Jul 24, 2020 at 09:56:27AM -0400, The Wanderer wrote:
> On 2020-07-24 at 09:50, to...@tuxteam.de wrote:
[...]
> Since writing that, I've had occasion to remember the term 'dirent',
> which I think is more the in-memory representation of a directory than
> the on-disk representation, but m
On 2020-07-24 at 09:50, to...@tuxteam.de wrote:
>
> On Fri, Jul 24, 2020 at 09:42:24AM -0400, The Wanderer wrote:
>
>> On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
>>> Nitpick: the directory entry is the one carrying the name.
>>
>> I had the impression that even a directory is stored in/as
On Fri, Jul 24, 2020 at 09:42:24AM -0400, The Wanderer wrote:
> On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
>
> > On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
> >
> >> On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
> >>
> >>> Sounds like a case where directly
On Fri, Jul 24, 2020 at 09:42:24AM -0400, The Wanderer wrote:
On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
Sounds like a case where directly editing the underlying
On Fri, Jul 24, 2020 at 09:42:24AM -0400, The Wanderer wrote:
> On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
>
> > On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
> >
> >> On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
> >>
> >>> Sounds like a case where directly
On 2020-07-24 at 09:22, to...@tuxteam.de wrote:
> On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
>
>> On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
>>
>>> Sounds like a case where directly editing the underlying device,
>>> to modify inode-or-equivalent contents s
On Fri, Jul 24, 2020 at 07:54:27AM -0400, Greg Wooledge wrote:
> On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
> > Sounds like a case where directly editing the underlying device, to
> > modify inode-or-equivalent contents such that the slash is no longer
^
Nitpick:
On Fri, Jul 24, 2020 at 07:49:26AM -0400, The Wanderer wrote:
> Sounds like a case where directly editing the underlying device, to
> modify inode-or-equivalent contents such that the slash is no longer
> there, might even be *advisable*.
Yeah, some sort of direct hex-edit on the unmounted file sy
ored
>> data in the inode.
>
> The main way that one gets a filename containing a '/' character in
> real life is by discovering a bug somewhere.
>
> I've personally seen it once, on an old HP-UX system that was acting
> as an NFS server for some Mac clie
life is by discovering a bug somewhere.
I've personally seen it once, on an old HP-UX system that was acting
as an NFS server for some Mac clients (long before Mac OS X). Apparently
the NFS server allowed the clients to create filenames with slashes in
them, since that's legal on Mac OS 9
>>> Yes. Unfortunately Systemd decided to forbid '/' in unit names,
You can probably work around that by using '⁄', for example ;-)
Stefan
any checksums,
hashes, or other validity data that may exist, never mind update them.)
The result, unsurprisingly enough, is:
ls: reading directory '/mnt/loop/': Input/output error
because neither ls nor basically anything in the stack it sits on
supports this, at least not with an ext
On Sat, Feb 11, 2012 at 11:47:14AM -0700, Andreas Dilger wrote:
>
> Looks interesting and useful... I wonder if it makes sense to include
> this into e2fsprogs at some point, so that it is available when users
> need it most...
We'll need to talk to the author about that. At the very least it
w
On 2012-02-11, at 11:30 AM, Ted Ts'o wrote:
> On Sat, Feb 11, 2012 at 05:33:30PM +, Rudolf Zran wrote:
>> Hi List!
>>
>> In an offlist reply someone recommended me ext4magic (see
>> http://developer.berlios.de/projects/ext4magic ).
>
> I wasn't familiar with ext4magic, so thanks for recommend
On Sat, Feb 11, 2012 at 05:33:30PM +, Rudolf Zran wrote:
> Hi List!
>
> In an offlist reply someone recommended me ext4magic (see
> http://developer.berlios.de/projects/ext4magic ).
I wasn't familiar with ext4magic, so thanks for recommending it.
After taking a quick look at its wiki page, it
Hi List!
In an offlist reply someone recommended me ext4magic (see
http://developer.berlios.de/projects/ext4magic ).
Like magic it recovered complete directory hierarchies with filenames,
timestamps, even ownership and permissions for more than 300GB of the
deleted data.
I can recommend this to
I, too, very recently lost all the files on a 1000 Gbyte drive,
because of a stupid blunder in attempting to format a USB flash drive.
>From this, I learned two things:
(1) Even a simple listing of the contents of a drive would be
invaluable in attempting to restore the drive from other sources.
On 02/10/2012 06:07 PM, Rudolf Zran wrote:
Hello Bernd!
I have written some tools in the past to recover the file structure of
an over-formated ext3/ext4 device based on directory blocks.
With some tweaks it should be able to assign the file#inode_numbers in
lost+found to a directory structure
to set expectations, things that you might do that tried to look
for directory blocks, etc., *might* give you more useful filenames as
opposed to random inode numbers in lost+found, but it's unlikely to
recover any more *files*. It sounds most of your files were located
in part of the inode table
contained useful content.
Just to set expectations, things that you might do that tried to look
for directory blocks, etc., *might* give you more useful filenames as
opposed to random inode numbers in lost+found, but it's unlikely to
recover any more *files*. It sounds most of your files were lo
Hello Ted!
>> I recently damaged an ext4 partition by accident
[...]
>> Maybe somebody knows a good method to just "repair" the
>> ext4-structure from the remaining part of the partition?
>
> Have you tried just simply running e2fsck, specifying an alternate superblock?
Yes of course I tried,
On Feb 9, 2012, at 11:29 AM, Rudolf Zran wrote:
> Hi everybody!
>
> I recently damaged an ext4 partition by accident (mistakenly forced
> a RAID sync with another partition onto it, which I realized after
> about 3% completion). As a result the beginning of the ext4 partition
> seems to be overw
Hello Bernd!
> I have written some tools in the past to recover the file structure of
> an over-formated ext3/ext4 device based on directory blocks.
> With some tweaks it should be able to assign the file#inode_numbers in
> lost+found to a directory structure.
> Problem is that I'm rather busy
On 02/09/2012 10:22 PM, Rudolf Zran wrote:
Hello Andreas!
[ext4 partition overwritten with garbage at the beginning]
* photorec from the testdisk package recoveres, luckily!, about 500GB of
data. Though the content seems to be pretty reasonable, no filenames
are recovered, since
rds ( see https://pzt.me/42yk and
> https://pzt.me/3frg )
>
> * "fsck.ext4 -b $SBOK -B 4096 -v -y /dev/loop0" recoveres after a long
> time.
> Filesystem is mountable. Root is empty besides lost+found folder,
> which contains about 300GB mostly useless data: Millions o
Hello Andreas!
[ext4 partition overwritten with garbage at the beginning]
>> * photorec from the testdisk package recoveres, luckily!, about 500GB of
>> data. Though the content seems to be pretty reasonable, no filenames
>> are recovered, since photorec oper
om content.
The ability to recover from something like this depends heavily on where
the directory structure and inodes were located. Filesystems tend to use
the start of the disk first, because it has the best performance (about 2x
as fast as the end).
> * photorec from the testdisk packa
ns, useless names and some random content.
* photorec from the testdisk package recoveres, luckily!, about 500GB of
data. Though the content seems to be pretty reasonable, no filenames
are recovered, since photorec operates without using filesystem knowledge.
Do you see any chances (besides consultin
kei...@strucktower.com wrote:
> keith@t520:~/evesdb4/mp3/misc$cp -vr /media/cdrom0/*.mp3 ./
> `/media/cdrom0/01 Zephyr & I.mp3' -> `./01 Zephyr & I.mp3'
> cp: reading `/media/cdrom0/01 Zephyr & I.mp3': Input/output error
> cp: failed to extend `./01 Zephyr & I.mp3': Input/output error
> `/media/cdr
output error
> cp: failed to extend `./01 All I Want To Do.mp3': Input/output error
>
I would try copying a few files one-by-one to make sure you know for sure which
files cp is choking on. You might also try using rsync, to see if it
handles things any differently.
Silly question: does vfa
output error
`/media/cdrom0/01 All I Want To Do.mp3' -> `./01 All I Want To Do.mp3'
cp: reading `/media/cdrom0/01 All I Want To Do.mp3': Input/output error
cp: failed to extend `./01 All I Want To Do.mp3': Input/output error
I am assuming (maybe incorrectly) that the proble
On Wednesday 10 August 2011 19:04:57 Mike McClain wrote:
>
>
> > myuser@mysytem:~/path-name-of-unicode-files$ rename -n 's/\x{202A}//' *
> >
> > I get no output although x{202A} is definitely the first char in the
> > filename. This definitely needs more than a cursory view into perl -
> > exact
> myuser@mysytem:~/path-name-of-unicode-files$ rename -n 's/\x{202A}//' *
>
> I get no output although x{202A} is definitely the first char in the filename.
> This definitely needs more than a cursory view into perl - exactly what I
> wanted to avoid.
> Maybe I better post in a perl mailinglist
o remove unicode control
> > > characters like U+202A; U+202C; U+200F from filenames.
> > > I found lots of examples to do this programmatically with python, perl,
> > > even for VB and Java.
> > > I was looking to do this with bash, find, grep and/or even sed beca
o remove unicode control
> > > characters like U+202A; U+202C; U+200F from filenames.
> > > I found lots of examples to do this programmatically with python, perl,
> > > even for VB and Java.
> > > I was looking to do this with bash, find, grep and/or even sed beca
On Tue, Aug 09, 2011 at 01:24:46PM -0700, Mike McClain wrote:
> On Tue, Aug 09, 2011 at 12:42:18PM -0400, Eike Lantzsch wrote:
> > Hi:
> >
> > For some time I'm looking to find a method to remove unicode control
> > characters like U+202A; U+202C; U+200F fro
On Tue, Aug 09, 2011 at 12:42:18PM -0400, Eike Lantzsch wrote:
> Hi:
>
> For some time I'm looking to find a method to remove unicode control
> characters like U+202A; U+202C; U+200F from filenames.
> I found lots of examples to do this programmatically with python, perl, eve
Hi:
For some time I'm looking to find a method to remove unicode control
characters like U+202A; U+202C; U+200F from filenames.
I found lots of examples to do this programmatically with python, perl, even
for VB and Java.
I was looking to do this with bash, find, grep and/or even sed beca
lee wrote:
> There's a difference between "touch -- file*" and "touch "file*"", isn't
> there?
Yes there is, and you can see the difference when you have one or more
files, in the current directory, whose names start with "file". (Hint:
precede or replace 'touch' with 'echo'.)
Chris
--
To UNS
Scott Ferguson writes:
> On 27/06/11 00:55, William Hopkins wrote:
>> On 06/26/11 at 09:45pm, Scott Ferguson wrote:
>>> On 26/06/11 19:25, Tom Furie wrote:
On Sat, Jun 25, 2011 at 03:20:13PM +1000, Scott Ferguson wrote:
> On 25/06/11 10:16, lee wrote:
>>>
>>>
>>> What does the "--" do??
On Mon, 27 Jun 2011 10:53:55 +0200, Raffaele Morelli wrote:
> 2011/6/24 Camaleón
>
>> On Fri, 24 Jun 2011 12:05:17 +0200, Raffaele Morelli wrote:
>>
>> > I am experiencing serious problems with my external HD, I can't
>> > create/write filenames c
>>> To give a silly example, a file named "-rf *" or "rm -rf *"
lee wrote:
>> I defy you to create a file with those name ;-p
touch './-rf *'
The ./ prefix is the key to removing it afterwards, too.
Chris
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "u
2011/6/24 Camaleón
> On Fri, 24 Jun 2011 12:05:17 +0200, Raffaele Morelli wrote:
>
> > I am experiencing serious problems with my external HD, I can't
> > create/write filenames containing accented chars, especially when
> > copying music from my amarok collecti
On 27/06/11 00:55, William Hopkins wrote:
> On 06/26/11 at 09:45pm, Scott Ferguson wrote:
>> On 26/06/11 19:25, Tom Furie wrote:
>>> On Sat, Jun 25, 2011 at 03:20:13PM +1000, Scott Ferguson wrote:
On 25/06/11 10:16, lee wrote:
>>
>>
>> What does the "--" do??
>
> POSIX standard is for -- to
On 06/26/11 at 09:45pm, Scott Ferguson wrote:
> On 26/06/11 19:25, Tom Furie wrote:
> > On Sat, Jun 25, 2011 at 03:20:13PM +1000, Scott Ferguson wrote:
> >> On 25/06/11 10:16, lee wrote:
>
>
>
> > You can't have tried very hard then: 'touch -- "-rf *"'.
> >
>
> >
> > Cheers,
> > Tom
> >
>
>
On 26/06/11 19:25, Tom Furie wrote:
> On Sat, Jun 25, 2011 at 03:20:13PM +1000, Scott Ferguson wrote:
>> On 25/06/11 10:16, lee wrote:
> You can't have tried very hard then: 'touch -- "-rf *"'.
>
>
> Cheers,
> Tom
>
You are (also) correct.
Turns out there's a number of ways to do that.
Wha
t4 - the system kept coming up with "not found" messages when
attempting to move filenames which had ISOcharacter set accented
characters.
Fortunately I've managed to rename them using Picard and MusicBrainz -
there's far too many to do by hand.
This thread was created by someone
On Sat, Jun 25, 2011 at 03:20:13PM +1000, Scott Ferguson wrote:
> On 25/06/11 10:16, lee wrote:
> > To give a silly example, a file named "-rf *" or "rm -rf *"
>
> I defy you to create a file with those name ;-p
> NOTE: I've tried. No point in it just being an untested opinion.
You can't have t
Andrew McGlashan writes:
> William Hopkins wrote:
>> You should be able to trust rm, at least. Just add -i if you're paranoid.
>
> And if you are more paranoid, fully path rm to ensure no alias is
> changing anything.
There are at least three things involved: rm, the shell and the user. If
the s
William Hopkins wrote:
You should be able to trust rm, at least. Just add -i if you're paranoid.
And if you are more paranoid, fully path rm to ensure no alias is
changing anything.
# which rm
/bin/rm
--
Kind Regards
AndrewM
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
On 26/06/11 00:37, lee wrote:
> lee writes:
>
>
> Save it as "removing.c", adjust the name of the file you want to remove
> and run gcc -Wall -Os -o removing removing.c. Than run ./removing to
> remove the file.
>
>
++1
LMAO :-D
Now *that* is a bigger hammer!
Cheers
--
You know we arme
On 06/25/11 at 07:37pm, lee wrote:
> Eduardo M KALINOWSKI writes:
>
> > Why all the touble?
> >
> > $ rm 'rm -rf *'
> >
> > does the job. Or use a file manager.
>
> Because I don't trust rm or a file manager to do it right and without
> unwanted side effects.
You should be able to trust rm, at
On 06/25/11 at 04:33pm, Scott Ferguson wrote:
> scott@work:~$ mount | grep /disk
> /dev/sdc1 on /media/disk type ext3 (rw,nosuid,nodev,uhelper=hal)
Looks fine..
> scott@work:~$ ls /media/disk/Music/"Various Artists/Amelie - Soundtrack"
> 01 - J'Y Suis Jamias All?.mp3 08 - A Quai.mp3
Eduardo M KALINOWSKI writes:
> Why all the touble?
>
> $ rm 'rm -rf *'
>
> does the job. Or use a file manager.
Because I don't trust rm or a file manager to do it right and without
unwanted side effects.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "uns
Ralf Mardorf writes:
>$ echo test > \*
>$ ls
>* Desktop Downloads hdsp.1
>Any idea how I can get rid of the file named *?
Exactly the same way you created it. With a backslash.
$ rm \*
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Tro
Scott Ferguson writes:
> On 25/06/11 23:57, lee wrote:
>> Should I send a feature request on the kernel package?
>>
>>
>
> Not necessary - the subject has been adequately covered in many posts
> between the original and this one.
The feature I'd request would be that there shall be ways to spe
On 06/25/2011 11:37 AM, lee wrote:
> lee writes:
>
>> ,
>> | lee@yun:~/tmp/naming$ ls -la
>> | insgesamt 52
>> | drwxr-xr-x 2 lee lee 4096 25. Jun 15:48 .
>> | drwx-- 12 lee lee 32768 25. Jun 15:48 ..
>> | -rw-r--r-- 1 lee lee 116 9. Jun 16:35 -rf
>> | -rw-r--r-- 1 lee lee94 7
lee writes:
> You can just rename a file with:
>
> # mv 1307474391 "rm -rf *"
>
> ,
> | lee@yun:~/tmp/naming$ ls -la
> | insgesamt 52
> | drwxr-xr-x 2 lee lee 4096 25. Jun 15:48 .
> | drwx-- 12 lee lee 32768 25. Jun 15:48 ..
> | -rw-r--r-- 1 lee lee 116 9. Jun 16:35 -rf
> | -rw-r--
On 25/06/11 23:57, lee wrote:
> Scott Ferguson writes:
>
>> On 25/06/11 10:16, lee wrote:
>>> Scott Ferguson writes:
>>>
>
> Should I send a feature request on the kernel package?
>
>
Not necessary - the subject has been adequately covered in many posts
between the original and this one.
C
Scott Ferguson writes:
> On 25/06/11 10:16, lee wrote:
>> Scott Ferguson writes:
>>
>>> I don't think the "no white spaces" and "no accented characters"
>>> "rule" is valid in the 21st century. But if some one can put up an
>>> authoritative, and recent, reason I'll reconsider.
>>
>> Since (un
Scott Ferguson writes:
> On 25/06/11 15:56, William Hopkins wrote:
>> On 06/25/11 at 03:36pm, Scott Ferguson wrote:
[...]
>> Any error message? Have you tried mounting with the encoding options
>> as recommended elsewhere?
>
> I may have missed something in the threads - as I don't know how to
On 25/06/11 21:18, Andrew McGlashan wrote:
> Hi,
>
> Scott Ferguson wrote:
> And to stop command history being a problem, I often use the full path
> the files/directories such as:
>rm /tmp/somedir/* /tmp/somedir/.*
Good point. I shall run with scissor no more.
>
> Cheers
> A.
>
Chee
Hi,
Scott Ferguson wrote:
There, we'll have to disagree. Perhaps your shell handles ls
differently. Also you are running as root, I'm not
Yes, well as root, I admit -- quick tests in a special and safe working
directory.
/bin/bash shell
Whatever you do use "*" do so with extreme caution, e
On 25/06/11 19:35, Andrew McGlashan wrote:
> Scott Ferguson wrote:
>
> The first part "*" removed both files AND any other file that might have
> been in the directory.
There, we'll have to disagree. Perhaps your shell handles ls
differently. Also you are running as root, I'm not
scott@work:~/s
Scott Ferguson wrote:
Bigger hammer
scott@work:~/spec$ touch "*" "&"
scott@work:~/spec$ ls -A
* &
scott@work:~/spec$ rm `ls -A`
rm: cannot remove `&': No such file or directory
The first part "*" removed both files AND any other file that might have
been in the directory.
# touch \* \
On 25/06/11 17:15, Andrew McGlashan wrote:
> Hi,
>
> Ralf Mardorf wrote:
>> $ echo test > \*
>> $ ls
>> * Desktop Downloads hdsp.1
>>
>> Any idea how I can get rid of the file named *?
>
> # touch \* \&
> # ls
> * &
> # find . -type f -name "\*" -print0|xargs -0 rm
> # ls
>
>
> # touch
Hi,
Ralf Mardorf wrote:
$ echo test > \*
$ ls
* Desktop Downloads hdsp.1
Any idea how I can get rid of the file named *?
# touch \* \&
# ls
* &
# find . -type f -name "\*" -print0|xargs -0 rm
# ls
# touch \* \&
# find . -type f -name "\&" -print0|xargs -0 rm
# ls
*
# touch \*
On 25/06/11 16:22, Ralf Mardorf wrote:
>
>>> To give a silly example, a file named "-rf *" or "rm -rf *"
>>
>> I defy you to create a file with those name ;-p
>> NOTE: I've tried. No point in it just being an untested opinion.
>
> $ echo test > *
> bash: *: ambiguous redirect
>
> $ ech
touch touch a file with a special character?
My apologies - I've worked out what you meant (I hope)
$xmodmap -e "keysym Alt_L = Multi_key"
scott@work:~/spec$ touch è
scott@work:~/spec$ ls
è
Works fine. The problem is not creating filenames with special
characters - it's transla
On Sat, 2011-06-25 at 08:22 +0200, Ralf Mardorf wrote:
> > > To give a silly example, a file named "-rf *" or "rm -rf *"
> >
> > I defy you to create a file with those name ;-p
> > NOTE: I've tried. No point in it just being an untested opinion.
>
> $ echo test > *
> bash: *: ambiguous r
> > To give a silly example, a file named "-rf *" or "rm -rf *"
>
> I defy you to create a file with those name ;-p
> NOTE: I've tried. No point in it just being an untested opinion.
$ echo test > *
bash: *: ambiguous redirect
$ echo test > \*
$ ls
* Desktop Downloads hdsp.1
Any id
On 25/06/11 15:56, William Hopkins wrote:
> On 06/25/11 at 03:36pm, Scott Ferguson wrote:
>> On 25/06/11 11:27, Doug wrote:
>>> On 06/24/2011 08:16 PM, lee wrote:
Scott Ferguson writes:
>>
>>
>>
>
> Maybe you should reply to one of the troubleshooting responses
> instead of the phil
t;>
>> I defy you to create a file with those name ;-p
>> NOTE: I've tried. No point in it just being an untested opinion.
>
> Why wouldn't you be able to? None of those are forbidden characters for
> filenames.
>
> ,
> |li
s
> where the problem came from. I have no problems with either ext3 or ext4
> in "creating" filenames with whitespaces and accented characters.
>
> Note the screen shot:-
> http://lists.debian.org/debian-user/2011/06/pngTe0u43cmOF.png
> - that's a file being tra
silly example, a file named "-rf *" or "rm -rf *"
>
> I defy you to create a file with those name ;-p
> NOTE: I've tried. No point in it just being an untested opinion.
Why wouldn't you be able to? None of those are forbidden characters for
filenames.
,
|liam@slimer:~/safe$ touch ./-rf\ *
|liam@slimer:~/safe$ ls
|-rf *
`---
--
Liam
signature.asc
Description: Digital signature
ing the accented character. --doug
In this case it would require educating Microsoft Windows users (and
corrupting my nicely organised and extensive music collection). Which is
where the problem came from. I have no problems with either ext3 or ext4
in "creating" filenames with whitesp
On 25/06/11 10:16, lee wrote:
> Scott Ferguson writes:
>
>> I don't think the "no white spaces" and "no accented characters"
>> "rule" is valid in the 21st century. But if some one can put up an
>> authoritative, and recent, reason I'll reconsider.
>
> Since (unfortunately) there isn't anything
On 25/06/11 08:05, David Jardine wrote:
> On Sat, Jun 25, 2011 at 01:34:54AM +1000, Scott Ferguson wrote:
>>
>> [...]
>>
>> I don't think the "no white spaces" and "no accented characters" "rule"
>> is valid in the 21st century. But if some one can put up an
>> authoritative, and recent, reason I'
On 25/06/11 08:05, David Jardine wrote:
>$ mkdir newdir; cd newdir
>$ touch 'one space' 'and two spaces'
>$ for jim in *; do echo $jim; done
>and two spaces
>one space
>
> So far, so good, but:
>
>$ for jim in `ls`; do echo $jim; done
>and
>two
>spaces
>one
On 06/24/2011 08:16 PM, lee wrote:
Scott Ferguson writes:
I don't think the "no white spaces" and "no accented characters"
"rule" is valid in the 21st century. But if some one can put up an
authoritative, and recent, reason I'll reconsider.
Since (unfortunately) there isn't anything preventin
Scott Ferguson writes:
> I don't think the "no white spaces" and "no accented characters"
> "rule" is valid in the 21st century. But if some one can put up an
> authoritative, and recent, reason I'll reconsider.
Since (unfortunately) there isn't anything preventing users from
creating files with
On Sat, Jun 25, 2011 at 01:34:54AM +1000, Scott Ferguson wrote:
>
> [...]
>
> I don't think the "no white spaces" and "no accented characters" "rule"
> is valid in the 21st century. But if some one can put up an
> authoritative, and recent, reason I'll reconsider.
>
You won't get anything auth
On 24/06/11 20:05, Raffaele Morelli wrote:
> Hi,
>
> I am experiencing serious problems with my external HD, I can't
> create/write filenames containing accented chars, especially when
> copying music from my amarok collection (as you can guess a lor of
> brazilian, f
On Fri, 24 Jun 2011 13:51:11 + (UTC)
Camaleón wrote:
> On Fri, 24 Jun 2011 12:05:17 +0200, Raffaele Morelli wrote:
>
> > I am experiencing serious problems with my external HD, I can't
> > create/write filenames containing accented chars, especially when
> >
Raffaele Morelli writes:
> 2011/6/24 lee
>
>> Raffaele Morelli writes:
>>
>> > I am experiencing serious problems with my external HD, I can't
>> create/write
>> > filenames containing accented chars, especially when copying music from
>>
On Fri, 24 Jun 2011 12:05:17 +0200, Raffaele Morelli wrote:
> I am experiencing serious problems with my external HD, I can't
> create/write filenames containing accented chars, especially when
> copying music from my amarok collection (as you can guess a lor of
> brazilian, f
2011/6/24 lee
> Raffaele Morelli writes:
>
> > I am experiencing serious problems with my external HD, I can't
> create/write
> > filenames containing accented chars, especially when copying music from
> my
> > amarok collection (as you can guess a lor of braz
Raffaele Morelli writes:
> I am experiencing serious problems with my external HD, I can't create/write
> filenames containing accented chars, especially when copying music from my
> amarok collection (as you can guess a lor of brazilian, french and
> italian music has plenty
2011/6/24 Andrei POPESCU
> On Vi, 24 iun 11, 12:05:17, Raffaele Morelli wrote:
> > Hi,
> >
> > I am experiencing serious problems with my external HD, I can't
> create/write
> > filenames containing accented chars, especially when copying music from
> my
>
Raffaele Morelli wrote:
> Hi,
>
> I am experiencing serious problems with my external HD, I can't
> create/write filenames containing accented chars, especially when
> copying music from my amarok collection (as you can guess a lor of
> brazilian, french and italian music
2011/6/24 Lorenzo Sutton
> Raffaele Morelli wrote:
> > Hi,
> >
> > I am experiencing serious problems with my external HD, I can't
> > create/write filenames containing accented chars, especially when
> > copying music from my amarok collection (as you ca
On Vi, 24 iun 11, 12:05:17, Raffaele Morelli wrote:
> Hi,
>
> I am experiencing serious problems with my external HD, I can't create/write
> filenames containing accented chars, especially when copying music from my
> amarok collection (as you can guess a lor of brazilian,
Hi,
I am experiencing serious problems with my external HD, I can't create/write
filenames containing accented chars, especially when copying music from my
amarok collection (as you can guess a lor of brazilian, french and
italian music has plenty of accented chars in filenames).
Is it a l
On 5.1.2011 13:15, S Mathias wrote:
> find duplicate filenames in a folder
> find | perl -ne 's!([^/]+)$!lc $1!e; print if 1 == $seen{$_}++'
>
> find duplicate filenames in a folder recursively
> ? how?
>
$ sudo aptitude install fdupes
--
Q: What's the
>> On Wed, 5 Jan 2011 03:15:01 -0800 (PST),
>> S Mathias said:
S> find duplicate filenames in a folder recursively? how?
It's a (pretty ugly) one-liner if you have something to reverse strings
in a file. Put this in (say) /usr/local/bin/rev:
#!/usr/bi
find duplicate filenames in a folder
find | perl -ne 's!([^/]+)$!lc $1!e; print if 1 == $seen{$_}++'
find duplicate filenames in a folder recursively
? how?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trou
On 2009-09-06 21:07 +0200, Patrick Wiseman wrote:
> I recently encountered a problem others have run into before - the
> default behavior on Linux of converting short, uppercase filenames on
> vfat partitions to lower case. Every time I mounted a disk with a
> vfat partition on it,
Hello, all:
I recently encountered a problem others have run into before - the
default behavior on Linux of converting short, uppercase filenames on
vfat partitions to lower case. Every time I mounted a disk with a
vfat partition on it, a directory with an uppercase name suddenly had
a lowercase
Ron Johnson wrote:
>
> The question still is why the file names are different:
> CH3CN+2.5%Fer.doc
> CH3CN+2.5%25Fer.doc
Because they're not both file names.
The first was the file name.
The second was the _encoding_ in the filename in a URI (the smb:... URI).
See RFC 3986.
Daniel
--
(Plain
1 - 100 of 347 matches
Mail list logo
