Sponsored Content
Full Discussion: VCS for Solaris 32 bit OS
Operating Systems Solaris VCS for Solaris 32 bit OS Post 302525815 by snchaudhari2 on Saturday 28th of May 2011 05:40:57 PM
Old 05-28-2011
VCS for Solaris 32 bit OS

Hi Admins,

I know that VCS supports Solaris x86-64bit only...and I need vcs for Solaris 32 bit-x86..running on vmware workstation.. I need to run vcs on vmware workstation...And my laptop support only 32bit... Please suggest..

Thanks..
 

10 More Discussions You Might Find Interesting

1. Solaris

64 bit solaris 9

How can I tell if im running a 64 bit version of solaris? (1 Reply)
Discussion started by: csaunders
1 Replies

2. Solaris

32 / 64 bit OS in Solaris

Dear All, This is Viswanadhan, new to Sun Solaris domain. In Sun Solaris ( SPARC ) has 32 bit and 64 bit OS. While insallation of OS there no specific option for 32 / 64 bit OS .On which basis OS installs for 32 / 64 bit OS ? Regards, Viswanadhan. (1 Reply)
Discussion started by: viswanadhan
1 Replies

3. Solaris

Solaris 64-bit to 32-bit

I had previous implemented the following in my menu.lst to be able to get to 32-bit operations. # title Solaris 10 32-bit root (hd0,0,a) kernel /platform/i86pc/multiboot kernel/unix module /platform/i86pc/boot_archive </code> Now, it is not working as I get the following error : ... (0 Replies)
Discussion started by: praveenr
0 Replies

4. Solaris

Porting C++ 32-bit code on 64-bit Solaris

Hi, I am trying to convert 32-bit code to 64-bit. I have defined function int main() { int* l; size_t len1; fun(len1); return 0; } void fun(int* ptr) { cout<<"\nsizeof(ptr)"<<sizeof(ptr); } However while compiling getting error as : Error: Formal argument ptr... (2 Replies)
Discussion started by: amit_27
2 Replies

5. Solaris

Solaris os 32 bit or 64 bit

:confused: how to find out wether my os is 32 bit or 64 bit. I am using Solaris 5.6. also i want to know the difference between 32 bit and 64bit os. any help will be much appreciated as i am in urgent need of this information (6 Replies)
Discussion started by: asalman.qazi
6 Replies

6. Solaris

Solaris + VCS , move a resource to another group

Hi, I am running Solaris 10 + VCS 5 in one of our environment. Recently one of my colleague configured all resources in a single service group.( ie, one service group which has all resources) ,Usually we create seperate service groups for Hardware & for application. For eg: SYS_HW_GRP, will... (0 Replies)
Discussion started by: mpics66
0 Replies

7. Solaris

VCS cluster verification on solaris

I am looking for a checklist, to audit the existing VCS (veritas cluster) setup on Solaris platform. Please let me know points/things that should be audited/verified. (0 Replies)
Discussion started by: user2ux
0 Replies

8. Solaris

VCS Simulator for Solaris

Hi, I just wanted to know, if VCS simulator (For Solaris) is available for free ? I will be running that on my Windows XP. If somebody have, please share the link. Regards ---------- Post updated at 08:34 AM ---------- Previous update was at 07:43 AM ---------- I was able to get it... (0 Replies)
Discussion started by: solaris_1977
0 Replies

9. Solaris

VCS on Solaris: VCS ERROR V-16-2-13077 (host2) Agent is unable to offline resource(DiskReservation)

hi, dear all I get a problem "VCS ERROR V-16-2-13077 " on VCS 4.1 for Solaris 10. I can not offline the host2 when the raid is bad. I don't know the reason and how to offline host2 and switch to host1. please help me, thank you! the message of engine_A.log is : ... (2 Replies)
Discussion started by: ForgetChen
2 Replies

10. Solaris

Solaris Trunking and its impact on VCS cluster and others

Hello guys, I have a question regarding link aggregation / trunking in Solaris 9 Sun Trunking does not come by default in Solaris 9 unlike Solaris 10 where we can use the "dladm" command to trunk 4 physical NIC interfaces together. My question is in Solaris 9. Will the configurations of... (1 Reply)
Discussion started by: br1an
1 Replies
PKGKDE-VCS(1)						  Debian KDE packaging VCS helper					     PKGKDE-VCS(1)

