Boot 5.0.7 in RAM and change keyboard


 
Thread Tools Search this Thread
Operating Systems SCO Boot 5.0.7 in RAM and change keyboard
# 1  
Old 08-02-2010
Boot 5.0.7 in RAM and change keyboard

hi

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?
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

keyboard and mouse dont work after sometime from boot in linux.

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)
Discussion started by: sanjay.login
1 Replies

2. Solaris

Solaris don't boot without mouse and keyboard

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)
Discussion started by: Timmerman
4 Replies

3. Solaris

Unable to change keyboard layout

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)
Discussion started by: solaris_user
14 Replies

4. Solaris

Unable to change keyboard layout

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)
Discussion started by: microbot
7 Replies

5. Solaris

HELP! Keyboard connected but Ultra60 doesn't boot :-((

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)
Discussion started by: montezumola
3 Replies

6. UNIX for Dummies Questions & Answers

New Sparc box wont boot. Keyboard?

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)
Discussion started by: Curt
5 Replies
Login or Register to Ask a Question
ABOOTIMG(1)						      General Commands Manual						       ABOOTIMG(1)

NAME
abootimg - manipulate Android Boot Images. DESCRIPTION
Tool to read/write/update android boot images SYNOPSIS
abootimg -i <bootimg> abootimg -x <bootimg> [<bootimg.cfg> [<kernel> [<ramdisk> [<secondstage>]]]] abootimg -u <bootimg> [-c "param=value"] [-f <bootimg.cfg>] [-k <kernel>] [-r <ramdisk>] [-s <secondstage>] abootimg --create <bootimg> [-c "param=value"] [-f <bootimg.cfg>] -k <kernel> -r <ramdisk> [-s <secondstage>] OPTIONS
-i print boot imgage informations -x Extract a boot image -u Update a boot image --create Create a boot image Options for extracting boot images bootimg Existing bootimage to use bootimg.cfg Name for the bootimg.cfg file, defaults to bootimg.cfg kernel Name for the kernel image, defaults to zImage ramdisk Name for the ramdisk image, defaults to initrd.img secondstage Name for the second-stage image, defaults to stage2.img Options for updating and creating boot images bootimg Existing bootimage to use -c param=value Existing bootimage to use -f <bootimg.cfg> Update bootimg.cfg with the named file -k <kernel> Update kernel with the named file -r <ramdisk> Update ramdisk with the named file -s <secondstage> Update secondstage image with the named file ABOOTIMG(1)