1.Open explorer
2.Navigate through thousands of levels of directory tree... ummm.. by mouse!
3.Select the directory (click the damned button again!), press Shift-Delete
4.Move the mouse pointer and click on "Yes" button
5.Wait...
6.Popup: "... sure to remove read-only files?"   <repeat step 4>
7.Wait...
8.Popup again! "... sure to remove system files?"   <repeat step 4>
9.Wait...
10.Damned Popup again!! "The file ... is locked"!
11.Open process explorer
12.Search for the locked file/dll handle
13.Right click on the handle, choose "Kill"
14.Go back to explorer, <repeat step 4>
15. ....


Guess how much time I wasted just to remove a trash cygwin dir?

<f**k!>

**** Post for FREE via your newsreader at post.usenet.com ****

The puny human animal #89cc9fea8371254dc467f2a880c23845 aquila_deus@yahoo.co.uk (Aquila Deus) cried:

> 1.Open explorer
> 2.Navigate through thousands of levels of directory tree... ummm.. by mouse!
> 3.Select the directory (click the damned button again!), press Shift-Delete
> 4.Move the mouse pointer and click on "Yes" button
> 5.Wait...
> 6.Popup: "... sure to remove read-only files?"   <repeat step 4>
> 7.Wait...
> 8.Popup again! "... sure to remove system files?"   <repeat step 4>
> 9.Wait...
> 10.Damned Popup again!! "The file ... is locked"!
> 11.Open process explorer
> 12.Search for the locked file/dll handle
> 13.Right click on the handle, choose "Kill"
> 14.Go back to explorer, <repeat step 4>
> 15. ....
>
>
> Guess how much time I wasted just to remove a trash cygwin dir?
>
> <f**k!>

PS: console version isn't much better. The command "del" stops whenever it
encounters any problem.


-- 
me = d2004xx = d2003xx = d2002xx

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 *** Usenet.com - The #1 Usenet Newsgroup Service on The Planet! ***
                      http://www.usenet.com
Unlimited Download - 19 Seperate Servers - 90,000 groups - Uncensored
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Aquila Deus wrote:
> **** Post for FREE via your newsreader at post.usenet.com ****
> 
> The puny human animal #89cc9fea8371254dc467f2a880c23845
> aquila_deus@yahoo.co.uk (Aquila Deus) cried: 
> 
>> 1.Open explorer
>> 2.Navigate through thousands of levels of directory tree... ummm..
>> by mouse! 
>> 3.Select the directory (click the damned button again!), press
>> Shift-Delete 
>> 4.Move the mouse pointer and click on "Yes" button
>> 5.Wait...
>> 6.Popup: "... sure to remove read-only files?"   <repeat step 4>
>> 7.Wait...
>> 8.Popup again! "... sure to remove system files?"   <repeat step 4>
>> 9.Wait...
>> 10.Damned Popup again!! "The file ... is locked"!
>> 11.Open process explorer
>> 12.Search for the locked file/dll handle
>> 13.Right click on the handle, choose "Kill"
>> 14.Go back to explorer, <repeat step 4>
>> 15. ....
>> 
>> 
>> Guess how much time I wasted just to remove a trash cygwin dir?
>> 
>> <f**k!>
> 
> PS: console version isn't much better. The command "del" stops
> whenever it 
> encounters any problem.

<shakes head>
Boot from the CD
Take the "Repair" option to enter the Recovery Console
   a. Use the Delete command.
   b. Use the Format command instead of the Delete command.

-- 
- relic -
Don't take life too seriously, You won't get out alive.

relic wrote:

> Aquila Deus wrote:
>> **** Post for FREE via your newsreader at post.usenet.com ****
>> 
>> The puny human animal #89cc9fea8371254dc467f2a880c23845
>> aquila_deus@yahoo.co.uk (Aquila Deus) cried:
>> 
>>> 1.Open explorer
>>> 2.Navigate through thousands of levels of directory tree... ummm..
>>> by mouse!
>>> 3.Select the directory (click the damned button again!), press
>>> Shift-Delete
>>> 4.Move the mouse pointer and click on "Yes" button
>>> 5.Wait...
>>> 6.Popup: "... sure to remove read-only files?"   <repeat step 4>
>>> 7.Wait...
>>> 8.Popup again! "... sure to remove system files?"   <repeat step 4>
>>> 9.Wait...
>>> 10.Damned Popup again!! "The file ... is locked"!
>>> 11.Open process explorer
>>> 12.Search for the locked file/dll handle
>>> 13.Right click on the handle, choose "Kill"
>>> 14.Go back to explorer, <repeat step 4>
>>> 15. ....
>>> 
>>> 
>>> Guess how much time I wasted just to remove a trash cygwin dir?
>>> 
>>> <f**k!>
>> 
>> PS: console version isn't much better. The command "del" stops
>> whenever it
>> encounters any problem.
> 
> <shakes head>
> Boot from the CD
> Take the "Repair" option to enter the Recovery Console
>    a. Use the Delete command.
>    b. Use the Format command instead of the Delete command.
> 

Booting to a CD to remove a directory???? You think that's better???? Damn
glad I don't use MS software. 

Aquila Deus wrote:

> **** Post for FREE via your newsreader at post.usenet.com ****
> 
> The puny human animal #89cc9fea8371254dc467f2a880c23845
> aquila_deus@yahoo.co.uk (Aquila Deus) cried:
> 
>> 1.Open explorer
>> 2.Navigate through thousands of levels of directory tree... ummm.. by
>> mouse! 3.Select the directory (click the damned button again!), press
>> Shift-Delete 4.Move the mouse pointer and click on "Yes" button
>> 5.Wait...
>> 6.Popup: "... sure to remove read-only files?"   <repeat step 4>
>> 7.Wait...
>> 8.Popup again! "... sure to remove system files?"   <repeat step 4>
>> 9.Wait...
>> 10.Damned Popup again!! "The file ... is locked"!
>> 11.Open process explorer
>> 12.Search for the locked file/dll handle
>> 13.Right click on the handle, choose "Kill"
>> 14.Go back to explorer, <repeat step 4>
>> 15. ....
>>
>>
>> Guess how much time I wasted just to remove a trash cygwin dir?
>>
>> <f**k!>
> 
> PS: console version isn't much better. The command "del" stops whenever it
> encounters any problem.

The problem you are having is due to Microshaft breaking compatibility
with old DOS programs and the command line. The command line console
in ex-pee is a fake immitation.
I find console works better with FreeDOS (a freed up DOS).
Boot up under FreeDOS and then type del c:\*.*/s  and answer yes.

To automate the process, I've even created a quick utility using the < pipe.

filea.bat:
  del c:\*.*/s < fileb

fileb:
  yes

Works wonders I can tell you. Even more fun when you rename "filea.bat" to
autoexec.bat to replace it. Works wonders with other other common commands
like win.bat, winnt.bat etc..

7 wrote:
> Aquila Deus wrote:
>
>> **** Post for FREE via your newsreader at post.usenet.com ****
>>
>> The puny human animal #89cc9fea8371254dc467f2a880c23845
>> aquila_deus@yahoo.co.uk (Aquila Deus) cried:
>>
>>> 1.Open explorer
>>> 2.Navigate through thousands of levels of directory tree... ummm..
>>> by mouse! 3.Select the directory (click the damned button again!),
>>> press Shift-Delete 4.Move the mouse pointer and click on "Yes"
>>> button
>>> 5.Wait...
>>> 6.Popup: "... sure to remove read-only files?"   <repeat step 4>
>>> 7.Wait...
>>> 8.Popup again! "... sure to remove system files?"   <repeat step 4>
>>> 9.Wait...
>>> 10.Damned Popup again!! "The file ... is locked"!
>>> 11.Open process explorer
>>> 12.Search for the locked file/dll handle
>>> 13.Right click on the handle, choose "Kill"
>>> 14.Go back to explorer, <repeat step 4>
>>> 15. ....
>>>
>>>
>>> Guess how much time I wasted just to remove a trash cygwin dir?
>>>
>>> <f**k!>
>>
>> PS: console version isn't much better. The command "del" stops
>> whenever it encounters any problem.
>
> The problem you are having is due to Microshaft breaking compatibility
> with old DOS programs and the command line. The command line console
> in ex-pee is a fake immitation.
> I find console works better with FreeDOS (a freed up DOS).
> Boot up under FreeDOS and then type del c:\*.*/s  and answer yes.
>
Why since all versions of Windows and Dos have the almost the same switches
for commands.  Looks like FreeDos might support them slightly differently,
or you screwed up the command.
Try using a /F command also,  it makes things easier...
'erase /F /S *.*'  should delete everything,  or you could use the DEL
command if you don't like erase....

