From owner-freebsd-questions Sat Apr 7 12: 5:46 2001 Delivered-To: freebsd-questions@freebsd.org Received: from dire.bris.ac.uk (dire.bris.ac.uk [137.222.10.60]) by hub.freebsd.org (Postfix) with ESMTP id BA4BC37B424 for ; Sat, 7 Apr 2001 12:05:42 -0700 (PDT) (envelope-from Jan.Grant@bristol.ac.uk) Received: from mail.ilrt.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP; Sat, 7 Apr 2001 20:05:35 +0100 Received: from cmjg (helo=localhost) by mail.ilrt.bris.ac.uk with local-esmtp (Exim 3.16 #1) id 14ly08-0006Sa-00; Sat, 07 Apr 2001 20:04:00 +0100 Date: Sat, 7 Apr 2001 20:04:00 +0100 (BST) From: Jan Grant To: Stuart Duckworth Cc: freebsd-questions Subject: Re: errors In-Reply-To: <000701c0bf89$fcd1b340$c36430d5@adbr03860> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 7 Apr 2001, Stuart Duckworth wrote: > Can anyone help with a couple of problems: > > 1. I have two hard drives on my computer: DOS C: drive has Win 98 and the > second drive has a DOS partition, from where I installed FBSD and the rest > is FBSD. When I boot the FBSD I get this message: > > ad1: WRITE command timeout tag=0 serv=0 - resetting. > ata0: resetting devices .. ata0-master: DMA limited to UDMA33, non-ATA66 > compliant cable. > done > > It is repeated 4 times then the boot continues. I have not got my DOS C: > drive accessible to FBSD because I nearly lost it during a previous install. > Is this an important error? No. > 2. I tried writing the "Hello World" program in C. It compiled and I got > a.out whose permissions were set to executable. When I tried to execute I > got the "command not found" error but when I logged out and then in again > a.out would execute. Can I make new files execute without having to log out > and in again? Yes. This is almost certainly a FAQ. If "." (the current directory) is on your path, this should 'just work'. If not, you can explicitly give the path to a.out like this: ./a.out If you create a new executable somewhere on your path (eg, in ~/bin, if that's on your path) then your shell may not notice it immediately. If that's the case, you can use rehash to force the shell to rescan your PATH looking for executables. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287163 Fax +44 (0)117 9287112 RFC822 jan.grant@bris.ac.uk Usenet: The separation of content AND presentation - simultaneously. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message