Sponsored Content
Full Discussion: Building a 43p using BOOTP
Operating Systems AIX Building a 43p using BOOTP Post 302145782 by johnf on Thursday 15th of November 2007 06:03:40 AM
Old 11-15-2007
Can I assume you mean on the SUSE Linux server?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

bootp/tftp

Hi, Setting up print queue, using SMIT on AIX And I have an option saying do I wish to make this a BOOTP/TFTP server. What exactly does this do? Thanks (3 Replies)
Discussion started by: maverick
3 Replies

2. UNIX for Dummies Questions & Answers

Network Install PXE/BootP/TFTP

Im trying to help my professor at school, were trying to setup a linux server, that is configured with bootp/tftp/PXE. the client computer NICs have support to boot off PXE. What we would like to do is if a client computer does not have an OS, it would boot off the server, and display a menu to the... (1 Reply)
Discussion started by: kwalick
1 Replies

3. UNIX for Dummies Questions & Answers

Save 43p bios?

Is there any way to backup the bios on a 43P-140 7043? (0 Replies)
Discussion started by: freestyle10269
0 Replies

4. Linux

BOOTP on HP Thin clients

Please m new around here! Can anyone take me thru implementing bootp on my thin clients via my central server? Preciate ur assistance. Thanks folks! (2 Replies)
Discussion started by: chuk_uka
2 Replies

5. AIX

43p 120

I have acquired a 43p 120 (7248-120) and I have two questions: Can anyone remember what is the highest version of AIX which I can install (5.1 I believe) and Can anyone remember how to boot this from the CDROM (boot floppy?) (1 Reply)
Discussion started by: johnf
1 Replies

6. SCO

Need help in BOOTP Server and Client configuration

Dear All; I need help in configuring the BOOTP server, I have found something on internet forums regarding the file: bootptab and editing some lines but Im not if they are all correct. Also, I need help to configure my clients (UNIX) to boot up with this bootp server(UNIX). I will be... (1 Reply)
Discussion started by: amirzandi
1 Replies

7. AIX

model 43P 7248 Recovery!

HI all! this is my problem: my boss got a Model 43P 7248-100 PowerPC server with the AIX 4.2 os, but some days ago it crashed and now it doesn't want to boot up again, it stops after the initial diagnostic phase with the "PowerPC" screen! I must recover some important data from the hard disk, so... (6 Replies)
Discussion started by: AKO
6 Replies

8. AIX

brisque impose 43P 150 aix version 4 HELP!!!!!!!!

hi to everybody I have a problem with the AIX version 4: I can not get into failsafe session kindly someone knows how to enter this mode? thanks in advance (5 Replies)
Discussion started by: elektrospeed
5 Replies

9. AIX

EXP400 with 43P machine not booting

Hello I connected the exp400 & turned on the aix machine which is 7043-150 but now I guess probably ODM is corrupted as it does not boot. Its stuck at 0518 code. Also, on the console it shows stuck on the kernel, which then it does not want to boot. Is it possible to fix from maintenance... (1 Reply)
Discussion started by: pdhawan
1 Replies

10. Solaris

Bootp/tftp issue neeeeeed help plz

i find a solution (2 Replies)
Discussion started by: shady_2005
2 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 09:27 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy