Free name change software for linux

DNS name parser is a Java utility library for parsing dns names, ip and hw addresses.

Synopsis

import su.netdb.parser.*;

Parser parser = new Parser();

Hashtable result = parser.parse(str);

System.out.println("string: "+result.get("string"));
System.out.println("hw: "+result.get("hw"));
System.out.println("name: "+result.get("name"));
System.out.println("domain: "+result.get("domain"));
System.out.println("ip_low: "+result.get("ip_low"));
System.out.println("ip_high: "+result.get("ip_high"));

"DNS name parser" is an utility library created to be used in a search application. Given a single input field its function is to differentiate between several types of possible input strings. Namely if it a dns name, IP address (exact, ip range or ip with wildcards) or hardware address. The result of the parsing is a Hashtable with possible keys "string", "hw", "name", "domain", "ip_low" and "ip_high".

Network Device Change Control (NDCC) is a system that monitors and records changes to the configurations of network equipment.

Network Device Change Control can store configuration snapshots for any text-based configs. It has been used to store configurations from Unix and Linux systems, Cisco routers, switches, load balancers, and firewalls, Foundry, NetScreen, Juniper, NetScaler, and others.

It only took a while to realize that router changes should be tracked. I rewrote the system to give a current and once-back system of configurations. Since I was using diff, I decided to leave the diff information in the system. Those diffs were emailed to a group so everyone knew when something was changed, along with what was changed.

Some time later, a bank needed to track configuration files, and the system was upgraded for use within a database. The first implementation was using perl as a CGI script against a PostgreSQL database. The company wanted many changes made for their auditing needs and most of those changes enhanced NDCC. Upgrades to their environment moved things to PHP and MySQL, and the system was rewritten for that environment and the old perl code has since been lost.

Workspace Name Applet is a Gnome panel applet to display and edit the name of the current workspace.

DBD::ODBC::Changes is a Perl module with logs of significant changes to the DBD::ODBC.

Not A Commander is yet another file manager modeled after the Norton Commander. Good integration with the command line is the primary goal.
This project is using the technology of Natural Stupidity for development: first get something working at all, then gradually improve it. My primary targets are the features that I personally would use. The features that I wont use anyway are not planned to be implemented at all (though if someone would contribute an implementation I would gladly accept it - as long as it does not break any of the things that I use).
Build
Run `make. That should build all the binary parts. The X11 headers are required for build. You may need to modify the Makefile for peculiarities of your particular system (directory names, libraries etc.).
Installation
Run `make install. By default the `nac binary is instaled into /usr/local/bin and the rest of files is installed into /usr/local/lib/nac (which is referred further as "the NAC directory").
These directory names can be changed in the Makefile. If the configuration file nac.sysrc was present in the NAC directory before installation, it will be moved into nac.sysrc.old.
Configuration
The default configuration of NAC can be changed with rc files. There are two rc files:
per system - nac.sysrc in the NAC directory per user - .nacrc in the users home directory
These files are common Tcl scripts that can be used to change the tunable values. NAC first sets the built-in values, then loads the system-wide rc file (if present), then loads the users rc file (if present). Thus the system-wide script can examine the built-in values and modify them was neccessary, and the users script can do the same thing with the result
of the system-wide script.
Be careful with the syntax, in case of an error in the rc scripts NAC wont start.
The list of the supported tunables and their values can be found at the top of tune.tcl. For now (the alpha phase of development) its expected to be quite liquid and change between snapshot releases. Probably some sort of versioning will be added after it stabilizes.
The sample system rc file included in a release contains only one setting - the name of font to use (most probably you dont have the font "koi9x16" which is the built-in default).
The default initial size of the window is defined by panel dimensions, variables named set panel:filespercolumn (number of rows in panels), panel:ncolumns (number of columns in panels), panel:columnwidth (width of a column in dots). The internal xterm is automatically resized to fit these dimensions. Alternative size in pixels or xterm characters can be
selected with command line options.
Enhancements:
- Various bugs were fixed and workarounds were included for bugs in glibc and Tk.

NanobloggerComments is a PHP/MySQL-based comment system for Nanoblogger.

Installation:

Login to mysql as user root and:

create database sessions; grant all privileges on sessions.* to session@localhost
identified by PASSWORD;

Chose and remember your own password

Create database structure:
mysql -u session -p sessions < db.sql

Now modify your blog.conf

First add new variables - BLOG_ADMIN and DB_PASS, will be used by install script. (If You have also changed database name or user edit after running install script consts.php to reflect this change)

BLOG_URL_ACTION="cmt.php?article=" (remeber that $BASE_URL is added by nb -
at least 3.2.3)

In templates dir remove HTML comments (< !-- -- >) from entry.htm and permalink_entry.htm. You also have to change URL in those two templates to

< a href="${BASE_URL}${BLOG_URL_ACTION}/$permalink_file" >
< script >checkPosts("$permalink_file");< /script > < /a >

And after every directive in templates (category_archive.htm,
main_index.htm, makepage.htm, month_archive.htm, permalink.htm ) add:

< script language="JavaScript"
src="${BASE_URL}${BLOG_URL_ACTION}&act=showjs"
type="text/javascript" > < /script >

Now install whole thing :
./install YOUR_WWW_BLOG_DIRECTORY

Script will check for blog.conf in current dir and if not found will check BLOG_CONF environment variable and target (install) directory. From this file will take all needed data to generate all headers, etc.

Now update Your blog. In my environment it is done through:

nb -u all && nb -P

Easy various links manager or Everest Linux Links Manager (evlinks) is a network manager and config toolkit that aims to replace network services and networkmanager.

Tthe design of evlinks:

1. use mac address as config file names to avoid interface name change.

2. multi profile support, for example, you can have a setting for Office and another setting for home.

3. never display info such as "eth0/wlan0/ath0" to users. what is the meaning of this strange words for normal user?

4. coupled loosely, if any component of evlinks crash or can not work, others works very well.

5. policy support: for example, whether start wired at booting time,whether start wireless at booting time,offline or online, if wired line unpluged, shall we switch to wireless?

The components of evlinks:

1. evlinkslo/evlinksboot:

run at system booting.
enable loopback and other interfaces according to config file.

2. evlinksiw, wireless config tool

3. evlinkswireless, a wrapper for evlinksiw to handle multiple wireless adapters. if you only have one wireless adapter, it will start evlinksiw directly.

4. evlinksw, wired config tool, support multiple profiles.

5. evlinkswired, same as evlinkswireless, a wrapper for evlinksw to handle multiple wired adapter.

6. evlinksmonitor, a hal client to monitor the adapter changes. since it use hal, then we can catch the signal when new adapter plugged and removed.

7. evlinkstraffic, network traffic monitor. used in evlinksmonitor and evlinkspppoe.

8. evlinkspppoe, PPPoE clients, used to connect ADSL(no PPPoA support)

9. evlinksdispatcher and evlinksrun. dirty code to help normal user run it easily.that is to say, normal user use evlinksrun to call evlinks utils, they all run as super user. it is not a good design, also had security problem, need change later.