I made the fatal mistake of rename the usr directory.
I cannot run any commands due to the fact that ld.so.1 is in usr/lib/--and it doesn't exist
How can I recover my system? (1 Reply)
hello all
im trying to use in sun Solaris the information received from the top command
now i several machines that dont have install the top program so when im running the script im geting error
saying after im running this code :
set MemoryInfo = `top | grep Memory`
if (... (2 Replies)
Hello everybody:
Im facing this weird problem on my SUN V890 running SOL9, from time to time I keep getting this error from the prompt when i press enter for blank:
OM: not found
sometimes if I entered a coomand it will give me: OM(command name):not found, but repeating the same command it... (4 Replies)
Hi All,
when i ran a shell script ,its showing "^M: not found" errore
i used the the code
dos2unix sunshine.sh sunshine1.sh
and then again i ran the scriptand then its still showing the errore
please help me in the matter.
thanks... (3 Replies)
hi:
I had an existing script in production and I commented some lines and implemented the same. The scripts fails with a cc of 127 and I get the msg:
^M: not found
I checked the file format and it is a PC file format. Does this cause the script to fail with cc= 127.
Can somebody... (4 Replies)
Hey
I have a weird "problem" here It's more out of curiosity, my script is working fine, but giving me a "pidt.sh: 7: Rather: not found" error...
#!/bin/sh
log="log/`date +%F_pidt.log`"
echo "---n`date`n---n" >> $log
for i in `cat pidt.conf`
do
|| $( /etc/init.d/$i start &&... (3 Replies)
i have downloaded <libncurses5-dev_5.7+20101128-1_i386.deb> and <ndk++-0.0.1alpha4.tar.bz2> which contains the header files curses.h and gtk/gtk.h ..
i have also included them using ..
#include "/home/ball/Desktop/Sudoku/project/libncurses5-dev_5.7+20101128-1_i386/usr/include/curses.h"
... (2 Replies)
I had a spot of trouble coming up with a title, hopefully you'll understand once you read my problem... :)
I have the output of an ldapsearch that looks like this:
dn: cn=sam,ou=company,o=com
uidNumber: 7174
gidNumber: 49563
homeDirectory: /home/sam
loginshell: /bin/bash
uid: sam... (2 Replies)
Discussion started by: samgoober
2 Replies
LEARN ABOUT FREEBSD
whereis
WHEREIS(1) BSD General Commands Manual WHEREIS(1)NAME
whereis -- locate programs
SYNOPSIS
whereis [-abmqsux] [-BMS dir ... -f] program ...
DESCRIPTION
The whereis utility checks the standard binary, manual page, and source directories for the specified programs, printing out the paths of any
it finds. The supplied program names are first stripped of leading path name components, any single trailing extension added by gzip(1),
compress(1), or bzip2(1), and the leading 's.' or trailing ',v' from a source code control system.
The default path searched is the string returned by the sysctl(8) utility for the ``user.cs_path'' string, with /usr/libexec and the current
user's $PATH appended. Manual pages are searched by default along the $MANPATH. Program sources are located in a list of known standard
places, including all the subdirectories of /usr/src and /usr/ports.
The following options are available:
-B Specify directories to search for binaries. Requires the -f option.
-M Specify directories to search for manual pages. Requires the -f option.
-S Specify directories to search for program sources. Requires the -f option.
-a Report all matches instead of only the first of each requested type.
-b Search for binaries.
-f Delimits the list of directories after the -B, -M, or -S options, and indicates the beginning of the program list.
-m Search for manual pages.
-q (``quiet''). Suppress the output of the utility name in front of the normal output line. This can become handy for use in a back-
quote substitution of a shell command line, see EXAMPLES.
-s Search for source directories.
-u Search for ``unusual'' entries. A file is said to be unusual if it does not have at least one entry of each requested type. Only
the name of the unusual entry is printed.
-x Do not use ``expensive'' tools when searching for source directories. Normally, after unsuccessfully searching all the first-level
subdirectories of the source directory list, whereis will ask locate(1) to find the entry on its behalf. Since this can take much
longer, it can be turned off with -x.
EXAMPLES
The following finds all utilities under /usr/bin that do not have documentation:
whereis -m -u /usr/bin/*
Change to the source code directory of ls(1):
cd `whereis -sq ls`
SEE ALSO find(1), locate(1), man(1), which(1), sysctl(8)HISTORY
The whereis utility appeared in 3.0BSD. This version re-implements the historical functionality that was lost in 4.4BSD.
AUTHORS
This implementation of the whereis command was written by Jorg Wunsch.
BUGS
This re-implementation of the whereis utility is not bug-for-bug compatible with historical versions. It is believed to be compatible with
the version that was shipping with FreeBSD 2.2 through FreeBSD 4.5 though.
The whereis utility can report some unrelated source entries when the -a option is specified.
BSD August 22, 2002 BSD