From: Christian Franke <Christian.Franke@t-online.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] grub2 for Cygwin
Date: Sat, 05 Apr 2008 14:44:08 +0200 [thread overview]
Message-ID: <47F77418.2020906@t-online.de> (raw)
In-Reply-To: <1207255136.2447.14.camel@dv>
Pavel Roskin wrote:
> On Thu, 2008-04-03 at 21:56 +0200, Christian Franke wrote:
>
>
>> OK, if there is no chance to get this accepted, grub2 project managers
>> should tell me soon.
>>
>
> I'm not a project manager, but I would hate to see useful code
> discarded.
>
:-)
> I think the ability to install GRUB from Windows would allow creating
> installers for Windows that install a free OS without reboots and would
> not rely on booting from any media other than the hard drive. I think a
> non-Cygwin port would be preferred for that, but Cygwin could be a
> useful stepping stone, a testbed and the build environment for the
> native port.
>
>
Yes, it actually is. I also use cygwin to build the non-Cygwin packages
for my other Windows ports (smartmontools, hdparm).
Cygwin's "kernel" is essentially a dll which emulates a Linux/POSIX API.
The GRUB2 cygwin binaries need only the following files to run OOTB from
Windows cmd.exe:
cygwin1.dll
cyglzo2-2.dll
cygncurses-8.dll (grub-emu only)
terminfo/c/cygwin (grub-emu only)
The shell scripts would require additional files from bash and
coreutils, of course.
> ...
> Maybe we could start with simple changes that don't make the code
> significantly more complex?
>
OK, then I would suggest to (re)start with the small change for
grub-mkdevicemap.
http://lists.gnu.org/archive/html/grub-devel/2007-12/msg00179.html
The patch is still current and already got positive feedback from Marco
and Robert.
I can also repost it, if desired.
> I think it would be nice to have a universal infrastructure for all
> platforms that would use linker scripts instead of strip and objcopy on
> all platforms.
>
objcopy has to be used if the native object format on a platform is not
(the) ELF (variant the grub loader expects).
Unfortunately, libbfd is apparently not designed to support conversion
of relocation info.
> Perhaps you could clone git://repo.or.cz/grub2.git and keep the patches
> in your local copy?
OK, added this as remote to my repo.
> The great thing about git is that it relieves the
> urgency of merges, as the changes can be held as separate patches and
> rebased to the current tree as needed.
>
>
BTW: Thanks to the clean upstream changes, merging from CVS was never a
problem since I started the Cygwin port in oct 2007.
>> The cygwin port of grub2 is targeted to users who want a *n[iu]x
>> environment, but (have to) use Windows as main work OS for whatever
>> reason. They likely have already installed cygwin :-)
>>
>
> Why would they benefit from GRUB? Just wondering.
>
>
The ability to maintain the boot manger and create rescue discs from
Cygwin shell without reboot is useful.
(There were some requests for a Cygwin release in the past, e.g:
http://savannah.gnu.org/bugs/?20497)
Christian
next prev parent reply other threads:[~2008-04-05 12:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 13:28 [PATCH] grub2 for Cygwin Christian Franke
2008-04-03 16:02 ` Bean
2008-04-03 19:56 ` Christian Franke
2008-04-03 20:38 ` Pavel Roskin
2008-04-05 12:44 ` Christian Franke [this message]
2008-04-07 2:07 ` Pavel Roskin
2008-04-07 19:46 ` Christian Franke
2008-04-13 10:37 ` Robert Millan
2008-04-13 10:39 ` Robert Millan
2008-04-13 20:24 ` Christian Franke
2008-04-14 12:00 ` Robert Millan
2008-04-14 13:36 ` Christian Franke
2008-04-15 13:12 ` Robert Millan
2008-04-15 14:26 ` Christian Franke
-- strict thread matches above, loose matches on Subject: below --
2007-10-16 12:03 Christian Franke
2007-10-16 13:34 ` Robert Millan
2007-10-20 23:37 ` Robert Millan
2007-10-21 13:07 ` Christian Franke
2007-10-21 13:18 ` Vesa Jääskeläinen
2007-10-21 13:51 ` Christian Franke
2007-10-21 14:13 ` Robert Millan
2007-11-09 13:57 ` Marco Gerards
2007-11-09 15:07 ` Christian Franke
2008-04-02 22:07 ` Christian Franke
2008-04-03 8:03 ` Bean
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47F77418.2020906@t-online.de \
--to=christian.franke@t-online.de \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.