devel

devel@lists.centos.org

4679 discussions

Start a nNew thread

(no subject)
by Jenny Pérez 12 May '09

12 May '09

1 0

RPM contribution
by David Dreggors 11 May '09

11 May '09

Sorry for the double post if there is one. I never saw the first hit the list and I relized I had sent from the wrong account. I would like to contribute an rpm that I built. The rpm is the latest snapshot of the madwifi driver which includes support for the Atheros AR5007EG. This is a popular card and is not supported currently under the ath5k module or the older madwifi driver. I have attached the spec file and the link to the src.rpm is: http://ddhj.homeip.net/madwifi/madwifi-hal-0.10.5.6-6.src.rpm # #Gen the last kernel-devel available on the machine. %{!?kernel: %{expand: %%define kernel %(rpm -q kernel-devel --last | head -1 | awk '{print $1}' | sed s/kernel-devel-// )}} %if %(echo %{kernel} | grep -c smp) %{expand:%%define myksmp -smp} %endif #Define the latest kernel installed %define mykversion %(echo %{kernel} | sed -e s/smp// -) %define mykrelver %(echo %{mykversion} | tr -s '-' '_') #rpm -q kernel --last | head -1 | awk '{print $1}' | sed s/kernel-// | sed -e s/smp// - | tr -s '-' '_' # Define based on the tar ball extract. # Those two variable will be instanced during the tarball generation %define revision r4016 %define snapshot 20090429 # branch is not used yet. %define branch hal-0.10.5.6 Summary: A linux device driver for Atheros chipsets (ar5210, ar5211, ar5212). Name: madwifi-hal Version: 0.10.5.6 Release: 6 License: GPL2 Group: System Environment/Kernel URL: http://madwifi.org Source0: http://snapshots.madwifi-project.org/madwifi-hal-0.10.5.6/madwifi-hal-0.10.… BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-%{revision}-%{snapshot} Requires: /sbin/depmod Requires: %{name}-module >= %{version} BuildRequires: /sbin/depmod BuildRequires: /lib/modules/%{mykversion}/build/Makefile %description This software contains a Linux kernel driver for Atheros-based Wireless LAN devices. The driver supports station, AP, ad-hoc, and monitor modes of operation. The Atheros driver depends on a device-independent implementation of the 802.11 protocols that originated in the BSD community (NetBSD in particular). The driver functions as a normal network device and uses the Wireless Extensions API. As such normal Linux tools can and should be used with it. Where the wireless extensions are lacking private ioctls have been added. There is only one driver included here; it supports PCI, miniPCI and Cardbus devices - USB devices are currently not supported by this driver! The driver can be built as a module or linked directly into the kernel. Note however that the net80211 layer is device-independent; there is no reason it cannot be used with any 802.11 device (in fact on BSD systems this is the case). There are currently 4 "programming generations" of Atheros 802.11 wireless devices (some of these have multiple hardware implementations but otherwise appear identical to users): 5210 supports 11a only 5211 supports both 11a and 11b 5212 supports 11a, 11b, and 11g 242x supports 11a, 11b, and 11g %package module Summary: A linux device driver for Atheros chipsets (ar5210, ar5211, ar5212, ar242x). Group: System Environment/Kernel Requires: kernel = %{mykversion} Release: 6_%{mykrelver} %description module This software is broken into multiple modules. The Atheros-specific device support is found in the ath_pci module; it should be loaded when an Atheros wireless device is recognized. The ath_pci module requires an additional device specific module, ath_hal, which is described more below. In addition the driver requires the wlan module which contains the 802.11 state machine, protocol support, and other device-independent support needed by any 802.11 device. This code is derived from work that first appeared in NetBSD and then FreeBSD. The wlan module may also force the loading of additional modules for crypto support (wlan_wep, wlan_tkip, wlan_ccmp, etc.), for MAC-based ACL support (wlan_acl), and for 802.1x authenticator support (wlan_xauth). The latter modules are only used when operating as an AP. The crypto modules are loaded when keys of that type are created. %prep %setup -q -n %{name}-%{version}-%{revision}-%{snapshot} find . -name Makefile\* | xargs perl -pi -e's,/sbin/depmod,: /sbin/depmod,' %build export MANDIR=/usr/share/man export KERNELRELEASE=%{mykversion} export KERNELPATH=/lib/modules/%{mykversion}/build export KERNELCONF=/lib/modules/%{mykversion}/build/.config export KMODPATH=/lib/modules/%{mykversion}/net export COPTS="-I /lib/modules/%{mykversion}/build/include/ $COPTS" make %install export MANDIR=/usr/share/man export KERNELRELEASE=%{mykversion} export KERNELPATH=/lib/modules/%{mykversion}/build export KERNELCONF=/lib/modules/%{mykversion}/build/.config export KMODPATH=/lib/modules/%{mykversion}/net rm -rf %{buildroot} # make info mkdir -p %{buildroot}/usr/local/bin mkdir -p %{buildroot}/$KMODPATH mkdir -p %{buildroot}/usr/share/madwifi make install DESTDIR=%{buildroot} KERNELPATH=/lib/modules/%{mykversion}/build MANDIR=/usr/share/man # cd tools ; make install DESTDIR=%{buildroot} KERNELPATH=/lib/modules/%{mykversion}/build BINDIR=/usr/local/bin ; cd .. %post module if [ $1 == 1 ] then echo "#Madwifi Driver" >> /etc/modprobe.conf echo "alias ath0 ath_pci" >> /etc/modprobe.conf echo "#Madwifi Driver" >> /etc/modprobe.d/blacklist echo "blacklist ath5k" >> /etc/modprobe.d/blacklist fi /sbin/depmod -ae %{mykversion} %postun module if [ $1 = 0 ] then /bin/sed -i 's/#Madwifi Driver//' /etc/modprobe.conf /bin/sed -i 's/alias ath0 ath_pci//' /etc/modprobe.conf /bin/sed -i 's/#Madwifi Driver//' /etc/modprobe.d/blacklist /bin/sed -i 's/blacklist ath5k//' /etc/modprobe.d/blacklist fi /sbin/depmod -ae %{mykversion} %clean rm -rf %{buildroot} %files %doc COPYRIGHT README INSTALL THANKS %attr(0755,root,root) /usr/local/bin/* %attr(0644,root,root) /usr/share/man/man8/* %files module %defattr(-,root,root,-) /lib/modules/%{mykversion}/net/*.*o %attr(0644,root,root) /usr/share/man/man8/* # %changelog * Sun May 10 2009 David Dreggors <ddreggors(a)cfl.rr.com> - Create RPM of snapshot: 20090429 of release: r4016 * Wed Dec 14 2005 Patrick Pichon <Patrick.Pichon(a)laposte.net> - Update accordingly to the new file name rule: madwifi-ng-r<revision>-<generation date>.tar.gz - 'branch' tag is not use yet. 'ng' is hardcoded as part of the file name - Change the computation to target the latest kernel-devel env. * Thu Nov 3 2005 Patrick Pichon <Patrick.Pichon(a)laposte.net> - Incorporate the changes made on the Makefile - Cleaning on the Description fields - Changing the URL to the new madwifi.org's one. - Install under /usr/share/doc/madwifi-release the INSTALL and THANKS files - Install under /usr/share/doc/madwifi-release the docs files. * Sun Oct 30 2005 Patrick Pichon <Patrick.Pichon(a)laposte.net> - Add Man pages * Mon Oct 24 2005 Lyonel Vincent <> - Fix the --rebuild option. * Mon Oct 3 2005 Lyonel Vincent <> - Build by default on latest kernel installed * Wed Jul 20 2005 Patrick Pichon <Patrick.Pichon(a)laposte.net - target particular kernel * Mon Oct 27 2004 Patrick Pichon <Patrick.Pichon(a)laposte.net> - Handle 2.4 kernel * Mon Sep 21 2004 Lyonel Vincent <> - change the naming of the kernel module part. * Mon Aug 23 2004 Patrick Pichon <Patrick.Pichon(a)laposte.net> - Update WPA has been merged into HEAD * Mon Jul 27 2004 Patrick Pichon <Patrick.Pichon(a)laposte.net> - Update to handle WPA branch. * Tue Jul 08 2004 Patrick Pichon <Patrick.Pichon(a)laposte.net> - Initial Release

3 3

Re: [CentOS-devel] [CentOS] jigdo images
by Scott Dowdle 08 May '09

08 May '09

Ralph, ----- "Ralph Angenendt" <ra+centos(a)br-online.de> wrote: > Shad L. Lords wrote: > > I'd guess that your basic os tree you created isn't in the same format > > as the mirrors then. I'm running it against the non-dvd mirror that I > > have and my results are below. > > > > -rw-r--r-- 1 root 34K May 7 11:32 CentOS-5.3-i386-bin-1of6.jigdo > > Can you mail that file around? The first 50 or so lines would be > enough. I still seem to have a problem with label and URI generation in the > .jigdo files. > > This is the file I get with the following command (which is missing > the --uri section): > > jigdo-file make-template \ > --image=/home/admin/iso/CentOS-5.3-i386-bin-DVD.iso \ > /local/mirror/linux/centos/5/os/i386/ \ > --label CentOS5-i386=/local/mirror/linux/centos/5/os/i386/ \ > --jigdo=/home/admin/iso/result/CentOS5-i386.jigdo \ > --template=/home/admin/iso/result/CentOS5-i386.template > > [Parts] > GFckbEI56dspBqCKRYqrwA=A:local/mirror/linux/centos/5/os/i386/CentOS/Cluster_Administration-as-IN-5.2-1.el5.centos.noarch.rpm > 68-TbW5iS6FcKlD_RWzOJQ=A:local/mirror/linux/centos/5/os/i386/CentOS/Cluster_Administration-bn-IN-5.2-1.el5.centos.noarch.rpm > iqQceDWNEj-0pWNDYajgQw=A:local/mirror/linux/centos/5/os/i386/CentOS/Cluster_Administration-de-DE-5.2-1.el5.centos.noarch.rpm Using a recent .jigdo file produced by the Fedora Unity folks for a Fedora 10 respin, I constructed two jigdo files for CentOS 5.3, one for each arch... but the could be combined into a single file if desired. The sample I used was: http://jigdo.fedoraunity.org/templates/20090414/Fedora-Unity-20090414-10.ji… You can find the two files I created here: http://img.cs.montana.edu/linux/centos/5/isos/jigdo/CentOS-5.3-i386.jigdo http://img.cs.montana.edu/linux/centos/5/isos/jigdo/CentOS-5.3-x86_64.jigdo Each one has multiple [Image] defs for all of the CDs and the DVD so that you can download one jigdo and then decide what which CD(s) or DVD you want to create. I just have some questions about some of the things found in the Fedora Unity .jigdo that don't seem to be documented in the jigdo-file man page. For example they have a [Mirrorlists] section and I'm not sure what that is about because they also have a lengthy [Servers] section. In the two .jigdo files I mention about the URLs for [Server] are static but it would be nice to have a URL that would dynamically rotate between various mirror sites to spread the download across more of the CentOS mirrors... rather than the handful of mirror URLs I put in there... which I'm thinking is what the [Mirrorlists] thing is all about?!? So far as not getting the jigdo-file command line just perfect... his recipe did work once I discovered the i386 reference that should have been $arch... and altered the rsync --exclude for my different source directory... but to construct my more complex, multiple [Image] .jigdo files I had to cheat and use a text editor. To get all of the parts I simply: grep '=CentOS:' *i386*.jigdo | sort | uniq > parts-i386.txt grep '=CentOS:' *x86_64*.jigdo | sort | uniq > parts-x86_64.txt So far I've really enjoyed learning about jigdo but want to learn more. :) TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work]

