Sponsored Content
Operating Systems SCO Is there a way to give the name of another kernel from 'boot:' prompt. Post 85983 by Perderabo on Sunday 9th of October 2005 08:38:26 PM
Old 10-09-2005
 

10 More Discussions You Might Find Interesting

1. Red Hat

linux will not boot, boot to grub prompt

my redhat 9 will not boot. We had a power failure and when the power came back, my redhat linux will not boot. The machine come up to grub prompt. I tried the following from grub prompt root (hd0, then press tab key partition num:0 filesystem type unknown, partition type 0x83... (7 Replies)
Discussion started by: hassan2
7 Replies

2. Solaris

no boot prompt display

just put blank harddisk in my ultra10. i see no display to show me the boot> prompt. i don't know what happened....?? Got a third party graphic card. Display was ok. Monitor seems to be ok. i used different one with same result. (1 Reply)
Discussion started by: S26+
1 Replies

3. Solaris

Can't boot from cdrom at ok prompt

I want to install Solaris 9 on SUN ULTRA 10. The cdrom is attached to an ide controller. The server is currently running Solaris 2.6 I insert Solaris cd 1 of 2 and at the ok prompt I type boot cdrom i get the error below Boot device: /pci@1f,0/pci@1,1/ide@3/cdrom@2,0:f file and args:... (11 Replies)
Discussion started by: Msororaji
11 Replies

4. Shell Programming and Scripting

Can give the input to prompt using shell script

Hi, I want to send input to promt from shell script, this thing is possible. I give the one command `/usr/share/ssl/misc/CA -newreq` it needs some user input like password etc., but i need this input also from shell script but it does not works. `/usr/share/ssl/misc/CA -newreq` <<EOF... (2 Replies)
Discussion started by: Vaibhav Agarwal
2 Replies

5. Solaris

Cannot boot from CDROM nor get to OK prompt SunV210

Server need to have the OS reinstalled (5.10 SPARC) and I cannot get it to the OK prompt. I also do not have the ALOM password and I've tried several different methods to zero out the NVRAM but to no avail. There is no ALOM battery that I can pull. I'm connecting via Cutecom (like minicom) and... (18 Replies)
Discussion started by: LittleLebowski
18 Replies

6. Linux

Dual boot not getting os selection prompt

Hi I have vista on c drive. and installed oracle enterprise linux on d: drive formated(EXT3) ... installation went fine. but when i start my laptop it directly boots vista . i do not get os selection menu. Please help Ankur:D (2 Replies)
Discussion started by: ankurk
2 Replies

7. Solaris

Open Boot PROM - OK Prompt +dd +mount

Greetings friends, I would like to 'clone' the system/root hard disk with dd. (Solaris 10 on SPARC). If I understood correctly, 'OK Prompt' can use dd command? Can it mount drives? (to avoid any possibility of cloning the wrong drive, I'd like to output dd to file) thanks. (3 Replies)
Discussion started by: orange47
3 Replies

8. Ubuntu

Kernel boot options removed by fault, no boot options

Hello Everyone, First of all, I highly appreciate all Linux forum members and whole Linux community. http://forums.linuxmint.com/images/smilies/icon_wink.gif. I wish you the best for all of you ! I will try to be short and concise: I am using Linux Mint 10 for 2 months on 2 ws, and all went... (3 Replies)
Discussion started by: cdt
3 Replies

9. Solaris

All Hardware information in Ok Boot Prompt

Can anyone tell me the command to check all the hardware information in Ok boot Prompt. Like the hard disk space memory size ..... (3 Replies)
Discussion started by: newbi8321
3 Replies

10. Linux

Unload kernel module at boot time (Debian Wheezy 7.2, 3.2.0-4-686-pae kernel)

Hi everyone, I am trying to prevent the ehci_hcd kernel module to load at boot time. Here's what I've tried so far: 1) Add the following line to /etc/modprobe.d/blacklist.conf (as suggested here): 2) Blacklisted the module by adding the following string to 3) Tried to blacklist the module... (0 Replies)
Discussion started by: gacanepa
0 Replies
RDEV(8)                                                      Linux Programmer's Manual                                                     RDEV(8)

