This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
To: psyche-list@listman.redhat.com From: John Nall <jnall01@alltel.net> Subject: Transferring updates across local network Date: Sun Feb 16 17:42:16 2003 This may be a dumb question, with the answer glaringly obvious. But I hate to make assumptions. Doing so has bit me in the past. Using RHN I have updated one of my three RH8.0 systems. All three of them are on a LAN, at my home. Since this updating is kind of a courtesy from Redhat, by virtue of my buying RH8.0 from them, I can only update one machine with RHN (or so I gather). So one machine is updated. The other two are not. It would seem logical to me that I should be able to then update the other two machines on the LAN then, by merely copying the files. Is that true? Or am I being overly naive/trusting/innocent??? Anyone done it? === To: psyche-list@listman.redhat.com From: Tony Nugent <tony@linuxworks.com.au> Subject: Re: Transferring updates across local network Date: Mon, 17 Feb 2003 12:53:45 +1000 On Sun Feb 16 2003 at 20:41, John Nall wrote: > Using RHN I have updated one of my three RH8.0 systems. All three of them > are on a LAN, at my home. Since this updating is kind of a courtesy from > Redhat, by virtue of my buying RH8.0 from them, I can only update one > machine with RHN (or so I gather). So one machine is updated. The other > two are not. It would seem logical to me that I should be able to then > update the other two machines on the LAN then, by merely copying the files. > > Is that true? Or am I being overly naive/trusting/innocent??? Anyone done it? Go to http://freshrpms.net/ and look at apt for rpm (and synaptic). === To: psyche-list@listman.redhat.com From: Charles <charlesnjohnson@tds.net> Subject: Re: Transferring updates across local network Date: Sun, 16 Feb 2003 21:02:17 -0600 John Nall wrote: > This may be a dumb question, with the answer glaringly obvious. But I > hate to make assumptions. Doing so has bit me in the past. > > Using RHN I have updated one of my three RH8.0 systems. All three of > them are on a LAN, at my home. Since this updating is kind of a > courtesy from Redhat, by virtue of my buying RH8.0 from them, I can only > update one machine with RHN (or so I gather). So one machine is > updated. The other two are not. It would seem logical to me that I > should be able to then update the other two machines on the LAN then, by > merely copying the files. > > Is that true? Or am I being overly naive/trusting/innocent??? Anyone > done it? > Do a man up2date, and you will see that one of the options is to leave the RPM on your system after they have been used. Then, copy them to the un-updated system and do the update. === To: psyche-list@listman.redhat.com From: Doug Brucks <brucks@felpsis.net> Subject: Re: Transferring updates across local network Date: Sun, 16 Feb 2003 21:20:39 -0600 At 08:41 PM 2/16/2003 -0500, you wrote: >This may be a dumb question, with the answer glaringly obvious. But I >hate to make assumptions. Doing so has bit me in the past. > >Using RHN I have updated one of my three RH8.0 systems. All three of them >are on a LAN, at my home. Since this updating is kind of a courtesy from >Redhat, by virtue of my buying RH8.0 from them, I can only update one >machine with RHN (or so I gather). So one machine is updated. The other >two are not. It would seem logical to me that I should be able to then >update the other two machines on the LAN then, by merely copying the files. > >Is that true? Or am I being overly naive/trusting/innocent??? Anyone >done it? I am sure there are other methods of updating over a lan, but this works for me. I am making the assumption that all 3 have internet access. I also do not run the rhnsd. I update by running up2date. You need to register all 3 machines with RHN. Not to worry... registration is free. I have 3 machines registered right now under one account, using different machine descriptions so I can tell which is which. Two of them run on separate partitions on one box (one for test and one for everyday use) and one is at work.The thing is, only 1 can be active at a time. When you want to update a machine, login to RHN and make that machine active. Then run up2date on the active machine. To save bandwidth and time, I make sure I configure up2date to save the update downloads. I think the default dir for the downloads is /var/spool/up2date. I have changed the default to a directory mounted to a shared partition on my home box so both installs can use them without having to copy the files. For work, I burn a CD and then copy the files from it to the default directory. When up2date connects, you tell it what to update. If the files are where up2date expects to see them, it will skip the download part. I even burn an update CD for a friend of mine so he doesn't have to download the updates over his dialup connection. Since his install is a little different from mine, he still has to download an update from time to time. Just a side note. I have recently paid for basic service. Although I could keep up2date for free, I wanted to give at least some support to my distro of choice. === To: psyche-list@listman.redhat.com From: Ed Wilts <ewilts@ewilts.org> Subject: Re: Transferring updates across local network Date: Sun, 16 Feb 2003 21:21:32 -0600 On Sun, Feb 16, 2003 at 08:41:10PM -0500, John Nall wrote: > This may be a dumb question, with the answer glaringly obvious. But I hate > to make assumptions. Doing so has bit me in the past. > > Using RHN I have updated one of my three RH8.0 systems. All three of them > are on a LAN, at my home. Since this updating is kind of a courtesy from > Redhat, by virtue of my buying RH8.0 from them, I can only update one > machine with RHN (or so I gather). So one machine is updated. The other > two are not. It would seem logical to me that I should be able to then > update the other two machines on the LAN then, by merely copying the files. You've got a few choices: 1. Buy subscriptions to RHN for all systems. 2. If all 3 are identically configured, you can run up2date on one system and tell it to keep the rpms after they've been downloaded (the default is to delete). Once the first system is done, you can then freshen your other systems from those rpms. 3. Use one of the many open source tools that try to emulate up2date. 4. Grab the files directly from a Red Hat ftp mirror and freshen your system the old fashion way. FWIW, I've got my home system subscribed to RHN (I've paid). The $60/year is really a bargain for the piece of mind to get all updates promptly, full ISOs if I need them on a high-priority basis, and new versions of the OS during the year. That, and Red Hat gets *all* the money, unlike what would happen if I went to a local store to buy the latest version twice per year. ===