Re: tftpboot images for potato
> Does anyone have a link to some tftp boot images for the potato
> release?
I don't recall where they are, off hand.
> Or if someone has a link to instructions on how to make a
> tftp image for sparc that would be great too...
Several months ago I sent a message to Brian Ward, Kernel HOWTO maintainer,
describing how kernel compilation on Sparc differs from i386, but,
unfortunately, this information has yet to be included in the HOWTO.
I'll include it below.
Eric
------- Forwarded Message
X-Mailer: exmh version 2.0.2 2/24/98 (debian)
To: Brian Ward <bri@cs.uchicago.edu>
From: sharkey@superk.physics.sunysb.edu
X-Eric-Conspiracy: There is no conspiracy
Subject: Re: how to compile a kernel?
In-reply-to: Your message of "Wed, 13 Oct 1999 20:43:50 EST."
<19991014014350.4BFDCAA025@smack.cs.uchicago.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 16 Oct 1999 17:28:19 +0900
Sender: sharkey@neutrino.kek.jp
> If someone can submit differences for other architectures including notes
> for common hardware quirks, then I can include them in the Kernel-HOWTO,
I did some digging on Deja, just to make sure I didn't miss anything.
I didn't. There were lots of posts on the topic, so this is definitely a
FAQ worth documenting. One post even complained that Linus had been sent
a patch to the top level README to make it less Intel-centric, but it was
never included.
Feel free to edit this in any way you see fit, or incorporate
it as is.
The process of compiling/installing a kernel for the Sparc or Sparc64
architectures is the same as compiling for i386, with the following
exceptions:
1. There is no program called LILO. The Sparc equivalent is called SILO,
exists as /sbin/silo, and is configured in /etc/silo.conf. The
silo configuration file has nearly the same syntax as lilo.conf.
The most notable difference is that the boot partition must be listed
with the "partition" keyword, such as "partition=1". Check the
silo man page for full details.
2. The make targets zImage and bzImage do not exist, instead, the target
"vmlinux" should be used instead.
3. The result of "make vmlinux" will not be in arch/i386/boot, but at the
top directory of the kernel source tree.
4. vmlinux will not be a compressed kernel image. This uncompressed kernel
image may be copied directly into /boot or wherever kernels are kept,
or it may be first compressed with gzip and then copied. Sparcs can
boot off both compressed and uncompressed images.
5. There is an additional "makable" called "tftpboot.img" which can be
used after "make vmlinux". This will combine the vmlinux kernel
image with a root filesystem image /usr/src/root.img, to
create a tftpboot.img file. This file can be used to boot diskless
Sparcs, or Sparcs which do not yet have Linux installed on a local
disk by placing it on a tftpboot server and issuing the "boot net"
command at the Sun boot prompt.
6. For UltraSparc, or sparc64, architectures, it is necessary to have
a 64-bit capable C compiler, such as egcs64. Unlike other
architectures, where the C compiler will be assumed to be gcc,
the sparc64 build expects a compiler called "sparc64-linux-gcc". If
this compiler does not exist, the build will fail.
That's probably it. I haven't uncovered any any particular hardware
quirks. There just isn't that much variation in Sun hardware, since pretty
much all of it (except for disk drives) is made by Sun. There are several
differences in the particular configuration options available, but they're
all pretty straightforward. (If your Sun has a Sparc ESP SCSI control,
select the Sparc EPS SCSI driver... etc. etc. etc.)
Contact me if you need any more info.
Eric
------- End of Forwarded Message
Reply to: