From owner-freebsd-small Tue Jul 20 19:44: 2 1999 Delivered-To: freebsd-small@freebsd.org Received: from mta1.snfc21.pbi.net (mta1.snfc21.pbi.net [206.13.28.122]) by hub.freebsd.org (Postfix) with ESMTP id 767CA15461 for ; Tue, 20 Jul 1999 19:43:54 -0700 (PDT) (envelope-from austsoft@jps.net) Received: from seinfeld (adsl-216-102-199-166.dsl.snfc21.pacbell.net [216.102.199.166]) by mta1.snfc21.pbi.net (8.9.3/8.9.3) with SMTP id TAA20665 for ; Tue, 20 Jul 1999 19:43:39 -0700 (PDT) Message-ID: <000001bed322$94306160$0100a8c0@seinfeld> Reply-To: "Austin Cross" From: "Austin Cross" To: Subject: Date: Tue, 20 Jul 1999 18:05:29 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe austsoft@jps.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Jul 20 20:40:39 1999 Delivered-To: freebsd-small@freebsd.org Received: from daedal.oneway.com (daedal.oneway.com [205.252.89.49]) by hub.freebsd.org (Postfix) with ESMTP id 5640614D6E for ; Tue, 20 Jul 1999 20:40:36 -0700 (PDT) (envelope-from jay@oneway.com) Received: from localhost (jay@localhost) by daedal.oneway.com (8.9.1/8.9.1) with ESMTP id XAA01564; Tue, 20 Jul 1999 23:39:55 -0400 (EDT) (envelope-from jay@oneway.com) Date: Tue, 20 Jul 1999 23:39:55 -0400 (EDT) From: Jay Kuri To: freebsd-small@freebsd.org Subject: Re: Small installation (8M flash) In-Reply-To: <19990720203549.A8116@palomine.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, So in answer to my own question... a combination. The PicoBSD release build mechanism works... (You have to make changes to the stage1 and stage3 to make your filesystem larger) The problem is that you can't dd the image onto the flash. Something about it is not right, and hence it does not boot. I suspect it has mostly to do with the percieved geometry of the flash (ide) drive as apposed to the expected FD geometry. In any case, you can partition and newfs the flash seperately and then do a spiffy vnconfig -a /dev/rvn0 picobsd.bin and then mount the image. Then you can tar up the contents and drop them onto your newly partitioned (now bootable) flash disk. When you try to boot from it it will work. sortof. You have to go into all of the startup scripts (and the kernel) to tell it about your IDE controller, so that it loads the root-info from the flash instead of trying to pull it off the floppy drive. I'll post more about my experiences with this later. When I tried to build the net picobsd floppy (under 3.2)... I got all kinds of errors when it started building the crunched utilities. Lots of linking errors.. undefined symbols. I chased them down. They are all related to password-related utils (passwd, pwd_mkdb, login). Missing -lpam -lradius -ltacplus -lskey -lmd. Unfortunately, even after all of these are added, it still has some problems with MD4Init, etc. Anyone seen this problem before? This is on a fresh 3.2-RELEASE installation, BTW, installed just for this purpose. Jay > Hi there, > > I noticed that nobody has responded (publically) to your message. Have you > learned anything further? > > I've found Sandisk 20MB Flash Drives for about $95 (U.S.). This seems gigantic, > considering that PicoBSD fits on a 1.44MB floppy, and it seems that one ought > to be able to put an installation of FreeBSD that does firewalling and NAT and > the like on one without the compromises that PicoBSD makes. Unfortunately I, > like you, don't know how to go about it. It would seem to be a matter of > copying a bunch of files from an already installed system, assuming you knew > which bunch of files you needed to copy. I may attempt some trail-and-error > installations and see what happens. > > If you learn anything else, I'd appreciate it if you'd let me (or the > freebsd-small list) know. I'll do the same. > > Thanks! > > Chris Johnson > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Jul 21 11:48: 9 1999 Delivered-To: freebsd-small@freebsd.org Received: from daedal.oneway.com (daedal.oneway.com [205.252.89.49]) by hub.freebsd.org (Postfix) with ESMTP id 8530514CC0 for ; Wed, 21 Jul 1999 11:47:58 -0700 (PDT) (envelope-from jay@oneway.com) Received: from localhost (jay@localhost) by daedal.oneway.com (8.9.1/8.9.1) with ESMTP id OAA08589 for ; Wed, 21 Jul 1999 14:46:51 -0400 (EDT) (envelope-from jay@oneway.com) Date: Wed, 21 Jul 1999 14:46:51 -0400 (EDT) From: Jay Kuri To: freebsd-small@freebsd.org Subject: Patch to PicoBSD net to fix pam stuff In-Reply-To: <199907211311.JAA25142@Aries.utstar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Aha. Found the two problems that prevent building net properly. In the Makefile file, NOPAM is defined. It should be NO_PAM. Also, in crunch.conf, -lradius needs to be added to the libs. patch follows. Jay *** Makefile.orig Wed Jul 21 11:47:43 1999 --- Makefile Wed Jul 21 11:47:51 1999 *************** *** 12,18 **** fi @cat crunch.conf|sed -e "s@/usr/src@${SRC}@" >crunch1.conf @crunchgen ./crunch1.conf ! @${MAKE} -f crunch1.mk -DNOPAM all \ "CFLAGS=${CFLAGS} -DCRUNCHED_BINARY -DNOSECURE -DNOCRYPT" #2>&1 >/dev/null clean: --- 12,18 ---- fi @cat crunch.conf|sed -e "s@/usr/src@${SRC}@" >crunch1.conf @crunchgen ./crunch1.conf ! @${MAKE} -f crunch1.mk -DNO_PAM all \ "CFLAGS=${CFLAGS} -DCRUNCHED_BINARY -DNOSECURE -DNOCRYPT" #2>&1 >/dev/null clean: *** crunch.conf.orig Wed Jul 21 11:48:40 1999 --- crunch.conf Wed Jul 21 11:48:23 1999 *************** *** 41,44 **** libs -lncurses -lmytinfo -lipx -lz -lpcap -lalias -lwrap libs -ledit -lutil -lmd -lcrypt -lmp -lgmp -lm -lkvm ! libs -lgnuregex -ltelnet --- 41,44 ---- libs -lncurses -lmytinfo -lipx -lz -lpcap -lalias -lwrap libs -ledit -lutil -lmd -lcrypt -lmp -lgmp -lm -lkvm ! libs -lgnuregex -ltelnet -lradius To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat Jul 24 11:32:15 1999 Delivered-To: freebsd-small@freebsd.org Received: from astart2.astart.com (astart2.astart.com [206.71.174.194]) by hub.freebsd.org (Postfix) with ESMTP id 63B0F15132 for ; Sat, 24 Jul 1999 11:32:11 -0700 (PDT) (envelope-from papowell@astart.com) Received: from h4.private (papowell@h4.private [10.0.0.4]) by astart2.astart.com (8.9.3/8.9.3) with ESMTP id LAA00501 for ; Sat, 24 Jul 1999 11:30:41 -0700 (PDT) Received: (from papowell@localhost) by h4.private (8.9.3/8.9.3) id LAA25306 for freebsd-small@FreeBSD.ORG; Sat, 24 Jul 1999 11:29:49 -0700 (PDT) Date: Sat, 24 Jul 1999 11:29:49 -0700 (PDT) From: papowell@astart.com Message-Id: <199907241829.LAA25306@h4.private> To: freebsd-small@FreeBSD.ORG Subject: picobsd-MOD.1.0.1 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK OK, I published the set of changes I made to picoBSD - now uses Makefiles - has a very sophisticated (stop snickering back there) way to specify files to be put on the MFS file system - you can build a single image (MFS in kernel image), a two file image (kernel, MFS in separate files), and two floppies (kernel and /boot stuff on one floppy, MFS and /etc... stuff on other floppy) by just setting a couple of flags. - way things are built is specified in a CONFIG file, make CONFIG=filename (filename is CONFIG by default) Well, I needed to build another floppy with some more stuff on it, and discovered a couple of ummm....uuhh.. bugs... in the Makefiles. Having a few minutes to spare, I fixed up a couple of things, including adding 'distclean', making the dependencies better so that less gets rebuilt when you modify a file, and stuff gets rebuilt when you do. Get the distribution from: ftp://ftp.astart.com/pub/LPRng/PICOBSD/picobsd-MOD.1.0.1.tgz Note 1: You can now put MFS_ADDITIONS=filename and the make commands in filename will be executed just before the MFS system build completes. This allows you to mangle, molest, and corrupt the standard MFS build in ways suitable for the 'dial' or other things. It is also a nice place to try to put files or executables which crunch does not handle. Remember to static link these. You can also do FLOPPY_ADDITIONS=filename and have some files added to the floppy. Enjoy. Patrick Powell Astart Technologies, papowell@astart.com 9475 Chesapeake Drive, Suite D, Network and System San Diego, CA 92123 Consulting 619-874-6543 FAX 619-279-8424 LPRng - Print Spooler (http://www.astart.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message