Sponsored Content
Full Discussion: Windows Emulator?
Operating Systems Linux Slackware Windows Emulator? Post 54021 by zazzybob on Friday 30th of July 2004 06:57:55 AM
Old 07-30-2004
Seeing as you're new to Linux, I'd recommend that you start of with Mandrake. Once your comfortable with it, you can consider installing another distro like Slackware or SuSE.


Cheers
ZB
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix emulator for windows 98

as part of my course i have to do a lot of programming using the universities unix server. i am able to access this from home using telnet but i cannot use axe or anything to edit my files. I was wondering if anyone knew of any software that could enable me yo do this as i like working at 2am when... (1 Reply)
Discussion started by: HALLY
1 Replies

2. UNIX Desktop Questions & Answers

Telnet Emulator

What's the best Telnet and SSH for Win32 platforms, along with an xterm terminal emulator to use nowadays? Thanks. (8 Replies)
Discussion started by: laila63
8 Replies

3. UNIX for Dummies Questions & Answers

Can anyone recommend a freeware X-windows emulator?

Are there any freeware or shareware X-windows emulators out there? I only have the need for an emulator on rare occasions and would like to avoid having to purchase something like Exceed or x32. Thanks (1 Reply)
Discussion started by: rhack
1 Replies

4. UNIX for Dummies Questions & Answers

UNIX Emulator

Where can I download a unix Emulator for Training and education of the IT personal in my company. (9 Replies)
Discussion started by: st_matan
9 Replies

5. Linux

how to use terminal emulator???

hello, can any body tell how to use terminal emulator.... i want to check he serial port communication with the help of that terminal emmulator.... also tell me how to open terminal emmulator.....and how to configure it........and how to use it... I am using fedora core 6..... (1 Reply)
Discussion started by: arunchaudhary19
1 Replies

6. Solaris

Windows emulator on Solaris machine

Hello together, in our German company we have buyed one English Windows XP version. Every one of us should have access to this windows installation. So we have reconsidered that we want to install this Windows on our SUN SPARC Solaris machine. It is only used for checking out licenses of our own... (2 Replies)
Discussion started by: SPORTS
2 Replies

7. Windows & DOS: Issues & Discussions

Mac OS X emulator for Windows XP?

Not quite sure if this is the right section, but you guys know lots of good stuff. Is there a good OS X emulator that I can put on my Windows XP system? I have PC's and at work/lab they run everything on mac's. Due to program compatibility issues, it would be nice if I could run mac software on... (2 Replies)
Discussion started by: silkiechicken
2 Replies

8. UNIX for Dummies Questions & Answers

Terminal Emulator

Hi, I was just wondering how to distinguish between the two terms: 1. Terminal emulator (vt100, vt220 and so on) 2. shell command line Then i decided to conclude myself that these 2 are very equivalent. am I right? this actually came to my mind when I was using my HP-UX terminal. I am... (1 Reply)
Discussion started by: messi777
1 Replies

9. Hardware

SparcStation 20 emulator

Hello, Just wanted to let interested people know that we've recently released a Linux freeware version of SparcStation 20 emulator. It emulates SS20 with some basic peripherals: a single SPARC V8 32bit CPU, up to 512MB RAM, an NCR53C94 SCSI controller, 2 serial lines, disks, a network adapter,... (7 Replies)
Discussion started by: Thlan
7 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)
All times are GMT -4. The time now is 03:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy