GeDI (GEneric Diskless Installer) / News: Recent posts

This took a while. People have been using everything straight from SVN (as I told them to do), so this is finally a tagged release of that.

There's been some major work done to the overall layout of GeDI. When I'm done, there should be a new release available for download. Until then, you can pull from the SVN (if you dare).

Created a new release based on the subversion drop. A few bug fixes as well as an update to unionfs.

With the new availability of subversion on sourceforge, GeDI has been migrated over to a subversion repo. Therefore, all work and updates to CVS will be halted and pushed to subversion.

I'm still working on the "make rpm" portion of the subversion repo, but that should be done shortly (so things will be shortly back to normal).

It's taken a bit of time to finally get documentation and everything else done, but the latest version of GeDI has a tag and an associated RPM to download. There are a number of changes that came with this update, but I can't really remember what any of them are (hence there's a ChangeLog).

After a bit of work (namely because I screwed up the first import), I've gone through and put gedi into SourceForge's CVS. Because SourceForge already had someone with the gedi name, I was forced to use gedi-tools, but the package is still name gedi (because I like that name). Therefore, when you do the CVS drop, you need to still use gedi-tools, but a "make rpm" will still create a gedi package. If this is confusing, don't worry about it... just do a make rpm and everything will be ok (at least it should be).

This release comes with a number of changes in the undelying scripts. Namely, there is better handling of creation of the dhcpd.conf, we're now using "group"s in dhcpd.conf, and we're now passing options to pxelinux to allow for a sharing of file in pxelinux.cfg between same nodetypes.

This release finally moves away from the idea of symlinks and ramdisks, and moves forward to unionfs. UnionFS allows the software to mount a read-only NFS root filesystem and merge it with a writeable RAM filesystem. Therefore, it can boot an unmodified image and still have the client node think that it has full write access.

This release get's everything to RHEL4 standards and does some better handling of creating ramdisks.

Enjoy.