Sponsored Content
Operating Systems BSD How to install Ultrix 4.2 on Qemu? Post 302944941 by gull04 on Sunday 24th of May 2015 04:43:54 AM
Old 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

How to password recovery on Ultrix

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

Anyone ever used qemu and networked it ?

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

QEMU not booting my image

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

Qemu + gdb

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

IBM AIX and QEMU Emulator?

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

Running c code in ARM QEMU

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

help about qemu-kvm boot with initrd

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

[Ultrix] /etc/init failed, errno 2

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

QEMU performance?

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
ldd_pa(1)						      General Commands Manual							 ldd_pa(1)

NAME
ldd_pa: ldd - list dynamic dependencies of executable files or shared libraries on PA-RISC systems SYNOPSIS
filename... Remarks This manpage describes on PA-RISC systems. For on Integrity systems, see ldd_ia(1). DESCRIPTION
is a command that can list the dynamic dependencies of incomplete executable files or shared libraries. lists verbose information about dynamic dependencies and symbol references. If the object file is an executable file, lists all shared libraries that would be loaded as a result of executing the file. If it is a shared library, lists all shared libraries that would be loaded as a result of loading the library. uses the same algorithm as the dynamic loader and to locate the shared libraries. See and sections in dld.sl(5) for more information. Options recognizes the following options: PA-RISC 32-bit only. Used in conjunction with and/or to force to bind all dependent libraries and report unsats. By default the smartbind mechanism in only binds libraries whose symbols are explicitly referenced. Check reference to data symbols. Check reference to data and code symbols. Display the search path used to locate the shared libraries. Display all dependency relationships. EXTERNAL INFLUENCES
Environment Variables uses the following environment variables to locate shared libraries. PA-RISC 64-bit mode: A colon-separated list of path names which defines the search path for shared libraries at runtime. See in dld.sl(5) for more information. A colon-separated or space-separated list of libraries which the dynamic loader implicitly loads first at runtime. See in dld.sl(5) for more information. A colon-separated list of path names which defines the search path for shared libraries at runtime. See and in dld.sl(5) for more information. The following internationalization variables affect the execution of Determines the locale category for native language, local customs and coded character set in the absence of and other environment variables. If is not specified or is set to the empty string, a default of (see lang(5)) is used instead of Determines the values for all locale categories and has precedence over and other environment variables. Determines the locale that should be used to affect the format and contents of diagnostic messages written to standard error. Determines the locale category for numeric formatting. Determines the locale category for character handling functions. Determines the location of message catalogs for the processing of If any internationalization variable contains an invalid setting, behaves as if all internationalization variables are set to See envi- ron(5). DIAGNOSTICS
prints the record of shared library path names to stdout. The optional list of symbol resolution problems are printed to stderr. returns zero when the operation is successful. A non-zero return code indicates that an error occurred. EXAMPLES
By default prints a simple dynamic path information. This consists of the dependencies recorded in the executable (or the shared library) followed by the physical location where these libraries are found. The option causes to print dependency relationship along with the dynamic path information. The option causes to analyze all symbol references and print information about unsatisfied code and data symbols. The option causes to print the dynamic search path lists used to load the libraries in the order that the path lists are referenced: WARNINGS
does not list shared libraries explicitly loaded using dlopen(3C) or shl_load(3X). FILES
output file 32-bit PA-RISC dynamic loader 64-bit PA-RISC dynamic loader 32-bit dummy executable loaded to check the dependencies of shared libraries. 64-bit dummy executable loaded to check the dependencies of shared libraries. message catalog SEE ALSO
System Tools ld(1) invoke the link editor Miscellaneous a.out(4) assembler, compiler, and linker output dld.sl(5) PA-RISC dynamic loader Texts and Tutorials
All times are GMT -4. The time now is 02:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy