From owner-freebsd-small Mon Jun 17 8:58:21 2002 Delivered-To: freebsd-small@freebsd.org Received: from elam.kais.kyoto-u.ac.jp (elam.kais.kyoto-u.ac.jp [130.54.60.9]) by hub.freebsd.org (Postfix) with ESMTP id BE44337B414 for ; Mon, 17 Jun 2002 08:58:09 -0700 (PDT) Received: from elam.kais.kyoto-u.ac.jp (localhost [127.0.0.1]) by elam.kais.kyoto-u.ac.jp (8.12.3/8.12.3) with ESMTP id g5HFw6Lf096986 for ; Tue, 18 Jun 2002 00:58:06 +0900 (JST) (envelope-from kaho@elam.kais.kyoto-u.ac.jp) Message-Id: <200206171558.g5HFw6Lf096986@elam.kais.kyoto-u.ac.jp> To: freebsd-small@freebsd.org Subject: Re: isp doesn't build out of the box either... References: User-Agent: EMH/1.10.0 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/20.7 (i386--freebsd) MULE/4.0 (HANANOEN) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Date: Tue, 18 Jun 2002 00:58:06 +0900 From: Kaho Toshikazu 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 Hi, picobsd maintainer, I think '-ltelnet' is necessary in isp/crunch.conf. Otherwise removes 'progs telnetd'. > ===> rtquery > telnetd.lo: In function `telnet': > telnetd.lo(.text+0x4696): undefined reference to `getent' > telnetd.lo(.text+0x46c4): undefined reference to `Getstr' > telnetd.lo(.text+0x46e3): undefined reference to `Getstr' > telnetd.lo(.text+0x4702): undefined reference to `Getstr' > *** Error code 1 > > Stop in /usr/src/release/picobsd/build/build_dir-isp/crunch. > ---> fail: Error <1> error code in <> > Error while building isp. > ---> Aborting ./picobsd -- kaho@elam.kais.kyoto-u.ac.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Mon Jun 17 16:17:10 2002 Delivered-To: freebsd-small@freebsd.org Received: from sccrmhc03.attbi.com (sccrmhc03.attbi.com [204.127.202.63]) by hub.freebsd.org (Postfix) with ESMTP id D551E37B417 for ; Mon, 17 Jun 2002 16:17:06 -0700 (PDT) Received: from obiwan ([12.245.11.114]) by sccrmhc03.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with SMTP id <20020617231705.GEMC20219.sccrmhc03.attbi.com@obiwan> for ; Mon, 17 Jun 2002 23:17:05 +0000 Message-ID: <000801c21655$19c6b7c0$0400a8c0@obiwan> From: "Rob Sanchez" To: Subject: picobsd + ports? Date: Mon, 17 Jun 2002 19:17:07 -0400 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 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 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 Hi, I've been working on building a custom PicoBSD floppy for firewall and VPN purposes, and was wondering if anybody knew how to add ports from the ports tree to PicoBSD. I know that 'ssh-picobsd' exists in /usr/ports/picobsd, but I am having trouble incorporating it as well as 'isakmpd' (from /usr/ports/security/isakmpd) into the floppy build process. I get errors such as this: ******************** make: don't know how to make /usr/obj-pico/picobsd/custom/usr/ports/security/isakmpd/app.o. Stop ---> fail: Error <2> error code in <> Error while building custom. ---> Aborting /usr/local/sbin/picobsd ******************* Does anyone know how to add an arbitrary port from the ports tree to PicoBSD? Or, could someone point me in the right direction? PicoBSD version 0.500 thank you kindly, Rob Sanchez To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Tue Jun 18 0:54:41 2002 Delivered-To: freebsd-small@freebsd.org Received: from mls.telia.net (mls.telia.net [194.237.170.103]) by hub.freebsd.org (Postfix) with ESMTP id 7B70437B400 for ; Tue, 18 Jun 2002 00:54:36 -0700 (PDT) Received: from mailbox.telia.net (mailbox.telia.net [194.237.170.234]) by mls.telia.net (8.11.6/8.11.6) with ESMTP id g5I7hCi42382; Tue, 18 Jun 2002 09:43:13 +0200 (CEST) Received: from qwerty.telia.net (pc5194123.far.telia.se [131.115.194.123]) by mailbox.telia.net (8.8.8/8.8.8) with ESMTP id JAA18987; Tue, 18 Jun 2002 09:54:30 +0200 (CEST) Message-Id: <5.1.0.14.0.20020618095221.02fa6230@mailbox.telia.net> X-Sender: jorgen@mailbox.telia.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 18 Jun 2002 09:53:29 +0200 To: "Rob Sanchez" , From: =?iso-8859-1?Q?J=F6rgen?= I Larsson Subject: Re: picobsd + ports? In-Reply-To: <000801c21655$19c6b7c0$0400a8c0@obiwan> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed 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 Hi Take a look at these sites you might find them useful. http://www.cse.ucsc.edu/~brucem/pico_notes.htm http://thewall.sourceforge.net/ /jorgen At 01:17 2002-06-18, Rob Sanchez wrote: >Hi, > >I've been working on building a custom PicoBSD floppy for firewall and VPN >purposes, and was wondering if anybody knew how to add ports from the ports >tree to PicoBSD. I know that 'ssh-picobsd' exists in /usr/ports/picobsd, >but I am having trouble incorporating it as well as 'isakmpd' (from >/usr/ports/security/isakmpd) into the floppy build process. I get errors >such as this: > >******************** >make: don't know how to make >/usr/obj-pico/picobsd/custom/usr/ports/security/isakmpd/app.o. Stop >---> fail: Error <2> error code in <> >Error while building custom. >---> Aborting /usr/local/sbin/picobsd >******************* > >Does anyone know how to add an arbitrary port from the ports tree to >PicoBSD? Or, could someone point me in the right direction? PicoBSD >version 0.500 > >thank you kindly, > >Rob Sanchez > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-small" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Jun 19 11:33:43 2002 Delivered-To: freebsd-small@freebsd.org Received: from gilliam.users.flyingcroc.net (gilliam.users.flyingcroc.net [207.246.128.2]) by hub.freebsd.org (Postfix) with ESMTP id 9F2EB37B403 for ; Wed, 19 Jun 2002 11:33:39 -0700 (PDT) Received: from localhost (atlev@localhost) by gilliam.users.flyingcroc.net (8.9.3/8.9.3) with ESMTP id LAA05334 for ; Wed, 19 Jun 2002 11:33:39 -0700 (PDT) Date: Wed, 19 Jun 2002 11:33:39 -0700 (PDT) From: Atle Veka To: freebsd-small@freebsd.org Subject: Problem with automated install (Missing operating system) Message-ID: <20020619112924.V58576-100000@gilliam.users.flyingcroc.net> 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 Hi all, I got no reply to my question at the main list, so I'm posting it here as this list has less traffic and maybe I'll have better luck. It's sort of on topic, but mainly not.. Sorry :) ---------- Forwarded message ---------- To: freebsd-questions@freebsd.org Hi, A quick intro on what I currently have; I've slapped an install.cfg (sysinstall conf) onto the mfsroot floppy which installs the distributions etc that I want. I have one boot disk which requires user interaction depending on what type of installation, then the correct mfsroot floppy is put in. Problem: On newer systems this all works great. It installs smoothly, boots up and is ready to go. However, on older systems the install process itself goes smooth, but then when it boots up the bootstrap says "Missing operating system". Same disks, same 4.5-RELEASE. I've played around with this for some time now, doing manual disklabel/fdisk commands to try to set up the boot process that somehow fails on the older machines with no luck. Has anyone encountered this problem, or have any ideas on where to look? I would greatly appreciate any insight. Thanks! Atle - Flying Crocodile Inc, Unix Systems Administrator To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Wed Jun 19 14:13: 9 2002 Delivered-To: freebsd-small@freebsd.org Received: from idiom.com (idiom.com [216.240.32.1]) by hub.freebsd.org (Postfix) with ESMTP id AEB2237B406 for ; Wed, 19 Jun 2002 14:12:57 -0700 (PDT) Received: from localhost (billy@localhost) by idiom.com (8.9.3/8.9.3) with ESMTP id OAA88893; Wed, 19 Jun 2002 14:12:43 -0700 (PDT) Date: Wed, 19 Jun 2002 14:12:43 -0700 (PDT) From: To: Atle Veka Cc: freebsd-small@FreeBSD.ORG Subject: Re: Problem with automated install (Missing operating system) In-Reply-To: <20020619112924.V58576-100000@gilliam.users.flyingcroc.net> 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 Some harddrives don't let you access the disk directly. I've encountered this with some Seagate drives. What happens is the install queries for hard drive geometry to figure out where to put the boot blocks (boot0, boot1, loader). Since the drive has this weird thing on it it gives back bogus geometry values so the boot blocks end up being written to the wrong sectors. The standard freebsd install (sysinstall) actually detects this, but disklabel and fdisk don't, or at least not regularly or reliably. When sysinstall detects the bogus geometry it installs what it thinks is the correct geomtery which for me has always worked. If you do a standard FreeBSD install at some point you will usually get a pop up letting you know that it got a bogus geometry. The work around is to preinstall the disk once with sysinstall and then ignore the part in the future where you are supposed to write the boot blocks. I havn't figured out how to detect the bogus geometry or what to use in place, however it hasn't been that important for me. ps. this is just my experience, I am by no means certain that is actually what happens, but that is what seems to be happeneing. -billy On Wed, 19 Jun 2002, Atle Veka wrote: > > Hi all, > > I got no reply to my question at the main list, so I'm posting it here as > this list has less traffic and maybe I'll have better luck. It's sort of > on topic, but mainly not.. Sorry :) > > > ---------- Forwarded message ---------- > To: freebsd-questions@freebsd.org > > > Hi, > > A quick intro on what I currently have; I've slapped an install.cfg > (sysinstall conf) onto the mfsroot floppy which installs the distributions > etc that I want. I have one boot disk which requires user interaction > depending on what type of installation, then the correct mfsroot floppy is > put in. > > Problem: On newer systems this all works great. It installs smoothly, > boots up and is ready to go. However, on older systems the install process > itself goes smooth, but then when it boots up the bootstrap says "Missing > operating system". Same disks, same 4.5-RELEASE. > > I've played around with this for some time now, doing manual > disklabel/fdisk commands to try to set up the boot process that somehow > fails on the older machines with no luck. > > Has anyone encountered this problem, or have any ideas on where to look? I > would greatly appreciate any insight. > > > Thanks! > > Atle > - > Flying Crocodile Inc, Unix Systems Administrator > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-small" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Thu Jun 20 21: 9:36 2002 Delivered-To: freebsd-small@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id CECE337B410; Thu, 20 Jun 2002 21:09:25 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g5L49IY55557; Thu, 20 Jun 2002 22:09:19 -0600 (MDT) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g5L49HG25194; Thu, 20 Jun 2002 22:09:17 -0600 (MDT) (envelope-from imp@village.org) Date: Thu, 20 Jun 2002 22:09:03 -0600 (MDT) Message-Id: <20020620.220903.34566132.imp@village.org> To: jhunt@lynden.on.ca Cc: questions@FreeBSD.ORG, small@FreeBSD.ORG, ITStaff@wmptl.com Subject: Re: Compact Flash vs ATA Disks From: "M. Warner Losh" In-Reply-To: <20020610173028.P89310-100000@lethargic.dyndns.org> References: <001401c210a7$f72b2d20$a800000a@transcon> <20020610173028.P89310-100000@lethargic.dyndns.org> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) 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 In message: <20020610173028.P89310-100000@lethargic.dyndns.org> Jason Hunt writes: : On Mon, 10 Jun 2002, Communications Machine wrote: : : > I need a comparison in terms primarily of performance and reliability : > between using compact flash to boot vs a standard ATA disk drive on a : > machine used primarily as a router/firewall. : > : [ ... snip ... ] : > : : Check out http://www.freebsd.org/doc/en_US.ISO8859-1/articles/solid-state/ : : Looks pretty interesting to me. You could do the same with a hard-drive : that is mounted read-only. The nice part about doing this is that it is : stateless, so you don't have to wait for fsck if it crashes. Except that even hard drives that are mounted read-only fail a lot more than the compact flash. We switched from ata hard disks to compact flash for our semi-embedded systems about two or so years ago. We went from getting about 1 disk RMA a week to not having had any CF RMAs yet. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message