03-24-2020
On another note:
I have had a few people comment about converting new site to www.unix.com versus community.unix.com, so let me remind everyone:
This site has over 200K man pages and none of the man pages migrate to the new forum (anytime soon, we may write a plugin for this sometime in the future, however).
So, this site has a lot of reference material which is very important, including man pages and code.
In some instance, the migration of legacy posts with code from here to discourse has results in instances of "code mangling" where, for example, the original vB4 to Discourse migration script changed new lines chars "\n" to hard line breaks in code fragements.
Our moderator (and Poster of the Year 2019 as well), Scrutinizer is working on perfecting this Ruby script and when he is done; we will test this on a staging site and then update all the posts on the new site.
Even when the new site reaches "perfection" (or 99.9..., whatever that means), this site has a tremendous amount of important reference material (man pages, original code, etc).
So, eventually we will turn this site into a reference site and keep the reference site available. However, this "conversion to a reference site" is going to happen slower than we originally thought because of some parsing errors we found (we can all thank Scrutinizer for this, looking carefully at code) in the original Discourse Ruby vbulletin.rb script.
Frankly, after working 14 days in a row, 12 hours a day, on this migration, I was disappointed to learn of the errors in the original vbulletin.rb script; but I'm glad we found them and we all owe a debt of gratitude to Scrutinizer for working on modifying the preprocessing routine of the original Discourse vbulletin.rb migration script.
Thank you Scrutinizer!!
Regarding updating the posts:
After we have fully tested the new preprocessing routine on a staging site, we will update the posts on the discourse site. Discourse keeps both the raw (preprocessed) and cooked (post-processed) text for each post in the DB. We will update the raw posts and recook them when it is time to do the rebaking.
Because of this hard line break issue for the "\n" char in code fragments, Scrutinizer is looking at more enhancements to preprocessing at the same time.
5 More Discussions You Might Find Interesting
1. Web Development
Hi,
I am fairly new to unix so please go easy on me.. I have a VPS on which I would like to setup a development and live web site environment and can't seem to work out what is the best technique for doing so.
I would like to be able to mirror the live site and have a "check out" and... (0 Replies)
Discussion started by: ciantrius
0 Replies
2. IP Networking
Hi,
I am trying to establish vpn between my linux server and cisco asa at client side.
I installed openswan on my cent os.
Linux Server
eth0 - 182.2.29.10
Gateway - 182.2.29.1
eth1 - 192.9.200.75
I have simple IPtables Like
WAN="eth0"
LAN="eth1" (0 Replies)
Discussion started by: ashokvpp
0 Replies
3. IP Networking
Q: "Does Cisco 1921 router support,, act as an endpoint for, site to site VPNs using IPSec? If so, how many? "
A: If you get the Cisco 1921/k9 with the security services bundle then it will have built in security features. Cisco, typically includes IP Sec tunnels I believe as part of that... (0 Replies)
Discussion started by: Ayaerlee
0 Replies
4. IP Networking
Hi @all,
I try to connect 2 LANs with IPSec/Openswan
LAN 1: 192.168.0.0/24
LAN 2: 192.168.1.0/24
This is my Config:
conn HomeVPN # # Left security gateway, subnet behind it, nexthop toward right. left=192.168.1.29 ... (1 Reply)
Discussion started by: bahnhasser83
1 Replies
5. What is on Your Mind?
Update: UserCP Screeching Frog 0.7641 - Changed Live Chat to Live Updates
In this version of the UserCP, I have changed "Live Chat" to "Live Updates" by disabling the ability to post in the "live chat" area and changed the name to "Live Updates"
The reason for this change is that experienced... (6 Replies)
Discussion started by: Neo
6 Replies
LEARN ABOUT DEBIAN
blaze-list
BLAZE-LIST(1) BlazeBlogger Documentation BLAZE-LIST(1)
NAME
blaze-list - lists blog posts or pages in the BlazeBlogger repository
SYNOPSIS
blaze-list [-cpqrsCPSV] [-b directory] [-I id] [-a author] [-t title] [-T tag] [-d day] [-m month] [-y year] [-n number]
blaze-list -h|-v
DESCRIPTION
blaze-list lists existing blog posts or pages in the BlazeBlogger repository. Additionally, it can also display basic repository
statistics.
OPTIONS
-b directory, --blogdir directory
Allows you to specify a directory in which the BlazeBlogger repository is placed. The default option is a current working directory.
-I id, --id id
Allows you to display a single blog post or a page with the specified id.
-a author, --author author
Allows you to list blog posts or pages by the selected author.
-t title, --title title
Allows you to list blog posts or pages with matching title.
-T tag, --tag tag
Allows you to list blog posts or pages with matching tag.
-d day, --day day
Allows you to list blog posts or pages from the specified day of a month. The value has to be in the "DD" form.
-m month, --month month
Allows you to list blog posts or pages from the specified month. The value has to be in the "MM" form.
-y year, --year year
Allows you to list blog posts or pages from the specified year. The value has to be in the "YYYY" form.
-n number, --number number
Allows you to specify a number of blog posts or pages to be listed.
-p, --page
Tells blaze-list to list pages.
-P, --post
Tells blaze-list to list blog posts. This is the default option.
-S, --stats
Tells blaze-list to display statistics.
-s, --short
Tells blaze-list to display each blog post or page information on a single line.
-r, --reverse
Tells blaze-list to display blog posts or pages in reverse order.
-c, --color
Enables colored output. When supplied, this option overrides the relevant configuration option.
-C, --no-color
Disables colored output. When supplied, this option overrides the relevant configuration option.
-q, --quiet
Disables displaying of unnecessary messages.
-V, --verbose
Enables displaying of all messages. This is the default option.
-h, --help
Displays usage information and exits.
-v, --version
Displays version information and exits.
EXAMPLE USAGE
List all blog post:
~]$ blaze-list
ID: 11 | 2010-07-05 | Jaromir Hradilek
Title: Join #blazeblogger on IRC
Tags: announcement
ID: 10 | 2009-12-16 | Jaromir Hradilek
Title: Debian and Fedora Packages
Tags: announcement
etc.
List all blog post in reverse order:
~]$ blaze-list -r
ID: 1 | 2009-02-10 | Jaromir Hradilek
Title: BlazeBlogger 0.7.0
Tags: release
ID: 2 | 2009-02-11 | Jaromir Hradilek
Title: BlazeBlogger 0.7.1
Tags: release
etc.
List all pages:
~]$ blaze-list -p
ID: 5 | 2009-02-10 | Jaromir Hradilek
Title: Downloads
ID: 4 | 2009-02-10 | Jaromir Hradilek
Title: Themes
etc.
List each blog post on a single line:
~]$ blaze-list -s
ID: 11 | 2010-07-05 | Join #blazeblogger on IRC
ID: 10 | 2009-12-16 | Debian and Fedora Packages
etc.
Display a short version of blog statistics:
~]$ blaze-list -Ss
There is a total number of 11 blog posts and 5 pages in the repository.
SEE ALSO
blaze-config(1), blaze-add(1)
BUGS
To report a bug or to send a patch, please, add a new issue to the bug tracker at <http://code.google.com/p/blazeblogger/issues/>, or visit
the discussion group at <http://groups.google.com/group/blazeblogger/>.
COPYRIGHT
Copyright (C) 2009-2011 Jaromir Hradilek
This program is free software; see the source for copying conditions. It is distributed in the hope that it will be useful, but WITHOUT ANY
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Version 1.2.0 2012-03-05 BLAZE-LIST(1)