problems with apropos Post: 302551647

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

'make' problems (compliation problems?)

I'm trying to compile and install both most recent version of 'make' and the most recent version of 'openssh' on my Sparc20. I've run into the following problems... and I don't know what they mean. Can someone please help me resolve these issues? I'm using the 'make' version that was...

2. UNIX for Dummies Questions & Answers

apropos

Please give me an alternate command for apropos on HP. Thanks in advance shilpa

3. Solaris

apropos not working

How come my 'apropos' cmd doesn't work in Solaris but works in Linux? How can I get it to work? Are the files in the 'companion' cd? Thanks.

4. UNIX for Advanced & Expert Users

Problems with Last

Hi, I,ve a Unixware 7.1.3 working correctly for two years ago, since a several weeks I've a problem with the command last . The information that this command return is : For example : 1.- The user root , time login : 12:15 h, time logoff 12:15 h (the real time is 14:00). Connected time is...

5. UNIX for Dummies Questions & Answers

Problems with using less

Hello, I am having problems with using less on Linux version 2.6.18-92.1.17.el5 (brewbuilder@hs20-bc1-7.build.redhat.com) (gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)). I am using csh but have the same problems on bash. If I pipe something to less it works perfectly i.e. cat file | less...

6. SuSE

Problems!!

good friends I am new to linux and I have the following TELNET service problem entering data devo telnet to a Windows server 2003 server and passes will not let me since the move to this server by telnet tells me the characters and thus invalidates me income, I have a service application...

7. Shell Programming and Scripting

while and do problems

Any ideas how to clear this error as it seems I dont understand if,do,while and els commands #!/bin/ksh set -x print "This script creates test messages" print "Please enter test case name" read testcasename echo $testcasename skipfield=Y while print "Do you want to skip this field...

8. Shell Programming and Scripting

If/then problems

#! /bin/bash # ask what the user would like to do CMD=$CMD MBA=$MB RS=$RS CT=$CT echo echo -n "What would you like to do?? REMEMBER WHEN PROGRAMMING ICP's TO SELECT CORRECT COMMAND ACCORDING TO NECCESSARY TYPE CODE! Please enter a command ct = program ctek ...

LEARN ABOUT NETBSD

compat_netbsd32

COMPAT_NETBSD32(8)					    BSD System Manager's Manual 					COMPAT_NETBSD32(8)

NAME

     compat_netbsd32 -- setup procedure for 32-bit compatibility on 64-bit platforms

DESCRIPTION

     The compat_netbsd32 module allows NetBSD/sparc64 to run NetBSD/sparc executables, and NetBSD/amd64 to run NetBSD/i386 executables.

     To use compat_netbsd32, one must either have COMPAT_NETBSD32 and EXEC_ELF32 in the kernel, or load the compat_netbsd32 and exec_netbsd32 ker-
     nel modules.

     Static executables typically need no additional setup.  Dynamic binaries require the dynamic linker plus shared libraries.  Most of these
     files will need to be placed under /emul/netbsd32.

     The easiest method of installing support for these is via the emulators/netbsd32_compat14, emulators/netbsd32_compat15, and
     emulators/netbsd32_compat16 packages, provided in the NetBSD packages collection.	These install 32-bit a.out and ELF compatibility
     libraries, respectively.  The details of what is actually necessary for correct operation are given below.  This obviously is handled by the
     emulator packages.

     For a.out compatibility, /usr/libexec/ld.so from a 32-bit distribution is required to exist as /emul/netbsd32/usr/libexec/ld.so.  For 32-bit
     ELF compatibility, /usr/libexec/ld.elf_so needs to be in /emul/netbsd32/usr/libexec/ld.elf_so.

     The shared libraries for a.out binaries do not live under the /emul/netbsd32 directory, but under the /emul/aout directory, where the a.out
     dynamic linker will find them.

BUGS

     A list of things which fail to work in compatibility mode should be here.

     IPC is not well supported.

     sysctl(3) is not well supported.

BSD
								  March 11, 2006							       BSD