> To automate the process, I've even created a quick utility using the
> < pipe.
>
> filea.bat:
>   del c:\*.*/s < fileb
>
> fileb:
>   yes
>
> Works wonders I can tell you. Even more fun when you rename
> "filea.bat" to autoexec.bat to replace it. Works wonders with other
> other common commands like win.bat, winnt.bat etc..

I just love it when Linux users can't seem to use simple things under XP
though they can use even MORE complex ones under Linux.....

On Sun, 08 Aug 2004 22:23:22 +0000, Quantum Leaper wrote:

>> Works wonders I can tell you. Even more fun when you rename "filea.bat"
>> to autoexec.bat to replace it. Works wonders with other other common
>> commands like win.bat, winnt.bat etc..
> 
> I just love it when Linux users can't seem to use simple things under XP
> though they can use even MORE complex ones under Linux.....

Having used both to accomplish the same on multiple occasions I will say
that it *is* simpler to do under Linux than under Windows.

To remove an entire directory tree along with any files thereof on Linux
via console is simply a matter of typing:

    rm -Rf <dirname>

As you have pointed out, the same thing on a winsystem requires the
command:

  del /f /s /q <dirname>

Not too much difference there, however, as the OP has pointed out, most
persons prefer to perform tasks like this from within a GUI environment.
The OP has already clearly stated the headaches that one has to go through
to do this on a wincomp.  With any Linux file manager, it's simply a
matter of selecting the target directory and deleting (and confirming once
if necessary).

Another factor is navigation.  It is much easier to navigate the file
system using a 'nix shell than a win one.  With later versions of the win
shell *finally* adding features like tab completion and command history,
it's a little bit better, but still a major PIA.

Also consider that with console File Management tools like Midnight
Commander, you can have the benefits of both console and GUI, something
that is sorely lacking on winsystems.

On Sun, 08 Aug 2004 22:31:13 +0800, Aquila Deus
<aquila_deus@yahoo.co.uk> wrote:

>**** Post for FREE via your newsreader at post.usenet.com ****
>
>The puny human animal #89cc9fea8371254dc467f2a880c23845 aquila_deus@yahoo.co.uk (Aquila Deus) cried:
>
>> 1.Open explorer
>> 2.Navigate through thousands of levels of directory tree... ummm.. by mouse!

Why don't you hit View->Toolbars->Address Bar once and for all, then
type in (or paste) the  path?

>> 3.Select the directory (click the damned button again!), press Shift-Delete
>> 4.Move the mouse pointer and click on "Yes" button
>> 5.Wait...
>> 6.Popup: "... sure to remove read-only files?"   <repeat step 4>
>> 7.Wait...
>> 8.Popup again! "... sure to remove system files?"   <repeat step 4>
>> 9.Wait...
>> 10.Damned Popup again!! "The file ... is locked"!
>> 11.Open process explorer
>> 12.Search for the locked file/dll handle
>> 13.Right click on the handle, choose "Kill"
>> 14.Go back to explorer, <repeat step 4>
>> 15. ....
>>
>>
>> Guess how much time I wasted just to remove a trash cygwin dir?
>>
>> <f**k!>
>
>PS: console version isn't much better. The command "del" stops whenever it
>encounters any problem.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

["Followup-To:" header set to comp.os.linux.advocacy.]
On Sun, 08 Aug 2004 14:59:16 GMT,
 relic <nospam@relic211.cjb.net> wrote:
> Aquila Deus wrote:
>> **** Post for FREE via your newsreader at post.usenet.com ****
>> 
>> The puny human animal #89cc9fea8371254dc467f2a880c23845
>> aquila_deus@yahoo.co.uk (Aquila Deus) cried: 
>> 
>>> 1.Open explorer
>>> 2.Navigate through thousands of levels of directory tree... ummm..
>>> by mouse! 
>>> 3.Select the directory (click the damned button again!), press
>>> Shift-Delete 
>>> 4.Move the mouse pointer and click on "Yes" button
>>> 5.Wait...
>>> 6.Popup: "... sure to remove read-only files?"   <repeat step 4>
>>> 7.Wait...
>>> 8.Popup again! "... sure to remove system files?"   <repeat step 4>
>>> 9.Wait...
>>> 10.Damned Popup again!! "The file ... is locked"!
>>> 11.Open process explorer
>>> 12.Search for the locked file/dll handle
>>> 13.Right click on the handle, choose "Kill"
>>> 14.Go back to explorer, <repeat step 4>
>>> 15. ....
>>> 
>>> 
>>> Guess how much time I wasted just to remove a trash cygwin dir?
>>> 
>>> <f**k!>
>> 
>> PS: console version isn't much better. The command "del" stops
>> whenever it 
>> encounters any problem.
>
><shakes head>
> Boot from the CD
> Take the "Repair" option to enter the Recovery Console
>    a. Use the Delete command.
>    b. Use the Format command instead of the Delete command.
>


Let me get this straight. 

You're suggesting he reboot, to delete a directory? 

OK, *that's* funny...

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBFwtvd90bcYOAWPYRAjQGAJ9FN5minVcNm7+Hgz8OXXv+IPYSUQCfZJAl
QNebVjD4misb10+XtaiOj8M=
=/+z1
-----END PGP SIGNATURE-----

-- 
Jim Richardson     http://www.eskimo.com/~warlock
I feel much better, now that I've given up hope.

**** Post for FREE via your newsreader at post.usenet.com ****

The puny human animal #63f1fb7961c37ae6f606ed0741ae509f PastaVerde cried:

> On Sun, 08 Aug 2004 22:31:13 +0800, Aquila Deus
> <aquila_deus@yahoo.co.uk> wrote:
>
>>**** Post for FREE via your newsreader at post.usenet.com ****
>>
>>The puny human animal #89cc9fea8371254dc467f2a880c23845 aquila_deus@yahoo.co.uk (Aquila Deus) cried:
>>
>>> 1.Open explorer
>>> 2.Navigate through thousands of levels of directory tree... ummm.. by mouse!
>
> Why don't you hit View->Toolbars->Address Bar once and for all, then
> type in (or paste) the  path?

Because windows' folders are usually badly named.. full of non-english, damned
asian char, whitespaces, weird symbols, ... And auto-completion doesn't work
when you're running something in the background (it uses a low-priority thread I
guess)

-- 
me = d2004xx = d2003xx = d2002xx

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 *** Usenet.com - The #1 Usenet Newsgroup Service on The Planet! ***
                      http://www.usenet.com
Unlimited Download - 19 Seperate Servers - 90,000 groups - Uncensored
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

On Mon, 09 Aug 2004 14:24:13 +0800, Aquila Deus
<aquila_deus@yahoo.co.uk> wrote:

>**** Post for FREE via your newsreader at post.usenet.com ****
>
>The puny human animal #63f1fb7961c37ae6f606ed0741ae509f PastaVerde cried:
>
>> On Sun, 08 Aug 2004 22:31:13 +0800, Aquila Deus
>> <aquila_deus@yahoo.co.uk> wrote:
>>
>>>**** Post for FREE via your newsreader at post.usenet.com ****
>>>
>>>The puny human animal #89cc9fea8371254dc467f2a880c23845 aquila_deus@yahoo.co.uk (Aquila Deus) cried:
>>>
>>>> 1.Open explorer
>>>> 2.Navigate through thousands of levels of directory tree... ummm.. by mouse!
>>
>> Why don't you hit View->Toolbars->Address Bar once and for all, then
>> type in (or paste) the  path?
>
>Because windows' folders are usually badly named.. full of non-english, damned
>asian char, whitespaces, weird symbols, ... And auto-completion doesn't work
>when you're running something in the background (it uses a low-priority thread I
>guess)

OK, your app, cygwin, was installed in a folder "full of non-english,
damned asian char, whitespaces, weird symbols", like c:\cygwin, right?

Error BR-549: MS DRM 1.0 rejects the following post from Jim Richardson:

> On Sun, 08 Aug 2004 14:59:16 GMT,
>  relic <nospam@relic211.cjb.net> wrote:
>>
>><shakes head>
>> Boot from the CD
>> Take the "Repair" option to enter the Recovery Console
>>    a. Use the Delete command.
>>    b. Use the Format command instead of the Delete command.
>
> Let me get this straight. 
> You're suggesting he reboot, to delete a directory? 
> OK, *that's* funny...

He's a Windows relic.

-- 
[X] Check here to always trust content from Lin�nut

