From: "Oliver Pitzeier" <o.pitzeier@uptime.at>
To: 'Jan-Benedict Glaw' <jbglaw@lug-owl.de>, linux-alpha@vger.kernel.org
Subject: RE: compiling kernel for an alphaserver (VERY OLD ONE)
Date: Sat, 26 Apr 2003 21:36:23 +0200 [thread overview]
Message-ID: <001901c30c2b$26993e10$1011a8c0@roadrunner> (raw)
In-Reply-To: <20030426160533.GX19139@lug-owl.de>
[ ... ]
> First, you download _source code_. This is about a 25MB
> compressed file containing about 120MB of sources. Then,
> you've got to configure and build these sources. The
> resulting binary file is the kernel image to boot of about
> 1.5 .. 3 MB size (comressed with gzip). This file can be
> booted through aboot or milo.
Like this one:
[oliver@track oliver]$ ls -lah /boot/vmlinuz-2.5.64
-rw-r--r-- 1 root root 1.9M Mar 6 16:58 /boot/vmlinuz-2.5.64
[ ... ]
And aboot.conf should look something like this:
[oliver@track oliver]$ cat /etc/aboot.conf
# aboot default configurations
# NOTICE: You have a /boot partition. This means that
# all kernel paths are relative to /boot/
0:1/vmlinuz-2.5.64 root=/dev/sda3 console=tty0
> > something like WARNING the file has a modification time in
> the future.
>
> # date -s '....'
>
> will fix it, possibly as well as installing ntpdate and ntpd.
You can try rdate as well...
rdate -s <timeserver>; hwclock -w
br,
Oliver
next prev parent reply other threads:[~2003-04-26 19:36 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
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 [this message]
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='001901c30c2b$26993e10$1011a8c0@roadrunner' \
--to=o.pitzeier@uptime.at \
--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 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.