All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-alpha@vger.kernel.org
Subject: Re: compiling kernel for an alphaserver (VERY OLD ONE)
Date: Sat, 26 Apr 2003 14:33:57 +0200	[thread overview]
Message-ID: <20030426123356.GU19139@lug-owl.de> (raw)
In-Reply-To: <yw1xel3p4pd8.fsf@zaphod.guide>

[-- Attachment #1: Type: text/plain, Size: 2700 bytes --]

On Sat, 2003-04-26 10:47:15 +0200, Måns Rullgård <mru@users.sourceforge.net>
wrote in message <yw1xel3p4pd8.fsf@zaphod.guide>:
> Alan Bort <333101@personal.net.py> writes:
> 
> > Ok... here is the deal.
> > 
> > I've read a couple tutorials on compiling kernel and stuff... but in
> > both my machines I have Mandrake 9.1 and a friend told me that it had
> > some compatibility issues with the new plain kernel... ANyway... the
> > problem is that I want to put the new kernel (not the latest, just
> > 2.4.20) on my Alphaserver200 Is that possible.. (I KNOW IT IS)...
> 
> 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.

> > 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...

> > I'm currently running RH7.0 on my alpha and It's an important machine in
> > my network... it's the router and the http/sendmail/ftp/etc server...
> > 
> > I'd appreciate all the help you can give me here... I'm new to linux (at
> > least at this level) and I certainly never did somthing like this... I
> > don't want to screw THIS one... I'm already downloading RH9 that isn't
> > supposed to have any trouble with the not-mdified kernel... so I think I
> > can screw that one up a few times... also... it's an x86 intel... so
> > LILO works and I can boot to any kernel I want.
> 
> Read about aboot.
> 
> If you're new at this stuff, you WILL screw it up once or twice before
> you learn it.  That doesn't mean that you'll loose any data, of
> course.

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.

MfG, JBG

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-04-26 12:33 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 [this message]
2003-04-26 12:54     ` Alan Bort
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=20030426123356.GU19139@lug-owl.de \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.