Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 29 Aug 1998 19:47:50 -0700 (PDT)
From:      Matthew Dillon <dillon@backplane.com>
To:        "Jonathan M. Bresler" <jmb@FreeBSD.ORG>
Cc:        mike@smith.net.au (Mike Smith), phk@critter.freebsd.dk, jdp@polstra.com, committers@FreeBSD.ORG, jkh@time.cdrom.com
Subject:   Re: make.conf
Message-ID:  <199808300247.TAA03666@apollo.backplane.com>
References:   <199808300157.SAA26023@hub.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
:	just got to work with a device from Ipsilon (now part of Nokia).
:	its a CheckPoint FireWall-1 running on top of FreeBSD :)
:	The root filesystem is mounted read-only.
:
:	<suggest work for others>
:	rather than addressing make.conf vs make.conf.local,
:	how about taking this issue on...getting us a read-only
:	root filesystem.  it'll take moving all the changing and
:	changeable files to another location with symlinks (ugh)
:	pointing to them...you'll take some heat but the results
:	will be considerably better.
:	</suggest work for others>
:
:jmb

    I'm currently booting a diskless workstation via NFS/BOOTP.  It mounts
    my main server's / and /usr partitions read-only.   Works great!  The
    diskless workstation is even running an almost-complete set of services.

    The only real problem I had was that I had to hook my rc.diskless boot
    script nearer to the beginning of /etc/rc so it wouldn't try to mount
    non-existant disks and such, and the 'xdm' program tries to create
    two log files in /usr/X11R6/lib/X11/xdm somewhere which I had to 
    redirect to /var/run/ using softlinks.

    After that it was just a matter of creating MFS filesystems for /var,
    /var/run, /var/db, /var/tmp, /dev (tty ownership), and /home.

lander:/home/dillon> df
Filesystem        1K-blocks     Used    Avail Capacity  Mounted on
209.157.86.2:/        63503    40282    18141    69%    /
devfs                    16       16        0   100%    dummy_mount
209.157.86.2:/usr    508143   422713    44779    90%    /usr
209.157.86.2:/var     63503    47896    10527    82%    /var
mfs:16                  959       69      814     8%    /var/run
mfs:18                 3935      345     3276    10%    /var/db
mfs:20                31743        9    29195     0%    /var/tmp
procfs                    4        4        0   100%    /proc
mfs:28                 1511       49     1342     4%    /dev
mfs:33                31743     1505    27699     5%    /home

lander:/home/dillon> ps axlww | fgrep mfs
    0    16     1   0  10  0  1536  200 mfsidl SLs   ??    0:01.02 mount_mfs -s 2048 -T qp120at dummy /var/run
    0    18     1   0  10  0  4616  464 mfsidl SLs   ??    0:00.98 mount_mfs -s 8192 -T qp120at dummy /var/db
    0    20     1   0  10  0 33316  148 mfsidl SLs   ??    0:01.27 mount_mfs -s 65536 -T qp120at dummy /var/tmp
    0    28     1   0  10  0  2560  164 mfsidl SLs   ??    0:01.02 mount_mfs -s 4096 -i 512 -T qp120at dummy /dev
    0    33     1   0  10  0 33316  920 mfsidl SLs   ??    0:01.33 mount_mfs -s 65536 -T qp120at dummy /home
  101  1429  1424  12   2  0   272  160 sbwait D+    p4    0:00.01 fgrep mfs
lander:/home/dillon> 

    I'm using persistent MFS mounts on two of the partitions... I've got a
    number of MFS-related patches which I haven't commited yet that allows
    for persistent backing store (and, in fact, you can even fsck the 
    backing store file prior to MFS-mounting it!  Hoa!), and one that deals
    with MFS-related paging issues.  But even without the hacks it can be
    made to work quite well.

						-Matt

    Matthew Dillon  Engineering, HiWay Technologies, Inc. & BEST Internet 
                    Communications
    <dillon@backplane.com> (Please include original email in any response)    



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808300247.TAA03666>