Date: Sat, 22 Apr 2000 17:33:44 -0400 From: "Edward W. Akeyson" <eakeyson@earthlink.net> To: <freebsd-small@freebsd.org> Subject: Iopener & PicoBSD ramblings Message-ID: <NDBBIDOKILFAGOJNPOELKEENCDAA.eakeyson@earthlink.net>
next in thread | raw e-mail | index | archive | help
Hello all,
I am trying to develop a FreeBSD image file to flash to the Sandisk (16MB)
on the iopener without attaching a hard drive (only for emergency or no
other way around it). When making PicoBSD on 3.4-Stable sources, it ends
with errors (shown below). I am also wondering if this is the best track- I
also have been playing with a 16MB virtual node disk file (geometry same as
Sandisk) with a truncated 3.4-stable system added to it. I have some
problems and questions- all replies greatly appreciated.
1. Failure of PicoBSD on 3.4-stable system due to errors during crunch
process (output below). I am using a 'custom' configuration for the iopener
copied from the "net" configuration. My 3.4-S system does not have a
'custom' choice (i understand one of the new things with 4.0), but I copied
the 'net' directory and the build script recognizes it fine. Specifically,
it fails on passwd, login and ppp during cruch. 'make'-ing in the crunch
directory does the same thing. I can get around these errors if I edit them
out of the crunch.conf file, but I think that I would need these eventually.
I also get the same errors when I try to compile one of the standard PicoBSD
types as well. When using PicoBSD for a system with much larger disk than a
floppy (e.g., 16MB as on the Sandisk), are there other considerations one
needs to keep in mind that I may not be realizing.
2. I have read on the FreeBSD-small mailing list that there are some
problems with PicoBSD. Is it better in 4.0-stable? I have been contemplating
upgrading my main system to 4.0, and this would likely push me in that
direction.
3. Is PicoBSD the best development platform for a 16MB image (space not so
tight)- should I move in the direction of hand assembling my own image file
without MFS, etc. as done in PicoBSD? If so, what should I be certain to
include besides kernel, boot loaders, /etc and any /bin or /sbin files I
need. Also, how can I test this image file before putting it on the iopener?
I would prefer not to open the thing, unless I absolutely have to, and I
want to make sure that the image will boot. I can upgrade from there.
4. I have read all the mailing lists and other documentation that I can
find, including the "HOWTO: flash disk image" or something like it from last
summer in freebsd-small, but it based on an earlier version of PicoBSD and
there seem to be some major differences to the current version (scripts vs.
makefile, etc.). Anyone else currently working on an image for the iopener?
I would like this to be a stepping-off point for me as I have several other
potential projects like this if this works out. I would be happy to share
notes with anyone else working on this or similar projects.
Thanks for any support or help. Sorry for the extra bandwidth but I would
really like to get this going with MY os of choice....
Output of crunch process for PicoBSD:
<snip>
cc -O -pipe -DNOPAM -DRELEASE_CRUNCH -DCRUNCHED_BINARY -DNOSECURE -DNOCRY
PT -DNOYPPASSWD -c routed_stub.c
ld -dc -r -o routed.lo routed_stub.o /usr/obj/usr/src/sbin/routed/if.o
/usr/obj/usr/src/sbin/routed/input.o /usr/obj/usr/src/sbin/routed/main.o
/usr/obj/usr/src/sbin/routed/output.o /usr/obj/usr/src/sbin/routed/parms.o
/usr/obj/usr/src/sbin/routed/radix.o /usr/obj/usr/src/sbin/routed/rdisc.o
/usr/obj/usr/src/sbin/routed/table.o /usr/obj/usr/src/sbin/routed/trace.o
crunchide -k _crunched_routed_stub routed.lo
echo "int _crunched_ipfw_stub(int argc, char **argv, char **envp){return
main(argc,argv,envp);}" >ipfw_stub.c
cc -O -pipe -DNOPAM -DRELEASE_CRUNCH -DCRUNCHED_BINARY -DNOSECURE -DNOCRY
PT -DNOYPPASSWD -c ipfw_stub.c
ld -dc -r -o ipfw.lo ipfw_stub.o /usr/obj/usr/src/sbin/ipfw/ipfw.o
crunchide -k _crunched_ipfw_stub ipfw.lo
echo "int _crunched_minigzip_stub(int argc, char **argv, char **envp){return
main(argc,argv,envp);}" >minigzip_stub.c
cc -O -pipe -DNOPAM -DRELEASE_CRUNCH -DCRUNCHED_BINARY -DNOSECURE -DNOCRY
PT -DNOYPPASSWD -c minigzip_stub.c
ld -dc -r -o minigzip.lo minigzip_stub.o
/usr/obj/usr/src/usr.bin/minigzip/minigzip.o
crunchide -k _crunched_minigzip_stub minigzip.lo
cc -static -o crunch1 crunch1.o sh.lo test.lo echo.lo hostname.lo ln.lo
getty.lo stty.lo login.lo inetd.lo telnetd.lo w.lo msg.lo kget.lo reboot.lo
init.lo ifconfig.lo df.lo sps.lo ns.lo vm.lo cat.lo cp.lo rm.lo mknod.lo
chmod.lo chown.lo mkdir.lo ls.lo syslogd.lo sysctl.lo route.lo pwd_mkdb.lo
dev_mkdb.lo mount.lo mount_msdos.lo umount.lo kill.lo mount_std.lo natd.lo
pwd.lo telnet.lo more.lo ppp.lo date.lo passwd.lo mount_cd9660.lo
mount_nfs.lo ping.lo traceroute.lo routed.lo ipfw.lo
minigzip.lo -lncurses -lmytinfo -lipx -lz -lpcap -lalias -lwrap -ledit -luti
l -lmd -lcrypt -lmp -lgmp -lm -lkvm -lgnuregex -ltelnet -lradius
login.lo: In function `auth_pam':
login.lo(.text+0xf30): undefined reference to `pam_start'
login.lo(.text+0xf42): undefined reference to `pam_strerror'
login.lo(.text+0xf5c): undefined reference to `pam_set_item'
login.lo(.text+0xf6e): undefined reference to `pam_strerror'
login.lo(.text+0xf90): undefined reference to `pam_set_item'
login.lo(.text+0xfa2): undefined reference to `pam_strerror'
login.lo(.text+0xfc6): undefined reference to `pam_authenticate'
login.lo(.text+0xff2): undefined reference to `pam_get_item'
login.lo(.text+0x102d): undefined reference to `pam_strerror'
login.lo(.text+0x1055): undefined reference to `pam_strerror'
login.lo(.text+0x1073): undefined reference to `pam_end'
login.lo(.text+0x1085): undefined reference to `pam_strerror'
login.lo(.data+0x98): undefined reference to `misc_conv'
ppp.lo: In function `ID0NgMkSockNode':
ppp.lo(.text+0x12468): undefined reference to `NgMkSockNode'
ppp.lo: In function `ether_Write':
ppp.lo(.text+0x27084): undefined reference to `NgSendData'
ppp.lo: In function `ether_Read':
ppp.lo(.text+0x270b6): undefined reference to `NgRecvData'
ppp.lo: In function `ether_MessageIn':
ppp.lo(.text+0x272db): undefined reference to `NgRecvMsg'
ppp.lo: In function `ether_Create':
ppp.lo(.text+0x27856): undefined reference to `NgSendMsg'
ppp.lo(.text+0x27898): undefined reference to `NgRecvMsg'
ppp.lo(.text+0x27ab2): undefined reference to `NgSendMsg'
ppp.lo(.text+0x27bab): undefined reference to `NgSendMsg'
ppp.lo(.text+0x27c55): undefined reference to `NgSendMsg'
passwd.lo: In function `local_passwd':
passwd.lo(.text+0x379): undefined reference to `local_password'
passwd.lo(.text+0x38d): undefined reference to `local_password'
passwd.lo: In function `main':
passwd.lo(.text+0x562): undefined reference to `yp_domain'
passwd.lo(.text+0x568): undefined reference to `yp_server'
passwd.lo(.text+0x575): undefined reference to `yp_server'
passwd.lo(.text+0x58a): undefined reference to `yp_server'
passwd.lo(.text+0x596): undefined reference to `force_old'
passwd.lo(.text+0x5f3): undefined reference to `use_yp'
passwd.lo(.text+0x60a): undefined reference to `yp_passwd'
passwd.lo(.text+0x650): undefined reference to `yp_in_pw_file'
passwd.lo(.text+0x662): undefined reference to `yp_passwd'
passwd.lo: In function `pw_error':
passwd.lo(.text+0xe96): undefined reference to `_use_yp'
*** Error code 1
Stop.
*** Error code 1
Stop.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-small" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?NDBBIDOKILFAGOJNPOELKEENCDAA.eakeyson>