Date: Wed, 29 Dec 1999 21:40:31 +0000 From: Mark Ovens <mark@ukug.uk.freebsd.org> To: Novocaer <_novocaer_@usa.net> Cc: stable@freebsd.org Subject: Re: 3.2 executables won't run Message-ID: <19991229214031.V1290@marder-1> In-Reply-To: <19991229212951.6807.qmail@nw171.netaddress.usa.net> References: <19991229212951.6807.qmail@nw171.netaddress.usa.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 29, 1999 at 02:29:51PM -0700, Novocaer wrote:
> Dear sirs,
> as it happens my first experience with FreeBSD is with 3.2-Stable,
> and i've yet to see this sort of problem ever.
> When i run a file, that should run, i get error message as if it didn't
> exist. So i check permissions- they're OK. I check it with "file"-
> the output seems reasonable (executable, stripped etc.). So i go hmmm.
> Maybe that's a shell problem. I change the shell- nothing. So i go hmmm.
> Maybe i loaded one or more modules that are somehow defective. Unloading-
> Nothing. So i go hmmm. Maybe i should try something else:
> #cat >asd <<EOF
> echo qwerty
> EOF
> #chmod a+x asd
> "file" on "asd" says "text file", but when i run it- you guessed- nothing.
> So i go hmmm. Maybe pleading to the CPU would help? So i type:
Ah, did you type ``./asd'' to run it (unless the current directory is
in your path):
marder-1# cat >asd <<EOF
echo qwerty
EOF
marder-1# chmod a+x asd
marder-1# asd
asd: Command not found.
marder-1# ./asd
qwerty
marder-1#
The same applies to your C program (use ``./a.out'')
If you've come to FreeBSD from Windows you need to know that FreeBSD
(in fact all *nixes) don't look in the current directory first (or at
all unless ``.'' is in your $PATH - which you *shouldn't* do)
> #cat >a.c <<EOF
> main(){
> printf('qwerty');
> }
> EOF
> #gcc a.c
> and get executable "a.out" that won't run either. So i go hmmm.
> #gdb a.out
> looking through the main() procedure reveals nothing strange.
> I got a feeling i'm missing something big here...
> Additional (Maybe) important data to analyse:
> A. I was unable to diferentiate the files that run from those that don't.
> It's not owner dependant, size dependant, shell dependant, in or out
> of X, loadable modules or not, made for Linux or not, not user
> dependant- i tried real hard.
> B. I used the same set of CD's to install on a different station (200mhz,
> 64mb, 6.4GB pentium) and the same problem appeared there.
> C. I tried it on different installs, expert/novice, w/ developer or w/o-
> again- nothing.
> D. Yes, i do hummm a-lot.
>
> Thank you.
>
>
> ----------------------------------------------------------------
> TagLine Thieves Guild Official Member # 31415926535
> ----------------------------------------------------------------
>
> ____________________________________________________________________
> Get free email and a permanent address at http://www.netaddress.com/?N=1
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
--
"there's a long-standing bug relating to the x86 architecture
that allows you to install Windows too"
-Matthew D. Fuller
________________________________________________________________
FreeBSD - The Power To Serve http://www.freebsd.org
My Webpage http://ukug.uk.freebsd.org/~mark/
mailto:mark@ukug.uk.freebsd.org http://www.radan.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991229214031.V1290>