From greg at runlevelzero.net Mon Dec 1 13:22:28 2003 From: greg at runlevelzero.net (Greg Kurtzer) Date: Mon, 1 Dec 2003 13:22:28 -0800 Subject: [cAos] New cAos screenshots! Message-ID: <20031201212228.GA1381@runlevelzero.net> http://www.runlevelzero.net/greg/images/cAos-screenshot-1.png http://www.runlevelzero.net/greg/images/cAos-screenshot-2.png I am pulling a bit more together, but expect the alpha release (notice I changed BETA to ALPHA) later today... (unless there is a major unforeseen problem). Greg -- Greg M. Kurtzer http://runlevelzero.net/ http://caosity.org/ http://warewulf-cluster.org/ From greg at runlevelzero.net Tue Dec 2 09:13:08 2003 From: greg at runlevelzero.net (Greg Kurtzer) Date: Tue, 2 Dec 2003 09:13:08 -0800 Subject: [cAos] cAos Alpha Release... Message-ID: <20031202171308.GA17564@runlevelzero.net> I was hoping to have this done yesterday, but we ran into an installation problem with rpm creating the rpmdb with root owning it (rpm:rpm should own it). After looking into the problem it looks like it is because %post in rpm adds the user rpm to the passwd file with a redirect to /dev/null. But because /dev/null is not spec'ed as a pre-requirement for the package, rpm is being installed before dev which means that the adduser command fails. I then added /dev/null as a buildreq for rpm, but then rpm would not compile due to auto debug_file generation. I spent the rest of the evening trying to figure out how to disable this (the %enable_debug_package %{nil} didn't seem to be working). In any case, I think that this is the last problem holding us back before the alpha release. I will send a status report soon... Greg -- Greg M. Kurtzer http://runlevelzero.net/ http://caosity.org/ http://warewulf-cluster.org/ From greg at runlevelzero.net Tue Dec 2 13:07:01 2003 From: greg at runlevelzero.net (Greg Kurtzer) Date: Tue, 2 Dec 2003 13:07:01 -0800 Subject: [cAos] cAos Alpha Release... In-Reply-To: <20031202171308.GA17564@runlevelzero.net> References: <20031202171308.GA17564@runlevelzero.net> Message-ID: <20031202210701.GB20757@runlevelzero.net> cAos alpha-1 is now released. http://caosity.org/index.php?option=displaypage&Itemid=57&op=page&SubMenu= Be gental. BTW, we will _really_ need some mirrors. Will everyone interested please let us know! Thanks! Greg On Tue, Dec 02, 2003 at 09:13:08AM -0800, Greg Kurtzer told me: > I was hoping to have this done yesterday, but we ran into an installation > problem with rpm creating the rpmdb with root owning it (rpm:rpm should own > it). After looking into the problem it looks like it is because %post in rpm > adds the user rpm to the passwd file with a redirect to /dev/null. But because > /dev/null is not spec'ed as a pre-requirement for the package, rpm is being > installed before dev which means that the adduser command fails. > > I then added /dev/null as a buildreq for rpm, but then rpm would not compile > due to auto debug_file generation. I spent the rest of the evening trying to > figure out how to disable this (the %enable_debug_package %{nil} didn't seem > to be working). In any case, I think that this is the last problem holding us > back before the alpha release. I will send a status report soon... > > Greg > -- > Greg M. Kurtzer > http://runlevelzero.net/ > http://caosity.org/ > http://warewulf-cluster.org/ > _______________________________________________ > cAos mailing list > cAos at caosity.org > http://www.caosity.org/mailman/listinfo/caos -- Greg M. Kurtzer http://runlevelzero.net/ http://caosity.org/ http://warewulf-cluster.org/ From vossenjp at netaxs.com Tue Dec 2 21:33:45 2003 From: vossenjp at netaxs.com (JP Vossen) Date: Wed, 3 Dec 2003 00:33:45 -0500 (EST) Subject: [cAos] RPM hangs (RH) Message-ID: Just to throw this question out there... I know there is a known issue with Red Hat 8 (and 9?) where rpm frequently (for me at least) hangs. I've never been clear on the reason or a real fix. I have a horrible kludge-around that gets me going again, but it's really bad. I assume that this will not be a problem in cAos? Just wondering, since the other rpm thread reminded me... TIA, JP ------------------------------|:::======|-------------------------------- JP Vossen, CISSP |:::======| jp{at}jpsdomain{dot}org My Account, My Opinions |=========| http://www.jpsdomain.org/ ------------------------------|=========|-------------------------------- You used to have to reboot the Windows 9.x series every couple of days because it would crash. Now you have to reboot Windows 200x or XP every couple of days because of a patch. How is that better or more stable? From herrold at owlriver.com Wed Dec 3 06:50:59 2003 From: herrold at owlriver.com (R P Herrold) Date: Wed, 3 Dec 2003 09:50:59 -0500 (EST) Subject: [cAos] Re: cAos] RPM hangs (RH) In-Reply-To: References: Message-ID: On Wed, 3 Dec 2003, JP Vossen wrote: > Just to throw this question out there... > > I know there is a known issue with Red Hat 8 (and 9?) where rpm frequently > (for me at least) hangs. I've never been clear on the reason or a real fix. > I have a horrible kludge-around that gets me going again, but it's really bad. > > I assume that this will not be a problem in cAos? Just wondering, since the > other rpm thread reminded me... The reasons are discussed in some depth at the http://www.rpm.org/ site, as are approaches on fixes on the rpm-4.1 and rpm-4.2 initial releases which accompanied those Red Hat releases. I do not know that I assume anything until we get out of testing. Good behaviours (not killing a running rpm session, removing stale lock-containing files, rpmfb rebuilds and analysis are app part of good RPM tools to know of. -- Russ Herrold From greg at runlevelzero.net Wed Dec 3 13:01:11 2003 From: greg at runlevelzero.net (Greg Kurtzer) Date: Wed, 3 Dec 2003 13:01:11 -0800 Subject: [cAos] Attention to mirror's Message-ID: <20031203210111.GE8347@runlevelzero.net> Will everyone that is planning on mirroring the cAos packages, please let us know at mirror at caosity.org (and join that mailing list). Mirrors will be shown at: http://caosity.org/index.php?option=displaypage&Itemid=57&op=page&SubMenu= Thanks! Greg -- Greg M. Kurtzer http://runlevelzero.net/ http://caosity.org/ http://warewulf-cluster.org/ From lance at uklinux.net Wed Dec 3 14:06:19 2003 From: lance at uklinux.net (Lance Davis) Date: Wed, 3 Dec 2003 22:06:19 +0000 (GMT) Subject: [cAos] Attention to mirror's In-Reply-To: <20031203210111.GE8347@runlevelzero.net> Message-ID: On Wed, 3 Dec 2003, Greg Kurtzer wrote: > Will everyone that is planning on mirroring the cAos packages, please let us > know at mirror at caosity.org (and join that mailing list). The mailing list is caos-mirror at caosity.org ... Lance -- uklinux.net - The ISP of choice for the discerning Linux user. From distro.watch at msa.hinet.net Sat Dec 6 07:32:32 2003 From: distro.watch at msa.hinet.net (Ladislav Bodnar) Date: Sat, 6 Dec 2003 23:32:32 +0800 Subject: [cAos] cAos Alpha Release... In-Reply-To: <20031202210701.GB20757@runlevelzero.net> References: <20031202171308.GA17564@runlevelzero.net> <20031202210701.GB20757@runlevelzero.net> Message-ID: <200312062332.32479.distro.watch@msa.hinet.net> Hello guys, On Wednesday 03 December 2003 05:07, Greg Kurtzer wrote: > cAos alpha-1 is now released. If you'd like to have cAos listed on DistroWatch, would someone fill in this form, please: http://www.distrowatch.com/dwres.php?resource=submit This would greatly speed up the listing process. Thanks a lot and all the best with your project :-) Ladislav Bodnar http://www.distrowatch.com From lance at uklinux.net Sat Dec 6 09:18:58 2003 From: lance at uklinux.net (Lance Davis) Date: Sat, 6 Dec 2003 17:18:58 +0000 (GMT) Subject: [cAos] cAos Alpha Release... In-Reply-To: <200312062332.32479.distro.watch@msa.hinet.net> Message-ID: On Sat, 6 Dec 2003, Ladislav Bodnar wrote: > Hello guys, > > On Wednesday 03 December 2003 05:07, Greg Kurtzer wrote: > > cAos alpha-1 is now released. > > If you'd like to have cAos listed on DistroWatch, would someone fill in this > form, please: > > http://www.distrowatch.com/dwres.php?resource=submit Done - thanks. But - a lot of packages arent built yet that will be in the beta ... and versions will undoubtedly change. > This would greatly speed up the listing process. > > Thanks a lot and all the best with your project :-) Thanks. Regards Lance -- uklinux.net - The ISP of choice for the discerning Linux user. From distro.watch at msa.hinet.net Sat Dec 6 18:03:21 2003 From: distro.watch at msa.hinet.net (Ladislav Bodnar) Date: Sun, 7 Dec 2003 10:03:21 +0800 Subject: [cAos] cAos Alpha Release... In-Reply-To: References: Message-ID: <200312071003.22472.distro.watch@msa.hinet.net> On Sunday 07 December 2003 01:18, Lance Davis wrote: > Done - thanks. > > But - a lot of packages arent built yet that will be in ?the beta ... > and versions will undoubtedly change. The form only served to create the initial page. From now on, I will keep an eye on your project and update the package versions with every new release. Here is the cAos page: http://www.distrowatch.com/table.php?distribution=caos Please let me know if you find any errors or inaccuracies. Thank you :-) Ladislav From vossenjp at netaxs.com Mon Dec 8 11:00:41 2003 From: vossenjp at netaxs.com (JP Vossen) Date: Mon, 8 Dec 2003 14:00:41 -0500 (EST) Subject: [cAos] GREAT cAos mention! Message-ID: Jeremy of LinuxQuestions.org interviewing Jeremy Hogan of Red Hat. Jeremy of LinuxQuestions.org specifically mentioned cAos2 EL. http://www.linuxquestions.org/questions/showthread.php?threadid=122959 Followup Interview with Jeremy Hogan of Red Hat ( post #1) With all of the recent Fedora and RHEL news, I thought another interview with Jeremy Hogan was in order. He was kind enough to agree to get badgered again. Thanks Jeremy. [...] 12-06-2003 03:55 A small addition to the interview for two frequently asked questions: linuxquestions.org) What does RH think of the repackaged RHEL distros (whiteboxlinux and cAos2 EL come to mind). Jeremy Hogan of Red Hat) It's a perfect example of the power of the GPL. They can do whatever they want. We sell RHEL with a stack of support and services, so it's not competition in the usual sense. [...] Later, JP ------------------------------|:::======|-------------------------------- JP Vossen, CISSP |:::======| jp{at}jpsdomain{dot}org My Account, My Opinions |=========| http://www.jpsdomain.org/ ------------------------------|=========|-------------------------------- You used to have to reboot the Windows 9.x series every couple of days because it would crash. Now you have to reboot Windows 200x or XP every couple of days because of a patch. How is that better or more stable? From greg at runlevelzero.net Mon Dec 8 11:55:10 2003 From: greg at runlevelzero.net (Greg Kurtzer) Date: Mon, 8 Dec 2003 11:55:10 -0800 Subject: [cAos] Cinch-1.1 released... Message-ID: <20031208195510.GC577@runlevelzero.net> I posted the cinch-1.1 installer earlier this morning. It now supports CDROM installs, ext3, and I fixed the current bugs in bugzilla. The next version should handle XFS, and automatic partitioning (if everything goes right). Please use https://bugzilla.caosity.org if you find any problems with it. -- Greg M. Kurtzer http://runlevelzero.net/ http://caosity.org/ http://warewulf-cluster.org/ From vossenjp at netaxs.com Mon Dec 8 14:16:47 2003 From: vossenjp at netaxs.com (JP Vossen) Date: Mon, 8 Dec 2003 17:16:47 -0500 (EST) Subject: [cAos] cAos Security--food for thought Message-ID: ************************** I am cross-posting this to raise interest and awareness. PLEASE reply only to cAos-SA-Devel which is where I think this really belongs, unless Greg has other thoughts. ************************** I just wanted to get *something* out for discussion, since I have not been heard from in a while. More serious work on cAos security is moving up my TODO list, but in the meantime here is some food for thought and discussion. As I've mentioned previously, my first order of business will be to write a security architecture document. This will frame at a very high level our goals and intent. In particular, I am not aware of a general purpose Linux distribution that is suitable out of the box for use as a "security appliance"--to install a firewall or Snort on, for example. A Red Hat minimal distro is (was) hopelessly bloated and other products are too specific (e.g. Mandrake's MNF). Some of the ideas in my head are the following. I encourage additions, changes and general thought and discussion. I really want to make cAos the no-brainer choice of the knowledgeable InfoSec practitioner looking for a Linux distribution to use for any task, security related or not. I don't believe that goal is incompatible with making cAos the no-brainer choice for ANYONE looking for a new Linux distro either. We should make sure that no flavor of cAos has any of the SANS Top 20 [0] (well, really the top 10 UNIX) vulnerabilities out of the box, and we should make sure that's easy to verify that periodically. The security meta-RPM will fit in here very nicely. We should include Bastille Linux [1] will all flavors, and have it running right out of the box. We should use/follow/review/something any/all of the following general hardening guides in some way: http://www.cisecurity.com/bench_linux.html We should include this tool out of the box http://www.linuxsecurity.com/docs/PDF/Securing-Optimizing-Linux-RH-Edition-1_3.pdf SANS NSA Others Obviously, not everything from each of these guides will be practical or even possible for all flavors and all circumstances. But where we can apply the change once and save each and every new cAos SysAdmin from having to do it-we should. And we should make it easy to do as much hardening and verification as possible, as simply as possible. We should steal ideas from: Check Point (SecurePlatform) Other Linux firewall platforms (MNF, Astaro Security Linux, etc.) The Linux Security Cookbook, ESA and others The above hardening guides Others? To accomplish some of the above, I will to create a new package: simple_security_scripts.rpm. Anyone with ideas or scripts to contribute PLEASE do so! simple_security_scripts will be a collection of, well, simple security scripts that are useful as both practical tools and as a security reference on what and how to do some very simple and basic security tasks. They will be written as simply as possible (no obfuscated code) and well commented to be accessible to newbies, so they can learn and do at the same time. Seasoned Admins may want to build on them. What security scripts do YOU have, or wish you had? It will install into /root/sss or something somewhat out of the way like that. Have to think about FHS. check_users = Look for users with no passwords, bad passwords, UID 0 users, set UID/GID programs, never logged in, last logins, failed logins, and maybe track changes to users and groups. check_logs = Verify that various log files exist (& touch if necessary) and are sane, other? check_apps = Simple netstat and ps output to see and trace what's running on a machine. Optionally flag various things like Telnet, sendmail, TFTP with warnings. Maybe have a 'grep -v' feature to suppress stuff you know about or don't care about to allow more exception-based output. Maybe a simple state table that shows if a new daemon that was not there yesterday is there today. sheck_sys_settings = Check various settings in /proc and sysctl, maybe check default umask, core settings, and lots of other stuff TBD. Maybe some simple IPTables scripts? Probably duplicated elsewhere, maybe there is a simple package we can just document and include. Something SIMPLE though. If people want Shorewall they can go get it. (Ideally out of cAos security yum, see below.) Some kind of logcheck program [2]. Tripwire, AIDE, or something similar, preferably that's actually possible to use without a 3 day course (guess tripwire's out). SSS may be tied in to the security Meta RPM as discussed by Greg a while back and referenced above in some way. Or even part of it? This RPM exists only to conflict with know insecure or vulnerable packages to provide a sanity check when people install them without thinking. Other stuff: Create a "Security Tools" yum task that includes packages like the applicable ones from insecure.org top 75 security tools like nmap, Nessus, Ethereal, Snort, Netcat, ntop, ngrep, dsniff, etc. [3] Some of these tools may be controversial, and should probably not be installed by default (CERTAINLY not on the core/minimal/security install). But they should be trivially easy to get, install and keep updated. Likewise other good "security" stuff. At some point I want to think about incorporating the faster ringbuffer libpcap (http://public.lanl.gov/cpw/?) AKA libpcap8 for speeding up Snort. I also have some random thoughts about default chroots for "things" TBD. OK, that's it for now. Thoughts, comments, grave philosophical objections? [0] http://www.sans.org/top20/ [1] http://www.bastille-linux.org/ [2] http://sourceforge.net/projects/sentrytools/ [3] http://www.insecure.org/tools.html Later, JP ------------------------------|:::======|-------------------------------- JP Vossen, CISSP |:::======| jp{at}jpsdomain{dot}org My Account, My Opinions |=========| http://www.jpsdomain.org/ ------------------------------|=========|-------------------------------- You used to have to reboot the Windows 9.x series every couple of days because it would crash. Now you have to reboot Windows 200x or XP every couple of days because of a patch. How is that better or more stable? From ras1 at jamrockmusic.com Mon Dec 8 19:45:44 2003 From: ras1 at jamrockmusic.com (Jesse) Date: Mon, 08 Dec 2003 19:45:44 -0800 Subject: [cAos] cAos Security--food for thought In-Reply-To: References: Message-ID: <1070941544.20784.15.camel@bill.jamrockmusic.com> This all sounds good. I like your ideas. What about an option to use a kernel patch such as grsec as well. While grsec is not going into the mainstream kernel anytime soon, it is still a really nice patch (much better than exec-sheild). Not saying that it should be default, only available if wanted. Keep up the great work folks!!! --jesse From rmcgaugh at atipa.com Tue Dec 9 07:30:23 2003 From: rmcgaugh at atipa.com (Rocky McGaugh) Date: Tue, 9 Dec 2003 09:30:23 -0600 (CST) Subject: [cAos] Announce: centos Message-ID: The cAos-EL projects have been officially renamed to: centos (Community ENTerprise Operating System) This only affects caosel1 and caosel2. This is partly an aid in dispelling the version confusion. ======== centos-1 Description: centos-1 is a freely distributable OS built from the source at: ftp://ftp.redhat.com/pub/redhat/linux/enterprise/2.1AS/en/os/ Altering non-Free packages, such as those encumbered by a non-redistributable Copyright or trademark. centos-1 is designed for people that need an Enterprise class OS without the cost of certification and support. This project is also the base from which cAos Core and cAos GP are based. There will initially be support for x86. Updates will be distributed via yum repositories. Status: Most sources have been built. This project needs an interested party to take ownership. ======== centos-2 Description: centos-2 is a freely distributable OS built from the source at: ftp://ftp.redhat.com/pub/redhat/linux/enterprise/3/en/os/i386/SRPMS Altering non-Free packages, such as those encumbered by a non-redistributable Copyright or trademark. centos-2 is designed for people that need an Enterprise class OS without the cost of certification and support. There will initially be support for x86, AMD64, and ia64. Updates will be distributed via yum repositories. Status: x86 initial build is 99.9% done. A new build will be done in the next couple days using the new name, incorporating the new "branding", and fixing a couple small issues. It is realistic to expect a testing release by Monday, Dec 15. -- Rocky McGaugh From laytonjb at comcast.net Tue Dec 9 16:10:38 2003 From: laytonjb at comcast.net (Jeffrey B. Layton) Date: Tue, 09 Dec 2003 19:10:38 -0500 Subject: [cAos] Anaconda for cAos? Message-ID: <3FD6647E.6060500@comcast.net> Good evening, I've been following cAos with an eye toward replacing RH on my desktop and for use on my clusters with Warewulf. :) I also have another use for cAos that I can't really fully explain right now, but I will try to talk around it. I'm interested in having a nice GUI for installing cAos for users that probably aren't that experienced. Anaconda isn't too bad (I've seen and used worse, especially when anaconda first came out) and some of the users I'm concerned about may have already used it for installing RH. So, has anybody thought/tried/succeeded in porting Anaconda to cAos? Has anybody thought about borrowing the 'port' from the WhiteBox gang? Thanks! Jeff P.S. I'm going to try Cinch, but haven't done so yet. Greg assures me that it's quite nifty. From chrish at trilug.org Wed Dec 10 02:48:04 2003 From: chrish at trilug.org (Magnus Hedemark) Date: Wed, 10 Dec 2003 05:48:04 -0500 Subject: [cAos] Anaconda for cAos? In-Reply-To: <3FD6647E.6060500@comcast.net> References: <3FD6647E.6060500@comcast.net> Message-ID: <3FD6F9E4.3000306@trilug.org> Jeffrey B. Layton wrote: > So, has anybody thought/tried/succeeded in > porting Anaconda to cAos? Has anybody thought > about borrowing the 'port' from the WhiteBox > gang? LOL. Anaconda was already there and it was pulled out. :) From laytonjb at comcast.net Wed Dec 10 15:22:50 2003 From: laytonjb at comcast.net (Jeffrey B. Layton) Date: Wed, 10 Dec 2003 18:22:50 -0500 Subject: [cAos] Anaconda for cAos? In-Reply-To: <3FD6F9E4.3000306@trilug.org> References: <3FD6647E.6060500@comcast.net> <3FD6F9E4.3000306@trilug.org> Message-ID: <3FD7AACA.5090704@comcast.net> Magnus, I was waiting for that. :) I was hoping that someone had maybe ported it on a whim (or else they've lost their mind or something - maybe I have). I know about Cinch, but does anyone have any recommendations for a GUI installed for cAos? Thanks! Jeff > Jeffrey B. Layton wrote: > >> So, has anybody thought/tried/succeeded in >> porting Anaconda to cAos? Has anybody thought >> about borrowing the 'port' from the WhiteBox >> gang? > > > LOL. Anaconda was already there and it was pulled out. :) > > _______________________________________________ > cAos mailing list > cAos at caosity.org > http://www.caosity.org/mailman/listinfo/caos > From greg at runlevelzero.net Tue Dec 16 01:39:18 2003 From: greg at runlevelzero.net (Greg Kurtzer) Date: Tue, 16 Dec 2003 01:39:18 -0800 Subject: [cAos] Caution... Message-ID: <20031216093918.GA16920@runlevelzero.net> I just updated several packages to support XFS natively in cAos, but I have not released the new cinch which will account for the new packages. most specifically, 'libattr' will need to be installed at the system installation time (and before the kernel install) other wise you will not end up with a usable system. Tomorrow cinch should be able to handle a native XFS installation of cAos. BTW, this error will also be relevant to people doing system updates. You will need to yum install libattr if it is not there already. Once we go into production, large changes like this will be handled via Requires tags in the RPMs themselves and automatically caught by yum. Have fun. -- Greg M. Kurtzer http://runlevelzero.net/ http://caosity.org/ http://warewulf-cluster.org/ From mickw at mbwcomputing.net Tue Dec 16 03:48:09 2003 From: mickw at mbwcomputing.net (Michael Watson) Date: Tue, 16 Dec 2003 22:48:09 +1100 Subject: [cAos] Installation Message-ID: <001c01c3c3ca$7c7e2dc0$2064a8c0@mwlaptop> Had problems installing using Internet Installation from Floppy. Yum continually crashed. System log showed process was terminated due to lack of memory. Restarting installation by exiting the Shell opened after each crash, enabled the system to install (eventually). I tried installation twice, first with 64Mb RAM, then with 128Mb RAM, with the same results. BTW. System running smoooth one installed. Very nice. Michael Watson MBW Computing -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.infiscale.org/pipermail/caos/attachments/20031216/d2808531/attachment.html From landman at scalableinformatics.com Tue Dec 16 06:32:39 2003 From: landman at scalableinformatics.com (Joe Landman) Date: Tue, 16 Dec 2003 09:32:39 -0500 Subject: [cAos] quick questions In-Reply-To: <20031216093918.GA16920@runlevelzero.net> References: <20031216093918.GA16920@runlevelzero.net> Message-ID: <3FDF1787.6010206@scalableinformatics.com> I want to mirror one of the (download) sites nightly for my own internal work. Are there specific procedures in place for this? Do you need some developed? Also, I did sign up on the page, but never did receive a password. Any hints? Joe From greg at runlevelzero.net Tue Dec 16 07:53:44 2003 From: greg at runlevelzero.net (Greg Kurtzer) Date: Tue, 16 Dec 2003 07:53:44 -0800 Subject: [cAos] quick questions In-Reply-To: <3FDF1787.6010206@scalableinformatics.com> References: <20031216093918.GA16920@runlevelzero.net> <3FDF1787.6010206@scalableinformatics.com> Message-ID: <20031216155344.GA11136@runlevelzero.net> On Tue, Dec 16, 2003 at 09:32:39AM -0500, Joe Landman told me: > I want to mirror one of the (download) sites nightly for my own internal > work. Are there specific procedures in place for this? Do you need > some developed? Have you seen: http://caosity.org/index.php?option=displaypage&Itemid=85&op=page&SubMenu= > Also, I did sign up on the page, but never did receive a password. Any > hints? Hrmm... I have seen this before. Click on lost password, and see if that helps. We are in the process of upgrading the site engine and moving the system. Greg -- Greg M. Kurtzer http://runlevelzero.net/ http://caosity.org/ http://warewulf-cluster.org/ From greg at runlevelzero.net Tue Dec 16 07:58:27 2003 From: greg at runlevelzero.net (Greg Kurtzer) Date: Tue, 16 Dec 2003 07:58:27 -0800 Subject: [cAos] Installation In-Reply-To: <001c01c3c3ca$7c7e2dc0$2064a8c0@mwlaptop> References: <001c01c3c3ca$7c7e2dc0$2064a8c0@mwlaptop> Message-ID: <20031216155827.GB11136@runlevelzero.net> On Tue, Dec 16, 2003 at 10:48:09PM +1100, Michael Watson told me: > > Had problems installing using Internet Installation from Floppy. Yum continually crashed. System log showed process was terminated due to lack of memory. Yes. right now this is the major limitation of cinch (it requires a lot of memory). We are working on some changes that _should_ allow one to install with 64Mb of RAM, but this will go into swap so it will be slow. 128Mb of ram should be fine. Expect cinch to be released later today, and I would love it if you can test! ;) > Restarting installation by exiting the Shell opened after each crash, enabled the system to install (eventually). I tried installation twice, first with 64Mb RAM, then with 128Mb RAM, with the same results. > > BTW. System running smoooth one installed. Very nice. Glad to hear it, and thanks! Greg -- Greg M. Kurtzer http://runlevelzero.net/ http://caosity.org/ http://warewulf-cluster.org/ From mailing-lists at hughesjr.com Wed Dec 17 08:02:44 2003 From: mailing-lists at hughesjr.com (Johnny Hughes) Date: Wed, 17 Dec 2003 10:02:44 -0600 Subject: [cAos] Installation In-Reply-To: <001c01c3c3ca$7c7e2dc0$2064a8c0@mwlaptop> References: <001c01c3c3ca$7c7e2dc0$2064a8c0@mwlaptop> Message-ID: <1071676964.1762.14.camel@myth.home.local> I tried an install (from floppy) on a PIII 800 with 768mb RAM and 1gb swap and 15gb drive with 100M boot 1gb swap and the rest / ... Made it OK through the DHCP, things started downloading, but there was an error and the file libattr.so.1 is not there....I'm not sure exactly why yet, but after I get back from seeing The Return of the King today I am going to trouble shoot some more. Has anyone else seen this error ... I searched for libattr.so.1 in bugzilla ... nothing there. -Johnny Hughes On Tue, 2003-12-16 at 05:48, Michael Watson wrote: > > Had problems installing using Internet Installation from Floppy. Yum > continually crashed. System log showed process was terminated due to > lack of memory. > > Restarting installation by exiting the Shell opened after each crash, > enabled the system to install (eventually). I tried installation > twice, first with 64Mb RAM, then with 128Mb RAM, with the same > results. > > BTW. System running smoooth one installed. Very nice. > > > Michael Watson > MBW Computing > From herrold at owlriver.com Wed Dec 17 08:54:07 2003 From: herrold at owlriver.com (R P Herrold) Date: Wed, 17 Dec 2003 11:54:07 -0500 (EST) Subject: [cAos] Re: cAos] Installation In-Reply-To: <1071676964.1762.14.camel@myth.home.local> References: <001c01c3c3ca$7c7e2dc0$2064a8c0@mwlaptop> <1071676964.1762.14.camel@myth.home.local> Message-ID: On Wed, 17 Dec 2003, Johnny Hughes wrote: > I tried an install (from floppy) on a PIII 800 with 768mb RAM and 1gb > swap and 15gb drive with 100M boot 1gb swap and the rest / ... Please file against the 'cinch' component of caos1-GP -- Mention the version (it is on the first screen) I have added a libattr component, but it sounds like this may be another issue. -- Russ Herrold From greg at runlevelzero.net Wed Dec 17 09:20:26 2003 From: greg at runlevelzero.net (Greg Kurtzer) Date: Wed, 17 Dec 2003 09:20:26 -0800 Subject: [cAos] Installation In-Reply-To: <1071676964.1762.14.camel@myth.home.local> References: <001c01c3c3ca$7c7e2dc0$2064a8c0@mwlaptop> <1071676964.1762.14.camel@myth.home.local> Message-ID: <20031217172026.GA27134@runlevelzero.net> Check out my post from Tuesday: http://caosity.org/pipermail/caos/2003-December/001209.html I have the new cinch that I will release today. the problem was that I had to migrate in XFS support, and this required a new package to be installed that the installer was not grabbing. Needless to say, it does now, or uhmm, will rather later today... ;) Greg On Wed, Dec 17, 2003 at 10:02:44AM -0600, Johnny Hughes told me: > I tried an install (from floppy) on a PIII 800 with 768mb RAM and 1gb > swap and 15gb drive with 100M boot 1gb swap and the rest / ... > > Made it OK through the DHCP, things started downloading, but there was > an error and the file libattr.so.1 is not there....I'm not sure exactly > why yet, but after I get back from seeing The Return of the King today I > am going to trouble shoot some more. > > Has anyone else seen this error ... I searched for libattr.so.1 in > bugzilla ... nothing there. > > -Johnny Hughes > On Tue, 2003-12-16 at 05:48, Michael Watson wrote: > > > > Had problems installing using Internet Installation from Floppy. Yum > > continually crashed. System log showed process was terminated due to > > lack of memory. > > > > Restarting installation by exiting the Shell opened after each crash, > > enabled the system to install (eventually). I tried installation > > twice, first with 64Mb RAM, then with 128Mb RAM, with the same > > results. > > > > BTW. System running smoooth one installed. Very nice. > > > > > > Michael Watson > > MBW Computing > > > > _______________________________________________ > cAos mailing list > cAos at caosity.org > http://www.caosity.org/mailman/listinfo/caos -- Greg M. Kurtzer http://runlevelzero.net/ http://caosity.org/ http://warewulf-cluster.org/ From greg at runlevelzero.net Wed Dec 17 23:21:07 2003 From: greg at runlevelzero.net (Greg Kurtzer) Date: Wed, 17 Dec 2003 23:21:07 -0800 Subject: [cAos] Caution... In-Reply-To: <20031216093918.GA16920@runlevelzero.net> References: <20031216093918.GA16920@runlevelzero.net> Message-ID: <20031218072107.GA32691@runlevelzero.net> So, I released cinch-1.2, but shortly thus after I found some bugs related to (I think) the way we built busybox. We used uClibc because it allowed us to make busybox very small and fixed the DNS problems. Unfortunately this brought to the table new and exciting problems! :) If you use the new cinch, please be aware that you will inert messages regarding "*: applet not found". Unfortunately there is another bug that is a bit more of a pain. It turns out that installing the grub bootloader sometimes hangs when dealing with xfs on the /boot file system. An easy fix is to jump to the second VT (ALT-F2), and kill the grub -shell program. It seems as though grub already did what it had to do, and is just not letting go. After you do that, the system should work fine. I will send an update when these problems are solved. Greg On Tue, Dec 16, 2003 at 01:39:18AM -0800, Greg Kurtzer told me: > I just updated several packages to support XFS natively in cAos, but I have > not released the new cinch which will account for the new packages. most > specifically, 'libattr' will need to be installed at the system installation > time (and before the kernel install) other wise you will not end up with a > usable system. > > Tomorrow cinch should be able to handle a native XFS installation of cAos. > > BTW, this error will also be relevant to people doing system updates. You will > need to yum install libattr if it is not there already. Once we go into > production, large changes like this will be handled via Requires tags in the > RPMs themselves and automatically caught by yum. > > Have fun. > -- > Greg M. Kurtzer > http://runlevelzero.net/ > http://caosity.org/ > http://warewulf-cluster.org/ > _______________________________________________ > cAos mailing list > cAos at caosity.org > http://www.caosity.org/mailman/listinfo/caos -- Greg M. Kurtzer http://runlevelzero.net/ http://caosity.org/ http://warewulf-cluster.org/ From landman at scalableinformatics.com Thu Dec 18 03:59:59 2003 From: landman at scalableinformatics.com (Joe Landman) Date: Thu, 18 Dec 2003 06:59:59 -0500 Subject: [cAos] Caution... In-Reply-To: <20031218072107.GA32691@runlevelzero.net> References: <20031216093918.GA16920@runlevelzero.net> <20031218072107.GA32691@runlevelzero.net> Message-ID: <3FE196BF.6080906@scalableinformatics.com> Hi Greg: On XFS systems, I usually set /boot to be ext3. This grub issue is pervasive across distributions (e.g. its a "grub" thing). Joe Greg Kurtzer wrote: >So, I released cinch-1.2, but shortly thus after I found some bugs related to >(I think) the way we built busybox. We used uClibc because it allowed us to >make busybox very small and fixed the DNS problems. Unfortunately this brought >to the table new and exciting problems! :) > >If you use the new cinch, please be aware that you will inert messages >regarding "*: applet not found". Unfortunately there is another bug that is >a bit more of a pain. It turns out that installing the grub bootloader >sometimes hangs when dealing with xfs on the /boot file system. An easy fix is >to jump to the second VT (ALT-F2), and kill the grub -shell program. It seems >as though grub already did what it had to do, and is just not letting go. >After you do that, the system should work fine. > >I will send an update when these problems are solved. > >Greg > >On Tue, Dec 16, 2003 at 01:39:18AM -0800, Greg Kurtzer told me: > > >>I just updated several packages to support XFS natively in cAos, but I have >>not released the new cinch which will account for the new packages. most >>specifically, 'libattr' will need to be installed at the system installation >>time (and before the kernel install) other wise you will not end up with a >>usable system. >> >>Tomorrow cinch should be able to handle a native XFS installation of cAos. >> >>BTW, this error will also be relevant to people doing system updates. You will >>need to yum install libattr if it is not there already. Once we go into >>production, large changes like this will be handled via Requires tags in the >>RPMs themselves and automatically caught by yum. >> >>Have fun. >>-- >>Greg M. Kurtzer >>http://runlevelzero.net/ >>http://caosity.org/ >>http://warewulf-cluster.org/ >>_______________________________________________ >>cAos mailing list >>cAos at caosity.org >>http://www.caosity.org/mailman/listinfo/caos >> >> > > > -- Joseph Landman, Ph.D Scalable Informatics LLC, email: landman at scalableinformatics.com web : http://scalableinformatics.com phone: +1 734 612 4615 From greg at runlevelzero.net Thu Dec 18 10:14:06 2003 From: greg at runlevelzero.net (Greg Kurtzer) Date: Thu, 18 Dec 2003 10:14:06 -0800 Subject: [cAos] Caution... In-Reply-To: <20031218072107.GA32691@runlevelzero.net> References: <20031216093918.GA16920@runlevelzero.net> <20031218072107.GA32691@runlevelzero.net> Message-ID: <20031218181406.GA4542@runlevelzero.net> I fixed the grub issue (at least it passed on my test systems). New cinch-1.2a has been uploaded. BTW, it still has the ':applet not found' errors, but same as before, they are benign. Greg On Wed, Dec 17, 2003 at 11:21:07PM -0800, Greg Kurtzer told me: > So, I released cinch-1.2, but shortly thus after I found some bugs related to > (I think) the way we built busybox. We used uClibc because it allowed us to > make busybox very small and fixed the DNS problems. Unfortunately this brought > to the table new and exciting problems! :) > > If you use the new cinch, please be aware that you will inert messages > regarding "*: applet not found". Unfortunately there is another bug that is > a bit more of a pain. It turns out that installing the grub bootloader > sometimes hangs when dealing with xfs on the /boot file system. An easy fix is > to jump to the second VT (ALT-F2), and kill the grub -shell program. It seems > as though grub already did what it had to do, and is just not letting go. > After you do that, the system should work fine. > > I will send an update when these problems are solved. > > Greg > > On Tue, Dec 16, 2003 at 01:39:18AM -0800, Greg Kurtzer told me: > > I just updated several packages to support XFS natively in cAos, but I have > > not released the new cinch which will account for the new packages. most > > specifically, 'libattr' will need to be installed at the system installation > > time (and before the kernel install) other wise you will not end up with a > > usable system. > > > > Tomorrow cinch should be able to handle a native XFS installation of cAos. > > > > BTW, this error will also be relevant to people doing system updates. You will > > need to yum install libattr if it is not there already. Once we go into > > production, large changes like this will be handled via Requires tags in the > > RPMs themselves and automatically caught by yum. > > > > Have fun. > > -- > > Greg M. Kurtzer > > http://runlevelzero.net/ > > http://caosity.org/ > > http://warewulf-cluster.org/ > > _______________________________________________ > > cAos mailing list > > cAos at caosity.org > > http://www.caosity.org/mailman/listinfo/caos > > -- > Greg M. Kurtzer > http://runlevelzero.net/ > http://caosity.org/ > http://warewulf-cluster.org/ > _______________________________________________ > cAos mailing list > cAos at caosity.org > http://www.caosity.org/mailman/listinfo/caos -- Greg M. Kurtzer http://runlevelzero.net/ http://caosity.org/ http://warewulf-cluster.org/ From greg at runlevelzero.net Thu Dec 18 10:28:28 2003 From: greg at runlevelzero.net (Greg Kurtzer) Date: Thu, 18 Dec 2003 10:28:28 -0800 Subject: [cAos] Caution... In-Reply-To: <3FE196BF.6080906@scalableinformatics.com> References: <20031216093918.GA16920@runlevelzero.net> <20031218072107.GA32691@runlevelzero.net> <3FE196BF.6080906@scalableinformatics.com> Message-ID: <20031218182828.GB4542@runlevelzero.net> On Thu, Dec 18, 2003 at 06:59:59AM -0500, Joe Landman told me: > Hi Greg: > > On XFS systems, I usually set /boot to be ext3. This grub issue is > pervasive across distributions (e.g. its a "grub" thing). Well, it is good to hear that others also had problems with this! :) Actually, on my last test, it looks like it is still failing. Back to the drawing board, but with that said, the installer would work fine with an ext2|3 /boot file system. Greg -- Greg M. Kurtzer http://runlevelzero.net/ http://caosity.org/ http://warewulf-cluster.org/ From rmcgaugh at atipa.com Fri Dec 19 07:55:51 2003 From: rmcgaugh at atipa.com (Rocky McGaugh) Date: Fri, 19 Dec 2003 09:55:51 -0600 (CST) Subject: [cAos] Announce: CentOS-3 test release "build4" Message-ID: http://mirror.centos.org/centos-3/build4/i386 http://mirror.centos.org/centos-3/build4/isos Yum repositories at: http://mirror.centos.org/centos-3/build4/i386/RedHat/RPMS/ http://mirror.centos.org/centos-3/build4/i386/addons/RPMS/ This is a test release, so the dir structure is not set in stone for future releases. Of particular interest are: i386/addons - RPMs and SRPMs of items needed to complete a rebuild, and also RPMs that were generated by the build but not shipped as part of the distro. i386/branding - SRPMS for re-branded RPMs. The RPMs have already been integrated in. As far as I know, there are no show-stopping bugs. I know of some gnome linking problems that need to be fixed before the official "RC1" release, but they should not really be much of a problem. Please log any bugs, including artwork problems, to https://bugzilla.caosity.org This will be my last cross-posted announcement for this project. If interested in announcements, please subscribe to the cAos Announce list at http://caosity.org/mailman/listinfo/caos-announce. It is a low-volume list. Thanks, -- Rocky McGaugh Atipa Technologies rocky at atipatechnologies.com rmcgaugh at atipa.com 1-785-841-9513 x3110 http://67.8450073/ perl -e 'print unpack(u, ".=W=W+F%T:7\!A+F-O;0H`");' From greg at runlevelzero.net Sat Dec 20 00:03:30 2003 From: greg at runlevelzero.net (Greg Kurtzer) Date: Sat, 20 Dec 2003 00:03:30 -0800 Subject: [cAos] cinch-1.2e released... Message-ID: <20031220080330.GA3030@runlevelzero.net> OK, I think that I have nailed down all of the bugs or adverted them gracefully. ;) For all of those interested, please download the current version of cinch and do some test installs! Floppy: http://mirror.caosity.org/cAos-1/cinch/floppy.img CDROM: http://mirror.caosity.org/cAos-1/cinch/cinch.iso BUGZ: https://bugzilla.caosity.org/ (and there will be bugs!) At this time, we are focusing on getting the installer stable so cAos can move into BETA. Thanks! -- Greg M. Kurtzer http://runlevelzero.net/ http://caosity.org/ http://warewulf-cluster.org/ From greg at runlevelzero.net Sat Dec 20 00:23:12 2003 From: greg at runlevelzero.net (Greg Kurtzer) Date: Sat, 20 Dec 2003 00:23:12 -0800 Subject: [cAos] timeline/landmarks for final release... Message-ID: <20031220082312.GB3030@runlevelzero.net> Here is a list of the things needed for cAos 1.0 to be released: - Get installer stable - Finish developing the temple so package maintainers can start working :) - Finalize the implementation and temple integration of build system - Rebuild entire OS to make sure we are still self hosting * Release beta1 - Finish package QA system - QA all core packages - Rebuild entire OS to make sure we are still self hosting * Release stable The temple is mostly done, and should be opened to package maintainers in the next several days. Most of the other needed projects have already been prototyped and just needs to be built for production. Also, we still _NEED_ a web site content maintainer... This is a person that will take charge of writing and editing content on the cAos site. They will have to stay involved with the current development (so they can write articles and post news) but would not have to be a developer (unless they desired). This is a very important position, but should not take much time. The requirements are that the person must have good writing skills and be motivated to keep the site current. Only a minimal amount of HTML knowledge is required (a very small set of basic tags). Anyone interested should contact me off list ASAP. Thanks! Greg -- Greg M. Kurtzer http://runlevelzero.net/ http://caosity.org/ http://warewulf-cluster.org/ From jawildman at rossberry.com Tue Dec 23 08:31:54 2003 From: jawildman at rossberry.com (Jim Wildman) Date: Tue, 23 Dec 2003 11:31:54 -0500 (EST) Subject: [cAos] Centos-3 vs RHAS3 In-Reply-To: References: Message-ID: I'm doing a parrallel install of RHAS3.0 and Centos-3 on identical hardware (IBM x335, dual 3.06G Xeons, 4G of RAM). Hard to tell the two apart. Once they're both up, I'm going to load test them, probably starting with lmbench. (Open to suggestions) Nits to pick Red Hat is mentioned in the following places.. The initial boot screen (syslinux.cfg I assume) The welcome screen at the end of the install encourages you to buy support for Centos at www.redhat.com. On the text install, the top line of the screen says "Centos..copyright Red Hat" etc It fires up the Red Hat Network agent on first boot, and asks you to agree to Red Hat's license. ----------------------------------------------------------------------- Jim Wildman, CISSP, RHCE jim at rossberry.com http://www.rossberry.com From lance at uklinux.net Tue Dec 23 09:16:32 2003 From: lance at uklinux.net (Lance Davis) Date: Tue, 23 Dec 2003 17:16:32 +0000 (GMT) Subject: [cAos] Centos-3 vs RHAS3 In-Reply-To: Message-ID: On Tue, 23 Dec 2003, Jim Wildman wrote: > I'm doing a parrallel install of RHAS3.0 and Centos-3 on identical > hardware (IBM x335, dual 3.06G Xeons, 4G of RAM). Hard to tell the two > apart. Once they're both up, I'm going to load test them, probably > starting with lmbench. (Open to suggestions) > > Nits to pick > Red Hat is mentioned in the following places.. > The initial boot screen (syslinux.cfg I assume) > The welcome screen at the end of the install encourages you to buy > support for Centos at www.redhat.com. > On the text install, the top line of the screen says "Centos..copyright > Red Hat" etc > It fires up the Red Hat Network agent on first boot, and asks you to > agree to Red Hat's license. Thanks - I think all of those are bugzilla'ed and will be fixed for next release, which will probably be RC1. htpps://bugzilla.caosity.org/ Regards Lance -- uklinux.net - The ISP of choice for the discerning Linux user. From drussell at sugardog.com Tue Dec 23 10:44:24 2003 From: drussell at sugardog.com (Don Russell) Date: Tue, 23 Dec 2003 13:44:24 -0500 Subject: [cAos] Centos-3 vs RHAS3 In-Reply-To: Message-ID: <000001c3c984$ca47e040$1c02a8c0@DUCK> Let me know on what you decide on load test wise. Do you know of anything that will "mail bomb" a server. Im currently building a cluster, and want to test it offline for a week or so with a shitload of mail coming in to see how she does. Any suggestions? Thanks, Don -----Original Message----- From: caos-admin at caosity.org [mailto:caos-admin at caosity.org] On Behalf Of Jim Wildman Sent: Tuesday, December 23, 2003 11:32 AM To: caos at caosity.org Subject: [cAos] Centos-3 vs RHAS3 I'm doing a parrallel install of RHAS3.0 and Centos-3 on identical hardware (IBM x335, dual 3.06G Xeons, 4G of RAM). Hard to tell the two apart. Once they're both up, I'm going to load test them, probably starting with lmbench. (Open to suggestions) Nits to pick Red Hat is mentioned in the following places.. The initial boot screen (syslinux.cfg I assume) The welcome screen at the end of the install encourages you to buy support for Centos at www.redhat.com. On the text install, the top line of the screen says "Centos..copyright Red Hat" etc It fires up the Red Hat Network agent on first boot, and asks you to agree to Red Hat's license. ----------------------------------------------------------------------- Jim Wildman, CISSP, RHCE jim at rossberry.com http://www.rossberry.com _______________________________________________ cAos mailing list cAos at caosity.org http://www.caosity.org/mailman/listinfo/caos From lance at uklinux.net Wed Dec 24 18:06:28 2003 From: lance at uklinux.net (Lance Davis) Date: Thu, 25 Dec 2003 02:06:28 +0000 (GMT) Subject: [cAos] Merrx Xmas Message-ID: Well its xmas day here now - so merry xmas to all. Dont eat too much of whatever you have for xmas. Cheers Lance -- uklinux.net - The ISP of choice for the discerning Linux user. From greg at runlevelzero.net Wed Dec 24 20:11:51 2003 From: greg at runlevelzero.net (Greg Kurtzer) Date: Wed, 24 Dec 2003 20:11:51 -0800 Subject: [cAos] temple is active... Message-ID: <20031225041151.GA3291@runlevelzero.net> I have activated the package maintainers accounts at the temple.caosity.org. This is for people interested in being a package maintainer for cAos (not centos at this point). The following list of usernames are the people that currently have access: +-----------+ | username | +-----------+ | datadevil | | dpilon | | gbro | | greg | | herrold | | jp | | jsquyres | | lance | | mej | | ralf | | ras | | troj | | tru | +-----------+ If you would like access or I missed your account, please fill out the form at: https://temple.caosity.org/account_request.php (and I apologize if you have already done this) If you don't remember your password, please go here: https://temple.caosity.org/lost_pass.php Please keep in mind that the temple is still in testing phases, and the auto-builder stuff has not been totally integrated yet. It will however give you access to park your SRPMS, and configure them to be integrated into the distribution. Have fun... Greg -- Greg M. Kurtzer http://runlevelzero.net/ http://caosity.org/ http://warewulf-cluster.org/ From greg at runlevelzero.net Thu Dec 25 22:37:16 2003 From: greg at runlevelzero.net (Greg Kurtzer) Date: Thu, 25 Dec 2003 22:37:16 -0800 Subject: [cAos] Hints for package builds... Message-ID: <20031226063716.GA16806@runlevelzero.net> I was debating the idea for package hints and the best way to implement them. Background: Hints are packages that _should_ be installed to build another (similar to a 'BuildRequires' in a RPM SPEC). Is there any reason why we should not mandate that all hints be specified as BuildRequires inside the SPEC itself (ie. HINT == BUILDREQ)? The only reason that I have come up with is that we may be changing many RPM SPEC's that otherwise would not need changing. -- Greg M. Kurtzer http://runlevelzero.net/ http://caosity.org/ http://warewulf-cluster.org/ From herrold at owlriver.com Fri Dec 26 07:15:10 2003 From: herrold at owlriver.com (R P Herrold) Date: Fri, 26 Dec 2003 10:15:10 -0500 (EST) Subject: [cAos] Re: cAos] Hints for package builds... In-Reply-To: <20031226063716.GA16806@runlevelzero.net> References: <20031226063716.GA16806@runlevelzero.net> Message-ID: On Thu, 25 Dec 2003, Greg Kurtzer wrote: > I was debating the idea for package hints and the best way to implement them. > > Background: Hints are packages that _should_ be installed to build another > (similar to a 'BuildRequires' in a RPM SPEC). > > Is there any reason why we should not mandate that all hints be specified as > BuildRequires inside the SPEC itself (ie. HINT == BUILDREQ)? The only reason > that I have come up with is that we may be changing many RPM SPEC's that > otherwise would not need changing. I addresed this in: https://bugzilla.caosity.org/show_bug.cgi?id=72 The reason for NOT 'mandating' this is that as one adds more and more 'BUILDREQ' content, it becomes more and more difficult to move a .spec file, and then the SRPM beteeen releases. But having a external, and as bug 72 proposes, local versioning HINT, we be exported more easily between our releases, and more generally to other RPM based distributions. Obviously one problem with the 'Balkanization' of distributions is that the ability to gain from the eforts of others is lost as we 'build walls' by mandating conduct. But separating local 'hints' which a given sub-product needs, but others may not, we encourage sharing. Bug 72 proposed a local way to version HINTS to support both cAos and CentOS products. -- Russ Herrold From mej at kainx.org Fri Dec 26 18:12:48 2003 From: mej at kainx.org (Michael Jennings) Date: Fri, 26 Dec 2003 21:12:48 -0500 Subject: [cAos] Hints for package builds... In-Reply-To: <20031226063716.GA16806@runlevelzero.net> References: <20031226063716.GA16806@runlevelzero.net> Message-ID: <20031227021248.GP6802@kainx.org> On Thursday, 25 December 2003, at 22:37:16 (-0800), Greg Kurtzer wrote: > I was debating the idea for package hints and the best way to > implement them. > > Background: Hints are packages that _should_ be installed to build > another (similar to a 'BuildRequires' in a RPM SPEC). > > Is there any reason why we should not mandate that all hints be > specified as BuildRequires inside the SPEC itself (ie. HINT == > BUILDREQ)? The only reason that I have come up with is that we may > be changing many RPM SPEC's that otherwise would not need changing. I agree with RPH. Furthermore, I feel that dependencies should be expressed (whenever possible) in terms of something other than the package name. For example, requiring perl(RPM) instead of rpm-perl. Package names vary wildly between distributions, but perl module names, shared library names, script interpreters, etc. tend not to vary. At least not nearly as much. Michael -- Michael Jennings (a.k.a. KainX) http://www.kainx.org/ n + 1, Inc., http://www.nplus1.net/ Author, Eterm (www.eterm.org) ----------------------------------------------------------------------- "The Road I have travelled on is paved with good intentions. It's littered with broken dreams that never quite came true." -- Restless Heart, "When She Cries" From greg at runlevelzero.net Sun Dec 28 00:25:12 2003 From: greg at runlevelzero.net (Greg Kurtzer) Date: Sun, 28 Dec 2003 00:25:12 -0800 Subject: [cAos] Hints for package builds... In-Reply-To: <20031226063716.GA16806@runlevelzero.net> References: <20031226063716.GA16806@runlevelzero.net> Message-ID: <20031228082512.GA20747@runlevelzero.net> Built by popular demand... All of the caos package maintainers should note that the temple package depo interface, now supports build hint definitions. Please use this field to specify a package name (sorry, file requires are not yet supported). All package maintainers should update their temple entries to include the proper hints. Every hour the current srpm and hint lists are built from the temple database at temple.caosity.org::srpms. BTW: Are there any volunteers to document the package maintenance process? On Thu, Dec 25, 2003 at 10:37:16PM -0800, Greg Kurtzer told me: > I was debating the idea for package hints and the best way to implement them. > > Background: Hints are packages that _should_ be installed to build another > (similar to a 'BuildRequires' in a RPM SPEC). > > Is there any reason why we should not mandate that all hints be specified as > BuildRequires inside the SPEC itself (ie. HINT == BUILDREQ)? The only reason > that I have come up with is that we may be changing many RPM SPEC's that > otherwise would not need changing. > > > -- > Greg M. Kurtzer > http://runlevelzero.net/ > http://caosity.org/ > http://warewulf-cluster.org/ > _______________________________________________ > cAos mailing list > cAos at caosity.org > http://www.caosity.org/mailman/listinfo/caos -- Greg M. Kurtzer http://runlevelzero.net/ http://caosity.org/ http://warewulf-cluster.org/ From greg at runlevelzero.net Sun Dec 28 00:29:40 2003 From: greg at runlevelzero.net (Greg Kurtzer) Date: Sun, 28 Dec 2003 00:29:40 -0800 Subject: [cAos] Buildroot updated... Message-ID: <20031228082940.GA26240@runlevelzero.net> buildroot-1 has been updated at: temple.caosity.org::buildroot-1 -- Greg M. Kurtzer http://runlevelzero.net/ http://caosity.org/ http://warewulf-cluster.org/ From kuko at maarmas.com Mon Dec 29 09:12:59 2003 From: kuko at maarmas.com (Miguel Armas) Date: Mon, 29 Dec 2003 17:12:59 +0000 Subject: [cAos] Some questions... Message-ID: <1072717979.1601.34.camel@homer.maarmas.int> Hi all!! I've been reading the FAQs and the list and I still have some questions about cAos/CentOS... 1. Will CentOS be only a RHEL rebuild and all contributions must go into cAos-GP, or can we contribute packages into CentOS? 2. If all contributions must go into cAos, do we have to wait for cAos-2 or can we start working with CentOS-3. I'll prefer to work on something based on RHEL3 instead of the 2 series If we can add contributions to CentOS I think we need the following before a public release: 1. A centos-release package with the CentOS GPG public keys. This should be the version number used by yum and apt. 2. GPG signed repositories available with yum and apt. The repositories could be like in Fedora (base, updates, stable, testing, unstable, etc) 3. Include yum and apt into the distro. The packages should use the previous repositories About the QA policy: 1. Are we going to reinvent the wheel, or can we use the ideas from the Fedora project? Well, I guess what I'm really saying is that we should try to use the ideas and work put into Fedora but using CentOS/cAos as the base system. This would make things easier for developers working on both projects (like me ;). If we follow the Fedora QA rules, it should be really easy to compile all the Fedora packages under CentOS/cAos... Salu2! -- -------------------------------------- Miguel Armas Consultor de Sistemas y Comunicaciones Ing. Tec. de Telecomunicaciones -------------------------------------- From mhedemark at trueposition.com Mon Dec 29 09:31:01 2003 From: mhedemark at trueposition.com (Hedemark, Magnus) Date: Mon, 29 Dec 2003 12:31:01 -0500 Subject: [cAos] Some questions... Message-ID: <9E72DA54A657354DAE751492248657C9514D28@mailhost.trueposition.com> Miguel Armas [mailto:kuko at maarmas.com] asks: > Hi all!! > I've been reading the FAQs and the list and I still have some > questions > about cAos/CentOS... > > 1. Will CentOS be only a RHEL rebuild and all contributions > must go into > cAos-GP, or can we contribute packages into CentOS? My understanding is that there will be a contrib area for CentOS after the infrastructure is in place. It is probably more important right now to stabilize the distro, and *then* get excited about third party packages. :) I will personally be packaging a few of my favorite apps for the contrib repository so I'm looking forward to this as well. > 2. If all contributions must go into cAos, do we have to wait > for cAos-2 > or can we start working with CentOS-3. I'll prefer to work on > something > based on RHEL3 instead of the 2 series I'm running CentOS-3 right now. There are some aesthetic issues to work out still but otherwise it's very run-able. > About the QA policy: > 1. Are we going to reinvent the wheel, or can we use the > ideas from the > Fedora project? I think that Fedora (the original Fedora, before Red Hat assimilation) would be a great place to start to pull contrib policies/procedures. --Magnus From greg at runlevelzero.net Mon Dec 29 17:31:34 2003 From: greg at runlevelzero.net (Greg Kurtzer) Date: Mon, 29 Dec 2003 17:31:34 -0800 Subject: [cAos] Some questions... In-Reply-To: <1072717979.1601.34.camel@homer.maarmas.int> References: <1072717979.1601.34.camel@homer.maarmas.int> Message-ID: <20031230013134.GA23115@runlevelzero.net> On Mon, Dec 29, 2003 at 05:12:59PM +0000, Miguel Armas told me: > Hi all!! > I've been reading the FAQs and the list and I still have some questions > about cAos/CentOS... > > 1. Will CentOS be only a RHEL rebuild and all contributions must go into > cAos-GP, or can we contribute packages into CentOS? There will be a contrib section. In the end, you can contribute to whatever project you wish. ;) (hopefully both!) > 2. If all contributions must go into cAos, do we have to wait for cAos-2 > or can we start working with CentOS-3. I'll prefer to work on something > based on RHEL3 instead of the 2 series You do not have to wait for cAos-2 to contribute to cAos (unless you don't want to work with cAos-1). FYI: cAos-1 is very current, and the only thing that is based on EL2 that matters now is glibc and gcc2. Everything else is pulled from EL3 or community maintained sources directly. Check out the packages at http://mirror.caosity.org/! :) > If we can add contributions to CentOS I think we need the following > before a public release: > > 1. A centos-release package with the CentOS GPG public keys. This should > be the version number used by yum and apt. > 2. GPG signed repositories available with yum and apt. The repositories > could be like in Fedora (base, updates, stable, testing, unstable, etc) cAos is using the following repositories: crazy: unQA'ed packages right off of the build farm current: All known good/secure packages chilled: the oldest known good/secure package coffin: obsolete packages > 3. Include yum and apt into the distro. The packages should use the > previous repositories YUM is included by default, but I am not sure about APT. > About the QA policy: > 1. Are we going to reinvent the wheel, or can we use the ideas from the > Fedora project? > Well, I guess what I'm really saying is that we should try to use the > ideas and work put into Fedora but using CentOS/cAos as the base system. > This would make things easier for developers working on both projects > (like me ;). If we follow the Fedora QA rules, it should be really easy > to compile all the Fedora packages under CentOS/cAos... As I read into it, the ideas from Fedora are sound, but (at least before RH assimilation) was not streamlined, and used bugzilla for almost everything. I am starting from the other direction (at least for cAos). First create a general flow principal, then streamline, and lastly the finishing touches. Right now I am building the QA systems. Greg -- Greg M. Kurtzer http://runlevelzero.net/ http://caosity.org/ http://warewulf-cluster.org/ From lance at uklinux.net Mon Dec 29 18:16:39 2003 From: lance at uklinux.net (Lance Davis) Date: Tue, 30 Dec 2003 02:16:39 +0000 (GMT) Subject: [cAos] Some questions... In-Reply-To: <20031230013134.GA23115@runlevelzero.net> Message-ID: On Mon, 29 Dec 2003, Greg Kurtzer wrote: > On Mon, Dec 29, 2003 at 05:12:59PM +0000, Miguel Armas told me: > > Hi all!! > > I've been reading the FAQs and the list and I still have some questions > > about cAos/CentOS... > > > > 1. Will CentOS be only a RHEL rebuild and all contributions must go into > > cAos-GP, or can we contribute packages into CentOS? > > There will be a contrib section. In the end, you can contribute to whatever > project you wish. ;) (hopefully both!) > > > 2. If all contributions must go into cAos, do we have to wait for cAos-2 > > or can we start working with CentOS-3. I'll prefer to work on something > > based on RHEL3 instead of the 2 series > > You do not have to wait for cAos-2 to contribute to cAos (unless you don't > want to work with cAos-1). You can also contribute directly to CentOS-3 and most packages should also build for caos-1 - although they may have to go through a different QA procedure, and there may be things that just woint build because of version dependencies etc. > FYI: cAos-1 is very current, and the only thing that is based on EL2 that > matters now is glibc and gcc2. Everything else is pulled from EL3 or community > maintained sources directly. Check out the packages at > http://mirror.caosity.org/! :) > > > If we can add contributions to CentOS I think we need the following > > before a public release: > > > > 1. A centos-release package with the CentOS GPG public keys. This should > > be the version number used by yum and apt. > > 2. GPG signed repositories available with yum and apt. The repositories > > could be like in Fedora (base, updates, stable, testing, unstable, etc) > > cAos is using the following repositories: > > crazy: unQA'ed packages right off of the build farm > current: All known good/secure packages > chilled: the oldest known good/secure package > coffin: obsolete packages (I thought we were using 'certified' now - dont see 'current' anywhere ???) I think that Centos could use the same repositories as caos for its contrib repo - so it would have :- base updates extras/crazy = unqa'ed extras/certified = qa'ed extras/chilled ??? > > > > 3. Include yum and apt into the distro. The packages should use the > > previous repositories > > YUM is included by default, but I am not sure about APT. Not yet ... also we hope to have up2date as an option. > > > About the QA policy: > > 1. Are we going to reinvent the wheel, or can we use the ideas from the > > Fedora project? > > Well, I guess what I'm really saying is that we should try to use the > > ideas and work put into Fedora but using CentOS/cAos as the base system. > > This would make things easier for developers working on both projects > > (like me ;). If we follow the Fedora QA rules, it should be really easy > > to compile all the Fedora packages under CentOS/cAos... > > As I read into it, the ideas from Fedora are sound, but (at least before RH > assimilation) was not streamlined, and used bugzilla for almost everything. I > am starting from the other direction (at least for cAos). First create a > general flow principal, then streamline, and lastly the finishing touches. > Right now I am building the QA systems. > I can see some benefits to using bugzilla for submissions, but prefer Gregs way of doing qa, because it allows for more than one qa tester, whereas I think fedora only has 1 ... ??? So maybe submissions via Bugzilla, in a 'fedora compatible' way, then push the submissions into a caos/centos qa system ??? Lance -- uklinux.net - The ISP of choice for the discerning Linux user. From greg at runlevelzero.net Mon Dec 29 19:14:21 2003 From: greg at runlevelzero.net (Greg Kurtzer) Date: Mon, 29 Dec 2003 19:14:21 -0800 Subject: [cAos] Some questions... In-Reply-To: References: <20031230013134.GA23115@runlevelzero.net> Message-ID: <20031230031421.GA23712@runlevelzero.net> On Tue, Dec 30, 2003 at 02:16:39AM +0000, Lance Davis told me: > > crazy: unQA'ed packages right off of the build farm > > current: All known good/secure packages > > chilled: the oldest known good/secure package > > coffin: obsolete packages > > (I thought we were using 'certified' now - dont see 'current' anywhere > ???) Oh yes... Silly me. :) -- Greg M. Kurtzer http://runlevelzero.net/ http://caosity.org/ http://warewulf-cluster.org/ From landman at scalableinformatics.com Tue Dec 30 18:59:34 2003 From: landman at scalableinformatics.com (Joe Landman) Date: Tue, 30 Dec 2003 21:59:34 -0500 Subject: [cAos] cAos install problem and a cinch question Message-ID: <1072839574.4462.240.camel@protein.scalableinformatics.com> Hi folks: Tried the install twice, and it died the same way. Filed a bug (180) on it. Quick question on cinch. Is it/will it be scriptable? Any docs? Also, is there a quick repository setup bit so I can have the bits here to work with rather than going out over the net? Thanks Joe From greg at runlevelzero.net Tue Dec 30 21:55:33 2003 From: greg at runlevelzero.net (Greg Kurtzer) Date: Tue, 30 Dec 2003 21:55:33 -0800 Subject: [cAos] cAos install problem and a cinch question In-Reply-To: <1072839574.4462.240.camel@protein.scalableinformatics.com> References: <1072839574.4462.240.camel@protein.scalableinformatics.com> Message-ID: <20031231055533.GA7953@runlevelzero.net> On Tue, Dec 30, 2003 at 09:59:34PM -0500, Joe Landman told me: > Hi folks: > > Tried the install twice, and it died the same way. Filed a bug (180) > on it. Just responded to it... > Quick question on cinch. Is it/will it be scriptable? Any docs? > Also, is there a quick repository setup bit so I can have the bits here > to work with rather than going out over the net? I built cinch with scripting the installation in mind. The install is driven literrally by 2 shell scripts. One for the initrd, and the other the stage2 install. All that has to happen is to source a file that has all of the entries already known, and begin each stanza with a if [ -z $VAR ]; then... Pretty easy but it will just take time. ;) Information for setting up a mirror can be obtained at: http://caosity.org/index.php?option=displaypage&Itemid=85&op=page&SubMenu= Otherwise, it is a yum repository set up in the same directory structure as we have starting from /cAos-[VERSION]/. Then just make sure you have the cinch directory that contains the stage2 image. You can also try the cdrom installation method. Grab cinch.iso, and it has a local repository thta will install a base system (very stripped down right now). Let us know how it goes! Greg -- Greg M. Kurtzer http://runlevelzero.net/ http://caosity.org/ http://warewulf-cluster.org/