1 0

Re: [CentOS-devel] [CentOS] jigdo images
by Scott Dowdle 08 May '09

08 May '09

Shad, ----- "Shad L. Lords" <slords(a)lordsfam.net> wrote: > Scott Dowdle wrote: > > Shad, > > > > ----- "Shad L. Lords" <slords(a)lordsfam.net> wrote: > >> From the os directory something like this should produce jigdo > >> files/templates for all associated iso files. > >> > >> for arch in i386 x86_64 > >> do > >> rsync -a --delete --delete-excluded \ > >> --exclude 'repodata/' --exclude 'EULA' \ > >> --exclude 'GPL' --exclude 'NOTES/' \ > >> --exclude 'RELEASE-NOTES*' --exclude 'RPM-GPG-KEY*' \ > >> --link-dest=../$arch/ $arch/ ${arch}.jigdo/ > >> > >> for iso in $(find ../isos/i386/ -name '*.iso' -size +100000) > >> do > >> jigdo-file make-template --force -i $iso \ > >> -j ${iso%.iso}.jigdo -t ${iso%.iso}.template \ > >> --label CentOS=$arch.jigdo/ \ > >> --uri > CentOS=http://mirror.centos.org/centos/5/os/$arch/ > >> \ > >> ${arch}.jigdo// > >> done > >> done > >> > >> After the files/templates are created they can be moved to a > >> different/better location as well as updating the Servers section if > >> desired. > > > > Thanks for the recipe. Worked for me. My only complaint is that the > > .template files are about 2/3rds the size of the .iso they are for... > > so you end up downloading 2/3rds of an ISO as a template, then all of > > the files that make up the media... and then have to process it for > > your own .iso. > > > > If you have a local copy of a the repos it pulls from that is handy... > > but if not, it seems to be significantly more downloading for the > > end user than just the .iso media... and the only transfer savings > > for the provider of the .jigdo (rather than providing the .isos) > > is that 1/3rd-ish savings over the .iso. > > > > Is that how it is supposed to work? > > I don't have the DVD iso so I'm not sure about that one but when I ran it > for the CD iso's I got a template of about 15MB for disc1 and < 1MB for > each of the other discs. If you remove the exclude for NOTES/ from the > rsync then the template drops to < 5MB (but you have to download all > the release notes). > > Are you sure you had a complete rsync of the os directory without excluding > anything prior to running the above command? This was really more a recipe > for the CentOS folks to as an example of how easy it would be to create > jigdo/template files from their master area that could then be pushed > to the mirrors for everyone to enjoy. Yes, I had complete os/ trees. I basically mounted the DVD iso and copied everything from it. Here's the results I get after running your script: [root@img i386]# pwd /var/www/html/linux/centos/5/isos/i386 [root@img i386]# ls -lha total 13G drwxr-xr-x 2 root root 4.0K May 6 14:37 . drwxr-xr-x 4 root root 4.0K Mar 27 11:58 .. -rw-r--r-- 1 root root 624M Mar 21 10:17 CentOS-5.3-i386-bin-1of6.iso -rw-r--r-- 1 root root 13K May 6 14:48 CentOS-5.3-i386-bin-1of6.jigdo -rw-r--r-- 1 root root 482M May 6 14:48 CentOS-5.3-i386-bin-1of6.template -rw-r--r-- 1 root root 637M Mar 21 10:18 CentOS-5.3-i386-bin-2of6.iso -rw-r--r-- 1 root root 13K May 6 15:22 CentOS-5.3-i386-bin-2of6.jigdo -rw-r--r-- 1 root root 411M May 6 15:22 CentOS-5.3-i386-bin-2of6.template -rw-r--r-- 1 root root 635M Mar 21 10:19 CentOS-5.3-i386-bin-3of6.iso -rw-r--r-- 1 root root 25K May 6 14:43 CentOS-5.3-i386-bin-3of6.jigdo -rw-r--r-- 1 root root 388M May 6 14:43 CentOS-5.3-i386-bin-3of6.template -rw-r--r-- 1 root root 632M Mar 21 10:20 CentOS-5.3-i386-bin-4of6.iso -rw-r--r-- 1 root root 14K May 6 15:12 CentOS-5.3-i386-bin-4of6.jigdo -rw-r--r-- 1 root root 354M May 6 15:12 CentOS-5.3-i386-bin-4of6.template -rw-r--r-- 1 root root 638M Mar 21 10:21 CentOS-5.3-i386-bin-5of6.iso -rw-r--r-- 1 root root 5.1K May 6 15:07 CentOS-5.3-i386-bin-5of6.jigdo -rw-r--r-- 1 root root 383M May 6 15:07 CentOS-5.3-i386-bin-5of6.template -rw-r--r-- 1 root root 625M Mar 21 10:22 CentOS-5.3-i386-bin-6of6.iso -rw-r--r-- 1 root root 3.3K May 6 15:16 CentOS-5.3-i386-bin-6of6.jigdo -rw-r--r-- 1 root root 599M May 6 15:16 CentOS-5.3-i386-bin-6of6.template -rw-r--r-- 1 root root 3.7G Mar 31 08:38 CentOS-5.3-i386-bin-DVD.iso -rw-r--r-- 1 root root 71K May 6 15:04 CentOS-5.3-i386-bin-DVD.jigdo -rw-r--r-- 1 root root 2.6G May 6 15:04 CentOS-5.3-i386-bin-DVD.template -rw-r--r-- 1 root root 8.3M Mar 21 09:05 CentOS-5.3-i386-netinstall.iso -rw-r--r-- 1 root root 505 Mar 31 08:33 md5sum.txt -rw-r--r-- 1 root root 741 Mar 31 08:33 md5sum.txt.asc -rw-r--r-- 1 root root 569 Mar 31 08:33 sha1sum.txt -rw-r--r-- 1 root root 805 Mar 31 08:33 sha1sum.txt.asc As you can see, my .template files are about 2/3rds the size of the .iso they are for. What's up with that? When I ran your script I was inside of the os/ dir... and there are i386 and x86_64 dirs there... and it as part of the process created i386.jigdo/ and x86_64.jigdo/ directories... and copied everything from the i386 and the x86_64 dirs into the .jigdo directories... so maybe I'm doing something wrong? TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work]

