10 More Discussions You Might Find Interesting
1. Red Hat
Hi All
On one of my sandbox machine, I want to replace RHEL 6.2 to RHEL 7.3.
I am using both developer editions.
rhel-server-7.3-x86_64-dvd.iso ... This is what I have downloaded from
Red Hat Enterprise Linux Download | Red Hat Developers
My understanding is this file would work as a... (1 Reply)
Discussion started by: videsh77
1 Replies
2. SuSE
Hi All,
I would need your assistance to make a bootable USB with SUSE LINUX Enterprise Server
I have already downloaded relevant OS (Trail Version) packages @
1) SLES-11-SP4-DVD-i586-GM-DVD1
2) SLES-11-SP4-DVD-i586-GM-DVD2
when I tried to open these packages with PowerISO one of the... (7 Replies)
Discussion started by: Leaner_963
7 Replies
3. Solaris
trying to do this for a DR situation. I've cloned an iSCSI LUN to another server. I've created an LDOM on it. set the LDOM to auto-boot=false and exported the LUN as a raw disk to the new LDOM. After starting the LDOM and telnetting to it. I can get to the OK prompt and see the disk but when I try... (2 Replies)
Discussion started by: os2mac
2 Replies
4. UNIX for Dummies Questions & Answers
hi,
i recently built a pxe file the problem is I don't know how to add it in the pxe server.
I was wondering if you guys know how to add my pxe file in the pxe server so that when I run the device we're using, I can go lan boot then at boot: I will just type a text and it will boot the built... (0 Replies)
Discussion started by: h0ujun
0 Replies
5. Fedora
I need to boot the ultimate boot cd from an usb stick. Do I just copy the iso image to the usb key?
How do I make the usb stick bootable? (4 Replies)
Discussion started by: locoroco
4 Replies
6. Filesystems, Disks and Memory
In our HP/Unix system, our master scsi drive was bootable and our mirrored drive was non-bootable. Are any of these alternatives possible:
1) Make the non-bootable scsi drive bootable? How?
2) Create a bootable scsi drive, then copy the mirrored data to the newly created scsi drive?
I seek... (1 Reply)
Discussion started by: bfisk
1 Replies
7. Solaris
The second disk that I'm trying to make bootable is to hold another version of Solaris (9).
I've created the partitions with format and labeled the disk - created the filesystems with newfs - created and mounted the directories.
...but I think I've missed something out like using fdisk to... (16 Replies)
Discussion started by: pondlife
16 Replies
8. Solaris
Hey all,
I'm a newbie to iso files and I just downloaded
the 2 iso files for *cough* ms2003 R2 *cough*
trial software. After I downloaded the iso files
I just dragged them to my burn software gui
and sure enough it burned to dvd 2 iso files.
When I attempted to boot the image using VMware... (0 Replies)
Discussion started by: bdsffl
0 Replies
9. UNIX for Dummies Questions & Answers
Hi ,
I am using a laptop with windows XP as the operating system. i want to use linux/unix without installing it on my machine.
I heard that i can do so using some Linux bootable CD .... which can be used to work on linux environment with out physically installing it on your system.
I... (2 Replies)
Discussion started by: newbie07
2 Replies
10. UNIX for Dummies Questions & Answers
Hello all,
I'm trying to recover from backup file to a new system with a new disk. I'm able to partition my new hard drive the same way as my old drive, but I'm unable to boot off of it. I have set the fdisk to toogle as a boot flag. But it does not seem to be working. Does anyone know how to... (4 Replies)
Discussion started by: larryase
4 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)