Bug#298240: grub: Include DebBlue splash screen
Luis R. Rodriguez
mcgrof@ruslug.rutgers.edu (Luis R. Rodriguez), 298240@bugs.debian.org
Mon, 7 Mar 2005 17:38:31 -0500
--8aUgEFSDYDA6u3T0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Mar 08, 2005 at 09:18:51AM +1100, Jason Thomas wrote:
> Because the splashimages may not work for everyone and could leave them
> with an unbootable system. But, most things you do to the boot
> sector/record could leave your system in an unbootable state.
>=20
> So, If you think that the splashimage code is reliable enough go for it.
>=20
> Have we fixed it yet so that it will not just load random data from the
> drive, if its pointed at a non-existant file?
I am not sure, we'll have to test and verify through the splashimage
patch we use. We could also just wait until the first release=20
of grub 1 (?) -- I believe one objective was to get a graphical boot=20
loader so it may be easier if it's maintained upstream. There also
seems little point to push something like this since this already missed the
sarge release.
Luis
--=20
GnuPG Key fingerprint =3D 113F B290 C6D2 0251 4D84 A34A 6ADD 4937 E20A 525E
--8aUgEFSDYDA6u3T0
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFCLNfnat1JN+IKUl4RAlopAKCBVhQ0sbwtiFbiUngYV44CNhzANgCfVcUS
Mqim5vwba/ntoZdmRNIkPy4=
=qBSS
-----END PGP SIGNATURE-----
--8aUgEFSDYDA6u3T0--