From owner-freebsd-current@FreeBSD.ORG Mon Jun 22 02:10:03 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A09111065670 for ; Mon, 22 Jun 2009 02:10:03 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: from mail-gx0-f207.google.com (mail-gx0-f207.google.com [209.85.217.207]) by mx1.freebsd.org (Postfix) with ESMTP id 4E91D8FC14 for ; Mon, 22 Jun 2009 02:10:03 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: by gxk3 with SMTP id 3so4277133gxk.19 for ; Sun, 21 Jun 2009 19:10:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:received:date:from:to :subject:message-id:in-reply-to:references:x-mailer:mime-version :content-type:content-transfer-encoding; bh=DyLu3xBfsLk/9F8mU/xpQY/ODshRv8SIti8nkFZlewY=; b=wnGmK4kHHLG9q0qXw/GR8Z3kc5Coxe+c32XrdnGgssKKkuvamgYWZ+rO9Wjk+RokZh r8uHjdOQ7ItZQRaqiXX4X7Oplwh7FQ4tkPGoD5iEdeE7Bz9cSRpSKva9nYL4gx6MEvf1 lpxvtXHcWBd/+hsf/EZuYi62TvFaMEWDApguk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:date:from:to:subject:message-id:in-reply-to:references :x-mailer:mime-version:content-type:content-transfer-encoding; b=mE6mjIqSmagsVqGt0EsEthddneXlY3mTABTJRyUL9TbIbdgP5JPYJgn0qjdLbFbMWp IRtsjMNNlknI/PrBXVCMEHH2o5x74pErJceyc77T3Pu0qkSAqTHpGkmJ4ckjY/F1854v mq6bL4Myi55W5hdCkgcUtg+D8xnZPWfex1Sd0= Received: by 10.151.132.9 with SMTP id j9mr10255315ybn.139.1245636602737; Sun, 21 Jun 2009 19:10:02 -0700 (PDT) Received: from cygnus.homeunix.com ([189.71.105.194]) by mx.google.com with ESMTPS id 6sm307586ywi.33.2009.06.21.19.10.00 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 21 Jun 2009 19:10:01 -0700 (PDT) Sender: Nenhum_de_Nos Received: from arroway (arroway.apartnet [10.1.1.80]) by cygnus.homeunix.com (Postfix) with SMTP id 81CE1B8074 for ; Sun, 21 Jun 2009 23:09:56 -0300 (BRT) Date: Sun, 21 Jun 2009 23:10:17 -0300 From: Nenhum_de_Nos To: freebsd-current@freebsd.org Message-Id: <20090621231017.b2dc6e86.matheus@eternamente.info> In-Reply-To: <4A3D116B.7080308@elischer.org> References: <9ccd6cc4824b70cd9316ad9490dfd932.squirrel@cygnus.homeunix.com> <9ca40c9e2ad6e868fcbe6692e248ee13.squirrel@cygnus.homeunix.com> <4A3D116B.7080308@elischer.org> X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.9; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: tinybsd can't compile custom kernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jun 2009 02:10:03 -0000 On Sat, 20 Jun 2009 09:42:19 -0700 Julian Elischer wrote: > Nenhum_de_Nos wrote: > > On Sat, June 20, 2009 12:06, Nenhum_de_Nos wrote: > >> hail, > >> > >> I'm trying to compile tinybsd for a firewall. I copied firewall dir under > >> conf to cygnus. edited and tried to compile. > >> > >> It was ok till kernel compilation: > >> > >> ===> Chrooted make in /usr/obj/tinybsdbuild succeeded > >> ===> Cleaning up... > >> ===> Cleaning for autoconf-2.62 > >> ===> Cleaning for expat-2.0.1 > >> ===> Cleaning for pcre-7.9 > >> ===> Cleaning for libiconv-1.13 > >> ===> Cleaning for m4-1.4.13,1 > >> ===> Cleaning for help2man-1.36.4_3 > >> ===> Cleaning for gmake-3.81_3 > >> ===> Cleaning for autoconf-wrapper-20071109 > >> ===> Cleaning for p5-gettext-1.05_2 > >> ===> Cleaning for gettext-0.17_1 > >> ===> Cleaning for apache-2.2.11_7 > >> =====> Building customized tiny beastie kernel... > >> ERROR: Missing kernel configuration file(s) (TINYBSD). > >> *** Error code 1 > >> > >> Stop in /usr/src. > >> *** Error code 1 > >> > >> Stop in /usr/src. > >> > >> in conf/cygnus there is TINYBSD file and cygnus file. the tinybsd command > >> line ask for kernel conf file. there I type cygnus. > >> > >> [root@darkside /usr/src/tools/tools/tinybsd/conf]# ls -l cygnus/ > >> total 24 > >> -rw-r--r-- 1 root wheel 6361 Jun 19 22:32 TINYBSD > >> -rw-r--r-- 1 root wheel 6361 Jun 20 01:15 cygnus > >> drwxr-xr-x 3 root wheel 512 Feb 13 13:10 etc > >> -rw-r--r-- 1 root wheel 3799 Jun 25 2007 tinybsd.basefiles > >> -rw-r--r-- 1 root wheel 473 Jun 19 22:42 tinybsd.ports > >> [root@darkside /usr/src/tools/tools/tinybsd/conf]# > >> > >> I followed http://www.tinybsd.org/tinybsd/Documentation. > >> > >> also, is there a way to save all choices from ports build ? and the curses > >> menu don't work ok for choosing. is this the way was supposed to be ? > >> > >> thanks, > >> > >> matheus > > > > is possible to compile i386 tinybsd on amd64 install ? > > > > FreeBSD darkside.apartnet 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Sun Jun 14 > > 01:59:21 BRT 2009 > > root@darkside.apartnet:/usr/obj/usr/src/sys/Darkside8 amd64 > > > > thanks, > > > > matheus > > > > TinyBSD uses the systems binaries on teh host system by default.. > I've been told it can do a cross build by using a cross-built > directory instead of / but haven't done it.. > tinybsd is a shell script so you may be able to understand what > is going on by just reading it. the problem was indeed the ARCH of build machine. I got a vm running 7.2R i386 and csup'ed current (just got the code, running 7.2R). when I run tinybsd I got this: =====> Copying your custom configuration on conf/ ... 512+0 records in 512+0 records out 262144 bytes transferred in 0.008996 secs (29140030 bytes/sec) /dev/md0 512 # sectorsize 262144 # mediasize in bytes (256K) 512 # mediasize in sectors 0 # Cylinders according to firmware. 64 # Heads according to firmware. 32 # Sectors according to firmware. fdisk: invalid fdisk partition table found fdisk: Geom not found: "md0" ******* Working on device /dev/md0 ******* ******* Working on device /dev/md0 ******* parameters extracted from in-core disklabel are: cylinders=0 heads=64 sectors/track=32 (2048 blks/cyl) parameters to be used for BIOS calculations are: cylinders=0 heads=64 sectors/track=32 (2048 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 4294967264 (2097151 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 63/ sector 32 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: /dev/md0a: 0.2MB (496 sectors) block size 16384, fragment size 2048 using 1 cylinder groups of 0.24MB, 15 blks, 64 inodes. with soft updates super-block backups (for fsck -b #) at: 160 /tmp/tinybsd.0kJsPWcI: write failed, filesystem is full cpio: write error: No space left on device Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/md0a 118 118 -8 107% /tmp/tinybsd.0kJsPWcI 4+0 records in 4+0 records out 262144 bytes transferred in 0.010969 secs (23898790 bytes/sec) /tmp/tinybsd.Vipmzx0l /tmp/tinybsd.0kJsPWcI =====> Done! =====> Your configuration options were saved in /root/.tinybsd.tinybsd.root =====> You can see your build log in /root/tinybsd.log =====> Your final image is in /usr/src/tools/tools/tinybsd/tinybsd.bin =====> Now use dd(1) to write it. ./tinybsd sectors=254208 heads=64 spt=32 conf=cygnus was issued for a 128MB kingston CF. those values I got from diskinfo: /dev/da0 512 # sectorsize 130154496 # mediasize in bytes (124M) 254208 # mediasize in sectors 124 # Cylinders according to firmware. 64 # Heads according to firmware. 32 # Sectors according to firmware. when diskinfo was run, the cf card was connected through usb card reader, is this a problem ? well, some options from kernel (such as sio) made kernel not able to build, but as I won't use it comment did the job. I'll try to figure out from tinybsd script what to do next, but if anyone has any hints those wuold be much apreciated. thanks, matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style