> The problem with the debian imports (ubuntu also if I'm
right), is
> that the media import cannot perform all tasks that a redhat does.
> The media is built (was at least) for device attached installs, so
> kernel+initrd are no network aware. The ones required for pxe booting
> must be downloaded separately. Some of the possible workflows were
Recent Ubuntu Server CD's (the one below is 10.04.1) come with
everything you need to netboot:
I didn't know that. It's good for ubuntu and probably also for derived
distros, but not for debian.
> And this gets more complicated as debian does not care very much
about
> the "released" vs. "updates" structure, so either you move your
> imported packages into your repository-mirror directory or you will
> download again all the media contents into your local mirror.
Can you explain exactly what this means for users?
The way I understand it.. one imports the contents of a CD, and then one
can also import packages from a repository for, say, updates. Right?
How would the debian/ubuntu way of specifying packages inhibit this?
One can feed multiple sources for an install into debian-installer with
preseed files with
d-i apt-setup/local0/repository "http://cobblerbox/ubuntu lucid main
restricted"
d-i apt-setup/local1/repository "http://cobblerbox/ubuntu lucid universe"
d-i apt-setup/local2/repository "http://cobblerbox/ubuntu lucid-updates main"
Maybe this is also a change on new ubuntu versions, but previous
versions (and current debians) do not have a lucid-updates repository.
Updated packages are "mixed" with those initially released in the same
tree.
So, when importing a media the contents must not go to an "install
tree" but to a repository. Or the repository must live wherever you
have your "install tree".
Javier Palacios