Re: how to remote update 4.10 -> 5.3?

From: Brooks Davis (brooks_at_one-eyed-alien.net)
Date: 12/29/04

  • Next message: Palle Girgensohn: "Re: how to remote update 4.10 -> 5.3?"
    Date: Wed, 29 Dec 2004 13:01:10 -0800
    To: Palle Girgensohn <girgen@pingpong.net>
    
    
    

    On Wed, Dec 29, 2004 at 09:49:10PM +0100, Palle Girgensohn wrote:
    >
    >
    > --On onsdag, december 29, 2004 12.36.01 -0800 Brooks Davis
    > <brooks@one-eyed-alien.net> wrote:
    >
    > >On Wed, Dec 29, 2004 at 09:30:37PM +0100, Palle Girgensohn wrote:
    > >>Has anyone managed to update a 4.10 system to 5.3 remotely, i.e. without
    > >>console access, and without spare disk partitions?
    > >>
    > >>I have a bunch of 4.10 machines that are too far away for me to actually
    > >>do the update hands on. I've tried it on a test machine, it fails half
    > >>way through installworld, and really needs single user mode to succeed.
    > >>The install procedure fails since it starts using the newly installed
    > >>stuff, things like sh(1) and test(1), and they cannot find their
    > >>libc.so.5, I guess...
    > >>
    > >>One idea I have is copying / and /usr to some other place and set
    > >>ldconfig and PATH=some/other/place and when building and installing.
    > >>Haven't tried it yet, thought I'd hear anyone on this list has a better
    > >>suggestion?
    > >>
    > >>Optimally, there would a couple of gigs on a separate spare disk
    > >>partition so I could just install everything there and use it upon
    > >>reboot. Problem is, there is no such space. :(
    > >
    > >In general, my suggestion would be, don't do that. Do you really need
    > >to upgrade? Remember, 4.11 is likely to be supported for security
    > >upgrades into early 2006 so if your machines are working and you don't
    > >really need the new functionality, I'd suggest avoiding an upgrade.
    >
    > Well, I need wide char support, as in iswlower and the likes. Maybe I could
    > use some portability lib or similar...? Ideas?
    >
    > BTW, do you mean that 5.3 is not stable enough, or just that it is a
    > nuisance to upgrade? While I agree that 4.10 is very stable, a lot of
    > things have improved with 5.x...

    If you need the improved wide char support, then you will probably have
    to upgrade. 5.3 is generally stable, but I personally think upgrading
    for 4.x by any method other then a new install is a bad idea. It's
    certaintly possiable, but not trivial. I believe the instructions in
    UPDATING should work, but I've never tried them remotely.

    -- Brooks

    -- 
    Any statement of the form "X is the one, true Y" is FALSE.
    PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4
    
    



  • Next message: Palle Girgensohn: "Re: how to remote update 4.10 -> 5.3?"

    Relevant Pages

    • Re: how to remote update 4.10 -> 5.3?
      ... >> Well, I need wide char support, as in iswlower and the likes. ... >> nuisance to upgrade? ... > for 4.x by any method other then a new install is a bad idea. ... I've tried the UPDATING instructions, both locally and remotely (the latter ...
      (freebsd-stable)
    • Re: MS Project 2003 Demo
      ... upgrade path for P3 users who have current ... P3e/c is one if those newer Primavera developments, ... make a decision based on the functionality of each. ... >> download. ...
      (microsoft.public.project)
    • Re: **Urgent** New Edit in Datasheet error occurring on proven WSS
      ... We have over 1200 users so our upgrade plans for Office 2007 are not in the ... near future since the user experience will change quite extensively, ... the functionality I decided to attempt some client-based fixes. ... We ended up doing a repair of the WSS2 installation and then an ...
      (microsoft.public.sharepoint.windowsservices)
    • Re: NEWSGROUPS ?
      ... This is where we want to go with this, and you are going to have to upgrade whether you like it or not. ... The only real functionality improvement I can discern is the ability to choose to top or bottom post, and the safety options I guess. ... I'd wager that the number of customers MS has using the NNTP functionality of Exchange was low enough that there isn't that much of an outcry that it is going away. ... But, with PFs going away, the question of how NNTP could be handled without PFs was probably suitably complex that they weren't too concerned there either. ...
      (microsoft.public.outlook)
    • Re: Windows 2000 Mixed to Win2003. What to Expect?
      ... from the upgrade of 3 separate NT4 domains. ... All domains are running in Windows 2000 Mixed mode as a result of the NT4 upgrade, but all domain controllers in all domains are now running Win2003 servers, all Exchange servers have been upgraded to Exchange 2003. ... There are no Win2000 or NT4 domain controllers left on the network and no expectations to need this functionality either. ...
      (microsoft.public.windows.server.active_directory)