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 containing accented chars, especially when
>> > co
>>> 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 collection (as you can guess a lor of
> > b
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
On 26/06/11 09:17, William Hopkins wrote:
> On 06/25/11 at 04:33pm, Scott Ferguson wrote:
> OK, so the files are being created, and your FS can handle the characters, but
> somehow the characters aren't being translated. So it's not an issue with your
> filesystem, it's an issue with the filesys
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
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
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:
>>
>>
>
> What happens when you try touch touch a file with a special character?
My apologies - I
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
On 25/06/11 15:53, William Hopkins wrote:
> On 06/25/11 at 03:20pm, Scott Ferguson wrote:
>> On 25/06/11 10:16, lee wrote:
>>> Scott Ferguson writes:
>>>
>>>
>>> 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 tri
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:
> >>
>
>
>
> >>
> >>
> > Probably the best reason is if you *ever* share files, or send one to
> > someone else, he/she is as likely as not not to ha
On 06/25/11 at 03:20pm, Scott Ferguson wrote:
> 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 re
On 25/06/11 11:27, Doug wrote:
> On 06/24/2011 08:16 PM, lee wrote:
>> Scott Ferguson writes:
>>
>>
>>
> Probably the best reason is if you *ever* share files, or send one to
> someone else, he/she is as likely as not not to have the capability of
> inputting the accented character. --doug
I
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, french and italian music has
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
> > copying music from my amarok coll
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
>> my
>> > amarok collection (as you can guess a lor of bra
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, french and italian mus
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 brazilian, french and
> > italian music
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 of accented chars in
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
> > amarok collection (as you can guess a
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 has plenty of accented cha
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 can guess a lor of
> > brazilian, french and
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, french and
> italian mus
53 matches
Mail list logo
