I recently experienced a minor run-in with dpkg-deb. My system tells me, that

$ uname -a
Linux hoazin 2.6.28-16-generic #55-Ubuntu SMP Tue Oct 20 19:48:24 UTC 2009 i686 GNU/Linux

which seems to indicate that the Architecture field of the DEBIAN/control file should read ‘i686‘. Doing this results in the error:

deb Error: Wrong architecture 'i686'

Dismembering official packages reveals ‘i386‘ as the correct value.

This post is meant to be a “101″ for identifying byte signatures for the PPC version of WoW!  This post will make the assumptions that you have/are using:

• IDA Professional (running on Windows)
• IDA Plugin: PatterMaker by Ostapus (install into your IDA plugins folder)
• WoW 3.2.2a Binary
• You have an offset already

Step 1: Fire up IDA and select the 3.2.2a binary!

Open up IDA Pro and click Go, then File->Open and choose your binary (you will need to select all files).  Once you have selected the WoW 3.2.2a binary, you need to make sure you choose the PowerPC version vs. the I386.  You have both options since OS X supports Universal Binaries, but we’re only going into PPC during this “lesson.”

Step 2:  Grab a beer

Now we have to wait for IDA to process the binary, will usually take in between 5-10 minutes.  You’ll now it’s complete when the orange arrow stops jumping around in the bar or when the log says “The initial autoanalysis has been finished.”

Step 3: Jump to your offset

For this guide we’re going to use the Object List Manager offset 0×11D76CC.  So click Jump at the top and choose “Jump to address” and type in our offset.

Now we’re viewing that memory location in the binary!

Step 4: Find functions that reference this location

Now we want to see what other sections in the binary reference (or point to) this address.  To do this, simply right click on dword_11D76CC and choose “Jump to xref to operand…”

You’re now viewing a list of places that reference 0×11D76CC!  Woohoo almost there! Go ahead and choose the first reference in the list:

Step 5: Create our byte mask/signature

Now we’re viewing a function that is referencing the object list manager pointer (0×11D76CC). Now we can create a byte signature!  To do this, first we should enable  opcode bytes being shown.  Click Options -> General at the top and set the “Number of opcode bytes” to 4 (for I386 I would set this to 8).

Now lets highlight the bytes for this function. It is NOT important to select all of the bytes here, but we want to select enough so that we get a unique “footprint” of this function.  Basically by creating a byte signature we are actually creating a signature (footprint) for a given function. We are making the assumption that when new patches are released for WoW the structure of this function will not change (but the offset will).  This signature will help us find the function, and then extract the offset  So back to selecting it, make sure you select enough that actually contains the offset!

You’ll notice the offset is actually underlined in red!  These are the bytes we will always want to pull out from the signature, then we have the offset!  (On I386 the offset will be within one instruction vs. over a few as in PowerPC, this is due to PowerPC instructions being limited to 32-bits)

Step 6: Set up our mask for our signature!

Now to actually get our mask + signature on screen (make sure the text is still selected!) go to Edit -> Plugins -> Pattern Maker.  If you don’t see the pattern maker it’s because you didn’t install it in your IDA Plugins folder!  You should now see the signature:

The mask is NOT CORRECT.  For Intel it would be, but the plugin wasn’t created for PowerPC.  So now we need to do this ourselves!  It’s actually quite simple, we’ll slowly move from one opcode to the next from left to right then whenever we see part of the offset we’ll replace that corresponding x in the mask with a ?  See:

\x3C\x40\x01\x1D\x38\x60\x00\x00\x38\x80\x00\x00\x80\x42\x76\xCC\x2F\x82\x00\x00\x4D\x9E\x00\x20\x80\x62\x00\xBC\x80\x82\x00\xC0\x4E\x80\x00\x20
xx??xxxxxxxxxx??xxxxxxxxxxxxxxxxxxxx

There should be 10 x’s in between the ?’s as there are 10 opcodes between \x01\x1D and \x76\xCC in the signature.

Congrats! You now have your byte mask and signature! So now I recommend you find them for the rest of the offsets in Pocket Gnome so I don’t have to

Genç yaşlı herkesin sevgilisi Ubuntu’nun 9.04′ten bir sonraki 10.04′ten bir önceki adımı olan 9.10′un nihai sürümü çıktı.  Henüz denemedim ama fazla bir yenilik yokmuş galiba arayüzde falan. Gnome ayarlarını kontrol etme imkanı sağlıyormuş. Bir de Pidgin yerine Emphaty varsayılan mesajlaşma aracı olarak geliyormuş. Videolu chat açısından iyiymiş. Neyse linkler:

Download Ubuntu 9.10 (x86) 32-bit

Download Ubuntu 9.10 (x64) 64-bit

Definetely one my pet peeves about Windows Installer is how it deals with instruction set architectures (ISAs). Looking at Windows NT history, supported ISAs have come (amd64, IA-64) and gone (Alpha, PowerPC, MIPS) — yet most of the time, there was more than one ISA being officially supported. Having to ship binaries for multiple ISAs therefore always has been on the agenda for many ISVs.

