1*50dbef1aSdholland/* $NetBSD: msg.md.en,v 1.1 2014/07/26 19:30:47 dholland Exp $ */ 2*50dbef1aSdholland 3*50dbef1aSdholland/* 4*50dbef1aSdholland * Copyright 1997 Piermont Information Systems Inc. 5*50dbef1aSdholland * All rights reserved. 6*50dbef1aSdholland * 7*50dbef1aSdholland * Based on code written by Philip A. Nelson for Piermont Information 8*50dbef1aSdholland * Systems Inc. 9*50dbef1aSdholland * 10*50dbef1aSdholland * Redistribution and use in source and binary forms, with or without 11*50dbef1aSdholland * modification, are permitted provided that the following conditions 12*50dbef1aSdholland * are met: 13*50dbef1aSdholland * 1. Redistributions of source code must retain the above copyright 14*50dbef1aSdholland * notice, this list of conditions and the following disclaimer. 15*50dbef1aSdholland * 2. Redistributions in binary form must reproduce the above copyright 16*50dbef1aSdholland * notice, this list of conditions and the following disclaimer in the 17*50dbef1aSdholland * documentation and/or other materials provided with the distribution. 18*50dbef1aSdholland * 3. The name of Piermont Information Systems Inc. may not be used to endorse 19*50dbef1aSdholland * or promote products derived from this software without specific prior 20*50dbef1aSdholland * written permission. 21*50dbef1aSdholland * 22*50dbef1aSdholland * THIS SOFTWARE IS PROVIDED BY PIERMONT INFORMATION SYSTEMS INC. ``AS IS'' 23*50dbef1aSdholland * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 24*50dbef1aSdholland * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 25*50dbef1aSdholland * ARE DISCLAIMED. IN NO EVENT SHALL PIERMONT INFORMATION SYSTEMS INC. BE 26*50dbef1aSdholland * LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 27*50dbef1aSdholland * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 28*50dbef1aSdholland * SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 29*50dbef1aSdholland * INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 30*50dbef1aSdholland * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 31*50dbef1aSdholland * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF 32*50dbef1aSdholland * THE POSSIBILITY OF SUCH DAMAGE. 33*50dbef1aSdholland * 34*50dbef1aSdholland */ 35*50dbef1aSdholland 36*50dbef1aSdholland/* shark machine dependent messages, english */ 37*50dbef1aSdholland 38*50dbef1aSdholland 39*50dbef1aSdhollandmessage md_hello 40*50dbef1aSdholland{ 41*50dbef1aSdholland} 42*50dbef1aSdholland 43*50dbef1aSdhollandmessage md_may_remove_boot_medium 44*50dbef1aSdholland{If you booted from a floppy, you may now remove the disk. 45*50dbef1aSdholland} 46*50dbef1aSdholland 47*50dbef1aSdhollandmessage Keyboard_type {Keyboard type} 48*50dbef1aSdhollandmessage kb_default {} 49*50dbef1aSdholland 50*50dbef1aSdhollandmessage badreadbb 51*50dbef1aSdholland{Cannot read filecore boot block 52*50dbef1aSdholland} 53*50dbef1aSdholland 54*50dbef1aSdhollandmessage badreadriscix 55*50dbef1aSdholland{Cannot read RISCiX partition table 56*50dbef1aSdholland} 57*50dbef1aSdholland 58*50dbef1aSdhollandmessage notnetbsdriscix 59*50dbef1aSdholland{No NetBSD partition found in RISCiX partition table - Cannot label 60*50dbef1aSdholland} 61*50dbef1aSdholland 62*50dbef1aSdhollandmessage notnetbsd 63*50dbef1aSdholland{No NetBSD partition found (filecore only disk ?) - Cannot label 64*50dbef1aSdholland} 65*50dbef1aSdholland 66*50dbef1aSdhollandmessage dobootblks 67*50dbef1aSdholland{Installing boot blocks on %s.... 68*50dbef1aSdholland} 69*50dbef1aSdholland 70*50dbef1aSdhollandmessage arm32fspart 71*50dbef1aSdholland{We now have your NetBSD partitions on %s as follows (Size and Offset in %s): 72*50dbef1aSdholland} 73*50dbef1aSdholland 74*50dbef1aSdhollandmessage set_kernel_1 75*50dbef1aSdholland{Kernel (GENERIC)} 76*50dbef1aSdholland 77*50dbef1aSdhollandmessage setbootdevice 78*50dbef1aSdholland{In order to make your system boot automatically from the on-disk file 79*50dbef1aSdhollandsystem, you need to manually configure OpenFirmware to tell it where to 80*50dbef1aSdhollandload the kernel from. 81*50dbef1aSdholland 82*50dbef1aSdhollandOpenFirmware can load a NetBSD a.out kernel (sorry, ELF is not supported) 83*50dbef1aSdhollandstraight from a FFS partition on the local hard disk. So, to configure it 84*50dbef1aSdhollandto boot the just-installed kernel, run the following command from 85*50dbef1aSdhollandOpenFirmware's shell: 86*50dbef1aSdholland 87*50dbef1aSdhollandsetenv boot-device disk:\\netbsd.aout 88*50dbef1aSdholland 89*50dbef1aSdhollandYou only need to run this once and only if the 'boot-device' property did 90*50dbef1aSdhollandnot already contain the value shown above. 91*50dbef1aSdholland} 92*50dbef1aSdholland 93*50dbef1aSdhollandmessage badclearmbr 94*50dbef1aSdholland{Failed to clear the disk's first sector. If OpenFirmware cannot see the 95*50dbef1aSdhollanddisk, try to run the following command manually from the installer's shell 96*50dbef1aSdhollandutility: 97*50dbef1aSdholland 98*50dbef1aSdhollanddd if=/dev/zero of=%s bs=512 count=1 99*50dbef1aSdholland} 100