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
PKG_SUMMARY(5)						      BSD File Formats Manual						    PKG_SUMMARY(5)

NAME
pkg_summary -- summary of binary package repository DESCRIPTION
The file pkg_summary contains information about each package in a binary package repository as a list of variable-value pairs. The variables describing different packages are separated by one empty line. Each line has the format VARIABLE=VALUE. If the value consists of more than one line, each line is prefixed with VARIABLE=. Multi-line variables are guaranteed to be in consecutive lines. The following variables are used: BUILD_DATE (required) The date and time when the package was built. CATEGORIES (required) A list of categories which this package fits in, separated by space. COMMENT (required) A one-line description of the package. CONFLICTS (optional) A list of dewey patterns of packages the package conflicts with, one per line. If missing, this package has no conflicts. DEPENDS (optional) A list of dewey patterns of packages the package depends on, one per line. If missing, this package has no dependencies. DESCRIPTION (required) A more detailed description of the package. FILE_CKSUM (optional) A checksum type supported by digest(1) and checksum separated by space character. FILE_NAME (optional) The name of the binary package file. If not given, PKGNAME.tgz can be assumed. FILE_SIZE (optional) The size of the binary package file, in bytes. HOMEPAGE (optional) A URL where more information about the package can be found. LICENSE (optional) The type of license this package is distributed under. If empty or missing, it is OSI-approved. MACHINE_ARCH (required) The architecture on which the package was compiled. OPSYS (required) The operating system on which the package was compiled. OS_VERSION (required) The version of the operating system on which the package was compiled. PKG_OPTIONS (optional) Any options selected to compile this package. If missing, the package does not support options. PKGNAME (required) The name of the package. PKGPATH (required) The path of the package directory within pkgsrc. PKGTOOLS_VERSION (required) The version of the package tools used to create the package. PREV_PKGPATH (optional) The previous path of the package directory within pkgsrc when a package was moved. (See SUPERSEDES below for a renamed package.) PROVIDES (optional) A list of shared libraries provided by the package, including major version number, one per line. If missing, this pack- age does not provide shared libraries. REQUIRES (optional) A list of shared libraries needed by the package, including major version number, one per line. If missing, this package does not require shared libraries. SIZE_PKG (required) The size of the package when installed, in bytes. SUPERSEDES (optional) A list of dewey patterns of previous packages this package replaces, one per line. This is used for package renaming. The pkg_summary file can be generated using the pkg_info(1) -X option. For example, the following will list this data for all installed packages: pkg_info -X -a SEE ALSO
digest(1), pkg_info(1) HISTORY
The pkg_summary format was first officially documented in April 2006. BSD
April 11, 2009 BSD
All times are GMT -4. The time now is 03:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy