From: Eddy <eddyx89@gmail.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: CVS patch
Date: Wed, 09 Aug 2006 16:06:01 +0200 [thread overview]
Message-ID: <44D9EBC9.5040107@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
There is patchs for elks and elkscmd from CVS, in elkscmd i had to bring
bootblocks directory from dev86 sources and modify something in order to
build correctly "make comb".
I tried the built in qemu but init don't start yet.
Packages files from sf.net are broken, elks-0.1.3.tar.gz is still
unpackable, but it's not the same for elkscmd-(date).tar.gz, it's not
gzip format, nor bzip2, nor tar.
Some elks' web site links are not correct and not updated, i can help
you if I became developer, also as Italian translator.
Another strange thing is that there's no archive's list for this list,
am I writing to someone?? :P
Sincerely
Eddy.
Ps. I'll be on holidays for a tenth of days, and I'm quite sure I will
not able to receive mails.. C U.
[-- Attachment #2: patch-elks-CVS.patch --]
[-- Type: text/plain, Size: 1445 bytes --]
diff -Naur CVSori/elks/arch/i86/Makefile CVS/elks/arch/i86/Makefile
--- CVSori/elks/arch/i86/Makefile 2004-05-31 15:49:25.000000000 +0200
+++ CVS/elks/arch/i86/Makefile 2006-08-09 13:10:08.000000000 +0200
@@ -92,7 +92,7 @@
(cd $(BASEDIR) ; $(LD) $(LDFLAGS) $(ARCH_LD) \
$(ARCH_DIR)/sibo/crt0.o $(ARCH_DIR)/sibo/crt1.o \
init/main.o $(ARCHIVES) $(DRIVERS) \
- -t -M -o $(ARCH_DIR)/boot/system > System.tmp ; \
+ -M -o $(ARCH_DIR)/boot/system > System.tmp ; \
sort -k4 System.tmp > System.map ; rm -f System.tmp )
#SIBO image build
diff -Naur CVSori/elks/arch/i86/drivers/char/KeyMaps/mkcfg CVS/elks/arch/i86/drivers/char/KeyMaps/mkcfg
--- CVSori/elks/arch/i86/drivers/char/KeyMaps/mkcfg 2002-04-25 00:03:53.000000000 +0200
+++ CVS/elks/arch/i86/drivers/char/KeyMaps/mkcfg 2006-08-09 13:10:26.000000000 +0200
@@ -13,14 +13,14 @@
printf '# Automatically created - do not edit.\n\n' >&3
printf "choice 'XT Keyboard support'\t\t" >&3
printf '/* Automatically created - do not edit */\n\n' >&4
- while read FILE CODE NAME ; do
+ while read FILE CODE NAME ; do
printf '\t\\\n\t%-12s\tCONFIG_KEYMAP_%s' >&3 \
"${SEP}${NAME}" "${CODE}"
SEP=' '
printf '#include "%s"\t\t/* %s\t%-9s\t*/\n' >&4 \
"${FILE}" "${CODE}" "${NAME}"
done
- printf '"\t\tAmerican\n\n# EOF.\n' >&3
+ printf '\"\n' >&3
}
-codes | sort +1f | process 3> Config.in 4> keymaps.h
+codes | process 3> Config.in 4> keymaps.h
[-- Attachment #3: patch-elkscmd-CVS.patch.gz --]
[-- Type: application/gzip, Size: 64524 bytes --]
next reply other threads:[~2006-08-09 14:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-09 14:06 Eddy [this message]
2006-08-09 16:55 ` CVS patch Tom McCabe
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=44D9EBC9.5040107@gmail.com \
--to=eddyx89@gmail.com \
--cc=linux-8086@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