03-14-2020
This is the end of test build 2 (and 3).
Now that I have most of the general bugs worked out; and I'm convinced this migration will work, I will setup another server and start new test build 4 from scratch.
Now waiting for DNS to sync / propagate to new server IP address.
Will start new thread for test build 4 soon.
7 More Discussions You Might Find Interesting
1. Web Development
Please note, this information was copied from vbseo.com, now showing a database error. This is posted for reference since vbSEO seems to be going out of business:
If you ever need to uninstall vBSEO , you can use the following instructions. Make sure you carefully follow each step.
Login... (37 Replies)
Discussion started by: Neo
37 Replies
2. Linux
Recently i found this for give to docker a "personal" ip
ip addr del 10.1.1.133/24 dev eth0
ip link add link eth0 dev eth0m type macvlan mode bridge
ip link set eth0m up
ip addr add 10.1.1.133/24 dev eth0m
route add default gw 10.1.1.1On container i did
... (0 Replies)
Discussion started by: Linusolaradm1
0 Replies
3. AIX
I'm New to AIX / VIOS
We're doing a FC switch cutover on an ibm device, connected via SAN.
How do I tell if one path to my remote disk is lost? (aix lvm)
How do I tell when my link is down on my HBA port?
Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
4. Shell Programming and Scripting
Actually I was facing the following issue while building my Yocto SDK on Docker container
sudo docker build --tag="akash/eclipse-che:6.5.0-1" --tag="akash/eclipse-che:latest" /home/akash/dockerimage.yocto.support/
Sending build context to Docker daemon 26.93MB
Step 1/5 : FROM eclipse/cpp_gcc
... (3 Replies)
Discussion started by: Akash BHardwaj
3 Replies
5. UNIX for Beginners Questions & Answers
I don't know why, but the rendering of my code mucks up the spacing and indentation, despite being correct in the original file. I'm having issues getting the following script to run (specifically the nested script at the end of the docker command near the end of the script; I think I'm not passing... (2 Replies)
Discussion started by: James Ray
2 Replies
6. Docker
Hello All,
I had recently learnt a bit of Docker(which provides containerization process).
Here are some of my learning points from it.
Let us start first with very basic question:
What is Docker:
Docker is a platform for sysadmins and developers to DEPLOY, DEVELOP and RUN applications ... (7 Replies)
Discussion started by: RavinderSingh13
7 Replies
7. What is on Your Mind?
Dear All,
After being active on the Node-RED forum for the last few weeks, I have been very impressed with Discourse, and my eyes have been opened.
https://www.discourse.org/
but not the paid /hosted offering, but using the open distribution:
https://github.com/discourse/discourse
... (52 Replies)
Discussion started by: Neo
52 Replies
LEARN ABOUT DEBIAN
go-build
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)