Date: Sun, 18 Apr 1999 16:09:55 -0500 (EST) From: Alfred Perlstein <bright@rush.net> To: neill rr <robalama@yahoo.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Ports Problems Message-ID: <Pine.BSF.3.96.990418160016.11384T-100000@cygnus.rush.net> In-Reply-To: <19990418204221.17829.rocketmail@web119.yahoomail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 18 Apr 1999, neill rr wrote:
> Hello again,
>
> On 3.1-Release I have attempted to install a few ports and have had great success until this past
> weekend. After successfully installing Mutt, when I try to run it this is what I get:
>
> myname# mutt &
> [1] 6391
> myname#
> [1] + Suspended (tty output) mutt
> myname#
mutt is an interactive program, the problem is you put it in the background
with the trailing '&', it's now trying to write something to the console,
you should type:
fg %1
to bring it back.
>
> and of course nothing happens.
>
> Another port is wmcdplay-1.0b1. It also installed successfully but this is the error.
>
> myname# wmcdplay &
> [2] 6392
> myname# wmcdplay : Unable to open cdrom device '/dev/cdrom'.
>
> [2] Done wmcdplay
> myname#
>
> I went into the /dev dirictory and looked for associated files for this problem. I have almost
> everything there, and even after running throught "The Complete FreeBSD" I dont see anything that
> has "cdrom" (the whole string) for my Creative IDE drive.
you need to:
cd /dev ; ln -s <your cdrom device> cdrom
<your cdrom device> is most likely "wcd0c"
> x11amp is reacting wierd also. I just successfully installed it and this is what happens when I
> attempt to run it:
>
> myname# x11amp &
> x11amp: Command not found.
> [1] 13407
> [1] Exit 1 x11amp
> myname#
>
> and this happens even when I am in the /usr/local/bin/ directory.
>
> Most likely I am missing something simple, but any information is greatly appreciated. Thanks
please, If you can try to limit your line length to about 76 characters.
But otherwise the problem you are having with x11amp is that it's not
cached in your path.
Most unix shells look at $PATH to find executables, however they build that
cache only when they are first run. You can tell it to rebuild the cache
by running "rehash" in most shells.
Therefore if you just dump a program in /usr/local/bin and /usr/local/bin is
in your path (echo $PATH) you most likely will not actually be able to run
it unless you either:
a) specify the full path to it (/usr/local/bin/x11amp)
b) tell your shell to rebuild its PATH cache:
rehash
x11amp
it is an extremely dangerous thing to have the current directory in your PATH
the reason being that someone could dump a frequently misspelled trojan
horse into any directory and have you run the program when you make that
frequent typo. it can be used to hijack or cause damage to your account/
machine.
if you want to run a program in your current directory:
./program
-Alfred
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.990418160016.11384T-100000>