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-clean
GO-CLEAN(1) General Commands Manual GO-CLEAN(1)
NAME
go - tool for managing Go source code
SYNOPSIS
go clean [-i] [-r] [-n] [-x] [ packages ]
DESCRIPTION
Clean removes object files from package source directories. The go command builds most objects in a temporary directory, so go clean is
mainly concerned with object files left by other tools or by manual invocations of go build.
Specifically, clean removes the following files from each of the source directories corresponding to the import paths:
_obj/ old object directory, left from Makefiles
_test/ old test directory, left from Makefiles
_testmain.go
old gotest file, left from Makefiles
test.out
old test log, left from Makefiles
build.out
old test log, left from Makefiles
*.[568ao]
object files, left from Makefiles
DIR(.exe)
from go build
DIR.test(.exe)
from go test -c
MAINFILE(.exe)
from go build MAINFILE.go
In the list, DIR represents the final path element of the directory, and MAINFILE is the base name of any Go source file in the directory
that is not included when building the package.
OPTIONS
-i The -i flag causes clean to remove the corresponding installed archive or binary (what 'go install' would create).
-n The -n flag causes clean to print the remove commands it would execute, but not run them.
-r The -r flag causes clean to be applied recursively to all the dependencies of the packages named by the import paths.
-x The -x flag causes clean to print remove commands as it executes them.
For more about specifying packages, see go-packages(7).
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-CLEAN(1)