Needless to say, supporting multiple ISAs requires special consideration when developing setup packages and providing separate packages — one for each ISA — has become common practice to approach this. This approach makes perfect sense: Given the incompatibility of most ISAs, nobody needs Alpha binaries on a MIPS system or amd64 binaries on a IA-64 machine, so there seems little reason to mix ISAs within a single package.

Unsurprisingly, Windows Installer, which was created somewhere around 2000, also goes this route and encourages developers to provide separate packages for each ISA.

However, with the advent of amd64/x64/IA-32e/Intel 64/whateveryoucallit, the situation has changed: Because i386 and amd64 are so closely related and compatible, there are now plenty of situations where combining binaries of differing ISAs (i.e. amd64 and i386) in a single installer package makes perfect sense. Examples for this include:

• A package comprises a shell extension as well as a standalone App. For certain reasons (maybe the use of VB6), there only is a 32 bit version of the App. The shell extension, in contrast, is available for both, i386 and amd64. Whether you put everything into one package or provide separate packages for each ISA, one of them will comprise a mixture of ISAs.
• SDKs for unmanaged code usually include .lib and .dll files for multiple architectures. Shipping separate packages for i386 and amd64 (containing different binaries but the same headers, docs, etc.) may please the Windows Installer gods, but seems redundant, a waste of disk space, and user-unfriendly.

Thanks to the msidbComponentAttributes64bit flag, mixing architectures in a single MSI package is technically possible: You mark the package as being 32 bit and set said flag for all 64-bit components. Rather than splitting your setup into multiple packages, you can conveniently combine everything into one.

When reading the documentation (and ICE requirements, more on this later) carefully though, it turns out that this is not quite what the Windows Installer team invented this flag for. Anyway, it works fine, problem solved.

Hmmm…

If only there was not ICE80.

ICE80, alas, is critical if you intend to conform to the Requirements for the Windows Vista Logo Program for Software:

Applications must use the Windows Installer (MSI) or ClickOnce for installation. Windows Installation packages must not receive any errors from the Internal Consistency Evaluators (ICEs) listed here:

1-24, 27-31, 33-36, 38, 40-57, 59, 61-63, 65, 67-72, 74-84, 86-87, 89-94, 96-99

ICE80 mainly states that (1) you should not install 64 bit components to 32 bit directories (e.g. Program Files vs. Program Files (x86)) and (2) you should not use 64 bit components in a 32 bit package.

(1) is fair enough, although it raises the question where you should install your software to without splitting it in two or violating other ICE rules. Worse yet, (2) effectively means that said way to create multi-ISA packages, creating 32 bit packages with some components marked with msidbComponentAttributes64bit, is illegal alltogether.

So to be logo’ed, there seems to be no other way than providing separate packages, maybe along with (urgh!) a meta-package that installs the other two.

If there are more important things on your schedule than getting a Vista logo, ICE80 seems like something that can safely be ignored. Indeed, this is what I have done several times, including in case of the cfix installer.

Anyway, let’s ignore ICE80 once more and hold on to the plan of building a 32-bit package containing both, 32-bit and 64-bit components.

Urgh…

For an SDK that is installed on 64-bit Windows, it will usually make sense to install both, 32 and 64 bit .lib and .dll files etc. On 32-bit Windows, installing 64-bit components may seem odd, but due to the existence of amd64 compilers for i386, it still makes sense to install them or at least offer them as optional feature.

So far, so good. Things get interesting, though, when COM registration comes into play. Naturally, a 32 bit installer package sees the system like any other 32 bit application does. Most importantly, this means that Registry Reflection and File System Redirection applies.

Now consider a package that contains both a 32-bit and a 64-bit version of some COM server, each installed to a separate directory. COM Registration either be performed through the Class or the Registry table. Provided that the msidbComponentAttributes64bit flag has been used properly, such a package will work great on 64 bit systems thanks to Registry Reflection: The regsitry entries will be written to the proper (reflected) locations and both COM servers will work properly.

Now think what happens on 32-bit Windows: (1) There is no Registry Reflection and (2) Windows Installer silently ignores msidbComponentAttributes64bit flags. Result: The installation will run just as smooth as on the 64-bit system. However, while installing the files continues to works flawlessly, the registry will be left in a less-than-optimal state: Due to the nonexistence of Registry Reflection, the registration entries of both COM servers will have been written to the same location!

Needless to say, the server whose registration entries were written first will now be unusable.

In a way, Windows Installer has taken its revenge for breaking the rules.

Bottom line: Mixing 32 and 64-bit components in a single MSI works fine in many cases, but is against the MSI rules and can lead to further problems. And while I am still convinced that providing separate, ISA-specific packages is wrong or at least inconvenient in certain situations, it is definitely the safer and “right” way to go.

