Re: wine issues
From: mjt-pca (not_at_here.com)
Date: 09/26/03
- Next message: Walter Mautner: "Re: hooking linux up to router"
- Previous message: Robert Newson: "Re: I can't delete a virus"
- In reply to: Paul Lutus: "Re: wine issues"
- Next in thread: Paul Lutus: "Re: wine issues"
- Reply: Paul Lutus: "Re: wine issues"
- Reply: Paul Lutus: "Re: wine issues"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 26 Sep 2003 18:09:12 GMT
Paul Lutus wrote:
> mjt-pca wrote:
>
>> Paul Lutus wrote:
>>
>>> mjt-pca wrote:
>>>
>>>> Kamil wrote:
>>>>
>>>>>> have you run wine? you have to configure wine... when you do, pay
>>>>>> very
>>>>> close
>>>>>> attention to what your doing, as it basically will explain the setup
>>>>>> of
>>>>> the
>>>>>> Windows programs... you'll create your "Virtual" C drive etc...
>>>>>
>>>>> the problem i'm having is running it... where do i go to find the
>>>>> executable?
>>>>
>>>> try
>>>>
>>>> `find / -name wine`
>>>
>>> Please! That is the very slowest way to find something on a Linux
>>> system.
>>
>> On *ALL* Linux systems, hmmmmmmmmm?
>
> Your words, not mine. Read the first post. "Mandrake Linux 9.1".
Yes, Although the poster uses Redhat, the reader of a post to alt.linux
could be using ANY Linux such as Linux for the IBM mainframe, the Mac,
Sparc.... As well as CURRENT distributions such as Linux-BBC which the last
I checked does not contain whereis or locate. `find` will be found on more
distributions than locate and/or whereis. Since messages posted here can be
read by people that use ANY distribution for any platform, I post solutions
that any _*READER*_ can use. You have a problem with that? TO BAD.
> Virtually
> all recent Linux releases have both "whereis" and "locate." AFAIK all
> recent releases have "whereis."
>
Virtually but not ALL!!! I don't know why I knew you would be so self
centered that you would not accept giving a generic Linux answer in a
generic Linux usenet group, Let's take a look at what POS's whereis and
locate really are.
First, let's look at whereis. On my computer I have the file "cats" in
several places and I want to find where they are, so I use the command
whereis using the format YOU suggested:
[user@bear user]$ whereis cats
cats:
Oops, Guess I was wrong, eh? But I read a bit in man and tired a few things
and found I can specify what directory to search in. Lets be sure and start
the search at "/"
[user@bear user]$ whereis -B / cats
[user@bear user]$
Still, guess I was wrong about having any files called cats, eh? Let's try
something else, eh?
[user@bear user]$ whereis -B /* cats
[user@bear user]$
Nope, oops, did not read far enough down the man page:
[user@bear user]$ whereis -B /* -f cats
cats: /opt/cats
Damn, I finally found that file!!!! But I had to use a global and tell it
search all the directories under / for a file! Whereis does NOT SEARCH THE
WHOLE DIRECTORY TREE by default, nor can you just say start at "/". But
wait, there is MORE! I know that there are more files called cats on my
system so I try something else...
whereis -B /*/* -f cats
cats: /home/user/cats
Damn, whereis does not even search the HOME directory unless I put in /*/*??
But wait, when I do that, it does not find the file cats in /opt! That
SUCKS! But I have another file called cats on my system, lets try to find
it...
whereis -B /*/*/* -f cats
bash: /usr//bin/whereis: Argument list too long
Damn, I'm not going to be able to find it with whereis that suck ass way so
here we go:
whereis -B /export/*/*/*/*/* -f cats
cats: /export/whereis/is/really/fucked/eh/cats
Nope, I am not going to tell people to use whereis as a filesystem wide
search for file. The OP compiled and installed from source. I'm not sure
what instructions he used. He may have found some obscure set of
instructions, or made a _mistake_ that ended up installing in /opt or /wine
for that matter and whereis would not have found it. Of course, the whereis
man page sort of let me know this would happen:
FILES
/{bin,sbin,etc}
/usr/{lib,bin,old,new,local,games,include,etc,src,man,sbin,
X386,TeX,g++-include}
/usr/local/{X386,TeX,X11,include,lib,man,etc,bin,games,emacs}
Gee, guess where it searches and take a look, no /home! No /opt! There may
be some trick to get whereis to work but I don't see it on the man page!
Now, let's deal with locate! Do a locate bash and see what you get! On my
system I get 130 lines!
[matt@bear /]$ locate bash | wc -l
130
Not good. And heaven help the guy if he is trying to locate a file named
"class", locate returns 7694 lines on my system, but I search two linux
installs so cut that to 3847 lines. Much more manageable, eh?
Now I will admit that I made a mistake on telling the user the best way to
use the find command,
[matt@bear /]$ find / -name bash 2>/dev/null
/free/bin/bash
/bin/bash
DAMN, look at that, EXACTLY what I want!!!! As for finding my file class,
[matt@bear /]$ find / -name class 2>/dev/null
/opt/class
Again, exactly what *I* wanted, the single file.
Yeah, you can recomend search utilities that don't search the whole
filesystem or return thousands of lines just because the word is contained
SOMEWHERE in the filename... I'll stick with telling them about find so
they can find what they are looking for no matter where it is on the file
system or how many files *contain* the word.
- Next message: Walter Mautner: "Re: hooking linux up to router"
- Previous message: Robert Newson: "Re: I can't delete a virus"
- In reply to: Paul Lutus: "Re: wine issues"
- Next in thread: Paul Lutus: "Re: wine issues"
- Reply: Paul Lutus: "Re: wine issues"
- Reply: Paul Lutus: "Re: wine issues"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
