mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: hpa@zytor.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [UPDATED PATCH] Removal of boot sector code
Date: Tue, 4 Feb 2003 12:12:56 +0100 (MET)	[thread overview]
Message-ID: <200302041112.MAA02028@harpo.it.uu.se> (raw)

On 29 Jan 2003 19:12:31 -0800, H. Peter Anvin wrote:
>I have updated the boot sector removal code so that it now:
>
>a) Supports "make zdisk", "make bzdisk" and "make fdimage"
>   (Requires mtools and syslinux, but will work as a non-root user
>   as long as you have your floppy in /etc/fstab or syslinux setuid
>   root.)
>
>   There is also "make fdimage288" to create a 2.88 MB floppy image.

This works reasonably well for me, but it does require
MS-DOS fs support in the kernel, and having a /dev/fd0 entry
in /etc/fstab with "user" permissions (for some reason, "owner"
doesn't work).

I'd like to use my own recipe for "make bzdisk", to avoid these
restrictions. What about having "make bzdisk" optionally invoke
and external script, similarly to how "make install" works?

>The boot sector was very cool in 1992, but in 2003 it has outlived its
>usefulness, and it no longer supports what Linux boot loaders need,
>especially not with the 1 MB limit and the lack of support for
>non-legacy floppy devices (the geometry detection hack fails on
>those.)  Even a relatively simple 2.5 build exceeds that size for me,
>and with this patch "make bzdisk" actually works, whereas the original
>boot sector doesn't.

Indeed. Another reason is that gcc-3.2 generates (for me anyway)
much larger kernel images than gcc-2.95.3.

/Mikael

             reply	other threads:[~2003-02-04 11:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-04 11:12 Mikael Pettersson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-30  3:12 H. Peter Anvin

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=200302041112.MAA02028@harpo.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®