3 5

Re: [CentOS-devel] [CentOS] jigdo images
by Shad L. Lords 08 May '09

08 May '09

Ralph Angenendt wrote: >> I have been looking what Fedora is (or was) doing with Jigdo. It seems >> to solve some problems and create new ones[1]. > > Let me look into that. From the os directory something like this should produce jigdo files/templates for all associated iso files. for arch in i386 x86_64 do rsync -a --delete --delete-excluded \ --exclude 'repodata/' --exclude 'EULA' \ --exclude 'GPL' --exclude 'NOTES/' \ --exclude 'RELEASE-NOTES*' --exclude 'RPM-GPG-KEY*' \ --link-dest=../$arch/ $arch/ ${arch}.jigdo/ for iso in $(find ../isos/i386/ -name '*.iso' -size +100000) do jigdo-file make-template --force -i $iso \ -j ${iso%.iso}.jigdo -t ${iso%.iso}.template \ --label CentOS=$arch.jigdo/ \ --uri CentOS=http://mirror.centos.org/centos/5/os/$arch/ \ ${arch}.jigdo// done done After the files/templates are created they can be moved to a different/better location as well as updating the Servers section if desired. Hope this helps someone, -Shad

3 4

Portal for br.centos.org or pt_br.centos.org
by Thiago Avelino 07 May '09

