On Tue, 11 Feb 2003, Derek Vadala wrote: > On 11 Feb 2003, seth vidal wrote: > > > It's like 2 lines to edit it out and make it a variable. Go for it. > > > > How would you like to see it work? > > I think I'm planning to keep the distribution mirror, the update mirror > and my local distribution separate. That way I can integrate updates into > local mirrors as needed. In other words, I can maintain multiple versions > of the same distribution. > > > I did that b/c that's how I maintain my trees but modifying to make it > > read a config file for options would be easy - so would taking the > > option on the command line. > > Sorry if it seemed like I was complaining about the functionality. I was > merely thinking out loud. I like the idea of a config file. I need to look > at it a bit more and I'll send you some patches. I need to learn python > too. So give me a couple of days. I use this layout on my mirror: [summer@gw RedHat]$ ls 8.0 total 20 drwxr-sr-x 2 root 4096 Oct 3 17:32 Extras drwxr-xr-x 4 root 4096 Sep 25 05:50 ISO drwxr-sr-x 6 root 4096 Oct 3 12:45 dist drwxr-sr-x 4 cc 4096 Oct 9 11:28 ks drwxr-sr-x 8 root 4096 Oct 8 04:06 updates [summer@gw RedHat]$ It's accessible from my client installs. It was working well for NFS, I've switched to using HTTP more recently, but I've done lest testing in that context. If I make an updated tree, its release number gets a letter (u for updated). Extras contains additional packages I want to install. ks contains kickstart files. dist contains the contents of the ISOs, created as per the instructions on the CD. updates is a mirror of the relevant RHL updates tree. I have an Apache virtualhost configured for the area, pointing at /var/ftp/pub/ which is also my nfs export (ro). When I create an updated tree, I prefer to do it on another machine to ensure I don't clobber anything important. -- Please, reply only to the list.