(Note: Windows Installer 4.5 introduced multi-package transactions, which allow reliable and transactional multi-package setups to be built so that splitting a setup into multiple packages can be implemented without much pain. However, very few users already have Windows Installer 4.5 installed and Windows 2000 is not even supported by this release. For many of us, relying on this feature therefore is not really an option.)

This post will guide you to obtain your product key when you accidentally misplaced it.

1. Insert your Windows CD in CD-ROM.

2. Open the CD in Windows Explorer.

3. Open the I386 folder, and find the Unattend.txt file.

4. Double click the Unattend file, your product key is written under User Data.

You can also locate the unattend file easily by Right clicking the CD-ROM then choose Search, then type unattend.txt.

David vs Goliath

With Google finally announcing its very own Operating System – the Chrome OS on 7th of July, the IT industry is all set to witness yet another attack on Microsoft’s monopolistic fortified empire. Initially, Google plans to launch it for netbooks before moving on to the larger desktop PC and laptop market which is dominated by Microsoft’s Windows Operating Systems.

It is not the first time that Microsoft is facing competition in the Operating System market. Various flavours of Linux have been around for a while and are doing pretty good in the server domain. With the advent of the Mac OS for i386 environments, it was believed by many of those typical ‘Mac lovers’ that now Microsoft would surely have a run for its money. But neither Linux, nor the Mac have been really able to topple the Windows reign. This phenomenal success of Windows should not, in any case, be attributed to the R&D teams at MS, definitely not (how many BSODs have you faced!). It is the sales and marketing policy of Microsoft that keeps its Windows operating system at the pinnacle of this industry.

But this time, the game is a li’l different. On the other side of the court is not Linux, nor Apple; it’s Google – the behemoth who has proved itself time and again. Google revolutionised the web with its innovations at Google search. JavaScript and Ajax implementations of Gmail propelled yet another success story of Google. Google Docs are already a preferred choice of many netizens over the heavily priced MS Office suite. Orkut, YouTube, Blogger, Picasa, Google Earth, Apps, and many many more applications and services have redefined our entire web experience. So can we say that David has finally arrived confronting the long standing Goliath of the Operating System industry?

I have my set of doubts. Google’s domination of the web has been in all those areas which were earlier dominated either by Yahoo! (search, mail) or some other player; but not Microsoft. Even after about nine months of the launch of Google Chrome browser, it has not been able to challenge the market domination of Microsoft’s Internet Explorer or even the second place Firefox. We have also seen that Google’s services like Orkut have been vanquished by rivals like Facebook and MySpace.

Apart from this, my other doubt arises from the history of Google’s antagonist. Microsoft is known to be a fighter. Since its inception, it has fought and won bitter battles against big names like Apple, Netscape and even the mighty IBM. So Google and its Chrome OS have a tough opponent up front.

It’s not that my doubts arise only from these historical aspects of the two companies. There are certain technical aspects where Microsoft seems to have an edge over Google. Chrome is purely based on Cloud Computing which leaves me with a good for nothing rectangular piece of keys and screen which i may deter to call a ‘netbook’ in case of unavailability of a hi-speed broadband connection to the Internet, which is not such an uncommon scenario in most parts of the world! Although many Paul Buchheits may remind me of the famous “Don’t be Evil” quote of Google, i can never accept my prized possession – my personal data to be at the mercy of the Google Cloud and its ‘Privacy Policy’. For the developers, Google says that “the web is the platform”. Keeping in mind the huge numbers of application developers already working on the available platforms, does this insight look viable! Not in the near future for me!

And what about hardware and software support?! Being based on the Linux Kernel and Cloud Computing, i doubt Chrome OS to support my printer, scanner, camera, flash drives and memory cards as smoothly as Windows does after being 100% sure that it will not be able to run my trusted software and games! (Don’t remind me of WINE, plz!)

Then they tell me that Chrome OS will be based on the Linux Kernel with a new “windowing system”. Quoting the official Google Blog “….and we’re definitely going to need a lot of help from the open source community to accomplish this vision.” All this sounds familiar, isn’t it? Why not! Isn’t Chrome a Cloud implementation of Linux?! So what difference does it make to Microsoft when what actually it is facing is nothing but yet another Linux, only this time, it has a Cloud to back it up and is labelled Google!

But this one fact can ultimately bring all the difference to the equation. It is labelled Google and in the IT industry, when it’s Google, it’s got to be something big and surely something to contend with. Both Microsoft and Google have been leaders of two different playing fields as of now. This confrontation was surely on the cards and when now both of them find each other on their faces, mind my words, “there will be blood!”

Will the Google David bring down Microsoft or will the Goliath annihilate yet another adversary? It’s going to be really big this time!

¿Sabías que podés probar Linux sin tener que instalarlo ni cambiar nada en tu computadora? Algunas (por suerte cada vez son más) distribuciones de Linux se pueden probar e instalar desde un Live CD

