Sponsored Content
Operating Systems Solaris Flash Archives - A little bit of help :-) Post 302358382 by sbk1972 on Friday 2nd of October 2009 10:51:58 AM
Old 10-02-2009
Thanks for the reply. Do you use the hostname or the ip address ?? How does the install know about default routers / ip address / netmasks etc etc ?? Or do the previous install steps ask these questions, so the server is aware of the network etc etc ?

Also, just got an email telling me Ive got an infraction due to no code tags ! Amazing. What are code tags ?

SBK
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Jumpstart and Flash Archives

Ladies and Gentlemen: I am short on time and need to get up to speed fast on the use of flash archives. I am very familiar with Jumpstart and have used it successfully for the past 5 years. The current project I am working on requires optimization of time and speed when deploying systems which is... (0 Replies)
Discussion started by: rambo15
0 Replies

2. Solaris

Solaris Jumpstart and Flash Archives

Ladies and Gentlemen: I am short on time and need to get up to speed fast on the use of flash archives. I am very familiar with Jumpstart and have used it successfully for the past 5 years. The current project I am working on requires optimization of time and speed when deploying systems which is... (4 Replies)
Discussion started by: rambo15
4 Replies

3. UNIX for Dummies Questions & Answers

flash archives

HI, are you supposed to run flarcreate in multi user mode? or should you do it in single user? (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies

4. Solaris

bootable X86 dvd and flash archives

I have created a bootable DVD for X86 using a flash archive, the problem is that I have to specify the location at the beginning of the install. I have edited the any_machine profile under ./jumpstart_sample to contain the following install_type flash_install archive_location ... (4 Replies)
Discussion started by: eeisken
4 Replies

5. Solaris

zfs and flash archives

i had a situation where an app i was running just didn't have enough resources on a proliant dl365 (running sol10x86). so i ended up building out a dl385g2. the dl365 had zfs root file system which was managing the whole disk (smart array taking the raid 1+0). anyway, i figured i could migrate the... (2 Replies)
Discussion started by: pupp
2 Replies

6. UNIX for Dummies Questions & Answers

Flash causes 64-bit Ubuntu to crash

I've been running 64-bit Ubuntu for about 2 years now, but a few days ago it developed serious problems. Whenever I would load a Flash page* the computer would crash... well, sort of. The screen would go blank immediately, eventually causing the monitor to give the "no video detected" message. ... (0 Replies)
Discussion started by: CRGreathouse
0 Replies

7. Ubuntu

Flash causes 64-bit Ubuntu to crash

I've been running 64-bit Ubuntu for about 2 years now, but a few days ago it developed serious problems. Whenever I would load a Flash page* the computer would crash... well, sort of. The screen would go blank immediately, eventually causing the monitor to give the "no video detected" message. The... (2 Replies)
Discussion started by: CRGreathouse
2 Replies

8. Shell Programming and Scripting

How to handle 64 bit arithmetic operation at 32 bit compiled perl interpreter?H

Hi, Here is the issue. From the program snippet I have Base: 0x1800000000, Size: 0x3FFE7FFFFFFFF which are of 40 and 56 bits. SO I used use bignum to do the math but summing them up I always failed having correct result. perl interpreter info, perl, v5.8.8 built for... (0 Replies)
Discussion started by: rrd1986
0 Replies
GO-BUILD(1)						      General Commands Manual						       GO-BUILD(1)

NAME
go - tool for managing Go source code SYNOPSIS
go build [-o output] [ build flags ] [ packages ] DESCRIPTION
Build compiles the packages named by the import paths, along with their dependencies, but it does not install the results. If the arguments are a list of .go files, build treats them as a list of source files specifying a single package. When the command line specifies a single main package, build writes the resulting executable to output. Otherwise build compiles the pack- ages but discards the results, serving only as a check that the packages can be built. The -o flag specifies the output file name. If not specified, the name is packagename.a (for a non-main package) or the base name of the first source file (for a main package). OPTIONS
The build flags are shared by the build, install, run, and test commands: -a force rebuilding of packages that are already up-to-date. -n print the commands but do not run them. -p n the number of builds that can be run in parallel. The default is the number of CPUs available. -v print the names of packages as they are compiled. -work print the name of the temporary work directory and do not delete it when exiting. -x print the commands. -compiler name name of compiler to use, as in runtime.Compiler (gccgo or gc) -gccgoflags 'arg list' arguments to pass on each gccgo compiler/linker invocation -gcflags 'arg list' arguments to pass on each 5g, 6g, or 8g compiler invocation -ldflags 'flag list' arguments to pass on each 5l, 6l, or 8l linker invocation -tags 'tag list' a list of build tags to consider satisfied during the build. See the documentation for the go/build package for more information about build tags. For more about specifying packages, see go-packages(7). For more about where packages and binaries are installed, see go-gopath(1). SEE ALSO
go-install(1), go-get(1), go-clean(1). AUTHOR
This manual page was written by Michael Stapelberg <stapelberg@debian.org>, for the Debian project (and may be used by others). 2012-05-13 GO-BUILD(1)
All times are GMT -4. The time now is 02:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy