I've boot OpenServer Release 5.0.7 from a setup CD and started "Execute a shell on ramdisk filesystem".
Howto change keyboard from american to swiss german?
when i started booting linux ,after sometime both the mouse and the keyboard are getting freeze and wont respond(also the system gets hanged and all the process running dont go forward) ,nothing seem to work.
Keeping in mind that it will work after sometime ,i waited for one hour also ,but... (1 Reply)
Hi guys,
I've installed Solaris 10 (SunOS 5.10) in a x86 box. I will put this box as a home server to store my files/backups/whatterver shared stuff replacing my old NetBSD machine. But, after installed and correctly configured, when I tried to boot this box without keybord and mouse (USB both),... (4 Replies)
Hi to everyone
Once again I tried to modify my keyboard , because I am crazy keyborad can not be changed using
kbd-s
eeprom
also I tried to modify /boot/solaris/bootenv.rc
but I tried opensolaris and my keyboard works perfectly
So my question is
Can I transfer settings from... (14 Replies)
After Solaris 10 installation I was unable to change keyboard using known commands
kbd -s and eeprom keyboard layoit.
Also modifinig /boot/solaris/bootenv.rc did not helped.
And is possible to replace Solaris keymap with ubuntu keymap because my keyboard
work perfectly under Ubuntu and... (7 Replies)
Hi all,
This is my first post here :) Hope some guru here will be able to help ...
I'm in a predicament - my Ultra 60 worked fine before it was put into storage a year ago ... now, I've set it up in my PC room and I get the following message on startup:
Can't open input device.
Keyboard... (3 Replies)
Do I HAVE to have a Sun Sparc type keyboard?
Ive got an Ultra Sparc workstation I got from EBAY that was supposted to be working. This box has a PS2 AND Sparc's odd looking keyboard port.
Does my system have a switch in the BIOS simmilar to the x86 "Halt on keyboard error?" ...Or maybe a... (5 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)