Jim Richardson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> ["Followup-To:" header set to comp.os.linux.advocacy.]
> On Sun, 08 Aug 2004 14:59:16 GMT,
>  relic <nospam@relic211.cjb.net> wrote:
>> Aquila Deus wrote:
>>> **** Post for FREE via your newsreader at post.usenet.com ****
>>> 
>>> The puny human animal #89cc9fea8371254dc467f2a880c23845
>>> aquila_deus@yahoo.co.uk (Aquila Deus) cried:
>>> 
>>>> 1.Open explorer
>>>> 2.Navigate through thousands of levels of directory tree... ummm..
>>>> by mouse!
>>>> 3.Select the directory (click the damned button again!), press
>>>> Shift-Delete
>>>> 4.Move the mouse pointer and click on "Yes" button
>>>> 5.Wait...
>>>> 6.Popup: "... sure to remove read-only files?"   <repeat step 4>
>>>> 7.Wait...
>>>> 8.Popup again! "... sure to remove system files?"   <repeat step 4>
>>>> 9.Wait...
>>>> 10.Damned Popup again!! "The file ... is locked"!
>>>> 11.Open process explorer
>>>> 12.Search for the locked file/dll handle
>>>> 13.Right click on the handle, choose "Kill"
>>>> 14.Go back to explorer, <repeat step 4>
>>>> 15. ....
>>>> 
>>>> 
>>>> Guess how much time I wasted just to remove a trash cygwin dir?
>>>> 
>>>> <f**k!>
>>> 
>>> PS: console version isn't much better. The command "del" stops
>>> whenever it
>>> encounters any problem.
>> 
>> <shakes head>
>> Boot from the CD
>> Take the "Repair" option to enter the Recovery Console
>>    a. Use the Delete command.
>>    b. Use the Format command instead of the Delete command.
>> 
> 
> 
> Let me get this straight.
> 
> You're suggesting he reboot, to delete a directory?
> 
> OK, *that's* funny...

No, it's something you'd never be able to understand.

You're a typical linuxfuck.
Linux makes you stupid.
All linux users (lusers) are gay.

-- 
- relic -
Don't take life too seriously, You won't get out alive.

PastaVerde wrote:
> On Mon, 09 Aug 2004 14:24:13 +0800, Aquila Deus
> <aquila_deus@yahoo.co.uk> wrote:
> 
>> **** Post for FREE via your newsreader at post.usenet.com ****
>> 
>> The puny human animal #63f1fb7961c37ae6f606ed0741ae509f PastaVerde
>> cried: 
>> 
>>> On Sun, 08 Aug 2004 22:31:13 +0800, Aquila Deus
>>> <aquila_deus@yahoo.co.uk> wrote:
>>> 
>>>> **** Post for FREE via your newsreader at post.usenet.com ****
>>>> 
>>>> The puny human animal #89cc9fea8371254dc467f2a880c23845
>>>> aquila_deus@yahoo.co.uk (Aquila Deus) cried: 
>>>> 
>>>>> 1.Open explorer
>>>>> 2.Navigate through thousands of levels of directory tree...
>>>>> ummm.. by mouse! 
>>> 
>>> Why don't you hit View->Toolbars->Address Bar once and for all, then
>>> type in (or paste) the  path?
>> 
>> Because windows' folders are usually badly named.. full of
>> non-english, damned asian char, whitespaces, weird symbols, ... And
>> auto-completion doesn't work when you're running something in the
>> background (it uses a low-priority thread I guess)
> 
> OK, your app, cygwin, was installed in a folder "full of non-english,
> damned asian char, whitespaces, weird symbols", like c:\cygwin, right?

<snigger> Give up, you'd never understand.  linux has made you too stupid.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 09 Aug 2004 14:27:10 GMT,
 relic <nospam@relic211.cjb.net> wrote:
> Jim Richardson wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> 
>> ["Followup-To:" header set to comp.os.linux.advocacy.]
>> On Sun, 08 Aug 2004 14:59:16 GMT,
>>  relic <nospam@relic211.cjb.net> wrote:
>>> Aquila Deus wrote:
>>>> **** Post for FREE via your newsreader at post.usenet.com ****
>>>> 
>>>> The puny human animal #89cc9fea8371254dc467f2a880c23845
>>>> aquila_deus@yahoo.co.uk (Aquila Deus) cried:
>>>> 
>>>>> 1.Open explorer
>>>>> 2.Navigate through thousands of levels of directory tree... ummm..
>>>>> by mouse!
>>>>> 3.Select the directory (click the damned button again!), press
>>>>> Shift-Delete
>>>>> 4.Move the mouse pointer and click on "Yes" button
>>>>> 5.Wait...
>>>>> 6.Popup: "... sure to remove read-only files?"   <repeat step 4>
>>>>> 7.Wait...
>>>>> 8.Popup again! "... sure to remove system files?"   <repeat step 4>
>>>>> 9.Wait...
>>>>> 10.Damned Popup again!! "The file ... is locked"!
>>>>> 11.Open process explorer
>>>>> 12.Search for the locked file/dll handle
>>>>> 13.Right click on the handle, choose "Kill"
>>>>> 14.Go back to explorer, <repeat step 4>
>>>>> 15. ....
>>>>> 
>>>>> 
>>>>> Guess how much time I wasted just to remove a trash cygwin dir?
>>>>> 
>>>>> <f**k!>
>>>> 
>>>> PS: console version isn't much better. The command "del" stops
>>>> whenever it
>>>> encounters any problem.
>>> 
>>> <shakes head>
>>> Boot from the CD
>>> Take the "Repair" option to enter the Recovery Console
>>>    a. Use the Delete command.
>>>    b. Use the Format command instead of the Delete command.
>>> 
>> 
>> 
>> Let me get this straight.
>> 
>> You're suggesting he reboot, to delete a directory?
>> 
>> OK, *that's* funny...
>
> No, it's something you'd never be able to understand.
>
> You're a typical linuxfuck.
> Linux makes you stupid.
> All linux users (lusers) are gay.
>


Well, one thing I have a hard time understanding is why you think poor
insults will somehow make people overlook your lack of debating skills. 

But then, I so rarely deal with the mentally handicapped, that dealing
with you is a bit of a new experience for me. 

Please feel free to make more poor insults, and I will feel free to
laugh at your attempts to be witty. 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBF6tid90bcYOAWPYRAqu+AKCN3aBdG8lD8gL098F19NKyD+gA1gCg5ZET
YTzsA58vnFPkyjFloRu89g4=
=k8sf
-----END PGP SIGNATURE-----

-- 
Jim Richardson     http://www.eskimo.com/~warlock
Microsoft - because god hates us

"relic" <nospam@relic211.cjb.net> writes:

> Jim Richardson wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> 
>> ["Followup-To:" header set to comp.os.linux.advocacy.]
>> On Sun, 08 Aug 2004 14:59:16 GMT,
>>  relic <nospam@relic211.cjb.net> wrote:
>>> 
>>> <shakes head>
>>> Boot from the CD
>>> Take the "Repair" option to enter the Recovery Console
>>>    a. Use the Delete command.
>>>    b. Use the Format command instead of the Delete command.
>>> 
>> 
>> 
>> Let me get this straight.
>> 
>> You're suggesting he reboot, to delete a directory?
>> 
>> OK, *that's* funny...
>
> No, it's something you'd never be able to understand.
>
> You're a typical linuxfuck.
> Linux makes you stupid.
> All linux users (lusers) are gay.

Boy, that's a longwinded way to say "yes".

-- 
Jesse F. Hughes
"If anything is true in general about Usenet, it's that people can go
on and on about just about anything."  -- James Harris speaks the
truth.

PastaVerde wrote in message news:<hnbeh0hvan5o6a9u7mmfrbjm5roespmk34@4ax.com>...
> On Mon, 09 Aug 2004 14:24:13 +0800, Aquila Deus
> <aquila_deus@yahoo.co.uk> wrote:
> 
> >**** Post for FREE via your newsreader at post.usenet.com ****
> >
> >The puny human animal #63f1fb7961c37ae6f606ed0741ae509f PastaVerde cried:
> >
> >> On Sun, 08 Aug 2004 22:31:13 +0800, Aquila Deus
> >> <aquila_deus@yahoo.co.uk> wrote:
> >>
> >>>**** Post for FREE via your newsreader at post.usenet.com ****
> >>>
> >>>The puny human animal #89cc9fea8371254dc467f2a880c23845 aquila_deus@yahoo.co.uk (Aquila Deus) cried:
> >>>
> >>>> 1.Open explorer
> >>>> 2.Navigate through thousands of levels of directory tree... ummm.. by mouse!
> >>
> >> Why don't you hit View->Toolbars->Address Bar once and for all, then
> >> type in (or paste) the  path?
> >
> >Because windows' folders are usually badly named.. full of non-english, damned
> >asian char, whitespaces, weird symbols, ... And auto-completion doesn't work
> >when you're running something in the background (it uses a low-priority thread I
> >guess)
> 
> OK, your app, cygwin, was installed in a folder "full of non-english,
> damned asian char, whitespaces, weird symbols", like c:\cygwin, right?

