<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress.com" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>minix &amp;laquo; WordPress.com Tag Feed</title>
	<link>http://wordpress.com/tag/minix/</link>
	<description>Feed of posts on WordPress.com tagged "minix"</description>
	<pubDate>Sun, 07 Sep 2008 05:29:47 +0000</pubDate>

	<generator>http://wordpress.com/tags/</generator>
	<language>en</language>

<item>
<title><![CDATA[Installing Minix3 in kvm]]></title>
<link>http://itnomad.wordpress.com/?p=304</link>
<pubDate>Mon, 01 Sep 2008 23:56:40 +0000</pubDate>
<dc:creator>Alexander W. Janssen</dc:creator>
<guid>http://itnomad.wordpress.com/?p=304</guid>
<description><![CDATA[ 
I recently read about the Minix3 release so I thought I&#8217;d give it a try. Since I got a wee n]]></description>
<content:encoded><![CDATA[[caption id="" align="alignleft" width="69" caption=" "]<img src="http://www.osnews.com/img/15925/logo.gif" alt="Minix Logo" width="69" height="60" />[/caption]
<p>I recently read about the Minix3 release so I thought I'd give it a try. Since I got a wee new machine which can do real hardware-virtualisation using kvm/qemu, which works pretty fine with Windows XP, Linux and FreeBSD, I thought to give that new setup a really hard time. I started off installing GNU/Hurd which was a bit of a pain; when I first tried to install it I *really* thought I was installing GNU/Linux - the HURD installtion-routine was even showing off with Tux, the Linux-Penguin! That was kinda... odd.</p>
<p>However, I wanted to give Minix3 a shot and downloaded the official release from their website. This was version 3.1.2a and I thought kvm would do just fine. Unfortunately I ran into the same problem over and over again, trying to give kvm several different parameters all the time.</p>
<p>Thing was that I always got this "Floating exception"-error. After searching on the net quite a lot I basically found out that the new version - 3.1.3a - solves those kvm-related problems.</p>
<p>At the moment it's still installing - doing a bloody badblocks-scan - but later I'll post more details.</p>
<p>Oh, also, on a related note: I had quite some nice vacation the last weeks.</p>
<p><em>Update:</em> Base installation works. Networking doesn't. It's 2AM now, so I'll check that out later.</p>
]]></content:encoded>
</item>
<item>
<title><![CDATA[Interview with Andrew Tanenbaum, Creator of MINIX]]></title>
<link>http://osysnews.wordpress.com/2008/08/13/interview-with-andrew-tanenbaum-creator-of-minix/</link>
<pubDate>Wed, 13 Aug 2008 21:29:12 +0000</pubDate>
<dc:creator>osysnews</dc:creator>
<guid>http://osysnews.wordpress.com/2008/08/13/interview-with-andrew-tanenbaum-creator-of-minix/</guid>
<description><![CDATA[


&#8220;I recently had the opportunity to interview Andrew S. Tanenbaum, creator of the extremely ]]></description>
<content:encoded><![CDATA[<p>
<p><img src="http://osnews.com/images/icons/1.gif" alt="Interview with Andrew Tanenbaum, Creator of MINIX" /></p>
</p>
<p>"I recently had the opportunity to interview Andrew S. Tanenbaum, creator of the extremely secure Unix-like operating sytem MINIX 3. Andrew is also the author of Operating Systems Design and Implementation, the must-have book on programming and designing operating systems, and the man whose work inspired Linus Torvalds to create Linux. He has published over 120 works on computers (that's including manuals, second and third editions, and translations), and his works are known all over the world, being translated into a variety of different languages for educational use universally. He is currently a professor of computer science at Vrije University in Amsterdam, the Netherlands."<br /><!--more--></p>
]]></content:encoded>
</item>
<item>
<title><![CDATA[VIA Nano and Intel Atom Review - Battle of the Tiny CPUs]]></title>
<link>http://wlalng.wordpress.com/?p=69</link>
<pubDate>Fri, 01 Aug 2008 08:15:52 +0000</pubDate>
<dc:creator>thorsenine</dc:creator>
<guid>http://wlalng.wordpress.com/?p=69</guid>
<description><![CDATA[VIA Nano Reference Platform
The mini-ITX platform has officially been adopted by Intel with the Atom]]></description>
<content:encoded><![CDATA[<p><em><strong>VIA Nano Reference Platform</strong></em></p>
<p>The mini-ITX platform has officially been adopted by Intel with the Atom products meaning that the VIA-created standard should actually become a standard now -- good news for all.  For those that haven't seen a mini-ITX motherboard yet you'll be scratching your head at seeing such a compressed design.  There are two DDR2 DIMM slots, four SATA channels, one IDE connection and a single PCI Express x16 slot for graphics or other add-in cards.</p>
<p><img class="alignnone" src="http://www.pcper.com/images/reviews/597/via03.jpg" alt="" width="600" height="400" /></p>
<p>On the back of the reference board are a CompactFlash connection (for some solid-state storage action) and a mini PCI slot as well.  These would be GREAT features to have on a retail board as well - I imagine booting off of an 8GB high-speed CF drive and using a standard drive for storage.<br />
<img class="alignnone" src="http://www.pcper.com/images/reviews/597/via05.jpg" alt="" width="600" height="400" /></p>
<p>The external connections on the VIA reference board include the standard PS/2 connections, USB ports, serial output, dual NICs and VGA output to use in conjunction with the integrated S3 graphics core on the north bridge.  There are audio connections as well on the right hand side that support up to 6-channels of output.<br />
<img class="alignnone" src="http://www.pcper.com/images/reviews/597/via06.jpg" alt="" width="600" height="400" /></p>
<p>Here you can see the VIA 82375 south bridge under a passive heatsink, four SATA channels on the motherboard that all support RAID and the single PCI Express x16 slot that gives the VIA Nano platform such an edge over Intel's Atom for real world user applications.  Without a PCIe slot on the Atom motherboards, OEMs and users are forced to use the inferior integrated Intel IGP or a PCI graphics board, really limiting the possibilities of getting top performance out of the Atom architecture.<br />
<img class="alignnone" src="http://www.pcper.com/images/reviews/597/via07.jpg" alt="" width="600" height="400" /></p>
<p>VIA's reference design supports up to 4GB of DDR2-667 MHz memory though the controller is just single channel.<br />
<img class="alignnone" src="http://www.pcper.com/images/reviews/597/via09.jpg" alt="" width="600" height="400" /></p>
<p>The only power connection on the VIA Nano motherboard is a 20-pin ATX power connector - don't worry your 24-pin power supply connections will work just fine though.<img class="alignnone" src="http://www.pcper.com/images/reviews/597/via10.jpg" alt="" width="600" height="400" /></p>
<p>Under that single large heatsink with the fan on it lies the VIA CN896 north bridge chip and the VIA Nano processor; in our case the CPU is the Nano L2100 which operates at 1.8 GHz on an 800 MHz front-side bus with a max TDP of 25 watts. The north bridge handles all the PCI/PCIe and memory controller functions and also sports the VIA Chrome9 HC IGP that supports DX9 features.  Nothing to scream about, but it turns out to be faster than Intel's solution.<br />
<img class="alignnone" src="http://www.pcper.com/images/reviews/597/via11.jpg" alt="" width="600" height="400" /></p>
<p>Here's the classic "chip next to a quarter" image.<img class="alignnone" src="http://www.pcper.com/images/reviews/597/via12.jpg" alt="" width="600" height="400" /></p>
<p><em><strong>Intel Atom D945G Platform</strong></em></p>
<p><img class="alignnone" src="http://www.pcper.com/images/reviews/597/intel01.jpg" alt="" width="600" height="400" /></p>
<p>Just like the VIA board, the Atom processor is soldered and permanently affixed.</p>
<p>The Intel D945GCLF is the same form factor as the VIA Nano reference platform: mini-ITX.  This board design looks to be much simpler at first glance and that is in fact the case as we investigate a bit further into the design.</p>
<p><img class="alignnone" src="http://www.pcper.com/images/reviews/597/intel03.jpg" alt="" width="600" height="400" /></p>
<p>The only expansion slot that the Intel Atom motherboard offers is a PCI slot - any graphics expansion you plan to do will have to be relegated to this older interface.  This is really VIA's best selling point - they are allowing their platform to be completely open but Intel is ONLY ALLOWING their boards and board partners to ship with PCI slots.</p>
<p><img class="alignnone" src="http://www.pcper.com/images/reviews/597/intel04.jpg" alt="" width="600" height="400" /></p>
<p>The Intel board only has a single DIMM slot supporting up to 2GB of DDR2-667 memory.  The ATX power connector is again a 20-pin rather than 24-pin but will still fit with 24-pin PSUs.  There is a single IDE connection and two SATA channels for your storage connectivity.</p>
<p><img class="alignnone" src="http://www.pcper.com/images/reviews/597/intel05.jpg" alt="" width="600" height="400" /></p>
<p>Here you can see the processor heatsink is incredibly small and passive only and is dwarfed by the chipset heatsink above it.  Notice also that the Intel board requires you to use a secondary 4-pin power connection in addition to the standard ATX power connector.</p>
<p><img class="alignnone" src="http://www.pcper.com/images/reviews/597/intel06.jpg" alt="" width="600" height="400" /></p>
<p>The external connections on the board are similar to those seen on the VIA Nano reference board - PS/2, USB 2.0, serial, parallel, a single 10/100 NIC, 6-channel audio outputs and a VGA output.</p>
<p><img class="alignnone" src="http://www.pcper.com/images/reviews/597/intel07.jpg" alt="" width="600" height="400" /></p>
<p>Removing the heatsink reveals the full array of Intel chips - the Atom processor at the top, 945G north bridge in the middle and the Intel ICH7-M south bridge at the bottom.  It is interesting to see how much more cooling the 945G chipset requires compared to the Atom processor.</p>
<p><img class="alignnone" src="http://www.pcper.com/images/reviews/597/intel08.jpg" alt="" width="600" height="400" /></p>
<p>Wow, that is a TINY processor!  The model on this board is the Atom 230 that runs at 1.6 GHz on a 533 MHz FSB.<br />
<img class="alignnone" src="http://www.pcper.com/images/reviews/597/intel09.jpg" alt="" width="600" height="400" /></p>
<p>This poorly edited photo should show you the exact size comparison between the VIA Nano and Intel Atom processors - the Atom is the skinnier chip in the center with the Nano encompassing it with a much larger square.  It just goes to show that even though we think the Nano is incredibly small, Intel has a more cost efficient chip to offer up - the real question will be performance!<img class="alignnone" src="http://www.pcper.com/images/reviews/597/chip_comparison.jpg" alt="" width="279" height="249" /></p>
]]></content:encoded>
</item>
<item>
<title><![CDATA[MINIX™ 780G-SP128MB]]></title>
<link>http://wlalng.wordpress.com/?p=64</link>
<pubDate>Fri, 01 Aug 2008 07:44:22 +0000</pubDate>
<dc:creator>thorsenine</dc:creator>
<guid>http://wlalng.wordpress.com/?p=64</guid>
<description><![CDATA[A revolutionary product for lifestyle HD computing
Built with the fastest onboard graphics - AMD® 7]]></description>
<content:encoded><![CDATA[<p><img class="alignleft" src="http://www.jwele.com/UserFiles/jwele.com/1217225097.jpg" alt="" width="374" height="399" />A revolutionary product for lifestyle HD computing</p>
<p>Built with the fastest onboard graphics - AMD® 780G and with the help of 128MB side-port</p>
<p>memory, it further boosts up the graphics performance by another 15-19% in such a compact</p>
<p>size.</p>
<p>Featuring the hardware HD video decoder – Universal Video Decoder, and supporting Avivo™ HD</p>
<p>natively, MINIX™ 780G-SP128MB are also ready for DirectX® 10 like our award-winning (click</p>
<p>to view) JW-RS780UVD-AM2+ motherboard.</p>
<p><em><strong>Key Features Highlight:</strong></em></p>
<p>1. Integrated ATI Radeon™ HD 3200 Graphics</p>
<p>2. Supports DirectX® 10 3D graphics, Vista™ Aero Ready</p>
<p>3. Supports AMD® Phenom™ Quad-Core Processors (95W max.)</p>
<p>4. Built-in 128 MB Local Frame Buffer (Side-port memory)</p>
<p>5. Supports ATI Avivo™ HD technology and built-in Universal Video Decoder (UVD) which  leverages CPU consumption when play HD movie, hence power-saving</p>
<p>6. Designed with 100% high quality solid capacitors and components to ensure high performance and great longevity</p>
<p>7. One PCI-Express slot for expansion</p>
<p>8. Two DDR2 SO-DIMM slots for extensible upgrade</p>
<p>9. Supports J&#38;W® iPartner™ Control Centre</p>
<p>10. 7.1+2 Channel High-Performance HDA Codec with Content Protection (Realtek ALC885)<br />
<img class="alignnone" src="http://www.jwele.com/UserFiles/jwele.com/1217225708.jpg" alt="" width="605" height="274" /></p>
]]></content:encoded>
</item>
<item>
<title><![CDATA[GSoC Minix USB Project Update]]></title>
<link>http://rafavargas.wordpress.com/2008/07/23/gsoc-minix-usb-project-update/</link>
<pubDate>Wed, 23 Jul 2008 10:19:16 +0000</pubDate>
<dc:creator>Rafa Vargas</dc:creator>
<guid>http://rafavargas.wordpress.com/2008/07/23/gsoc-minix-usb-project-update/</guid>
<description><![CDATA[Last Friday GSoC midterms evaluations closed. It seems I continue in the program. That&#8217;s good ]]></description>
<content:encoded><![CDATA[<p><img style="border-width:0;margin:0 5px 0 0;" height="60" alt="" src="http://rafavargas.files.wordpress.com/2008/07/image.png" width="80" align="left" border="0">Last Friday GSoC midterms evaluations closed. It seems I continue in the program. That's good news. However, there has been several changes in the project.</p>
<ol>
<li>In the beginning we were two programmers but one of us (not me) dropped.</li>
<li>Our goal was to implement USB 2.0 (UHCI and USBD) support in Minix and provide some Mass Storage device drivers for pen drives, external USB hard drives (Flash and CAM/SCSI ones), etc. Nonetheless, this is too much for one person coding at summer. So the project goal was changed to finish a EHCI controller done by an Indian team and provide some support for basic USB 1.1 devices such as: keyboards, mice and hubs.</li>
</ol>
<p>Up to this point, I have not done so much coding in Google Summer of Code :( I hope this week I finally receive Indian USB code and can hack a little.</p>
]]></content:encoded>
</item>
<item>
<title><![CDATA[Scurta introducere in  Linux]]></title>
<link>http://pierdutinspania.wordpress.com/?p=15</link>
<pubDate>Wed, 16 Jul 2008 20:15:39 +0000</pubDate>
<dc:creator>adrian cojocaru</dc:creator>
<guid>http://pierdutinspania.wordpress.com/?p=15</guid>
<description><![CDATA[Totul a inceput in 1991 cu un tanar student al Univesitatii Helsinki din Finlanda pe nume Linus Torv]]></description>
<content:encoded><![CDATA[<p>Totul a inceput in 1991 cu un tanar student al Univesitatii Helsinki din Finlanda pe nume Linus Torvalds. Linus folosea in reteaua universitatii un mic sistem operativ pe nume Minix, dar nemultumit de limitatiile pe care le avea Minix-ul incepe sa scrie codul pentru un sistem operativ nou pe care avea sa-l numeasca Linux. Asa se naste primul kernel sau nucleu Linux, care il inregistreaza sub licenta GPL (Liecenta Publica Generala), licenta care permite libera distributie, modificare si folosire de software. Acesta a fost doar inceputul, imediat o multime de programatori din toate colturile lumii s-au alaturat proiectului iar Linux a inceput sa creasca vertiginos.</p>
<p>Pentru multa lume cuvantul "Linux" suna a ceva misterios, ceva care e folosit doar de informaticieni si hackeri experti.Nimic mai neadevarat,  Linux-ul din ziua de azi este destul de asemanator cu sistemul operativ Windows®, asta in ceea ce priveste aspectul grafic. Este adevarat ca Linux este un pic mai complex decat  Windows®, dar odata probat o sa ramaneti incantat de prestatiile pe care vi le ofera. De ce sa folositi Linux? Imi trec prin minte o gramada de motive din care o sa amintesc doar cateva:</p>
<ul>
<li>Pretul. Totul este gratis, orice program se poate descarca sau instala cu un coste zero. Este ideal pentru a fi folosit in scoli sau universitati cu un mare numar de calculatoare datorita costului redus care il presupune instalarea si intretinerea sistemelor Linux.</li>
<li>Securitate. Este mult mai sigur ca si Windows®, aproape ca nu exista virusi pentru Linux iar putinele "gauri" de securitate care se descopera sunt reparate foarte repede.</li>
<li>Stabilitate. Cand o sa folositi Linux o sa vedeti ca sunt foarte rare cazurile in care acesta se blocheaza, dovada ca in ziua de azi 80% din servidoarele web din toata lumea folosesc Linux ca plataforma, iar mari companii ca IBM, Dell, Hewlett-Packard, Novel, Oracle il folosesc in sistemele lor.</li>
<li>Compatibilitate. Se poate instala pe o mare varietate de hardware: computere personale(PC, MacIntosh si PowerPc), telefoane mobile, computere de buzunar, videoconsolas(XBox, Play Station 3, Play Station Portable, Dreamcast...).</li>
<li>Upgrade. Linux se misca foarte repede, nucleul este deja la versiunea 2.6 si se inbunatateste constant pentru a suporta hardware nou.</li>
<li>Personalizare. Mii de programe, aplicatii, gadgeturi sunt disponibile gratis pentru a face Linux sa arate asa cum vrei tu.</li>
<li>Utilizeaza putine recursuri. Ruleaza bine pe calculatoare vechi, nu are nevoie de hardware foarte performant, pentru a-l proba puteti sa folositi vechiul calculator care zace aruncat intr-un colt.</li>
</ul>
<p>Pentru cei care nu au vazut inca Linux in actiune:</p>
<p><span style='text-align:center; display: block;'><object width='425' height='350'><param name='movie' value='http://www.youtube.com/v/_qBGEmRn95g'></param><param name='wmode' value='transparent'></param><embed src='http://www.youtube.com/v/_qBGEmRn95g&rel=0' type='application/x-shockwave-flash' wmode='transparent' width='425' height='350'></embed></object></span></p>
<p>Cool, nu?</p>
<p>Daca v-am starnit curiozitatea si vrei sa simtiti pe pielea voastra ce inseamna Linux puteti sa va descarcati un LiveCd , va recomand<a href="http://www.knoppix.org/"> Knoppix</a> pentru usurinta cu care recunoaste hardware sau <a href="http://www.gentoo.org/main/en/where.xml">Gentoo </a>pentru flexibilitatea care o ofera.</p>
<p>Ce este un LiveCd? Un LiveCd nu este altceva decat o distributie Linux functionala 100%, fara a fi nevoie de a instala nimic in calculatorul in care il probam. Avem nevoie doar de un calculator care poate boota de pe un cd(majoritatea pot). LiveCd-ul foloseste memoria RAM a calculatorului pentru a instala un "hard disk virtual" care emuleaza un hard disk normal. Nu va fie frica sa probati in orice calculator, cand o sa-l restartati totul o sa fie exact ca inainte, LiveCd-ul nu modifica nimic din configuratia originala.</p>
<p>Acelora care vor sa incerce o instalare reala le recomand sa inceapa cu <a href="http://www.ubuntu.com">Ubuntu</a>, o distributie cu instalare grafica si care vine cu un desktop foarte complect si usor de folosit.Succes!</p>
]]></content:encoded>
</item>
<item>
<title><![CDATA[Minix Google Groups Clean RSS]]></title>
<link>http://rafavargas.wordpress.com/2008/07/02/minix-google-groups-clean-rss/</link>
<pubDate>Wed, 02 Jul 2008 23:27:50 +0000</pubDate>
<dc:creator>Rafa Vargas</dc:creator>
<guid>http://rafavargas.wordpress.com/2008/07/02/minix-google-groups-clean-rss/</guid>
<description><![CDATA[ For those of you who still use USENET comp.os.minix group and follow group activity through Google ]]></description>
<content:encoded><![CDATA[<p><img style="border-right:0;border-top:0;border-left:0;border-bottom:0;margin:0 5px 5px 0;" height="60" alt="image" src="http://rafavargas.files.wordpress.com/2008/07/image12.png" width="68" align="left" border="0"> For those of you who still use <a href="http://en.wikipedia.org/wiki/Usenet">USENET</a> <a href="http://groups.google.com/group/comp.os.minix">comp.os.minix</a> group and follow group activity through Google Groups (by RSS feed) and are tired of SPAM as much as me, we've established a RSS "proxy" in <a href="http://rafavargas.es/minix"><img style="border-width:0;" height="16" alt="RSS" src="http://rafavargas.files.wordpress.com/2008/07/image9.png" width="16" border="0"></a> <a href="http://rafavargas.es/minix/">http://rafavargas.es/minix/</a> where you can find Google Group's RSS filtered (spam-free).</p>
<p>Check and compare both RSS feeds and give it a try!</p>
<p><a href="http://rafavargas.es/minix"><img style="border-width:0;" height="16" alt="RSS" src="http://rafavargas.files.wordpress.com/2008/07/image9.png" width="16" border="0"></a> <a href="http://rafavargas.es/minix/">http://rafavargas.es/minix/</a></p>
<p><a href="http://groups.google.com/group/comp.os.minix/feed/rss_v2_0_msgs.xml"><img style="border-width:0;" height="16" alt="RSS" src="http://rafavargas.files.wordpress.com/2008/07/image9.png" width="16" border="0"></a> <a title="http://groups.google.com/group/comp.os.minix/feed/rss_v2_0_msgs.xml" href="http://groups.google.com/group/comp.os.minix/feed/rss_v2_0_msgs.xml">http://groups.google.com/group/comp.os.minix/feed/rss_v2_0_msgs.xml</a></p>
<p>Until now, we didn't have any false positives. Although, there's still so much work that could be done to improve this filter, we are not going to do it, because we had decided to move to a moderated group (change comp.os.minix to moderated). This RSS filter is a temporal solution.</p>
<p>P.S: this is not part of my job with Minix, it is just a matter of personal need.</p>
]]></content:encoded>
</item>
<item>
<title><![CDATA[POSIX]]></title>
<link>http://julianrdz.wordpress.com/?p=166</link>
<pubDate>Sat, 14 Jun 2008 00:06:00 +0000</pubDate>
<dc:creator>Julián Rodríguez</dc:creator>
<guid>http://julianrdz.wordpress.com/?p=166</guid>
<description><![CDATA[POSIX es el acrónimo de Portable Operating System Interface; la X viene de UNIX como seña de ident]]></description>
<content:encoded><![CDATA[<p>POSIX es el acrónimo de Portable Operating System Interface; la X viene de UNIX como seña de identidad de la API. El término POSIX fue sugerido por Richard Stallman en respuesta a la demanda de la IEEE, que buscaba un nombre fácil de recordar. Una traducción aproximada del acrónimo podría ser "Interfaz de Sistema Operativo Portátil basado en UNIX".</p>
<p>Estos son una familia de estándares de llamadas al sistema operativo definidos por el IEEE y especificados formalmente en el IEEE 1003. Persiguen generalizar las interfaces de los sistemas operativos para que una misma aplicación pueda ejecutarse en distintas plataformas. Estos estándares surgieron de un proyecto de normalización de las API y describen un conjunto de interfaces de aplicación adaptables a una gran variedad de implementaciones de sistemas operativos.</p>
<p>POSIX especifica las interfaces de usuario y software al Sistema Operativo en 15 documentos diferentes. La línea de comandos estándar y las interfaces de scripting se basaron en Korn Shell. Otros programas a nivel de usuario (user-level), servicios y utilidades incluyen awk, echo, ed (computación) y cientos de otras. Los servicios a nivel de programa requeridos incluyen definición de estándares básicos de I/O, (file(Computación, UNIX), terminal, y servicios de red. POSIX también especifican una API para las librerías de threading, que es muy popular y muy utilizada en muchos sistemas operativos.</p>
<p>Una serie de pruebas acompañan al estándar POSIX. Son llamadas PCTS en alusión al acrónimo Posix Conformance Test Suite.</p>
<p>Desde que la IEEE empezó a cobrar altos precios por la documentación de POSIX y se ha negado a publicar los estándares, ha aumentado el uso del modelo Single Unix Specification. Este modelo es abierto, acepta entradas de todo el mundo y está libremente disponible en Internet. Fue creado por The Open Group.</p>
<p>Los sistemas operativos que soportan POSIX son:<br />
* A/UX<br />
* AIX<br />
* BSD/OS<br />
* HP-UX<br />
* INTEGRITY<br />
* Irix<br />
* LynxOS<br />
* Mac OS X<br />
* MINIX<br />
* OpenVMS<br />
* QNX<br />
* RTEMS (POSIX 1003.1-2003 Profile 52)<br />
* Solaris<br />
* OpenSolaris<br />
* UnixWare<br />
* VxWorks<br />
* Windows con kernel NT (usados en Windows NT, 2000, 2003; XP, Vista): sólo en algunas ediciones o con determinadas aplicaciones instaladas.</p>
]]></content:encoded>
</item>
<item>
<title><![CDATA[USB Icon Specification]]></title>
<link>http://rafavargas.wordpress.com/?p=327</link>
<pubDate>Tue, 03 Jun 2008 05:24:05 +0000</pubDate>
<dc:creator>Rafa Vargas</dc:creator>
<guid>http://rafavargas.wordpress.com/?p=327</guid>
<description><![CDATA[Ever wonder why every USB certified cable/connector/device/hub has the same icon without any modific]]></description>
<content:encoded><![CDATA[<p>Ever wonder why every USB certified cable/connector/device/hub has the same icon without any modification? Well, it seems it is part of the USB specification (USB 2.0 Spec, Sect 6.5, Page 93). I've just discovered this today.</p>
<p><a href="http://rafavargas.wordpress.com/files/2008/06/usblogospec.png"><img class="aligncenter size-full wp-image-328" src="http://rafavargas.wordpress.com/files/2008/06/usblogospec.png" alt="USB Icon Spec" width="510" height="370" /></a></p>
<p>More information:</p>
<ul>
<li><a href="http://www.usb.org/developers/docs/usb_20_040908.zip" target="_blank">USB Specification</a></li>
</ul>
]]></content:encoded>
</item>
<item>
<title><![CDATA[IBL, Grosseto corre ai ripari: in arrivo Travis Minix, sarà il rilievo di Mikkelsen]]></title>
<link>http://doubleplay.wordpress.com/?p=322</link>
<pubDate>Sun, 01 Jun 2008 17:02:05 +0000</pubDate>
<dc:creator>Maurizio Roveri</dc:creator>
<guid>http://doubleplay.wordpress.com/?p=322</guid>
<description><![CDATA[Si chiama Travis Wayne Minix. Americano. Lanciatore destro. Lo ha tesserato il Montepaschi Grosseto ]]></description>
<content:encoded><![CDATA[<p>Si chiama Travis Wayne Minix. Americano. Lanciatore destro. Lo ha tesserato il Montepaschi Grosseto come secondo pitcher straniero. Sarà lui, dal 12 giugno in occasione di gara1 contro la Danesi Nettuno (secondo week end del girone di ritorno), il “rilievo” di Lincoln Mikkelsen.</p>
<p><!--more--><br />
Una scelta tecnica suggerita dalla situazione di un monte di lancio che non gode propriamente di buona salute e anche dalla necessità di non dovere spremere troppo il braccio del quarantenne Mikkelsen (apparso ultimamente un po’ affaticato). L’arrivo di Minix permetterà a Chris Cooper di essere stabilmente utilizzato nella partita dei lanciatori oriundi, come rilievo di un Oberto che sta ultimando il recupero dopo il lungo stop per infortunio (Cooper potrebbe anche fare il partente, in attesa che Oberto ritrovi la miglior condizione di forma).<br />
Nato a Knox, nello Stato dell’Indiana l’8 agosto 1977, Trevis Minix si è formato all’Università di Ball State. E’ stato scelto al 23° giro da Tampa Bay nel draft del 1999. La carriera di questo buon pitcher parla di 8 stagioni nelle Minors, per l’Organizzazione di Tampa Bay e poi di Filadelfia. E’ salito fino al Triplo, indossando la casacca di Durham (affiliata a Tampa Bay) e di Scranton (affiliata ai Phillies). I suoi numeri sono interessanti: 328 partite in totale (8 da partente), 525.1 riprese lanciate, 27 vittorie, 19 sconfitte e 32 salvezze. Con una media-pgl di 2.91.<br />
Minix dovrebbe essere a Grosseto la prossima settimana e disponibile a lanciare per l’importante sfida della settimana successiva contro Nettuno allo stadio “Roberto Jannella”.</p>
]]></content:encoded>
</item>
<item>
<title><![CDATA[История на GNU/Linux]]></title>
<link>http://bcclf.wordpress.com/?p=22</link>
<pubDate>Tue, 27 May 2008 23:18:55 +0000</pubDate>
<dc:creator>Васил Стоев</dc:creator>
<guid>http://bcclf.wordpress.com/?p=22</guid>
<description><![CDATA[Историята на GNU/Linux започва още през 60-те години на мина]]></description>
<content:encoded><![CDATA[<p style="text-align:justify;"><span style="font-family:Verdana;color:#0000ff;"><em><span style="color:#000000;">Историята на GNU/Linux започва още през 60-те години на миналия век. Тя е Unix - подобна ОС. Основите които се Unix въвежда са толкова фундаментални че трябва да започнем разказа от самата нея. Те са се превърнали в канон за разработчиците на ОС. Ще кажем няколко думи и за наследника на Unix - Free BSD. Въпреки че няма никаква връзка с проекта GNU. Но така ще имате най - ясна представа за модерните течения в развитието на свободния софтуер. </span></em></span></p>
<p style="text-align:justify;"><span style="color:#0000ff;"><strong>Съдържание</strong><br />
</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">1. UNIX<br />
2. MINIX<br />
3. Системата GNU<br />
4. Free Software Fondation<br />
5. Линус Торвалдс</span></p>
<p style="text-align:center;"><a href="http://bcclf.files.wordpress.com/2008/05/660px-free_software_portal_logosvg.png"><img class="size-medium wp-image-24 aligncenter" src="http://bcclf.wordpress.com/files/2008/05/660px-free_software_portal_logosvg.png?w=300" alt="united free software logo" width="300" height="272" /></a></p>
<p style="text-align:justify;"><span style="font-family:Verdana;color:#0000ff;"><strong>UNIX</strong></span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">Unix (Юникс) е разработена през 1969 г., от група на AT&#38;T работеща в Bell Labs включваща Кен Томпсън, Денис Ричи, и Дъглас МакИлрой.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">През 60-те, Massachusetts Institute of Technology (Масачузетски Технологичен Институт), AT&#38;T Bell Labs, и General Electric работят по експериментална операционна система наречена Multics (Multiplexed Information and Computing Service), създадена да се изпънява на GE-645 мейнфрейм (огромен компютър заемащ няколко зали, производителността му е била &#60; = от бързодействието на вашата настолна машина). Целта е създаване на комерсиален продукт, но успех не е постигнат. Multics е интреактивна операционна система с много нови възможности и повишена сигурност. Краен продукт е създаден, но производителността му е много ниска.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">AT&#38;T Bell Labs се оттегля и разпредели ресурсите си по други проекти. Един от разработчиците от екипа на Bell Labs, Кен Томпсън, продължава да работи за проекта, и написва игра за GE-645 наречена Пътуване в пространството (Space Travel). Но тя е бавно се изпълнява на GE машината и доста скъпа, струва $75 за изпълнение от дефицитното компютърно време. Едно време машините са били бавнички. Предварително се е планирало какви програми ще се изпълняват на тях. Всеки компютър си е имал оператор или група от оператори които са въвеждали данни и стартирали програми за обработка на машината. Трябвало е да се плащат заплати, а и компютрите са гълтали десетки kWh електроенергия. Докато сега е обратното - имаме дефицит на процесорно време.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">Томпсън пренаписва играта на асемблер за Digital Equipment Corporation - PDP-7 с помощта на Дени Ричи. Този проект заедно с работата му по проекта Multics, кара Томпсън да създаде нова операционна система за PDP-7. Той и Ричи ръководят екип от разработчици, включително Руд Канадей (Rudd Canaday), от Bell Labs разработващ файловата система както и новата многозадачна операционна система. Тя включваше и интерпретатор за командния ред.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">През 1970, проектът е наречен Unics (съкратено от Uniplexed Information and Computing System), и поддържаше едновременно двама потребители. Името е приписано на Браиън Керниган (Brian Kernighan),</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">Дотогава нямаше финансова поддръжка от Bell Labs. Когато Computer Science Research Group поиска да използва Unix на машина много по-голяма от PDP-7, Томпсън и Ричи успяват да изтъргуват с обещание за добавяне на възможности за обработка на текст към Unix за PDP-11/20 машина. Това доведе до минимална финансова поддръжка от страна на Bell. За пръв път през 1970, Операционната система UNIX официално беше именувана и се изпълнява на PDP-11/20. Добавена е програма за форматиране на текст наречена roff и текстов редактор. и трите написани на асемблер за PDP-11/20. Bell Labs използва тази "система за обработка на текст", направена от Unix, roff, и редактора, за обработка на тест за подаване на патенти. Roff еволюира в troff, пътвата електронна програма за публикуване с пълни типографски възможности. Ръководство на UNIX програмиста (UNIX Programmer's Manual) е публикувано на 3 ноември 1971.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">През 1973, е решено да се пренапише Unix на C. Промяната улеснява модифицирането/прехвърлянето на Unix на други машини (т.е. преносимостта), и възможност и други разработчици могат да създадат варианти. Кода стана по-стегнат и компактен, което доведе до по бърза разработка на Unix. AT&#38;T направи Unix достъпен за университетите и компаниите, а също и за правителството на САЩ под лиценз. Лиценза включва целия изходен код с изключение на машинно-зависимата част написана на асемблер за PDP-11. Обаче, копия на машинно зависимото ядро с коментари се разпространяват в края на 70-те под форма на копирана книга на Джон Лион от University of New South Wales - Lions' Commentary on UNIX 6th Edition, with Source Code, което доведе до приемане на Unix като операционна система за обучение.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">Версиите на Unix се определят от версиите на съответните им ръководства т.е. "Fifth Edition UNIX" и "UNIX Version 5" се използват за едно и също нещо. Разработката се разшири с версии 4, 5, и 6 пуснати до 1975. Тези версии добавят концепцията за съобщителен канал, водещо до разработката на модулна кодова база, което повиши още скоростта на разработване. Версия 5 и по-специално версия 6 доведоха до множество различни версии на Unix в Bell Labs и извън нея, например PWB/UNIX, IS/1 (първия комерсиален Unix), и пренасянето му на Interdata 7/32 (първия не-PDP Unix) от University of Wollongong.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">През 1978 е представен UNIX/32V, за VAX система. По това време повече от 600 машини изпълняват някаква форма на Unix. Unix версия 7 - последната широкоразпространена версия на Research Unix е представена през 1979. Версии 8, 9 и 10 са разработени през 80-те но бяха разпространени само в няколко университета, които създадоха документи описващи новостите. Това доведе до разработката на Plan 9 from Bell Labs - нова преносима разпределена система.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">През 80-те AT&#38;T лицензира UNIX System III, базирана основно на версия 7, за комерсиално използване през 1982. Тя включваше поддръжка на VAX. AT&#38;T продължи да лицензира по-старите версии на Unix. За да сложи край на объркването между различните версии, AT&#38;T ги комбинира в UNIX System V Release 1. Тя предложи нови възможности като редактора vi (изисква магистърска степен по текстообработка, по лесно е да пишете на pico) и curses от Berkeley Software Distribution на Unix разработени от University of California, Berkeley. Тя включваше поддръжка на Western Electric 3B.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">Тъй като новото комерсиално лицензиране на UNIX не е изгодно за академично използване както по-ранните версии изследователи от Бъркли продължават да разработват BSD Unix като алтернатива на UNIX System III и V, първоначално за PDP-11 (2.xBSD завършвайки с 2.11BSD) и по-късно за VAX-11 (версии 4.x на BSD). Много от нововъведенията в Unix първо се появяват в BSD, например C shell с контрол на задачите (създаден по модел на ITS), най-важния аспект от разработката на BSD е добавянето на TCP/IP кода към Unix ядрото. Усилията на BSD имат като резултат няколко версии съдържащи мрежовия код: 4.1c BSD, 4.2 BSD, 4.3 BSD, 4.3B SD-Tahoe ("Tahoe" е прякора на CCI Power 6/32 архитектурата - първата версия на различна ор DEC платформа на BSD ядрото), Net/1, 4.3BSD-Reno (за наподобяване на "Tahoe", и тъй като тази версия е "хазартна"), Net/2, 4.4BSD, и 4.4BSD-lite. Мрежовия код в тези версии е прародител на TCP/IP мрежовия код използващ се сега, включително и кода пуснат по-късно в AT&#38;T System V UNIX и Microsoft Windows. Съпътстващия Berkeley Sockets API е де - факто стандарт за мрежови програмни интерфейси и е копиран от много платформи.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">Други компании започват предлагането на комерсиални версии на UNIX за техните миникомпютри и работни станции. Повечето от тях са разработени бъз основа на System V и лицензирани от AT&#38;T; но има и BSD базирани. Един от водещите разработчици на BSD, Бил Джой(Bill Joy), основа Sun Microsystems през 1982 и създаде SunOS (сега Solaris) за техните работни станции. През 1980, Microsoft представи техния първи Unix за 16-битови компютри наречен Xenix, който Santa Cruz Operation (SCO) прехрърли за Intel 8086 процесор през 1983, и създаде Xenix клон - SCO UNIX през 1989.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">През 1984 се сформира група наречена X/Open с цел създаване на съвместима отворена система за стандартизиране на UNIX. Към средата на 80-те, несъвместимистта между конкуриращите се версии на Unix, наречени Unix войни пречат на приемането на Unix на пазар, който започна да се доминира от Microsoft-ските операционни системи. Вдъхновена от разработването на двойни (AT&#38;T/BSD) версии на Unix, IEEE работна група P1003 разработи първия POSIX стандарт за Unix-базирани програмни интерфейси, публикуван през 1988.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">AT&#38;T добави в UNIX System V, като заключване на файлове, администриране на системата, потоци, Отдалечена файлова система(Remote File System) и TLI. AT&#38;T си сътрудничи със Sun Microsystems и от 1987 и 1989 добави възможности от Xenix, BSD, SunOS, и System V в System V Release 4 (SVR4), независимо от X/Open. Тази версия консолидира всички предишни възможности в себе си, и сложи край на конкуриращите се версии. Но също и по-високи лицензионни такси.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">През 1990, Open Software Foundation обяви OSF/1, техния Unix стандарт, базиран на Mach и BSD. Фондацията е основана през 1988 и се финансира от няколко Unix компании желащи да се противопоставят на AT&#38;T и Sun за SVR4. Впоследствие AT&#38;T и друга група формират "UNIX International" за да се противопоставят на OSF. Този конфликт между конкуриращи се компании е наречен "Юникс войни".</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">През 1991, група от BSD разработчици (Дон Сели Donn Seeley, Майк Карелс Mike Karels, Бил Жолиц Bill Jolitz, и Треант Хейн Trent Hein) напусна Калифорнийския университет за да основе Berkeley Software Design, Inc (BSDI). BSDI произвежда напълно функционална комерсиална версия на BSD Unix за Интел базирани компютри, което постави началото на използването на евтини компютри за сериозни изчисления. Скоро след основаването на компанията Бил Жолиц напусна BSDI за да създаде 386BSD, положил началото на FreeBSD, OpenBSD, и NetBSD.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">До 1993 повечето комерсиални доставчици на UNIX променят техните Unix варианти на System V базирани и добавят много от възможностите на BSD. Създаването на COSE от основните играчи на Unix пазара постави края на Unix войните, и доведе до сливането на UI и OSF през 1994. Въпреки, че запази името OSF работата по OSF/1 е спряна същата година. Единствения доставчик, който я изпозваше бе Digital, той продължи разработката и преименува продукта на Digital UNIX в началото на 1995.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">Скоро след обнародването на UNIX System V Release 4, AT&#38;T продаде правата върху UNIX на Novell. Novell разработва своя собствен версия - UnixWare сливайки NetWare с UNIX System V Release 4. Novell я използва срещу Windows NT, но тяхното присъствие на пазара продължи да намалява.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">През 1993, Novell реши да предаде UNIX запазената марка и правата за сертифициране на X/Open.  През 1996, X/Open се сля с OSF, създавайки Open Group. Стандартите на Open Group дефинират какво е и какво не е "UNIX" операционна система.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">През 1995, бизнеса на администриране и поддръжка на съществуващите UNIX лицензи и правото за разработка на System V кода са продадени от Novell на Santa Cruz Operation. Въпроса дали Novell също продава запазената марка е основа за съдебен процес.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">През 2000, SCO продава целия UNIX бизнес на Caldera Systems, по късно променила името си на The SCO Group. Този нов играч на пазара започна съдебни процеси срещу потребители и доставчици на Linux. SCO твърдят, че Linux съдържа защитен от закона Unix код притежание на The SCO Group. Другие твърдения са нарушение на търговската тайна от IBM, или нарушаване на договора от бивши клиенти на Santa Cruz преминали към Linux. Но Novell отрича твърденията на SCO че държи правата на UNIX кода. Според Novell, SCO (и SCO Group) са франчайз за Novell, която сържи основните права, и право на вето към лицензиите давани от SCO, и 95% от прихода. SCO Group не е на това мнение и го оспорва в процеса наречен SCO срещу Novell.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;"><strong>MINIX</strong></span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">През 1987 Андрю Таненбаум създава MINIX във Врие Университет в Амстердам. Целта му е да илюстрира принципите описани в неговата книга "Операционна система: Дизайн и имплементация". MINIX е минималистична система написана с учебна цел. Съкратен вариант от около 12 000 реда от написания на C основен изходен код на ядрото, мениджъра на паметта и файловата система на MINIX 1.0, са включени в тази книга. Prentice-Hall също публикува изходния код на MINIX, както и бинарен вариант на флопи диск с технически наръчник. MINIX 1.0 е направена като система-клон, която е съвместима със Edition 7 на Unix. По принцип MINIX е писан за IBM PC и IBM PC/AT, които са били актуални по онова време. MINIX е важен възел от историята на LINUX. Тя е причината, може би и вдъхновението на Линус Торвалдс да напише ядрото на свободната операционна система.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">Сегашният собственик на търговската марка UNIX е The Open Group, консорциум за индустриални стандарти. Обаче правата върху изходния код на Unix, са оспорвани в дело от 2004, където доставчика на UNIX SCO Group Inc. обвинява Novell в компрометиране на името (slander of title). Забележете че собственикът на търговската марка използва UNIX, а не Unix. Терминът UNIX не е акроним, а следва конвенцията, възприета по-рано компютърните системи да се именуват с главни букви като ENIAC и MISTIC.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">Само системи, напълно съвместими и сертифицирани по UNIX спецификацията (Single UNIX Specification) могат да се наричат "UNIX". Другите се наричат "Unix подобни" (Unix-like). Днес термина Unix се използва за посочване на система с характеристиките на Version 7 Unix или UNIX System V.<br />
<strong><br />
Системата GNU</strong></span></p>
<p style="text-align:justify;"><a href="http://bcclf.files.wordpress.com/2008/05/stallman.jpg"><img class="alignnone size-full wp-image-27" src="http://bcclf.wordpress.com/files/2008/05/stallman.jpg" alt="" width="182" height="140" /></a></p>
<p style="text-align:justify;"><span style="color:#0000ff;">Проектът GNU, чиято цел е създаване на нова операционна система свободен софтуер е основан от Ричард Столман през 1984 г. Системата съдържа голям брой инструменти и програми, например компилатори, текстови редактори и сървъри. Софтуерът се разпространява с лиценза GNU GPL, което гарантира бъдещата му свободна достъпност. Този лиценз ви прави пълноправен собственик на вашата ОС. Вие можете да я модифицирате както намерите за добре, да я продавате, подарявате и копирате. Това не ви прави "пират". Разпространявайки я под този лиценз, правите човека на който сте я дали/продали също пълноправен собственик. Задължително е да прилагате изходния къд към диска с ОС който разпространявате или да осигурите достъпност към него качвайки го в мрежата или разпространявайки го на хартиен носител (като обем - двайсетина пъти колкото трите тома на "Капитала" от Карл Маркс).</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">През 1991 г. към почти завършената операционна система е добавено ядрото Линукс, написано от Линус Торвалдс. С Линукс ГНУ става напълно работеща операционна система и това спомага за бързото ѝ разпространение. До тогава GNU обществото е разполагало с недотам съвършенно но работещо ядро Hurd, което се изпълнява върху микроядрото Mach. От GNU признават, че са имали много проблеми по написването на това ядро. Най - вече от концептуална гледна точка и липса на работещо такова което да им служи като модел. С Hurd GNU операционната система намира минимално приложение сред потребителите и не е била много популярна. Новото ядро налага значителен ремонт по вече създадения GNU софтуер. Цялостна, работеща система се получава едва когато към ядрото Linux се добавят огромен брой малки и по-големи приложни програми, създадени от проекта GNU и затова наричани „GNU софтуер“. От комбинацията между ядро Линукс и програми на GNU идва името GNU/Linux.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">Много хора допринасят за развитието на свободната операционна система. Линус Торвалдс се е заел да напише ядро, подобно на Юникс (Линукс). Доналд Кнут се е заел да напише програма за форматиране на текст (TeX). Боб Шайфлер се е заел да разработи графична система с прозорци (X Window system).</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">Проектът GNU поддържа системите GNU/Линукс, както и самата система GNU. ФСС финансира пренаписването на разширенията към библиотеката на GNU за Си, които са специфични за Линукс, така че сега те са добре интегрирани и съвременните системи GNU/Линукс използват текущото издание на библиотеката без промени. ФСС спонсорира също и ранния стадий на разработка на Дебиан GNU/Линукс.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;"><strong>FSF</strong></span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">Фондацията за свободен софтуер (Free Software Foundation),  е създадена през 1985 г. от Ричард Столман. Целта ѝ е да осигурява на компютърните потребители права за ползване, изучаване, копиране, промяна и разпространение на компютърни програми. Тя подпомага разработката и използването на свободен софтуер - по-специално операционната система GNU и свободна документация. FSF насърчава пропагандата на етичните и политическите ползи от употребата на свободен софтуер. Фондацията за свободен софтуер набляга върху създаването на нов свободен софтуер и включването му в съгласувана система, с цел да се намали (и премахне) нуждата от употреба на комерсиален софтуер. FSF защитава, съхранява и предлага свободен софтуер. Тя разпространява копия на програмите от проекта GNU и учебници срещу такса за доставката. Фондацията получава и пожертвувания, които насочва към проекта GNU.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">Ричард Столман (и сътрудници) e автор на популярния лиценз GNU GPL Versin 2 и GNU GPL Versin 3. Този лиценз формира правната защита на свободния софтуер.  Смисълът на лиценза GPL е в това, че всички притежатели на системата имат равни имуществени права върху нея. Вие можете да модифицирате програмата по ваше желание, да тиражирате неограничено своята дистрибуция и да го продавате даже и за един милион долара или просто да го подарите на всички, които го поискат. При това, всеки, на когото се продали или подарили вашата дистрибуция има същите права, които имате и вие.<br />
<strong><br />
Линус Торвалдс</strong></span></p>
<p style="text-align:justify;"><a href="http://bcclf.files.wordpress.com/2008/05/linus_torvalds.jpg"><img class="alignnone size-full wp-image-30" src="http://bcclf.wordpress.com/files/2008/05/linus_torvalds.jpg" alt="" width="85" height="124" /></a></p>
<p style="text-align:justify;"><span style="color:#0000ff;">Роден е в Хелзинки, Финландия на 28 декември 1969 г. Торвалдс учи в университета в Хелзинки от 1988 до 1996 и завършва специалността компютърни науки.<br />
Интересът му към компютрите започва с 8-битовите машини Commodorе VIC-20 (Комодор). След това се сдобива с „преносимия“ компютър Sinclair QL (процесор Motorola 68008 и скорост 7,5 MHz), на който пренаписва операционната система почти изцяло. Той създава и един асемблер, текстов редактор, както и няколко игри. През 1990 получава IBM компютър (базиран на Intel 80386) и с него започва работата си по една често употребявана система тогава - Minix.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">Още като студент той написва ядрото Линукс, занимавайки се с Minix, разпространява го сред приятели студенти и програмисти чрез университетския FTP-сървър и всеки започва да добавя по нещо и да го подобрява. Началната му цел е била написването на терминален емулатор за Minix, но резултатът от експериментите му е една оформяща се нова операционна система. Към началната версия на ядрото той прибавя и приложенията BASH (шел) и GCC (компилатор). Неговият талисман — плюшен пингвин на име Тъкс, става символ на Линукс.</span></p>
<p style="text-align:justify;"><span style="color:#0000ff;">Е това е историята на проекта GNU/Linux. По точно на мащабния проект, защото той включва в себе си много по - малки като обем проекти, всеки свързан със създаването на определена програма. Хиляди хора имат принус за развитието на GNU/Linux - програмисти, преводачи, обикновенни хора като мен и вас. Всяко едно предложение към обществото, частие в групи дискутиращи развитието на проекта е принос. Ако откриете пропуск в защита или бъг в системата и съобщите вие също допринасяте за развитието на Линукс. Принципа на линукс обществото е "от всеки според способностите, на всеки – според нуждите“.</span></p>
<p style="text-align:justify;"><em>Източник за този материал е wikipedia.org. </em></p>
]]></content:encoded>
</item>
<item>
<title><![CDATA[لینوکس!]]></title>
<link>http://saarblog.wordpress.com/?p=96</link>
<pubDate>Mon, 12 May 2008 16:03:23 +0000</pubDate>
<dc:creator>Saar</dc:creator>
<guid>http://saarblog.wordpress.com/?p=96</guid>
<description><![CDATA[کمی بعد از انتشار MINIX (سیستم عامل آموزشی که توسط اندرو س.]]></description>
<content:encoded><![CDATA[<p dir="rtl" align="justify">کمی بعد از انتشار MINIX (سیستم عامل آموزشی که توسط اندرو س. تانن‌باوم) یک گروه خبری یوزنت (USENET - بولتنهای خبری اینترنتی برای بحث و تبادل نظر در زمینه‌های مختلف) بنام comp.os.minix برای بحث درباره‌ی آن تشکیل شد. در عرض چند هفته تعداد اعضای این گروه خبری به ۴۰,000 نفر رسید، و اغلب آنها افرادی بودند که میل داشتند امکانات جدیدی به MINIX اضافه کرده و آنرا بزرگتر و بهتر کنند. برای آنهایی که از MS-DOS متنفر بودند، وجود MINIX (به همراه کد منبع آن) دلیلی شد تا یک PC خریده و تجربه‌ی متفاوتی با آن داشته باشند.</p>
<p dir="rtl" align="justify">یکی از این افراد دانشجوی فنلاندی بنام لینوس توروالدز (Linus Torvalds) بود. توروالدز MINIX را روی کامپیوتر که به تازگی خریده بود نصب کرد و کد آن را به دقت مطالعه کرد. وی که مایل بود گروه‌های خبری (از جمله comp.os.minix) را روی کامپیوتر MINIX خود مطالعه کند، نه در دانشگاه، دریافت که MINIX فاقد چنین امکانی است. لینوس تصمیم گرفت برنامه‌ی مورد نیاز را خودش بنویسد، اما خیلی زود متوجه شد که برای این کار به یک درایور ترمینال جدید نیاز دارد، پس آن را هم نوشت. کمی بعد به وسیله‌ای برای ذخیره کردن مباحث گروه‌های خبری نیاز پیدا کرد، پس یک درایور دیسک (و کمی بعد سیستم فایل) هم نوشت. تا آگوست ۱۹۹۱  لینوس موفق به خلق یک هسته‌ی سیستم‌عامل ابتدایی شده بود، و در تاریخ ۲۵ آگوست ۱۹۹۱  آن را روی گروه خبری comp.os.minix اعلام کرد.افراد زیادی برای کمک به لینوس گرد آمدند، و بالاخره اولین ویرایش این سیستم عامل در ۱۳ مارس ۱۹۹۴ منتشر شد؛ لینوکس (Linus MINIx) متولد شده بود.</p>
<p dir="rtl" align="justify">لینوکس یکی از موفقیت‌های مهم در نهضت منبع‌باز (Open Source) که MINIX در شروع آن نقش مهمی داشت محسوب می‌شود. لینوکس سیستم عامل ویندوز و یونیکس را به مبارزه طلبید، چون روی سیستم‌های ساده‌ای اجرا می‌شد که رقبایش آنها را از رده خارج تلقی می‌کردند. به زودی چند نرم‌افزار منبع باز دیگر، از جمله سرویس دهنده‌ی وب آپاچی(Apache) و پایگاه داده‌ی MySQL، به کمک لینوکس شتافتند و به موفقیت آن در بازار کمک رساندند. اکنون لینوکس به همراه آپاچی، MySQL و زبانهای برنامه نویسی منبع باز Perl و PHP (که روی هم رفته به عنوان LAMP شهرت یافته‌اند)، بخش عمده‌ای از بازار سرویس دهنده‌های وب را در اختیار دارند.</p>
<p dir="rtl" align="justify">
<p>طراحی و پیاده‌سازی سیستم‌عامل (کتاب MINIX)، اندرو س. تانن‌باوم، آلبرت س. وودهال؛</p>
]]></content:encoded>
</item>
<item>
<title><![CDATA[1992 - Linux is obsolete]]></title>
<link>http://bathroomreading.wordpress.com/?p=125</link>
<pubDate>Mon, 28 Apr 2008 18:06:52 +0000</pubDate>
<dc:creator>bathroomreading</dc:creator>
<guid>http://bathroomreading.wordpress.com/?p=125</guid>
<description><![CDATA[Eben bin ich auf einen mittlerweile schon gut 16 Jahre alten Thread gestoßen. Darin debattieren unt]]></description>
<content:encoded><![CDATA[<p>Eben bin ich auf einen mittlerweile schon gut 16 Jahre alten Thread gestoßen. Darin debattieren unter anderem <a href="http://de.wikipedia.org/wiki/Andrew_S._Tanenbaum" target="_blank">Andrew Tanenbaum</a> und <a href="http://de.wikipedia.org/wiki/Linus_Torvalds" target="_blank">Linus Torvalds</a> über Linux und dessen Architektur. Das nenne ich mal einen guten Geschichtsunterricht in Sachen Betriebssysteme! Ein bisschen Zeit sollte man sich zum lesen nehmen, da die Postings recht ausführlich sind. Das Tolle: Das Niveau dieser Flamewars ist wesentlich höher als das heutiger, da die beteiligten Leute wissen wovon sie reden.</p>
<p><a href="http://groups.google.com/group/comp.os.minix/browse_thread/thread/c25870d7a41696d2/f447530d082cd95d" target="_blank">LINUX is obsolete</a></p>
<p><a href="http://groups.google.com/group/comp.os.minix/browse_thread/thread/c37da71ec2777791/7ca118a12765a380" target="_blank">Unhappy campers</a></p>
]]></content:encoded>
</item>
<item>
<title><![CDATA[Google Summer of Code]]></title>
<link>http://rafavargas.wordpress.com/?p=271</link>
<pubDate>Tue, 22 Apr 2008 07:39:21 +0000</pubDate>
<dc:creator>Rafa Vargas</dc:creator>
<guid>http://rafavargas.wordpress.com/?p=271</guid>
<description><![CDATA[I talked about this a few weeks back. I tried to get a position as a Microsoft SDE(T) Intern but the]]></description>
<content:encoded><![CDATA[<p><img src="http://rafavargas.wordpress.com/files/2008/04/soc08-198x128_white.jpg" alt="Google Summer of Code" width="198" height="128" class="alignleft size-full wp-image-272" style="margin:5px;" />I talked about this a few weeks back. I tried to get a position as a <a href="http://www.microsoft.com/spain/careers/internshipsinRedmond.mspx">Microsoft SDE(T) Intern</a> but they told me we weren't able to offer a position at that moment (they will contact me back again in January).</p>
<p>In that moment I was resolved to do something nice in summer. I am programming CRUD applications since my first teenage years and that becomes very boring when you want to rock and improve my coding skills: so I decided to flip bits, not your CRUD <em>burguers'</em> Java accounting application.</p>
<p>So then, <a href="http://penyaskitodice.wordpress.com/">Penyaskito</a> told me to apply for Google Summer of Code and I considered his piece of advice. Finally, I only sent one application: <a href="http://code.google.com/soc/2008/minix/appinfo.html?csaid=17B646067E824BEF">Minix USB Stack</a> and know what? It was chosen! I will be working on Minix USB support during this summer with <a href="http://theebgar.net/">another student from Sri Lanka</a> and both mentored by Benjamin Gras.</p>
<p>Now, I have a great summer of code to enjoy the low level system programming. Just for fun!</p>
<p>But as you know, good news come in packs and some of my friends have been chosen too!<br />
<a href="http://penyaskitodice.wordpress.com/">Christian "Penyaskito" Lopez Espinola</a> with his <a href="http://code.google.com/soc/2008/argouml/appinfo.html?csaid=D38C90B46354F462">UI Code generation for ArgoUML property panels</a> as well as <a href="http://pibgeus.homeip.net/blog/">Pablo "GeuS" Iñigo Blasco</a> and his proposal: <a href="http://code.google.com/soc/2008/mono/appinfo.html?csaid=14D8E0C7C1C301C9">LinQ binding for sqlite (Mono)</a>.</p>
<p>Congratulations!</p>
<p>More information:</p>
<ul>
<li><a href="http://code.google.com/soc/2008/minix/about.html">Minix Summer of Code page in Google Code</a></li>
<li><a href="http://penyaskitodice.wordpress.com/2008/04/21/anunciados-google-summer-of-code-2008/">Penyaskito's post about this.</a></li>
</ul>
]]></content:encoded>
</item>
<item>
<title><![CDATA[Google Summer of Code Application]]></title>
<link>http://rafavargas.wordpress.com/2008/04/06/google-summer-of-code-application/</link>
<pubDate>Sun, 06 Apr 2008 22:18:57 +0000</pubDate>
<dc:creator>Rafa Vargas</dc:creator>
<guid>http://rafavargas.wordpress.com/2008/04/06/google-summer-of-code-application/</guid>
<description><![CDATA[Tomorrow is last day to apply for Summer of Code. Finally, I didn&#8217;t apply for Haskell; just fo]]></description>
<content:encoded><![CDATA[<p>Tomorrow is last day to apply for Summer of Code. Finally, I didn't apply for Haskell; just for Minix. However, it seems to be difficult to be chosen. Tanenbaum stated it clearly at SoC page in Minix3.org. My application has received some comments which are not so grateful to be honest. But it is true that I have not so much experience at drivers development.</p>
<p>However, if I am not given a GSoC position, I'll collaborate with Minix anyway. I would like to do some coding in kernel-space rather than user-space and developing an USB Stack is what I need. If this project is not assigned to some one else, then I'll do it on my own (although mentoring would help).</p>
<p>By the moment, I only can wait for response.</p>
]]></content:encoded>
</item>
<item>
<title><![CDATA[Mari belajar OS!]]></title>
<link>http://pengendali.wordpress.com/2008/04/02/aku-nak-belajar-os/</link>
<pubDate>Tue, 01 Apr 2008 21:31:57 +0000</pubDate>
<dc:creator>Kudin</dc:creator>
<guid>http://pengendali.wordpress.com/2008/04/02/aku-nak-belajar-os/</guid>
<description><![CDATA[MINIX 3, versi terbaru MINIX, ialah sistem pengendalian(OS) yang dibangunkan bagi tujuan pendidikan.]]></description>
<content:encoded><![CDATA[<p><img src="http://pengendali.files.wordpress.com/2008/04/minix-racoon.jpg" alt="minix-racoon.jpg" align="left" /><a href="http://www.minix3.org/" target="_blank">MINIX 3</a>, versi terbaru MINIX, ialah sistem pengendalian(OS) yang dibangunkan bagi tujuan pendidikan. Dengan jumlah kod kernel yang kecil, MINIX amat sesuai untuk pelajar dan peminat OS untuk mempelajari asas-asas OS. Jadi kalau sudah biasa dengan Linux, BSD dan lain-lain OS yang serupa UNIX, tapi tak ada asas dalam OS, boleh baca buku <span style="font-style:italic;">Operating System: Design and Implementation</span> edisi ketiga, dan berjinak-jinak dengan MINIX 3. Jadi apa yang ada pada MINIX 3 dan ciri-ciri umum OS (dari wikipedia):</p>
<ol style="font-style:italic;">
<li>process management</li>
<li>memory management</li>
<li>disk and filesystem</li>
<li>networking</li>
<li>security</li>
<li>graphical user interfaces</li>
<li>device drivers</li>
</ol>
<p>Apa yang tiada dalam minix ialah <span style="font-style:italic;">swap memory(virtual memory management?)</span>. Arahan <a href="http://www.minix3.org/manpages/man1/chmem.1.html">chmem</a> adalah perlu untuk menambah memori.</p>
]]></content:encoded>
</item>
<item>
<title><![CDATA[Mari belajar OS!]]></title>
<link>http://pengendali.wordpress.com/2008/04/02/aku-nak-belajar-os/</link>
<pubDate>Tue, 01 Apr 2008 21:31:57 +0000</pubDate>
<dc:creator>Kudin</dc:creator>
<guid>http://pengendali.wordpress.com/2008/04/02/aku-nak-belajar-os/</guid>
<description><![CDATA[MINIX 3, versi terbaru MINIX, ialah sistem pengendalian(OS) yang dibangunkan bagi tujuan pendidikan.]]></description>
<content:encoded><![CDATA[<p><img src="http://pengendali.wordpress.com/files/2008/04/minix-racoon.jpg" alt="minix-racoon.jpg" align="left" /><a href="http://www.minix3.org/" target="_blank">MINIX 3</a>, versi terbaru MINIX, ialah sistem pengendalian(OS) yang dibangunkan bagi tujuan pendidikan. Dengan jumlah kod kernel yang kecil, MINIX amat sesuai untuk pelajar dan peminat OS untuk mempelajari asas-asas OS. Jadi kalau sudah biasa dengan Linux, BSD dan lain-lain OS yang serupa UNIX, tapi tiada asas dalam OS, boleh baca buku <span style="font-style:italic;">Operating System: Design and Implementation</span> edisi ketiga, dan berjinak-jinak dengan MINIX 3. Jadi apa yang ada pada MINIX 3 dan ciri-ciri umum OS (dari wikipedia):</p>
<ol style="font-style:italic;">
<li>process management</li>
<li>memory management</li>
<li>disk and filesystem</li>
<li>networking</li>
<li>security</li>
<li>graphical user interfaces</li>
<li>device drivers</li>
</ol>
<p>Apa yang tiada dalam MINIXialah <span style="font-style:italic;">swap memory(virtual memory management?)</span>.</p>
]]></content:encoded>
</item>
<item>
<title><![CDATA[Quote from Reliable Systems]]></title>
<link>http://rafavargas.wordpress.com/2008/03/28/quote-from-reliable-systems/</link>
<pubDate>Fri, 28 Mar 2008 20:54:12 +0000</pubDate>
<dc:creator>Rafa Vargas</dc:creator>
<guid>http://rafavargas.wordpress.com/2008/03/28/quote-from-reliable-systems/</guid>
<description><![CDATA[&#8220;The goal of reliable systems will have been achieved when no computer has a RESET button and ]]></description>
<content:encoded><![CDATA[<blockquote><p>"The goal of reliable systems will have been achieved when no computer has a RESET button and no user has ever experienced a crash and does not know anyone personally who has ever experienced a crash."</p></blockquote>
<div style="text-align:right;">Andrew S. Tannenbaum.</div>
]]></content:encoded>
</item>
<item>
<title><![CDATA[Operating systems...]]></title>
<link>http://pranith.wordpress.com/?p=4</link>
<pubDate>Sat, 02 Feb 2008 14:13:52 +0000</pubDate>
<dc:creator>pranith</dc:creator>
<guid>http://pranith.wordpress.com/?p=4</guid>
<description><![CDATA[I&#8217;ve been reading quite a few things lately. The microkernel vs monolithic kernel debate seems]]></description>
<content:encoded><![CDATA[<p>I've been reading quite a few things lately. The microkernel vs monolithic kernel debate seems to continue. It is true that the idea of having a highly modularized kernel sounds very interesting. But according to experts it is very hard to actually implement and carries a significant amount of overhead. But, once the core part of it is done the rest of the system should be easier to develop owing to the modularized nature. It might also be highly robust since one component of the system cannot affect another component since they are separated. Andy Tanenbaum, the venerable academic whose research areas include secure and reliable systems has always advocated the idea of a microkernel. He, along with a student Jorrit N. Hereder have redeveloped Minix (the father of linux) into it's current version 3. Will be trying it out very soon.</p>
]]></content:encoded>
</item>
<item>
<title><![CDATA[MINIX 3.1.2 image released]]></title>
<link>http://virtualbox.wordpress.com/?p=23</link>
<pubDate>Sun, 27 Jan 2008 13:57:19 +0000</pubDate>
<dc:creator>Emanuele Cipolla</dc:creator>
<guid>http://virtualbox.wordpress.com/?p=23</guid>
<description><![CDATA[A minimal MINIX 3.1.2 image has been released. You can grab it here.
Note that, as the MINIX k]]></description>
<content:encoded><![CDATA[<p align="justify">A minimal MINIX 3.1.2 image has been released. You can grab it <a TITLE="MINIX 3.1.2 image" HREF="/images/minix/#minix312">here</a>.</p>
<p align="justify">Note that, as the MINIX kernel AFAIK does not support the network<br> card VirtualBox emulates, you'll have to download <a TITLE="The MINIX 3.1.2 ISO image" TARGET="_blank" HREF="http://www.minix3.org/download/IDE-3.1.2a.iso.zip">the official ISO image</a> to add new packages through packman, the MINIX 3 package manager.</p>
]]></content:encoded>
</item>
<item>
<title><![CDATA[Distributions, the Focus &amp; the Future]]></title>
<link>http://vinci.wordpress.com/2008/01/09/distributions-the-focus-m-the-future/</link>
<pubDate>Wed, 09 Jan 2008 15:56:46 +0000</pubDate>
<dc:creator>vinci</dc:creator>
<guid>http://vinci.wordpress.com/2008/01/09/distributions-the-focus-m-the-future/</guid>
<description><![CDATA[Looking at the development of Foresight Linux and other distributions I got some thoughts about comm]]></description>
<content:encoded><![CDATA[<p>Looking at the development of Foresight Linux and other distributions I got some thoughts about common problems. One thing I think where the BSDs but also Minix and Plan9 are better is the fact that they tend to build their own software, meaning that they are often not such a mess of so many upstream projects. But still there are similar problems like when they use ported software. Lets look at a standard desktop: This includes a kernel and an operating system - and then some base software and some graphical server. BSDs and Linux both use<br />
X11/Xorg here, which means its basicall not a project native to a BSD. Also they present window managers like GNOME, KDE, whatever who also have different development focusses. And then a whole lot of "applications". What is bad about that? I think the problem is that if a distribution or operating system uses a lot of applications that are not really generated to be used by the distribution but only "ported" it always means that you need to add work to make it work on the special environment. All Unices share some environments, so many things will just work - and also if applications are compiled for a specific platform the configuration scripts change some locations and behavior to fit the environment. But this means that when writing an "application" or "library" or whatever the author must think about and know these environments. Classical Unix commands were traditionally build for a specific Unix - so this also meant that there was going on a lot of extra work for the different Unices. So ported code is something that got more popular with Linux and the GNU tools and also with the idea of Free/Libre Open Source Software. But still this means that portability is a burden - and also it seems questionable if all this diversity of languages, libraries, software  is needed or good for a working environment. The ability to share code is a good thing, there is no doubt about that. But I also think portability massively slows down the development of software and although it reduces the need to repeatedly work on similar code on different platforms it also adds the need to have all supported platforms in the mind when adding code. Often the results are not foreseeable. Not being able to foresee the results means that things can not be planned as good as possible and it also means that working on portability and compatibility is becoming a major task. And if you also see all this different programs and know that they all interact wth each other the possible flaws and bugs are growing daily with more software and more features. So in open source software the development often goes into developing abstraction layers like hal/dbus, so that the applications interact only with the abstraction layer, while others work on the interaction of the abstraction layer with the hardware etc.. Thats one solution for the problem, but it also adds another layer of interaction where things can go wrong. I am not sure if we really will end up with systems that are easier because we have abstraction layers that help application programers to interact with the underlaying system. I am not sure if this doesn't rather add more complexity and really does not make things more simple.<br />
Where I becoming sceptical is at the point where I think nobody really has a big picture on projects like Gstreamer+Xorg+Dbus/Hal, Pulseaudio, etc etc. Everybody has some part of the picture but mostly I think people are focussing ony solving their own problems. So somebody sees one problem and begins working on code that targets this problem. Maybe he will be able to produce some software that accomplishes the targeted goal - but if this project gets a dependency it also means other projects and people depend on this work. Like lets say FreeBSD  now also uses hal, but maybe hal is not that well supported as on Linux. Then if software like GNOME has hal as a dependency this also means FreeBSD will have to support a software that might for some reasons not have the quality that they wish it would have. This can have two different outcomes: a) Either a distribution decides that it cant support this software any more or b) it will find a way to invest some time to make it work. I guess Slackware chose the way a) as it decided not to support GNOME any more. There is maybe the third way: proclaiming a focus. OpenBSD says it only supports the core software. Linux distributions nowadays often declare that GNOME desktop is their focus (some still say its KDE for them). This means that you articulate: If you want support use this software - if you use something else do it at your own risk. Fair enough. But many of these decisions are not transparent to the user. So maybe he thinks its nice to to away from Windows and switch to ... Linux - but he might end up using a Linux that does not support the software he may want to use as good as he likes. You may now say that this is not a problem as he can switch. But I think switching is not what should be something a user should do often - or always when his distribution switches its politics. So if somebody has used GNOME - if then Slackware has decided to dump supporting GNOME it might be painful to switch.</p>
<p>The older I get the more I admire trustworthyness of software. Meaning: these points:</p>
<ul>
<li> If I boot up my computer tomorrow, will it still work as expected?</li>
<li>If the projects says its going to make a new release on date X, will I really get new software on this date?</li>
<li>If I have a problem with some old data and the software gets renewed - will i get support tomorrow or in some years from now?</li>
<li>Is this free software - meaning can I do with it what I want or am I trapped?</li>
</ul>
<p>These are some basic points that are becoming more and more important to me - maybe this means I am getting old? ;-) Well I still like fresh ideas and new functionality - but I tend to dislike a system that breaks - where I cant update software or cant boot or Xorg crashes or I loose data. If I loose data then please only if I decide to use experimental software.</p>
<p>Open question is which operating system gives me what I want. One thing is for sure: You do not get that from something like Gentoo. Gentoo seems to me more for people who want to either have the possibility to use the latest software or to be able to easily compile software customized to their preferences. The problem is that you also HAVE to compile and do all the work in order to have an acceptable system. You can not ignore all the possibilities but often have to declare what you prefer even if you have no idea of what all these USE flags mean. Debian? From my experience Debian is not all about stability. It may often sound as Debian gives me what I just wrote above but I often have experienced dramatic switches of software behavior and also you are forced to answer so many damn questions on each update - and if you want to ignore you may end up in a state where you cant use your software. I often was at the point where I repeatedly had to try a dpkg-reconfigure in order to not only set the settings the way I like but also in  a way that Debian (dpkg) remembers and not just overwrites on next update. What else do we have? Ubuntu and Fedora? Both are sure respectful distributions with a bunch of good software but on the other hand they did make some strange decisions in the past and I would not like to depend on one of them. Now to my current favorite: Foresight: The package manager conary is great - it focuses on GNOME and also has always met its release deadlines. But if you look at some details there are so many flaws which are not targeted as they should be. I still think Foresight maybe is the greates Linux distro around especially because of the mix of the best package manager around, the focus and the ability to package oneself with great ease. But still it suffers from the fact that it needs to support a lot of upstream projects which are not as cooperative sometimes as they should be. And I have found that I can not depend on it like connecting some random scanner or camera and it will work. But this is not due to the fact that those hardware is not supported on Linux in general - its rather because the packages are not as good as they need to be and many hardware not well tested. I hate to say that again, but its the truth. The way out would be to have more people and more testing and more knowledge about all the possible problems. I am quite optimistic that Foresight can and will become the best distribution around because it makes development much easier and if it would have the manpower of Ubuntu it sure would outact it.</p>
<p>But there is still the problem for me that I need a more reliable system as my productive machine - and I tend to believe that I wont get it in the Linux world. The BSDs have some flaws like not as good hardware support and some software wont work there - like you dont get the latest GNOME on OpenBSD. Everything has pros and cons - and everybody has to decide which operating system meets his own interest best. One thing I cant stand any more is that since I had my first computer which was an Amiga 2000 with 8MhZ I experience sometimes or often high load averages and situations where the graphical user interface seems to freeze or working with it becoming extremely slow. I am no longer accepting that. I dont want to wait for stupid tasks to finish. I accept that if I do some actions at once like compiling and watching a video - that this might kind of "freeze" my computer because he needs to do so much - but I am not accepting a high load for my everyday work. The relation needs to fit - so extreme tasks may take up a lot of CPU - but listenng to a stupid OGG file may NOT.</p>
<p>I havent seen any progress on any of the current Linux desktops to really solve that problem. That way also one of the reasons why I started working with wmii partly. I never really understood how people could use Debian with a GNOME from stoneage - and I stll cant really - but what I can understand now is that the latest software does not always have to be the greatest - given that you have the software that you need. I currently do not have all that. I like to be able to print some letters, listen to music, watch videos and edit some photos, the rest is maybe random internet usage. I have yet not worked very much with LaTeX but maybe that could play a role in not depending on OpenOffice.org. I know this would mean to learn some more about it to be able to do some similar things - but it should be achievable. I know that I will not be able to expect random hardware to work - and I am not expecting that any more. But I still like to be able to work with some new hardware like USB sticks etc. without much configuration.</p>
<p>I guess maybe OpenBSD is not as good on desktop - maybe NetBSD. Any suggestions? I think I leave out Plan9 for now. Minix maybe?</p>
]]></content:encoded>
</item>

</channel>
</rss>
