From: Tommy McCabe <rocketjet314@yahoo.com>
To: linux-8086@vger.kernel.org
Subject: More bug fixes
Date: Sun, 29 Feb 2004 08:52:22 -0800 (PST) [thread overview]
Message-ID: <20040229165222.79342.qmail@web11704.mail.yahoo.com> (raw)
Ay, ay, ay, there are a lot of annoying bugs! This is
another version of the MAKEDEV script and an elkscmd
patch. Fixed:
#1- MAKEDEV tried to create bda16, bda17, bda18, and
so on up to 63, while I believe PC BIOS only allows
for 16 partitions, 3 primary, 1 extended, and 12
logical. The same for regular hda. Why doesn't MAKEDEV
created an bda ,to represent the entire disk?
#2- Small spelling error- the linking program is
called ln, not l.
#3- The root disk, by default, doesn't have enough
inodes for all the files, so I put in a -i224
modifier. But now there are too many inodes to fit all
the files in. Ideas, anyone?
#4- Added a provision for making any combination or
boot disk where the files in /elks/include are
automatically put in the /usr/bcc/include directory to
fix the errors saying "can't include linuxmt/blah.h".
__________________________________
Do you Yahoo!?
Get better spam protection with Yahoo! Mail.
http://antispam.yahoo.com/tools
reply other threads:[~2004-02-29 16:52 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=20040229165222.79342.qmail@web11704.mail.yahoo.com \
--to=rocketjet314@yahoo.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