You can find below download link for Wolfenstein Enemy Territory client for Linux 2.6 :
http://am4computers.com/downloads/ET/et-linux-2.2.60.x86.run
Also, please run below patch afterwards :
http://am4computers.com/downloads/ET/et-2.60b.zip
You can find below download link for Wolfenstein Enemy Territory client for Linux 2.6 :
http://am4computers.com/downloads/ET/et-linux-2.2.60.x86.run
Also, please run below patch afterwards :
http://am4computers.com/downloads/ET/et-2.60b.zip
Today, we installed the latest openERP 7.0 on our openSuSE 12.1 server. Also, we patched the new openERP 7.0 code similar to our post http://am4computers.com/wordpress/archives/258 to enable RTL support. As of now, all is working great with full support for Arabic and Hebrew.
A HOWTO for installing Google Talk on SUSE Linux for Firefox :
32 bit Code:
mkdir goog; cd goog wget http://dl.google.com/linux/direct/google-talkplugin_current_i386.deb ar vx google-talkplugin_current_i386.deb sudo tar xvzf data.tar.gz -C /
64 bit Code:
mkdir goog; cd goog wget http://dl.google.com/linux/direct/google-talkplugin_current_amd64.deb ar vx google-talkplugin_current_amd64.deb sudo tar xvzf data.tar.gz -C /
Then restart Firefox.
After you restart firefox, in the Tools -> Addons -> Plugins tab, you’ll see google talk. And yes, it should now work!
Lately, we have been getting below error from the openERP-web client as soon as we log out the console session :
Traceback (most recent call last): File "/usr/local/lib/python2.6/site-packages/CherryPy-3.1.2-py2.6.egg/cherrypy/wsgiserver/__init__.py", line 1174, in communicate req.respond() File "/usr/local/lib/python2.6/site-packages/CherryPy-3.1.2-py2.6.egg/cherrypy/wsgiserver/__init__.py", line 544, in respond self._respond() File "/usr/local/lib/python2.6/site-packages/CherryPy-3.1.2-py2.6.egg/cherrypy/wsgiserver/__init__.py", line 556, in _respond response = self.wsgi_app(self.environ, self.start_response) File "/usr/local/lib/python2.6/site-packages/CherryPy-3.1.2-py2.6.egg/cherrypy/_cptree.py", line 239, in __call__ return app(environ, start_response) File "/usr/local/lib/python2.6/site-packages/CherryPy-3.1.2-py2.6.egg/cherrypy/_cptree.py", line 130, in __call__ return self.wsgiapp(environ, start_response) File "/usr/local/lib/python2.6/site-packages/CherryPy-3.1.2-py2.6.egg/cherrypy/_cpwsgi.py", line 313, in __call__ return head(environ, start_response) File "/usr/local/lib/python2.6/site-packages/CherryPy-3.1.2-py2.6.egg/cherrypy/_cpwsgi.py", line 301, in tail return self.response_class(environ, start_response, self.cpapp) File "/usr/local/lib/python2.6/site-packages/CherryPy-3.1.2-py2.6.egg/cherrypy/_cpwsgi.py", line 74, in __init__ self.setapp() File "/usr/local/lib/python2.6/site-packages/CherryPy-3.1.2-py2.6.egg/cherrypy/_cpwsgi.py", line 96, in setapp _cherrypy.log(tb, severity=40) File "/usr/local/lib/python2.6/site-packages/CherryPy-3.1.2-py2.6.egg/cherrypy/__init__.py", line 385, in __call__ return log.error(*args, **kwargs) File "/usr/local/lib/python2.6/site-packages/CherryPy-3.1.2-py2.6.egg/cherrypy/_cplogging.py", line 55, in error self.error_log.log(severity, ' '.join((self.time(), context, msg))) File "/usr/local/lib/python2.6/logging/__init__.py", line 1093, in log self._log(level, msg, args, **kwargs) File "/usr/local/lib/python2.6/logging/__init__.py", line 1143, in _log self.handle(record) File "/usr/local/lib/python2.6/logging/__init__.py", line 1153, in handle self.callHandlers(record) File "/usr/local/lib/python2.6/logging/__init__.py", line 1190, in callHandlers hdlr.handle(record) File "/usr/local/lib/python2.6/logging/__init__.py", line 669, in handle self.emit(record) File "/usr/local/lib/python2.6/logging/__init__.py", line 778, in emit self.handleError(record) File "/usr/local/lib/python2.6/logging/__init__.py", line 720, in handleError traceback.print_exception(ei[0], ei[1], ei[2], None, sys.stderr) File "/usr/local/lib/python2.6/traceback.py", line 124, in print_exception _print(file, 'Traceback (most recent call last):') File "/usr/local/lib/python2.6/traceback.py", line 13, in _print file.write(str+terminator) IOError: [Errno 5] Input/output error This error can be avoided using : nohup python2.6 openerp-web.py &
OpenERP version 5 won’t work with python 2.7 installed be default on openSuSE 12.1 server. The trick is to download and install python 2.6 as source and install it parallel to default version.
After that, you’ll have two python executables on the system, python (for 2.7) and python2.6 for the outdated version. The 2.6 version will be used to start the openerp server as below :
python2.6 openerp-server.py -r dbuser -w dbpassword &
Also, you need to install system wide packages needed by default installation of the openERP system. And you must use python2.6 or easy_install-2.6 to install missing python modules. My system was up and running after installing below python modules :
You must choose the same python module version numbers, update versions won’t work.
After transferring our openERP 5.0.16 server to a new host, we are getting this error message while trying to add an attachment through the web client :
a class that defines __slots__ without defining __getstate__ cannot be pickled
The problem was that the default version of cherrypy was 3.2.2 and the web-server seems to have needed 3.1.2.
You can use ‘easy_install cherrypy==3.1.2’ to install the required version and now the web-server works fine.
Hosting Joomla on awardspace servers will probably cause your Joomla site to not direct to pages and articles correctly and you’ll be getting a lot of pages not found errors – “404 Page Not Found”.
Such issues are usually caused by the SEF functionality of Joomla. There are several things you should check in order to fix this:
var $live_site = ‘http://yourdomain.com/joomla/ ‘;
If you follow all of the steps above you should have a fully operational Joomla website with the SEF functionality enabled.
NoMachine NX client and FreeNX will start your GUI as KDE or GNOME. But if you choose custom desktop from configuration menu, you can set the command to ‘startxfce4’. This will start the XFCE desktop instead (if installed).
This is a copy of the original post on http://yourlinuxguy.com/?p=916.
It looks like some people are working very hard out there to try and preserve iFolder for future versions of Opensuse. To those people (the NoFolder crew, Ravi Kumar, etc.), I’m indebted; I simply would be at a loss without iFolder. Yes, I use DropBox, and a couple other things, but there’s just nothing like iFolder for complete control over the server and the sync’d content.
But the sad fact is, it has suffered a bit of neglect as of late. Okay, a LOT of neglect. And you’re probably here because you have an Opensuse 12.1 (or 11.4) server, and you tried to install iFolder 3.8.x on it, and had some trouble.
Notes: I strongly recommend you see my old post about setting up iFolder 3.8 on Opensuse 11.1 for background and additional detail, as this post will be brief and to-the-point without much supporting detail. All the work in this doc was performed on the x86_64 version of Opensuse, and was tested on both 12.1 and 11.4.
FIRST, you need a working Apache2 installation with SSL support. Find previous post if you need help with this.
We need to install below packages :
ifolder3-enterprise-3.8.4.0.11091.1-6.2.x86_64
novell-ifolder-enterprise-plugins-3.8.4.10192.1-6.3.x86_64
And run all 3 configuration scripts and please note that you must use an alternative simias datastore location of /ifolder
:
simias-server-setup ifolder-admin-setup ifolder-web-setup NOTE: When asked for server address, use a fully qualified server address as below :
Change :
Public URL: https://192.168.0.79/simias10
Private URL: https://192.168.0.79/simias10
to
Public URL: https://ifolder01.MyDomainName.com:52443/simias10
Private URL: https://192.168.0.79/simias10
…and now my external clients can connect via the ifolder client, and sync seems to be working.
NOTE 2 : Don’t use default server data folder. I use /home/iFolder/
A note about the next step: If you just stopped here, you’d be able to pull up the /admin page, but not log in; you’d get a red message saying that your password doesn’t match or whatever. I see this error quite commonly out there… So let’s change the FlaimWrapper softlink pointer to an existing location:
rm /usr/lib64/simias/web/bin/FlaimWrapper.so ln -s /usr/lib64/libFlaimWrapper.so.0 /usr/lib64/simias/web/bin/FlaimWrapper.so
And lastly, restart stuff:
rcSuSEfirewall2 restart;rcapache2 stop; rcapache2 start
And that should do it! Log in at /admin, configure some users, etc., etc., etc. I’m guessing you are here because you know already how to *use* iFolder, just got stuck installing and configuring it, so I’ll not go into any usage detail.
By the way, the NoFolder.com page has some good troubleshooting tips, but if you follow these steps accurately, and you use the SAME hostname throughout the configuration, you should be fine.
See, it’s not that bad. And it’s totally worth it. Enjoy!
Following is a step-by-step guide to creating your own CA (Certificate Authority) — and also self-signed SSL server certificates — with openssl on Linux. Self-signing is the simpler route to take, but making one’s own CA allows the signing of multiple server certificates using the same CA and involves only a few extra steps.
After using openssl to generate the necessary files, you’ll need to integrate them into Apache. This process differs between Linux distros and versions of Apache.
Generate a server key:
openssl genrsa -des3 -out server.key 4096 Then create a certificate signing request with it. This command will prompt for a series of things (country, state or province, etc.). Make sure that “Common Name (eg, YOUR name)” matches the registered fully qualified domain name of your box (or your IP address if you don’t have one). I also suggest not making a challenge password at this point, since it’ll just mean more typing for you. The default values for the questions ([AU], Internet Widgits Pty Ltd, etc.) are stored here: /etc/ssl/openssl.cnf. So if you’ve got a large number of certificate signing requests to process you probably want to carefully edit that file where appropriate. Otherwise, just execute the command below and type what needs to be typed:In this step you’ll take the place of VeriSign, Thawte, etc. You’ll first build the CA key, then build the certificate itself.
The Common Name (CN) of the CA and the Server certificates must NOT match or else a naming collision will occur and you’ll get errors later on. In this step, you’ll provide the CA entries. In a step below, you’ll provide the Server entries. In this example, I just added “CA” to the CA’s CN field, to distinguish it from the Server’s CN field. Use whatever schema you want, just make sure the CA and Server entries are not identical.
CA:
Common Name (CN): www.somesite.edu CA
Organization (O): Somesite
Organizational Unit (OU): Development
Server:
Common Name (CN): www.somesite.edu
Organization (O): Somesite
Organizational Unit (OU): Development
If you don’t have a fully qualified domain name, you should use the IP that you’ll be using to access your SSL site for Common Name (CN). But, again, make sure that something differentiates the entry of the CA’s CN from the Server’s CN.
The command below does a number of things. It takes your signing request (csr) and makes a one-year valid signed server certificate (crt) out of it. In doing so, we need to tell it which Certificate Authority (CA) to use, which CA key to use, and which Server key to sign. We set the serial number to 01, and output the signed key in the file named server.crt. If you do this again after people have visited your site and trusted your CA (storing it in their browser), you might want to use 02 for the next serial number, and so on. You might create some scheme to make the serial number more “official” in appearance or makeup but keep in mind that it is fully exposed to the public in their web browsers, so it offers no additional security in itself.
If you took route 1B and created a CA, you’ll have two additional files:
ca.crt: The Certificate Authority’s own certificate.
ca.key: The key which the CA uses to sign server signing requests.
The CA files are important to keep if you want to sign additional server certificates and preserve the same CA. You can reuse these so long as they remain secure, and haven’t expired.
DocumentRoot “/srv/www-ssl/htdocs”
ServerName xxx.xxx.xxx.xxx:443
ServerAdmin youremail@yoursite.org
Just before the </VirtualHost> directive is closed, add the following, making tweaks as necessary for your environment. If you don’t make a directory directive, the SSL instance won’t know where to look for the doc root.
Make sure that HTTP and HTTPS are enabled for the External Zone. Note that this mechanism assumes port 80 and port 443 respectively. If you want to set up HTTP or HTTPS on a different port (for instance, 8080 or 444) you need to go to the Advanced screen and manually type in the port number under “TCP Ports” and describe the protocol you’re adding (for example, HTTP or HTTPS) in the last line under “IP Protocols.” If you have a router, it probably carries additional firewall rules. You’ll need to open up the appropriate port(s) there as well. That’s beyond the scope of this document, but should be in the docs that pertain to your hardware.
Bad Behavior has blocked 136 access attempts in the last 7 days.