¿Qué es un Live CD y dónde lo consigo?

Un Live CD es un cd o un dvd que adentro tiene una distro de Linux. Al meterlo en la lectora, cuando prenda la computadora me va a preguntar si quiero iniciar desde el CD/DVD. Acá se presentan distintas variantes. Ubuntu, presenta una pantalla con el logo, nos pide que elijamos nuestro idioma y te da la opción de “Probar Ubuntu sin alterar su equipo”, otras distros directamente te muestran la pantalla de inicio de sesión. La información con la que se debe iniciar sesión probablemente se encuentre en la página donde conseguimos el Live CD

Una vez que apretamos enter la primer opción (o nos logueamos, según la distro) va a aparecer el escritorio. En él podemos probar todas las aplicaciones que vienen preinstaladas y explorar el sistema. Aprovechen para toquetear, conocer, probar…. total no pueden romper nada! (bueno, sí, poder pueden pero sería bastante difícil)

Si decidimos instalarlo, suele aparecer en el escritorio un icono que dice “Instalar”. Al hacerle doble click se va a iniciar el proceso guiado de instalación. Hoy por hoy, en Ubuntu 9.04, les juro que este proceso no lleva más de 20 minutos -con toda la furia, eh-

Y ahora, lo que todos esperaban… ¿dónde lo consigo? Por lo general en las páginas de cada distribución aparece un link para bajarlo, y suelen especificar cuál es el live cd.

Tengo muchas opciones ¿cuál bajo?

