If you are experiencing issues installing LiveCode within a Linux environment the most likely cause of this is that the installer has not had its executable bit set. This lesson will explain how to do this within the Ubuntu Linux environment

I recently got an old iMac G3 and felt the need to replace the crappy existing MacOS 9 system with my favorite system : Linux of course!

After a mandatory RAM upgrade (from stock 64M to 512M), I found that the CD drive is extremely picky/worn-out and wouldn’t boot any burned install CDs…

But that’s not enough to stop me, since those iMac models support booting from the network.

I first tried to netboot Debian Squeeze on it, but there were some issues (yaboot started but couldn’t load the kernel).

After some research, it appears that Ubuntu has an updated netinstall iso which just works!

The most comprehensive guide on iMac 3 disassembly - useful to replace the hard disk and install another operating system like GNU/Linux :)

A video walkthough of some of the must know tips and tricks for the Samsung Galaxy S2. Details and screenshots at http://thehandheldblog.com/2011/06/14/galaxy-s2-tips-tricks/

Questions de Chantal Patry, Service local du RÉCIT, CS Harricana

Avez-vous testé le logiciel WordQ avec LibreOffice?
Avez-vous éprouvé des problèmes avec certaines fonctions essentielles dont le suivi du curseur lors de la lecture et le suivi de la boîte de prédiction de mots lors de l’écriture? Si oui, qu’avez-vous fait pour remédier à cela?

There are currently two registry settings required to be added on the Windows 7 client prior to joining a Samba Domain. These are:

    HKLMSystemCCSServicesLanmanWorkstationParameters
        DWORD  DomainCompatibilityMode = 1
        DWORD  DNSNameResolutionRequired = 0

Samba also ships with a registry patchfile that users can apply directly. The patchfile can be found in recent Samba sourcecode: $SOURCE/docs-xml/registry/Win7_Samba3DomainMember.reg or in Samba Bugzilla here: https://bugzilla.samba.org/attachment.cgi?id=4988&action=view

Make sure to either reboot Windows 7 or restart the LanmanWorkstation service after setting these entries.

Do not edit any other registry parameters (NETLOGON) that have been seen in the wild. If you have already modified your Windows 7 registry, please make sure to reset the keys to their default values.

If you have changed the NETLOGON Parameters, make sure and turn them back to '1' as shown below:

   HKLMSystemCCSServicesNetlogonParameters
       DWORD  RequireSignOrSeal = 1
       DWORD  RequireStrongKey = 1

A recent Jon Carroll column got me thinking about Making and Fixing.

This was the passage that got me started:

... I took it to Dave up at the repair place. "You need a new battery," he said. Looked like a fine battery to me, but what do I know? I had a second opinion from the guy who wanted to sell me a battery. What could go wrong?

I brooded about this on the way. I realized how much we are at the mercy of the repair people in our lives, and how much we do not know about, well, most things.

A thread on the Ubuntu-devel-discuss mailing list last month asked about how to find out what processes are making outgoing network connectsion on a Linux machine. It referenced Ubuntu bug 820895: Log File Viewer does not log "Process Name", which is specific to Ubuntu's iptables logging of apps that are already blocked in iptables ... but the question goes deeper.

Several years ago, my job required me to use a program -- never mind which one -- from a prominent closed-source company. This program was doing various annoying things in addition to its primary task -- operations that got around the window manager and left artifacts all over my screen, operations that potentially opened files other than the ones I asked it to open -- but in addition, I noticed that when I ran the program, the lights on the DSL modem started going crazy. It looked like the program was making network connections, when it had no reason to do that. Was it really doing that?

People often ask the Free Software Foundation (FSF) what license is recommended to use for their project. The FSF has written about this publicly before, but the information has been scattered around between different essays, FAQ entries, and license commentaries. This article collects all that information into a single source, to make it easier for people to follow and refer back to.

The recommendations are focused on licensing a work that you create—whether that's a modification of an existing work, or a new original work. These recommendations do not address the issue of combining existing material under different licenses. If you're looking for help with that, please check the FSF license FAQ.

switch2osm.org explains how to make the switch – from first principles to technical how-tos.