linux-alpha.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: mru@users.sourceforge.net (Måns Rullgård)
To: 333101@personal.net.py
Cc: linux-alpha@vger.kernel.org
Subject: Re: compiling kernel for an alphaserver (VERY OLD ONE)
Date: 26 Apr 2003 15:52:44 +0200	[thread overview]
Message-ID: <yw1xof2t2wnn.fsf@zaphod.guide> (raw)
In-Reply-To: <1051361328.1967.64.camel@Gandalf>

Alan Bort <333101@personal.net.py> writes:

> > > 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.
> well: 4,0M    patch-2.4.20.bz2
> 
> that's what du patch-2.4.20.bz2 returns....

That's the patch (i.e. difference) from 2.4.19 to 2.4.20.  The full
source is called linux-2.4.20.tar.bz2, but remember that 2.4.20 is
broken.

> > > 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.
> But I will be able to boot to my good kernel... won't I?

Sooner or later, of course.  Which distribution is installed right now?

-- 
Måns Rullgård
mru@users.sf.net
-
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

  reply	other threads:[~2003-04-26 13:52 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
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 [this message]
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=yw1xof2t2wnn.fsf@zaphod.guide \
    --to=mru@users.sourceforge.net \
    --cc=333101@personal.net.py \
    --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).