Wow, when I get a decent network connection, redhat it'll be. Could a redhat 55.2 box be updated to 6.2 this way? At 06:05 PM 9/27/00 -0700, you wrote: > >For those who would like to know, Redhat offers a similar utility to >Debian's update. Redhat calls it rpmfind. You specify a word on the command >line and rpmfind wills earch the database for it, if it finds, it tells you >allthe dependences, you just hit "download all" option. >Best, >Vic >******* ******* ******* >have you thought of visiting Cybertsar's Internet Kingdom? It is still >alive! >Here is the URL: >http://nimbus.ocis.temple.edu/~vtsaran/ >******* ******* ******* >----- Original Message ----- >From: "Gene Collins" <collins at gene3.cc.iastate.edu> >To: <speakup at braille.uwo.ca> >Sent: Tuesday, September 26, 2000 9:24 AM >Subject: Re: Distro discusion > > >> Kirk, http://www.linuxdoc.org/ is your documentation friend! There are >> very explicit howtos out there for hardware and various software. >> Debian also follows the Sys V. init style. The thing I find most >> helpful about Debian is that the apt-get installation program manages >> software dependentcies for you very nicely. If you upgrade gcc for >> example, apt-get will also upgrade the appropriate libraries. >> >> Gene >> >> >Personally, the biggest thing that I believe is important on a >> >distribution is good documentation on where files are placed. Having said >> >that, I think it is past time for the distributions to discuss this and >> >commit to following a standard (or two). Certainly there will be >> >differences in such things as init scripts. After all Slackware uses a >BSD >> >style init (more or less) while RedHat uses a SystemV ini (more or less). >> > >> >There are advantages to both of them, and that isn't the point. The thing >> >is that RedHat does place some config files in strange places. If there >> >was one place to put a given file it would make Linux overall >> >stronger. There could still be room for each to do its thing for >> >improvement. (For instance once you say that all init scripts will reside >> >in rc.d you can choose to follow the redhat method of a directory for >each >> >run level and one for the actual scripts. Or you could decide to place >> >them all in the /etc/rc.d dir.) >> > >> >Actually, documentation is the biggest weakness I see in Linux. The fact >> >is that much of the documentation is great if you already know what your >> >doing. Some of it is great, and some is lousy. Sometimes knowing whre to >> >look though can be a major task in the first place. One master document >> >giving direction on where to look for all network functions would be >> >nice. One covering all disk subsystems would also go a long way. >> > >> >-- >> >Kirk Wood >> >Cpt.Kirk at 1tree.net >> >------------------ >> > >> >Seek simplicity -- and distrust it. >> > Alfred North Whitehead >> > >> > >> > >> >_______________________________________________ >> >Speakup mailing list >> >Speakup at braille.uwo.ca >> >http://speech.braille.uwo.ca/mailman/listinfo/speakup >> >> _______________________________________________ >> Speakup mailing list >> Speakup at braille.uwo.ca >> http://speech.braille.uwo.ca/mailman/listinfo/speakup > > >_______________________________________________ >Speakup mailing list >Speakup at braille.uwo.ca >http://speech.braille.uwo.ca/mailman/listinfo/speakup > > >
