05-24-2015
Hi,
Are you certain that you have a version of Ultrix for the CPU type, from memory Ultrix was DEC native so probably PA RISC and Alpha processor types will be required.
The Qemu Hypervisor will only support the OPEN RISK Version of Ultrix which I think will need to be Version 4.5 with it's own libraries installed - it does not support shared libraries.
Also the version that you are using is from around 1991, there is a much later version from 1995 that you should be looking at.
Regards
Gull
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I got myself a dec 5100 running ultrix with unknow password, how do i recover or change the root password on it? (10 Replies)
Discussion started by: cybermike
10 Replies
2. UNIX for Dummies Questions & Answers
hi i got a virtual linux machine running on qemu
my problem is connecting it to the internet
im a bit confused weather i have to make a virtual network card in qemu
and than tun tap it?
can anyone thats done it before help me out? (1 Reply)
Discussion started by: russian460
1 Replies
3. Filesystems, Disks and Memory
hello all,
I have been trying to boot an image (.IMG) using qemu, for quite some time now and i can't seem to get it to work. I've been able to boot from the Windows XP CD, the Debian iso image, etc, so I know qemu is configured properly and is working. But when it come to booting an image that I... (34 Replies)
Discussion started by: neur0n
34 Replies
4. Programming
Hi, I got:
host machine: RedHat (RHEL6)
virtual machine: RedHat (RHEL6)
I run (on host machine):
qemu-system-x86_64 ...... -S -s
after that i run (on host machine):
gdb
target remote localhost:1234
set architecture i386:x86-64
and then i can use (on host machine) 'ctrl + c' to... (2 Replies)
Discussion started by: Chrisdot
2 Replies
5. AIX
Hi friends,
I am a UNIX lover. I have tried several unix flavors including linux, solaris(x86) and FreeBSD, all these are the unices which can be installed on x86 hardware. Now to use the IBM AIX, I searched and googled alot, finally I came across QEME, which emulates the PowerPC platorm to turn... (9 Replies)
Discussion started by: gabam
9 Replies
6. Programming
I created and Compiled a C program to run in QEMU for ARM.
When I run the program using the command
#qemu-arm -L /home/arm-2010.09/arm-none-linux-gnueabi/libc ./test
it gives me the following error:
If 'qemu-arm' is not a typo you can use command-not-found to lookup the package that contains... (0 Replies)
Discussion started by: rupeshkp728
0 Replies
7. Red Hat
I used the redhat RHEL6 boot with initrd but it failed, can sb help me
# /usr/libexec/qemu-kvm --enable-kvm -smp 8 -m 1024 -net nic,model=virtio -net tap,script=/etc/qemu-ifup -initrd /boot/initramfs-2.6.32-279.el6.x86_64.img -kernel /boot/vmlinuz-2.6.32-279.el6.x86_64 -append "root=/dev/ram... (4 Replies)
Discussion started by: yanglei_fage
4 Replies
8. UNIX for Dummies Questions & Answers
I am running the gxemul software under cygwin,
Just when installing the .iso image, I got the error shown in
the picture. Any ideas what's happening?
Thanks
Jack (1 Reply)
Discussion started by: lucky7456969
1 Replies
9. Virtualization and Cloud Computing
Heyas
So, i like doing custom a LiveImage of my OS.
Using Redhats kickstart/livecd-creator method.
Anyway, so i would like to test the liveimages...
AND also, i WOULD like to install FreeBSD, Solaris, or whatever, onto a Virtual Machine.
I used to use Oracles Virtualbox, but eversince... (3 Replies)
Discussion started by: sea
3 Replies
LEARN ABOUT XFREE86
libbash
LIBBASH(7) libbash Manual LIBBASH(7)
NAME
libbash -- A bash shared libraries package.
DESCRIPTION
libbash is a package that enables bash dynamic-like shared libraries. Actually its a tool for managing bash scripts whose functions you may
want to load and use in scripts of your own.
It contains a 'dynamic loader' for the shared libraries ( ldbash(1)), a configuration tool (ldbashconfig(8)), and some libraries.
Using ldbash(1) you are able to load loadable bash libraries, such as getopts(1) and hashstash(1). A bash shared library that can be loaded
using
ldbash(1) must answer 4 requirments:
1. It must be installed in $LIBBASH_PREFIX/lib/bash (default is /usr/lib/bash).
2. It must contain a line that begins with '#EXPORT='. That line will contain (after the '=') a list of functions that the library
exports. I.e. all the function that will be usable after loading that library will be listed in that line.
3. It must contain a line that begins with '#REQUIRE='. That line will contain (after the '=') a list of bash libraries that are
required for our library. I.e. every bash library that is in use in our bash library must be listed there.
4. The library must be listed (For more information, see ldbashconfig(8)).
Basic guidelines for writing library of your own:
1. Be aware, that your library will be actually sourced. So, basically, it should contain (i.e define) only functions.
2. Try to declare all variables intended for internal use as local.
3. Global variables and functions that are intended for internal use (i.e are not defined in '#EXPORT=') should begin with:
__<library_name>_
For example, internal function myfoosort of hashstash library should be named as
__hashstash_myfoosort
This helps to avoid conflicts in global name space when using libraries that come from different vendors.
4. See html manual for full version of this guide.
AUTHORS
Hai Zaar <haizaar@haizaar.com>
Gil Ran <ril@ran4.net>
SEE ALSO
ldbash(1), ldbashconfig(8), getopts(1), hashstash(1) colors(1) messages(1) urlcoding(1) locks(1)
Linux Epoch Linux