history
sorcery
by anders pearson
Fri 15 Mar 2002 11:56:11
after reading a <a href="http://www.nvmax.com/cgi-bin/nvmax.pl?action=reviews:SORCERER_GNU">few </a> <a href="http://www.idg.net/go.cgi?id=647988">intriguing</a> <a href="http://www.distrowatch.com/review-sorcerer.php">reviews</a> last week, i decided to give <a href="http://www.distrowatch.com/sorcerer.php">Sorcerer Linux</a> a try. the thought of a distribution that was completely compiled from source on my own machine and had the ability to automatically keep all the software installed completely up-to-date was more than enough to make me drool.
so last friday night, i backed up all my data and made careful notes of my hardware configuration. on saturday i went to download the ISO image for the install cd from what was the current site at the time, sorcerer.wox.org. instead of the page i'd seen before, i was redirected to the <a href="http://www.lunar-penguin.org/">lunar penguin</a> site. there had been mention in a few of the reviews that Kyle Sallee, the main developer of Sorcerer was getting a job and wouldn't be able to continue working on it. from what i could glean from a quick look at the lunar penguin site, it looked like kyle had finally given up and abandoned sorcerer and lunar penguin had taken its place. i decided to hold off on installing just to let things settle down a bit.
so i installed <a href="http://www.debian.org/">Debian</a> instead, spent a few days trying unsuccessfully to get networking working, gave up on debian and reinstalled <a href="http://www.mandrake.com/">mandrake</a>. all the while i read through the Sorcerer <a href="http://mail.envisage.co.za/pipermail/sgl/">mail archives</a> trying to figure out what had happened and what direction things were moving in.
what i found was absolutely fascinating. it was a little more complex than just being kyle running out of time and energy to work on the project. while none deny that kyle is a fantastically talented coder who did some great work, there were apparently some personality conflicts. he would consistently reject patches that others contributed. in general it looked like he only wanted contributors who would do exactly what he told them and who would do all the grunt work for him. but he would refuse any contributions that came with input on the direction of the project. all this time, he was loudly complaining that if people didn't start helping him (on his terms only) SGL development would have to stop.
naturally, flame-wars ensued on the mailing list, egos were damaged, tempers flared, and kyle became less and less coherent. some of the other developers, who were largely interested in having periodic "stable" releases forked the code and created the lunar penguin distro. around saturday, something in kyle snapped and he took down the sorcerer web site, replacing it with a redirect to the lunar penguin site. from this and some comments he made to other people, it appeared that he was stepping down from SGL and was endorsing LP.
meanwhile, the rest of the sorcerer developers, free from kyle's restraints got busy picking up the pieces, reorganizing and getting things going again. they put together a <a href="http://www.sorcerylinux.org/">new website</a> and got back to work on the code.
but things got weirder. the original SGL website changed from redirecting to LP to an <a href="http://sorcerer.wox.org/">almost surreal manifesto</a>. unsigned and written in the third person, attacking the LP team and the SGL developers alike and making vague, questionable legal threats. no one seems to have heard directly from kyle since it appeared. he hasn't come forward to either confirm or deny that he wrote and posted the diatribe or to answer any of the many <a href="http://www.sorcerylinux.org/modules.php?op=modload&name=News&file=article&sid=7&mode=thread&order=0">rebuttals</a> to it.
after following this whole saga i figured that at the very least i should install sorcerer just to make sure it was worth the time and energy i was putting into researching it. the amount of activity and the speed with which the SGL developers recovered the project after kyle pretty much deliberately tried to kill it assures me that SGL isn't going to be abandoned anytime soon. technically, i have yet to hear any criticisms of it beyond bug reports on some weird configurations.
so i downloaded and installed. i started wednesday night and, because i hadn't RTFM'd carefully enough, i screwed some stuff up and couldn't get it to boot without a rescue disk. it took about 5 minutes on irc yesterday to find someone who knew how to fix it to help me out. when i went home last night i made the change and everything started working flawlessly again. i got networking up without a hitch, updated the system, rebuilt it so the binaries of the minimal system that came on the install CD were replaced with freshly compiled and optimized ones. compiling is slow so that took pretty much all night. i started xfree86 compiling before i left for work this morning; i expect that it's still going as i write this. i'll still have to compile gnome and kde before i have a whole desktop machine again but already i'm impressed with how smoothly things have gone.
when you go to compile an app, sorcery automatically figures out all of its dependencies, downloads those and compiles them. i'm not really done yet but so far i'm definately impressed with sorcerer. with some UI work on the installer and better documentation i think sorcerer has what it takes to be a major distribution. being highly optimized, configurable and constantly updated should make it the distro that all the "cool" geeks are running within a year or two. of course, since the install takes so long and you need to know a lot about linux just to get it working, we'll probably still be handing out redhat or mandrake CDs to newbies.
comments
anders pearson - Fri 15 Mar 2002 11:57:11
the saga continues. the diatribe on sorcerer.wox.org has now been replaced with a new shorter one.anders pearson - Fri 15 Mar 2002 11:58:11
and now, in a display of fabulously irresponsible journalism, linuxtoday.com is running the sorcerer.wox.org diatriabe as a <a href="http://linuxtoday.com/news_story.php3?ltsn=2002-03-15-008-26-OS-CY-DV">story</a>. read <a href="http://linuxtoday.com/news_story.php3?ltsn=2002-03-15-008-26-OS-CY-DV-0006">Jean's reply</a>.Mark Boudreau - Fri 15 Mar 2002 11:59:11
How's the documentation? I was looking through it, and it seems pretty good, but the only time you can tell if the documentation is good is when you really need it. Also, any gotchas that you came across that the docs didn't seem to cover?anders pearson - Fri 15 Mar 2002 12:00:11
it's not that bad. kind of sparse and poorly organized but better than some i've seen. sorcerer does a few peculiar things that make it more or less necessary to read the documentation carefully. eg, when you use the regular menuconfig to turn options on and off in the kernel, there are a few things that you have to be careful to not touch because sorcerer requires them. the biggest problem with the documentation as far as being suitable for newbies is that since sorcerer's installer still requires you to do other things like configure and compile your own kernel, the documentation for that stuff isn't included. they expect that you're reasonably comfortable compiling a kernel already. what got me was that it uses devfs, which i'm relatively unfamiliar with. this means that you have things like /devices/discs/disc0/part1 instead of /dev/hda1. so when sorcerer dropped me into /etc/lilo.conf to make any changes i needed i saw it pointing to the devfs stuff for the boot location, thought it was wrong and changed it to /dev/hda (what i'm used to seeing in lilo.conf). once i figured out that i'd screwed that up it was a pretty simple matter to boot from a rescue disk, change it back and rerun lilo. if i'd actually read the documentation more carefully the whole install would have gone perfectly smooth. so i think some more prominent mention of the whole devfs thing should probably be in the docs.