06-27-2002
I have tried to boot the server in single mode (boot -s ) from ok
prompt.
This displayed the following error message:
Bad trap CPU=0 type=0x31 rp=0x10403648 addr=1024 mnu_fsr=0x0
End trackback
what does the above message means? what is the solution to this above problem
Can you help please.
Thank in Advance
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I am trying to install Perl 5.005 on solaris 2.5, following the perl
installation guide in INSTALL file that comes with Perl software
However, according to the installation procedure, it instruct me to to excute "make" command after running the Configure which I did but everytime I excute... (3 Replies)
Discussion started by: hassan2
3 Replies
2. UNIX for Dummies Questions & Answers
Well I have a new hosting account. I love these guys, because they have everything I need, and give me everything I need, but at the cost of I must configure it myself. I am trying to create a subdomain, and they use raw zone access for dns administration. I have no idea how to configure the zone... (1 Reply)
Discussion started by: btmitch
1 Replies
3. UNIX for Advanced & Expert Users
I wanted to know what email app most Sun solaris / unix gurus use ? I have become quite NON microsoft in the last few months in my studying solaris..
thanks
simon2000 (6 Replies)
Discussion started by: simon2000
6 Replies
4. UNIX for Dummies Questions & Answers
Please forgive me if this is the wrong place for this post. I didn't see a good place to post this topic in. :D
I would like to know what's the most popular and reliable Java IDE out there nowadays? A FREE one would be awesome! :D
Thanks for your suggestion!
Cheers! (10 Replies)
Discussion started by: laila63
10 Replies
5. UNIX for Advanced & Expert Users
I'm trying to tar 3000 files into a single tar file to be extracted on another server. Command I'm using:
find . -name '*cost*' -print| xargs tar -cvf mylist.tar (Note tar is contained on filesystem not tape drive which is what I want)
Above command works fine and displays all 3000+ file... (3 Replies)
Discussion started by: budrito
3 Replies
6. Shell Programming and Scripting
perl guru's,
what i think is, not simply writing a script...i like to write a script which must take less time to run and less memory use..i like to fine tune my program...
for ex, my program has a subroutine(1 file open &file close and 1print )
2if loops(1 file open &file close and... (2 Replies)
Discussion started by: sekar sundaram
2 Replies
7. AIX
Hi alls
I don't see any solution and I need to have feedback from other people...
On a test machine (AIX 5.1) I've installed OpenSSH software on it (with openssl, prng, etc...) like is described on IBM AIX Docs. To control the installation I've rebooted the machine and all was ok (CDE was... (15 Replies)
Discussion started by: nymus7
15 Replies
8. Shell Programming and Scripting
Hi ,
I wanted to find delata between two huge ( 8 GB ) files . Say file_TDY and file_YDY : These files are sorted based on a key .
I am using a command :
1)bdiff file_TDY file_YDY > diff_file
2) grep ' ^< ' diff_file > TDY_delta
I wanted only the changed records and newly added... (2 Replies)
Discussion started by: ajaybalki
2 Replies
9. What is on Your Mind?
A long time ago, my computer crashed, at that time, I was using Windows98, but
because I was a noob at computers, my friend recommended me apro to fix it for me.
He came, saw the computer, and asked if I had a backup/installation disk
for Windows 98. I said no.
He thought about it for a... (1 Reply)
Discussion started by: vistastar
1 Replies
10. Shell Programming and Scripting
hello,
i'm recompiling some c++ code for OSX and there are some bugs as the configure is not picking up some libs like atlas, pastix, etc, it should be finding either in standard path or with pkgconfig but it's not so i'm rewriting the Makefile. C++ territory is a bit of a stretch with all of... (0 Replies)
Discussion started by: f77hack
0 Replies
LEARN ABOUT FREEBSD
rbootd
RBOOTD(8) BSD System Manager's Manual RBOOTD(8)
NAME
rbootd -- HP remote boot server
SYNOPSIS
rbootd [-ad] [-i interface] [config_file]
DESCRIPTION
The rbootd utility services boot requests from Hewlett-Packard workstations over a local area network. All boot files must reside in the
boot file directory; further, if a client supplies path information in its boot request, it will be silently stripped away before processing.
By default, rbootd only responds to requests from machines listed in its configuration file.
The options are as follows:
-a Respond to boot requests from any machine. The configuration file is ignored if this option is specified.
-d Run rbootd in debug mode. Packets sent and received are displayed to the terminal.
-i interface
Service boot requests on specified interface. If unspecified, rbootd searches the system interface list for the lowest numbered,
configured ``up'' interface (excluding loopback). Ties are broken by choosing the earliest match.
Specifying config_file on the command line causes rbootd to use a different configuration file from the default.
The configuration file is a text file where each line describes a particular machine. A line must start with a machine's Ethernet address
followed by an optional list of boot file names. An Ethernet address is specified in hexadecimal with each of its six octets separated by a
colon. The boot file names come from the boot file directory. The ethernet address and boot file(s) must be separated by white-space and/or
comma characters. A pound sign causes the remainder of a line to be ignored.
Here is a sample configuration file:
#
# ethernet addr boot file(s) comments
#
08:00:09:0:66:ad SYSHPBSD # snake (4.3BSD)
08:00:09:0:59:5b # vandy (anything)
8::9:1:C6:75 SYSHPBSD,SYSHPUX # jaguar (either)
The rbootd utility logs status and error messages via syslog(3). A startup message is always logged, and in the case of fatal errors (or
deadly signals) a message is logged announcing the server's termination. In general, a non-fatal error is handled by ignoring the event that
caused it (e.g. an invalid Ethernet address in the config file causes that line to be invalidated).
The following signals have the specified effect when sent to the server process using the kill(1) command:
SIGHUP Drop all active connections and reconfigure.
SIGUSR1 Turn on debugging, do nothing if already on.
SIGUSR2 Turn off debugging, do nothing if already off.
FILES
/dev/bpf# packet-filter device
/etc/rbootd.conf configuration file
/tmp/rbootd.dbg debug output
/usr/mdec/rbootd directory containing boot files
/var/run/rbootd.pid process id
SEE ALSO
kill(1), socket(2), signal(3), syslog(3)
BUGS
If multiple servers are started on the same interface, each will receive and respond to the same boot packets.
BSD
December 11, 1993 BSD