From: Alan Bort <333101@personal.net.py>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: linux-alpha@vger.kernel.org
Subject: Re: compiling kernel for an alphaserver (VERY OLD ONE)
Date: 26 Apr 2003 09:54:10 -0300 [thread overview]
Message-ID: <1051361649.1968.70.camel@Gandalf> (raw)
In-Reply-To: <20030426123356.GU19139@lug-owl.de>
El sáb, 26 de 04 de 2003 a las 09:33, Jan-Benedict Glaw escribió:
[SNIP]
> > Don't use 2.4.20 on Alpha, it has nasty bugs. 2.4.19 is fine, as are
> > 2.4.21-pre1 and up.
>
> Or 2.5.x. I'm running them for quite some time on NoName, Miata and
> Avanti with no problems at all.
I'll try with 2.4.19 I think it is a little more tested... or at least I
think it should
>
> > > Since Lilo is not an option... what happends if I missconfigure
> > > something??? how do I boot to another kernel??? from the bios console???
> >
> > Have you read the aboot man pages. On Alphas, aboot does what lilo
> > does on PCs (approximately).
>
> aboot (for SRM-based machines), or milo (which is for AlphaBIOS based
> machines).
>
> > > I've noted that the downloadable file is only 4 MB (a little less)... is
> > > that the FULL kernel???
> >
> > Is that already compiled? My kernels usually end up around 1.5 MB in
> > size, or ~2.7 MB uncompressed.
> Maybe it contains loads of drivers. I think you can easily get a 4MB
> uncompressed kernel image...
The problem is that It's 4MB compressed WITH BZ2!
>
[SNIP]
>
> I subscribe that. Alpha is _not_ i386, so some things _are_ different.
> Please, do some reading (and asking) first, then eventually don't shoot
> your foot.
Of course... I'll odo as much resaerch as I do for ANY 'new' sthing I do
on linux... but... will reading preapre me well for what I should
expect???
Thanks a lot.
--
Alan Bort
Linux Registered User 298277 -Country Manager- [http://counter.li.org]
[ http://www.linuxquestions.org ] Username: Ciccio
[ http://es.tldp.org ]
Ciccio.-
-
To unsubscribe from this list: send the line "unsubscribe linux-alpha" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2003-04-26 12:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-26 2:04 compiling kernel for an alphaserver (VERY OLD ONE) Alan Bort
2003-04-26 8:47 ` Måns Rullgård
2003-04-26 12:33 ` Jan-Benedict Glaw
2003-04-26 12:54 ` Alan Bort [this message]
2003-04-26 15:58 ` Jan-Benedict Glaw
2003-04-26 18:47 ` Alan Bort
2003-04-26 12:48 ` Alan Bort
2003-04-26 13:52 ` Måns Rullgård
2003-04-26 14:00 ` Alan Bort
2003-04-26 16:01 ` Måns Rullgård
2003-04-26 16:05 ` Jan-Benedict Glaw
2003-04-26 19:36 ` Oliver Pitzeier
2003-04-26 20:50 ` Jan-Benedict Glaw
2003-04-26 19:42 ` Oliver Pitzeier
2003-04-26 20:51 ` Jan-Benedict Glaw
2003-04-27 0:18 ` Oliver Pitzeier
2003-04-26 16:02 ` Jan-Benedict Glaw
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=1051361649.1968.70.camel@Gandalf \
--to=333101@personal.net.py \
--cc=jbglaw@lug-owl.de \
--cc=linux-alpha@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;
as well as URLs for NNTP newsgroup(s).