9 More Discussions You Might Find Interesting
1. Red Hat
Hi
In opensuse we have this nice version control variable I use much when designing rpm spec files:
rpm --showrc | grep suse_version
%if 0%{?suse_version} > 0 && 0%{?suse_version} < 1700
-14: suse_version 1140But I do not find anything close to this in rhel/centos
The only way... (0 Replies)
Discussion started by: mortenb
0 Replies
2. UNIX for Dummies Questions & Answers
Hi How would i get xconsole of redhat5 linux machine.
Following is the distribution detail.
# lsb_release -a
LSB Version: :core-3.1-ia32:core-3.1-noarch:graphics-3.1-ia32:graphics-3.1-noarch
Distributor ID: RedHatEnterpriseServer
Description: Red Hat Enterprise Linux Server release 5.5... (1 Reply)
Discussion started by: pinga123
1 Replies
3. Red Hat
hi ,
Can anybody please let me know the difference in the version of RedHat linux 5.2 and 9.0.
Will there be any difference if i execute the script in RedHat linux 9.0 insead of RedHat linux 5.2?
Thanks in Advance. (7 Replies)
Discussion started by: flamingo_l
7 Replies
4. Red Hat
Hi,
I would like to know if should i patch my system and sshd based on the version that i have here below:
cat /etc/redhat-release
Red Hat Enterprise Linux ES release 4 (Nahant Update 5)
------------
uname -a: redhat kernel version and type (64-bit or not)
Linux server2 2.6.9-55.ELsmp... (2 Replies)
Discussion started by: lamoul
2 Replies
5. UNIX for Advanced & Expert Users
How can I find out with a C program, on which RedHat version the program is being ran ? I do know through compilation variables that I'm on RedHat but so far cannot find out which one.
Currently the closest I got was to invoke an ls or cat through syscall for the release or motd files.
... (5 Replies)
Discussion started by: amirvosko
5 Replies
6. UNIX for Dummies Questions & Answers
Hi All,
I need to know RedHat linux version installed on a different servers.
I know uname -a or /proc/version
Is any other command to know the Linux version????
When we telnet to any of the Linux server, the version shows very clearly like
Red Hat Enterprise Linux ES release 3 (Taroon... (1 Reply)
Discussion started by: bache_gowda
1 Replies
7. Linux Benchmarks
==============================================================
BYTE UNIX Benchmarks (Version 3.11)
System -- Linux linux.hhc.ac.uk 2.6.9-11.ELsmp #1 SMP Fri May 20 18:26:27 EDT 2005 i686 i686 i386 GNU/Linux
Start Benchmark Run: Wed Jul 6 15:06:07 BST 2005
1 interactive users.... (2 Replies)
Discussion started by: Garp
2 Replies
8. Linux
I just purchased a Linksys WPC11 Version 4 wireless PCMCIA card, and am looking for the device driver for it.
Apparently, as opposed to Version 1-4, it uses a RealTek 8180 chipset. However, the kernel module which Linksys released does not work on any other distribution EXCEPT for Redhat Linux.... (0 Replies)
Discussion started by: Farhan
0 Replies
9. UNIX for Dummies Questions & Answers
Guys
How do i know the version of linux (Redhat) on one of our systems..Thanks in advance..The uname -r gives 2.4.18-0.13..Is it the kernel version (3 Replies)
Discussion started by: sssow
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)
