From owner-freebsd-small Tue Mar 9 8:47:30 1999 Delivered-To: freebsd-small@freebsd.org Received: from ns1.tu-graz.ac.at (ns1.tu-graz.ac.at [129.27.2.3]) by hub.freebsd.org (Postfix) with ESMTP id 3067714D49 for ; Tue, 9 Mar 1999 08:47:11 -0800 (PST) (envelope-from mbretter@sbox.tu-graz.ac.at) Received: from babsi.tu-graz.ac.at (teleweb-17.vc-graz.ac.at [193.171.247.17]) by ns1.tu-graz.ac.at (8.8.6/8.8.6) with ESMTP id RAA06708 for ; Tue, 9 Mar 1999 17:46:53 +0100 (MET) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 09 Mar 1999 17:48:50 +0100 (CET) From: Michael Bretterklieber To: freebsd-small@freebsd.org Subject: 3.1 Release problems Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have (had) many problems with the new PicoBSD 0.43 included in 3.1-Release: 1. the build-process stopped in stage1 with no error and no warning. I found the following wrong lines in the script, because the new bootloader resides in /boot: "dd if=/usr/mdec/boot1 of=fs.PICOBSD conv=notrunc 2> /dev/null" I changed them to: "dd if=/boot/boot1 of=picobsd.bin conv=notrunc 2> /dev/null" 1a: In stage3 is this line: "disklabel -Brw -b /usr/mdec/fdboot -s /usr/mdec/bootfd /dev/rvn0 fd1440 2>&1 >/dev/null" I replaced them with: "disklabel -Brw -b /boot/boot1 -s /boot/boot2 /dev/rvn0 fd1440 2>&1 >/dev/null" 2. Two aout-objects are required in /usr/lib/aout: kzhead.o and kztail.o. I had to copy these files from my old 3.0 disk. Wy are there aout things? I thought everything is now ELF? 3. I added PAM, because login has some PAM-functions. I thing PAM is a good idea, so this isn't a problem, but should I remove the -DNOSECURE define from blah/crunch1/Makefile CFLAGS? What does the define -DNOSECURE mean? 3a. What I have to do, if I don't want PAM? Is it right if I add in blah/crunch1/Makefile the additional CFLAGS: -DNOPAM? ? 4. The biggest problem is, that my PicoBSD crashes after the device-probing: Init died with signal 6 and the system automatically reboots?@! 5. Now the PicoBSD takes much more place then the old version, so I had to remove the sshd. I have now 50KB free without sshd, before I had 36KB with sshd? 6. Has anybody tried to add "skip" to PicoBSD? Thanx, ---------------------------------- E-Mail: Michael Bretterklieber Date: 09-Mar-99 Time: 17:29:50 ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Mar 12 15:25:25 1999 Delivered-To: freebsd-small@freebsd.org Received: from mea1.munich.net (mea1.munich.net [199.108.107.11]) by hub.freebsd.org (Postfix) with ESMTP id 6314114DC4 for ; Fri, 12 Mar 1999 15:25:21 -0800 (PST) (envelope-from obermair@acm.org) Received: from munich.net ([199.108.109.131]) by mea1.munich.net (Post.Office MTA v3.1.2 release (PO203-101c) ID# 127-45094U2500L250S0) with ESMTP id AAA12454 for ; Fri, 12 Mar 1999 23:22:43 +0100 Message-ID: <36E9949D.3FAC6C82@munich.net> Date: Fri, 12 Mar 1999 23:26:37 +0100 From: Thomas Obermair Organization: Inlab Software GmbH X-Mailer: Mozilla 4.07 [en] (X11; I; Linux 2.0.36 i686) MIME-Version: 1.0 To: freebsd-small@freebsd.org Subject: PicoBSD: How to supress kernel configuration menu on startup ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I just installed and set up PicoBSD networking version to perform as a simple router between an analog leased line and a local network. Everything works just fine. Just one simple thing remains: PicoBSD does not come up without user interaction (pressing ENTER in the kernel configuration menu). I would be glad if anyone could tell me how to configure boot.config / kernel.config (?) to supress this configuration menu in order to provide automatic reboot e.g. after a power outage. Best Regards, Thomas -- Thomas Obermair Inlab Software GmbH http://www.munich.net/inlab To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Mar 12 15:51:42 1999 Delivered-To: freebsd-small@freebsd.org Received: from freja.webgiro.com (10.0.29.209.212.in-addr.arpa [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id 2601614D0A for ; Fri, 12 Mar 1999 15:51:40 -0800 (PST) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id 395FD18BE; Sat, 13 Mar 1999 00:51:31 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id 387E749C2; Sat, 13 Mar 1999 00:51:31 +0100 (CET) Date: Sat, 13 Mar 1999 00:51:29 +0100 (CET) From: Andrzej Bialecki To: Thomas Obermair Cc: freebsd-small@FreeBSD.ORG Subject: Re: PicoBSD: How to supress kernel configuration menu on startup ? In-Reply-To: <36E9949D.3FAC6C82@munich.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 On Fri, 12 Mar 1999, Thomas Obermair wrote: > Hello, > > I just installed and set up PicoBSD networking version to > perform as a simple router between an analog leased line > and a local network. > > Everything works just fine. Just one simple thing remains: > PicoBSD does not come up without user interaction (pressing > ENTER in the kernel configuration menu). > > I would be glad if anyone could tell me how to configure > boot.config / kernel.config (?) to supress this configuration > menu in order to provide automatic reboot e.g. after a > power outage. That's easy. Put a 'quit' into your /kernel.config on the floppy (not on the MFS). Or, you can edit your ${TYPE}/config/PICOBSD file and remove INTRO_USERCONFIG option. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message From owner-freebsd-small Fri Mar 12 16:34:11 1999 Delivered-To: freebsd-small@freebsd.org Received: from mea1.munich.net (mea1.munich.net [199.108.107.11]) by hub.freebsd.org (Postfix) with ESMTP id B23391545E for ; Fri, 12 Mar 1999 16:33:41 -0800 (PST) (envelope-from obermair@acm.org) Received: from munich.net ([199.108.109.131]) by mea1.munich.net (Post.Office MTA v3.1.2 release (PO203-101c) ID# 127-45094U2500L250S0) with ESMTP id AAA12688; Sat, 13 Mar 1999 00:30:58 +0100 Message-ID: <36E9A4A0.F28ED869@munich.net> Date: Sat, 13 Mar 1999 00:34:56 +0100 From: Thomas Obermair Organization: Inlab Software GmbH X-Mailer: Mozilla 4.07 [en] (X11; I; Linux 2.0.36 i686) MIME-Version: 1.0 To: Andrzej Bialecki Cc: freebsd-small@freebsd.org Subject: Re: PicoBSD: How to supress kernel configuration menu on startup ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-small@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > > On Fri, 12 Mar 1999, Thomas Obermair wrote: ... > > > > I would be glad if anyone could tell me how to configure > > boot.config / kernel.config (?) to supress this configuration > > menu in order to provide automatic reboot e.g. after a > > power outage. > > That's easy. Put a 'quit' into your /kernel.config on the floppy (not on > the MFS). Or, you can edit your ${TYPE}/config/PICOBSD file and remove > INTRO_USERCONFIG option. Unfortunately it does not work that way: I am sure having edited /kernel.config to contain "quit\n" having mounted the floppy on a 2.2.2 system. The "kernel configuration menu" keeps coming up at reboot ... I dont't have the PicoBSD Development Kit installed so I currently cannot try your second hint. Any further Ideas what could be going wrong ? Many thanks so far, Thomas -- Thomas Obermair Inlab Software GmbH http://www.munich.net/inlab To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-small" in the body of the message