[Server-devel] mkusbinstall enhancements
Jerry Vonau
jvonau at shaw.ca
Tue Feb 24 21:42:17 EST 2009
On Wed, 2009-02-25 at 14:47 +1300, Martin Langhoff wrote:
> On Mon, Feb 23, 2009 at 8:27 AM, Jerry Vonau <jvonau at shaw.ca> wrote:
> > Wow, did I have a fun night for once, sorry for the delay in replying.
>
> :-)
>
> > That should of read --baseurl=file:///mnt/isodir/updates
>
> I am a bit lost -- you do run a bit too fast. Or maybe erlang cooked
> my noodle...
>
Anaconda by default mounts the usb key at /mnt/isodir, I've just made
another repo available on the usb in /updates. In order to enable this
repo you need to add the repo line to the ks.cfg file
> > I've uploaded a XSupdates.zip to http://members.shaw.ca/jvonau/pub/0216/
> > Just unpack the zip to your usbdrive and add the line in sample.ks to
> > the top of the present ks.cfg file on the usbdrive. The installer should
> > add the repo into its repo setup routine and be available for the
> > install.
>
> Will review. How did you prepare the files? What's the magic?
>
I just ran "createrepo ." in the directory, and zipped it up. Could be
used to add local content.
> > This look like it maybe useful to rollout incremental changes to the
> > base rpms, instead of installing, then "yum updating" we could packages
> > up the newer rpm files for use with this "updates repo" and have them
> > installed from the get go. We could add a createrepo routine to
> > mkusbinstall to create a blank repo in updates off the bat and leave the
> > repo line in the ks.cfg file, should have no ill effects if there is
> > nothing present in the repo.
>
> Sounds evil. How about people who burn the iso? Or a deployment that
> drives anaconda-over-nfs or similar? If we make mkusbinstall really
> smart, we leave behind everyone who isn't using usb ;-)
>
> cheers,
>
This is for usb ATM... To add file to an iso, mkslim could do that,
while a change to the repo line would be needed(I'd need to work up the
syntax). NSF would be a snap, uses the same logic as harddrive to fine
an iso. I'd just add the /updates to the root of the export, might just
work with out changing the repo line, but I would have to mock that up
to be sure.
Sorry got to leave for work, back in 12 hours
Jerry
More information about the Server-devel
mailing list