From: Miguel Bolanos <mike@linuxlabs.com>
To: Tommy McCabe <rocketjet314@yahoo.com>
Cc: linux-8086@vger.kernel.org
Subject: ** Applied ** Re: full5 with elksnet
Date: Wed, 09 Jun 2004 07:42:23 -0600 [thread overview]
Message-ID: <1086764754.3982.1.camel@talena.hsol.net> (raw)
In-Reply-To: <20040603190129.32087.qmail@web51306.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1906 bytes --]
Removed the mkdir lines and applied. thanks.
Mike
On Thu, 2004-06-03 at 13:01, Tommy McCabe wrote:
> This patch:
>
> 1. Includes ktcp in full5.
>
> 2. Makes sure there is a /bin directory to put ktcp
> into in both comb_net and full5 (yes, I did use the -p
> option, though I don't know why).
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Friends. Fun. Try the all-new Yahoo! Messenger.
> http://messenger.yahoo.com/
>
> ______________________________________________________________________
> --- ./elkscurr/elkscmd/Makefile 2004-06-03 14:56:54.000000000 -0400
> +++ ./elks/elkscmd/Makefile 2004-06-03 14:54:17.000000000 -0400
> @@ -224,6 +224,10 @@
> dd if=$(FD_BSECT) of=$(FULL3_TARGET_FS) bs=512 count=2 conv=notrunc
>
> full5: mount_full3fs $(ELKS_DIR)/arch/i86/boot/Image $(FD_BSECT) $(KHELPER)
> + cd $(ELKSNET_DIR)/ktcp ; \
> + make ; \
> + mkdir -p $(TARGET_MNT)/bin
> + cp -p -f ktcp $(TARGET_MNT)/bin
> @for i in $(DIRS); do make -C $$i rfs ; done
> cp $(ELKS_DIR)/arch/i86/boot/Image $(TARGET_MNT)/boot/linux
> cp $(KHELPER) $(TARGET_MNT)/boot/boot
> @@ -237,6 +241,7 @@
> comb_net: mount_rootnetfs $(ELKS_DIR)/arch/i86/boot/Image $(FD_BSECT) $(KHELPER)
> cd $(ELKSNET_DIR)/ktcp ; \
> make ; \
> + mkdir -p $(TARGET_MNT)/bin
> cp -p -f ktcp $(TARGET_MNT)/bin
> @for i in $(DIRS); do make -C $$i net_rfs ; done
> cp $(ELKS_DIR)/arch/i86/boot/Image $(TARGET_MNT)/boot/linux
--
--------------------miguel bolanos, systems administrator, linuxlabs
... ........ ..... .... 230 peachtree st nw ste 2701
the original linux labs atlanta.ga.us 30303
-since 1995 http://www.linuxlabs.com
office 404.577.7747 fax 404.577.7743
--------------------------------------------------------------------
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-06-09 13:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-03 19:01 full5 with elksnet Tommy McCabe
2004-06-03 21:26 ` claudio
2004-06-03 21:32 ` Tommy McCabe
2004-06-04 3:34 ` Miguel Bolanos
2004-06-04 11:35 ` claudio
2004-06-04 20:28 ` Tommy McCabe
2004-06-04 0:33 ` David Given
2004-06-05 13:11 ` claudio
2004-06-04 3:18 ` Miguel Bolanos
2004-06-09 13:42 ` Miguel Bolanos [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=1086764754.3982.1.camel@talena.hsol.net \
--to=mike@linuxlabs.com \
--cc=linux-8086@vger.kernel.org \
--cc=rocketjet314@yahoo.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