Que haya tantas versiones con letritas y números raros suele asustar, lo importante es no entrar en pánico! Para saber cuál tengo que bajar tengo que saber cuál es la arquitectura de mi procesador. Sí, sí, ya sé que suena difícil pero les juro que no lo es. Si usan Windows, botón derecho en Mi PC, Propiedades, y en la ventanita que les aparece busquen el procesador que tienen. Pueden tener Intel o AMD de 32 o 64 bits. Además, pueden tener más de un núcleo (si es una máquina relativamente nueva, probablemente tengan un Dual Core – Core 2 Duo, X2, depende de la marca y modelo.

(Esta parte es aburrida pero necesaria)

Probablemente tengan que usar alguna de estas:

• Intel x86 / IA-32 (“i386″): soporta todos los procesadores IA-32, hechos por Intel (incluyendo todas las series de Pentium y las recientes máquinas Core Duo en modo de 32 bits), AMD (K6, todas las series de Athlon y las series Athlon64 en modo de 32 bits), Cyrix y otros fabricantes. Resumiendo, este es masomenos universal y sería muy raro que no les ande, aunque no es el mejor para todas las plataformas.
• AMD64 (“amd64″) o x86_64: Adaptación a los procesadores de 64 bits AMD64. El objetivo es soportar espacios de usuario tanto de 32 como de 64 bits en esta arquitectura. Esta adaptación permite usar los Opteron de 64 bits de AMD, los procesadores Athlon y Sempron, y lo procesadores de Intel con soporte EM64T, incluyendo Pentium D y varias series de Xeon y Core2. Si quieren leer más sobre el asunto este de los procesadores de 64 bits, en éste artículo de la Wikipedia hasta te tira los nombres de los modelos de procesadores y todo.

Yo tengo un Intel, ¿Qué es eso de EM64T?

No viene al caso qué es puntualmente lo que significan las siglas, pero los procesadores Intel que tienen soporte EM64T son:

• Intel Xeon (algunos modelos desde ‘Nocona’)
• Intel Pentium 4 (modelos serie 500, 600′)
• Intel Pentium D
• Intel Pentium Extreme Edition
• Intel Celeron D
• Intel Core 2 Duo (Conroe, Allendale)
• Intel Core 2 Quad (Conroe, Kentsfield)

Ok, me bajé el .iso, ¿ahora qué hago?

Tienen que grabarlo en un cd o dvd (según correponda), utilizando su programa preferido. Para ver exactamente cómo se hace, acá les dejo la búsqueda en Google. Una vez grabado, reinicio la computadora con el cd/dvd puesto en la lectora y ahí es cuando empieza la magia.

El equipo de desarrollo CentOS se complace en anunciar la disponibilidad de CentOS 5.3 i386 Live CD.

Este CD se basa en nuestra CentOS-5.3 i386 distribución.

Se puede utilizar como un trabajo, con el siguiente software:

# Openoffice.org 2.3.0
# Firefox 3.0.6
# Thunderbird 2.0.0.18
# Pidgin 2.5.5
# Xchat 2.6.6
# Gimp 2.2.13

También se puede utilizar como un CD de rescate con las siguientes herramientas:

# Memtest86 + -1,65
# Set completo de LVM y RAID de herramientas de línea de comandos
# Nmap y NMapFE
# Traceroute
# Samba-3.0.33 cifs con el soporte del kernel de Windows para conectarse a recursos compartidos de archivos
# Visor de Sistema de Registro de
# GUI del Administrador de dispositivos de hardware

Los siguientes paquetes fueron retirados para llegar a la meta 700. Puede instalar de nuevo utilizando el “yum install ‘comando mientras se ejecuta bajo el LiveCD medio ambiente:

# Emacs
# K3b
# Scribus

================================================== ==============

El proyecto CentOS Live CD página está aquí:
https: / / projects.centos.org / trac / livecd /

Los scripts de creación de Live CD, capturas de pantalla, arrancar desde una llave USB, la creación de Live CD personalizado y otra información se encuentra disponible allí.

================================================== ==============

El CentOS 5.3 i386 Live CD se basa en el de Fedora livecd-tools proyecto:

http://fedoraproject.org/wiki/FedoraLiveCD

================================================== ==============

Puede obtener el CentOS 5.3 i386 Live CD de la CentOS espejos:

http://isoredirect.centos.org/centos/5/isos/i386/

* Nombre del archivo: CentOS-5.3-i386-LiveCD.iso
* Tamaño: 691MB
* Md5sum: 54bc01353cc67c4ddfaa7f1bc3b75c0e
* SHA1Sum: 4d01884a67d585b9431336a6db39f7ec66dddc47

================================================== ==============

Notas:

LiveCD Notas:

http://wiki.centos.org/Manuals/ReleaseNotes/CentOSLiveCD5.3

CentOS-5.3 Notas:

http://wiki.centos.org/Manuals/ReleaseNotes/CentOS5.3

Notas de aquí arriba:

http://www.centos.org/docs/5/html/release-notes/as-x86/index.html

CentOS-5 Documentación está aquí:

http://www.centos.org/docs/5/

================================================== ==============

El proyecto CentOS gustaría agradecer a Patrice Guay para la creación de este CD. Patrice CentOS-5/LiveCD dirige el proyecto y ha contribuido mucho tiempo y esfuerzos en crear y trabajar con el LiveCD de la CentOS-5.

También queremos dar las gracias al equipo de QA CentOS para probar este LiveCD y sus muchas sugerencias para mejorarlo.

================================================== ==============

Para estar al día con CentOS:

Visite nuestro sitio web en http://www.centos.org/

Únete a la lista de correo de CentOS:

http://lists.centos.org/mailman/listinfo/centos

Captura en el Wiki http://wiki.centos.org

Formar parte de diversos miembros del equipo en el IRC en irc.freenode.net # CentOS-devel

================================================== ==============

Y, por último, estamos ante una importante actualización para la próxima versión de la CentOS 5 LiveCD, y están tomando en las ideas, sugerencias y contribuciones para este código. Si tienes alguna idea, hacer venir y hablar con nosotros!

================================================== ==============

Disfrutar,

El Equipo de Desarrollo de CentOS

Vista en: | Lista CentOs

Buscando por ahí me encontré con estos archivos…

Son los links para descargarse el REDHAT en su última versión, la 5.3.

http://rapidshare.com/files/187725338/RHEL-Server-5.3-i386-DVD-ISO.part01.rar

http://rapidshare.com/files/187725342/RHEL-Server-5.3-i386-DVD-ISO.part02.rar

http://rapidshare.com/files/187731585/RHEL-Server-5.3-i386-DVD-ISO.part03.rar

http://rapidshare.com/files/187731591/RHEL-Server-5.3-i386-DVD-ISO.part04.rar

http://rapidshare.com/files/187735817/RHEL-Server-5.3-i386-DVD-ISO.part05.rar

http://rapidshare.com/files/187735822/RHEL-Server-5.3-i386-DVD-ISO.part06.rar

http://rapidshare.com/files/187745773/RHEL-Server-5.3-i386-DVD-ISO.part07.rar

http://rapidshare.com/files/187752273/RHEL-Server-5.3-i386-DVD-ISO.part08.rar

http://rapidshare.com/files/187752276/RHEL-Server-5.3-i386-DVD-ISO.part09.rar

http://rapidshare.com/files/187756315/RHEL-Server-5.3-i386-DVD-ISO.part10.rar

http://rapidshare.com/files/187756320/RHEL-Server-5.3-i386-DVD-ISO.part11.rar

http://rapidshare.com/files/187767512/RHEL-Server-5.3-i386-DVD-ISO.part12.rar

http://rapidshare.com/files/187767518/RHEL-Server-5.3-i386-DVD-ISO.part13.rar

http://rapidshare.com/files/187775671/RHEL-Server-5.3-i386-DVD-ISO.part14.rar

http://rapidshare.com/files/187775678/RHEL-Server-5.3-i386-DVD-ISO.part15.rar

http://rapidshare.com/files/187779973/RHEL-Server-5.3-i386-DVD-ISO.part16.rar

http://rapidshare.com/files/187779982/RHEL-Server-5.3-i386-DVD-ISO.part17.rar

http://rapidshare.com/files/187785877/RHEL-Server-5.3-i386-DVD-ISO.part18.rar

http://rapidshare.com/files/187785883/RHEL-Server-5.3-i386-DVD-ISO.part19.rar

http://rapidshare.com/files/187792676/RHEL-Server-5.3-i386-DVD-ISO.part20.rar

http://rapidshare.com/files/187792679/RHEL-Server-5.3-i386-DVD-ISO.part21.rar

http://rapidshare.com/files/187800475/RHEL-Server-5.3-i386-DVD-ISO.part22.rar

http://rapidshare.com/files/187800481/RHEL-Server-5.3-i386-DVD-ISO.part23.rar

http://rapidshare.com/files/187805129/RHEL-Server-5.3-i386-DVD-ISO.part24.rar

http://rapidshare.com/files/187805133/RHEL-Server-5.3-i386-DVD-ISO.part25.rar

http://rapidshare.com/files/187809607/RHEL-Server-5.3-i386-DVD-ISO.part26.rar

http://rapidshare.com/files/187809613/RHEL-Server-5.3-i386-DVD-ISO.part27.rar

http://rapidshare.com/files/187811045/RHEL-Server-5.3-i386-DVD-ISO.part28.rar

Pueden descargarlo todo, es una imagen *.iso de un DVD, creo que son 3 Gb.

As of Linux kernel 2.6.x, the official maximum filesystem size for a 32-bit ( i386 ) host ext3 file system was 4TB (or, seemingly, 8TB as of kernel 2.6.17).

However, as of linux kernel 2.6.19, the 32-bit ext3 maximum size appears to be 16TB.

Đây là thư mục I386 trong đĩa Windows XP cho những bạn muốn cài đặt ngôn ngữ tiếng Việt cho WinXP mà không cần đĩa CD. Chỉ cần down về và khi được yêu cầu chỉ cần Browse đến thư mục vừa down.
Download I386

==================================================================================

Đối với người sử dụng Windows là người Việt Nam, khi sử dụng các chương trình, phần mềm để nhập hoặc xem các văn bản tiếng Việt thường phải đồng bộ hóa hệ điều hành mình đang xài mới có thể xem, nhập tiếng Việt vào được. Hiện giờ các chương trình, phần mềm đều đã hỗ trợ tốt cho ngôn ngữ Việt nhưng có những lúc người dùng sẽ gặp trở ngại đối với các chương trình không hỗ trợ.

Để đồng bộ hóa Windows XP, ta vào Control Panel > Regional and Language Setting > vào tab Language đánh dấu check vào 2 dòng:

• Install files for complex script and right-to-left languages (including Thai)
• Install files for East Asia languages

Để cài đặt, nó sẽ yêu cầu ta bõ đĩa CD Windows XP vào. Nhưng nếu bạn không có đĩa XP thì có thể download ở đây rồi khi báo thiếu file chỉ cần Browse vào thư mục vừa down (nhớ extract file nén trước).

Pour essayer une distribution de linux vous avez un choix immense – il suffit d’aller sur net pour en trouver plein: http://en.wikipedia.org/wiki/Comparison_of_Linux_distributions . Avant d’en choisir une il faut se poser juste quelques questions:
- ce quoi l’architecture de votre ordi? Autrement dit, si c’est un model récent vous n’aurez pas de problème d’en choisir le juste, à savoir la version qui se nomme “pc standard” ou “x86″ ou “pc32bit” ou encore “i386″. C’est pour faire simple. Il y a souvent plusieurs distributions, comme c’est le cas de debian.
- essayer ou installer? Très souvent vous pouvez télécharger une version qui se nomme “LiveCD”. Ainsi sans l’installer vous pouvez l’essayer en démarrant avec comme si vous étiez sous linux Par la suite il est possible de l’installer si vous êtes satisfaits de votre nouvelle acquisition.
- essayer plusieurs distributions avant d’en adopter une? Décidément oui. Chacune a des inconvénients, voire des incompatibilités avec votre matériel. Et j’en passe la liste des choses à vérifier. Je ne citerai que la carte audio, video, wifi, port usb… La liste serait longue mais c’est à vous de décider ce qu’il vous convient le plus.

Aunque esto lo he realizado más como prueba que como otra cosa, es posible que sea necesario compilar un paquete como 32 bit desde un sistema corriendo un linux en arquitectura AMD64.

En sí el tema no es complicado, aunque no siempre será posible hacerlo, al menos de una manera sencilla. Al compilador gcc se le puede pasar como parámetro -m32 para indicarle que el código generado es de 32 bit y ha de ser linkado con las librerías de 32 bit. Aquí es donde realmente puede aparecer el problema, ya que no siempre es posible tener a mano las librerías de desarrollo de 32 bit en tu sistema (por poner un ejemplo, SDL).

Por cierto, es necesario instalar la librería libc6-dev-i386 (según Ubuntu, comprobar el nombre en otras distribuciones) para evitar el mensaje molesto del stub:

error: /gnu/stubs-32.h: No such file or directory

En mi caso de prueba he escrito el siguiente código en el fichero main.c:

#include <stdio.h>

int main(int argc, char *argv[])
{
printf(“Prueba de compilación\n”);
return 0;
}

También he creado un archivo Makefile:

CC = gcc
CFLAGS32 = -Os -s -m32
CFLAGS64 = -Os -s

exec32: main32.o
$(CC) main32.o -o exec32 $(CFLAGS32)

exec64: main64.o
$(CC) main64.o -o exec64 $(CFLAGS64)

main32.o: main.c
$(CC) $(CFLAGS32) -c main.c -o main32.o

main64.o: main.c
$(CC) $(CFLAGS64) -c main.c -o main64.o

clean:
rm -f main32.o exec32 main64.o exec64

Lanzamos las siguientes órdenes:

make exec32

make exec64

y obtenemos sendos ficheros ejecutables, uno de 32 bit y el otro de 64. Comprobamos con la utilidad file.

file exec32

exec32: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.6.8, dynamically linked (uses shared libs), stripped

file exec64

exec64: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), for GNU/Linux 2.6.8, dynamically linked (uses shared libs), stripped

