Aaah, I see. :)

It looks like you're addressing all the issues fine, so I have no
gripes.  I'll check out the starships lab and you'll probably get a slew
of fixme's.  :)

Hans :)

* Michael Torrie ([EMAIL PROTECTED]) thus spake:
> Because of my brain-dead junk filter, I've missed half of the conversation.  
> Gotta love hotmail.  For some reason I still use it...
> 
> First off, we are beta testing a lab of RH 7 machines and plan to eventually 
> reimage everything.  Before you panic, read all the message.  The purpose of 
> this beta test time is to try to get the setup such that the transition will 
> be relatively painless.  (No I'm not being facetious here, either).
> 
> As for the reasoning, we'll I'll tell you what led up to this.
> 
> First off, RH7 itself is *not* broken.  Straight off the CD, two important 
> components *are* broken, which are fixed (by my and redhat).  First the 
> GLIBC was a prelimary version of 2.2 (2.1.92 or something) that was broken 
> in many ways.  This has since been fixed with the official release of glibc 
> 2.2.  Mandrake 7.2 also ships with this glibc.  The biggest gripe was the 
> compiler.  It has got a lot of problems.  It's more ansi compliant too, 
> which causes a lot of grief for those of us who depended on the broken gcc 
> 2.7 series compiler.  I fixed this compiler gripe by going with 2.95 
> (essentially a mandrake rebuild).
> 
> The C++ standard library that ships with rh 6.2 has a number of problems and 
> things unplemented.  I was thinking it would be nice to upgrade it a bit.  
> The version that ships with GCC 2.95 seemed nice enough, so I wanted to put 
> that on.  For some reason that I can't recall, I wanted to upgrade the glibc 
> (I think there were some threading issues and I had one program that had to 
> be compiled against it).   Previous to this time I had upgraded rpm (and the 
> databse) to rpm 4.0.  I got the latest RH rpm for glibc2.2 and installed it, 
> along with the Redhat 6.x compatibility libraries (for glibc 2.1).  I then 
> built a custom version of GCC 2.95.1 to upgrade the compiler.  This works 
> well and even compiles the kernel! ;)  In fact, I haven't found a single 
> piece of my C++ code that wouldn't compile.
> 
> Another factor was that because my machine (the image) was running rpm 4, 
> Helix Gnome updater program completely bombed, saying it couldn't deal with 
> rpm 4, being compiled for redhat 6.
> 
> Once I had upgrade the GLIBC and the compiler, I realized that I was now 
> pretty much running redhat 7, so I went ahead and replaced all the rest of 
> the packages with fresh counterparts.  That's how I ended up with a RH 7 
> (almost -- more like 6.99) distribution.  Now helix update works fine too.  
> So in a way, it kind of came about by accident.  Also interesting is that 
> the entire upgrade from rh 6.2 to rh 7 was done without a reboot.  I was 
> already running a custom kernel.  So in otherwords, I did upgrade on a 
> package-by-package basis.  The end result is more or less rh7, that works.
> 
> Some specs:
> Kernel 2.2.18/2.4.2 (having some probs with kernel 2.4)
> - custom build with spiffy boot logo, supermount support
>    (see lpp.freelords.org)
> GLIB 2.2
> GCC 2.95
> KDE 2.1 (with anti-aliasing support enabled)
> Ximian Gnome 1.2 (will probably be 1.4 by the time images go out)
> A lot of other software that I need to catalogue.
> Binary compatible with stock rh7 and rh6
> 
> As for this not being the time, I don't think it much matters.  I can put in 
> kernel 2.4 whenever I want, and will do so once I resolve a couple of small 
> issues.  Redhat 7.1 is almost out and will upgrade the packages as soon as 
> they are stable.  (All this can be done on all my machines remotely too 
> without rebooting -- 7.1 is just rpm upgrades really.  I have my own kernel 
> already).  The biggest concern for us at this point is making sure students 
> can transition.  CS 240 especially.  We'd appreciate if all issues are 
> reported to us about problems compiling, missing programs, etc so we can get 
> things fixed.  The rh7 machines are currently the starships in room 1027.  
> Check them out.  Give me feedback.
> 
> As for enlightenment, I'll put it on my todo list.  I thought I had 
> installed it on the old image... 16.x, I mean.  I'll check on the new image.
> 
> That ends the epic of the accidental upgrade to rh7.
> 
> Michael
> 
> >From: Hans Fugal <[EMAIL PROTECTED]>
> >
> >I agree.  If it ain't broke don't fix it - and IMHO 7.0 is broke and 6.2
> >isn't.
> >
> >Hans :)
> >
> >* Mark Gulbrandsen ([EMAIL PROTECTED]) thus spake:
> > > Just my opinion...
> > >
> > > I hope they don't update yet.
> > >
> > > This is not the time to reinstall linux boxes.  All of the distributions 
> >are
> > > gearing up for new releases that include the 2.4.x kernel as well as the
> > > latest versions of software.  Wait for those releases.  Its probably 
> >only a
> > > month or two away.  Update packages on a case by case basis instead.
> > >
> > > Again, just my opinion.
> > >
> > > On Wednesday 14 March 2001 09:26, you wrote:
> > > > Also, does anyone [i.e. the CS folk] know what's going on with the 
> >rumours
> > > > about major reinstalls in the CS labs? I've heard they're all getting
> > > > RedHat 7.0 (with a better/older version of g++).
> > > > Few questions:
> > > >   1. Why? Isn't 6.2 good enough?
> > > >   2. What kernel will be used?
> > > >   3. Can I _please_ get a v.16+ version of Enlightenment on there? I 
> >don't
> > > > remember if that's default with RH7.
> > > >
> > > >
> > > > thanks,
> > > >         Ross
> > > >
> > > > On Wed, 14 Mar 2001, Ammon Skidmore wrote:
> > > > > I've been using vim a lot lately for coding.  It's really nice... 
> >once
> > > > > you get it configured properly.  Lately I've been configuring it 
> >like
> > > > > crazy, so I thought I'd share the results of my obsession here.  I'd 
> >like
> > > > > to hear of any other useful things you've added to your .vimrc...
> > > > >
> > > > > http://www.skidperfect.com/temp/vimrc.txt
> > > > >
> > > > > note1: syntax hilighting (syntax on) and the gui (vim -g), if I 
> >remember
> > > > > right, isn't installed on RedHat by default, and hence the CS labs.
> > > > > You'll have to compile your own (ftp.vim.org).
> > > > >
> > > > > note2: the gui font I've chosen is pretty small (good for lcd 
> >screens).
> > > > > you may want to delete that line.
> > > > >
> > > > > -Ammon
> > > > > 
> >-------------------------------------------------------------------------
> > > > >-------- To unsubscribe from the BYU UUG discussion mailist list, 
> >send
> > > > > email to [EMAIL PROTECTED] with the word 
> >"UNSUBSCRIBE" as
> > > > > the message body
> > > >
> > > > 
> >---------------------------------------------------------------------------
> > > >------ To unsubscribe from the BYU UUG discussion mailist list, send 
> >email
> > > > to [EMAIL PROTECTED] with the word "UNSUBSCRIBE" as 
> >the
> > > > message body
> > >
> > > --
> > > Mark Gulbrandsen
> > > Software Engineer
> > > [EMAIL PROTECTED]
> > > 801-491-0606
> > > ZServe Corporation
> > > LdsSingles.com -- The Premier Meeting Place
> > > 
> >---------------------------------------------------------------------------------
> > > To unsubscribe from the BYU UUG discussion mailist list, send email to
> > > [EMAIL PROTECTED] with the word "UNSUBSCRIBE" as the 
> >message body
> >
> >--
> >"Captain, I do not believe you realize the gravity of your situation"
> >         -- Spock
> >---------------------------------------------------------------------------------
> >To unsubscribe from the BYU UUG discussion mailist list, send email to
> >[EMAIL PROTECTED] with the word "UNSUBSCRIBE" as the 
> >message body
> 
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
> 
> --------------------------------------------------------------------------------- 
> To unsubscribe from the BYU UUG discussion mailist list, send email to
> [EMAIL PROTECTED] with the word "UNSUBSCRIBE" as the message body

-- 
"Captain, I do not believe you realize the gravity of your situation" 
        -- Spock 
--------------------------------------------------------------------------------- 
To unsubscribe from the BYU UUG discussion mailist list, send email to
[EMAIL PROTECTED] with the word "UNSUBSCRIBE" as the message body

Reply via email to