From: ctino.schmitt@t-online.de (SchmiTTT)
To: linux-kernel@vger.kernel.org
Subject: hello ? from one not in anything advanced . . .
Date: 21 Jan 2003 22:04:34 +0100 [thread overview]
Message-ID: <1043183075.10987.21.camel@linux> (raw)
Hi !
At present I have SuSE (ouch! I know now too, its a sticky Distri)
8.0 with kernel 2.4.18 . . .
Wanted to install kernel 2.4.20, though there is no special one for
SuSE, but want to build this kernel from a CD of a magazine. And it
should run too.
I have at present this SuSE konfiguration with a boot-Discette (there
is a part of LILO on it, but not whole LILO). This discette is not
able to be viewed in (for security purpose). The files on it are
invisible or "not readable".
Easiest way is then to create an extra boot-diskette for 2.4.20
but this fails with the warning (though kernel is compressed
with 'make bzImage'):
warning: kernel is too big for standalone boot from floppy
make[1]: leaving directory . . . blah
I tried as in README explained with 'make bzdisk' and a diskette
in drive A . . . same warning . . .
Somehow the README seems not to be quite proper or not
detailed enough . . .???
For feedback thank you very much !!!
Regards
Tino.
reply other threads:[~2003-01-21 20:51 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=1043183075.10987.21.camel@linux \
--to=ctino.schmitt@t-online.de \
--cc=linux-kernel@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