Prev: Rolex Watch wholesale (paypal payment and free shipping)
Next: Low level formatting of laser servo diskettes
From: mjt on 22 Jun 2010 13:31
On Tue, 22 Jun 2010 02:18:54 +0000 (UTC)
no.top.post(a)gmail.com wrote:

> Is this OS operating correctly ?

To be a techno weenie dweeb, the 'ls' command is
responsible for its output, not the operating system.

> > [root(a)localhost Legal]# ls *op
> > ls: *op: No such file or directory

Why are you running as root? I hope you're not
running root as a "regular user" account! Break
yourself of this bad habit!!

> > [root(a)localhost Legal]# ls *op*
> > Apr26Ltop Legal:Dictionarys Legal:Top.Bak Log.Bak
> > Legal:Definitions LEGAL:SU LEGALXLA Routledge
> > Legal:Definitions.Bak Legal:Top Log
> > [root(a)localhost Legal]#
>
> Doesn't "*op" include "Legal:Top" ?
> How the hell does it include "LEGALXLA" ?

Let's run through a couple of tests ... hopefully, the light will shine :)

mtobler(a)ren:~> ls -l | grep tt
-rw-r--r-- 1 mtobler users 105315 2010-05-13 09:22 attack.png
-rw-r--r-- 1 mtobler users 19466 2010-01-19 13:52 letter-to-jvc.odt
-rw-r--r-- 1 mtobler users 17953 2010-05-26 19:11 totto.ods
mtobler(a)ren:~> mkdir letters && cd letters && touch letter1 letter2 letiter3 && mkdir LEGALXLA
mtobler(a)ren:~/letters> cd

mtobler(a)ren:~> mkdir witt
mtobler(a)ren:~> ls *tt
mtobler(a)ren:~> touch witt/test
mtobler(a)ren:~> ls *tt
test
mtobler(a)ren:~> ls -l | grep tt
-rw-r--r-- 1 mtobler users 105315 2010-05-13 09:22 attack.png
drwxr-xr-x 3 mtobler users 4096 2010-06-22 12:22 letters
-rw-r--r-- 1 mtobler users 19466 2010-01-19 13:52 letter-to-jvc.odt
-rw-r--r-- 1 mtobler users 17953 2010-05-26 19:11 totto.ods
drwxr-xr-x 2 mtobler users 4096 2010-06-22 12:24 witt

mtobler(a)ren:~> ls *tt*
attack.png letter-to-jvc.odt totto.ods

letters:
LEGALXLA letiter3 letter1 letter2

witt:
test
mtobler(a)ren:~>


--
Our vision is to speed up time, eventually eliminating it.
-- Alex Schure
<<< Remove YOURSHOES to email me >>>

From: mjt on 22 Jun 2010 13:33
On Tue, 22 Jun 2010 17:10:35 +0000 (UTC)
J G Miller <miller(a)yoyo.ORG> wrote:

> On Tuesday, June 22nd, 2010 11:57:07 -0500, mjt asked:
> > dumb question - how did all those files show up in the (ls *op*)
> > list when you only have one file in the dir?:
>
> Yes, it is at first a little confusing.
>
> In fact there are no "files" in the directory, only the single
> directory topsyturvy.
>
> So when you do ls *op*, it matches the op in topsyturvy and then
> lists all of the files contained within, including the LEGALXLA.

The oversight on my part is that I assumed John did not
create all those files in the topsyturvy dir And we all
know what "assumed" means :)

--
"I have made mistakes but I have never made the mistake of claiming
that I have never made one."
-- James Gordon Bennett
<<< Remove YOURSHOES to email me >>>

From: Tauno Voipio on 22 Jun 2010 14:29
no.top.post(a)gmail.com wrote:
> Is this OS operating correctly ?
>
>> [root(a)localhost Legal]# ls *op
>> ls: *op: No such file or directory
>> [root(a)localhost Legal]# ls *op*
>> Apr26Ltop Legal:Dictionarys Legal:Top.Bak Log.Bak
>> Legal:Definitions LEGAL:SU LEGALXLA Routledge
>> Legal:Definitions.Bak Legal:Top Log
>> [root(a)localhost Legal]#
>
> Doesn't "*op" include "Legal:Top" ?
> How the hell does it include "LEGALXLA" ?
>
> Does anybody else believe is subconcious knowledge, like what told me to try
> `ls *op*` to find 'Legal:Top'
>
> While writing this, I think I discovered why Legal:Top is not seen in `ls *op`.
> So why didn't they restrict the valid file-ID to avoid this problem?
>
> TIA.
>

What do:

ls -al
ls -al *op*

show?

--

Tauno Voipio
tauno voipio (at) iki fi
From: Robert Heller on 22 Jun 2010 14:33
At Tue, 22 Jun 2010 17:10:35 +0000 (UTC) J G Miller <miller(a)yoyo.ORG> wrote:

>
> On Tuesday, June 22nd, 2010 11:57:07 -0500, mjt asked:
> > dumb question - how did all those files show up in the (ls *op*) list
> > when you only have one file in the dir?:
>
> Yes, it is at first a little confusing.
>
> In fact there are no "files" in the directory, only the single
> directory topsyturvy.
>
> So when you do ls *op*, it matches the op in topsyturvy and then
> lists all of the files contained within, including the LEGALXLA.
>
> This is why it is always a good idea to use ls -l rather than
> ls to see what the filetypes of the entities are which are present.

-d and -F are also good options to use on occasion...

>

--
Robert Heller -- 978-544-6933
Deepwoods Software -- Download the Model Railroad System
http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows
heller(a)deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/

From: Chick Tower on 22 Jun 2010 14:50
On 2010-06-22, no.top.post(a)gmail.com <no.top.post(a)gmail.com> wrote:
> Is this OS operating correctly ?
>
>> [root(a)localhost Legal]# ls *op
>> ls: *op: No such file or directory
>> [root(a)localhost Legal]# ls *op*
>> Apr26Ltop Legal:Dictionarys Legal:Top.Bak Log.Bak
>> Legal:Definitions LEGAL:SU LEGALXLA Routledge
>> Legal:Definitions.Bak Legal:Top Log
>> [root(a)localhost Legal]#
>
> Doesn't "*op" include "Legal:Top" ?
> How the hell does it include "LEGALXLA" ?

I see you used Oberon Mail to post this. Is this a Linux question or an
Oberon question?

If it's about Linux, try "ls -o" or "ls -l". (That's a lower-case L.)
That should show you if the mysteriously-returned filenames are in the
current working directory or somewhere else. If you have a directory
that matches *op*, though, the command "ls *op*" would return every file
in that directory, I believe.

I didn't know or even wonder about this before, but it was interesting
learning about this through experimentation.
--
Chick Tower

For e-mail: aols2 DOT sent DOT towerboy AT xoxy DOT net
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Rolex Watch wholesale (paypal payment and free shipping)
Next: Low level formatting of laser servo diskettes