<DIV> </DIV>
<DIV>Dear All,</DIV>
<DIV>In our view a doubts expressed by some quarters regarding RedHat is no longer being a viable option are unfounded. Because we should acknowledge the people at Red Hat Inc, who despite the massive shift in direction of their Red Hat Linux have managed to once again produce a rock solid Red Hat Fedora Linux version 1 which can be treated as Red Hat version 10, for the continuity of the Red Hat. Now this RedHat version will be continue in the name of Fedora.</DIV>
<DIV>Comparing Fedora and Enterprise Packages</DIV>
<DIV>The Fedora project was set up a "proving ground" for developing technology that can be used by RedHat, Inc to include in its Red Hat Enterprise Linux products. Because the separation of RedHat Linux into the Fedora project and Enterprise Linux is still quite new, there is significant overlap between the packages included in the two directions.</DIV>
<DIV>The following bullets are intended to give you a flavor of the differences between the Fedora core software included with this and the RedHat Enterprise Linux software you can purchase from Red Hat, Inc.</DIV>
<DIV>* Many personal use packages in Fedora are not included in the Enterprise districbution. For example, enterprise contains fewer for playing and ripping music (no cdp, cdda2wav, cdrdao, or grip packages), fewer games (no freeciv, maelstrom or tuxracer) and fewer personal proudctivity tools (no gnucash, gnumeric, abiword, or koffice)</DIV>
<DIV>* Most packages in Enterprise that are not in Fedore are those that are needed particularly for high demand, high availability servers. Enterprise packages not in Fedora include kernel software that can utilise large amounts of RAM (kernel-hugemem), tools for configuring diskless workstations (redhat-config-netboot) and monitoring tools (crash)</DIV>
<DIV>Although the timing of the releases of Fedora Core and Red Hat Enterprise Linux version 3 may make some version numbers different, there are literally hundreds of software packages that are the same in the two distributions.</DIV>
<DIV> </DIV>
<DIV>Now the latest distribution contains kernel 6.2 and KDE 3.2 etc,. While building the base OS for Bio-Linux you can install and configure the latest applications available and bundle with Bioinformatics softwares.</DIV>
<DIV> </DIV>
<DIV>In the meanwhile, debian is also a strong Linux Distribution. But any debian application is available for scientific purpose can be easily converted using alien command.</DIV>
<DIV> </DIV>
<DIV>At the same time the entire base system need not be change for Bio-Linux frequently instead you can concentrate on adopting more Bioinformatics, Biotechnology application for integration with the base system.</DIV>
<DIV> </DIV>
<DIV>These are our suggestions only for further thinking and deliberations.</DIV>
<DIV>Thanking you,</DIV>
<DIV>Yours Sincerely,</DIV>
<DIV>M.S.Yatnatti,</DIV>
<DIV>CEO, Biotechinfobytes,</DIV>
<DIV>Super computer aided Biotechnology Programme center</DIV>
<DIV>University of Agricultural Sciences, Hebbal Campus</DIV>
<DIV>Bangalore - 560 024<BR><BR><B><I>bio-linux-request@ivsun01.nerc-oxford.ac.uk</I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="BORDER-LEFT: #1010ff 2px solid; MARGIN-LEFT: 5px; PADDING-LEFT: 5px">Send Bio-Linux mailing list submissions to<BR>bio-linux@bioinf.ceh.ac.uk<BR><BR>To subscribe or unsubscribe via the World Wide Web, visit<BR>http://www.bioinf.ceh.ac.uk/mailman/listinfo/bio-linux<BR>or, via email, send a message with subject or body 'help' to<BR>bio-linux-request@bioinf.ceh.ac.uk<BR><BR>You can reach the person managing the list at<BR>bio-linux-admin@bioinf.ceh.ac.uk<BR><BR>When replying, please edit your Subject line so it is more specific<BR>than "Re: Contents of Bio-Linux digest..."<BR><BR><BR>Today's Topics:<BR><BR>1. Bio-Linux future directions - OS choice. (Dan Swan)<BR>2. Re: Bio-Linux future directions - OS choice. (Chris Beck)<BR>3. Re: Bio-Linux future directions - OS choice. (Dan Swan)<BR><BR>--__--__--<BR><BR>Message: 1<BR>Date: Tue, 09 Mar 2004 16:16:52 +0000<BR>From: Dan Swan <DSWAN@CEH.AC.UK><BR>Reply-To: dswan@ceh.ac.uk<BR>Organization: Centre For
Ecology and Hydrology<BR>To: bio-linux@ivsun01.nerc-oxford.ac.uk<BR>Subject: [Bio-Linux] Bio-Linux future directions - OS choice.<BR><BR>Dear All,<BR><BR>As you know we have been continuing to work on the development of the<BR>Bio-Linux system and one of the recent considerations has been what<BR>operating system to base Bio-Linux on now that Red Hat is no longer a<BR>viable option. We would like to let you know the progress of our<BR>evaluation and ask for any feedback you may have about the choice of<BR>base level systems for further Bio-Linux development.<BR><BR>We began the evaluation by installing and working with a number of<BR>possible base Linux systems. Through discussion with other EGTDC<BR>members and staff from the CEH IT support team (CCS), we then narrowed <BR>the field to two systems for further testing, based on the requirements <BR>we felt most important for Bio-Linux, such as stability, future support, <BR>ease of updating once deployed and ease of
administration.<BR><BR>The two base systems chosen for further evaluation were Debian,<BR>installed from a Knoppix Live-CD, and Fedora. The evaluation consisted<BR>of installing these systems on identical platforms, and having members<BR>of the EGTDC at CEH Oxford work on the machines over a two week<BR>period, noting their impressions of the systems with regards to general<BR>usability, as well as how the systems performed when used for specific<BR>tasks.<BR><BR>A full discussion of the experiences and impressions people had about<BR>these two systems took place during the Bio-Linux strategy meeting on<BR>March 5, 2004, which was attended by CEH Oxford EGTDC members and two<BR>members of the local CCS staff.<BR><BR>A number of key points were raised about the systems during this<BR>meeting:<BR><BR>KDE vs. Gnome:<BR>Overall feelings suggested that the KDE interface of Knoppix/Debian<BR>was preferable to the Gnome interface in Fedora. This was more to do <BR>with responsiveness and
ease of menu configuration than look and feel.<BR>Comments were made to the effect that the Bio-Linux look and feel could<BR>be maintained on both platforms through the Bluecurve theme.<BR><BR>Apt-get vs. rpm:<BR>The biggest difference to the two systems is the use of apt-get in<BR>Debian versus rpm in Fedora. Comments were made that yum commands for<BR>interacting with rpm's are very close to those of apt-get. Various<BR>utilities were installed through apt-get on the Debian system, and<BR>comments were positive about the interactive configuration it allows<BR>when being updated.<BR><BR>Menu-based system configuration:<BR>Comments regarding the use of menu based configuration focused on the<BR>fact that the configuration tools for Fedora are more polished and<BR>more comprehensive than Knoppix but that printer configuration and user<BR>administration which were most likely to be used were present on<BR>Knoppix.<BR><BR>Pre-installed packages:<BR>There were comments regarding
packages not present on Knoppix that are<BR>present on Fedora but it was agreed that this could be easily be<BR>remedied during remastering if a significant number of packages needed<BR>to be added in.<BR><BR>Bioinformatics applications:<BR>All bioinformatics applications were tested at a basic level on both<BR>platforms. As expected, no significant problems were found with<BR>Fedora as it is quite close to Bio-Linux 3.0's current base system. All<BR>packages ran equally under Knoppix once some compatibility libraries<BR>for C++ were installed.<BR><BR>Conclusions:<BR><BR>Overall a unanimous preference for Knoppix/Debian was expressed; some<BR>key differences that led to this preference are outlined below:<BR><BR>Firstly, and very importantly, we felt that the Debian base of Knoppix<BR>will prove to be more stable than any other distribution. This means<BR>that the base system is likely to require major updating less often, and<BR>that the major system updates that do become
necessary are likely to be<BR>easily executed and go smoothly.<BR><BR>The KDE interface, supplied by default with KDE/Debian, is crisper and<BR>more responsive than the Gnome interface, supplied by default with<BR>Fedora. It is also much easier to configure, which is essential both for <BR>the Bio-Linux development team as we endeavor to produce a user-friendly <BR>system, and also for users themselves to adapt their environment to best <BR>suit their working habits.<BR><BR>Another factor is that the Knoppix remastering process is well<BR>documented and has a well supported community and will reduce the<BR>hardware requirements for our current build methods.<BR><BR>We would be interested to hear from anyone that has opinions about the<BR>continuation of development on a Knoppix-Debian system, as input from<BR>the user community is always welcome.<BR><BR>We hope to release a Bio-Linux 4.0 alpha publically for feedback in the <BR>not too distant future, announcements will be made
here.<BR><BR>regards,<BR><BR>Dan<BR>-- <BR>Dr Dan Swan - Bio-Linux Developer | RHCE<BR>EGTDC, CEH, Mansfield Road, Oxford, OX1 3SR<BR>Tel: 01865 281 658 Fax: 01865 281 696<BR>http://envgen.nox.ac.uk/ | dswan@ceh.ac.uk<BR><BR>--__--__--<BR><BR>Message: 2<BR>Date: Tue, 09 Mar 2004 12:30:32 -0500<BR>From: Chris Beck <CBECK@GENE.CONCORDIA.CA><BR>CC: bio-linux@ivsun01.nerc-oxford.ac.uk<BR>Subject: Re: [Bio-Linux] Bio-Linux future directions - OS choice.<BR><BR>Speaking as a non-grant user I have only one caveat. It might be wise to also take into consideration the distribution that the bio <BR>packages are built-developed under ... if they track a fast moving distro like fedora (which will be moving to kernel 2.6 within the <BR>next few months then a slow moving distro like debian might fall behind. That, of course, is contingent on the pakcages in question <BR>being closely tied to the underlying system, if they are loosely coupled then no worries.<BR><BR>Cheers,<BR>Chris<BR><BR>It is
whispered that Dan Swan was heard, on or about 09/03/04 11:16 AM to say:<BR><BR>> Dear All,<BR>> <BR>> <BR>> Firstly, and very importantly, we felt that the Debian base of Knoppix<BR>> will prove to be more stable than any other distribution. This means<BR>> that the base system is likely to require major updating less often, and<BR>> that the major system updates that do become necessary are likely to be<BR>> easily executed and go smoothly.<BR>> <BR><BR>-- <BR><BR>Chris Beck / Y.A.B.A. / Fungal Genomics / CFSG / Concordia University<BR>"We do not inherit the Earth from our Ancestors,<BR>we borrow it from our Children."<BR><BR>--__--__--<BR><BR>Message: 3<BR>Date: Wed, 10 Mar 2004 10:01:41 +0000<BR>From: Dan Swan <DSWAN@CEH.AC.UK><BR>Reply-To: dswan@ceh.ac.uk<BR>Organization: Centre For Ecology and Hydrology<BR>To: Chris Beck <CBECK@GENE.CONCORDIA.CA><BR>CC: bio-linux@ivsun01.nerc-oxford.ac.uk<BR>Subject: Re: [Bio-Linux] Bio-Linux future directions - OS
choice.<BR><BR>Chris Beck wrote:<BR>> Speaking as a non-grant user I have only one caveat. It might be wise <BR>> to also take into consideration the distribution that the bio packages <BR>> are built-developed under ... if they track a fast moving distro like <BR>> fedora (which will be moving to kernel 2.6 within the next few months <BR>> then a slow moving distro like debian might fall behind. That, of <BR>> course, is contingent on the pakcages in question being closely tied to <BR>> the underlying system, if they are loosely coupled then no worries.<BR><BR>In my experience bioinformatics software tends not to track the latest <BR>jumps in gcc versions too quickly, although this is rarely a problem as <BR>a quick install of the libstdc++ backwards compatibilty libraries tends <BR>to fix and issues. I think there is a general reaction to wait for <BR>platforms to be seen to be stable, I know I have not made the switch to <BR>a 2.6 kernel yet.<BR><BR>The
Debian install that Knoppix does is actually very up to date as it <BR>tracks certain elements from testing/unstable (for those who are worried <BR>about those designations Debian does not describe anything as "stable" <BR>until it has been around for a *very* long time).<BR><BR>Here are the specs from my test Debian/Knoppix machine:<BR><BR>gcc version 3.3.3 (Debian)<BR>This is perl, v5.8.3<BR>Python 2.3.3<BR>java version "1.4.2_02"<BR>ruby 1.8.1 (2004-02-03) [i386-linux]<BR>Linux knoppix 2.4.24-xfs<BR>Apache/1.3.29<BR><BR>And from my test Fedora Core 1 machine:<BR><BR>gcc version 3.3.2 20031022 (Red Hat Linux 3.3.2-1)<BR>This is perl, v5.8.3<BR>Python 2.2.3<BR>java version "1.4.2_03"<BR>ruby 1.8.0 (2003-08-04) [i386-linux-gnu]<BR>Linux fedora 2.4.22-1.2174.nptl<BR>Apache/2.0.48<BR><BR>As you can see they're very close at the moment. I think it's extremely <BR>important to track Perl, Ruby and Python very closely with maintenance <BR>releases and in my experience Knoppix Debian is
much more up to speed <BR>with this than Fedora.<BR><BR>With regards to the bioinformatics packages, we fully intend to create <BR>deb packages on i686 machines here, and then have an apt repository (we <BR>would have done the same for rpm/yum if we had chosen Fedora). This <BR>means we will test and version check the software prior to release.<BR>Also things like BioPerl are already packaged as deb's - this removes <BR>the need for trying to bash through broken CPAN installs and rpm hell <BR>with GD under Fedora. Keeping BioPerl up to date on versions 1-3 has <BR>been a particular bugbear.<BR><BR>I hope this answers some of your concerns.<BR><BR>regards,<BR><BR>Dan<BR><BR>-- <BR>Dr Dan Swan - Bio-Linux Developer | RHCE<BR>EGTDC, CEH, Mansfield Road, Oxford, OX1 3SR<BR>Tel: 01865 281 658 Fax: 01865 281 696<BR>http://envgen.nox.ac.uk/ | dswan@ceh.ac.uk<BR><BR><BR>--__--__--<BR><BR>_______________________________________________<BR>Bio-Linux mailing
list<BR>Bio-Linux@bioinf.ceh.ac.uk<BR>http://www.bioinf.ceh.ac.uk/mailman/listinfo/bio-linux<BR><BR><BR>End of Bio-Linux Digest</BLOCKQUOTE><p><font face=arial size=-1>Do you Yahoo!?<br>
<a href="http://us.rd.yahoo.com/mailtag_us/*http://mail.yahoo.com" target="_blank"><b>Yahoo! Mail</a></b> - More reliable, more storage, less spam