Sponsored Content
Full Discussion: How to set guest static IP
Operating Systems Linux Ubuntu How to set guest static IP Post 302221005 by broli on Saturday 2nd of August 2008 10:27:25 PM
Old 08-02-2008
Quote:
Originally Posted by satimis
Hi broli,


dhcp is dynamic IP. It is working. Guest can connect Internet.

I tried to set "interfaces" with a static IP as a separate PC working alone but without result. I think the settings on "interface" on all Linux distro will be the same.


satimis
i know what dhcp is.
red hat based distros do not use that file to configure networking

if you use dhcp you wont be able to set a "static" ip, unless you have control over the dhcp server
 

7 More Discussions You Might Find Interesting

1. IP Networking

I need HELP to Set up Coyote Linux router with 1 static IP & 64 internal static IP

hello, i need help on setting my coyote linux, i've working on this for last 5 days, can't get it to work. I've been posting this message to coyote forum, and other linux forum, but haven't get any answer yet. Hope someone here can help me...... please see my attached picture first. ... (0 Replies)
Discussion started by: dlwoaud
0 Replies

2. Linux

Could static library include static library?

I have some static library(libxxx.a libyyy.a). And I want to generate my library(libzzz.a), libzzz.a will use libxxx.a and libyyy.a I wan't my application only use libzzz.a, (means libzzz.a had include libxxx.a, libyyy.a), how can I do that? Thank you. example: I have zzz.c. I do ... (4 Replies)
Discussion started by: freemagic
4 Replies

3. Red Hat

Could not see virtual fc in KVM guest OS

Hi All, I have RHEL 5u4 physical system with 2 Qlogic fc cards. It hosts 2 KVM virtual machines which are also running RHEL 5u4 OS. After all these I have created a virutal HBA (refered in google) successfully on the base OS. But the same is not visible to guest OS. My question here is, ... (1 Reply)
Discussion started by: Vichu
1 Replies

4. Programming

Even the Static cURL Library Isn't Static

I'm writing a program which uses curl to be run on Linux PCs which will be used by a number of different users. I cannot make the users all install curl on their individual machines, so I have tried to link curl in statically, rather than using libcurl.so. I downloaded the source and created a... (8 Replies)
Discussion started by: BrandonShw
8 Replies

5. Red Hat

KVM - VM Guest

Background : - Need to create addition 40G storage for VM guest. 1. I have created new KVM - VM guest on RHEL 5.8 server hosting server. 2. Hosting server has occupied all size with LV and there is not space to create new LV. 3. I tried to achieve this requirement by creating 40G file size and... (1 Reply)
Discussion started by: Nats
1 Replies

6. Red Hat

How to set static routes for packets, within the same Network?

I have three systems A,B,C. I want to configure A in such a way that all packets from A to C goes via B. I tried: 1. ip route add 'ip of C' via 'ip of B' 2. route add -net 'net address' netmask gw 'ip of B' These commands work initially when I try a ping or traceroute and expire after... (2 Replies)
Discussion started by: kanak
2 Replies

7. Linux

Unable to set static ip address

Hi All, Am using centos 7 in my vmware workstatio with the bridged network. when run the ifconfig cmd its not at all showing the ip address and pls advise how to set static ip address in my linux box. (1 Reply)
Discussion started by: sarathkumar s
1 Replies
PBUILDER-DIST(1)					      General Commands Manual						  PBUILDER-DIST(1)