Podemos comprobar los tamaños de los archivos:

ls -l exec*

-rwxrwx— 1 root plugdev 5660 2009-03-10 12:04 exec32
-rwxrwx— 1 root plugdev 6400 2009-03-10 12:04 exec64

Una buena diferencia, creo yo… y eso que he utilizado -s para reducir el tamaño del ejecutable.

You can download the image here.

Bueno, aparezco para revivir el blog luego de una gran ausencia (me tuvieron que recordar que tenia blog XD) y vengo a poner una guia de como instalar la canon pixma IP1800 en debian, he visto muchos otros tutos que hay en internet, pero se aplican a ubuntu (versiones antiguas) y ya no aplican a debian, aqui esta lo que se necesita para hacerla funcionar:

1-Ingredientes:
apt-get install lo siguiente:
-cups
-foomatic-db
-gutenprint
-un navegador web.
-alien

####Edicion 12-02-09 #######
Las dependencias de los paquetes ya convertidos son estas:
apt-get install libc6 libcupsys2 libgtk1.2

2- Paso 1: bajarse el driver de la pagina de canon (rpm)
cnjbfilter-1800series.rpm
cnjbfilter-common.rpm

3- Instalar drivers
Primero generamos los debs para poder instalar con dpkg

alien -kc cnijfilter-common-2.70-1.i386.rpm
alien -kc cnijfilter-ip1800series-2.70-1.i386.rpm

luego instalamos los debs resultantes:

dpkg -i *.deb

4-Instalar la impresora:
Ahora entramos en la configuracion de cups, conectamos nuestra impresora al port de usb y luego vamos al navegador web y ponemos esta direccion:

http://localhost:631/

Esa es la direccion del servidor cups con el cual instalaremos la impresora, (esta forma es independiente del entorno de escritorio y del window manager).

Damos click al boton de “añadir impresora” y luego se nos preguntara el nombre, lugar y descripcion de la impresora (pueden poner lo que quieran aqui).

Luego nos preguntara cual es el tipo de impresora, veran (si se instalo correctamente el driver) que ya sale una etiqueta con el nombre de la impresora, la seleccionamos y vamos al fabricante “canon”, luego al driver “Canon IP1800″ y luego de esto nos pedira el user y contraseña “root y la pass de root” luego si todo funciono dira que la impresora ha sido agregada y podran probar imprimiendo la pagina de prueba.

Por el momento no hay un driver para amd64, y este servidor no ha intentado instalarla de ese modo (:p) asi que por momento esta impresora solo puede funcionar en 32 bits (si alguien ya la ha instalado en amd64 favor deje su comentario).

In the last message I discussed selecting the branch that might best suit our needs.   Today I am going to focus on making sure we have the right architecture.  Very simply, this is probably i386 for most people.  But you should understand a little about them all so that you can decide which of these is applicable to your situation.  So, let’s get started at the top of the list.

ALPHA
If you have a machine based on the ALPHA architecture, then you should know that as of 7.0 FreeBSD no longer supports the DEC Alpha.  This was a 64-bit setup that has since been replaced by versions from AMD and INTEL, and thus is not a mainstream product line.    Support is provided through version 6, however, and can be expected until the 6.x branch is retired.

AMD64
This is a growing architecture.  This category, which I will be using, is for those computers that are capable of 64 bit processing.  One important note for INTEL and AMD 64 bit processors and motherboards, you really need to go and check the compatiblity list to be sure that your motherboard is supported.   If not, you should probably stay with the i386 family to be sure that your system will be stable.

