kaskepedia

Adobe AIR on 64bit Fedora 11

2010-05-03T13:01:00.010+02:00

In my first attemp installing Adobe AIR on Fedora 11, I got the following error: “gnome-keyring or kwallet is necessary to install Adobe AIR”

Adobe AIR is 32bit, so if you want to install it on a 64bit Fedora 11 you will need to install the 32bit version of the required packages:

[root@local ~]$ yum install gnome-keyring.i586 rpm-libs.i586

In the process, a dependency problem may appear:

--> Processing Conflict: GConf2-2.26.2-1.fc11.2.x86_64 conflicts GConf2-dbus
--> Finished Dependency Resolution
GConf2-2.26.2-1.fc11.2.x86_64 from installed has depsolving problems
--> GConf2 conflicts with GConf2-dbus
Error: GConf2 conflicts with GConf2-dbus

To solve it, install GConf2.i586: [root@local ~]$ yum install GConf2.i586

Then, download Adobe AIR from Adobe's website and install it:

[root@local ~]$ chmod +x AdobeAIRInstaller.bin

[root@local ~]$ ./AdobeAIRInstaller.bin

dhcpd starts before NetworkManager brings up network interfaces

2010-04-30T15:26:00.000+02:00

To ensure that dhcpd starts after NetworkManager brings up network interfaces, edit dhcp daemon start script (located in /etc/rc.d/rc5.d/) and insert the following line at the beginning: sleep 10

Mendeley Desktop on Linux 64bit: libssl.so.0.9.8 error

2010-04-26T15:32:00.006+02:00

[oskar@local bin]$ ./mendeleydesktop

error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or directory

SOLUTION: make a symlink to libssl library

[root@local ~]$ ln -s /usr/lib64/libssl.so.0.9.8n /usr/lib64/libssl.so.0.9.8

NOTE: make sure your symlink is in the appropriate lib directory

for 32-bit: /usr/lib
for 64-bit: /usr/lib64

Verify the ownership of your gadget

2010-03-13T12:37:00.002+01:00

Social apps often deal with people's personal information, so it's important to respect and protect this data. Since social applications communicate between several computers, you need a way to verify that an HTTP request is legitimate.

In this case, you need to verify that the requests coming into your application server are actually originating from the container you're working with. If you don't verify the origin of the request, you could be handing out personal data to anyone that sends an HTTP request to your application server.

Google secures communication between our gadget containers (like iGoogle) and your servers by signing and verifying requests using OAuth. In order to set up this secure communication channel, you need to register your app and obtain a Consumer Key and a Consumer Secret for use in OAuth parameter signing.

Trying to host a big file size gadget

2010-03-13T12:31:00.001+01:00

Google Gadget Editor limits the maximum gadget file size to 100000 bytes.
Try to host the gagdet file on Google Code's project hosting: a Subversion repository will be created using your project name
Check out the project: svn checkout https://<project-name>.googlecode.com/svn/trunk/ gadget-test --username <username>
Save the gadget file (new-gadget.xml) in your local SVN folder.
Commit the file: svn commit -m "bla bla bla" --username <username>
Add gadget to iGoogle using http://<project-name>.googlecode.com/svn/trunk/new-gadget.xml

* When prompted for your password in SVN, use your googlecode.com password, which can be found on the "Settings" tab of your "Profile" page.

How do I import an existing Subversion repository to Google Project Hosting?

2009-11-05T17:42:00.004+01:00

To upload the history of an existing Subversion repository, use the svnsync tool that ships with Subversion 1.4 or later. Run svnsync help to read more about this tool.

Note that your Google Code repository must be reset to revision 0 for this to work. Your project's Source tab will display instructions on how to reset the repository yourself. (Note: you must be a project owner to reset your own repository, and also to push code up with svnsync.)

Here's a sample transcript that demonstrates how you can push history from an existing local repository to your repository on Google Code:

$ svnsync init --username YOURUSERNAME https://YOURPROJECT.googlecode.com/svn file:///path/to/localrepo
Copied properties for revision 0.
$ svnsync sync --username YOURUSERNAME https://YOURPROJECT.googlecode.com/svn
Committed revision 1.
Copied properties for revision 1.
Committed revision 2.
Copied properties for revision 2.
[...]

