From 9fans-admin@cse.psu.edu Fri Jun 15 06:57:25 2001
Received: from mailhost.lanl.gov (mailhost.lanl.gov [128.165.3.12]) by
acl.lanl.gov (8.11.3/8.8.5) with ESMTP id f5FCvPp3092931; Fri, 15 Jun 2001
06:57:25 -0600 (MDT)
Received: from mailproxy1.lanl.gov (mailproxy1.lanl.gov [128.165.0.26])
by mailhost.lanl.gov (8.10.1/8.10.1/(cic-5, 6/12/00)) with ESMTP id
f5FCvO600302;
Fri, 15 Jun 2001 06:57:24 -0600
Received: from mail.cse.psu.edu (psuvax1.cse.psu.edu [130.203.4.6])
by mailproxy1.lanl.gov (8.11.4/8.11.4/(ccn-5)) with ESMTP id f5FCvOE08147;
Fri, 15 Jun 2001 06:57:24 -0600
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.20.6])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP
id 0728419A25; Fri, 15 Jun 2001 08:57:12 -0400 (EDT)
Received: from nautilus.dat.escet.urjc.es (nautilus.dat.escet.urjc.es
[212.128.1.37])
by mail.cse.psu.edu (CSE Mail Server) with SMTP id 5CF95199F0
for <9fans@cse.psu.edu>; Fri, 15 Jun 2001 08:56:58 -0400 (EDT)
To: 9fans@cse.psu.edu
Subject: Re: [9fans] change to bitsy/devsac.c to use the new bootldr
From: "F.J.Ballesteros" <nemo@gsyc.escet.urjc.es>
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="upas-vevowdrhwhhqrwknpfrwmxsanz"
Message-Id: <20010615125658.5CF95199F0@mail.cse.psu.edu>
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0.1
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive: <http://lists.cse.psu.edu/archives/9fans/>
Date: Fri, 15 Jun 2001 15:07:29 +0200
Status: RO
X-Status:
This is a multi-part message in MIME format.
--upas-vevowdrhwhhqrwknpfrwmxsanz
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
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.
--upas-vevowdrhwhhqrwknpfrwmxsanz
Content-Type: message/rfc822
Content-Disposition: inline
Return-Path: <9fans-admin@cse.psu.edu>
Received: from mail.cse.psu.edu (postfix@psuvax1.cse.psu.edu [130.203.4.6])
by gsyc.escet.urjc.es (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id
OAA28097;
Fri, 15 Jun 2001 14:42:32 +0200
X-Authentication-Warning: gsyc.escet.urjc.es: Host postfix@psuvax1.cse.psu.edu
[130.203.4.6] claimed to be mail.cse.psu.edu
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.30.6])
by mail.cse.psu.edu (CSE Mail Server) with ESMTP
id 0F45E19A23; Fri, 15 Jun 2001 08:42:12 -0400 (EDT)
Received: from plan9.cs.bell-labs.com (ampl.com [204.178.31.2])
by mail.cse.psu.edu (CSE Mail Server) with SMTP id 30DBC19A12
for <9fans@cse.psu.edu>; Fri, 15 Jun 2001 08:41:14 -0400 (EDT)
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
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-Id: <20010615124114.30DBC19A12@mail.cse.psu.edu>
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0.1
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive: <http://lists.cse.psu.edu/archives/9fans/>
Date: Fri, 15 Jun 2001 08:41:11 -0400
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;
}
}
--upas-vevowdrhwhhqrwknpfrwmxsanz--