GNU GRUB - Bugs: bug #47980, grub2 does not support the legacy...
You are not allowed to post comments on this tracker with your current authentication level.
bug #47980: grub2 does not support the legacy command "write"
Submitter: | Elmar Stellnberger <estellnb> | ||
Submitted: | Sun 22 May 2016 04:17:34 PM UTC | ||
Category: | Booting | Severity: | Major |
Priority: | 3 - Low | Item Group: | Software Error |
Status: | None | Privacy: | Public |
Assigned to: | None | Originator Name: | Elmar Stellnberger |
Open/Closed: | Open | Release: | other |
Release: | Reproducibility: | Every Time | |
Planned Release: | 2.03+ |
Sun 22 May 2016 04:18:18 PM UTC, comment #1: |
Elmar Stellnberger <estellnb> |
Sun 22 May 2016 04:17:34 PM UTC, original submission:
Package: grub
I have tried to dd the boot image of the Ultimate Boot CD into a hard disk partition in order to boot it from there. Then I have converted the menu.lst as used by Grub1 on that CD image by grub-menulst2cfg. As it turned out most entries are no more bootable with grub2 because of the 'write' command being no more supported. As Jordan_U has told me on #grub this command would no more be supported due to security reasons.
root (hd0,17)
|
Elmar Stellnberger <estellnb> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2016-10-11 | phcoder | Priority | 5 - Normal | ![]() |
3 - Low |
Planned Release | None | ![]() |
2.03+ |
My idea about the write command is that it could serve as a
replacement for kernel parameters whenever an OS needs to be
chainloaded. That way also non-directly supported OSes like Windows or DOS or any new not yet supported ones could be customized.
The command found for fdubcd.img.gz is:
write --offset=15 /bin/setargs.bat ubcdcmd=keydisk\r\n
It simply replaces the given file for the given string at the given offset. The file itself contains sufficient spaces at the given position in order to hold for the parameter passed via write. As already said there are no additional security/safety considerations necessary as long as the file resides inside a RAM disk.