07 May '09

Hi, my name is Thiago Avelino, I'm Brazilian, talks in Brazil on CentOS (RedHat), part of porjeto LXDE (Development). First I want to know when we have the CentOS website of Brazil, and I actively helping put this content on the portal, the portal can be CentOS BR bringing more public Brazilian (Spanish) to use and help the CentOS. Today I have a mirror of CentOS in Brazil (mirror.centos-br.org) If you need help in mounting the structure to be putting the portals for parents I am here to help, work actively with (WordPress, Drupal, phpBB and XOOPS) We will be structured so as soon as possible that only the CentOS grow the community in each country, we have an example with Ubuntu it is a community in each country and it More specifically every day. -- att. Thiago Avelino Programador | SysAdmin Linux User: #484673 Asterisk User: #63483 Digium User: D1039273 São Paulo - SP / Brasil LSB Certification | LPI Certification | RHCE Certification www.avelino.us | www.centos-br.org | www.xfce.org

6 9

Re: [CentOS-devel] [PHP 5.2.6] Feedback / Centos Testing and CentOS Extras
by William L. Maltby 07 May '09

07 May '09

On Thu, 2009-03-12 at 12:54 +0100, Paulo Martinez wrote: > - Sorry for double posting. The Archive was not including my post. - > - For the sake of them, which only read through the archive. - I *think* there's a small delay (I don't know how much) for things to get moved to the archive. In the past I noticed that stuff I posted was not available right away, but was a few days later when I checked again. <snip> -- Bill

10 21

Updates push / announcements automation
by Karanbir Singh 07 May '09

07 May '09

As a part of the restructuring of the buildsystems and the updates processing process, we are at a time where there is the option of also redoing the way announcements are done. I've already factored in RSS feeds per repo, but is there anything else that could / should / would make sense in the actual emails that get sent out ? I know changelog has been something that people have mentioned in the past, is that still something that might be good-to-have / must-have in the announcement emails ? Also, for CentOS-4, only security updates are normally announced. What do people feel about changing that so that all updates are announced, including SA / BA / EA and CentOS specific bugfix's ? Finally, and this is the big question that *will* impact a lot of people and specially those with automation - what do people think about combined update announcements for all Arch's in a single email like what happens upstream ? C2.1/C3/C4 will be hard to get into this process since the arch specific builders dont stay in sync, but for C5, with the ia64/ppc and s390 now pretty much online with the i386 and x86_64 its something that we *could* potentially target. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

