[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: More install problems under Ultra10 and tftp...



Dale Scheetz <dwarf@polaris.net> writes:

> On Mon, 28 Jun 1999, Eric Delaunay wrote:
> 
> > Dale Scheetz wrote:

> > > I am certain that if someone can tell me how to extract the contents from
> > > a tftpboot.img file, I can get past these problems.

> > The kernel is not extracted from tftpboot.img by dboostrap but
> > from one of the resc1440*.bin image (either from floppy drive, or
> > cdrom or even from the net).

> I know that, but those images _are_ contained in the tftpboot image.

The tftpboot image contains two kernels and a compress ramdisk.

> My current problem is that the tftpboot image that I have is
> tftpboot-2.2.1.img. This one will boot with the file systems enabled that
> I need. What I don't have are the rescue and drivers disk images that
> correspond to that boot image. It is my understanding that these are
> contained in the tftpboot image, hense my desire to be able to extract the
> contents of this style file image.

The drivers and rescue disk are found in:
   ftp://ftp.debian.org/debian/dists/slink/main/disks-sparc/current

The relevent files are:

  drv1440-2.2.1.bin
  resc1440-2.2.1.bin
  drv1440-2.2.1-sun4u.bin
  resc1440-2.2.1-sun4u.bin

(The sun4u versions are for Ultras.)

The tftpboot-2.2.1.image is made with "maketilo" from the tilo package.
It is made by converting the sparc and sparc64 kernels to a.out,
compressing them, appending them to the end of a small a.out program,
tilo, and setting some offset values in tilo.

A raw a.out kernel can also be used for tftp booting, as can an a.out
kernel with a ramdisk properly piggybacked onto the end.


Steve
dunham@cse.msu.edu


Reply to: