Hello Tim -

Ok, here's some results - we may be onto something here:

Ls -la /bin/sh gives this: 
Lrwxrwxrwx 1 root root 4 2007-02-03 14:43 /bin/sh -> bash*
I think that's correct, that /bin/sh is an "alias" for bash, is that the
correct technology?

But here's the strange thing:
Running bootstrap like this: ./bootstrap
Gives
-bash: ./bootstrap /bin/sh^M: bad interpeter: no such file or dir

I dunno what "/bin/sh^M" means, but I'm not sure that's correct. There must
be something wrong here, because I think to that it should execute properly,
or I've goofed up on something during the install.

Running
Bash ./bootstrap
Gives me the exact results as  sh ./bootstrap, the same "command not found"
line happens.

I'm logged in as root. Could this be some sort of a priviledge problem?

Leland 


Leland, [EMAIL PROTECTED]
Remember, if it ain't broke, you're not tryin'!!
The sooner you fall behind, the more time you will have to catch up
A common mistake people made when designing something completely foolproof
was to underestimate the ingenuity of complete fools 
 And remember: An amateur built the Ark. Titanic was built by professionals.

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tim
Sailer
Sent: Sunday, February 04, 2007 11:18 PM
To: owfs-developers@lists.sourceforge.net
Subject: Re: [Owfs-developers] Newbie question


On Mon, February 5, 2007 0:02, Leland Helgerson said:
> Hello all -
>
> Ok, some more info is gathered.
>
> Sh is bash - I checked - I'm glad that at least I knew how to do that.

Based on your output below, I'm inclined to disagree with you...

What does 'ls -la /bin/sh' give you?

> I thought I may have figured it out in that I created a directory 
> /OWFS/ not /owfs/, I didn't know if the caps in the sub name would 
> make a difference, but it doesn't appear so. One thing, I've got some 
> QNX experience but not Linux, the /owfs/ directory is at the root of 
> the drive, not at /root/owfs/, I'm not used to a "/root/" directory, 
> so I'm not sure if the directory location would make a difference.
>
> Here's what I get when doing the bootstrap (cut & pasted from terminal
> window):
>
> [EMAIL PROTECTED]:/owfs# sh ./bootstrap
> : command not found:
  ^^^^^^^^^^^^^^^^^^^^^

This is why I think you are not using standard bash. Try leaving out the
'sh' and just run './bootstrap'.

Or, try running 'bash bootstrap'

The scripts are executable, so you shouldn't have to run them under 'sh'.
I seem to remember seeing things like this waaaaay back when I had to admin
a machine that had 'ash' symlinked to /bin/sh.

Tim
--
Tim Sailer
Coastal Internet, Inc.
www.buoy.com
631-399-2910


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers

Reply via email to