9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi ALL,
I was looking out for any freeware tool which can compare config properties of 2 linux machines for ex java properties.
Tried in Google but no luck.
Any help would be greatly appreciated :) (3 Replies)
Discussion started by: nikhil jain
3 Replies
2. Solaris
Hi,
I am porting a piece of code from Solaris to Linux. Code uses VMSTAT command.
On Solaris machine VMSTAT output is following:
uname -a:
SunOS rgsm01 5.9 Generic_118558-03 sun4u sparc SUNW,Sun-Fire-V440
vmstat:
kthr memory page disk faults cpu
r b w swap free re mf pi po fr de sr m1 m2... (3 Replies)
Discussion started by: Basant Mishra
3 Replies
3. Shell Programming and Scripting
When I run script listed below it causes my Linux to hang. When it freezes I can do totally nothing, move cursor, switch to another terminal or whatever. Linux is just not responding and the only way out I know is a hard reset of PC.
#!/bin/bash
if ; then
echo "one parameter is needed: IP... (3 Replies)
Discussion started by: mass85
3 Replies
4. UNIX for Dummies Questions & Answers
Hi alll
i had a file authorized_keys on machine one. now i need to copy this authorized keys file into machine2,machine 3.....
i use
scp authorized_keys root@192.168.168.11:/tmp/
for copying file .
is there ant way to copy the same filr to multiple machines at one go
... (1 Reply)
Discussion started by: kalyankalyan
1 Replies
5. Programming
Hey guys, i am creating a tool that'll run a couple network test, generate a report then email the report. Now i a bit stuck with the email sending part... I tried at first a script which worked on some machines but then it'll work fine on some machine and act up on others... I can't really rely... (2 Replies)
Discussion started by: Jess83
2 Replies
6. Red Hat
We have two machines, prod and uat. The TERM variable in both machines are different
prod
echo $TERM
vt100
UAT
echo $TERM
xterm
I have checked the .profile file and could not find any entry ? There are some scripts on the box which are run by Autosys scheduler they seem to run in... (1 Reply)
Discussion started by: amit1_x
1 Replies
7. HP-UX
Hi All,
I'm not sure if this has been posted before. Anyone knows a site how to do a hardware check (ex. ioscan) on an HP-UX machine that runs in Linux,Solaris and Windows? I'm checking the docs.hp.com and it gives me HP-UX stuff. does HP even supports such highlevel commands we use on HP-UX OS?... (2 Replies)
Discussion started by: grumash
2 Replies
8. Linux
How do I map some winxp machines on a linux machine using samba?
any help will be apreciated
Thanks (3 Replies)
Discussion started by: raulb
3 Replies
9. IP Networking
i hear everyone talking about this SAMBA "service" that comes with Linux distros...im having no luck getting this to work, neither one of the boxes on the network sees each other. im only an intermediate level user of Linux...Networking with Windows machines is relatively new to me, so you can... (3 Replies)
Discussion started by: fuji250
3 Replies
build(1) General Commands Manual build(1)
NAME
build - build SuSE Linux RPMs in a chroot environment
SYNOPSIS
build [--clean|--no-init] [--rpms path1:path2:...] [--arch arch1:arch2:...] [--root buildroot] [specfile|srcrpm]
build --help
build --verify
DESCRIPTION
build is a tool to build SuSE Linux RPMs in a safe and clean way. build will install a minimal SuSE Linux as build system into some direc-
tory and will chroot to this system to compile the package. This way you don't risk to corrupt your working system (due to a broken spec
file for example), even if the package does not use BuildRoot.
build searches the spec file for a BuildRequires: line; if such a line is found, all the specified rpms are installed. Otherwise a selec-
tion of default packages are used. Note that build doesn't automatically resolve missing dependencies, so the specified rpms have to be
sufficient for the build.
If a spec file is specified on the command line, build will use this file and all other files in the directory for building the package. If
a srcrpm is specified, build automatically unpacks it for the build. If neither is given, build will use all the specfiles in the current
directory.
OPTIONS
--clean
remove the build system and reinitialize it from scratch.
--no-init
skip the build system initialization and start with build immediately.
--list-state
list rpms that would be used to create a fresh build root. Does not create the build root or perform a build.
--rpms path1:path2:path3...
Where build can find the SuSE Linux RPMs needed to create the build system. This option overrides the BUILD_RPMS environment vari-
able.
--arch arch1:arch2:arch3...
What architectures to select from the RPMs. build automatically sets this to a sensible value for your host if you don't specify
this option.
--root buildroot
Specifies where the build system is set up. Overrides the BUILD_ROOT enviroment variable.
--useusedforbuild
Tell build not to do dependency expansion, but to extract the list of packages to install from "# usedforbuild" lines or, if none
are found, from all "BuildRequires" lines. This option is useful if you want to re-build a package from a srcrpm with exactly the
same packages used for the srcrpm build.
--norootforbuild
--help Print a short help text.
--verify
verify the files in an existing build system.
.spec FILE OPTIONS
The build command interprets some special control comments in the specfile:
# norootforbuild
# needsrootforbuild
build uses either user root or user abuild in the build system to do the build. For non-SUSE distros as well as since SUSE 10.2,
the default build user is abuild. For 10.2 and before, the default build user is root. These two flags in the spec file allow to
deviate from the defaults and force-set the build user to abuild and root (for # norootforbuild and # needsrootforbuild respec-
tively.
# needsbinariesforbuild
provide the binary rpms that have been used to set up the build root in /.build.binaries within the build root.
ENVIRONMENT
BUILD_ROOT
The directory where build should install the chrooted build system. "/var/tmp/build-root" is used by default.
BUILD_RPMS
Where build can find the SuSE Linux RPMs. build needs them to create the build system. "/media/dvd/suse" is the default value
which will do the trick if you have the SuSE Linux DVD mounted.
BUILD_RPM_BUILD_STAGE
The rpm build stage (-ba, -bb, ...). This is just passed through to rpm, check the rpm manpage for a complete list and descrip-
tions. "-ba" is the default. You can use this to add more options to RPM.
SEE ALSO
rpm(1),
Maximum RPM:
http://www.rpm.org/max-rpm/
cross distribution packaging:
http://en.opensuse.org/Build_Service/cross_distribution_package_how_to
SUSE packaging standards and guidelines:
http://en.opensuse.org/Packaging
(c) 1997-2008 SuSE Linux AG Nuernberg, Germany build(1)