All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mr. Oogie Boogie" <rpreston@mitre.org>
To: mtd@infradead.org
Cc: dviro@lucidvon.com, phiggins@transzap.com
Subject: Re: Patched LILO problems
Date: Thu, 25 May 2000 15:49:29 -0400	[thread overview]
Message-ID: <392D83C9.BF8341D2@mitre.org> (raw)
In-Reply-To: 14636.60670.580939.911318@jodie.lucid

Dvir Oren wrote:
> 
> Patrick Higgins writes ("Patched LILO problems"):
> 
> > I'm using the binary patched LILO from mtd/patches/lilo-mtd.tar.gz, and it
> > doesn't seem to pass the correct command line to kernel.  The parameters I
> 
> Yes.  I noticed that the patched LILO does not in fact pass parameters
> (well, the only ones I used were root=) to the kernel.  For my purposes,
> I just rdev each kernel.
> 
> Perhaps it would be a good idea to go over the patches and see if it
> destroys something.

I had this problem as well.  This was a few months ago so my memory is
a little fuzzy.  The patch I used I downloaded from M-systems.  I
mucked around with it to try and find why the command line got mangled
and discovered that it passes the command line correctly when I booted
from a hard drive (the hd was a mirror image of the DoC) or from a
floppy with the DoC as root, so I'm pretty sure it is not the patch.

I gave up in frustration and hard coded the command line I wanted into
the kernel.  I'd like a better solution, so if you find one please let
me know.

-- 
Ralph A. Preston
The MITRE Corporation
202 Burlington Road, MS E015
Bedford, MA 01730-1420
Work: 781-271-7914  Fax: 781-271-8875  Cell: 617-257-2695


To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

      reply	other threads:[~2000-05-25 19:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-24 21:55 Patched LILO problems Patrick Higgins
2000-05-25  9:06 ` Dvir Oren
2000-05-25 19:49   ` Mr. Oogie Boogie [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=392D83C9.BF8341D2@mitre.org \
    --to=rpreston@mitre.org \
    --cc=dviro@lucidvon.com \
    --cc=mtd@infradead.org \
    --cc=phiggins@transzap.com \
    /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.