Sponsored Content
Top Forums UNIX for Advanced & Expert Users Boot loop errors caused by RC.CONF Post 33854 by norsk hedensk on Tuesday 21st of January 2003 09:14:02 PM
Old 01-21-2003
boot into single user mode.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

how do i set up dual boot again, possible virus caused problems...

ok well last night "something" caused by computer to "flip out"...i noticed that it seemed to be in dos but there was allot of info displaying on the screen real fast and after turning it off i was told there was no hard disk detected... so after talking to tech support i got windows up and... (4 Replies)
Discussion started by: justchillin
4 Replies

2. UNIX for Dummies Questions & Answers

Custom kernel compiling, won't boot, and errors.

First of all, I'd like to preface this post by relaying that I have considerable experience with FreeBSD but I'm a Linux newb. I've been attempting to compile linux-2.6.29.3 from source and I'm having some problems and have a few newb questions... a) First of all, my kernel won't boot, it fails... (0 Replies)
Discussion started by: urbanriot
0 Replies

3. Solaris

SCSI boot errors

Help needed please! I see the following scsi errors during boot up. The server eventually boots up successfully. Please let me now how to fix these errors: Executing last command: boot Boot device: disk File and args: SunOS Release 5.8 Version Generic_117350-62 64-bit Copyright 1983-2003 Sun... (4 Replies)
Discussion started by: pingmeback
4 Replies

4. AIX

AIX 5.3 Boot Errors

IBM P Series #7026 Error Codes #E47E212E - init #1BA70F4E - SRC #BA431EB7 - SRC #C69F5C9B- SYSPROC #369DO49B - SYSPFS This happens on reboot the core dump fills up the root file system so I don't think it completes the dump. I can't read the core file with dbx. Thanks (6 Replies)
Discussion started by: tholmes
6 Replies

5. Solaris

Sun Sparc Ultra 4 won't boot - disk errors

Hi all. I am seeing in one of our less-used servers that it crashed and now won't restart. I get the message 'continue with normal startup or boot into maintenance mode'. I go into maintenance and run fsck on /usr0 (mentioned in error at restart) it then reboots but goes right back to... (3 Replies)
Discussion started by: jamie_collins
3 Replies

6. Shell Programming and Scripting

Loop through hosts file - cat /etc/resolv.conf

Hello... I am trying to loop through my hosts file that contains 100+ servers to check or update the nameservers on them... My while loop is breaking after the first server responds... #!/bin/bash while read line; do a=( $(echo $line | tr " " "\n") ) if }" != "" ] && }" != "#" ] &&... (1 Reply)
Discussion started by: CompSCI
1 Replies

7. UNIX for Dummies Questions & Answers

While Loop Errors

I have the following chunk of code... while when I try to execute this script, it outputs an error "test: ] missing" Is there a syntax error here? (9 Replies)
Discussion started by: itech4814
9 Replies

8. Red Hat

Grub.conf kernel field boot messages verbosity configuration

I am trying to understand what are the differences of boot messages verbosity levels for the kernel field in grub.conf From my research, there appear to be three levels: quiet verbose debug I have also found documents that specify removing quiet from the kernel field. If this is done, is... (1 Reply)
Discussion started by: thaebich
1 Replies
BOOT(8) 						    BSD System Manager's Manual 						   BOOT(8)

NAME
boot -- system bootstrapping procedures DESCRIPTION
This document provides information on using common features in the NetBSD boot loader. Additional information may be found in architecture- specific boot(8) manual pages. In the native NetBSD boot protocol, options are passed from the boot loader to the kernel via flag bits in the boothowto variable (see boothowto(9)). Interactive mode In interactive mode, the boot loader will present a prompt, allowing input of these commands: boot [device:] [filename] [-1234abcdmqsvxz] The default device will be set to the disk that the boot loader was loaded from. To boot from an alternate disk, the full name of the device should be given at the prompt. device is of the form xd [N[x]] where xd is the device from which to boot, N is the unit number, and x is the partition letter. The following list of supported devices may vary from installation to installation: hd Hard disks. fd Floppy drives. The default filename is netbsd; if the boot loader fails to successfully open that image, it then tries netbsd.gz (expected to be a kernel image compressed by gzip), followed by netbsd.old, netbsd.old.gz, onetbsd, and finally onetbsd.gz. Alternate system images can be loaded by just specifying the name of the image. Options are: -1 Sets the machine-dependent flag RB_MD1 in boothowto. -2 Sets the machine-dependent flag RB_MD2 in boothowto. -3 Sets the machine-dependent flag RB_MD3 in boothowto. -4 Sets the machine-dependent flag RB_MD4 in boothowto. -a Sets the RB_ASKNAME flag in boothowto. This causes the kernel to prompt for the root file system device, the system crash dump device, and the path to init(8). -b Sets the RB_HALT flag in boothowto. This causes subsequent reboot attempts to halt instead of rebooting. -c Sets the RB_USERCONF flag in boothowto. This causes the kernel to enter the userconf(4) device configuration manager as soon as possible during the boot. userconf(4) allows devices to be enabled or disabled, and allows device locators (such as hard- ware addresses or bus numbers) to be modified before the kernel attempts to attach the devices. -d Sets the RB_KDB flag in boothowto. Requests the kernel to enter debug mode, in which it waits for a connection from a kernel debugger; see ddb(4). -m Sets the RB_MINIROOT flag in boothowto. Informs the kernel that a mini-root file system is present in memory. -q Sets the AB_QUIET flag in boothowto. Boot the system in quiet mode. -s Sets the RB_SINGLE flag in boothowto. Boot the system in single-user mode. -v Sets the AB_VERBOSE flag in boothowto. Boot the system in verbose mode. -x Sets the AB_DEBUG flag in boothowto. Boot the system with debug messages enabled. -z Sets the AB_SILENT flag in boothowto. Boot the system in silent mode. consdev dev Immediately switch the console to the specified device dev and reprint the banner. dev must be one of pc, com0, com1, com2, com3, com0kbd, com1kbd, com2kbd, com3kbd, or auto. See Console Selection Policy in boot_console(8). dev [device] Set the default drive and partition for subsequent filesystem operations. Without an argument, print the current setting. device is of the form specified in boot. help Print an overview about commands and arguments. ls [path] Print a directory listing of path, containing inode number, filename, and file type. path can contain a device specification. quit Reboot the system. In an emergency, the bootstrap methods described in the NetBSD installation notes for the specific architecture can be used. FILES
/boot boot program code loaded by the primary bootstrap /netbsd system code /netbsd.gz gzip-compressed system code /usr/mdec/boot master copy of the boot program (copy to /boot) /usr/mdec/bootxx_fstype primary bootstrap for filesystem type fstype, copied to the start of the NetBSD partition by installboot(8). SEE ALSO
Architecture-specific boot(8) manual pages, ddb(4), userconf(4), halt(8), installboot(8), reboot(8), rescue(8), shutdown(8), boothowto(9) BUGS
The kernel file name must be specified before, not after, the boot options. Any filename specified after the boot options, e.g.: boot -d netbsd.test is ignored, and the default kernel is booted. BSD
September 4, 2009 BSD
All times are GMT -4. The time now is 01:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy