All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC PATCH] Sector 2 of non-embedded core.img: write early or patch later?
Date: Sun, 29 Jun 2008 23:10:15 +0200	[thread overview]
Message-ID: <20080629211015.GC24784@thorin> (raw)
In-Reply-To: <4867C9FC.7000903@nic.fi>

On Sun, Jun 29, 2008 at 08:44:28PM +0300, Vesa Jääskeläinen wrote:
> Robert Millan wrote:
> >On Sun, Jun 29, 2008 at 04:23:24PM +0300, Vesa Jääskeläinen wrote:
> >>This also relates to problem with installing to MBR and there is no room 
> >>for embedding core.img there. I have been using USB stick where there is 
> >>not enough room for core.img what I want to store there. So only option 
> >>is to leave core.img to filesystem and install MBR.
> >
> >But then you can add an empty partition (type 0x00) starting at sector 63,
> >and grub-setup will overwrite it.
> >
> >Or you could leave that region unpartitioned.
> 
> At least on my disks there is 32 KiB free space.

Typically they're 32 kiB - 512 B (because most tools reserve that space
for some legacy restriction that no longer exists ;-)).

> But not ~50 KiB what my 
> core.img requires.

What do you put in your core?

-- 
Robert Millan

<GPLv2> I know my rights; I want my phone call!
<DRM> What good is a phone call… if you are unable to speak?
(as seen on /.)



      reply	other threads:[~2008-06-29 21:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27 21:24 [RFC PATCH] Sector 2 of non-embedded core.img: write early or patch later? Pavel Roskin
2008-06-28  4:46 ` Bean
2008-06-28  4:58 ` Bean
2008-06-30 22:43   ` Pavel Roskin
2008-06-28  9:09 ` Vesa Jääskeläinen
2008-06-29 11:29 ` Robert Millan
2008-06-29 13:23   ` Vesa Jääskeläinen
2008-06-29 17:38     ` Robert Millan
2008-06-29 17:44       ` Vesa Jääskeläinen
2008-06-29 21:10         ` Robert Millan [this message]

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=20080629211015.GC24784@thorin \
    --to=rmh@aybabtu.com \
    --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.