Re: Creating a local RPM repository



On Fri, 2009-11-06 at 09:21 -0800, Mike Smith wrote:
I am currently reviewing the possibility of allowing some of our
employees to use Fedora on their machines instead of Windows. On of
my concerns is the bandwidth tied up by multiple machines downloading
the same RPMs through our Internet gateway. Is there a way to set up
a local RPM repository on our internal networks so that the RPMs only
have to be downloaded from the main repositories once. All of our
user machines would be configured to look at the local repository
instead of the main one.

Yes, and if you googled your subject line, you'd probably have found the
answer. Or you could try googling create local yum repo.

I don't recall the answer for creating the repo, else I'd say it here.
But it's not hard to find. It comes up often enough.

Another option is to simply use a caching proxy (e.g. Squid) between you
and one mirror, and set the clients to all use the same mirror (through
your proxy). When one client fetches a package, it's cached, the next
client will use the cached copy. Squid will take care of expunging old
cached content, itself (there's file age, and amount of bytes filling
the cache, that it considers). You don't have to set up one machine to
be a yum mirror, they're all just clients.

It's a marvellous way to stop Windows update from wasting your
bandwidth, too (if you're going to keep some of those Windows boxes
still working).

--
[tim@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686

Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.



--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines



Relevant Pages

  • Re: "Do not have access to logon to this session"
    ... different machines and ended up with the same results. ... EventLog on these clients? ... Windows XP, Windows 2000, and Windows NT ... home to Remote Desktop on their Windows XP Pro SP2 machines here ...
    (microsoft.public.windows.terminal_services)
  • RE: Windows XP Fax Printing
    ... I understand that three of five Windows XP clients cannot send fax through ... Make sure the Fax service is started in your Windows XP computer. ... Microsoft CSS Online Newsgroup Support ... On 1 of the machines, I uninstalled and re-installed the Fax Services ...
    (microsoft.public.windows.server.sbs)
  • Re: "Do not have access to logon to this session"
    ... EventLog on these clients? ... Windows XP, Windows 2000, and Windows NT ... something over 100 client machines as members. ... home to Remote Desktop on their Windows XP Pro SP2 machines here ...
    (microsoft.public.windows.terminal_services)
  • Re: Sharing with workgroup
    ... Your clients should be able to get to [tmp]. ... There is a slight change in the way the Windows machines fail to connect..... ... the Windows clients can't access the tmp directory. ...
    (linux.redhat)
  • Re: Microfocus COBOL 3.2.43 (16bit)
    ... Given that they probably have Windows PCs everywhere they need them, ... sufficient new central machines with VMs may be just additional cost. ... I used Mac's back then for clients in the publishing industry who ... as the speed of the connection and utilization and b) is not ...
    (comp.lang.cobol)