Path

[Ryan Schmidt]

On Sep 29, 2009, at 19:49, Peter Hindrichs wrote:

> On 2009-09-29, at 20:31 , Ryan Schmidt wrote:
>
>> Bash might look in one of several files for its initialization  
>> instructions. These files are  
>> called .profile, .bash_profile, .bashrc, .login, and .bash_login,  
>> and would be directly in your home directory. Which of those files  
>> do you have, and what is their contents?
>
> Not sure how to go about this.
>>

You could find out which of these files exist by running these two  
commands:

cd ~
ls -l .profile .bash_profile .bashrc .login .bash_login

For each file that it shows existing, you could open it into TextEdit  
using e.g.:

open -e .profile

and copy and paste the contents into your reply email.


>> What's in /usr/local? Find out with:
>>
>> find /usr/local
>
> This is what I have
>
>
> Freedom:~ peterhin$ find /usr/local
> /usr/local
> /usr/local/bin
> /usr/local/bin/foomatic-gswrapper
> /usr/local/bin/foomatic-rip
> /usr/local/bin/hpijs
> /usr/local/clamXav
> /usr/local/clamXav/bin
> /usr/local/clamXav/bin/clamav-config
> /usr/local/clamXav/bin/clamconf
> /usr/local/clamXav/bin/clamdscan
> /usr/local/clamXav/bin/clamdtop
> /usr/local/clamXav/bin/clamscan
> /usr/local/clamXav/bin/freshclam
> /usr/local/clamXav/bin/sigtool
> /usr/local/clamXav/etc
> /usr/local/clamXav/etc/clamd.conf
> /usr/local/clamXav/etc/freshclam.conf
> /usr/local/clamXav/include
> /usr/local/clamXav/include/clamav.h
> /usr/local/clamXav/lib
> /usr/local/clamXav/lib/libclamav.6.dylib
> /usr/local/clamXav/lib/libclamav.a
> /usr/local/clamXav/lib/libclamav.dylib
> /usr/local/clamXav/lib/libclamav.la
> /usr/local/clamXav/lib/libclamunrar.6.dylib
> /usr/local/clamXav/lib/libclamunrar.a
> /usr/local/clamXav/lib/libclamunrar.dylib
> /usr/local/clamXav/lib/libclamunrar.la
> /usr/local/clamXav/lib/libclamunrar_iface.6.so
> /usr/local/clamXav/lib/libclamunrar_iface.a
> /usr/local/clamXav/lib/libclamunrar_iface.la
> /usr/local/clamXav/lib/libclamunrar_iface.so
> /usr/local/clamXav/lib/pkgconfig
> /usr/local/clamXav/lib/pkgconfig/libclamav.pc
> /usr/local/clamXav/sbin
> /usr/local/clamXav/sbin/clamd
> /usr/local/clamXav/share
> /usr/local/clamXav/share/clamav
> /usr/local/clamXav/share/clamav/daily.cld
> /usr/local/clamXav/share/clamav/freshclam.log
> /usr/local/clamXav/share/clamav/main.cld
> /usr/local/clamXav/share/clamav/main.cvd
> /usr/local/clamXav/share/clamav/mirrors.dat
> /usr/local/clamXav/share/man
> /usr/local/clamXav/share/man/man1
> /usr/local/clamXav/share/man/man1/clamconf.1
> /usr/local/clamXav/share/man/man1/clamdscan.1
> /usr/local/clamXav/share/man/man1/clamdtop.1
> /usr/local/clamXav/share/man/man1/clamscan.1
> /usr/local/clamXav/share/man/man1/freshclam.1
> /usr/local/clamXav/share/man/man1/sigtool.1
> /usr/local/clamXav/share/man/man5
> /usr/local/clamXav/share/man/man5/clamd.conf.5
> /usr/local/clamXav/share/man/man5/freshclam.conf.5
> /usr/local/clamXav/share/man/man8
> /usr/local/clamXav/share/man/man8/clamav-milter.8
> /usr/local/clamXav/share/man/man8/clamd.8
> /usr/local/etc
> /usr/local/etc/foomatic
> /usr/local/etc/foomatic/direct
> /usr/local/etc/foomatic/filter.conf
> /usr/local/etc/foomatic/filter.conf.sample
> /usr/local/share
> /usr/local/share/doc
> /usr/local/share/doc/hplip-3.9.2
> /usr/local/share/doc/hplip-3.9.2/COPYING
> /usr/local/share/doc/hplip-3.9.2/copyright
> /usr/local/share/doc/hplip-3.9.2/README_LIBJPG
> /usr/local/share/man
> /usr/local/share/man/man1
> /usr/local/share/man/man1/foomatic-rip.1
> /usr/local/share/man/whatis

Ok, that's not so bad. You can keep /usr/local/bin in your path. Just  
be aware that you shouldn't install software in /usr/local that's  
available via MacPorts; use MacPorts to install it instead. In this  
case, we don't have portfiles for hplip/foomatic so it's ok.

We do have a portfile for clamav, but since your clamXav is not  
installed in prefix /usr/local but instead in prefix /usr/local/ 
clamXav it shouldn't interfere with MacPorts, and I understand clamXav  
is a graphical frontend for clamav so just installing clamav from  
MacPorts might not give you the same interface.


P.S: Use Reply All so your reply goes to the list too, not just to me.