No, I was talking about other dirs like "C:\Documents and Settings"
named by M$'s idiots. Cygwin's problems are mainly about permissions.

In comp.os.linux.advocacy, Aquila Deus
<aquila_deus@yahoo.co.uk>
 wrote
on 8 Aug 2004 07:22:27 -0700
<c5cfac8f.0408080622.248708db@posting.google.com>:
> 1.Open explorer
> 2.Navigate through thousands of levels of directory tree... ummm.. by mouse!

Optimization: type the path of the parent in the provided widget.

But I agree, it's ugly -- and I for one am not always sure
I'm in the right place, as Windows doesn't show the entire
pathname, unless one pulls down the path menu, which is
nice from a display standpoint (a rectangle versus a thin
line) but is dumb from a usability standpoint (one can't
do anything else until the roller snaps back up).

> 3.Select the directory (click the damned button again!), press Shift-Delete

Or press, move, drop on Trash.  Not the prettiest of metaphors
either way; I'd just as soon press "Delete" and be done with it.

> 4.Move the mouse pointer and click on "Yes" button
> 5.Wait...
> 6.Popup: "... sure to remove read-only files?"   <repeat step 4>
> 7.Wait...
> 8.Popup again! "... sure to remove system files?"   <repeat step 4>
> 9.Wait...
> 10.Damned Popup again!! "The file ... is locked"!
> 11.Open process explorer
> 12.Search for the locked file/dll handle
> 13.Right click on the handle, choose "Kill"
> 14.Go back to explorer, <repeat step 4>
> 15. ....
>
>
> Guess how much time I wasted just to remove a trash cygwin dir?
>
> <f**k!>

A philosophical difference, of course: Linux can remove
open files, as the inode can keep track of the file until
it is closd.  NTFS does not have that option.  FAT does
have that option if one calls the head of the clusterlist
the inode, though I'm not sure either of NT or Win9x takes
advantage of that capability.  I'd also have to look to
see how Linux implements FAT.  (VFAT is an ugly hack -- not
that FAT is all that pretty.)

Another philosophical difference, although it's somewhat
less.  IMO, Windows assumes the user is an idiot (a fair
assumption in many cases, apparently :-) ).  Linux assumes
the user has half a clue, and if the user knows to use
the -r and -f switches, that the user is fully clued.
If one wants to have Linux behave idiotically -- or
at least allow the user to verify everything -- one can
use the -i switch, or even a different command such as 'mv'.

Of course, I've not studied Nautilus or Konqueror extensively,
so don't know precisely what they do.

An interesting thought would be a "prescan" of some sort, but
there's a danger of stale information.  Basically, the computer
would say something to the effect of:

    "I am about to delete these files and directories, but I've
    noticed this list of discrepancies.  What should I do with
    each of these discrepancies?"

and the user would respond to this *before* the deletion commences.
Failing that, the deletion would be undoable -- I think Microsoft
had this notion in mind with the trashcan metaphor -- in some
fashion.

If one wants to get really cute the information would
be updated dynamically; however, the only OS I know
of that might have been able to do that is Amiga[D]OS,
by registering a notification listener with a directory.
I do not believe any Unix flavor has that option, although
it would be a nice hack -- and there might even be such a
beastie but if so I'm not sure where it is at this point;
presumably readdir(3) would point thereto in its "SEE
ALSO" area.


-- 
#191, ewill3@earthlink.net
It's still legal to go .sigless.

Rapskat wrote:
> On Sun, 08 Aug 2004 22:23:22 +0000, Quantum Leaper wrote:
>
>>> Works wonders I can tell you. Even more fun when you rename
>>> "filea.bat" to autoexec.bat to replace it. Works wonders with other
>>> other common commands like win.bat, winnt.bat etc..
>>
>> I just love it when Linux users can't seem to use simple things
>> under XP though they can use even MORE complex ones under Linux.....
>
> Having used both to accomplish the same on multiple occasions I will
> say that it *is* simpler to do under Linux than under Windows.
>
> To remove an entire directory tree along with any files thereof on
> Linux via console is simply a matter of typing:
>
>     rm -Rf <dirname>
>
> As you have pointed out, the same thing on a winsystem requires the
> command:
>
>   del /f /s /q <dirname>
>
> Not too much difference there, however, as the OP has pointed out,
> most persons prefer to perform tasks like this from within a GUI
> environment. The OP has already clearly stated the headaches that one
> has to go through to do this on a wincomp.  With any Linux file
> manager, it's simply a matter of selecting the target directory and
> deleting (and confirming once if necessary).
>
One extra switch,  really hard.   Your correct under the GUI it would have
required a couple more steps,  but since he was COMPARING it to Linux,
thats why I used a command line.   Its not that hard removing it under the
GUI but you have to turn off a couple of Attributes first.
He said he couldn't do it,  if I remember correctly,  all I was doing was
telling him HOW it could be done.

> Another factor is navigation.  It is much easier to navigate the file
> system using a 'nix shell than a win one.  With later versions of the
> win shell *finally* adding features like tab completion and command
> history, it's a little bit better, but still a major PIA.
>
It depends more on how you have your system setup.   Both my Linux and
Windows systems are fairly easy to navigate,   though I almost never need
command line stuff under Windows,  if the author set his program(s) up
correctly.

> Also consider that with console File Management tools like Midnight
> Commander, you can have the benefits of both console and GUI,
> something that is sorely lacking on winsystems.

I don't know if I installed any file management tools for Linux.   Since
from all the sources I could find,  it looks like they copied Norton
Commander for DOS.   I guess if you like that sort of thing,  its great....

Aquila Deus wrote:
> PastaVerde wrote in message
> news:<hnbeh0hvan5o6a9u7mmfrbjm5roespmk34@4ax.com>...
>> On Mon, 09 Aug 2004 14:24:13 +0800, Aquila Deus
>> <aquila_deus@yahoo.co.uk> wrote:
>>
>>> **** Post for FREE via your newsreader at post.usenet.com ****
>>>
>>> The puny human animal #63f1fb7961c37ae6f606ed0741ae509f PastaVerde
>>> cried:
>>>
>>>> On Sun, 08 Aug 2004 22:31:13 +0800, Aquila Deus
>>>> <aquila_deus@yahoo.co.uk> wrote:
>>>>
>>>>> **** Post for FREE via your newsreader at post.usenet.com ****
>>>>>
>>>>> The puny human animal #89cc9fea8371254dc467f2a880c23845
>>>>> aquila_deus@yahoo.co.uk (Aquila Deus) cried:
>>>>>
>>>>>> 1.Open explorer
>>>>>> 2.Navigate through thousands of levels of directory tree...
>>>>>> ummm.. by mouse!
>>>>
>>>> Why don't you hit View->Toolbars->Address Bar once and for all,
>>>> then type in (or paste) the  path?
>>>
>>> Because windows' folders are usually badly named.. full of
>>> non-english, damned asian char, whitespaces, weird symbols, ... And
>>> auto-completion doesn't work when you're running something in the
>>> background (it uses a low-priority thread I guess)
>>
>> OK, your app, cygwin, was installed in a folder "full of non-english,
>> damned asian char, whitespaces, weird symbols", like c:\cygwin,
>> right?
>
> No, I was talking about other dirs like "C:\Documents and Settings"
> named by M$'s idiots. Cygwin's problems are mainly about permissions.

You got it right,  all you do is ADD qoutes around any directory with white
space,   just because Unix/Linux hates white space in the file system
doesn't mean everyone does....

"Aquila Deus" <aquila_deus@yahoo.co.uk> wrote in message
news:c5cfac8f.0408080622.248708db@posting.google.com...
> 1.Open explorer
> 2.Navigate through thousands of levels of directory tree... ummm.. by
mouse!
> 3.Select the directory (click the damned button again!), press
Shift-Delete
> 4.Move the mouse pointer and click on "Yes" button
> 5.Wait...
> 6.Popup: "... sure to remove read-only files?"   <repeat step 4>
> 7.Wait...
> 8.Popup again! "... sure to remove system files?"   <repeat step 4>
> 9.Wait...
> 10.Damned Popup again!! "The file ... is locked"!
> 11.Open process explorer
> 12.Search for the locked file/dll handle
> 13.Right click on the handle, choose "Kill"
> 14.Go back to explorer, <repeat step 4>
> 15. ....
>
>
> Guess how much time I wasted just to remove a trash cygwin dir?
>
> <f**k!>

