CML2 may be as ready for Linux 2.5 as it can be, but that doesn't matter one bit if Linus doesn't want to take it. It seems to me ESR is taking it for granted that this will be the next kernel configuration scheme, but what's the word from the main man himself? I haven't heard a word about CML1 being replaced, but then I really don't follow the LKML too closely.
I imagine there would be quite a few oposed to this, especially if Linux now needs to ship with Python as well.
Would it perhaps be feasible to to compile the CML2 parser, and just ship that binary for those that don't want to install Python as well? Or does someone have other tricks up their sleeve?
Or even better, use a program like cfengine (http://www.iu.hioslo.no/cfengine/) and automate all your sysadmin tasks. We use a similar system at work written by our developers, and maintaining our 150+ servers spread out in 3 countries is *easy*. Need to upgrade Apache? Do it in one place, and it'll be distributed out during the night or on demand. Need to apply a patch of some kind? Yet again, it's done in one place and pushed out to the servers.
Slackware is what I started out with when I first tried Linux. A friend told me what packages I should get and I downloaded them all at school, put them on floppies and installed at home. Since then I've tried both RedHat and Debian but I still prefer Slackware! These days I'm actually running FreeBSD but I have Debian 2.1 on a partition here. (despite the fact that it didn't even configure LILO right, like slack does.)
I prefer installing everything manually, although that makes for a messy system after a while. (That's why I like FreeBSD, you have full control over the sources from the ports collection, and yet you have a nice uninstall function.)
I don't use Debian though, because I really can't stand dselect. Now that slack 4.0 is out it seems like the perfect time to wipe that partition and start over.:-)
It's really good seeing that the distro is still going strong and I'm looking forward till my CD's arrive.:-) Happy days are here again...
RIPE has pretty much all of the RFC's in text format, as far as I can see, at ftp.ripe.net/rfc/. The file rfc-retrieval.txt contains a list of mirrors which probably are closer to you.
CML2 may be as ready for Linux 2.5 as it can be, but that doesn't matter one bit if Linus doesn't want to take it. It seems to me ESR is taking it for granted that this will be the next kernel configuration scheme, but what's the word from the main man himself? I haven't heard a word about CML1 being replaced, but then I really don't follow the LKML too closely.
I imagine there would be quite a few oposed to this, especially if Linux now needs to ship with Python as well.
Would it perhaps be feasible to to compile the CML2 parser, and just ship that binary for those that don't want to install Python as well? Or does someone have other tricks up their sleeve?
Or even better, use a program like cfengine (http://www.iu.hioslo.no/cfengine/) and automate all your sysadmin tasks. We use a similar system at work written by our developers, and maintaining our 150+ servers spread out in 3 countries is *easy*. Need to upgrade Apache? Do it in one place, and it'll be distributed out during the night or on demand. Need to apply a patch of some kind? Yet again, it's done in one place and pushed out to the servers.
There's no end to the possibilities!
Slackware is what I started out with when I first tried Linux. A friend told me what packages I should get and I downloaded them all at school, put them on floppies and installed at home. Since then I've tried both RedHat and Debian but I still prefer Slackware! These days I'm actually running FreeBSD but I have Debian 2.1 on a partition here. (despite the fact that it didn't even configure LILO right, like slack does.)
:-)
:-) Happy days are here again...
I prefer installing everything manually, although that makes for a messy system after a while. (That's why I like FreeBSD, you have full control over the sources from the ports collection, and yet you have a nice uninstall function.)
I don't use Debian though, because I really can't stand dselect. Now that slack 4.0 is out it seems like the perfect time to wipe that partition and start over.
It's really good seeing that the distro is still going strong and I'm looking forward till my CD's arrive.
Way to go Patrick, keep slack going!
RIPE has pretty much all of the RFC's in text format, as far as I can see, at ftp.ripe.net/rfc/. The file rfc-retrieval.txt contains a list of mirrors which probably are closer to you.