linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: problems booting 2.5 kernel, rh9
Date: 17 Apr 2003 13:59:11 -0700	[thread overview]
Message-ID: <b7n4iv$dub$1@cesium.transmeta.com> (raw)
In-Reply-To: 20030417111714.GA16335@wind.cocodriloo.com

Followup to:  <20030417111714.GA16335@wind.cocodriloo.com>
By author:    Antonio Vargas <wind@cocodriloo.com>
In newsgroup: linux.dev.kernel
> 
> Dave, since your ISP is blocking my mail, I reply on lkml...
> 
> I booted fine the 2.5 kernel by tagging it for netboot and
> then placing it on my tftp directory. I never use harddisk
> bootloaders, so if you can not make it work with grub,
> I would get ahead and make it boot from floppy. Yes, it
> takes a minute to load a kernel, but it works and is simple.
> 
> I use syslinux for that, it's fairly simple and you can
> enter kernel options directly at the boot prompt.
> 
> Also, since it's a dos 8.3-formatted floppy, you can upgrade
> your kernel by simply replacing the kernel file.
> 
> If you need a dos-formatted empty disk, I can post one to my
> homepage for you to download.
> 

Especially on recent 2.5, you can just "make bzdisk" and have it make
a syslinux floppy.  make bzdisk FDARGS='blah' lets you set the default
options right on the fly.  You need syslinux 2.02 or later (and, of
course, write permission to the floppy drive) if you want to do this
as non-root.

	-hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64

      reply	other threads:[~2003-04-17 20:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-17  3:01 problems booting 2.5 kernel, rh9 Dave Mehler
2003-04-17 11:17 ` Antonio Vargas
2003-04-17 20:59   ` H. Peter Anvin [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='b7n4iv$dub$1@cesium.transmeta.com' \
    --to=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;
as well as URLs for NNTP newsgroup(s).