Sponsored Content
Full Discussion: SCO and VMware
Top Forums UNIX for Dummies Questions & Answers SCO and VMware Post 302097438 by Corona688 on Friday 24th of November 2006 10:15:43 AM
Old 11-24-2006
According to this you need the 5.0.7 boot CD -- you can get it from downloading SCO's trial version. The 5.0.4 CD won't work, it'll give you the error you noted.
 

6 More Discussions You Might Find Interesting

1. SCO

all tcp are CLOSED on SCO Unix on VMWARE

Hi folks, First of all, sorry about my english, isn't the best and thks for advance. Here es my problem... I have virtualize an SCO unix with VMware ESX 3 and everything was going on beatifull until that i try to connect from anorther host, i can't do it so i check the connection with... (5 Replies)
Discussion started by: martocapo
5 Replies

2. SCO

VMware and SCO Unixware 7.1.4 Network issue

I am haveing a problem with my VMware ESXi 4.1 server and a virtual SCO UnixWare 7.1.4 server that I need for a legacy application for my company. The problem seems simple but I can't find a solution. The UnixWare (UW) server is a clean install and patched as SCO recommends. I am able to telnet to... (1 Reply)
Discussion started by: DudeCrush
1 Replies

3. SCO

Failure while installing SCO UNIXWare7.1.4 on vmware workstation9, virtualbox

Sir I am trying to install UnixWare7.1.4 on vmware workstation9, virtualbox and I am getting the following error FATAL BOOT ERROR: decompression failed For installing SCO Unixware7.1.4 I have created virtual harddisk of size 18GB, 1024 RAM, 64bit video memory, chosen unixware7.1.4... (1 Reply)
Discussion started by: rupeshforu3
1 Replies

4. UNIX for Advanced & Expert Users

SCO 6.0 & VMware problems

I've moved a physical server over to VMWare ESXi 5.1 using SCO 6.0 with MP4. For whatever reason, people are occasionally getting kicked out or are closing out their telnet session and it is leaving their processes running. When this happens, the sar %idle drops from 98-95% down to 25-20%. ... (1 Reply)
Discussion started by: Carlitos71
1 Replies

5. SCO

Moving SCO Virtual Machine in VMWare Environment: Critical Licensing Error Messages

Some years ago our company chose to run a critical proprietary app under SCO Unix. My predecessor tried to move A SCO Unix virtual machine from our dedicated VMWare environment to a shared Cloud VMWare environment. My predecessor received licensing messages from these critical servers so... (2 Replies)
Discussion started by: timfox1234
2 Replies

6. SCO

Configuare Network SCO UNIX 5.0.7 on Vmware

hi i installed sco unix open server 5.0.7 on virtual machine vmware and runing it, its work perfect and good. now how i can configuare network at scoadmin that i able to access nework ? ---------- Post updated at 08:56 AM ---------- Previous update was at 01:47 AM ---------- nobody can... (2 Replies)
Discussion started by: farzad226
2 Replies
SVNPATH(1)																SVNPATH(1)

NAME
svnpath - output svn url with support for tags and branches SYNOPSIS
svnpath svnpath tags svnpath branches svnpath trunk DESCRIPTION
svnpath is intended to be run in a Subversion working copy. In its simplest usage, svnpath with no parameters outputs the svn url for the repository associated with the working copy. If a parameter is given, svnpath attempts to instead output the url that would be used for the tags, branches, or trunk. This will only work if it's run in the top-level directory that is subject to tagging or branching. For example, if you want to tag what's checked into Subversion as version 1.0, you could use a command like this: svn cp $(svnpath) $(svnpath tags)/1.0 That's much easier than using svn info to look up the repository url and manually modifying it to derive the url to use for the tag, and typing in something like this: svn cp svn+ssh://my.server.example/svn/project/trunk svn+ssh://my.server.example/svn/project/tags/1.0 svnpath uses a simple heuristic to convert between the trunk, tags, and branches paths. It replaces the first occurrence of trunk, tags, or branches with the name of what you're looking for. This will work ok for most typical Subversion repository layouts. If you have an atypical layout and it does not work, you can add a ~/.svnpath file. This file is perl code, which can modify the path in $url. For example, the author uses this file: #!/usr/bin/perl # svnpath personal override file # For d-i I sometimes work from a full d-i tree branch. Remove that from # the path to get regular tags or branches directories. $url=~s!d-i/(rc|beta)[0-9]+/!!; $url=~s!d-i/sarge/!!; 1 LICENSE
GPL version 2 or later AUTHOR
Joey Hess <joey@kitenet.net> Debian Utilities 2013-12-23 SVNPATH(1)
All times are GMT -4. The time now is 08:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy