Sponsored Content
Full Discussion: Booting in read-only
Top Forums UNIX for Dummies Questions & Answers Booting in read-only Post 2090 by 98_1LE on Wednesday 18th of April 2001 01:40:55 PM
Old 04-18-2001
To boot from the CD, simply put the CD in the drive, as toor type halt to bring you down to the OK prompt (or press "stop" & "a" at the same time). From the OK prompt, type;
boot cdrom
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Booting

Hi all, I've managed to get Mandrake 9 installed by disconnecting my 2 windows' drives. When I reconnect them Mandrake wants to take over. I figure it's time for the BootManager, or should I use a Linux specific one like Lilo? Or have I already stuffed up by not running Lilo at time of... (2 Replies)
Discussion started by: onestepto
2 Replies

2. Linux

Problems booting RH 8

I installed RH8 on Thinkpad R51. The install went smooth, but when I tried to boot, it hanged at: PCI_IDE: unknown IDE controller on Pci bus 00 device f9, VID=8086, ID=24ca PCI: Device 00:1f.1 not available because of resource collisions. PCI_IDE: (ide_setup_pci_device:) could not enable... (0 Replies)
Discussion started by: etc
0 Replies

3. Solaris

Solaris m/c not booting

My Solaris machine is not booting.It just stops at the point Boot device: /pci@1e,600000/ide@d/disk@0,0:a File and args: Whether i try boot or boot -s it is stopping at this point.. I tried boot cdom -s.It went into single user mode but I am not able to run a fsck in this mode. Right... (1 Reply)
Discussion started by: lydiaEd
1 Replies

4. Solaris

booting problem

any one can help me. my system running on solaris 2.7. recently there is sudden power failure while system running. after that unable to boot the system. it is giving comment that "can not open /etc/path_to_inst" and then returning back to "OK" after comment of termination. The processor is... (10 Replies)
Discussion started by: prabir
10 Replies

5. Solaris

booting from CD

Hello.. I am Still Learing Solaris .. when i try to Install Solaris 8 from its CD...i pressed STOP + A and i get a OK prompt screen. I then typed, "boot cdrom" and i am getting this error message. " FATAL: system is not bootable, boot command is disabled." How do we enable the boot... (5 Replies)
Discussion started by: vr76413
5 Replies

6. UNIX for Dummies Questions & Answers

problem booting

Dear List, While I was adding second hard disk to my system, I changed the /etc/fstab file by adding the following line: /mnt/sdb1 /dev/sdb1 ext3 default 2 1 Now system does not boot and gives the following error: Checking filesystems /: Clean, 309260/18495840 files, 1064776/18486790... (2 Replies)
Discussion started by: siavoush
2 Replies

7. Solaris

Error while booting the os

ater successfully completeing my solaris 10 installation i am not able boot the machine properly . my machine is continously rebooting after switching on the machine. what the problem ? is it the boot process problem or some other if any body got the solution mail it my email id (11 Replies)
Discussion started by: ravinder singh
11 Replies

8. UNIX and Linux Applications

Problems with booting

Hi, I've just installed Centos 5.3 x86_64 into a CPU. I've done a yum update to update the version to Centos 5.4. I then installed mysql, php, apache and phpmyadmin into the system. After the installation of phpmyadmin the screen suddenly goes blank, but the monitor is still on, and the cpu... (0 Replies)
Discussion started by: anaigini45
0 Replies

9. Solaris

Dual Booting - Solaris image CD doesn't read in BIOS

I am trying to install solaris 10-x86 as second OS on top of Windows XP. I have downloaded iso image from Oracle website and burned into bootable cd. when I loaded into CD-drive and made changes in BIOS to boot from CD. Its not reading from CD drive. After restarting the system with CD(solaris... (8 Replies)
Discussion started by: SunSolars_admin
8 Replies

10. Solaris

Errors while booting

sol10 sendmail : unable to qualify domain name (local host) ---- using short name sol10 sendmail : My unqualified host name (local host) keystore version failure (3 Replies)
Discussion started by: nash
3 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:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy