The article mentions the method to deploy APT-MIRROR so that you can use a local repository in your intranet insted going to internet again.
\nI will use the local repository IP to 192.100.100.40<\/p>\n
Packages required:–
\n1.Apt-Mirror
\n2.Apache Webserver (to distribute to whole intranet)
\nSteps :—<\/p>\n
1.Setting up the apt-mirror<\/p>\n
\r\n$sudo apt-get install apt-mirror\r\n$sudo nano \/etc\/apt\/apt-mirror <---- (the configuration file of apt-cache)\r\n\r\n---------------------------XXXXXXXXXXXXXXXXX--------------------\r\n############# config ##################\r\n#\r\n#set base_path \/var\/spool\/apt-mirror\r\n# if you change the base path you must create the directories below with\r\nwrite privileges\r\n#\r\n# set mirror_path $base_path\/mirror\r\n# set skel_path $base_path\/skel\r\n# set var_path $base_path\/var\r\n# set cleanscript $var_path\/clean.sh\r\nset defaultarch \r\nset nthreads 20\r\nset _tilde 0\r\n#\r\n############# end config ##############\r\ndeb-i386 http:\/\/archive.ubuntu.com\/ubuntu jaunty main restricted\r\nuniverse multiverse\r\ndeb-i386 http:\/\/archive.ubuntu.com\/ubuntu jaunty-updates main restricted\r\nuniverse multiverse\r\ndeb-i386 http:\/\/archive.ubuntu.com\/ubuntu jaunty-backports main\r\nrestricted universe multiverse\r\ndeb-i386 http:\/\/archive.ubuntu.com\/ubuntu jaunty-security main\r\nrestricted universe multiverse\r\ndeb-i386 http:\/\/archive.ubuntu.com\/ubuntu jaunty-proposed main\r\nrestricted universe multiverse\r\nclean http:\/\/archive.ubuntu.com\/ubuntu\r\n-------------------------XXXXXXXXXXXXX----------------------------------------\r\n<\/pre>\nI am creating local repo for Jaunty you can replace it with karmic or hardy incase you want a repo of that Disros. In above configuration file what i have done is my source file for
\ndownloading whole package is \/var\/spool\/apt-mirror. I wanted the repository for the 32 bit system so i mentioned deb-i386. You can replace\/add deb-amd64 if you want only 32 bit repo or incase
\nyou want repo for both architecture.<\/p>\n
2.Dumping the packages in local repository.<\/p>\n
\r\n$sudo apt-mirror\r\n\r\nYou will see something like this on your screen\/terminal\r\n-------------------------XXXXXXXXX---------------------------------------------\r\nt143@t143-desktop:\/var\/log$ sudo apt-mirror\r\nDownloading 90 index files using 20 threads...\r\nBegin time: Thu Feb 11 16:32:14 2010\r\n[20]... [19]... [18]... [17]... [16]... [15]... [14]... [13]... [12]...\r\n[11]... [10]... [9]... [8]... [7]... [6]... [5]... [4]... [3]... [2]...\r\n[1]... [0]...\r\nEnd time: Thu Feb 11 16:32:18 2010\r\nProceed indexes: [PPPPPP]\r\n28.0 GiB will be downloaded into archive.\r\nDownloading 29319 archive files using 20 threads...\r\nBegin time: Thu Feb 11 16:32:26 2010\r\n[20]...\r\n--------------------------XXXXXXXXXX--------------------------------\r\n<\/pre>\nThis will take some time as 30 GB downloading takes sometime<\/p>\n
3.Clean Up The Local Repo<\/p>\n
\r\nt143@t143-desktop:$ sudo \/bin\/bash \/var\/spool\/apt-mirror\/var\/clean.sh\r\nRemoving 157 unnecessary files [13316096 bytes]...\r\n[0%]................done.\r\nRemoving 18 unnecessary directories...\r\n[0%]..................done.\r\n\r\n3.Mirroring it for the intranet\r\nIn case you don not have apache installed\r\n\r\n$sudo apt-get install apache2\r\n<\/pre>\n4.Create A Daily Cron Job<\/p>\n
\r\nt143@t143-desktop:\/var\/log$ \/etc\/cron.d\/apt-mirror\r\n\r\n#\r\n# Regular cron jobs for the apt-mirror package\r\n#\r\n0 4 * * * apt-mirror \/usr\/bin\/apt-mirror >\r\n\/var\/spool\/apt-mirror\/var\/cron.log\r\n<\/pre>\nThis will make apt-mirror run at 4.00 each day, and it will log to
\n\/var\/spool\/apt-mirror\/var\/cron.log.<\/p>\n
5. Local Mirrors Accessible Over HTTP<\/p>\n
Once apache installed and running<\/p>\n
\r\n$cd \/var\/www\r\n$sudo ln -s \/var\/spool\/apt-mirror ubuntu\r\nNow my repo address over intranet will become :--\r\ndeb http:\/\/192.100.100.40\/ubuntu jaunty main restricted universe\r\nmultiverse\r\ndeb http:\/\/192.100.100.40\/ubuntu jaunty-updates main restricted universe\r\nmultiverse\r\ndeb http:\/\/192.100.100.40\/ubuntu jaunty-backports main restricted\r\nuniverse multiverse\r\ndeb http:\/\/192.100.100.40\/ubuntu jaunty-security main restricted\r\nuniverse multiverse\r\ndeb http:\/\/192.100.100.40\/ubuntu jaunty-proposed main restricted\r\nuniverse multiverse\r\n6.Testing our local repository\r\nlets add this to one of the host computer on intranet\r\n$sudo nano \/etc\/apt\/sources.list\r\nLets add our local repo address inside it\r\n\r\ndeb http:\/\/192.100.100.40\/ubuntu jaunty main restricted universe\r\nmultiverse\r\ndeb http:\/\/192.100.100.40\/ubuntu jaunty-updates main restricted universe\r\nmultiverse\r\ndeb http:\/\/192.100.100.40\/ubuntu jaunty-backports main restricted\r\nuniverse multiverse\r\ndeb http:\/\/192.100.100.40\/ubuntu jaunty-security main restricted\r\nuniverse multiverse\r\ndeb http:\/\/192.100.100.40\/ubuntu jaunty-proposed main restricted\r\nuniverse multiverse\r\n\r\n<\/pre>\n$sudo apt-get update
\nhere we go we have all the packages coming from our local repository.
\ncheers!!!<\/p>\n","protected":false},"excerpt":{"rendered":"
The article mentions the method to deploy APT-MIRROR so that you can use a local repository in your intranet insted going to internet again. I will use the local repository IP to 192.100.100.40 Packages required:– 1.Apt-Mirror 2.Apache Webserver (to distribute to whole intranet) Steps :— 1.Setting up the apt-mirror $sudo apt-get install apt-mirror $sudo nano … <\/p>\n