Fix to properly newfs the MFS in case of custom setup. Mention this in docs.
Submitted by: Richard Wackerbarth <rkw@Dataplex.NET>
This commit is contained in:
parent
4568e792af
commit
9993c373dc
@ -1,7 +1,7 @@
|
||||
#! /bin/sh -
|
||||
|
||||
#
|
||||
# $Id: stage1,v 1.1.1.1 1998/08/27 17:38:42 abial Exp $
|
||||
# $Id: stage1,v 1.2 1998/09/07 06:46:25 abial Exp $
|
||||
#
|
||||
|
||||
set -e
|
||||
@ -59,23 +59,26 @@ then
|
||||
exit 10
|
||||
fi
|
||||
|
||||
# Default setting for other (custom) setups.
|
||||
INODES=16000
|
||||
# You can save some space on MFS if you don't want so many inodes...
|
||||
if [ "${TYPE}" = "dial" ]
|
||||
then
|
||||
newfs -i 10240 -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null
|
||||
INODES=10240
|
||||
fi
|
||||
if [ "${TYPE}" = "router" ]
|
||||
then
|
||||
newfs -i 12000 -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null
|
||||
INODES=12000
|
||||
fi
|
||||
if [ "${TYPE}" = "net" ]
|
||||
then
|
||||
newfs -i 16000 -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null
|
||||
INODES=16000
|
||||
fi
|
||||
if [ "${TYPE}" = "isp" ]
|
||||
then
|
||||
newfs -i 15000 -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null
|
||||
INODES=15000
|
||||
fi
|
||||
newfs -i $INODES -m 0 -p 0 -o space /dev/rvn0c 2>&1 >/dev/null
|
||||
mount /dev/vn0c /mnt
|
||||
if [ "X$?" != "X0" ]
|
||||
then
|
||||
|
@ -1,5 +1,5 @@
|
||||
<html>
|
||||
<! $Id: how2build.html,v 1.1.1.1 1998/08/27 17:38:42 abial Exp $ >
|
||||
<! $Id: how2build.html,v 1.2 1998/09/04 19:47:24 abial Exp $ >
|
||||
<head>
|
||||
<title><center>PicoBSD Development Kit</center></title>
|
||||
</head>
|
||||
@ -35,7 +35,9 @@
|
||||
|
||||
<p> You can also choose a special type called 'custom'. You'll need to
|
||||
supply the full path to your own custom config tree constructed
|
||||
exactly like one of the standard config directories.</p>
|
||||
exactly like one of the standard config directories. Also, you'll
|
||||
probably want to adjust the number of inodes on MFS - see the
|
||||
<code>stage1</code> script and look for <code>INODES=</code>.</p>
|
||||
|
||||
<p> I also recommend to adjust the ISA devices parameters to
|
||||
match the ones of your hardware - though PicoBSD can save the
|
||||
|
Loading…
Reference in New Issue
Block a user