Port triggering

2009-05-22T12:45:00.000+02:00

From Wikipedia
—–

Port triggering is a way to automate port forwarding in which outbound traffic on predetermined ports (’triggering ports’) causes inbound traffic to specific incoming ports to be dynamically forwarded to the initiating host, while the outbound ports are in use. This allows computers behind a NAT-enabled router on a local network to provide services that would normally require the computer to have a fixed address on the local network.

WiFi authentication

2009-05-22T11:50:00.000+02:00

The 802.11 standard supports two means of client authentication between the wireless NIC and the AP: open system and shared key.

With shared key, the AP sends the client device a challenge text packet that the client must then encrypt with the correct WEP key and return to the AP. If the client has the wrong key or no key, authentication will fail and the client will not be allowed to associate with the AP. Shared key authentication is not considered secure, because a hacker who detects both the clear-text challenge and the same challenge encrypted with a WEP key can decipher the WEP key.

With open system, authentication involves supplying the correct SSID. Even if a client can complete authentication and associate with an AP, the use of WEP prevents the client from sending data to and receiving data from the AP, unless the client has the correct WEP key.

Registros DNS: A, CNAME y NS

2009-01-09T14:16:00.000+01:00

In layman's terms:

"A xxx", quiere decir "felicidades, lo encontraste, la IP es xxx"

"CNAME blablabla.com", quiere decir "mejor pregunta por blablabla.com, y lo que te respondan sobre ese dominio, también es valido para el que buscas"

"NS xxx", quiere decir "yo no sé, pero pregúntale a xxx"

Restore AWL500 to factory settings

2008-12-24T22:18:00.002+01:00

Create a empty file called: Load_Default.upg

After this go to: start > run > cmd
You will see now a MS-DOS window.

Go to the directory where the file is saved.
Type: tftp IP_OF_AWL500 put Load_Default.upg .
After 10 seconds with the state busy press Ctrl+C to stop it.

AWL500 is now back into default factory settings.

64bit browsers and 32bit plugins

2008-12-02T21:05:00.001+01:00

clipped from www.redhat.com

Not all applications are provided in the form of standalone programs—some are provided as plug-ins to other applications. One such example is the Macromedia® Flash™ plug-in for web browsers. Currently this plug-in is available for Linux but only for 32-bit Intel-compatible processors.

A web browser plug-in is a library that gets dynamically loaded by the web browser program. It is not currently possible in Linux for a 64-bit program to dynamically load a 32-bit library. This means that the 64-bit Mozilla Firefox in Fedora Core (for example) cannot use the Macromedia Flash plug-in at all.

One work-around is to uninstall the 64-bit Mozilla Firefox package and install the equivalent package from the 32-bit Fedora Core distribution. The result is that the web browser is a 32-bit application, and this makes it possible to load 32-bit plug-ins such as Flash. It does, however, make it impossible to use any 64-bit plug-ins.

Get Clipmarks - The easiest way to email text, images and videos you find on the web.

Pecha Kucha

2008-10-11T15:44:00.002+02:00

clipped from en.wikipedia.org

Pecha Kucha (ペチャクチャ, ^?) or Pecha Kucha Night is a presentation format in which work can be easily and informally shown.

The idea behind Pecha Kucha is to keep presentations concise, the interest level up and to have many presenters sharing their ideas within the course of one night. Therefore the 20x20 Pecha Kucha format was created: each presenter is allowed a slideshow of 20 images, each shown for 20 seconds.

The 20x20 format of Pecha Kucha is now also being adopted in the business world, with some company internal business presentations being run in a strict 6 minutes 40 seconds, with all discussion and questions held to the end of the presentation. This is primarily a device to help timebox presentations, force presenters to be more focused in their message, allow them to flow uninterrupted, and ultimately to avoid the "death by powerpoint" syndrome, of sitting through long and often tedious PowerPoint presentations.

Get Clipmarks - The easiest way to email text, images and videos you find on the web.