Re: [9fans] change to bitsy/devsac.c to use the new bootldr

[F.J.Ballesteros <nemo@gsyc.escet.urjc.es>]

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

I think that would be nice.

In fact, I was thinking of just adding a newramdisk: target
to the mkfile, w/ something like...
	cat <{echo -n xxxx} oldramdisk >newramdisk

On the other hand, wouldn't it be better to encourage people
to use the new boot loader (since otherwise they might break
their real power on switch)? 

Probably you know better than me which option is likely to
be more adequate.

BTW, I am very grateful to the one(s) who decided that sac.fs would be
a tar file. In general, I'm grateful to you all for keeping Plan 9  so
clean. It is orders of magnitude easier to modify/adapt it than it is
for the other systems I've seen.


[-- Attachment #2: Type: message/rfc822, Size: 1707 bytes --]

From: presotto@plan9.bell-labs.com
To: nemo@gsyc.escet.urjc.es, 9fans@cse.psu.edu
Subject: Re: [9fans] change to bitsy/devsac.c to use the new bootldr
Date: Fri, 15 Jun 2001 08:41:11 -0400
Message-ID: <20010615124114.30DBC19A12@mail.cse.psu.edu>

Might this be a better change, i.e., so it'll work both with
both the old and new bootldr's?

	p = (uchar*)Flash_tar+4;
	data = tarlookup(p, sacfs, &i);
	if(data == 0) {
		p = (uchar*)Flash_tar;
		data = tarlookup(p, sacfs, &i);
		if(data == 0) {
			print("devsac: could not find file: %s\n", sacfs);
			return;
		}
	}