Patrick Shanahan wrote:
* doc
[07-23-04 15:46]: Patrick Shanahan wrote:
either ndiswrapper is *not* an executable or it is *not* in root's path.
How do I determine if it is an executable?
How do I cause it to be in root's path?
This, of course, leaves unanswered the question of why the make install did not cause ndiswrapper to be set up correctly -- a question for another day! ;-)
First question answer. See if executable is set in the permissions. you@local:~> ls -l /<location>/ndiswrapper
Second question answer. Add the path to <filename> to root's path.
but I suspect that the answers make little sense to you. Just off-hand, I would suggest that you need to spend some time with the Admin and User manuals you received with your distro. Your questions are of a *very* basic level.
I have spent hundreds of dollars and hundreds of hours reading manuals and online how-to's, mans, etc. The problem is they all assume elements of knowledge and thus skip them -- even in instructions that claim to be "basic". I frankly no longer have the funds and time to try to figure out why "make install" is not properly coded to get the job done and to try and guess the correct workaround -- the coder should have written the necessary tests and code to handle the exceptions -- or to at least write error messages that are less cryptic and more helpful than M$. I should be able to type "help set permissions executable" and read simple instructions with complete examples within Suse instead of a string and list of variables designed for someone already well-versed in linux command parsing. I should be able to type "help add path to root's path" and read the same. Man -k output is generally a nightmare, e.g. one sends "man -k path" and gets essentially and useless useless dump or every command that includes the word "path". Some of the items on the list look like a Webster's dictionary definition that uses the word in its own definition -- not helpful -- or that references obscure terminology -- not newbie friendly. As Linux tries to move into general use the lack of truly basic instructions in a highly accessible and easily understood format will make or break the effort -- things have improved but still have along way to go. Meanwhile I just want make install to make install ndiswrapper, not to send me into days wasted trying to figure out what the incomplete make install code did wrong. Is that too much to ask? *Rant Off* Sorry, just frustrated because life is busy and I keep imagining that computers are supposed to make things more rather than less efficient! Linux is better than M$ Windows but still wastes far too much of my time. ;-\ -- Thanks! & 73, doc kd4e West Central Florida Drake, Heathkit, Kenwood, TenTec, Yaesu Radio Life: http://www.gospelcom.net/twr/ Linux-Incompatible hardware is defective! USA Pres. Election 2004: http://www.rnc.org/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~