Linux Newbie help
 help / color / mirror / Atom feed
From: Michael Gruner <stockraser@yahoo.de>
To: Ray Olszewski <ray@comarre.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: self-made potato driver-1.bin
Date: 26 Aug 2002 14:09:42 +0200	[thread overview]
Message-ID: <1030363455.928.35.camel@highflyer> (raw)
In-Reply-To: <5.1.0.14.1.20020825152156.0225d270@celine>

Am Mon, 2002-08-26 um 00.40 schrieb Ray Olszewski:
> First, why not try installing Woody? Potato is no longer Debian-stable; 
> Woody is, as of about a month ago. Its installer may be new enough to solve 
> your problem.
I downloaded the woody install-disks and will give that a try. I use
potato because I have potato cds here and a 56k modem line without a
flatrate :-/

> Third, I'm curious as to how you created a working replacement kernel for 
> the bootdisk. Did you follow the instructions in the README file on the 
> rescue floppy?  If you did, then you should have a working replacement, so 
> why not just dodge the modules issue completely by compiling in the NIC 
> drivers you need (as newer bootdisks do with the tulip driver, for example)?
I read the README on the floppy and I think I now know how to put a new
kernel on that floppy so the question is how to build that driver-x.bin
disks
> 
> Finally ... if you have a working system, install the boot-floppies 
> package. In includes a script for creating the drivers disk set. 
my production-desktop is a SuSE(rpm-based). However I'll try to get that
.deb installed on it.
> The 
> drivers file is created as a single file, then put on multiple floppies 
> using a small c program called "floppy-split". I haven't used this myself, 
> but I doubt you can fake your way around it ... from a quick skim of the 
> source, it looks like the driver floppies don't have a real filesystem on 
> them, just parts of a file that can be reassembled by some app on the 
> rescue disk.
That sounds interesting I'll search for that floppy-split program to get
more information about how to create that one file as you mentioned.

micha
-- 
Windmuehlenweg 22 07907 Schleiz
mobil: +491628955029
e-Mail: Michael.Gruner@fh-hof.de

__________________________________________________________________

Gesendet von Yahoo! Mail - http://mail.yahoo.de
Yahoo! pr‰sentiert als offizieller Sponsor das Fuflball-Highlight des
Jahres: - http://www.FIFAworldcup.com
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2002-08-26 12:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-25 19:50 self-made potato driver-1.bin Michael Gruner
2002-08-25 20:46 ` pa3gcu
2002-08-26 12:09   ` Michael Gruner
2002-08-26 13:39     ` pa3gcu
2002-08-25 22:40 ` Ray Olszewski
2002-08-26 12:09   ` Michael Gruner [this message]
2002-08-26 14:34     ` Ray Olszewski
2002-08-26  8:20 ` ichi
2002-08-25 21:02   ` pa3gcu
2002-08-26 10:12     ` ichi
2002-08-26  6:28       ` pa3gcu
2002-08-26 14:58         ` Hal MacArgle

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=1030363455.928.35.camel@highflyer \
    --to=stockraser@yahoo.de \
    --cc=linux-newbie@vger.kernel.org \
    --cc=ray@comarre.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox