This is quite interesting, it would seem that the pkgadd for the vpath IBM drivers has an interesting side effect. It over writes the /etc/system file (note over write and not append) with;
All the stuff that was in there before is just trashed, recover the old file from tape and edit is the answer at the moment. This just goes to show that making changes to a live system and not going for a reboot, is just asking for problems!
Regards
Dave
Last edited by gull04; 03-25-2012 at 05:14 PM..
Reason: Can't spell old!
Hello.
System is a HP Visualize C3600 running X11 and after a power failure machine will not boot (see error messages below)
From what I've read, this may be caused by a corrupted etc/inittab file. Solution suggested on other websites is to boot in single user mode and edit file inittab... (2 Replies)
Hi all
I used a dual boot operating system and it works fine for me. Now , i install a Ati radeon 9250 Agp card on my system and this results in boot failure of fedora 6. The graphics card is working fine with windows XP , i.e i have no compatibility issues.The system also refuses to boot when i... (2 Replies)
I installed solaris virtually and tried to format the partitions .. I dont know what went wrong, It got rebooted and hangs in the screen "No partitions" and after pressing Enter button it goes to "INT18 boot failure" and hangs there once again . Could any one of you suggest why this has happened... (3 Replies)
I have installed Solaris 10 OS in Sun Virtual Box that uses x86 32 bit system. After an abnormal shutdown i'm getting the following message on the console when i try to boot.
SunOS Release 5.10 Version Generic_127128_11 32-bit
Copyright 1983-200 Sun Microsystems, Inc. All rights reserrved.
Use... (3 Replies)
hi
SCO Unix 5.0.6 doesn't boot due to this problem:
not a directory
boot not found
cannot open
stage 1 boot failure: error loading hd (40)/boot
Knows someone howto solve it? (16 Replies)
This is what is displayed on the screen as the system tries to boot and then hangs:
0>Test CPU(s)....Done
0>Interrupt Crosscall....|
SC Alert: DHCP negotiation failed, perhaps misconfigured or no DHCP server avail
able
Done
0>Init Memory....|
SC Alert: Host System has Reset
'Done
0>PLL... (2 Replies)
Hi,
i am running an old Opensolaris 5.11 snv_111b on an x86 server. After almost 4 years of successful service, last night out of the blue started to refuse all connections to it's services, ssh, http,etc. The only visible solution at that time was a restart. But now instead of booting the... (2 Replies)
When I login to the live console of my server and go to the console, I am getting the below message
Processor is booting from the first available device.
To discontinue, press any key within 10 seconds.
10 seconds expired.
Proceeding...
Trying Primary Boot Path... (11 Replies)
Discussion started by: chacko193
11 Replies
LEARN ABOUT REDHAT
halt
HALT(8) Linux System Administrator's Manual HALT(8)NAME
halt, reboot, poweroff - stop the system.
SYNOPSIS
/sbin/halt [-n] [-w] [-d] [-f] [-i] [-p] [-h]
/sbin/reboot [-n] [-w] [-d] [-f] [-i]
/sbin/poweroff [-n] [-w] [-d] [-f] [-i] [-h]
DESCRIPTION
Halt notes that the system is being brought down in the file /var/log/wtmp, and then either tells the kernel to halt, reboot or poweroff
the system.
If halt or reboot is called when the system is not in runlevel 0 or 6, in other words when it's running normally, shutdown will be invoked
instead (with the -h or -r flag). For more info see the shutdown(8) manpage.
The rest of this manpage describes the behaviour in runlevels 0 and 6, that is when the systems shutdown scripts are being run.
OPTIONS -n Don't sync before reboot or halt.
-w Don't actually reboot or halt but only write the wtmp record (in the /var/log/wtmp file).
-d Don't write the wtmp record. The -n flag implies -d.
-f Force halt or reboot, don't call shutdown(8).
-i Shut down all network interfaces just before halt or reboot.
-h Put all harddrives on the system in standby mode just before halt or poweroff.
-p When halting the system, do a poweroff. This is the default when halt is called as poweroff.
DIAGNOSTICS
If you're not the superuser, you will get the message `must be superuser'.
NOTES
Under older sysvinit releases , reboot and halt should never be called directly. From release 2.74 on halt and reboot invoke shutdown(8) if
the system is not in runlevel 0 or 6. This means that if halt or reboot cannot find out the current runlevel (for example, when
/var/run/utmp hasn't been initialized correctly) shutdown will be called, which might not be what you want. Use the -f flag if you want to
do a hard halt or reboot.
The -h flag puts all harddisks in standby mode just before halt or poweroff. Right now this is only implemented for IDE drives. A side
effect of putting the drive in standby mode is that the write cache on the disk is flushed. This is important for IDE drives, since the
kernel doesn't flush the write-cache itself before poweroff.
The halt program uses /proc/ide/hd* to find all IDE disk devices, which means that /proc needs to be mounted when halt or poweroff is
called or the -h switch will do nothing.
AUTHOR
Miquel van Smoorenburg, miquels@cistron.nl
SEE ALSO shutdown(8), init(8)
Nov 6, 2001 HALT(8)