Hi James,

I tried both; the GENERIC-RD which comes with "flashboot-SNAP-20101224" results in some devices being unknown (not surprisingly; different config than matches the sources).

Then I tried RAMDISK and GENERIC from /sys/arch/i386/conf (obsd 4.9).

The building of GENERIC stops with:
=============================
cp bsd bsd.rd
/root/flashboot/obj/rdsetroot bsd.rd < mr.fs
bsd.rd: no rd_root_image symbols?
*** Error code 1

Stop in /root/flashboot (line 95 of /root/flashboot/Makefile).
Your kernel is stored here /root/flashboot/obj/
=============================

Which makes sence to me since this config is not configured for a ramdrive root filesystem.


The RAMDISK get futher but fails with:
# /dev/rsvnd0c:
/mnt: write failed, file system is full

Or better said; it continues and builds de bsd.gz but that bsd.gz doesn't work because it can not load /sbin/init. (Most likely because it was never copied to /mnt during the making of the ramdrive filesystem).

So I'm getting closer but haven't succeeded just yet.

Mark





James Records writes:

Hey mark:


Skipjack and libdes were retired from the system. CAST-128 implementation was also removed from libc.

are you copying the kernel conf from a 4.9 obsd system?


On Tue, May 3, 2011 at 1:19 PM, Hi Stuart & List, I think I found the topic you mention and this is what I understood from it: tar -xzf flashboot-SNAP-20101224.tar.gz
   cd flashboot
   export WORKDIR=sandbox
   mkdir -p ${WORKDIR}
   tar -xzf ../base49.tgz -C ${WORKDIR}/
   tar -xzf ../etc49.tgz -C ${WORKDIR}/
   tar -xzf ../comp49.tgz -C ${WORKDIR}/
   tar -xzf ../man49.tgz -C ${WORKDIR}/
   tar -xzf ../src.tar.gz -C ${WORKDIR}/usr/src/
   tar -xzf ../sys.tar.gz -C ${WORKDIR}/usr/src/
   mv ${WORKDIR}/dev ${WORKDIR}/dev-orig
   mkdir ${WORKDIR}/dev
   mount_mfs -o nosuid -s 32768 /dev/wd0b ${WORKDIR}/dev
   cp -p ${WORKDIR}/dev-orig/MAKEDEV ${WORKDIR}/dev/MAKEDEV
   cd ${WORKDIR}/dev/
   ./MAKEDEV all
   cd -
   cp -p mk-mini.conf ${WORKDIR}/mk-mini.conf
   chroot ${WORKDIR} /bin/ksh
   export MAKECONF=/mk-mini.conf
   cd /sys/arch/i386/conf
   config RAMDISK
   cd ../compile/RAMDISK
   make clean ; make depend ; make
   cd /usr/src
   make obj
   cd /usr/src/etc
   env DESTDIR=/ sudo make distrib-dirs
   cd /usr/src
   make SUDO=sudo build
I have some doubts if I need to do the "config RAMDISK" and the "make clean ; make depend ; make" since that builds a 'regular' openbsd kernel. But I don't think it hurts either. Anyway; the build finished without problems and now I'm a bit lost about what I should do the topic talks about changin flash-dist to 'workdir' in build-bindist.sh but dat file doesn't have a reference to flash-dist. build-kernel.sh, for example, does but 4.9 doesn't like the GENERIC-RD kernel. Copying the RAMDISK kernel from regular BSD; starts building but quits with a missing library "des". It does create a bsd (just not the bsd.gz) but that kernel doesn't boot completely and than reboots. I assume I have to make my own "GENERIC-RD" but where do I start? Note: I haven't tried the script yet that was posted earlier today. I will try that tomorrow. But from first glance it doesn't look a lot different from what I did manually. Mark Stuart Henderson writes: It is possible but you need to do things a different way.
     Use a chroot jail rather than DESTDIR which no longer works.
     See the list archives for more info
On 2011/05/03 11:23, <URL:mailto:flashbootl...@itmon.nl>flashbootl...@itmon.nl wrote: Dear List, My home firewall runs on an Alix system with a flashboot OpenBSD 4.6. I haven't upgraded since and I thought now with the release of 4.9 it
       made sence to build a new flashboot.
I installed a virtualbox with 4.9; downloaded the latest flashboot
       scripts (2010-12-24) and executed build-release as stated in the
README. This has worked for me with 4.6 without problems. But now the
       building seams to fail on "libstdc++-v3"
Has anyone succesfully build a 4.9 FlashBoot image? Is this still possible? Mark _______________________________________________
   flashboot mailing list
   <URL:mailto:flashboot@mindrot.org>flashboot@mindrot.org
<URL:https://lists.mindrot.org/mailman/listinfo/flashboot>https://lists. mindrot.org/mailman/listinfo/flashboot

_______________________________________________
flashboot mailing list
flashboot@mindrot.org
https://lists.mindrot.org/mailman/listinfo/flashboot

Reply via email to