Archive for the 'FreeBSD' Category

Using ssh-agent in an elegant way

Logging into many a remote hosts and, or servers from my desktop and, or notebook is a routine job for me, hence I extensively use ssh and ssh-agent every day. I wanted to use the same ssh-agent instance from each and every terminal whether I’m on a virtual console or in front of x-window desktop running a terminal emulator. I created a tiny bash script say ssh-agent.sh in the /etc/profile.d as follows:

SSH_ENV="$HOME/.ssh/ssh-agent.env"

function start_agent {
    /usr/bin/ssh-agent |sed 's/^echo/#echo/' >"$SSH_ENV"
    chmod 600 "$SSH_ENV"
    . "$SSH_ENV" >/dev/null
}

# Source SSH settings, if applicable
if [ -f "$SSH_ENV" ]; then
    . "$SSH_ENV" >/dev/null
    ps -e |grep ^$SSH_AGENT_PID |grep -q ssh-agent$ || start_agent
else
    start_agent
fi

And the life now seems quite easier since then :)

Available distributions

I have a small collection of various CD’s and, or DVD’s for distributions of Linux and, or Unix which I would love to share with you. Please bring some extra blanks and get the media burned for your favorite distro only at the cost of a smile :)

I shall arrange to download other such images also, provided these are freely and legally available somewhere via Internet.

The FreeBSD ports I maintain or test

I proudly, have been maintaining and, or submitting a few ports for FreeBSD project since December 2006. The authorized volunteers however, take time to approve and, or commit new and, or updated ports; may be due to the workload they handle.

Hence, I have created a public repository for sharing these with all those of you, who either are interested to use or help me in testing these ports, even before these are committed to the real ports tree. Please feel free to download, test and, or report any bugs; a feedback of yours though not mandatory, shall highly be appreciated.

After downloading the requisite and, or suggested <whatever>.shar.gz file(s) for a port, to extract and, or install, all you need to do is, as root repeat the following for the *.shar.gz files:

# zcat <whatever>.shar.gz |sh

or for the <whatever>.patch.gz file(s):

# zcat <whatever>.patch.gz |patch -d/ -p1

Now, visit the main ports’ directory and perform:

# cd /usr/ports/<category>/<port>
# make install clean

That’s all, and you have done it!

The YATE has been ported to FreeBSD

An updated YATE port is available for FreeBSD. I hope it will also build fine on all BSD variants; haven’t tested. Please report your success and, or failure on other variants.

WWW: http://YATE.null.ro

To install/upgrade the ports download:

To extract, build and install:

# zcat <path>/yate-devel.shar.gz |sh
# zcat <path>/spandsp-devel.patch.gz |patch -d/ -p1
# portupgrade -f -o comms/spandsp-devel spandsp
# cd /usr/ports/net/yate-devel
# make install 

or

# make package

Before running csup and, or cvsup do create and, or update a refuse file:

# cat <<EOT >>/var/db/sup/refuse
ports/comms/spandsp-devel*
ports/net/yate-devel*
EOT

A yate ports collection for FreeBSD created by Alex Rodin ‘alex DOT rodin AT gmail DOT com’ is also/already available in the yate mailing list archive. Kindly note, that this one is different and also includes, though small, but the following enhancements over the latest CVS head:

  • Added support to run daemon under NON-root uid and, or gid on Unix systems.
  • Module loading and, or initialization messages moved to highest debug level.
  • Added support for aliases in regfile; the ‘alias->number’ are now aliases.
  • Added support to show ip.add.re.ss:port for connections in rmanager module.
  • Updated and, or up-to-date manpages, README and INSTALL files.

I’m not that expert in SIP, H.323, IAX2, Jingle and other such protocols and, or PSTN technology, so I request you to please post your relevant and, or technical questions to Null Team only; the creators of Yate at http://yate.null.ro/pmwiki/index.php?n=Main.MailList

[ALERT] Google AdSense is a fraud

In its current incarnation the Google AdSense is definitely a fraud. IMHO, thousands if not millions of AdSense publishers have already been robbed by invalid click Google excuses till date. As and when an AdSense publisher site and, or blog starts earning a good amount or starts attracting visitors, the Google AdSense people usually come up with this standard excuse:

It has come to our attention that invalid clicks and/or impressions have been generated on the Google ads on your site(s). We have herefore disabled your Google AdSense account. Please understand that this was a necessary step to protect the interest of the AdWords advertisers.

And publishers disabled for invalid click activity are not allowed further participation in AdSense and do not receive any further payments. The earnings on your account will be properly returned to the affected advertisers, who knows?

On searching even at Google itself, you too may find:

Google AdSense—a scam?
How to Bring Google AdSense Down
Nonsense with Google’s AdSense?
Google, p2pnet: AdSense saga
Google’s adsense a Fraud
Google Adsense is a fraud
Wikipedia: AdSense#criticism

Google gets gruff over click fraud
Google Sued for AdSense Fraud
Obviously google adsense is a fraud
Don’t Get Caught With Google Adsense Click Fraud
Google Files Click-Fraud Suit
AdSense Has A Scam Side

Neither the publishers have enough of the skills and, or expertise to verify who has created the said invalid clicks nor the Google is fair enough to show you the records. Moreover, it is not that easy a job to prove that the records have not been doctored. I’m not lawyer, but I feel that the Google Adsense business in it present form is not transparent and they people are cheating their AdSense publishers in violation of common law.

I therefore, request all AdSense publishers to stop displaying Google advertisements with immediate effect and ask these Google people for some transparent method such as pay per thousand impressions excluding all page views from local network and, or the server itself.




Close
E-mail It