03-05-2012
You may need to capture more lines, and in more detail too, to see what's actually going on. If logging can't be arranged, a digital photo will help.
init is having trouble running for some reason. did it ever print anything to the screen?
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Does anyone know if there is free software that can keep 2 filesystem on remote machines , synced.
This will be part of our Disaster Recovery to keep one machine off site , which will take over should the need arise..
Thanks (6 Replies)
Discussion started by: markdr011
6 Replies
2. Linux
Hi Linux Admin Guys
My onsite server is always 15 min slow and seems like NTPD (Network Time Protocol (NTP) daemon) not running properly. can anyone suggest me how to rectify this problem? we can't seem to get NTP to properly sync the clock.
Any help is resolving the issue will be helpful.... (12 Replies)
Discussion started by: csaha
12 Replies
3. UNIX for Dummies Questions & Answers
I am trying to Install RHEL AS 4 on x86 pc, through VNC and got the below error, Am not pretty sure as how to resolve this. Can some one guide me through the process, or what might be missing....
Have Installed RHEL, many a times but cudnt find this out...
Wud appreciate an early reply ......... (0 Replies)
Discussion started by: Crazy_murli
0 Replies
4. Linux
ok so I just installed fedora core 6 on my dell inspiron 700m and I go to boot into linux and I get this error. Has anyone seen this before?
I also had XP Pro and Vista installed on this pc prior to putting fedora core 6 on the machine. I'm trying to setup a triple boot system.
Please Help... (2 Replies)
Discussion started by: dave043
2 Replies
5. UNIX Desktop Questions & Answers
Hi ALL,
I am getting error..
kernal panic-not syncing:fatal exception
while booting.
Please help me..
Thanks
Jack (7 Replies)
Discussion started by: jack00423
7 Replies
6. Filesystems, Disks and Memory
Hi all,
I tried setting up RAID between 2 partitions and it was success.
If I write some things on /dev/md0, both partition got affected.
Then I stop the RAID, and I mounted one of my partition and I created a file in it.
Now I started the RAID (mdadm --assemble --scan)
What I expected... (1 Reply)
Discussion started by: lakshmananindia
1 Replies
7. Slackware
Hi,
first of all I'm 110% newbie, sorry for any mistake if I made it.
In my country there are no normal or active linux forums, so i found this forum.
Ok, that's for begining, but not for may real problem.
---------------------------------------------------
I am system administrator... (4 Replies)
Discussion started by: ElvijsL
4 Replies
8. Red Hat
HI All,
server stopped here, we are suspecting server crash, need install new OS.
Any suggestions on this. kindly help to us.
Thanks
Rajesh (0 Replies)
Discussion started by: Rajesh_Apple
0 Replies
9. Red Hat
dear experts linux
i am using RHEL 5.5 run on a physical server.
i am front of a big trouble, the Rhel can't run correctly , it show me this error message in black screen:
reading all physical volumes. this my take a while ..
found volume group "VolGroup00" using metadata type lvm2
9... (1 Reply)
Discussion started by: wassimpb
1 Replies
print(9E) Driver Entry Points print(9E)
NAME
print - display a driver message on system console
SYNOPSIS
#include <sys/types.h>
#include <sys/errno.h>
#include <sys/ddi.h>
#include <sys/sunddi.h>
int prefixprint(dev_t dev, char *str);
INTERFACE LEVEL
Architecture independent level 1 (DDI/DKI). This entry point is required for block devices.
PARAMETERS
dev Device number.
str Pointer to a character string describing the problem.
DESCRIPTION
The print() routine is called by the kernel when it has detected an exceptional condition (such as out of space) in the device. To display
the message on the console, the driver should use the cmn_err(9F) kernel function. The driver should print the message along with any
driver specific information.
RETURN VALUES
The print() routine should return 0 for success, or the appropriate error number. The print routine can fail if the driver implemented a
non-standard print() routine that attempted to perform error logging, but was unable to complete the logging for whatever reason.
SEE ALSO
cmn_err(9F)
Writing Device Drivers
SunOS 5.10 15 Sep 1992 print(9E)