07-20-2006
What OS? For such questions, always post the output of the 'uname -a' command. You can mask the hostname with 'xxxxx' if you want.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
On my PC I have two hard disks, the first with Windows 98 SE and the second with Linux Mandrake 8.0 (Traktopel). When I have installed Linux, it has modified the boot record of the 1st HD and it has added a graphic menu (LILO) for selecting the OS to use. By default, if I don't press a key, Linux... (2 Replies)
Discussion started by: robotronic
2 Replies
2. UNIX for Advanced & Expert Users
Hey !
I am running EWS-UX/V (Rel 4.2) on NEC EWS/4800/330 station and I am having problems rebooting my station : I am getting the following message on display : BOOT : PANIC : File size out of range.
According to user guide, this error is occuring when a file exceeding the limit and/or... (2 Replies)
Discussion started by: fredo
2 Replies
3. UNIX for Dummies Questions & Answers
I have a diskless work station.
i want to boot from a remote linux machine.
what changes i will have to do in configuration.
Plz tell me
thanks (1 Reply)
Discussion started by: hemant29
1 Replies
4. SCO
I get a message saying
Not enough space to dump xxxxx pages
Press any key to reboot
Safe to power off
After rebooting it never gets to the "Press CTRL D to continue or enter password for single user" message before it goes back to "Not enough space..." message above. Vicious cycle.
... (0 Replies)
Discussion started by: deloev
0 Replies
5. UNIX for Dummies Questions & Answers
being nosey on sons laptop and set a password and now need to undo this but its in the boot system :eek::eek::eek: (4 Replies)
Discussion started by: hempel
4 Replies
6. Solaris
We have a system that won't boot. It is Sun V245 that was patched yesterday with the latest Recommended 10 patch cluster. I will post what we get during the boot at the end of the email message. We have tried rebuilding the bootblk, booting from the cdrom, and running an fsck, booting into failsafe... (2 Replies)
Discussion started by: brownwrap
2 Replies
7. Solaris
Hi,
I am running into a some problems creating a dual boot system of 2 solaris instances using ZFS file system and I was wondering if someone can help me out.
First some back ground. I have been asked to change the file system of our server from UFS to ZFS. Currently we are using Solaris... (3 Replies)
Discussion started by: estammis
3 Replies
8. HP-UX
Hello,
I have a very old hp rp2450 running 11i2 that I had to power off. When turning it back on it hangs with the following message. Would booting into SUM get me any further? I've never used SUM, so I'm asking before I go down that rabbit hole.
Thanks for the help.
#
## extra content... (1 Reply)
Discussion started by: calabaria
1 Replies
9. Red Hat
Hi
im using centos 6.4
starting yesterday i have a strange issue that im unable to resolve. the system is booting to GRUB menu and the os is not starting. i tried to run a repair install and the message attached is what i get, what can cause this?
thanks, (1 Reply)
Discussion started by: guy3145
1 Replies
10. UNIX for Advanced & Expert Users
Hi,
I got stuck in a very messy situation yesterday after attempting to resolve a filesystem full issue. The user reported that their filesystem (/var/DWS) was 100% full even after moving few files of sizes 14G, 30G and 50G out of the directory. I checked the filesystem once more after this... (5 Replies)
Discussion started by: anaigini45
5 Replies
LEARN ABOUT FREEBSD
fastboot
REBOOT(8) BSD System Manager's Manual REBOOT(8)
NAME
reboot, halt, fastboot, fasthalt -- stopping and restarting the system
SYNOPSIS
halt [-lnpq] [-k kernel]
reboot [-dlnpq] [-k kernel]
fasthalt [-lnpq] [-k kernel]
fastboot [-dlnpq] [-k kernel]
DESCRIPTION
The halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM (and subsequently a SIGKILL) and,
respectively, halt or restart the system. The action is logged, including entering a shutdown record into the user accounting database.
The options are as follows:
-d The system is requested to create a crash dump. This option is supported only when rebooting, and it has no effect unless a dump
device has previously been specified with dumpon(8).
-k kernel
Boot the specified kernel on the next system boot. If the kernel boots successfully, the default kernel will be booted on successive
boots, this is a one-shot option. If the boot fails, the system will continue attempting to boot kernel until the boot process is
interrupted and a valid kernel booted. This may change in the future.
-l The halt or reboot is not logged to the system log. This option is intended for applications such as shutdown(8), that call reboot
or halt and log this themselves.
-n The file system cache is not flushed. This option should probably not be used.
-p The system will turn off the power if it can. If the power down action fails, the system will halt or reboot normally, depending on
whether halt or reboot was called.
-q The system is halted or restarted quickly and ungracefully, and only the flushing of the file system cache is performed (if the -n
option is not specified). This option should probably not be used.
The fasthalt and fastboot utilities are nothing more than aliases for the halt and reboot utilities.
Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending
doom and cleanly terminating specific programs.
SEE ALSO
getutxent(3), boot(8), dumpon(8), nextboot(8), savecore(8), shutdown(8), sync(8)
HISTORY
A reboot utility appeared in Version 6 AT&T UNIX.
BSD
October 11, 2010 BSD