Re: tinybsd can't compile custom kernel

On Sat, 20 Jun 2009 09:42:19 -0700
Julian Elischer <julian_at_elischer.org> 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_at_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_at_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_at_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:
<UNUSED>
The data for partition 3 is:
<UNUSED>
The data for partition 4 is:
<UNUSED>
/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