From owner-freebsd-alpha Tue Oct 12 11:12:56 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from mail.netbsd.org (redmail.netbsd.org [155.53.200.193]) by hub.freebsd.org (Postfix) with SMTP id 4CB7C14F13 for ; Tue, 12 Oct 1999 11:12:53 -0700 (PDT) (envelope-from cgd@netbsd.org) Received: (qmail 19318 invoked by uid 1000); 12 Oct 1999 18:11:25 -0000 To: Wilko Bulte Cc: tg@ihf.rwth-aachen.de (Thomas Gellekum), freebsd-alpha@FreeBSD.ORG Subject: Re: DEC3000/400 SRM bootp overview References: <199910121737.TAA55060@yedi.iaf.nl> From: cgd@netbsd.org (Chris G. Demetriou) Date: 12 Oct 1999 11:11:24 -0700 In-Reply-To: Wilko Bulte's message of Tue, 12 Oct 1999 19:37:00 +0200 (CEST) Message-ID: <87u2nwh2k3.fsf@redmail.netbsd.org> Lines: 25 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wilko Bulte writes: > I have the f/w images, that is not the problem. How would you get them > onto the machine is the question. I mean, the machines support upgrading > firmware via bootp. Sort of chicken and egg. MOP netbooting should also work > for f/w updates I think. bootp's out, mop booting's annoying but probably possible, but... this is why NetBSD/alpha has the 'mkbootimage(8)' command. you can mkbootimage a firmware upgrade image (one of the .exe's, not one of the other-suffixed files), and dd it on to floppy, or i'd even guess burn the resulting (small; typically less than 1MB 8-) file on to a CD-ROM... Looks like at least most of the rest of the NetBSD/alpha boot blocks have been copied (although it doesn't look like whoever did the copying was careful enough to file off all the serial numbers^W^Winstances of the NetBSD name in them), why not copy those bits too? cgd -- Chris Demetriou - cgd@netbsd.org - http://www.netbsd.org/People/Pages/cgd.html Disclaimer: Not speaking for NetBSD, just expressing my own opinion. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message