mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Holden <alex@linuxhacker.org>
To: linux-kernel@vger.rutgers.edu
Cc: linux-embedded@waste.org
Subject: Announce: initrd-tftp 0.2
Date: Fri, 31 Dec 1999 04:31:51 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.04.9912310404420.548-100000@hyperspace.linuxhacker.org> (raw)

* Please CC: me in replies as I'm not on linux-kernel currently *

I've just finished implementing and testing gzipped image support for
initrd-tftp, as well as fixing a few bugs (including telling you nicely 
when the image is too large for the ramdisk), and adding the capability to
specify what tftp server to use and file to download on the kernel command
line. It's even fairly well documented! ;)

You can download the patch (still against 2.2.13) from:
ftp://ftp.linuxhacker.org/pub/kernel/initrd-tftp/initrd-tftp-0.2.patch.gz
Please let me know of any problems you encounter.

The only things remaining to do are to clean a couple of things up to make
it play nicely in the case where you want to compile it in but not load an
initrd, and seperating the last of CONFIG_BLK_DEV_INITRD out from
CONFIG_BLK_DEV_INITRD_TFTP (ie. you shouldn't need the old floppy disk
loader and memory area loader (where the boot loader loads the ramdisk
into a memory area for you) if you're getting the initrd via tftp).

--------------- Linux- the choice of a GNU generation. --------------
: Alex Holden (M1CJD)- Caver, Programmer, Land Rover nut, Radio Ham :
-------------------- http://www.linuxhacker.org/ --------------------







-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

                 reply	other threads:[~1999-12-31  4:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=Pine.LNX.4.04.9912310404420.548-100000@hyperspace.linuxhacker.org \
    --to=alex@linuxhacker.org \
    --cc=linux-embedded@waste.org \
    --cc=linux-kernel@vger.rutgers.edu \
    /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®