From: Michael Hofmann <michael.hofmann-@gmx.net>
To: linux-8086@vger.kernel.org
Subject: Compiling Trouble etc
Date: Wed, 1 Jan 2003 17:03:19 +0100 [thread overview]
Message-ID: <200301011702.25636.michael.hofmann-@gmx.net> (raw)
Hello,
where can I get the missing binaries for the complete distribution, as found
in elkscmd and elksnet?
Compiling is probably not meant for the average user that I am. All I get is
errors, and without profound documentation I don't seem to be able to resolve
the issues.
A few more questions:
- When trying to compile, I wanted to incorporate the German keymap to
accomodate my keyboard. It seems like the keymap is compiled into the kernel,
there is probably no other way to map a German layout? If so, does anyone
have a "Germanized" kernel for me?
- Since there is no adduser command, how do I establish a user account?
- A while ago someone posted a link to e3, a small editor suitable for ELKS. I
dld it and compiled, but it doesn't seem to work. The precompiled binary also
doesn't work. Did anyone succeed, and how? I always hated vi and would
appreciate something less cryptic. (BTW the Linux version works fine on my
RH7.3 system)
- Are there plans for ethernet drivers, particularly the 3C503 (I remember
someone suggested this card a while ago)?
I have many more questions, but this should be enough for now. Thanks to
everyone who contributed to ELKS. I have been fascinated ever since I started
lurking about 3 years ago, to have sth else than DOS to run on my 286-16.
TIA,
Michael
next reply other threads:[~2003-01-01 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-01 16:03 Michael Hofmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-01 22:53 Compiling Trouble etc Michael Hofmann
2003-01-03 19:15 Neil Holmes
2003-01-03 21:46 Michael Hofmann
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=200301011702.25636.michael.hofmann-@gmx.net \
--to=michael.hofmann-@gmx.net \
--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