I’m facing an issue related to inconsistences in the source code that am porting, for example, variable-naming:

struct sample {
int variableName;
int otra_variable;
};

Did you notice the problems? First, using camelCase to declare the variable, then using underscore to separate words in variable, and also mixing both Spanish and English. I just don’t like it. I’m updating the code while testing its performance. A C-based refactoring tool would be nice,

So I need, to find either C-based refactoring tool or write mine and then need to spell comments, by either finding an application or, also, writing mine.

So, now, I need:

1. Refactoring tool, to refactor C sources.
2. Comments speller tool, to spell source code comments.
3. Mediawiki 2 Docbook 2 MonoDoc, to allow browsing current manuals and tutorial in MonoDoc.
4. MonoCanvas, yes! I haven’t yet finished this! Need it NOW!

A lot of free software to write.

Months ago I succed booting QNX6 with GRUB, to allow booting both Debian and QNX6. GRUB’s manual says it all, however a minor change was needed to acomplish this task.

grub> rootnoverify (hd1,1)
grub> makeactive
grub> chainloader +4
grub> boot

I never put bugs in my programs[1]. – Anonymous (or at least I haven’t yet found author’s name) –

I’m very close to finish QNX to Linux porting, am preparing my early adopted source code to debug and improve, of course using gdb, valgrind and strace. I love squashing bugs!

Nowadays I’m using Ubuntu Edgy on the desktop, and Debian Sid on the laptop, I use Banshee for iPod sychronizing in both computers, however, after upgrading Banshee to 0.11, everything seems to be too slowly, loading takes forever and switching between playlist drives my crazy, I’ve opened a bug telling this. I’m not the only only facing this problem, Carlos has this problem too, so I’m not crazy.

Meanwhile will use Amarok, looks very nice, has a lot of options, is iTunes-like, and seems to work with my device.

Recientemente estoy buscando reactivar la comunidad hispana del proyecto Mono, hay temporadas que las contribuciones aumentan y otras que no, lo sé, escribir documentación es una tarea pesada, pero realmente necesaria, documentar es primordial, aunque tengas la mejor aplicación o API, con el mejor rendimiento, el mejor diseño y este escrita limpiamente, si esta no está documentada, básicamente no sirve.

Hay cosas por hacer, por mientras he abierto en Forge Novell un proyecto relacionado a esto, claro del mismo nombre, monohispano, no se que ocurre en Hispalinux, pero los servidores CVS estan muriendo poco a poco, el de LuCAS lleva ya así desde algunos años, el wiki va de la misma forma y parece que ya no quedan administradores con los cuales poder hablar. No se cual sea el futuro, igual y me equivoco, pero mientras planeo que se utilice el SVN del proyecto además del Bugzilla.

Siento que lo más interesante de esto es la propuesta de crear una aplicación que permite transformar de formato MediaWiki a Docbook, y luego de ese a formato MonoDoc, eso, sin duda sería fantástico, los tutoriales actualmente escritos podrían ser agregados al Monodoc y todo estaría integrado de una forma fantástica. Sin duda le daré una hojeada a eso, he encontrado algunas aplicaciones que parecen realizar eso, html2wiki y html2wikipedia, parece que la ultima podría servir de base para poder lograrlo, hay que tomarse un tiempo porque a futuro esto sería de total utilidad.

Mono includes Mono.Unix.Native, so flagging is made easy:

using System;
using System.Runtime.InteropServices;

public unsafe static void Main (string []args)
{
int int_sizeof = sizeof (int) * 22;
SharedMemory m = new SharedMemory ();
IntPtr filedes = SharedMemory.Open ("myregion",
OpenFlags.O_CREAT | OpenFlags.O_RDWR,
FilePermissions.S_IRUSR | FilePermissions.S_IWUSR);
int res = SharedMemory.FTruncate (filedes, int_sizeof);
byte* len = SharedMemory.MMap (0, int_sizeof,
MmapProts.PROT_READ | MmapProts.PROT_WRITE,
MmapFlags.MAP_SHARED, filedes, 0);
Console.WriteLine ("Open: "+filedes+" FTruncate: "+
res+" v "+(len!=null));
}
}
}

Above example is a quick port of the OpenGroup example. There’s still missing the “real writing“. Compile with:

mcs -unsafe SharedMemory.cs -out:SharedMemory.exe -r:System.dll -r:Mono.Posix.dll

Don’t forget to do

ls -la /dev/shm

to see your shared memory mapped file.

Due to the problem at hotel, I needed to buy a scanner because of need to scan tickets send “real” signed letter to the bank… and I did it and did it wrong, bought a non-supported one! Why the hell didn’t read the compatibility list!!

If there’s no other option, will hack the SANE backend to use my not supported scanner.