11.3Smaya/*	$NetBSD: md.h,v 1.3 2019/10/02 11:16:01 maya Exp $	*/
21.1Sdholland
31.1Sdholland/*
41.1Sdholland * Copyright 1997 Piermont Information Systems Inc.
51.1Sdholland * All rights reserved.
61.1Sdholland *
71.1Sdholland * Written by Philip A. Nelson for Piermont Information Systems Inc.
81.1Sdholland *
91.1Sdholland * Redistribution and use in source and binary forms, with or without
101.1Sdholland * modification, are permitted provided that the following conditions
111.1Sdholland * are met:
121.1Sdholland * 1. Redistributions of source code must retain the above copyright
131.1Sdholland *    notice, this list of conditions and the following disclaimer.
141.1Sdholland * 2. Redistributions in binary form must reproduce the above copyright
151.1Sdholland *    notice, this list of conditions and the following disclaimer in the
161.1Sdholland *    documentation and/or other materials provided with the distribution.
171.1Sdholland * 3. The name of Piermont Information Systems Inc. may not be used to endorse
181.1Sdholland *    or promote products derived from this software without specific prior
191.1Sdholland *    written permission.
201.1Sdholland *
211.1Sdholland * THIS SOFTWARE IS PROVIDED BY PIERMONT INFORMATION SYSTEMS INC. ``AS IS''
221.1Sdholland * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
231.1Sdholland * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
241.1Sdholland * ARE DISCLAIMED. IN NO EVENT SHALL PIERMONT INFORMATION SYSTEMS INC. BE
251.1Sdholland * LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
261.1Sdholland * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
271.1Sdholland * SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
281.1Sdholland * INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
291.1Sdholland * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
301.1Sdholland * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
311.1Sdholland * THE POSSIBILITY OF SUCH DAMAGE.
321.1Sdholland *
331.1Sdholland */
341.1Sdholland
351.1Sdholland/* md.h -- Machine specific definitions for the bebox */
361.1Sdholland
371.1Sdholland
381.1Sdholland/* bebox uses the mbr code. */
391.1Sdholland#include "mbr.h"
401.1Sdholland
411.1Sdholland/* constants and defines */
421.1Sdholland
431.1Sdholland
441.2Smartin#define XNEEDMB		256	/* Extra megs for full X installation */
451.2Smartin#define DEBNEEDMB	900	/* Extra megs for debug sets */
461.2Smartin
471.1Sdholland
481.1Sdholland
491.1Sdholland/*
501.1Sdholland *  Default filesets to fetch and install during installation
511.1Sdholland *  or upgrade. The standard sets are:
521.3Smaya *      base etc comp games man misc rescue tests text xbase xcomp xetc xfont xserver
531.1Sdholland */
541.1Sdholland
551.1Sdholland#define SET_KERNEL_1_NAME	"kern-GENERIC"
561.1Sdholland
571.1Sdholland/*
581.1Sdholland * Machine-specific command to write a new label to a disk.
591.1Sdholland * For example, bebox  uses "/sbin/disklabel -w -r", just like bebox
601.1Sdholland * miniroot scripts, though this may leave a bogus incore label.
611.1Sdholland * Sun ports should probably use  DISKLABEL_CMD "/sbin/disklabel -w"
621.1Sdholland * to get incore  to ondisk inode translation for the Sun proms.
631.1Sdholland * If not defined, we assume the port does not support disklabels and
641.1Sdholland * hand-edited disklabel will NOT be written by MI code.
651.1Sdholland *
661.1Sdholland * On bebox, do what the 1.2 install scripts did.
671.1Sdholland */
681.1Sdholland#define DISKLABEL_CMD "disklabel -w -r"
69