Just signed up so saying hi to the world - or at least those that are here anyways :o)
"Not all distributions have staff, some have "wheel" instead."
What does this mean?
When I type in "vlc" on terminal in Mandriva 2009 Free, I get a message that it cannot be played and that there's some segmentation fault.
It suggests me to try "cvlc".And it works.
What is Segmentation Fault?
One day when I tried another SIM card with the Huawei E220 modem that I told about in http://kerneltrap.org/node/17017, I got the following error message on bearerbox.log:
2009-04-11 08:19:59   DEBUG: AT2[eus_smsc]: --> AT+IFC=2,2^M 2009-04-11 08:20:00   DEBUG: AT2[eus_smsc]: <-- +CME ERROR: SIM failure 2009-04-11 08:20:00   ERROR: AT2[eus_smsc]: Generic error: +CME ERROR: SIM failure 2009-04-11 08:20:00   INFO: AT2[eus_smsc]: cannot enable hardware handshake
The other day when I was fiddling with JobScheduler (http://jobscheduler.sourceforge.net), I realized that my development machine's system clock lagged by about 8 seconds behind that of the server machine that hosted the JobScheduler because whenever I looked at my local machine's clock to setup a job to run at the next 10 seconds, the JobScheduler in the server machine failed to run the job due to expiration of the schedule (the JobScheduler used the server machine's system clock, of course). I had both machines running the same GNU/Linux distribution, which was Ubuntu 8.04 Desktop, and they were synchronized to ntp.ubuntu.com. But, upon encountering the lagging problem, I decided to synchronize my development machine's system clock to that of the server machine. However, I wanted the server machine to synchronize to ntp.ubuntu.com. It turned out that implementing such an idea was not easy.
One day after I had successfully set up a subversion mirror and kept it in sync with svnsync through svn+ssh protocol as described here: http://blog.codefront.net/2007/03/31/setting-up-svnsync-ed-mirrored-svn-..., I would like to have the sync happen automatically everytime there was a commit. Oh, the blog didn't mention anything about svn+ssh protocol, but it was easily done following the subversion manual itself. So, I coded post-commit and post-revprop-change hooks as described here: http://journal.paul.querna.org/articles/2006/09/14/using-svnsync. However, as Chu Yeow mentioned in his blog that he settled with cron to do the sync because the hooks method didn't work, it also didn't work for me. Both machines were using GNU/Linux Ubuntu 8.04 Desktop.
Just today I overwrote an important file accidentally. Fortunately, I had another terminal running `less' that had been reading the overwritten file up to the state just before it was overwritten (i.e., I read the file in another terminal with `less' and kept it open after I had overwritten the file). So, I wanted to save the content of the display buffer of `less' to a file. But, how?
My first-time experience using trac for reporting a bug was ended with a question: How do I find a ticket based on its number?
While googling for the right program to mirror an SVN repository, I came across this post: http://blog.codefront.net/2007/03/29/setting-up-svnsync-ed-mirrored-svn-....
The post is about tutorial on using svnsync, which is a very handy program available since SVN 1.4 to mirror an SVN repository. The first part is not so interesting but for one thing: checkinstall (http://asic-linux.com.mx/~izto/checkinstall/).
When crafting a complex SQL query (i.e., the query has at least one subquery), two things have to be kept in mind:
1. Reduce the search space
2. Do query on index
As a real example, last week I tuned a query that previously took about 45 minutes to complete.
Now it takes only 12 minutes, which is an improvement of 73%. Here goes the story.
I have used Slackware 10.2 since 2007 after I upgraded from Slackware 10.1.
What I didn't know was that Slackware 10.2 was shipped with a broken dhclient.
I have been all over Apple's support site and the techies from several sites with no help. I then posted my error message on Google and wound up on this site. I am not sure I am in the correct spot but will ask the question anyway.
LSE - Linux Security Engine
LSE is an open source security project for GNU/Linux (Kernel 2.6 series).
It employs a "white list" approach to allow/disallow program execution on your computer.
It's an easy way to prevent user running applications which can be malicious [virus, backdoor, rootkit, ...] or simply unwanted.
I have already covered phishing in few of my earlier posts here:
I just received an email from 'email@example.com' indicating me that
Attention! Your AXIS Online Banking Account has been violated!
Someone with IP Address 126.96.36.199 tried to access your personal account!
In accordance with Axis Online Banking User Agreement and to ensure that
your account has not been compromised, access to your account was limited.
Your account access will remain limited until this issue has been resolved.
Please follow the link below to resolve this problem:
With logo and all completely there... Sounds pretty official. The problem is, I don't have an Axis Bank account :-)
So I thought ofcourse this is phishing. This can immediately be found out by hovering your mouse over the link specified. Usually, the href tag points to the real phishers website, whereas the contents of the "a" tag is the string of your bank's website. It was confirmed this is certainly a phishing site.
Then I thought lets go where they are really pointing me to and see what is happening. As I clicked it, FireFox Phishing Protection kicked-in and informed me that this site is reported for phishing attacks. Now that was good! Protection from some real danger! I wonder what happens when you open the link in IE....
Anyway, this kind of phishing detection is black-listing based phishing detection. It works, as we just saw, but it doesn't work on zero-day attacks. For it to work, people have to report this site to be a phishing site. And there is a window, between the site coming up and people reporting that site. And the window is sufficient for the phishers to gain access to vital account information of many many innocent people.
That reminds me of a project guided by the Dreamz Group by Amey. The project had a browser plugin. They had come up with a bunch of rules or suspicions that you can detect on typical phished websites. If the rules/suspicions match, a warning is displayed. For example, what we did above by hovering the mouse pointer is one such rule. And solutions like these raise the bar quite a lot. I am not sure if there are any commercially available solutions for these. But there certainly should be some around.