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
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.
First, you need to download the LiveCD iso image of your choice. After inserting your USB stick, you can find out what device it is
~> su # grep -Ff <(hwinfo --disk --short) <(hwinfo --usb --short)
Finally, once you’ve found your block device, write the image to it. Point ‘dd’ to the full path such as ‘/home/user/Downloads/openSUSE-12.1-KDE-LiveCD-x86_64.iso’ or change directory (example: cd ./Downloads) to where the image is contained.
# umount /dev/sdX
# dd if=/path/to/downloaded.iso of=/dev/sdX
First, locate and download latest Java version from Java.com :
http://java.com/en/download/linux_manual.jsp?locale=en&host=java.com
1. Exit Firefox.
2. Uninstall any previous installations of Java Plugin.
Only one Java Plugin can be used at a time. When you want to use a different plugin, or version of a plugin, remove the symbolic links to any other versions and create a fresh symbolic link to the new one.
Remove the symbolic links (or move them to another directory) to javaplugin-oji.so
and libnpjp2.so
from the Firefox plugins
directory /usr/lib64/browser-plugins
3. Install downloaded java plugin
4. Create a symbolic link to the Java Plugin in the Firefox plugins
directory.
Create a symbolic link to the Java Plugin
libnpjp2.so
file in the Firefoxplugins
directory:cd /usr/lib64/browser-plugins ln -s /usr/java/jre1.6.0_23/lib/amd64/libnpjp2.so
5. Start the Firefox browser .
Type about:plugins in the Location bar to confirm that the Java Plugin is loaded. You can also click the Tools menu to confirm that Java Console is there.
iFolder is a simple and secure storage solution that can increase your productivity by enabling you to back up, access and manage your personal files-from anywhere, at any time. Once you have installed iFolder, you simply save your files locally-as you have always done-and iFolder automatically updates the files on a network server and delivers them to the other machines you use.
Using iFolder, you can designate any network server as an iFolder server and publish information to a personal iFolder created on that server. Once your folder is established, you can install iFolder on the computers you regularly use and download information from your personal iFolder to any of those computers. Not only that, but using iFolder, you can also invite other iFolder users to share your files in the same safe and secure way so that your teams always have the most relevant copy of a document.
Below are installation instructions for openSuSE 10.3 server :
Download the following packages :
ifolder3 from http://www.kablink.org/index.php
http://ftp.novell.com/pub/mono/download/x86/mono/1.2.6-4/mono-core-1.2.6-4.novell.i586.rpm
http://ftp.novell.com/pub/mono/download/x86/mono/1.2.6-4/mono-data-1.2.6-4.novell.i586.rpm
http://ftp.novell.com/pub/mono/download/x86/mono/1.2.6-4/mono-data-sqlite-1.2.6-4.novell.i586.rpm
http://ftp.novell.com/pub/mono/download/x86/mono/1.2.6-4/mono-web-1.2.6-4.novell.i586.rpm
http://ftp.novell.com/pub/mono/download/x86/mono/1.2.6-4/mono-nunit-1.2.6-4.novell.i586.rpm
http://ftp.novell.com/pub/mono/download/x86/mono/1.2.6-4/mono-winforms-1.2.6-4.novell.i586.rpm
http://ftp.novell.com/pub/mono/download/noarch/xsp/1.2.6-2/xsp-1.2.6-2.novell.noarch.rpm
http://ftp.novell.com/pub/mono/download/suse-103-i586/mod_mono/1.2.6-1/apache2-mod_mono-1.2.6-1.suse103.novell.i586.rpm
Install as following :
rpm -i mono-core-1.2.6-4.novell.i586.rpm
rpm -i mono-data-1.2.6-4.novell.i586.rpm
rpm -i mono-data-sqlite-1.2.6-4.novell.i586.rpm
rpm -i mono-nunit-1.2.6-4.novell.i586.rpm
rpm -i mono-web-1.2.6-4.novell.i586.rpm –nodeps
rpm -i mono-winforms-1.2.6-4.novell.i586.rpm
rpm -i xsp-1.2.6-2.novell.noarch.rpm
rpm -i apache2-mod_mono-1.2.6-1.suse103.novell.i586.rpm
Then install iFolder server.
*Google has also released official builds of Google Chrome for Linux and Mac OS X (see update below). If you are looking to install Chrome on a USB stick, check out Portable Google Chrome.
The Google Browser port, known as Crossover Chromium, is available for download on Mac OS X as a native Mac .dmg file or on Ubuntu, RedHat, Suse, etc. as standard Linux packages.
Google Chrome is built with open source code from Chromium.
Mac users can simply drag the Chromium .dmg file into their Applications folder. Linux users should use the appropriate tools for their respective Linux distributions to unpack the installer package. Google Chrome on Linux is available for both 32bit and 64bit versions.
If you installed Google Chrome on Linux using the .deb package, you can uninstall the Google Browser using the Synaptic package manager or via the following command – sudo aptitude purge cxchromium
Google Chrome for Mac & Linux – Official Builds
Update: The official builds of Google Chromium are now available for Linux and Mac here. The interface and features of Chromium for Mac OS X are similar to that of Chrome for Windows but it’s a developer release and not very stable yet.
Two New Gartner Linux Research Notes
Leading IT research and advisory company Gartner has published two new Linux research notes:
Moblin, short for mobile Linux, is an open source project focused on developing software for Mobile Internet Devices (MIDs) and other new categories of devices such as netbooks and nettops. Intel launched the Moblin.org site in July 2007 and significantly updated the site in April 2008 with the launch of the Intel Atom processor family at the Intel Developer Forum in Shanghai. A custom SDK is also available on the site. The Moblin 2 OS was specifically designed to run on an Intel Atom processor in a netbook. In April 2009 Intel turned Moblin over to the Linux Foundation. Watch the below video for an introduction to the new beta version :
Find below bash script for openSuSE 11.0 and 11.1 that will install 64bit Flash Player :
#!/bin/bashecho “Stopping Firefox”
sudo killall -9 firefox
echo “Removing previous installations of flash plugin :”
sudo rm -f /usr/lib64/browser-plugins/npwrapper.libflashplayer.so
sudo rm -f /usr/lib/browser-plugins/libflashplayer.so
sudo rm -f /usr/lib/flash-plugin/libflashplayer.so
sudo rm -rfd /usr/lib/nspluginwrapper
echo “Installing Flash Player 10”
wget http://download.macromedia.com/pub/labs/flashplayer10/libflashplayer-10.0.42.34.linux-x86_64.so.tar.gz
tar zxvf libflashplayer-10.0.42.34.linux-x86_64.so.tar.gz
sudo cp libflashplayer.so /usr/lib64/browser-plugins/libflashplayer.so
sudo cp libflashplayer.so /usr/lib/browser-plugins/libflashplayer.so
# some cleaning up
sudo rm -rf libflashplayer-10.0.42.34.linux-x86_64.so.tar.gzYou need to chmod +x then execute it. Remember to enable flash pluging in Firefox then restarting.
Bad Behavior has blocked 44 access attempts in the last 7 days.