vyatta-cfg-system.git/scripts/grub-setup, branch hollywoodVyatta system-level configuration templates/scripts (mirror of https://github.com/vyos/vyatta-cfg-system.git)
https://git.amelek.net/vyos/vyatta-cfg-system.git/atom?h=hollywood2008-08-14T02:06:36+00:00Bugfix: 12922008-08-14T02:06:36+00:00Bob Gilligangilligan@vyatta.com2008-08-14T02:06:36+00:00urn:sha1:629acfb44e5fccb18a19092034913eddf6cc1c1c
Disable logo per instructions from Anatoly.
Bugfix: 12922008-08-11T21:24:02+00:00Bob Gilligangilligan@vyatta.com2008-08-11T21:24:02+00:00urn:sha1:883737f620c6e0e95b1f92d2e24e9375efb20910
Re-enable the Vyatta logo on boot.
More spaces (bugs http://bugzilla.vyatta.com/show_bug.cgi?id=3549 and http://bugzilla.vyatta.com/show_bug.cgi?id=3552)2008-08-08T01:27:18+00:00rbaloccarbalocca@vyatta.com2008-08-08T01:27:18+00:00urn:sha1:dc94c5c8e77817df8908c2b6aad08d70b1e142d3Fixes for bugs: http://bugzilla.vyatta.com/show_bug.cgi?id=3549 and http://bugzilla.vyatta.com/show_bug.cgi?id=35522008-08-08T01:18:12+00:00rbaloccarbalocca@vyatta.com2008-08-08T01:18:12+00:00urn:sha1:d2da6d1177bb0cb1922c2f2b73b8a4f557cece28
This fix involves removing multiple spaces between args on the kernel command line.
This fixes the symptom, but the root cause is an uninitialized variable in the grub-pc code,
so there is absolutely no guarrantee that this problem will not arrise again. The correct fix
is either to return to grub (V1) or to have the developers find and fix the unitialized memory.
Fix for http://bugzilla.vyatta.com/show_bug.cgi?id=35202008-08-06T22:29:06+00:00Rick Baloccarbalocca@vyatta.com2008-08-06T22:29:06+00:00urn:sha1:fe3d0a401c90030ffdbf0b9e6d3db9dc2543c304