More proof that *nix makes you stupid.

Quantum Leaper wrote:

> You got it right,  all you do is ADD qoutes around any directory with white
> space,   just because Unix/Linux hates white space in the file system
> doesn't mean everyone does....


[twilson@goliath tmp]$ mkdir "Linux doesn\'t mind white space at all"
[twilson@goliath tmp]$ ll
total 1
drwxr-xr-x    2 twilson  users          48 Aug  9 19:02 Linux doesn\'t 
mind white space at all
[twilson@goliath tmp]$ cd Linux\ doesn\\\'t\ mind\ white\ space\ at\ all/
[twilson@goliath Linux doesn\'t mind white space at all]$
[twilson@goliath Linux doesn\'t mind white space at all]$ cd ..
[twilson@goliath tmp]$ rm -rf Linux\ doesn\\\'t\ mind\ white\ space\ at\ 
all/


-- 
Tom Wilson
Prof:    So the American government went to IBM to come up with a data
	 encryption standard and they came up with ...
Student: EBCDIC!"

Quantum Leaper wrote:

> Aquila Deus wrote:
> 
>>PastaVerde wrote in message
>>news:<hnbeh0hvan5o6a9u7mmfrbjm5roespmk34@4ax.com>...
>>
>>>On Mon, 09 Aug 2004 14:24:13 +0800, Aquila Deus
>>><aquila_deus@yahoo.co.uk> wrote:
>>>
>>>
>>>>**** Post for FREE via your newsreader at post.usenet.com ****
>>>>
>>>>The puny human animal #63f1fb7961c37ae6f606ed0741ae509f PastaVerde
>>>>cried:
>>>>
>>>>
>>>>>On Sun, 08 Aug 2004 22:31:13 +0800, Aquila Deus
>>>>><aquila_deus@yahoo.co.uk> wrote:
>>>>>
>>>>>
>>>>>>**** Post for FREE via your newsreader at post.usenet.com ****
>>>>>>
>>>>>>The puny human animal #89cc9fea8371254dc467f2a880c23845
>>>>>>aquila_deus@yahoo.co.uk (Aquila Deus) cried:
>>>>>>
>>>>>>
>>>>>>>1.Open explorer
>>>>>>>2.Navigate through thousands of levels of directory tree...
>>>>>>>ummm.. by mouse!
>>>>>
>>>>>Why don't you hit View->Toolbars->Address Bar once and for all,
>>>>>then type in (or paste) the  path?
>>>>
>>>>Because windows' folders are usually badly named.. full of
>>>>non-english, damned asian char, whitespaces, weird symbols, ... And
>>>>auto-completion doesn't work when you're running something in the
>>>>background (it uses a low-priority thread I guess)
>>>
>>>OK, your app, cygwin, was installed in a folder "full of non-english,
>>>damned asian char, whitespaces, weird symbols", like c:\cygwin,
>>>right?
>>
>>No, I was talking about other dirs like "C:\Documents and Settings"
>>named by M$'s idiots. Cygwin's problems are mainly about permissions.
> 
> 
> You got it right,  all you do is ADD qoutes around any directory with white
> space,   just because Unix/Linux hates white space in the file system
> doesn't mean everyone does....
> 
> 

UNIX/Linux doesn't suffer from the whitespace problem at all and it 
works the same way with the quotes.

-- 
---------------------------------
My other computer is a VAX.

Let's see what "Name:" <no.mail@here.com> has under their hat... 

>
>"Aquila Deus" <aquila_deus@yahoo.co.uk> wrote in message
>news:c5cfac8f.0408080622.248708db@posting.google.com...
>> 1.Open explorer
[SNIP]

you idiot
--

"I say we take off, nuke the site from orbit... 
It's the only way to be sure." 
{Ripley/Hicks, Aliens}

=SIGKILL

Name: wrote:

> More proof that *nix makes you stupid.
> 

Hmm,

X-Newsreader: Microsoft Outlook Express 6.00.2800.1437

The Newsreader alone qualifies you as brain damaged.

PKB

GreyCloud wrote:
> Quantum Leaper wrote:
>
>> Aquila Deus wrote:
>>
>>> PastaVerde wrote in message
>>> news:<hnbeh0hvan5o6a9u7mmfrbjm5roespmk34@4ax.com>...
>>>
>>>> On Mon, 09 Aug 2004 14:24:13 +0800, Aquila Deus
>>>> <aquila_deus@yahoo.co.uk> wrote:
>>>>
>>>>
>>>>> **** Post for FREE via your newsreader at post.usenet.com ****
>>>>>
>>>>> The puny human animal #63f1fb7961c37ae6f606ed0741ae509f PastaVerde
>>>>> cried:
>>>>>
>>>>>
>>>>>> On Sun, 08 Aug 2004 22:31:13 +0800, Aquila Deus
>>>>>> <aquila_deus@yahoo.co.uk> wrote:
>>>>>>
>>>>>>
>>>>>>> **** Post for FREE via your newsreader at post.usenet.com ****
>>>>>>>
>>>>>>> The puny human animal #89cc9fea8371254dc467f2a880c23845
>>>>>>> aquila_deus@yahoo.co.uk (Aquila Deus) cried:
>>>>>>>
>>>>>>>
>>>>>>>> 1.Open explorer
>>>>>>>> 2.Navigate through thousands of levels of directory tree...
>>>>>>>> ummm.. by mouse!
>>>>>>
>>>>>> Why don't you hit View->Toolbars->Address Bar once and for all,
>>>>>> then type in (or paste) the  path?
>>>>>
>>>>> Because windows' folders are usually badly named.. full of
>>>>> non-english, damned asian char, whitespaces, weird symbols, ...
>>>>> And auto-completion doesn't work when you're running something in
>>>>> the background (it uses a low-priority thread I guess)
>>>>
>>>> OK, your app, cygwin, was installed in a folder "full of
>>>> non-english, damned asian char, whitespaces, weird symbols", like
>>>> c:\cygwin, right?
>>>
>>> No, I was talking about other dirs like "C:\Documents and Settings"
>>> named by M$'s idiots. Cygwin's problems are mainly about
>>> permissions.
>>
>>
>> You got it right,  all you do is ADD qoutes around any directory
>> with white space,   just because Unix/Linux hates white space in the
>> file system doesn't mean everyone does....
>>
>>
>
> UNIX/Linux doesn't suffer from the whitespace problem at all and it
> works the same way with the quotes.

I almost never see spaces in the file system,  at least with Linux,  but I
see it a lot in Windows.   It also depends on my meaning of Unix/Linux,  did
I mean the OS or the User or both?    If Unix/Linux liked whitespace it
would work even with out qoutes,   like quite a few windows commands.
I know you it not hard to use white space in Unix/Linux but it seems not to
be used that much....

Tom Wilson wrote:
> Quantum Leaper wrote:
>
>> You got it right,  all you do is ADD qoutes around any directory
>> with white space,   just because Unix/Linux hates white space in the
>> file system doesn't mean everyone does....
>
>
> [twilson@goliath tmp]$ mkdir "Linux doesn\'t mind white space at all"
> [twilson@goliath tmp]$ ll
> total 1
> drwxr-xr-x    2 twilson  users          48 Aug  9 19:02 Linux doesn\'t
> mind white space at all
> [twilson@goliath tmp]$ cd Linux\ doesn\\\'t\ mind\ white\ space\ at\
> all/ [twilson@goliath Linux doesn\'t mind white space at all]$
> [twilson@goliath Linux doesn\'t mind white space at all]$ cd ..
> [twilson@goliath tmp]$ rm -rf Linux\ doesn\\\'t\ mind\ white\ space\
> at\ all/

Where did I say it was impossible,  all I said that it hates whitespace.
Also you example show that Windows is easier,  since I don't need the
backslashes at least for Windows.....

Quantum Leaper wrote:
> Tom Wilson wrote:
> 
>>Quantum Leaper wrote:
>>
>>
>>>You got it right,  all you do is ADD qoutes around any directory
>>>with white space,   just because Unix/Linux hates white space in the
>>>file system doesn't mean everyone does....
>>
>>
>>[twilson@goliath tmp]$ mkdir "Linux doesn\'t mind white space at all"
>>[twilson@goliath tmp]$ ll
>>total 1
>>drwxr-xr-x    2 twilson  users          48 Aug  9 19:02 Linux doesn\'t
>>mind white space at all
>>[twilson@goliath tmp]$ cd Linux\ doesn\\\'t\ mind\ white\ space\ at\
>>all/ [twilson@goliath Linux doesn\'t mind white space at all]$
>>[twilson@goliath Linux doesn\'t mind white space at all]$ cd ..
>>[twilson@goliath tmp]$ rm -rf Linux\ doesn\\\'t\ mind\ white\ space\
>>at\ all/
> 
> 
> Where did I say it was impossible,  all I said that it hates whitespace.
> Also you example show that Windows is easier,  since I don't need the
> backslashes at least for Windows.....

However, Windows can't do a tenth of what *nix can do from the 
commandline and rightly so since it was designed around the GUI.

Quoting and escaping from the commandline can be cumbersome sometimes, 
but, the flexibility you get in return is well worth it.

Very simplistic example...

[twilson@goliath twilson]$ echo -e "\nThe output of \`which date\` is 
`which date`\nAnd, `which date` returns \"`date`\"\n"

The output of `which date` is  /usr/bin/date
And, /usr/bin/date returns "Mon Aug  9 22:12:55 EDT 2004"

[twilson@goliath twilson]$

-- 
Tom Wilson
"Gee, Toto, I don't think we are in Kansas anymore."

On Tue, 10 Aug 2004 01:57:58 +0000, Quantum Leaper wrote:

You would still have to quote it from the command line.  And, this is a
very stupid position to take since any modern bash is going to escape the
whole thing for you by simply pressing tab.  In other words, not only
would you be faster on Linux, but you could escape the whole thing with
fewer key strokes than you could on Windows.  Shesh.

Cheers,

Greg

Quantum Leaper wrote:
> GreyCloud wrote:
> 
>>Quantum Leaper wrote:
>>
>>
>>>Aquila Deus wrote:
>>>
>>>
>>>>PastaVerde wrote in message
>>>>news:<hnbeh0hvan5o6a9u7mmfrbjm5roespmk34@4ax.com>...
>>>>
>>>>
>>>>>On Mon, 09 Aug 2004 14:24:13 +0800, Aquila Deus
>>>>><aquila_deus@yahoo.co.uk> wrote:
>>>>>
>>>>>
>>>>>
>>>>>>**** Post for FREE via your newsreader at post.usenet.com ****
>>>>>>
>>>>>>The puny human animal #63f1fb7961c37ae6f606ed0741ae509f PastaVerde
>>>>>>cried:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>On Sun, 08 Aug 2004 22:31:13 +0800, Aquila Deus
>>>>>>><aquila_deus@yahoo.co.uk> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>**** Post for FREE via your newsreader at post.usenet.com ****
>>>>>>>>
>>>>>>>>The puny human animal #89cc9fea8371254dc467f2a880c23845
>>>>>>>>aquila_deus@yahoo.co.uk (Aquila Deus) cried:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>1.Open explorer
>>>>>>>>>2.Navigate through thousands of levels of directory tree...
>>>>>>>>>ummm.. by mouse!
>>>>>>>
>>>>>>>Why don't you hit View->Toolbars->Address Bar once and for all,
>>>>>>>then type in (or paste) the  path?
>>>>>>
>>>>>>Because windows' folders are usually badly named.. full of
>>>>>>non-english, damned asian char, whitespaces, weird symbols, ...
>>>>>>And auto-completion doesn't work when you're running something in
>>>>>>the background (it uses a low-priority thread I guess)
>>>>>
>>>>>OK, your app, cygwin, was installed in a folder "full of
>>>>>non-english, damned asian char, whitespaces, weird symbols", like
>>>>>c:\cygwin, right?
>>>>
>>>>No, I was talking about other dirs like "C:\Documents and Settings"
>>>>named by M$'s idiots. Cygwin's problems are mainly about
>>>>permissions.
>>>
>>>
>>>You got it right,  all you do is ADD qoutes around any directory
>>>with white space,   just because Unix/Linux hates white space in the
>>>file system doesn't mean everyone does....
>>>
>>>
>>
>>UNIX/Linux doesn't suffer from the whitespace problem at all and it
>>works the same way with the quotes.
> 
> 
> I almost never see spaces in the file system,  at least with Linux,  but I
> see it a lot in Windows.   It also depends on my meaning of Unix/Linux,  did
> I mean the OS or the User or both?    If Unix/Linux liked whitespace it
> would work even with out qoutes,   like quite a few windows commands.
> I know you it not hard to use white space in Unix/Linux but it seems not to
> be used that much....
> 
> 

I've already found this situation a lot in OS X.  Apple seems to like 
white spaces to make the file system a bit more readable.  I've used it 
on occasion to make a few directories.

-- 
---------------------------------
My other computer is a VAX.

On Mon, 09 Aug 2004 21:49:28 -0500, Greg Copeland <nospam@nowhere.com>
wrote:

>On Tue, 10 Aug 2004 01:57:58 +0000, Quantum Leaper wrote:
>
>You would still have to quote it from the command line.  And, this is a
>very stupid position to take since any modern bash is going to escape the
>whole thing for you by simply pressing tab.  In other words, not only
>would you be faster on Linux, but you could escape the whole thing with
>fewer key strokes than you could on Windows.  Shesh.

Well, you might want to open a command prompt on XP and hit the tab
key, then.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, 10 Aug 2004 06:38:33 +0200,
 PastaVerde <> wrote:
> On Mon, 09 Aug 2004 21:49:28 -0500, Greg Copeland <nospam@nowhere.com>
> wrote:
>
>>On Tue, 10 Aug 2004 01:57:58 +0000, Quantum Leaper wrote:
>>
>>You would still have to quote it from the command line.  And, this is a
>>very stupid position to take since any modern bash is going to escape the
>>whole thing for you by simply pressing tab.  In other words, not only
>>would you be faster on Linux, but you could escape the whole thing with
>>fewer key strokes than you could on Windows.  Shesh.
>
> Well, you might want to open a command prompt on XP and hit the tab
> key, then.


Compared to Bash, tab completion on XP's "command line" is pathetic. 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBGIE+d90bcYOAWPYRAkKYAJ9bHJyF+WkGIzMsPhLzljBvFVkMiwCeOBSt
xgEPNksVj7WFjKy/S9ggr3Q=
=+XKb
-----END PGP SIGNATURE-----

-- 
Jim Richardson     http://www.eskimo.com/~warlock
RFC 882 put the dot in .com.

**** Post for FREE via your newsreader at post.usenet.com ****

The puny human animal #63f1fb7961c37ae6f606ed0741ae509f PastaVerde cried:

> On Mon, 09 Aug 2004 21:49:28 -0500, Greg Copeland <nospam@nowhere.com>
> wrote:
>
>>On Tue, 10 Aug 2004 01:57:58 +0000, Quantum Leaper wrote:
>>
>>You would still have to quote it from the command line.  And, this is a
>>very stupid position to take since any modern bash is going to escape the
>>whole thing for you by simply pressing tab.  In other words, not only
>>would you be faster on Linux, but you could escape the whole thing with
>>fewer key strokes than you could on Windows.  Shesh.
>
> Well, you might want to open a command prompt on XP and hit the tab
> key, then.

C:\Documents 0and Settings
C:\Documents 1and Settings
C:\Documents 2and Settings
C:\Documents 3and Settings
C:\Documents 4and Settings
C:\Documents 5and Settings
C:\Documents 6and Settings
C:\Documents 7and Settings
C:\Documents 8and Settings
C:\Documents 9and Settings
C:\Documents and Settings
C:\Documents bnd Settings
C:\Documents cnd Settings
C:\Documents dnd Settings
C:\Documents end Settings
C:\Documents fnd Settings
C:\Documents gnd Settings
C:\Documents hnd Settings
C:\Documents ind Settings
C:\Documents jnd Settings
C:\Documents knd Settings
C:\Documents lnd Settings
C:\Documents mnd Settings
C:\Documents nnd Settings
C:\Documents ond Settings
C:\Documents pnd Settings
C:\Documents qnd Settings
C:\Documents rnd Settings
C:\Documents snd Settings
C:\Documents tnd Settings
C:\Documents und Settings
C:\Documents vnd Settings
C:\Documents wnd Settings
C:\Documents xnd Settings
C:\Documents ynd Settings
C:\Documents znd Settings
C:\Documents �Aand Settings

:D


-- 
me = d2004xx = d2003xx = d2002xx

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 *** Usenet.com - The #1 Usenet Newsgroup Service on The Planet! ***
                      http://www.usenet.com
Unlimited Download - 19 Seperate Servers - 90,000 groups - Uncensored
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

**** Post for FREE via your newsreader at post.usenet.com ****

The puny human animal #bde6b724f8b707896523937387c0a182 The Ghost In The Machine <ewill@aurigae.athghost7038suus.net> cried:

> In comp.os.linux.advocacy, Aquila Deus
> <aquila_deus@yahoo.co.uk>
>  wrote
> on 8 Aug 2004 07:22:27 -0700
> <c5cfac8f.0408080622.248708db@posting.google.com>:

<snip>

> An interesting thought would be a "prescan" of some sort, but
> there's a danger of stale information.  Basically, the computer
> would say something to the effect of:
>
>     "I am about to delete these files and directories, but I've
>     noticed this list of discrepancies.  What should I do with
>     each of these discrepancies?"
>
> and the user would respond to this *before* the deletion commences.
> Failing that, the deletion would be undoable -- I think Microsoft
> had this notion in mind with the trashcan metaphor -- in some
> fashion.
>
> If one wants to get really cute the information would
> be updated dynamically; however, the only OS I know
> of that might have been able to do that is Amiga[D]OS,
> by registering a notification listener with a directory.
> I do not believe any Unix flavor has that option, although
> it would be a nice hack -- and there might even be such a
> beastie but if so I'm not sure where it is at this point;
> presumably readdir(3) would point thereto in its "SEE
> ALSO" area.

Linux has it :)

I remember there is an option when you config kernel... but this is my
one-year-old memory :)

-- 
me = d2004xx = d2003xx = d2002xx

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 *** Usenet.com - The #1 Usenet Newsgroup Service on The Planet! ***
                      http://www.usenet.com
Unlimited Download - 19 Seperate Servers - 90,000 groups - Uncensored
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

Error BR-549: MS DRM 1.0 rejects the following post from Quantum Leaper:

>> No, I was talking about other dirs like "C:\Documents and Settings"
>> named by M$'s idiots. Cygwin's problems are mainly about permissions.
>
> You got it right,  all you do is ADD qoutes around any directory with white
> space,   just because Unix/Linux hates white space in the file system
> doesn't mean everyone does....

Actually, UNIX/Linux will take just about any ASCII character in a file-name,
including tabs and control characters.  I just created two files:

   tab^Ifile
   tab^Gfile

where ^I is a tab and ^G is a bell character.  Since these characters show up
like this in a listing:

   tab?file
   tab?file

you can have a little fun with this feature <grin>.

You need to leap outside the DOS box a little more, Quantum.

Why are young kids so ignorant of UNIX?

-- 
[X] Check here to always trust content from Lin�nut

Error BR-549: MS DRM 1.0 rejects the following post from Jim Richardson:

>> Well, you might want to open a command prompt on XP and hit the tab
>> key, then.
>
> Compared to Bash, tab completion on XP's "command line" is pathetic. 

Indeed.  But at least it is the default now (at least on Win 2003 Server).

By the way, we've been doing some DOS scripting lately, and noticed that
Microsoft has upgraded its crappy command-line language quite a bit with some
features that they've patently copped from UNIX.  It's still crappy, but I
think it indicates just how much BSD influence Longhorn will have, if and when
it comes out.

Microsoft... "We're number two, we try harder."  <chuckle>

-- 
[X] Check here to always trust content from Lin�nut

On Tue, 10 Aug 2004 06:50:30 -0500, Lin�nut <lin�nut@bone.com> wrote:

>Error BR-549: MS DRM 1.0 rejects the following post from Quantum Leaper:
>
>>> No, I was talking about other dirs like "C:\Documents and Settings"
>>> named by M$'s idiots. Cygwin's problems are mainly about permissions.
>>
>> You got it right,  all you do is ADD qoutes around any directory with white
>> space,   just because Unix/Linux hates white space in the file system
>> doesn't mean everyone does....
>
>Actually, UNIX/Linux will take just about any ASCII character in a file-name,
>including tabs and control characters.

... and / < > |  of course... just kidding!

Can it take Unicode characters as on NTFS?

On Tue, 10 Aug 2004 18:13:51 +0200, PastaVerde wrote:

> 
> .. and / < > |  of course... just kidding!
> 
> Can it take Unicode characters as on NTFS?

I'm not aware of any linux FS which are unicode compliant.  Don't take
that as an absolute.  I'm just don't think any do support unicode.

Cheers,

Greg

PastaVerde wrote:

> On Tue, 10 Aug 2004 06:50:30 -0500, Lin�nut <lin�nut@bone.com> wrote:
> 
> 
>>Error BR-549: MS DRM 1.0 rejects the following post from Quantum Leaper:
>>
>>
>>>>No, I was talking about other dirs like "C:\Documents and Settings"
>>>>named by M$'s idiots. Cygwin's problems are mainly about permissions.
>>>
>>>You got it right,  all you do is ADD qoutes around any directory with white
>>>space,   just because Unix/Linux hates white space in the file system
>>>doesn't mean everyone does....
>>
>>Actually, UNIX/Linux will take just about any ASCII character in a file-name,
>>including tabs and control characters.
> 
> 
> .. and / < > |  of course... just kidding!
> 
> Can it take Unicode characters as on NTFS?
> 

Of course.

-- 
---------------------------------
My other computer is a VAX.

In comp.os.linux.advocacy, Diogenes
<diogenes@athens.gr>
 wrote
on Mon, 9 Aug 2004 07:29:44 -0700
<NQLRc.14287$_C6.7111@cyclops.nntpserver.com>:
> PastaVerde wrote:
>> On Mon, 09 Aug 2004 14:24:13 +0800, Aquila Deus
>> <aquila_deus@yahoo.co.uk> wrote:
>> 
>>> **** Post for FREE via your newsreader at post.usenet.com ****
>>> 
>>> The puny human animal #63f1fb7961c37ae6f606ed0741ae509f PastaVerde
>>> cried: 
>>> 
>>>> On Sun, 08 Aug 2004 22:31:13 +0800, Aquila Deus
>>>> <aquila_deus@yahoo.co.uk> wrote:
>>>> 
>>>>> **** Post for FREE via your newsreader at post.usenet.com ****
>>>>> 
>>>>> The puny human animal #89cc9fea8371254dc467f2a880c23845
>>>>> aquila_deus@yahoo.co.uk (Aquila Deus) cried: 
>>>>> 
>>>>>> 1.Open explorer
>>>>>> 2.Navigate through thousands of levels of directory tree...
>>>>>> ummm.. by mouse! 
>>>> 
>>>> Why don't you hit View->Toolbars->Address Bar once and for all, then
>>>> type in (or paste) the  path?
>>> 
>>> Because windows' folders are usually badly named.. full of
>>> non-english, damned asian char, whitespaces, weird symbols, ... And
>>> auto-completion doesn't work when you're running something in the
>>> background (it uses a low-priority thread I guess)
>> 
>> OK, your app, cygwin, was installed in a folder "full of non-english,
>> damned asian char, whitespaces, weird symbols", like c:\cygwin, right?
>
> <snigger> Give up, you'd never understand.  linux has made you too stupid.
>

Pssst....d00d.  Green Noodles is a Winvocate. :-)

-- 
#191, ewill3@earthlink.net
It's still legal to go .sigless.

Error BR-549: MS DRM 1.0 rejects the following post from Greg Copeland:

> On Tue, 10 Aug 2004 18:13:51 +0200, PastaVerde wrote:
>
>> .. and / < > |  of course... just kidding!
>> 
>> Can it take Unicode characters as on NTFS?
>
> I'm not aware of any linux FS which are unicode compliant.  Don't take
> that as an absolute.  I'm just don't think any do support unicode.

Linux supports Microsoft's Joliet extension of ISO 9660, so CD-ROMs support
unicode:

http://www.redhat.com/docs/manuals/linux/RHL-8.0-Manual/admin-primer/s1-storage-basics.html

I suppose all Linux file systems support UTF-8, and are hence unicode
compatible in some partial manner.

-- 
[X] Check here to always trust content from Lin�nut

Error BR-549: MS DRM 1.0 rejects the following post from PastaVerde:

> On Tue, 10 Aug 2004 06:50:30 -0500, Lin�nut <lin�nut@bone.com> wrote:
>
>>> You got it right,  all you do is ADD qoutes around any directory with white
>>> space,   just because Unix/Linux hates white space in the file system
>>> doesn't mean everyone does....
>>
>>Actually, UNIX/Linux will take just about any ASCII character in a file-name,
>>including tabs and control characters.
>
> .. and / < > |  of course... just kidding!

Yeah, those too.

> Can it take Unicode characters as on NTFS?

Not really.  I couldn't get it to accept a null character in a filename, though
the ESC character was no problem.

-- 
[X] Check here to always trust content from Lin�nut

On Tue, 10 Aug 2004 17:09:28 -0500, Lin�nut <lin�nut@bone.com> wrote:

> I suppose all Linux file systems support UTF-8, and are hence unicode
> compatible in some partial manner.

Dude, UTF-8 _is_ Unicode!  It is the real deal, not a half-measure.

There are several different representations of Unicode.  Windows NT
happens to use UTF-16 but Unix has gone with the UTF-8 encoding instead.
One reason for this surely is that existing filesystems could work with
UTF-8 without modification.

<http://www.unicode.org/standard/principles.html>

   "The Unicode Standard defines three encoding forms that allow the
   same data to be transmitted in a byte, word or double word oriented
   format (i.e. in 8, 16 or 32-bits per code unit). All three encoding
   forms encode the same common character repertoire and can be
   efficiently transformed into one another without loss of data. The
   Unicode Consortium fully endorses the use of any of these encoding
   forms as a conformant way of implementing the Unicode Standard."


-- 
 -| Bob Hauck
 -| To Whom You Are Speaking
 -| http://www.haucks.org/

Lin�nut wrote:

> Error BR-549: MS DRM 1.0 rejects the following post from Quantum Leaper:
> 
>>> No, I was talking about other dirs like "C:\Documents and Settings"
>>> named by M$'s idiots. Cygwin's problems are mainly about permissions.
>>
>> You got it right,  all you do is ADD qoutes around any directory with
>> white
>> space,   just because Unix/Linux hates white space in the file system
>> doesn't mean everyone does....
> 
> Actually, UNIX/Linux will take just about any ASCII character in a
> file-name,
> including tabs and control characters.  I just created two files:
> 
>    tab^Ifile
>    tab^Gfile
> 
> where ^I is a tab and ^G is a bell character.  Since these characters show
> up like this in a listing:
> 
>    tab?file
>    tab?file
> 
> you can have a little fun with this feature <grin>.
> 
> You need to leap outside the DOS box a little more, Quantum.
> 
> Why are young kids so ignorant of UNIX?
> 
> --
> [X] Check here to always trust content from Lin�nut
That is an old (25+ years) of hiding files. The listing shows up as
??????.???
and (supposedly) only the author could access it.
-- 
Russ Lyttle
Not Powered by ActiveX
http://home.earthlink.net/~lyttlec/philosophy/logos.html

aquila_deus@yahoo.co.uk (Aquila Deus) wrote in message news:<c5cfac8f.0408080622.248708db@posting.google.com>...
> 1.Open explorer
> 2.Navigate through thousands of levels of directory tree... ummm.. by mouse!
> 3.Select the directory (click the damned button again!), press Shift-Delete
> 4.Move the mouse pointer and click on "Yes" button
> 5.Wait...
> 6.Popup: "... sure to remove read-only files?"   <repeat step 4>
> 7.Wait...
> 8.Popup again! "... sure to remove system files?"   <repeat step 4>
> 9.Wait...
> 10.Damned Popup again!! "The file ... is locked"!
> 11.Open process explorer
> 12.Search for the locked file/dll handle
> 13.Right click on the handle, choose "Kill"
> 14.Go back to explorer, <repeat step 4>
> 15. ....
> 
> 
> Guess how much time I wasted just to remove a trash cygwin dir?
> 
> <f**k!>

Idiot, RTFM!


Peter Bilt
SP2!!!!!!

In article <G5GdnXqTsaY81YTcRVn-jQ@comcast.com> (Tue, 10 Aug 2004 17:13:53
-0500), Lin�nutlin�nut wrote:

>> Can it take Unicode characters as on NTFS?

I don't know about Unicode.

> I couldn't get it to accept a null character in a filename, though
> the ESC character was no problem.

NUL and '/' are the only forbidden characters.

On Tue, 10 Aug 2004 17:09:28 -0500, Lin�nutlin�nut wrote:
> I suppose all Linux file systems support UTF-8, and are hence unicode
> compatible in some partial manner.

Good point, I forgot about iso9660 and other associated removable media
filesystems.  Aside from those and the distributed filesystems, I don't
believe the other filesystems support unicode.

Good point, just the same.

Cheers,

Greg

Error BR-549: MS DRM 1.0 rejects the following post from Bob Hauck:

> On Tue, 10 Aug 2004 17:09:28 -0500, Lin�nut <lin�nut@bone.com> wrote:
>
>> I suppose all Linux file systems support UTF-8, and are hence unicode
>> compatible in some partial manner.
>
> Dude, UTF-8 _is_ Unicode!  It is the real deal, not a half-measure.
>
> There are several different representations of Unicode.  Windows NT
> happens to use UTF-16 but Unix has gone with the UTF-8 encoding instead.
> One reason for this surely is that existing filesystems could work with
> UTF-8 without modification.

Okay, my bad, and UNIX's good.  Actually, I now recall having read what you
say, I think in Eric Raymond's book.

> <http://www.unicode.org/standard/principles.html>
>
>    "The Unicode Standard defines three encoding forms that allow the
>    same data to be transmitted in a byte, word or double word oriented
>    format (i.e. in 8, 16 or 32-bits per code unit). All three encoding
>    forms encode the same common character repertoire and can be
>    efficiently transformed into one another without loss of data. The
>    Unicode Consortium fully endorses the use of any of these encoding
>    forms as a conformant way of implementing the Unicode Standard."

Thanks for smackin' me up on this one!

-- 
[X] Check here to always trust content from Lin�nut

Error BR-549: MS DRM 1.0 rejects the following post from Greg Copeland:

> On Tue, 10 Aug 2004 17:09:28 -0500, Lin�nutlin�nut wrote:
>> I suppose all Linux file systems support UTF-8, and are hence unicode
>> compatible in some partial manner.
>
> Good point, I forgot about iso9660 and other associated removable media
> filesystems.  Aside from those and the distributed filesystems, I don't
> believe the other filesystems support unicode.
>
> Good point, just the same.

Turns out we're wrong!

-- 
[X] Check here to always trust content from Lin�nut

peterbilt_usa@hotmail.com (Peter Bilt) wrote in message news:<30a094b6.0408101701.6ac346d6@posting.google.com>...
> aquila_deus@yahoo.co.uk (Aquila Deus) wrote in message news:<c5cfac8f.0408080622.248708db@posting.google.com>...
> > 1.Open explorer
> > 2.Navigate through thousands of levels of directory tree... ummm.. by mouse!
> > 3.Select the directory (click the damned button again!), press Shift-Delete
> > 4.Move the mouse pointer and click on "Yes" button
> > 5.Wait...
> > 6.Popup: "... sure to remove read-only files?"   <repeat step 4>
> > 7.Wait...
> > 8.Popup again! "... sure to remove system files?"   <repeat step 4>
> > 9.Wait...
> > 10.Damned Popup again!! "The file ... is locked"!
> > 11.Open process explorer
> > 12.Search for the locked file/dll handle
> > 13.Right click on the handle, choose "Kill"
> > 14.Go back to explorer, <repeat step 4>
> > 15. ....
> > 
> > 
> > Guess how much time I wasted just to remove a trash cygwin dir?
> > 
> > <f**k!>
> 
> Idiot, RTFM!

The Maunal tells me to reboot to delete locked files. Should I follow it?

On Tue, 10 Aug 2004 22:10:10 -0500, Lin�nutlin�nut wrote:

> Error BR-549: MS DRM 1.0 rejects the following post from Greg Copeland:
> 
>> On Tue, 10 Aug 2004 17:09:28 -0500, Lin�nutlin�nut wrote:
>>> I suppose all Linux file systems support UTF-8, and are hence unicode
>>> compatible in some partial manner.
>>
>> Good point, I forgot about iso9660 and other associated removable media
>> filesystems.  Aside from those and the distributed filesystems, I don't
>> believe the other filesystems support unicode.
>>
>> Good point, just the same.
> 
> Turns out we're wrong!

I thought I remembered the distributed FS supporting unicode.

Cheers,

greg

aquila_deus@yahoo.co.uk (Aquila Deus) writes:

> The Maunal tells me to reboot to delete locked files. Should I follow it?

Really?  Cite?  Which "Maunal"?

-- 
Jesse F. Hughes
"Contrariwise," continued Tweedledee, "if it was so, it might be, and
if it were so, it would be; but as it isn't, it ain't. That's logic!"
                                                     -- Lewis Carroll