NAME
rdev - query/set image root device, RAM disk size, or video mode SYNOPSIS
rdev [-Rrvh] [-o offset] [image [value [offset]]] rdev [-o offset] [image [root_device [offset]]] ramsize [-o offset] [image [size [offset]]] vidmode [-o offset] [image [mode [offset]]] rootflags [-o offset] [image [flags [offset]]] DESCRIPTION
With no arguments, rdev outputs an /etc/mtab line for the current root file system. With no arguments, ramsize, vidmode, and rootflags print usage information. In a bootable image for the Linux kernel on i386, there are several pairs of bytes which specify the root device, the video mode, and the size of the RAM disk. These pairs of bytes, by default, begin at offset 504 (decimal) in the kernel image: 498 Root flags (500 and 502 Reserved) 504 RAM Disk Size 506 VGA Mode 508 Root Device (510 Boot Signature) rdev will change these values. Typical values for the image parameter, which is a bootable Linux kernel image, might be: /vmlinux /vmunix /boot/bzImage-2.4.0 /dev/fd0 /dev/fd1 When using the rdev command, the root_device parameter might be something like: /dev/hda1 /dev/hdf13 /dev/sda2 /dev/sdc4 /dev/ida/c0d0p1 One may also specify the device by a comma-separated pair of decimal integers major,minor. For the ramsize command, the size parameter specifies the size of the RAM disk in kilobytes. 2.0.x kernels and newer dynamically allocate the ramdisk and do not need this setting. For the rootflags command, the flags parameter contains extra information used when mounting root. Currently the only effect of these flags is to force the kernel to mount the root filesystem in readonly mode if flags is non-zero. For the vidmode command, the mode parameter specifies the video mode: -3 = Prompt -2 = Extended VGA -1 = Normal VGA 0 = as if "0" was pressed at the prompt 1 = as if "1" was pressed at the prompt 2 = as if "2" was pressed at the prompt n = as if "n" was pressed at the prompt If the value is not specified, the image will be examined to determine the current settings. OPTIONS
-r Causes rdev to act like ramsize (Not relevant for 2.0.x and newer kernels). -R Causes rdev to act like rootflags. -v Causes rdev to act like vidmode. -h Provides help. BUGS
The rdev utility, when used other than to find a name for the current root device, is an ancient hack that works by patching a kernel image at a magic offset with magic numbers. It does not work on architectures other than i386. Its use is strongly discouraged. Use a boot loader like SysLinux or LILO instead. HISTORY
At offset 502 there used to be the device number of the swap device (in Linux 0.12), and "rdev -s" or "swapdev" would set this. However, since Linux 0.95 this constant is not used any longer, and the swap device is specified using the swapon(2) system call. At offset 504 there used to be the size of the ramdisk in kilobytes. One would specify a size, and this much was grabbed off the top of memory. In Linux 1.1.39 it became also possible to set this value on the kernel command line. In Linux 1.3.48 the ramdisk setup was changed. Ramdisk memory is now taken from the buffer cache, so that the ramdisk can grow dynamically. The interpretation of the ramdisk word was changed to a word of which the high order bit is a prompt flag (1: prompt for ramdisk: "VFS: Insert ramdisk floppy and press ENTER" - this is needed with a two-floppy boot), the next bit a load flag (1: load ramdisk), and the low order 11 bits give the starting block number of the root filesystem image (so that one can have a single floppy boot). See also linux/Documentation/ramdisk.txt. AUTHORS
Originally by Werner Almesberger (almesber@nessie.cs.id.ethz.ch) Modified by Peter MacDonald (pmacdona@sanjuan.UVic.CA) rootflags support added by Stephen Tweedie (sct@dcs.ed.ac.uk) AVAILABILITY
The rdev command is part of the util-linux-ng package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/. Linux 0.99 20 November 1993 RDEV(8)
All times are GMT -4. The time now is 11:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy