03-17-2020
All is done, for the initial migrations except for "vb thanks" to "discourse likes".
(of course the discourse site is behind the vb site as far as the most recent posts....)
It's looking good, but I would like to get the "vb thanks" to "discourse likes" working.
This User Gave Thanks to Neo For This Post:
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. 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
6. What is on Your Mind?
OK.
Like we all do, we learn a lot from tests, test migrations, and so forth.
Today, I started from scratch on test migration 2, armed with a lot more knowledge,
The main differences are as follows:
Installed discourse plugin ruby-bbcode-to-md before starting the install
Modified... (30 Replies)
Discussion started by: Neo
30 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
jfs_fscklog
jfs_fscklog(8) Extract/Display JFS fsck Log jfs_fscklog(8)
NAME
jfs_fscklog - extract a JFS fsck service log into a file and/or format and display the extracted file
SYNOPSIS
jfs_fscklog [ -d ] [ -e device ] [ -f output.file ] [ -p ] [ -V ]
DESCRIPTION
jfs_fscklog with option -e device extracts the contents of either the most recent or immediately prior (specified with option -p) JFS fsck
service log from the specified device, and writes the output to a file. The file name may be specified with the -f option, or the default
file name is <pwd>fscklog.new. If the -p option is used, the default file name is <pwd>fscklog.old.
jfs_fscklog with option -d formats and displays the contents of the extracted file.
jfs_fscklog with options -d and -e device extracts and displays the JFS fsck service log.
OPTIONS
-d Format and display a previously extracted JFS fsck service log.
-e device
Extract the JFS fsck service log from device and store it in a file. (device is the special file name corresponding to the actual
device from which the fsck log will be extracted (e.g. /dev/hdb1 )).
-f file.name
Specify the file name, overriding the default file name. When used with -e device, file.name specifies the name of the file into
which the JFS fsck log will be extracted. When used with -d, file.name specifies the name of the extracted file whose contents will
be formatted and displayed.
file.name must be 127 characters or less in length.
file.name will be created in the present working directory unless it is fully qualified.
-p Extract the prior log (as opposed to the most recent log).
-V Print version information and exit (regardless of any other chosen options).
EXAMPLES
Extract the most recent JFS fsck log on /dev/hda5 into <pwd>fscklog.new:
jfs_fscklog -e /dev/hda5
Extract the most recent JFS fsck log on /dev/hdb3 into /temp/l9651107.log:
jfs_fscklog -e /dev/hdb3 -f /temp/l9651107.log
Display the JFS fsck log that was extracted into /temp/l9651107.log:
jfs_fscklog -d -f /temp/l9651107.log
Extract and display the previous JFS fsck log from /dev/hda8:
jfs_fscklog -e /dev/hda8 -d -p
REPORTING BUGS
If you find a bug in JFS or jfs_fscklog, please report it via the bug tracking system ("Report Bugs" section) of the JFS project web site:
http://jfs.sourceforge.net/
Please send as much pertinent information as possible, including any jfs_fscklog error messages and the complete output of running jfs_fsck
with the -v option on the JFS device.
SEE ALSO
jfs_fsck(8), jfs_mkfs(8), jfs_tune(8), jfs_logdump(8), jfs_debugfs(8)
AUTHOR
Barry Arndt (barndt@us.ibm.com)
jfs_fscklog is maintained by IBM.
See the JFS project web site for more details:
http://jfs.sourceforge.net/
October 28, 2002 jfs_fscklog(8)