eCryptfs.org now serves as the project's official portal to numerous resources, including: information about the project, StackExchange questions and answers, mailing list archives, the Google Plus page, package download links for all major Linux OSes, pointers to the kernel and userspace source code repositories, support resources, documentation, and news.

The kernel sources continue to be hosted on git.kernel.org, and the user space sources and bugs hosted on Launchpad.net.  We are now using StackExchange.com for questions and answers rather than Launchpad.

A special thanks goes out to the original authors and developers of eCryptfs in the IBM Linux Technology Center Security Team, the Canonical Kernel and Security Team, Red Hat and beyond, as well as all of the contributors to eCryptfs over the last 7 years.  Gazzang commissioned the artwork and web design, and is sponsoring the web hosting of eCryptfs.org as a bit of a "thank you" to the eCryptfs community growing far and wide.  

Sources

• Dustin Kirkland's blog
• ecryptfs home page

Here's what's in web.xml :

the filter

    <filter-mapping>
        <filter-name>Auto Login Filter</filter-name>
        <url-pattern>/documents/*</url-pattern>
        <dispatcher>REQUEST</dispatcher>
        <dispatcher>FORWARD</dispatcher>
    </filter-mapping>

and the servlet

    <servlet-mapping>
        <servlet-name>Web Server Servlet</servlet-name>
        <url-pattern>/documents/*</url-pattern>
    </servlet-mapping>

my page was ( I'll explain later why the past ) served at http://myserver/documents (obviously this is not the real url) and in that page there was the document library portlet.

When I tried to click on a document the url that was called was http://myhost/documents/-/document_library/view/21794

If we analyze what happens in the servlet container, the filter is fired and then the servlet is fired ( I didn't actually debug/test this but that's what I expected to happen ) then everything should have been sent to the document library portlet and the file should have been served... should

That was not the case and, up to this morning, I had no idea that the problem was the page name. To make a long story short, I tested, instead of using the friendly url 'documents', using the canonical liferay path : http://myhost/web/mycommunity/documents/-/document_library/view/21794 and magically the file was served ! What happened ? As far as I can tell : neither the filter nor the servlet was fired. This, to me, looks like a bug : I asked the liferay forum for a confirmation bofore opening a big report but haven't received any reply up to now.

I have, for the moment, resolved my issue by changing the 'friendly url' from documents to document_library so that now the url is http://myhost/documents_library/-/document_library/view/21794 and everything is back to normal .

If you are willing to test/replicate the issue, please update the liferay forum report so that the staff @liferay can actually be aware of the issue an maybe come up with a better solutio/update of the documentation !

The Lawrence Livermore National Laboratory has been working on porting the native Solaris ZFS source to the Linux kernel as a kernel module. I believe that as long as the project remains under contract with the DoD there will be continuous updates. You can check what's going on at http://zfsonlinux.org.

On Debian

Step 1 : prepare the directories and download the sources :

mkdir ~/src/{spl,zfs}
$ cd ~/src/spl
$ wget http://github.com/downloads/zfsonlinux/spl/spl-0.6.0-rc8.tar.gz
$ cd ~/src/zfs
$ wget http://github.com/downloads/zfsonlinux/zfs/zfs-0.6.0-rc8.tar.gz

Step 2 : install the dependencies for SPL, compile and make debs :

$ sudo aptitude install build-essential gawk alien fakeroot linux-headers-$(uname -r)
$ cd ~/src/spl
$ tar -xf spl-0.6.0-rc8.tar.gz
$ cd spl-0.6.0-rc8
$ ./configure
$ make deb

Step 3 : install the dependencies for ZFS, compile and make debs :

$ sudo aptitude install zlib1g-dev uuid-dev libblkid-dev libselinux-dev parted lsscsi
$ cd ~/src/zfs
$ tar -xf zfs-0.6.0-rc8.tar.gz
$ cd zfs-0.6.0-rc8
$ ./configure
$ make deb

If everything went fine, you have the deb files ready for install :

$ sudo dpkg -i ~/src/{spl,zfs}/*.deb

On Ubuntu

You can, of course, follow the installation path exposed above or you can simply use this PPA https://launchpad.net/~zfs-native.

Note

The manpages get installed to /share/man/. You can modify your $MANPATH variable to include /share/man/man8/ or create symlinks :

# cd /usr/share/man/man8/
# ln -s /share/man/man8/zdb.8 zdb.8
# ln -s /share/man/man8/zfs.8 zfs.8
# ln -s /share/man/man8/zpool.8 zpool.8

Start playing with it

Now, make your zpool:

$ sudo zpool create test raidz sdd sde sdf sdg sdh sdi

It is stable enough to run a ZFS root filesystem on a GNU/Linux installation for your workstation as something to play around with. It is copy-on-write, supports compression, deduplication, file atomicity, off-disk caching, encryption, and much more.

References :

Aaron Toponce's blog

Lawrence Livermore National Laboratory

The easy pattern : you have superuser privileges

In this scenario, the user is superuser ( postgres ) or is inheriting from the superuser role. If that's the case then all you need to do is open a psql shell and issue the command

 copy <table> from <file> with delimiter '<delimiter>' ;

where

• <table> is the name of the table that you want to populate with the data
• <file> is the path to the file that contains your csv data
• <delimiter> is the delimiter used in your csv file to separate the fields ( usually ',' or ';' )

The way you open a connection depends on what you are using : if you are using a gui ( such as pgAdmin ) you simply double click on the database that contains the table that you want to populate and then hit the SQL button in the toolbar. If you are using a console then you have to use pql command :

 psql -h <servername> -U <username> <databasename>

where

• <servername> is the name or ip address of the PostgreSQL server you are connecting to
• <username> is the username that you are using to connect
• <databasename> is the name of the database that contains the table you want to work on

The not so obvious pattern : you are a regular user

In this scenario you are connecting to the database via a user that has ( at least ) connect and insert privileges on the table that you want to populate. In this situation you cannot "simply" use the copy command telling postgres to get the data from a file because you need superuser privileges in order to import from a file . The work around here is to use stdin since everybody can use it ! This is going to limit the options a little but still ... Open a terminal and issue the commad :

cat <filename> | psql -U <username> -h <servername> <database> -c "copy <table> from stdin ;"

if you are on Windows system replace cat with type

Variation of the problem

• The file contains different number of columns than the table does

copy <table>(field1,field2, ..., fieldn) from ...

• The file contains headers : I don't want to import that too !

copy <table> from [stdin|<filename>] with CSV HEADER;

• The file contains special characters :

 \encoding ISO_8859_1  ;
 copy <table> from [stdin|<filename>] with CSV HEADER;  

If you want to deepen your knowledge of the powerful copy command here's the official documentation

This video shows the proof of concept in action.

This proof-of-concept comes to you courtesy of Eike Rathke of Red Hat, Michael Meeks of SUSE, and Will Thompson of Collabora.

What else can I say other than " looking forward to see it in action " on my box !

I think the instructions I found online to be, at best, confusing. The best bet you have is going with the docs that come along the package ... but there are some mistakes there too .

First things first . I would suggest to download a separate tomcat instance for your tests then, when you're ready and satisfied with the configuration of your mondrian demo, deploy into your "production" tomcat/servlet container.

For my tests and for the sake of these mini how-to, I have used tomcat 6, Sun Jdk 6 and MySQL ( installed using apt-get ).The other thing you need is the MySQL jdbc : download it and put it somewhere on your machine - I have a ~/libs/java dir where I store all my java libraries .

Unzip and start tomcat and fire mysql; test that tomcat responds by looking at http://localhost:8080 ( change the port if you modified the server configuration ) then test that mysql is up and running by issuing mysqlshow -u root mysql . Once you are sure you have everything installed, up and running you can download Mondrian from SourceForge.

Unzip your mondrian archive file somewhere. For my tests I used ~/devel/ETL. Wherever you unzipped your files you should have a tree that looks like this :

+-- demo
|   +-- access
+-- doc
|   +-- api
|   |   +-- mondrian
|   |       +-- calc
|   |       |   +-- impl
|   |       +-- gui
|   |       |   +-- validate
|   |       |       +-- impl
|   |       +-- i18n
|   |       +-- mdx
|   |       +-- olap
|   |       |   +-- fun
|   |       |   |   +-- extra
|   |       |   |   +-- vba
|   |       |   +-- type
|   |       +-- olap4j
|   |       +-- parser
|   |       +-- recorder
|   |       +-- resource
|   |       +-- rolap
|   |       |   +-- agg
|   |       |   +-- aggmatcher
|   |       |   +-- cache
|   |       |   +-- sql
|   |       +-- server
|   |       +-- spi
|   |       |   +-- impl
|   |       +-- test
|   |       |   +-- build
|   |       |   +-- clearview
|   |       |   +-- comp
|   |       |   +-- loader
|   |       +-- tui
|   |       +-- udf
|   |       +-- util
|   |       +-- web
|   |       |   +-- servlet
|   |       |   +-- taglib
|   |       +-- xmla
|   |           +-- impl
|   |           +-- test
|   +-- images
+-- lib

under the lib dir there's what you're looking for : mondrian.war. Now, stop tomcat and unzip mondrian.war into <TOMCAT_HOME>/webapps . At this point you need to create the sample database for your mondrian installation. The Mondrian demo comes with a foodmart database ... in ACCESS ( OMG ! ) format. Thanks God they provided a plain SQL file that you can upload into your mysql ... not ! What they forgot to tell you is that :

1. you have to create the schema yourself
2. you have to create the user yourself
3. the instructions don't work

Let's proceed :

open your mysql console ( as root ) and issue the following :

create database foodmart;
grant all privileges on foodmart.* to foodmart@localhost identified by 'foodmart';

the first line creates a schema 'foodmart', the second line creates a user 'foodmart' with password 'foodmart' that can do anything on the 'foodmart' schema when connecting from localhost.

Now, exit the mysql root shell and test your new user : mysql -u foodmart -p type 'foodmart' (or whatever password you chose) when promped and see if you can connect. If everything went fine you can now exit the console.

Now it's time to fill the demo database : go to <TOMCAT_HOME>/webapps/mondrian/WEB-INF and issue the command :

java -cp "./lib/mondrian.jar:./lib/olap4j.jar:./lib/log4j-1.2.8.jar:./lib/commons-logging-1.0.4.jar:./lib/eigenbase-xom.jar:./lib/eigenbase-resgen.jar:./lib/eigenbase-properties.jar:<WHERE YOU HAVE UNZIPPED YOUR MYSQL JDBC>/mysql-connector-java-3.1.14-bin.jar" mondrian.test.loader.MondrianFoodMartLoader -verbose -tables -data -indexes -jdbcDrivers=com.mysql.jdbc.Driver -inputFile=<WHERE YOU HAVE UNZIPPED MONDRIAN>/mondrian/demo/FoodMartCreateData.sql -outputJdbcURL="jdbc:mysql://localhost/foodmart?user=foodmart&password=foodmart"

As I said before, I have my mysql jdbc library in ~/libs/java, change

<WHERE YOU HAVE UNZIPPED YOUR MYSQL JDBC>/mysql-connector-java-3.1.14-bin.jar

into whatever suits your configuration. When you get the prompt again you're almost there : your database is created but you still need to configure your mondrian installation to use mysql ( by default it tries a jdbc/odbc bridge connection to the above mentioned Access database ) .

Now, go to <TOMCAT_HOME>/mondrian/WEB-INF/ and change web.xml so that every instance of

<param-value>@mondrian.webapp.connectString@</param-value>

is migrated to

<param-value>Provider=mondrian;Jdbc=jdbc:mysql://localhost/foodmart?user=foodmart&#38;password=foodmart;Catalog=/WEB-INF/queries/FoodMart.xml;JdbcDrivers=com.mysql.jdbc.Driver;</param-value>

Edit mondrian.properties ( same directory ) and change the variable mondrian.test.connectString

mondrian.test.connectString=Provider=mondrian;Jdbc=jdbc:mysql://localhost/foodmart?user=foodmart&password=foodmart;JdbcDrivers=com.mysql.jdbc.Driver;Catalog=/WEB-INF/queries/FoodMart.xml;

now you have to tell the same to the jsp pages : goto queries sub directory and change the following jsps :

1. arrows.jsp
2. colors.jsp
3. fourhier.jsp
4. mondrian.jsp

so that the tag jp:mondrianQuery looks like :

<jp:mondrianQuery id="query01" jdbcDriver="com.mysql.jdbc.Driver" jdbcUrl="jdbc:mysql://localhost/foodmart?user=foodmart&password=foodmart" catalogUri="/WEB-INF/queries/FoodMart.xml">   

now ... fire tomcat and open mondrian demo page and enjoy !

the references

• I found that the best bits of information for mondrian deployment are shipped together with the zip under <WHERE YOU HAVE UNZIPPED>/doc.
• In order to better understand what the jpivot library ( shipped together with the mondrian demo ) was doing I found this page from ETL-Tools.Info as being of great use

Said that : happy cubing !

The Hebrew University of Jerusalem has released 80,000 ( yes, you read correctly ) Einstein's scanned documents and made them searchable in the Einstein Archive online website they launched.

Don't hold your breath : it's not a collection of unpublished scientific work rather, quoting the site, a collection of an Autograph, Calculation, Transcript or one of many other document types. In other words you can find postcards or letters that have nothing to do with the scientist's work together with proper scientific work ( sorry for the horrible english :) )

Preamble .

When a work has gone orphan, it means that it is effectively lost until the copyright monopoly expires, 70 years after the creator’s death. You can only hope that somebody has kept a copy illegally and copied it across new forms of storage media as they go in and out of fashion as the decades come and go, or it will be lost forever.

What they claimed it happened

in the JURI commetee is, quoting MEP Engström’s assistant - Henrik Alexandersson, “a temporary form of democratic surplus”. You have to understand that the JURI commetee has the responsibility of safeguarding the integrity and trustworthiness of the legal framework as a whole in Europe. Are you still with me ? Ok. That committee counts 24 individual votes. This particular reform was rejected counting 12 votes for reform and 14 against . Yes, that counts 26. If you also note that there was a person not voting you understand that if there were 12 votes for reform there must have been 11 against it and the reform should have passed. The other fantastic thing that is claimed to have happend two weeks ago was that, unfortunately, when this was done, along with formally requesting a re-vote, that re-vote was denied.

Conclusion

What can I say ? I have checked out the minutes and the docs about that meeting on the EU website and honestly did not find anything, BUT according to Rick Falkvinge there are eye witnesses : you might put enough pressure on him and they might come out in the open.

IMHO : I can't honestly believe that something like that can happen ( I refer to the denial of a re-vote ) in a democracy. Someone might argue that we may not be in a democracy but have the illusion of it . The point is that YOU have to commit : follow what's going on. Ask your representatives to share documents, minutes and everything that can possibly help you make up your own opinion.; put pressure on your members of the parliament, let your voice be heard : it doesn't matter if we don't agree, just don't stay silent.

my own 2 c.

The script is pretty well commented and self explanatory : it creates a full backup on Sundays and an incremental backup the other days. Every beginning of month it creates a full backup.

#!/bin/bash
# full and incremental backup script
# created 07 February 2000
# Based on a script by Daniel O'Callaghan <danny@freebsd.org>
# and modified by Gerhard Mourani <gmourani@videotron.ca>
# modified by Marco Ferretti <marco.ferretti@gmail.com> on 16 Aug 2008

#Change the 5 variables below to fit your computer/backup

#COMPUTER=server				                                                                # name of this computer
PROJECTS="/home/marco/Projects/Workspaces /home/marco/Projects/Nitro /home/marco/Projects/Readytec"             # projects directory
CVS="/home/marco/dev /home/cvs"                                                                                 # CVS directory
DOCUMENTS="/etc /home/marco/Documents"                                                                          # documents directory
MAIL="/home/marco/.mozilla-thunderbird"				                                                # email
USERS="/home/bruno "                           	                                                                # users to fully backup
DIRECTORIES="$DOCUMENTS $USERS $PROJECTS $MAIL $CVS"                                                            # directoris that will be passed to tar
BACKUPDIR=/media/backup-disk/backup/archives	                                                                # where to store the backups
TIMEDIR=/media/backup-disk/backup/log		                                                                # where to store time of full backup
TMPFILE=/tmp/backup.local.tmp
TAR=/bin/tar					                                                                # name and locaction of tar
LOGFILE=/media/backup-disk/backup/log/backup.log                                                                # log file 

#You should not have to change anything below here
PATH=/usr/local/bin:/usr/bin:/bin
DOW=`date +%a`              		                                                                        # Day of the week e.g. Mon
DOM=`date +%d`              		                                                                        # Date of the Month e.g. 27
DM=`date +%d%b`             		                                                                        # Date and Month e.g. 27Sep

# On the 1st of the month a permanet full backup is made
# Every Sunday a full backup is made - overwriting last Sundays backup
# The rest of the time an incremental backup is made. Each incremental
# backup overwrites last weeks incremental backup of the same name.
#
# if NEWER = "", then tar backs up all files in the directories
# otherwise it backs up files newer than the NEWER date. NEWER
# gets it date from the file written every Sunday.


echo "`date` Starting backup backup script" > $LOGFILE

# Monthly full backup
if [ $DOM = "01" ]; then
	echo "`date +%d-%b-%y` Starting montly full backup" >> $LOGFILE
        NEWER=""
#        $TAR $NEWER -cfj $BACKUPDIR/$COMPUTER-$DM.tar.bz2 $DIRECTORIES
#	$TAR $NEWER -cjf $TMPFILE $DIRECTORIES
#Version that creates one big file
#        $TAR $NEWER -cjf $BACKUPDIR/monthly/$DM-full.tar.bz2 $DIRECTORIES 
#Version that splits the file in 4Gb parts (DVD burn ready
	$TAR $NEWER cjf - $DIRECTORIES | split --bytes=4G -d - $BACKUPDIR/monthly/$DM-full.tar.bz2_
        #Remove the big file ...
	rm BACKUPDIR/monthly/$DM-full.tar.bz2
#	cp $TMPFILE $BACKUPDIR/monthly/$DM-full.tar.bz2
fi

# Weekly full backup
if [ $DOW = "Sun" ]; then
	echo "`date +%d-%b-%y` Starting weekly full backup" >> $LOGFILE
        NEWER=""
        NOW=`date +%d-%b`

        # Update full backup date
#        echo $NOW > $TIMEDIR/$COMPUTER-full-date
#        $TAR $NEWER -cjf $BACKUPDIR/$COMPUTER-$DOW.tar $DIRECTORIES
        echo $NOW > $TIMEDIR/full-date
        $TAR $NEWER -cjf $BACKUPDIR/weekly/$DOW-full.tar.bz2 $DIRECTORIES
#        $TAR $NEWER -cjf $TMPFILE $DIRECTORIES        
#	cp $TMPFILE $BACKUPDIR/weekly/$DOW-full.tar.bz2        

# Make incremental backup - overwrite last weeks
else
        # Get date of last full backup
#        NEWER="--newer `cat $TIMEDIR/$COMPUTER-full-date`"
#        $TAR $NEWER -cf $BACKUPDIR/$COMPUTER-$DOW.tar $DIRECTORIES
	echo "`date +%d-%b-%y` Starting incremental backup" >> $LOGFILE
        NEWER="--newer `cat $TIMEDIR/full-date`"
        $TAR $NEWER -cjf $BACKUPDIR/weekly/$DOW.tar.bz2 $DIRECTORIES
#        $TAR $NEWER -cjf $TMPFILE $DIRECTORIES        
#	cp $TMPFILE $BACKUPDIR/weekly/$DOW.tar.bz2                
fi
echo "`date` end of backup backup script" >> $LOGFILE

If you have, for example, installed liferay and upgraded it to version 6.0.6 you are likely to have problems my frieds; it took me a whole day to understand what was going ( literally ) tits-up in my server since i noticed an exception in liferay that I thought I already had fixed with the use of portal-legacy-5.2.properties.

Said that I would like to thank the guys at Debian and at Ubuntu for their great job ... and I can't help but ask them to pay a little more attention when they release upgrades that impact server releases of their stuff.

hope this helps someone out there