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
filezilla
filezilla(1) FileZilla Manual filezilla(1)
NAME
FileZilla - FTP client
SYNOPSIS
filezilla
filezilla [-l <logontype>] <FTP URL>
filezilla -h|-s|-v
filezilla -c <site>
DESCRIPTION
FileZilla is a powerful client for plain FTP, FTP over SSL/TLS (FTPS) and the SSH File Transfer Protocol (SFTP).
OPTIONS
-c <site>, --site <site>
Connect to the given site from the Site Manager. Site has to be given as complete path, with a slash as separation character. Any
slash or backslash that is part of a segment has to be escaped with a backslash. Path has to be prefixed with 0 for user defined
entries or 1 for default entries. Site path may not contain double quotation marks.
Example: filezilla -c 0/foo/bar/sl/ash connects to the user site sl/ash in the site directory foo/bar
May not be used together with -s nor with URL parameter.
-h, --help
Displays a help dialog listing these commandline options.
-l <logontype>, --logontype <logontype>
Set a special logontype, can only be used in combination with a FTP URL as argument.
Logontype has to be either ask or interactive. If -l isn't given, the normal logontype is used.
-s, --sitemanager
Start with Site Manager opened. May not be used together with -c nor with URL parameter.
-v, --version
Display version number of FileZilla.
ENVIRONMENT
The FZ_DATADIR environment variable can be used to specify the directory containing FileZilla's data files.
SUPPORT
Please visit http://filezilla-project.org/ for further information. Report bugs only if you are using the latest version available from the
FileZilla website.
COPYRIGHT
Copyright (C) 2004-2010 Tim Kosse
FileZilla is distributed under the terms of the GNU General Public License version 2 or later.
SEE ALSO
fzdefaults.xml(5)
April 2008 filezilla(1)