i386
This architecture encompasses most every PC.  If you’ve purchased a computer from a big name manufacturer such as Dell, Compaq, HP, or Gateway, then you have this architecture.  This is a 32 bit operating system, much like your current version of Windows.  Unless you are running a much older PC, like an old 80386 processor.  If that is the case, then as of 7.0 your processor is not supported.  The 6.x branches will support your processor though until retired.

ia64
This is INTEL’s 64 bit Itanium processor family.  This particular port is, as of this writing, still a tier 2 platform.  Although from what I can tell, it seems as if that is basically in name only.  What’s a tier 2 platform?  The BSD project breaks each architecture port down by how much support it will receive.   Here’s a quick rundown of the different tiers:

• Tier 1 – Fully supported system.  i386 is an example of a fully supported architecture port.
• Tier 2 – Mostly supported systems.  Not all ports or packages may work with them, but most should.  ia64 is an example of this level of support.
• Tier 3 – An experimental architecture.  This level denotes new architecture or older architecture that may be phasing out of support.  However, this could also be architecture that is not in widespread use and does not warrant mainstream support at the tier 1 or 2 levels.  MIPS is an example of architecture at this level.
• Tier 4 – Unsupported.  Any architecture that does not fall into the previous categories is completely unsupported by the FreeBSD project.

PC98
The NEC PC-98×1 is the target of this architecture port.  You can read more about this on its wiki page.  It is a tier 1 architecture and is fully supported by the FreeBSD Project.

POWERPC
This is, from what I can tell, the Apple architecture.  If you are on a MacIntosh and you are using OS X, you may already know that you are running BSD.  This port is a tier 2 level architecture and I highly recommend that you read more about it.

SPARC64
This is the FreeBSD architecture port for Sun’s UltraSPARC family of systems.  It has tier 2 support and I recommend that if this system is one that you use, then please read the documentation before committing to installing FreeBSD.

That covers the major players in the FreeBSD Project.  For those who may be interested I will be using the AMD64 installation files, which should not differ greatly from the others.  After all of this we are very close to being ready to install the OS.  Now before moving on to the next article you should start downloading the particular build that you will need.  I want everything so that I won’t have much to download lateron, so I selected the DVD ISO to download.  You can select any that you like, from boot only to the DVD version or in between.  I will discuss what to do with the files in the next aritcle, so feel free to read on if you need to learn a little more before committing.

I was one of several people that downloaded the crossover office and crossover games installers when they had their free download day. They installed very easily on my Fedora 9 laptop and worked pretty well. Today however, I attempted the same installers on my x86_64 Fedora 10 machine and it took some research and work to get it going.

If you try to run the installer, it will say that you do not have an x86 compatible machine and it cannot continue. However, what you can do is install enough i386 libraries to trick the installer into thinking it’s in an x86 environment. After googling through a lot of forums I found some X libraries, and then basically compensated for each error message thereafter.

Here is my (so far) comprehensive list of i386 libraries you need:

glibc-2.9-2.i686
libXau-1.0.4-1.fc10.i386
libXdmcp-1.0.2-6.fc10.i386
libxcb-1.1.91-5.fc10.i386
libX11-1.1.4-5.fc10.i386
libXext-1.0.4-1.fc9.i386
libXi-1.1.3-4.fc9.i386
libICE-1.0.4-4.fc10.i386
e2fsprogs-libs-1.41.3-2.fc10.i386
libSM-1.1.0-2.fc10.i386
libXt-1.0.5-1.fc10.i386
libXpm-3.5.7-4.fc9.i386
libXmu-1.0.4-1.fc9.i386
zlib-1.2.3-18.fc9.i386
libXfixes-4.0.3-4.fc10.i386
libXdamage-1.1.1-4.fc9.i386
libXxf86vm-1.0.2-1.fc10.i386
libdrm-2.4.0-0.21.fc10.i386
mesa-libGL-7.2-0.13.fc10.i386
mesa-libGLw-6.5.1-5.fc9.i386
glitz-0.5.6-6.fc10.i386

Also note that glibc will bark out a lot of errors that i386 conflicts with i686, but it seems to work. A lot of these were pulled as dependencies on others. You can install crossover office with out mesa/glitz libraries but it will complain that you have no OpenGL, so then most games probably won’t work, if not all until you install mesa and glitz for i386.

Enjoy!

——————–

UPDATE

I got sound to work by installing the i386 package for alsa-plugins-pulseaudio.  I also installed the nvidia lib for i386 so my nvidia card would get recognized.  Everything is working now.

Good reference and reading for recent OSX trojans: 

CA Blog: New Trojans Strike OS X 

ArborNetworks: New OS X Malcode: Not Just a DNSChanger

There’s a slight changes on DMG (as graphically shown below), depending on the Remote IP address it’s trying to access. 

Ubuntu 8.10 Intrepid Ibex!!!!, Go Grab It NOW!!!!

Desktop i386: Download

Desktop AMD 64: Download

What Are You Waiting For????? GOOOOOOOOO!!!!