NAME
pkgkde-vcs - a helper tool for Debian pkg-kde VCS repositories. SYNOPSIS
pkgkde-vcs [-vy] subcommand [ SUBCOMMAND OPTIONS ] [ -- EXTERNAL TOOL OPTIONS ] pkgkde-git [-vy] subcommand [ SUBCOMMAND OPTIONS ] [ -- EXTERNAL TOOL OPTIONS ] DESCRIPTION
pkgkde-vcs is a helper tool which aims to simplify a couple of routine tasks associated with packaging management in version control system (VCS) repositories. pkgkde-vcs transparently supports VCSes used by Debian Qt/KDE maintainer groups wrapping various VCS related command sequences into a convenient CLI interface. Please note that this helper enforces the best practises and packaging conventions adopted by Debian Qt/KDE maintainer groups and therefore it should not be considered as a general purpose packaging helper. pkgkde-vcs should be run from the fully checked out packaging repository of the package it is supposed to act upon. Firstly, it attempts to detect a VCS in use for the particular packaging in the working directory. Please note, that the detection might fail if underlying VCS utilities are not installed. If you want or have to force a specific VCS type, run the command as pkgkde-$vcs, for example pkgkde-git. If detection is successful, pkgkde-vcs will perform tasks as defined for the specified subcommand (e.g. tag). Different set of subcommands might be defined for each VCS and each of them might accept a different set of SUBCOMMAND OPTIONS (see below). All locally unrecognized subcommand options (or the ones specified as EXTERNAL TOOL OPTIONS after --) will be passed to the external VCS tool(s) which pkgkde-vcs executes to do the job. pkgkde-vcs accepts a couple of common options which apply to the helper as whole or are common for all VCSes it supports. They should be passed before subcommand in order to be recognized. Even if pkgkde-vcs does extensive sanity checks before doing anything, an underlying command it executes might still fail. Then pkgkde-vcs will terminate immediately possibly leaving repository in an inconsistent state. It is up to a user to recover from such a failure. At the moment, pkgkde-vcs supports only Git VCS. OPTIONS
Common options -y By default, execution of the first external command that makes changes to the repository has to be explicitly confirmed by user. However, if this option is specified, the first command will be run without confirmation. -n Do not run any external commands that make changes to the repository. Useful with -v to see what commands with what options would be run. -v Be more verbose (e.g. show external commands as they are executed). -- EXTERNAL TOOL OPTIONS Pass additional EXTERNAL TOOL OPTIONS to the external commands pkgkde-vcs executes to accomplish the task. See documentations of the specific subcommand for more details. SUPPORTED VERSION CONTROL SYSTEMS AND SUBCOMMANDS
Git In order to use pkgkde-vcs with Git, git(1) must be available in PATH. Bare Git repositories are not supported and Git repository should be in the fully checked out state (except clone). The following subcommands for Git repositories are supported at the moment: clone Clone the specified pkg-kde git repository. This subcommand should be specified by forcing VCS to git, i.e. by running pkgkde-git command rather than pkgkde-vcs. Repository should be specified relatively to the root of the official pkg-kde repository tree. Once operation is complete, the cloned repository will be put at the same relative location on the local filesystem and update-config (see below) will be executed on it. For example, in order to clone kde4libs repository from kde-sc, akonadi repository from kde-req and pkg-kde-tools repository from the root tree, execute: $ pkgkde-git clone kde-sc/kde4libs $ pkgkde-git clone kde-req/akonadi $ pkgkde-git clone pkg-kde-tools tag Tag current packaging state (HEAD) as upload to Debian archive. Repository working tree must be clean before executing this subcom- mand. Current package version and target distribution are automatically determined from debian/changelog. Distribution must be a valid Debian suite in order to avoid tagging of unfinished (aka UNRELEASED) revisions. The subcommand will create an annotated Git tag under "debian/" namespace. The subcommand itself does not accept any additional options. All EXTERNAL TOOL OPTIONS (if specified) and will be passed to git tag invocation. It is recommended to sign tags by speci- fying -s option. The tag created by pkgkde-vcs tag will meet the following requirements: o The tag will named as "debian/<version>" where <version> is a full debian package version without epoch. All occurrences of the ~ character in <version> will be replaced with the - character because Git does not support ~ character in tag names. o The tag will be assigned the message with content like <version>/<distribution>" where <version> is a full debian version of the package (without any modifications including epoch) and <distribution> is the distribution this package is uploaded. For example, a standard pkgkde-vcs tag will execute the following under the hood (assuming version is 1:2.3.4-5 and distribution is experimental): $ git tag debian/2.3.4-5 -m "1:2.3.4-5/experimental" update-config Do some common configuration on the checked out packaging repository. At the moment, the subcommand performs the following: o Set up master branch and debian tags for pushing. -f option may be specified to force update of the pushing configuration even if some pushing configuration already exists. o Set repository user name and email address to the values of the DEBFULLNAME and DEBEMAIL environment variables respectively. -f option may be specified to override the values even if the repository has some specified already. LICENSE
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. AUTHORS
Modestas Vainius <modax@debian.org> 0.15 2012-05-27 PKGKDE-VCS(1)
All times are GMT -4. The time now is 03:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy