From owner-freebsd-small Sun Jun 3 7:41:27 2001 Delivered-To: freebsd-small@freebsd.org Received: from nwlynx.network-lynx.net (nwlynx.network-lynx.net [63.122.185.99]) by hub.freebsd.org (Postfix) with ESMTP id 0654337B401 for ; Sun, 3 Jun 2001 07:41:25 -0700 (PDT) (envelope-from Don@Silver-Lynx.com) Received: from Silver-Lynx.com (doze-1.network-lynx.net [63.122.185.106]) by nwlynx.network-lynx.net (8.11.1/8.9.3/Who.Cares) with ESMTP id f53Efvj29130 for ; Sun, 3 Jun 2001 08:41:57 -0600 (MDT) (envelope-from Don@Silver-Lynx.com) Message-ID: <3B1A4C90.31B07636@Silver-Lynx.com> Date: Sun, 03 Jun 2001 08:41:20 -0600 From: Don Wilde X-Mailer: Mozilla 4.72 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-small@freebsd.org Subject: Re: picobsd available for download? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG s wrote: > > i dont think people actually use picobsd anymore :) > We use it the way it's intended to be used... by modifying the configs in /usr/src/release/picobsd and subs and rolling our own custom version that fits our needs. It's not THAT difficult, and the guys (Thank you, Luigi!) who are actively working with it and (unlike me) understand the inner structure and source are more than willing to help you get it to compile. -- Don Wilde http://www.Silver-Lynx.com Silver Lynx Embedded Microsystems Architects 2218 Southern Bl. Ste. 12 Rio Rancho, NM 87124 505-891-4175 FAX 891-4185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sun Jun 3 8:17:50 2001 Delivered-To: freebsd-small@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id 5F92037B401 for ; Sun, 3 Jun 2001 08:17:35 -0700 (PDT) (envelope-from oppermann@monzoon.net) Received: (qmail 33371 invoked from network); 3 Jun 2001 15:16:29 -0000 Received: from unknown (HELO monzoon.net) ([62.48.0.122]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 3 Jun 2001 15:16:29 -0000 Message-ID: <3B1A54C1.65CB6B2@monzoon.net> Date: Sun, 03 Jun 2001 17:16:17 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-small@freebsd.org Subject: VN device and dd disk images Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello I want to install 128MB SanDisk instead of an IDE HDD in some of my machines. The 128MB are enough to place a reduced but otherwise normal FreeBSD on it. (So no need for PicoBSD). I've got all that done and my prototype SanDisk is running fine. Now for deployment I simply have a machine with a HDD and dd the whole SanDisk into a file and do it vice versa to make a new SanDisk for deployment. All fine and good until I want to update some of the programs in the dd image of the original SanDisk. Now the idea of using the vn device crossed my mind. Unfortunatly for some reason I'm unable to mount the /dev/vn0 device, either because superblock not found or no permission. Might it be that I did the dd image the wrong way? Which device do I have to dd from the SanDisk to use the image for vn? Will I still be able to dd that file back to a virgin SanDisk and boot directly from it without any modification? Any pointers very appreciated. -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sun Jun 3 13:53:19 2001 Delivered-To: freebsd-small@freebsd.org Received: from comp1.mastery.ca (comp1.mastery.ca [209.202.88.60]) by hub.freebsd.org (Postfix) with ESMTP id 08FE737B401 for ; Sun, 3 Jun 2001 13:53:17 -0700 (PDT) (envelope-from mail@max-info.net) Received: from 78kw954 (dyn216-8-130-5.ADSL.mnsi.net [216.8.130.5]) (authenticated) by comp1.mastery.ca (8.11.3/8.11.1) with ESMTP id f53KrEL00500 for ; Sun, 3 Jun 2001 16:53:15 -0400 (EDT) (envelope-from mail@max-info.net) Message-ID: <010d01c0ec6e$ef806260$3200a8c0@Home> From: "Ryan Masse" To: Subject: cannot compile picoBSD from 4.3-RELEASE CVS Date: Sun, 3 Jun 2001 16:50:05 -0400 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm trying to compile the 'net' picoBSD version from my build box running FreeBSD 4.3-RELEASE. I have the entire /usr/src tree extracted in which i proceed to run /usr/src/release/picobsd/build/picobsd choosing the 'net' version then do a build. I get the below error during the process. i have yet get though a complete build with or withought using a custom kernel config. I've tried this process on multiple release on multiple boxes so i'm assuming i'm missing a key step. Anyone have any ideas to what i'm doing wrong? udp.o' is up to date. `vjcomp.o' is up to date. `minigzip.o' is up to date. crunchgen: /root/build_dir-net/crunch1.conf:19: `../../tinyware' is not a directory, skipping it usage: cp [-R [-H | -L | -P]] [-f | -i] [-pv] src target cp [-R [-H | -L | -P]] [-f | -i] [-pv] src1 ... srcN directory lan2# Thanks, Ryan Masse To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Jun 4 9: 1:34 2001 Delivered-To: freebsd-small@freebsd.org Received: from dsl3i239.cruzio.com (dsl3i239.cruzio.com [205.179.211.239]) by hub.freebsd.org (Postfix) with ESMTP id 2ED5637B401 for ; Mon, 4 Jun 2001 09:01:32 -0700 (PDT) (envelope-from brucem@dsl3i239.cruzio.com) Received: (from brucem@localhost) by dsl3i239.cruzio.com (8.11.3/8.11.3) id f54Fmq600482 for freebsd-small@freebsd.org; Mon, 4 Jun 2001 08:48:52 -0700 (PDT) (envelope-from brucem) Date: Mon, 4 Jun 2001 08:48:52 -0700 (PDT) From: "Bruce R. Montague" Message-Id: <200106041548.f54Fmq600482@dsl3i239.cruzio.com> To: freebsd-small@freebsd.org Subject: re: "net" 4.3 PicoBSD build Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG See: http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=107436+109534+/usr/local/www/db/text/2001/freebsd-small/20010318.freebsd-small Hope this helps... On second thought (sorry for the repeat): ------------- The "tinyware" utilities are not included in the current 4.3 Beta picobsd "net" crunchgen, although the /bin links are created. This means that attempting to invoke "vm", "dmesg", "ps", and "netstat" returns an error of the form: "crunch1: ps not compiled in." The build produces the following error: "crunchgen: /usr/src/release/picobsd/build/build_dir-net/crunch1.conf:19: `../../tinyware' is not a directory, skipping it" and "ignoring program because of errors" for the following tinyware pgms: vm msg sps ns The fix appears simply to use the absolute path to tinyware, similar to what is done in the other "crunch.conf" files, that is: "srcdirs /usr/src/release/picobsd/tinyware" instead of: "srcdirs ../../tinyware" ----- --- crunch.cong.original Wed Mar 14 21:35:27 2001 +++ crunch.conf Wed Mar 14 21:37:46 2001 @@ -16,7 +16,7 @@ srcdirs /usr/src/usr.sbin srcdirs /usr/src/libexec # sources for ns & vm -srcdirs ../../tinyware +srcdirs /usr/src/release/picobsd/tinyware ----- The "crunch.conf" files in the picobsd subdirs for the "bridge", "dial", "isp", and "router" types all specify the absolute path. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Jun 6 7: 8:43 2001 Delivered-To: freebsd-small@freebsd.org Received: from tao.org.uk (genesis.tao.org.uk [212.135.162.62]) by hub.freebsd.org (Postfix) with ESMTP id A81EE37B405 for ; Wed, 6 Jun 2001 07:08:29 -0700 (PDT) (envelope-from joe@tao.org.uk) Received: by tao.org.uk (Postfix, from userid 100) id A209A521; Mon, 4 Jun 2001 19:31:47 +0100 (BST) Date: Mon, 4 Jun 2001 19:31:47 +0100 From: Josef Karthauser To: Paul Jansen Cc: small@freebsd.org Subject: Re: picobsd available for download? Message-ID: <20010604193147.D30534@tao.org.uk> References: <20010601165614.15133.qmail@web5104.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="+KJYzRxRHjYqLGl5" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010601165614.15133.qmail@web5104.mail.yahoo.com>; from vlaero@yahoo.com.au on Sat, Jun 02, 2001 at 02:56:14AM +1000 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --+KJYzRxRHjYqLGl5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Jun 02, 2001 at 02:56:14AM +1000, Paul Jansen wrote: > Are there versions of PicoBSD available for download > anywhere? The website has an old .04 version and it's > been that way for years. > Are there plans to make images available anywhere? > I'm interested in a recent version of the NET floppy. PicoBSD has been maintained in the FreeBSD tree for a number of years and take a look in /usr/src/release/picobsd now. Install a recent copy of FreeBSD-stable including the source code Joe --+KJYzRxRHjYqLGl5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjsb1BIACgkQXVIcjOaxUBbaXACdEEdfcCrnyi23uWFO2yxNU/31 FnAAoKhnwY/tGoz+nZovxKfSupFZ9a0p =C8LE -----END PGP SIGNATURE----- --+KJYzRxRHjYqLGl5-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Jun 8 10:20:38 2001 Delivered-To: freebsd-small@freebsd.org Received: from ns2.sysadmin-inc.com (ns2.sysadmin-inc.com [209.16.228.145]) by hub.freebsd.org (Postfix) with SMTP id 2CECE37B407 for ; Fri, 8 Jun 2001 10:20:36 -0700 (PDT) (envelope-from peter@sysadmin-inc.com) Received: (qmail 57969 invoked by alias); 8 Jun 2001 17:20:35 -0000 Received: from unknown (HELO w2kstest) (10.10.1.70) by ns2.sysadmin-inc.com with SMTP; 8 Jun 2001 17:20:35 -0000 From: "Peter Brezny" To: Subject: updating kernel parameters. Date: Fri, 8 Jun 2001 13:19:54 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The picobsd-net disk I compiled from a 4.3 machine I updated yesterday doesn't seem to be able to update the kerel parameters file, or files change in the /etc dir. /stand/update says it's 'done' but a reboot from the disk doesn't have the chagnes (from the kernel config in the beginning or any changes made afterwards). Any Ideas on why update doesn't work? TIA Peter Brezny SysAdmin Services Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Jun 8 10:44:36 2001 Delivered-To: freebsd-small@freebsd.org Received: from ns2.sysadmin-inc.com (ns2.sysadmin-inc.com [209.16.228.145]) by hub.freebsd.org (Postfix) with SMTP id 6DE1D37B403 for ; Fri, 8 Jun 2001 10:44:31 -0700 (PDT) (envelope-from peter@sysadmin-inc.com) Received: (qmail 58242 invoked by alias); 8 Jun 2001 17:44:30 -0000 Received: from unknown (HELO w2kstest) (10.10.1.70) by ns2.sysadmin-inc.com with SMTP; 8 Jun 2001 17:44:30 -0000 From: "Peter Brezny" To: Subject: writing/getting kernel configs into flopy. Date: Fri, 8 Jun 2001 13:43:50 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've got a machine I want to use with picobsd that has some isa nic's in it. However, i have not figured out a way to convince picobsd to save the kernel configuration I put into it on boot. I get the feeling there is a way to write a kernel config file by hand, and put it somewhere to be compiled into the build of the disk image, however, I've never written a kernel config file by hand and don't know where to start, or where to place it once i've got one. Could someone forward some pointers? TIA Peter Brezny SysAdmin Services Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Jun 8 14:19:40 2001 Delivered-To: freebsd-small@freebsd.org Received: from ns2.sysadmin-inc.com (ns2.sysadmin-inc.com [209.16.228.145]) by hub.freebsd.org (Postfix) with SMTP id 5D8F137B405 for ; Fri, 8 Jun 2001 14:19:37 -0700 (PDT) (envelope-from peter@sysadmin-inc.com) Received: (qmail 62248 invoked by alias); 8 Jun 2001 21:19:36 -0000 Received: from unknown (HELO test) (10.10.1.20) by ns2.sysadmin-inc.com with SMTP; 8 Jun 2001 21:19:36 -0000 From: "Peter" To: Subject: firewall rules not loading. Date: Fri, 8 Jun 2001 17:18:47 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've managed to get things a little closer to running, and even have a functioning network on the 'net' version of picobsd, however I'm having problems getting it to read my firewall script. I wrote my own and put it in the same way I have in the past with full blown versions of freebsd, but it doesn't seem to be working. I can load the script manually after picobsd is up, and it works. I've attached my rc.conf below. Any comments are welcome. TIA Peter Brezny purplecat.net #!/bin/sh # $FreeBSD: src/release/picobsd/net/floppy.tree/etc/rc.conf,v 1.6 1999/08/28 01:33:41 peter Exp $ swapfile="/swap" # Set to name of swapfile if aux swapfile desired. ### Network configuration sub-section ###################### ### Basic network options: ### hostname="newlife.fire.sysadmin-inc.com" # Set this! tcp_extensions="NO" # Allow RFC1323 & RFC1644 extensions (or NO). network_interfaces="lo0 ep0 ed0" # List of network interfaces (lo0 is loopback). ifconfig_lo0="inet 127.0.0.1" # default loopback device configuration. ifconfig_ep0="inet 10.30.1.40/24" ifconfig_ed0="inet 10.20.40.1/24" #ifconfig_lo0_alias0="inet 127.0.0.254 netmask 0xffffffff" # Sample alias entry. ### Network daemons options: ### inetd_enable="YES" # Run the network daemon dispatcher (or NO) inetd_flags="" # Optional flags to inetd snmpd_enable="NO" # Run the SNMP daemon (or NO) snmpd_flags="-C -c /etc/snmpd.conf" # Optional flags to snmpd ### Network routing options: ### defaultrouter="10.30.1.1" # Set to default gateway (or NO). static_routes="" # Set to static route list (or leave empty). gateway_enable="YES" # Set to YES if this host will be a gateway. arpproxy_all="" # replaces obsolete kernel option ARP_PROXYALL. # Firewall Options firewall_enable="YES" natd_enable="YES" natd_interface="ep0" firewall_script="/etc/rc.firewall.pico" ### Allow local configuration override at the very end here ## if [ -f /etc/rc.conf.local ]; then . /etc/rc.conf.local fi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Jun 8 19:23: 6 2001 Delivered-To: freebsd-small@freebsd.org Received: from dsl3i239.cruzio.com (dsl3i239.cruzio.com [205.179.211.239]) by hub.freebsd.org (Postfix) with ESMTP id 887B637B405 for ; Fri, 8 Jun 2001 19:22:58 -0700 (PDT) (envelope-from brucem@dsl3i239.cruzio.com) Received: (from brucem@localhost) by dsl3i239.cruzio.com (8.11.3/8.11.3) id f592AB900946 for freebsd-small@freebsd.org; Fri, 8 Jun 2001 19:10:11 -0700 (PDT) (envelope-from brucem) Date: Fri, 8 Jun 2001 19:10:11 -0700 (PDT) From: "Bruce R. Montague" Message-Id: <200106090210.f592AB900946@dsl3i239.cruzio.com> To: freebsd-small@freebsd.org Subject: Dirty PicoBSD build notes. Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG re: > I get the feeling there is a way to write > a kernel config file by hand... Very quick, very dirty, verify before use PicoBSD customization doc. Many who know a lot more may have some better input. ------- * Assure you have a version of the host FreeBSD system with the "vn" device in its config file: "pseudo-device vn" You may have to rebuild the "/dev/vn*" dir entries... ------- * cd "/usr/src/release/picobsd" and create a new dir with the name you want for "your" picobsd system. Into this dir, copy one of the existing template picobsd config dir's contents. The templates are also in "/usr/src/release/picobsd"; they are "bridge", "custom", "net", "dial", "install", "isp", and "router". I think I've typically used bridge, net, and router. These may not work "as-is", treat them as starter kits. You may want to test their state by building your starter kit. To build the picobsd kit in subdir "router", for instance: >su >cd /usr/src/release/picobsd/build >set path = (. $path) >picobsd router Insert a floppy and hit return twice at the two menus. After a successful picobsd build, in addition to putting a bootable image on the floppy, there will be a bootable file named "kernel" in "/usr/src/release/picobsd/build/build_dir-router" and a binary image of the bootable floppy in "picobsd.bin" in the same subdir. The subdir name will depend on the name of your conf dir. PicoBSD puts all executables and an image of a RAM-based root filesystem into a single "kernel" ELF file. The "kernel" file in the _floppy image_ is compressed (PicoBSD will "uncompress itself" on boot). The "kernel" file in the subdir is not compressed. If your config dir is named "mysys", you would do a "picobsd mysys" above to build your system. The build results would be left in a subdir named "build_dir-mysys". In your config dir, edit file PICOBSD to contain your desired FreeBSD kernel options and devices, in file "config" add your desired "/dev" device nodes, in file "crunch.conf" put the executables that you want to include. Specify your script files using a subdir named "floppy.tree" in your conf dir (also use file "floppy.tree.exclude" to eliminate files from the default "floppy.tree" in "/usr/src/release/picobsd/"). The files in the subdir "/usr/src/release/picobsd/mfs_mtree" are included in the root file system built into the kernel file using the root tree structure specified by the "mfs.mtree" file in your config directory. ========================================= Elaborations ========================================= ------ * The "/usr/src/release/picobsd/build/picobsd" script does all the heavy lifting. Read this file for the "real" documentation". See the header of this file for usage documentation. This script is, amoung other things, a wrapper for a FreeBSD kernel build. It creates a "virtual disk device" using a file and makes this (file) a bootable FreeBSD (picobsd) disk, by putting a root file system, boot blocks, and a kernel in this "device's" "/" dir. Startup scripts are included in the memory-based filesystem included internal to the kernel itself. ------ * The picoBSD build cycle builds a floppy "image" file and then at the very end does a block-block copy of this image to floppy, using dd (disk dup). You do not need to build or use the floppy image, the "kernel" file can be netbooted, booted from flash, etc.. ------- * As the picobsd script header doc indicates, each picobsd config directory contains: * A FreeBSD kernel config file named "PICOBSD". Edit this to include desired kernel options, in particular you will often want to specify drivers (devices). The "PICOBSD" config file is a normal FreeBSD config file with the addition of a comment line starting with "#PicoBSD". This line is processed as args by the "picobsd" script. * Edit a file named "config" to list device nodes to be created in "/dev". Add any device node names you need to the MY_DEVS string. * Edit the "crunch.conf" file to control the crunchgen of the system image. This indicates which executables to include in the single kernel ELF file. Add "srcdirs", "progs", and "libs" as needed. The "progs" statements specify all the executables that you require. The "srcdirs" are where the program's "Makefile"s are found. The crunchgen in effect renames all the program's "main()"'s and creates a single "main()" with a little stub code that dispatches to the real entry-point based on the arg0 cmd-line name. Because of this, "links" are important in the picobsd file tree (so as to provide desired names). * A default "/usr/src/release/picobsd/floppy.tree" subdir contains files to put in the floppy file system. Each config dir can have a "floppy.tree.exclude" file that indicates paths of default files _not_ to include. Each conf dir can have its own "floppy.tree" subdir tree, containing its own "/etc/rc" and "/etc/rc.filewall" scripts, etc. These "floppy.tree" files are typically "/etc" files that you may want to edit on the floppy. A default "/usr/src/release/picobsd/mfs_tree" contains the files built into the root file system in the kernel image. Each config dir should contain a "mfs.mtree" file which specifies (ala mtree) a map of the directory structure you want to create in the memory-based file system. Once the system boots, the ram file system is volatile and files can be edited, etc.. Such modifications will be lost, of course, at reboot. The floppy can be mounted as a normal filesystem (both from a host and by picobsd after picobsd boots). This enables presistent (re)editing of startup scripts (put "ed" in your crunch.conf if you are a minimalist). Note that there is no easy way to permanently edit a file included in the kernel image (mfs_tree). The current default "rc" scripts in "release/picobsd" copy the /etc files from the floppy into the /etc from the mfs_tree at the start of boot script processing, enabling overwriting a file to be updated. ----- * To completely clean up a picobsd build, for example, after a build using "picobsd net": * cd /usr/src/sys/compile and delete the "PICOBSD-net" build directory. * cd /usr/src/sys/i386/conf and delete the "PICOBSD-net" config file. * cd /usr and delete the "obj-pico" subdirectory. * cd /usr/src/release/picobsd/build and delete the "build_dir-net" subdirectory * cd /tmp and delete the "picobsd.XXXXXXXXXX" (temp name) subdirectory(s). and delete the "reply.XXXXXXXXXX" temporary file(s). Note that only one "obj-pico" subdirectory is created, that is, there are not versions created based on the name of your build. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Jun 8 21:41:19 2001 Delivered-To: freebsd-small@freebsd.org Received: from comp1.mastery.ca (comp1.mastery.ca [209.202.88.60]) by hub.freebsd.org (Postfix) with ESMTP id A600837B403; Fri, 8 Jun 2001 21:41:14 -0700 (PDT) (envelope-from rmasse@mastery.ca) Received: from 78kw954 (dyn216-8-128-63.ADSL.mnsi.net [216.8.128.63]) (authenticated) by comp1.mastery.ca (8.11.3/8.11.1) with ESMTP id f594fDL14262; Sat, 9 Jun 2001 00:41:13 -0400 (EDT) (envelope-from rmasse@mastery.ca) Message-ID: <095201c0f09e$223a02a0$3200a8c0@Home> From: "Ryan Masse" To: Cc: "FreeBSD-Questions" Subject: picobsd image Date: Sat, 9 Jun 2001 00:39:11 -0400 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG someone please take a look at my below steps in creating a picobsd image and tell me what if anything i'm doing wrong. 1. build box = 4.3-RELEASE 2. extracted entire /usr/src tree 3. cd'd to /usr/src/release/picobsd && cp'd -R router test 4. cd'd to /usr/src/release/picobsd/build && ran ./picobsd test 5. left the kernel untouched for test purposes && built the kernel The build process seemed to work for it asked me to insert a floppy to write the picobsd.bin image to disk. I mount the floppy via -t ufs to /mnt and see only a file 'kernel'. From here on in is were i get lost. I was expecting to see directories such as /bin /sbin /etc etc. but all i see is the 'kernel'. I thought maybe this 'kernel' file is another image, so i did vnconfig vn0 kernel then mount /dev/vn0c /mnt but i get invalid super block or similar error. So then i tried dd if=kernel of=/dev/md0 then i try mount /dev/md0c /mnt but i get a Bad block error. I tried booting off of the newly created disk but i get a kernel panic that it can't find /bin /sbin dir and the system enters a continuos loop. I've tried every version included within the picobsd source (dial, net, etc.) with all the same results. Am i missing something? Any help would be much appreciated Thanks, Ryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Jun 8 23:18:43 2001 Delivered-To: freebsd-small@freebsd.org Received: from dsl3i239.cruzio.com (dsl3i239.cruzio.com [205.179.211.239]) by hub.freebsd.org (Postfix) with ESMTP id AD36237B405 for ; Fri, 8 Jun 2001 23:18:41 -0700 (PDT) (envelope-from brucem@dsl3i239.cruzio.com) Received: (from brucem@localhost) by dsl3i239.cruzio.com (8.11.3/8.11.3) id f5965sj05182 for freebsd-small@freebsd.org; Fri, 8 Jun 2001 23:05:54 -0700 (PDT) (envelope-from brucem) Date: Fri, 8 Jun 2001 23:05:54 -0700 (PDT) From: "Bruce R. Montague" Message-Id: <200106090605.f5965sj05182@dsl3i239.cruzio.com> To: freebsd-small@freebsd.org Subject: re: picobsd image Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG re > someone please take a look .... Here's a stab... > I mount the floppy via -t ufs to /mnt and see > only a file 'kernel'. You don't have to mount the floppy after the picobsd script writes it (although it is reassuring to check). You should be able to just boot the floppy that has only the single kernel file "visible". Among other things, this means you can boot a single file and get "everything". > I was expecting to > see directories such as /bin /sbin /etc These dirs/files are "inside" the kernel. You will see them after you boot it. (You can also have other files (or files with the same names as the ones "inside" your kernel) on the floppy, but you don't _need_ them). You cant mount/access/edit the files "inside" the (compressed) kernel file via the mounted floppy. > ((Mount/boot troubles wrt /etc, local vn devices, etc)) On a 4.3-RC system I just built a copy of "router", as you did, and it worked. So, no particular ideas... Maybe delete all the remanants of your last "test" build, and try again. Also, are your host "/dev/vn*" device nodes OK? Perhaps your host "vn" device just never got unmounted, or somesuch?? Sometimes if you get things really hosed messing with mounting, initing, and such, you may want to simply delete the /dev/vn device nodes and recreate them with MAKEDEV. - bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Jun 8 23:33:32 2001 Delivered-To: freebsd-small@freebsd.org Received: from ns2.alphaque.com (ns2.alphaque.com [202.185.254.11]) by hub.freebsd.org (Postfix) with SMTP id 3D71637B403 for ; Fri, 8 Jun 2001 23:33:30 -0700 (PDT) (envelope-from dinesh@alphaque.com) Received: (qmail 20109 invoked from network); 9 Jun 2001 06:33:28 -0000 Received: from ns2.alphaque.com (HELO prophet.alphaque.com) (202.185.254.11) by ns2.alphaque.com with SMTP; 9 Jun 2001 06:33:28 -0000 Received: from localhost (q76o0h@localhost [127.0.0.1]) by prophet.alphaque.com (8.11.3/8.11.3) with ESMTP id f596X2L00594 for ; Sat, 9 Jun 2001 14:33:02 +0800 (MYT) (envelope-from dinesh@alphaque.com) Date: Sat, 9 Jun 2001 14:33:01 +0800 (MYT) From: Dinesh Nair To: freebsd-small@freebsd.org Subject: re: picobsd image In-Reply-To: <200106090605.f5965sj05182@dsl3i239.cruzio.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > I mount the floppy via -t ufs to /mnt and see > > only a file 'kernel'. try redoing this, but this time not mounting the floppy after insertion. the script writes a disk image on the the raw device, and this may fail if the floppy were mounted. --dinesh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat Jun 9 2:10:34 2001 Delivered-To: freebsd-small@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id E469B37B405 for ; Sat, 9 Jun 2001 02:10:30 -0700 (PDT) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id LAA60179; Sat, 9 Jun 2001 11:05:11 +0200 (CEST) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200106090905.LAA60179@info.iet.unipi.it> Subject: Re: Dirty PicoBSD build notes. In-Reply-To: <200106090210.f592AB900946@dsl3i239.cruzio.com> from "Bruce R. Montague" at "Jun 8, 2001 07:10:11 pm" To: "Bruce R. Montague" Date: Sat, 9 Jun 2001 11:05:11 +0200 (CEST) Cc: freebsd-small@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG just a couple of comments (for 4.3 and newer): + you can just copy /usr/src/release/picobsd/build/picobsd into some standard directory in the path (e.g. /usr/bin or /usr/local/bin) to avoid modifying the path; + your picobsd configuration can be anywere -- "picobsd foo" will first look for , and only afterwards will search /usr/src/release/picobsd/`basename ` . A picobsd config is assumed if /PICOBSD is present. Other than that, a pretty good document. Thanks Bruce! cheers luigi > Very quick, very dirty, verify before use PicoBSD > customization doc. Many who know a lot more may > have some better input. -----------------------------------+------------------------------------- Luigi RIZZO, luigi@iet.unipi.it . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Sat Jun 9 15:28:33 2001 Delivered-To: freebsd-small@freebsd.org Received: from fedde.littleton.co.us (cfedde.dsl.frii.net [216.17.139.141]) by hub.freebsd.org (Postfix) with ESMTP id D0B2137B401; Sat, 9 Jun 2001 15:28:28 -0700 (PDT) (envelope-from cfedde@fedde.littleton.co.us) Received: from fedde.littleton.co.us (localhost [127.0.0.1]) by fedde.littleton.co.us (8.11.4/8.11.2) with ESMTP id f59MSLi41514; Sat, 9 Jun 2001 16:28:21 -0600 (MDT) Message-Id: <200106092228.f59MSLi41514@fedde.littleton.co.us> To: "Ryan Masse" Cc: small@FreeBSD.ORG, "FreeBSD-Questions" Subject: Re: picobsd image In-Reply-To: <095201c0f09e$223a02a0$3200a8c0@Home> From: Chris Fedde Date: Sat, 09 Jun 2001 16:28:21 -0600 Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 9 Jun 2001 00:39:11 -0400 "Ryan Masse" wrote: +------------------ | I tried booting off of the newly created disk but i get a kernel panic that | it can't find /bin /sbin dir and the system enters a continuos loop. | | I've tried every version included within the picobsd source (dial, net, | etc.) with all the same results. Am i missing something? | | Any help would be much appreciated +------------------ Just to check this out I tried with my recently cvsup'd src directory (june 4 or so) and had no problems building a copy of the router configuration. It worked on the first try once I got a floppy disk that passed the fdformat test. -- Chris Fedde To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message