[NTLUG:Discuss] NTLUG:Discuss] Re: Creating an APT-GET Mirror

Dennis dearroz at comcast.net
Tue Oct 26 10:46:37 CDT 2004


Bryan J. Smith wrote:

Subject: [NTLUG:Discuss] Re: Creating an APT-GET Mirror
From:
"Bryan J. Smith" <b.j.smith at ieee.org>
Date:
Mon, 25 Oct 2004 12:36:14 -0400
To:
saj at thecommune.net, NTLUG Discussion List <discuss at ntlug.org>

On Mon, 2004-10-25 at 11:42, Stuart Johnston wrote:

 >> You might also look at http://apt-proxy.sourceforge.net/.  Rather than
 >> downloading an entire mirror, apt-proxy will simply download and cache
 >> packages as they are requested.  I've never actually used it myself 
but it
 >> sounds like it will work for RPM distros.


APT is APT, YUM is YUM.  The package back-end doesn't matter except when
it comes to the end-system actually resolving dependencies, fetching and
installing the packages.  I assume such a "proxy" wouldn't need to
understand dependency resolution, which is done at the end-system.

This is a nice option for performance on a network.  I've used it for
both Debian and Fedora based systems.

I assume (and I may be wrong), however, Dennis is more interested in
students creating their own, local APT repositories as a tool for
controlling system releases.  But then again, it's really little more
than a matter of running a gen script.

-- Bryan

-- Bryan J. Smith b.j.smith at ieee.org

================================
To add a little clarification, I have the students presently install RH 
7.2 full install - only because a full install takes about 1 hour.  Full 
installation of RH 9 or Fedora requires in excess of 3 hours - way to 
long for class installation.  The hopeful intent is for the class to do 
a minimum installation of Fedora, then apt-get (yum) any other (server) 
applications required for the course.  Thus the install time would be 
minimum, realistic updating of a server using apt-get (yum) .  One of my 
objectives is to have the students learn that Linux serves as a server, 
one has an alternative to MS.

Dennis
dearroz at comcast.net





More information about the Discuss mailing list