The error says something like this “Request exceeded the limit of 10 internal redirects due to probable configuration error. Use ‘LimitInternalRecursion’ to increase the limit if necessary. Use ‘LogLevel debug’ to get a backtrace.”

And that is exactly what I did, I used the LogLevel debug and this is what I was getting on my apache error log:

[Wed Mar 21 12:29:50 2012] [debug] core.c(3063): [client xxx.xxx.xxx] r->uri = /index.php
[Wed Mar 21 12:29:50 2012] [debug] core.c(3069): [client xxx.xxx.xxx] redirected from r->uri = /index.php
[Wed Mar 21 12:29:50 2012] [debug] core.c(3069): [client xxx.xxx.xxx] redirected from r->uri = /index.php
[Wed Mar 21 12:29:50 2012] [debug] core.c(3069): [client xxx.xxx.xxx] redirected from r->uri = /index.php
[Wed Mar 21 12:29:50 2012] [debug] core.c(3069): [client xxx.xxx.xxx] redirected from r->uri = /index.php
[Wed Mar 21 12:29:50 2012] [debug] core.c(3069): [client xxx.xxx.xxx] redirected from r->uri = /index.php
[Wed Mar 21 12:29:50 2012] [debug] core.c(3069): [client xxx.xxx.xxx] redirected from r->uri = /index.php
[Wed Mar 21 12:29:50 2012] [debug] core.c(3069): [client xxx.xxx.xxx] redirected from r->uri = /index.php
[Wed Mar 21 12:29:50 2012] [debug] core.c(3069): [client xxx.xxx.xxx] redirected from r->uri = /index.php
[Wed Mar 21 12:29:50 2012] [debug] core.c(3069): [client xxx.xxx.xxx] redirected from r->uri = /index.php
[Wed Mar 21 12:29:50 2012] [debug] core.c(3069): [client xxx.xxx.xxx] redirected from r->uri = /login

According to the solutions I found on discussion forums, the problem was usually associated with the MultViews option not being disabled. Your virtual host configuration should be something like this:

   <VirtualHost *:80>
ServerName www.yourhost.com
DocumentRoot /somewhere/public    # <– be sure to point to ‘public’!
<Directory /somewhere/public>
AllowOverride all              # <– relax Apache security settings
Options -MultiViews            # <– MultiViews must be turned off
</Directory>
</VirtualHost>

Another solution I found was to create an .htaccess file at the root of apache, and add the following content to it:

RewriteBase /

After viewing this, I searched for a .htaccess file, and to my suprise I actually had one pointing to my wordpress directory. I had done this before creating a virtual host. After removing the file .htaccess my problem was resolved.

I don’t expect this to be a solution to your problem, but at least it can give you some hints like it gave me.

Good luck!

Fidel.


sudo apt-get install ntfs-config


This will in turn install ntfs-3g, and any other dependencies. After this, you should have your problem resolved. You should pay attention to the command used. You should use “apt-get” as opposed to “aptitude”. “aptitude” seems to have some sort of bug.

Hope that has helped you sort out the writing to ntfs issue.

All the best,

Fidel.

Regards,

Fidel.

If you are looking for a quick and dirty way you can do it as described in http://goodbadtech.com/2009/05/13/ruby-on-rails-import-csv-data-into-database/, which I will elaborate below:

require ‘csv’
CSV.open(‘your-csv-file.csv’, ‘r’).each do |row|
YourModel.create(:field1 => row[0], :field2 => row[1])
end

Here your-csv-file.csv is the name of the csv file that contains the data you wish to import. YourModel is the name of your model. For instance, if you are importing data into your Language model, then YourModel is Language. field1 and field2 are the names of your model’s fields, which are not required to have an order. row[0] and row[1] are the items found according to their position in the CSV line.

What this code will do is go throug each record (line) found in the CSV file and create an instance of that model in the database, using ActiveRecord. In order for this code to work you will need to fire up the Rails console like this:

rails console (if you are using Rails 3 or above)
ruby script/console (if you are using Rails 2.xxx or below)

And that’s basically it. This a quick and dirty way to import data into your Rails database using CSV. If you want a more complete solution, where you will be able to upload data from your browser, then have a look at this article http://goodbadtech.com/2009/05/13/ruby-on-rails-import-csv-data-into-database/

I am preparing another article that will show you how to import data from an Excel or ODF file.

Until then, hope this one was useful.

This article covers the implementation of a compiler using the SableCC framework and the Java programming language. The language we are going to implement is a subset of Pascal that we will call SmallPascal. This is a very small language that can be used as a calculator. In other words, the language supports the integer data type, reading from standard input and writing to the standard output. For those that come from a Microsoft Windows background, the standard input in Unix based operating systems is normally represented by the keyboard, and the standard output by the screen. In other words, our compiler will work in the command line and will read data from the keyboard and display text in the screen.

The SableCC framework is a piece of software that simplifies compiler writing. It does include support for writing lexical analysers (or lexers) and syntactic analysers (or parsers). The parser generates a tree that represents your grammar. This tree can then be manipulated by tree walkers known as visitors (for more information about this, please read Gagnon (1998)), in order to create a semantic analyser, code generator and code optimizer. In this article we will only cover the semantic analyser and the code generator. In future articles I will demonstrate more advanced compiler writing techniques.

Now that we know what this article is all about, let’s define the steps required to implement our compiler. Gagnon (1998) defines the following 5 steps one must follow in order to implement our compiler:

1. We create a SableCC specification file containing the lexical definitions and the grammar for the language being designed.
2. After creating the SableCC specification file, we generate the framework by launching SableCC on the specification file.
3. Once the code is generated, we generate the working classes. This is the only code we have to write in Java^TM. It is in this step that we write the semantic analyser, the code generator, and possibly the code optimizer. In the case of an interpreter, we write a single class. These working classes may be subclasses of one of the classes from the analysis subfolder generated by SableCC in the previous step.
4. Following our tree walkers, we need to create our main class, known as the driver class of the compiler. It is used to activate the lexer, parser and working classes.
5. Finally, after implementing the driver class, we compile the compiler with a Java^TM compiler.

Once the steps are described, we are now going to follow one by one in turn, in the following sections.

I have finally found the time to bring my site back up. I was initially implementing a website using Ruby on Rails, but later decided on using something that was already stable and flexible for my own site.

I will start by bringing up all the tutorials that were found in the old site, and will soon start posting new articles in areas I am acquainted with.

I hope that you enjoy reading my articles and hope to hear from you so that I can improve the site to make your reading more pleasurable.

Thanks!

Fidel.