12-03-2004
Neither is better nor worse than the other. There are many different flavours of UNIX and Linux - each with its own strengths and weaknesses.
On a laptop, you are going to be looking at one of the *BSD's or some distribution of Linux. Many people have personal favourites (mine is SUSE Linux) - but this all depends on your requirements and level of UNIX/Linux expertise.
For a beginner that wants good hardware recognition, go with Mandrake Linux, if you're proficient and want good hardware recognition go with SUSE, and if you're looking for a truly configurable and rock-solid Linux system go with Slackware.
Again; many people will question this and have their own preferences, it is all dependent on your needs and ability.
Cheers
ZB
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Aahhhh!! I am so much frustrated trying to recover my superuser account. I need help!!! Please can anyone tell me how to recover a the root account? Thank you in advance. (1 Reply)
Discussion started by: pnoi_blitz
1 Replies
2. UNIX for Dummies Questions & Answers
Could anyone explain if Linux is Unix? I'm a newbie here, just installed Oracle 8i on Redhat 7.2. (4 Replies)
Discussion started by: Prettyman
4 Replies
3. Answers to Frequently Asked Questions
Unix is the name of an operating system. And unix is a registered trademark. This is what makes things murky.
One of my favorite books is The Design and Implementation of the 4.3BSD UNIX Operating System. That book is out of print, but a newer book is available: The Design and Implementation... (0 Replies)
Discussion started by: Perderabo
0 Replies
4. Linux
Hey there, new to the forum :)
Im currently at university studying UNIX, but i need some help. Can someone help me out with operational / technical differences between the two? Even if You just give me some topics i can go research them...
much appreciated
Josh (1 Reply)
Discussion started by: kiwi_bloke
1 Replies
5. UNIX for Dummies Questions & Answers
quick question that may bring long answers :)
I am currently looking into porting an existing Recital system from Unix to Linux. possibly not a good idea :) Basically;
Would i be better shooting myself in the foot now? or
do you know if there would be a fair expense due to buying Linux and the... (0 Replies)
Discussion started by: Kuz972
0 Replies
6. UNIX for Dummies Questions & Answers
hi all,
i have a linux operating system...can i practice unix commands on linux system....there is any changes in the commands.....can any one post some meterial..
thanks (1 Reply)
Discussion started by: madhu_msinus@ya
1 Replies
7. UNIX for Dummies Questions & Answers
why would one choose unix over linux? (2 Replies)
Discussion started by: lizzy
2 Replies
8. Fedora
I just started a new semester and I started my UNIX class yesterday. I've already decided to use python along with my learning process but what I really want to use with it is Kali as my UNIX/Linux platform to learn off of since I already wanted to learn Cyber Sec. anyways. I just wanted to know if... (12 Replies)
Discussion started by: ApacheOmega
12 Replies
9. Post Here to Contact Site Administrators and Moderators
We work hard to make The UNIX and Linux Forums one of the best UNIX and Linux knowledge sources on the net. The site is certainly one of the top UNIX and Linux Q&A sites on the web. In order to provide certain members the best quality account services, you can now get some great extra features by... (2 Replies)
Discussion started by: Neo
2 Replies
10. What is on Your Mind?
Forum Moderation @UNIX.com | The UNIX and Linux Forums
https://youtu.be/WGwgibE4Rq0
Also note: In the video I mentioned removing legacy menu items in the ModCP which are unused. I have already "CSS'ed out" the unused menu items:
... (0 Replies)
Discussion started by: Neo
0 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)