5 4

Re: [CentOS-devel] [CentOS-docs] Portal for br.centos.org or pt_br.centos.org
by Thiago Avelino 07 May '09

07 May '09

The CentOS-BR.org is a site where there are several things about CentOS in Brazil, where we have our front end for a while here in Brazil that do not leave the br.centos.org and we have hundreds of the mirror is sponsored by Locaweb, so it is banner ads. 2009/5/6 Cleber Souza <cleber.lists(a)gmail.com>: > On Wed, May 6, 2009 at 10:02 AM, Ralph Angenendt <ra+centos(a)br-online.de> wrote: >> Thiago Avelino wrote: >>> Ralph: Not understand what you mean! >> >> a) Please don't top post. >> >> b) No offense meant, but your last mails all loked like you are the sole >> proprietor of everything "CentOS Brazil". There already is a vivid(?) >> community around the CentOS-br mailing list - that's why I asked if >> there has been communication with that mailing list. >> >> Cheers, >> >> Ralph >> >> _______________________________________________ >> CentOS-devel mailing list >> CentOS-devel(a)centos.org >> http://lists.centos.org/mailman/listinfo/centos-devel >> >> > > > Hi Thiago and all, > > I saw a little increase in email traffic in the pt-br mail list by I > think that this should be discussed also there, and I did not see any > message about it in the list. Think about community and not only one > person. > Some other points took my attention on your participation, sometime > ago I started receiving spam through an email that I only used for the > pt-br list, it thinks me believe that someone is getting users' email > and sending them ads email about a magazine (one with ads at > centos-br.org) > This site is also increasing being populated with more and more > partners ads (nothing against partners) but what is theirs involvement > ($) with the centos-br.org website? I hope this is not getting more a > commercial than a community participation. > > > -- > Cleber Paiva de Souza > _______________________________________________ > CentOS-devel mailing list > CentOS-devel(a)centos.org > http://lists.centos.org/mailman/listinfo/centos-devel > -- Thiago Avelino | www.avelino.us icq: 2522219 - jabber: thiagoavelinoster(a)gmail.com

1 0

LiveCD development
by Dag Wieers 06 May '09

06 May '09

Hi, I am amazed by the usefulness of the CentOS LiveCD and I would like to discuss the scope of the project. Some of the recommendations I made go against the original idea of LiveCD project. But my (outside) stance on the LiveCD is that it should give the best achievable experience possible for people when trying CentOS. To me that includes adding drivers that are available in other repositories (which are missing from upstream, including wireless firmware, etc...) I do agree that as soon as we leave the deliver-what-upstream-has path, we may open a can of worms (do we also want to fix known bugs ? replace upstream software ? legality ?), so we have to decide what is desirable, what is possible and where the project's effort ends. What are the various goals of the LiveCD project ? - A way for people to see what hardware is supported by CentOS - with drivers included by upstream only - with drivers that can be added with little effort (to eg. accomodate eeepc and other purposes) - including a tool to send a hardware status report to a central database - A tool for recovering a broken system - include only a few basic tools for debugging - A tool for installing CentOS on a system - A workable environment for people to use day by day - do we want persistent storage - does it need to be installable from Windows - does it include wireless firmware - Provide the tools for people to make their own spins - all sorts of appliances, eg. DVR, rescue, ... I am sure we can list more applicable use-cases for this project. And in the end we have to agree which fit the LiveCD project (eg. whether we make an official CentOS LiveCD and a seperate CentOS-plus LiveCD) and what the main priorities are. Also, to stimulate the LiveCD development there should be no reason why we couldn't release a LiveCD 5.3.1 or LiveCD 5.3.2 if there are compelling reasons to make a new respin (and update the mirrors). In the end I see a bright future for the LiveCD as the project where driver-development (dasha, elrepo), CentOS-based appliances, hardware testing, and much more come together. To me it is one of those unique opportunities to drive different other projects with a very positive attitude as it brings (even more) meaning to CentOS to a lot of (new) people. Where do we want to go with this and what is realistically achievable ? I am thrilled to find out :) -- -- dag wieers, dag(a)wieers.com, http://dag.wieers.com/ -- [Any errors in spelling, tact or fact are transmission errors]

10 30

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel