Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 15 Mar 2001 16:16:15 +1100
From:      Murray Taylor <mtaylor@bytecraft.com.au>
To:        "'freebsd-small@freebsd.org'" <freebsd-small@freebsd.org>, "'freebsd-questions@freebsd.org'" <freebsd-questions@freebsd.org>
Subject:   PicoBSD Bridge build breaks on 'MFS filesystem signature not foun d in kernel'
Message-ID:  <710709BB8B02D311942E006067441810544294@MELEXC01>

next in thread | raw e-mail | index | archive | help
I am attempting to build a picoBSD Bridge using the attached files and it
breaks at the
almost last step with the message

'MFS filesystem signature not found in kernel'

from the write_mfs_in_filesystem.c program

Other environmental conditions ....
Using 4.2-Stable cvsupped 13/mar/2001
make world done
Not yet installed newly rebuilt kernel as system is still being used in
production
but have done a 'make' in the kernel build directory OK

I am using 
./picobsd --floppy_size 1440 -v build
as the command

and am setting MFS bytes/inode to 4096
and MFS size to 2000
via the dialogue box

I have changed all ${TYPE} to $THETYPE} as TYPE was never setup anywhere
and added the -s labels option to the vnconfig lines
throughout the picobsd script.

Any suggestions???

Murray Taylor
Project Engineer

Bytecraft P/L	+61 3 9587 2555
		+61 3 9587 1614 fax
		mtaylor@bytecraft.com.au


===== bridge/PICOBSD file ==========
#
# $FreeBSD: src/release/picobsd/bridge/PICOBSD,v 1.1.4.3 2001/01/29 22:40:02
luigi Exp $
#
# Line starting with #PicoBSD contains PicoBSD build parameters
#marker         def_sz  init    MFS_inodes      floppy_inodes
#PicoBSD	1440	init	8192		32768
options MD_ROOT_SIZE=1440      # same as def_sz

# next to each option there is the approx. space used in the
# picobsd image.

machine		i386
cpu		I386_CPU
cpu		I486_CPU
cpu		I586_CPU
#cpu		I686_CPU
ident		PICOBSD
maxusers	20

options		INET			#InterNETworking
options		FFS			#Berkeley Fast Filesystem
options		FFS_ROOT		#FFS usable as root device [keep
this!]
#options		BOOTP
options		MFS			#Memory Filesystem
options		MD_ROOT		#MFS as root
options		COMPAT_43		#Compatible with BSD 4.3 [KEEP
THIS!]

#options	MSDOSFS		#MSDOS Filesystem
#options	CD9660		#ISO 9660 Filesystem, 12KB
#options	PROCFS		#Process filesystem, 4KB
options	USERCONFIG		#boot -c editor, 4KB
options	INTRO_USERCONFIG	#imply -c and parse info area
options	VISUAL_USERCONFIG	#visual boot -c editor

options		IPFIREWALL
options		IPFIREWALL_DEFAULT_TO_ACCEPT
options		IPDIVERT # divert (for natd, 4KB)
#options	DEVFS
options		PCI_QUIET
# Support for bridging and bandwidth limiting
options	DUMMYNET
options	BRIDGE
options	HZ=1000
options NMBCLUSTERS=4096

#config		kernel	root on fd0a

device	isa0
device	pci0

device		fdc0	at isa? port IO_FD1 irq 6 drq 2
device		fd0	at fdc0 drive 0

#device ata0	at isa? port IO_WD1 irq 14
#device ata1	at isa? port IO_WD2 irq 15
#device ata
#device atadisk
#device	atapicd	# 8KB

# atkbdc0 controls both the keyboard and the PS/2 mouse
device	atkbdc0	at isa? port IO_KBD
device		atkbd0	at atkbdc? irq 1
#device          psm0    at atkbdc? irq 12 # 8KB

device		vga0	at isa?

# syscons is the default console driver, resembling an SCO console
device		sc0	at isa?

device		npx0	at nexus? port IO_NPX irq 13

device		sio0	at isa? port IO_COM1 flags 0x10 irq 4
device		sio1	at isa? port IO_COM2 irq 3

# device ppc0	at isa? port? flags 0x40 irq 7
# device	ppbus0
# device		nlpt0	at ppbus?
# device		plip0	at ppbus?
# device		ppi0	at ppbus?

#
# The following Ethernet NICs are all PCI devices.
#
device	miibus 
device de0              # DEC/Intel DC21x4x (``Tulip'')
#device	fxp0             # Intel, 4KB
#device	xl0		# 3Com
#device	ep0
#device rl0		# Realtek 8139, 4KB
#device dc0		# New Dec/Intel DC21x4x, 8KB

#device ed0 at isa? port 0x280 irq 5 iomem 0xd8000
#device ed1 at isa? port 0x300 irq 5 iomem 0xd0000

pseudo-device	loop
pseudo-device	ether
pseudo-device	tun	2	# 4KB, for ppp
#pseudo-device	vn
pseudo-device	pty	16
pseudo-device	md		# memory disk

#options	MATH_EMULATE		#Support for x87 emulation, 4KB
pseudo-device	bpf 4	# 4KB, for tcpdump
#options	NFS			#Network Filesystem
#options	NFS_NOSERVER		#Network Filesystem
options		DDB


====== bridge/config file =============
# configuration for picobsd build script.
# it should only contain variable definitions -- it is sourced
# by the shell much like rc.conf* files

MY_DEVS="std tun2 vty10 fd0 ad0 pty0 cuaa0 cuaa1 bpf0 bpf1 bpf2"

======= bridge/crunch.conf file ========
#
# $FreeBSD: src/release/picobsd/bridge/crunch.conf,v 1.1.2.1 2001/02/19
23:24:30 luigi Exp $
#
# configuration file for "bridge" floppy.
# Depending on your needs, almost surely you will need to
# modify your configuration to add/remove/change programs used in
# the floppy image. Remember that some programs also require
# matching kernel options to enable device drivers etc.
#
# Next to most of the programs i have tried to indicate the approximate
# space consumed, but beware that these values change from release
# to release, and might depend on the presence of other programs which
# share the same libraries.
#
# NOTE: the string "/usr/src" will be automatically replaced with the
# correct value set in 'build' script - you should change it there

# Default build options. Basically tell the Makefiles which understand
# that to use the most compact possible version of the code.
#
buildopts -DNOPAM -DRELEASE_CRUNCH -DNONETGRAPH -DNOIPSEC -DNOINET6

# directories where to look for sources of various binaries.
srcdirs /usr/src/bin
srcdirs /usr/src/sbin/i386
srcdirs /usr/src/sbin
srcdirs /usr/src/usr.bin
srcdirs /usr/src/gnu/usr.bin
srcdirs /usr/src/usr.sbin
srcdirs /usr/src/libexec
# Some programs are especially written for PicoBSD and reside here
srcdirs /usr/src/release/picobsd/tinyware
#
# And there are others (mostly ports) which reside in their specific
# directories. For them, we use the "special" commands to tell
# crunchgen where to look for sources, objects, which Makefile
# variables contain the list of sources and objects, and so on.

# init is almost always necessary.
progs init # 4KB.
# fsck is almost always necessary, unless you have everything on the
# image and use 'tar' or something similar to read/write raw blocks
# from the floppy.
progs fsck # 24KB.
# ifconfig is needed if you want to configure interfaces...
progs ifconfig # 4KB.
#
# You will also need a shell and a bunch of utilities.
# The standard shell is not that large, but you need many
# external programs. In fact most of them do not take much space
# as they merely issue a system call, and print the result; the
# libraries are already needed anyways, so they end up using almost
# no additional memory.
# There are a few exceptions such as 'less', which in 4.x is
# rather large.
progs sh # 36KB.
ln sh -sh
progs echo # 0KB.
progs pwd
progs mkdir rmdir
progs chmod chown
progs mv ln # 0KB.
progs mount
progs minigzip # 0KB.
ln minigzip gzip
progs cp # 0KB.
progs rm
progs ls
progs kill
progs df # 0KB.
progs ps # 4KB.
progs ns # 4KB.
ln ns netstat
progs vm # 0KB.
progs cat # 0KB.
progs test # 0KB.
ln test [
progs hostname # 0KB.
progs login # 4KB.
progs getty # 4KB.
progs stty # 4KB.
progs w # 0KB.
progs msg # 0KB.
ln msg dmesg
progs kget # 0KB.
progs reboot # 0KB.
progs less # 36KB
ln less more
#progs more # 12KB
#special more srcdir /usr/ports/picobsd/more

progs sysctl
progs swapon # 0KB.
progs pwd_mkdb # 0KB.
progs dev_mkdb # 0KB.
progs umount
progs mount_std
progs du # 0KB.
progs tail # 0KB.
progs tee # 0KB.
progs passwd # 0KB.

progs route # 8KB
# progs mount_msdos
# progs comcontrol
#
# If you want to run natd, remember the alias library
#progs natd # 20KB
#libs -lalias	# natd
#
# ppp is rather large. Note that as of Jan.01, RELEASE_CRUNCH
# makes ppp not use libalias, so you cannot have aliasing.
#progs ppp # 112KB

# You need an editor. ee is relatively small, though there are
# smaller ones. vi is much larger.
# The editor also usually need a curses library.
progs ee # 32KB.
libs -lncurses
# progs vi # ??
# libs -lcurses # for vi

#progs tcpdump # 100KB.
#special tcpdump srcdir /usr/src/usr.sbin/tcpdump/tcpdump

progs arp # 0KB.

progs disklabel # 4KB.
progs fdisk # 4KB.
progs vnconfig # 0KB.

progs grep # 16KB.
progs date # 4KB.
progs mount_nfs # 0KB.
ln mount_nfs nfs
progs ping # 4KB.
#progs routed # 32KB.
progs ipfw # 12KB.
progs traceroute # 0KB.
# progs mount_cd9660 # 4KB.
# ln mount_cd9660 cd9660
# progs newfs # 12KB.
#ln newfs mount_mfs
ln chown chgrp
# ln mount_msdos msdos
ln mount_std procfs
ln mount_std mount_procfs

# If you need to access the box remotely, and maybe copy files
# from/to it, you can use telnet, rsh or ssh.
# inetd is only needed for telnet and rshd
progs inetd # 12KB.
progs telnet # 20KB.
progs telnetd # 12KB.
#progs ftp # 28KB.
#progs tar # 32KB.

# Check the ssh license! If you want to use this,
# go to /usr/ports/security/ssh-picobsd, do a make extract configure
#progs sshd	# includes ssh and scp
special sshd objvar SSHD_OBJS
special sshd srcdir /usr/ports/picobsd/ssh-picobsd/work/ssh-1.2.27
special sshd objdir /usr/ports/picobsd/ssh-picobsd/work/ssh-1.2.27

### ee uses ncurses instead of curses
libs -ledit -lutil -lmd -lcrypt -lmp -lgmp -lm -lkvm
libs -lmytinfo -lipx -lz -lpcap -lwrap
libs -ltermcap -lgnuregex -ltelnet # -lcurses

======= bridge/floppy.tree.exclude file ======
etc/snmpd.conf
etc/ppp

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-small" in the body of the message




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