Couple things. Download the tarball. Blow it out as usual. However, before blowing out tree, be sure you are root. It will want to blow out /dev, and you have to be root in order to do this. Actually, most of this is covered in the readme. It is detailed. I worked hard on it (just like this initial release). Use the force.
|
NEWS: Believe it or not, I'm going to do something with this project. Unfortunately I've got 50 other pressing things on my plate before I'll take this project up again. The good news is that I've got some related projects coming up so I might dust this project off and get things back up and running. We'll see. I'm still awaiting info from the Litestream author regarding the patch / license issue questions I had for him. Once I hear back I'll proceed with switching RiR over to Litestream. I'm working on a client first and foremost. Floppy based, mpg123 on the back, it should be pretty sweet. RIMiRadio 0.4 released. Major change is that it now has Icecast 1.3.10. There were several security problems in previous versions of Icecast. How much they can be exploited on a floppy distro remains to be seen, but I'd suggest upgrading anyway. Minor change is that I've corrected the /etc/issue reporting the wrong version of RiR. Enjoy! RiR v 0.4 the Enjoy the Silence release. Latest news is that 1.3.10 is available on the Icecast site. I'm going to try to sit down this weekend and build it / release a new RiR. I'll also probably see where things stand with Litestream on a floppy. Icecast 2.0 is not here yet, but is supposed to be around the corner. The problem with litestream is there is no authentication for the source stream. Right now I'm looking at 1 of 2 options: Get xinetd / tcpwrappers running on the floppy and wrapping around the source stream port Use IPChains (RiR is kernel 2.2 based) and setting up rules that way. I think I'm going to have to go the xinetd route which may have additional advantages. Of course, if any of you have any suggestions I'm entertaining them at this moment. Well, it appears the Icecast list suffered some downtime. Development is in fact still taking place. Likewise, Icecast 2.0 is supposed to be on the way. Apparently all of the bugs I ranted about and others have thrown a fit about are fixed in the lastest cvs snapshots. I'm going to have to get my cvs on and see what the hoopla is about. I was also informed that if in fact I set my timings correct you can keep a client without kicking them sans source (think distributed on demand jukebox). I'll have to play around with that, but it would seem litestream would be the better server... especially on a closed network. First and foremost. Icecast is broken. I've spent a couple of weeks on the icecast-discuss list. There are two major bugs floating around at this time. Both of them have been known for quite awhile. Both from discussion (and not from testing) appear to be in RiR, all versions. There is no point upgrading or downgrading the Icecast server that ships with RiR because it is in both stable and beta versions. This BLOWS. Icecast is poised to be the streaming server for Ogg Vorbis. If I were on the Ogg Vorbis team I'd put my foot down. According to sources, the code for Icecast is in such bad shape that a fresh start to it is most likely the best way to get rid of the issues that currently plague this sorry excuse for a server. The problem is, while I'd be more than happy to help put the smak down on these issues, I don't posess the tools upon which to get the job done. Futhermore, there are some features that I would like to see added to icecast. But, I don't see them being added without the codebase being fixed. I personally believe the Icecast team should take a lesson or two out of the pages of the Apache and Samba team's books, especially when it comes to doing config files. Needless to say, I apologize for the rant, but wanted to give you the current state of affairs for RiR. I'm looking at ripping out Icecast and all of its problems and replace it with the Litestream server. For whatever reason I felt there was some show stopper with Litestream and was the reason I felt I had to use Icecast. I'll probably rediscover the issue when it comes time to make the move. However, unless Icecast gets its act together I'm going to have to do what is good for the long term. Dump Icecast and move to Litestream. --Sean... RIMiRadio v 0.3 the Ball and Chain release * Small update to the crypt code in configRiR and finally adding the promised icecast.conf file for reference purposes (icecast.ref). * The changes in configRiR involve the crypted pass routine. In short, the code indicated it came from the BSD adduser script. Unfortunately I did not properly credit the code in question and there were some questions surrounding the licensing. Rob H from NLUG was kind enought to clean room the code in question and submitted it back as GPL to my project. Note, everything else on RiR is GPL. * Clarified the NIC support list. They are:
* RiR-0.2 removed from download given the aformentioned licensing issues. Otherwise 0.3 has not really changed. Please upgrade to this version, it has several major changes and allows you to easily setup a Icecast server faster than the law allows. (And contrary to the liner notes, the icecast.conf as shipped with icecast is not in there. Not really that big of a deal, but I'll get it up in the next day or so). I'm also not sure why it is now 2.3 megs, up from 1.4 on 0.1, but it all still crams onto a floppy, so I'm not too worried. from 0.1 to 0.2
* First and foremost, the login issue is fixed. Amazing what happens when you give a problem a little bit of time and another look. Thanks Craig! Anyway, we're making use of tiny login, again from the fine folks at Lineo. This also adds passwd and su. We're still using mingetty. Using the getty from tinylogin is only 6k vs mingetty's 12k. I found it acceptable given the lack of reasonable documentation available for TL's getty. I may revisit this later, but space can and should be trimmed in other areas before forcing this issue. FYI, this login supports crypted passes as I was hoping to use... nothing more and nothing less. Glad I did not have to hack up a shell script. That would have sucked. * Added the kernel .config that I forgot to add when I made the initial tarball. * I created configRiR for the purposes of making everyone's life easier and to have a default network come up on boot. You will not need to boot or hack something up as necessary in the 0.1 release. configRiR creates ~/tree/sbin/network (a shell script) out of the questions it asks you. /etc/resolv.conf is currently created on the fly out of this shell script... hence you will not find it in ~/tree. You can change this if you like, and if the response is overwhelming, I'll change that behavior too. * Added the passwd config. This will create the accounts in ~/tree/etc/passwd with crypted passwords. It makes use of the perl crypt feature. * Added the icecast server config. Basic must have options only. Superceded by 0.2. Please only use this if you need a starting point for another project. RIMiRadio v 0.1 the fsckit! release Sean... |