09-10-2002
If this is SunOS, can you verify that "/usr/bin/uname -a" fails and "/sbin/uname -a" succeeds? The former is dynamically linked while the latter is statically linked. If the dynamically linked version is failing you have some kind of shared library problem. By running truss on the dynamically linked version, I notice the open on /dev/zero which looks like the only opportunity that I see to generate the particular error that you are reporting. Can you verify that /dev/zero is present? What shell are you using?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I write a sh script that zip and copy to tape all files that older then 2 hours.
1. The way I choose is - touch a file with "now - 2 hours", then use fine with '! -newer'
2. Do you have any other idea to do it ?
tnx. (1 Reply)
Discussion started by: yairon
1 Replies
2. Programming
I need to compile a file,but 'make' does
not work.please tell me how to use it or
need which tools? (3 Replies)
Discussion started by: dsun5
3 Replies
3. Shell Programming and Scripting
I wonder how I shall read the result below, especially 'what'
shown below.
The result was shown when I entered 'w'.
E.g what is TOP? What is gosh ( what does selmgr mean?)?
login@ idle JCPU PCPU what
6:15am 7:04 39 39 TOP
6:34am 6:45 45 45 TOP
6:41am ... (1 Reply)
Discussion started by: Aelgen
1 Replies
4. UNIX for Advanced & Expert Users
Can anybody help me?
I am developing a utility for automating message paging to a BT alphanumeric pager.
I am using a USR 56K Fax-modem connected to /dev/cuab on a Sun Ultra-10. I am using the UNIX 'tip' utility to connect to the modem and I have configured the modem as follows: Baud Rate:... (2 Replies)
Discussion started by: mybeat
2 Replies
5. UNIX for Dummies Questions & Answers
Hi, guys, I have a big problem.
I've got a sun solaris 4.1.4 workstation, and the /var/adm/message file will add one row every few seconds. It becomes a large file in a short time.
I wander if there are some mistakes configuring the workstation.
the /var/adm/message is as follow:
... (3 Replies)
Discussion started by: cloudsmell
3 Replies
6. UNIX for Dummies Questions & Answers
echo 'it's friday'
why appear the > (3 Replies)
Discussion started by: yls177
3 Replies
7. IP Networking
Hey all,
I've bought a few bits from Belkin who seem quite happy to support FreeBSD! Last time I bought a UPS from them and it's still going well :D
I saw this on their website that the 16bit PCMCIA card was supported under FreeBSD:
http://www.belkin.com/network/F5D5020.html
I went to my... (0 Replies)
Discussion started by: WIntellect
0 Replies
8. Email Antispam Techniques and Email Filtering
Here is a crude procmail recipe that I quickly created (NOT a procmail recipe expert, btw) that has been catching lots of spam (current second after the charset_spam recipe posted earlier):
:0B
* .*If.you.do.not.wish.to.receive...*
more_spam
:0B
* You.requested.to.receive.this.mailing... (0 Replies)
Discussion started by: Neo
0 Replies
9. UNIX for Advanced & Expert Users
Somehow someone created a file named '-ov' in the root directory.
Given the name, the how was probably the result of some cpio command they bozo'ed.
I've tried a number of different ways to get rid of it using * and ? wildcards, '\' escape patterns etc.. They all fail with " illegal option --... (3 Replies)
Discussion started by: GSalisbury
3 Replies
10. Shell Programming and Scripting
Hopefully this doesn't come off as too much of a "newbie" question or a flamebait. But I have recently begun working with a Sun Solaris box after having spent the past five years working with RedHat. From what i can tell, thing look fairly similar and the 'man' command is some help. But I've... (7 Replies)
Discussion started by: deckard
7 Replies
LEARN ABOUT NETBSD
rescue
RESCUE(8) BSD System Manager's Manual RESCUE(8)
NAME
rescue -- rescue utilities in /rescue
DESCRIPTION
The /rescue directory contains a collection of common utilities intended for use in recovering a badly damaged system. With the transition
to a dynamically-linked root beginning with NetBSD 2.0, there is a real possibility that the standard tools in /bin and /sbin may become non-
functional due to a failed upgrade or a disk error. The tools in /rescue are statically linked and should therefore be more resistant to
damage. However, being statically linked, the tools in /rescue are also less functional than the standard utilities. In particular, they do
not have full use of the locale, pam(3), and nsswitch libraries.
If your system fails to boot, and it shows an error message similar to:
init: not found
try booting the system with the boot flag ``-a'' and supplying /rescue/init, which is the rescue init(8), as the init path.
If your system fails to boot, and it shows a prompt similar to:
Enter full pathname of shell or RETURN for /bin/sh:
the first thing to try running is the standard shell, /bin/sh. If that fails, try running /rescue/sh, which is the rescue shell. To repair
the system, the root partition must first be remounted read-write. This can be done with the following mount(8) command:
/rescue/mount -uw /
The next step is to double-check the contents of /bin, /lib, /libexec, and /sbin, possibly mounting a NetBSD installation CD-ROM and copying
files from there. Once it is possible to successfully run /bin/sh, /bin/ls, and other standard utilities, try rebooting back into the stan-
dard system.
The /rescue tools are compiled using crunchgen(1), which makes them considerably more compact than the standard utilities.
FILES
/rescue Root of the rescue hierarchy.
SEE ALSO
crunchgen(1)
HISTORY
The rescue utilities first appeared in NetBSD 2.0.
AUTHORS
The rescue system was written by Luke Mewburn <lukem@NetBSD.org>. This manual page was written by Simon L. Nielsen <simon@FreeBSD.org>,
based on text by Tim Kientzle <kientzle@FreeBSD.org>.
BUGS
Most of the rescue tools work even in a fairly crippled system. The most egregious exception is the rescue version of vi(1), which currently
requires that /usr be mounted so that it can access the termcap(5) files. Hopefully, a failsafe termcap(3) entry will eventually be added
into the curses(3) library, so that /rescue/vi can be used even in a system where /usr cannot immediately be mounted. In the meantime, the
rescue version of the ed(1) editor can be used from /rescue/ed if you need to edit files, but cannot mount /usr.
BSD
January 20, 2009 BSD