Wednesday, February 24, 2010

Amazone MS Licencing deal

Strange news have been published recently:

News entry on information week

In short:

A company, using Linux systems/technologies pays some unknown license fees for "perhaps" patent violations, even MS not being able to prove anything...

So they probably just wish to prevent some treats from the big player in this business.

In other environments such stuff would be called "Protection racket", paying to prevent being harmed by the "stronger" player on the market.
With no proofs, no clear win for the one how pays....

Thursday, February 18, 2010

Windows 7 and Samba

Yet another post on the Windows 7 & SAMBA subject:

To be able to join Windows 7 stations into a Samba controlled domain you must do the following steps:

- Make sure you have samba version 3.3.4
We also did try with 3.3.9 and 3.4.3 but have not been able to get it working in our environment....

- In the registry of the windows 7 system change these settings



You should now be able to join the domain and login as well.

Open Word, Excel und PDF documents with wine

Normally you don't install (ms|open)-office under wine.
You rather have the full openoffice directly installed under linux.

To allow windows apps to open the files with the native openoffice applications you can do the following:

- Create a registry file containing your associations per application

For example


@="c:\\ooffice.exe %1"


@="c:\\ooffice.exe %1"


@="c:\\pdfreader.exe %1"

Then import this with regedit.exe
Now create the helper applications under C:\ of your wine installation.

For example: ooffice.exe (Make sure it is executable chmod a+x ooffice.exe)

ooffice "`winepath -u "$*"`"

or for pdf:

acroread "`winepath -u "$*"`"

What happens:

1. In the registry you tell windows what app to start for the corresponding file type
2. In the helper file ooffice.exe you start the native linux application
The helper application winpath converts a windows path into the corresponding linux path

Tuesday, February 16, 2010

More printing with freenx

Ok, so now we got remote printing working with freenx

What had to be done:

- Disable (or remove) apparmor from the server
- In the /usr/lib/nx/nxnode script, we did force cups=1 (Arround line 1096)

No idea why cups is not set, but once it's set we can print from gnome applications.

Thursday, February 11, 2010

Printing with FreeNX

In current Ubuntu environments with FreeNX installed, then printing does not work out of the box.
To get it working, we had to change two things:

* Create a symlink for /usr/lib/nx/nxsmb -> /usr/lib/cups/backend
* chmod a+x for /usr/lib/

After this, it's possible to print to the remote printer.
What now is left, is telling gnome/kde to use that local cups server instead of the localhost one.

Welcome in my Weblog

In this blog I will post small tricks, experiences, nasty things and much more about computer technology usage.