NAME
pbuilder-dist, cowbuilder-dist - multi-distribution pbuilder/cowbuilder wrapper SYNOPSIS
pbuilder-dist distribution [architecture] operation [options] [...] cowbuilder-dist distribution [architecture] operation [options] [...] DESCRIPTION
pbuilder-dist is a wrapper that makes it easy to use pbuilder with many different versions of Ubuntu and/or Debian. It is common to symlink this script in order to give it many names in the form of pbuilder-distribution or pbuilder-distribution-architec- ture, like for example pbuilder-feisty, pbuilder-sid, pbuilder-gutsy-i386, etc. The same applies to cowbuilder-dist, which uses cowbuilder. The main difference between both is that pbuilder compresses the created chroot as a a tarball, thus using less disc space but needing to uncompress (and possibly compress) its contents again on each run, and cowbuilder doesn't do this. USAGE
There are many arguments listed on the synopsis; each of them, if used, has to be used exactly in the same order as it appears there. In case you renamed the script to pbuilder-distribution, do not use the distribution parameter; same with i386 / amd64 if the name also con- tains -architecture. distribution Replace this with the codename of the version of Ubuntu or Debian you want to use. architecture This optional parameter will attempt to construct a chroot in a foreign architecture. For some architecture pairs (e.g. i386 on an amd64 install), the chroot will be created natively. For others (e.g. armel on an i386 install), qemu-user-static will be used. Note that some combinations (e.g. amd64 on an i386 install) require special separate kernel handling, and may break in unexpected ways. operation Replace this with the action you want pbuilder to do (create, update, build, clean, login or execute). If you don't specify any action, but the next argument is a .dsc file, it will assume that it should build. Check its manpage for more details. [...] Replace this with other parameters, if needed. For example, if build is the option, you will need to also specify a .dsc file. As a special feature, if you specify a .dsc file you can skip the build option and this script will automatically assume that building is the action you want to do. OPTIONS
--main-only (deprecated: mainonly) If you specify this option, only packages from the main (in Debian) or main and restricted (in Ubuntu) components will be used. By default, all official components are enabled. This only has effect when creating a new environment. --debug-echo The generated pbuilder/cowbuilder command will be printed to the standard output instead of being executed. This is useful for debugging. --buildresult DIRECTORY (pbuilder-dist only) If this option is specified, the resultant files of the pbuilder build are placed in DIRECTORY. --release-only Only use the release pocket. Default for development releases. --security-only Only use the release and security pockets. Suitable environment for preparing security updates. --updates-only Only use the release, security, and updates pocket. Not the proposed-updates pocket. EXAMPLES
pbuilder-dist gutsy create Creates a pbuilder environment for Ubuntu Gutsy, with all components enabled. pbuilder-sid --main-only create Creates a pbuilder environment for Debian Sid, with only the main component. pbuilder-feisty build ./sample_1.0-0ubuntu1.dsc Builds the specified package on an already existing Ubuntu Feisty environment. pbuilder-dist feisty withlog build ./sample_1.0-0ubuntu1.dsc Same as above, but stores pbuilder's output on a file. pbuilder-etch i386 update Updates an existing i386-architecture Debian Etch environment on an amd64 system. cowbuilder-experimental create Creates a cowbuilder environment for Debian Experimental. FILES AND ENVIRONMENT VARIABLES
By default, pbuilder-dist will store all the files it generates in ~/pbuilder/. This can be changed by setting the PBUILDFOLDER environment variable. If the directory doesn't exist, it will be created on the run. A file with the log of the last operation, called last_operation.log, will be saved in the results subdirectory of each build environment. The default authentication method is sudo. You can change this by setting the PBUILDAUTH variable. By default, pbuilder-dist use the master Debian and Ubuntu mirrors. The pbuilder MIRRORSITE and OTHERMIRROR variables are supported, as are the standard ubuntu-dev-tools variables: UBUNTUTOOLS_DEBIAN_MIRROR, PBUILDER_DIST_DEBIAN_MIRROR, UBUNTUTOOLS_DEBSEC_MIRROR, PBUILDER_DIST_DEBSEC_MIRROR, UBUNTUTOOLS_UBUNTU_MIRROR, PBUILDER_DIST_UBUNTU, UBUNTUTOOLS_UBUNTU_PORTS_MIRROR, and PBUILDER_DIST_UBUNTU_PORTS_MIRROR. See ubuntu-dev-tools (5) for details. You may also want to know that pbuilder-dist exports DIST and ARCH environment variables to the invoked process, containing the name of the distribution and the architecture targeted by the current build. You can make use of them, for example, in pbuilderrc. BUGS
If you experience any problem with this script contact me on rainct@ubuntu.com or file a bug at https://bugs.launch- pad.net/ubuntu/+source/ubuntu-dev-tools. Please ensure first that the problem is really this script and not an issue with pbuilder or cowbuilder themselves. SEE ALSO
pbuilder(1), pbuilderrc(5), cowbuilder(1), ubuntu-dev-tools(5). AUTHORS
pbuilder-dist and this manual page were written by Siegfried-A. Gevatter <rainct@ubuntu.com>, with contributions from Iain Lane <iain@orangesquash.org.uk>, Emmet Hikory <persia@ubuntu.com> and others. pbuilder-dist is released under the GNU General Public License, version 2 or later. ubuntu-dev-tools January 10, 2008 PBUILDER-DIST(1)
All times are GMT -4. The time now is 09:57 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy