Bug#263178: update(install does not modify boot_dev and boot_osflags)
On Thu, Aug 05, 2004 at 01:38:03PM -0700, Steve Langasek wrote:
> > > According to my somewhat limited research, an interface to the SRM would
> > > be available if CONFIG_SRM_ENV was set to "y" during kernel build.
> > > Unfortunately, this is not the default :-(
> > OK, this seems to be fixed now (= boot.img as of Aug 4, 5423316 bytes),
> > I can see /proc/srm_environment while the base installation is going on.
> There have been no changes recently to the SRM support in the alpha
> kernels; I don't know why it failed before for you, but it wasn't due to
> missing kernel support.
Oops, so perhaps I only looked at the installed kernel before (which
does not have SRM support enabled) ...
> There's no modification visible because no modification is being done.
> No code has been written to attempt to change the SRM boot variables
> from debian-installer; and you shouldn't expect this to be done for
> sarge. While having the installer ensure you end up back in Debian
> after a reboot sounds like a good idea, the task of mapping Unix devices
> to SRM names is really quite difficult, and not something to be
> attempted this soon before a release.
OK, I accept this. Feel free to lower the priority of this bug report...