From rd at tilde.se Mon Sep 3 22:52:49 2007 From: rd at tilde.se (Rickard Dahlstrand) Date: Mon, 03 Sep 2007 14:52:49 +0200 Subject: [flashboot] flashboot build issue? In-Reply-To: <20070831073350.W14913@ingenuity.resourcechain.com> References: <20070831073350.W14913@ingenuity.resourcechain.com> Message-ID: <46DC03A1.5010404@tilde.se> Hi Jason, Sorry for the low attention on this lists, but for all I know the Flashboot-community is a bit thin. ;-) I haven't tried to build using 4.2 as I'm not running it anywhere, but building 4.1 works like a charm. Other than that I can't help you until I get my 4.2-snapshot going. Anyone else?? Rickard. Jason George wrote: > Damien asked me to forward this to the list. > > I'll also add that my system is running the Aug 23 snapshot: > > OpenBSD 4.2 (GENERIC) #374: Thu Aug 23 10:41:10 MDT 2007 > deraadt at i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC > cpu0: Intel Pentium III ("GenuineIntel" 686-class, 128KB L2 cache) 898 MHz > cpu0: > FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXS > R,SSE > > > ---------- Forwarded message ---------- > Date: Thu, 30 Aug 2007 22:43:37 -0600 (MDT) > From: Jason George > To: djm at mindrot.org > Subject: flashboot build issue? > > > Hi - > > I was wondering if there is an issue with 4.2-based source tree and flashboot. > > I hadn't run any of the build scripts in about 3.5 months (around the time of > the hackathon) but noticed yesterday that my scripts from January were now > failing on the build-release portion. (They'd been running fine in different > incarnations for well over a year) Initially, they failed trying to install > the man page for ypclnt.3. This caused me to start digging. > > I then downloaded the 20070830 snapshot and encountered the same issue. > > I tracked it down to the options in mk-mini.conf. If I leave various options > of KERBEROS, YP, etc equal to NO, then the build fails in different places when > trying to install. > > My setup involves building a raw, clean source tree from fresh cvs tree from a > daily cvsync snapshot. I merge my custom binaries in much later (nothing to do > with the build-release script) so that isn't the cause. > > Any thoughts? A standard build-world from /usr/src works just fine. It's the > mk-mini options that are crating the build for me. Did something change in > "make" and how it handle its options in the last number of months that I've > missed? > > Commenting options below allows the build-release to run to completion, and the > followup scripts to build a compressed kernel, etc run, but the implication is > that Kerberos is now compiled in, etc... > > Thanks! > > --Jason > > # more mk-mini.conf > # $Id: mk-mini.conf,v 1.1 2006/08/26 17:52:44 jakob Exp $ > > WARNINGS=yes > PIPE=-pipe > STATIC= > DEBUG= > > #KERBEROS=no > #KERBEROS5=no > #YP=no > #AFS=no > #TCP_WRAPPERS=no > > > > > > # more build-release.sh > #!/bin/sh > # > # $Id: build-release.sh,v 1.2 2006/09/03 18:28:33 jakob Exp $ > > set -xe > > ### PATH = /v00/embedded/src/ResourceChain/flashboot-20070830/ > BASE=`pwd` > > #BSDSRCDIR=${BSDSRCDIR:-/usr/src} > BSDSRCDIR=${BSDSRCDIR:-/v00/embedded/src/OpenBSD/OpenBSD-current/src} > > #BSDOBJDIR=${BSDOBJDIR:-${BASE}/flash-obj} > BSDOBJDIR=${BSDOBJDIR:-/v00/embedded/obj/flashboot/flash-obj} > > #DESTDIR=${DESTDIR:-${BASE}/flash-dist} > DESTDIR=${DESTDIR:-/v00/embedded/obj/flashboot/flash-dist} > > _MINI=-mini > > RELEASEDIR=${BASE}/release${_MINI} > MAKECONF=${BASE}/mk${_MINI}.conf > SUDO=sudo > > export BSDSRCDIR BSDOBJDIR DESTDIR RELEASEDIR MAKECONF SUDO > > cd ${BSDSRCDIR} > mkdir -p ${BSDOBJDIR} ${DESTDIR} > > if [ "x$1" != "xbuilt" ] ; then > rm -rf ${DESTDIR}/* > make -k cleandir > rm -rf ${BSDOBJDIR}/* > > make obj > cd etc > make distrib-dirs > cd .. > > make build > fi > > cd etc > make distribution-etc-root-var > cd .. > # > > _______________________________________________ > flashboot mailing list > flashboot at mindrot.org > https://lists.mindrot.org/mailman/listinfo/flashboot > From stevesk at pobox.com Mon Sep 10 07:43:41 2007 From: stevesk at pobox.com (Kevin Steves) Date: Sun, 9 Sep 2007 14:43:41 -0700 Subject: [flashboot] flashboot build issue? In-Reply-To: <20070831073350.W14913@ingenuity.resourcechain.com> References: <20070831073350.W14913@ingenuity.resourcechain.com> Message-ID: <20070909214341.GB13273@steam.sbcglobal.net> On Fri, Aug 31, 2007 at 07:35:39AM -0600, Jason George wrote: : the hackathon) but noticed yesterday that my scripts from January were now : failing on the build-release portion. (They'd been running fine in different : incarnations for well over a year) Initially, they failed trying to install : the man page for ypclnt.3. This caused me to start digging. : : I then downloaded the 20070830 snapshot and encountered the same issue. : : I tracked it down to the options in mk-mini.conf. If I leave various options : of KERBEROS, YP, etc equal to NO, then the build fails in different places when : trying to install. : : My setup involves building a raw, clean source tree from fresh cvs tree from a : daily cvsync snapshot. I merge my custom binaries in much later (nothing to do : with the build-release script) so that isn't the cause. : : Any thoughts? A standard build-world from /usr/src works just fine. It's the : mk-mini options that are crating the build for me. Did something change in : "make" and how it handle its options in the last number of months that I've : missed? I see the same thing and have not yet been able to track its cause down. I get the problem also when I build 4.2 using 4.1 make program, and 4.1 /usr/share/mk makefiles. install -c -o root -g bin -m 444 shmget.cat2 /extra/flash-dist/usr/share/man/cat2/shmget.0 install -c -o root -g bin -m 444 ypclnt.cat3 /extra/flash-dist/usr/share/man/cat3/ypclnt.0 install: ypclnt.cat3: No such file or directory *** Error code 71 Stop in /extra/OPENBSD_4_2/src/lib/libc (line 88 of /usr/share/mk/bsd.man.mk). *** Error code 1 Stop in /extra/OPENBSD_4_2/src/lib. *** Error code 1 Stop in /extra/OPENBSD_4_2/src (line 73 of Makefile). From stephan at tesch.cx Wed Sep 12 06:34:49 2007 From: stephan at tesch.cx (Stephan Tesch) Date: Tue, 11 Sep 2007 22:34:49 +0200 Subject: [flashboot] flashboot build issue? In-Reply-To: <20070909214341.GB13273@steam.sbcglobal.net> References: <20070831073350.W14913@ingenuity.resourcechain.com> <20070909214341.GB13273@steam.sbcglobal.net> Message-ID: <200709112234.50491.stephan@tesch.cx> Am Sonntag, 9. September 2007 23:43:41 schrieb Kevin Steves: Hi guys, > : the hackathon) but noticed yesterday that my scripts from January were > : now failing on the build-release portion. (They'd been running fine in > : different incarnations for well over a year) Initially, they failed > : trying to install the man page for ypclnt.3. This caused me to start > : digging. > : > : I then downloaded the 20070830 snapshot and encountered the same issue. > : > : I tracked it down to the options in mk-mini.conf. If I leave various > : options of KERBEROS, YP, etc equal to NO, then the build fails in > : different places when trying to install. > : > : My setup involves building a raw, clean source tree from fresh cvs tree > : from a daily cvsync snapshot. I merge my custom binaries in much later > : (nothing to do with the build-release script) so that isn't the cause. > : > : Any thoughts? A standard build-world from /usr/src works just fine. > : It's the mk-mini options that are crating the build for me. Did > : something change in "make" and how it handle its options in the last > : number of months that I've missed? > > I see the same thing and have not yet been able to track its > cause down. I think I found the cause for this trouble. Remember the recent changes to sudo? There is a new default that the environment isn't inherited. There are some variables found in /etc/sudoers, that are kept nonetheless, but as far as I can see it, one is missing: MAKECONF. I can't tell if this should be preserved by default, maybe Todd can say a few words? Take care, Stephan From rancor at dathomir.se Fri Sep 14 22:57:11 2007 From: rancor at dathomir.se (rancor at dathomir.se) Date: Fri, 14 Sep 2007 14:57:11 +0200 Subject: [flashboot] dhclient would not work if cable is disconnected or dhcp server is unavailable during boot Message-ID: <55953.1189774631@dathomir.se> An HTML attachment was scrubbed... URL: http://lists.mindrot.org/pipermail/flashboot/attachments/20070914/2a6d4357/attachment.html From Sommer at ferien.de Sat Sep 15 00:04:18 2007 From: Sommer at ferien.de (Sommer Arnim) Date: Fri, 14 Sep 2007 16:04:18 +0200 Subject: [flashboot] dhclient would not work if cable is disconnected ordhcp server is unavailable during boot Message-ID: <0A52E62A2A8E0041B20B3A8534B70E8E01C335@mail.ferien.local> Perhaps ifstated could help you; but it is not part of the standard fileset. Arnim Sommer -----Urspr?ngliche Nachricht----- Von: rancor at dathomir.se [mailto:rancor at dathomir.se] Gesendet: Freitag, 14. September 2007 14:57 An: flashboot at mindrot.org Betreff: [flashboot] dhclient would not work if cable is disconnected ordhcp server is unavailable during boot Hi. I'm running flashboot 4.1 on a Soekris 4801-50. sis0 is configured with dhcp and it work if the interface is connected during boot. If the interface is disconnected during boot the interface will never recover after I connect it. I tried to configure dhclient to retry in dhclient.conf but without positive result. I have also tried to manually start dhclient in rc.more but dhclient terminates without retrying any further. Is there any way to get dhclient keep running so I can connect the wire after boot and make dhcp work without reboot? Best Regards rancor -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.mindrot.org/pipermail/flashboot/attachments/20070914/ccf92673/attachment.html From rancor at dathomir.se Sat Sep 15 01:06:31 2007 From: rancor at dathomir.se (rancor at dathomir.se) Date: Fri, 14 Sep 2007 17:06:31 +0200 Subject: [flashboot] dhclient would not work if cable is disconnected ordhcp server is unavailable during boot Message-ID: <13318.1189782391@dathomir.se> An HTML attachment was scrubbed... URL: http://lists.mindrot.org/pipermail/flashboot/attachments/20070914/8fde5d7a/attachment-0001.html From rd at tilde.se Sat Sep 15 17:10:14 2007 From: rd at tilde.se (Rickard Dahlstrand) Date: Sat, 15 Sep 2007 09:10:14 +0200 Subject: [flashboot] dhclient would not work if cable is disconnected or dhcp server is unavailable during boot In-Reply-To: <55953.1189774631@dathomir.se> References: <55953.1189774631@dathomir.se> Message-ID: <46EB8556.6050707@tilde.se> Hi, I use a small watchdog-script for this. It checks for a running dhclient and starts it if it for some reason failed. Just start it in rc.local with /etc/scripts/dhc-watchdog.sh > /dev/null 2> /dev/null & #!/bin/sh if (grep dhcp /etc/hostname.sis0) then while true; do if (ps -aux | grep dhclient | grep -v grep) then echo "ok.." else echo "down, launching dhclient.." dhclient sis0 fi sleep 10 done fi rancor at dathomir.se wrote: > Hi. > > I'm running flashboot 4.1 on a Soekris 4801-50. > > sis0 is configured with dhcp and it work if the interface is connected > during boot. If the interface is disconnected during boot the > interface will never recover after I connect it. > > I tried to configure dhclient to retry in dhclient.conf but without > positive result. > > I have also tried to manually start dhclient in rc.more but dhclient > terminates without retrying any further. > > Is there any way to get dhclient keep running so I can connect the > wire after boot and make dhcp work without reboot? > > Best Regards rancor > > ------------------------------------------------------------------------ > > _______________________________________________ > flashboot mailing list > flashboot at mindrot.org > https://lists.mindrot.org/mailman/listinfo/flashboot > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.mindrot.org/pipermail/flashboot/attachments/20070915/063575a8/attachment.html From jbg at masterplan.org Sun Sep 16 01:38:28 2007 From: jbg at masterplan.org (Jason George) Date: Sat, 15 Sep 2007 09:38:28 -0600 (MDT) Subject: [flashboot] flashboot build issue? In-Reply-To: <20070909214341.GB13273@steam.sbcglobal.net> References: <20070831073350.W14913@ingenuity.resourcechain.com> <20070909214341.GB13273@steam.sbcglobal.net> Message-ID: <20070915092520.C48458@ingenuity.resourcechain.com> On Sun, 9 Sep 2007, Kevin Steves wrote: > On Fri, Aug 31, 2007 at 07:35:39AM -0600, Jason George wrote: > : the hackathon) but noticed yesterday that my scripts from January were now > : failing on the build-release portion. (They'd been running fine in different > : incarnations for well over a year) Initially, they failed trying to install > : the man page for ypclnt.3. This caused me to start digging. > : > : I then downloaded the 20070830 snapshot and encountered the same issue. > : > : I tracked it down to the options in mk-mini.conf. If I leave various options > : of KERBEROS, YP, etc equal to NO, then the build fails in different places when > : trying to install. > : > : My setup involves building a raw, clean source tree from fresh cvs tree from a > : daily cvsync snapshot. I merge my custom binaries in much later (nothing to do > : with the build-release script) so that isn't the cause. > : > : Any thoughts? A standard build-world from /usr/src works just fine. It's the > : mk-mini options that are crating the build for me. Did something change in > : "make" and how it handle its options in the last number of months that I've > : missed? > > I see the same thing and have not yet been able to track its > cause down. > > I get the problem also when I build 4.2 using 4.1 make program, and > 4.1 /usr/share/mk makefiles. > > install -c -o root -g bin -m 444 shmget.cat2 /extra/flash-dist/usr/share/man/cat2/shmget.0 > install -c -o root -g bin -m 444 ypclnt.cat3 /extra/flash-dist/usr/share/man/cat3/ypclnt.0 > install: ypclnt.cat3: No such file or directory > *** Error code 71 > > Stop in /extra/OPENBSD_4_2/src/lib/libc (line 88 of /usr/share/mk/bsd.man.mk). > *** Error code 1 > > Stop in /extra/OPENBSD_4_2/src/lib. > *** Error code 1 > > Stop in /extra/OPENBSD_4_2/src (line 73 of Makefile). > I was out for my regular beers with Theo on Wednesday and mentioned this breakage (prefacing, of course, that I knew this isn't supported through the regular channels). Since I can still repeat the error conditions running strictly as root and with the sudo references completely eliminated, the trigger is somewhere in the make and .mk file setup. Unfortunately, I think part of the solution is to checkout OPENBSD_4_1 and selectively update the local tree week by week since about the start of May. Then do a full rebuild and install and repeat... This will at least reduce the window of commits to have to go through that might be triggering the error. From stephan at tesch.cx Sun Sep 16 03:36:08 2007 From: stephan at tesch.cx (Stephan Tesch) Date: Sat, 15 Sep 2007 19:36:08 +0200 Subject: [flashboot] flashboot build issue? In-Reply-To: <20070915092520.C48458@ingenuity.resourcechain.com> References: <20070831073350.W14913@ingenuity.resourcechain.com> <20070909214341.GB13273@steam.sbcglobal.net> <20070915092520.C48458@ingenuity.resourcechain.com> Message-ID: <200709151936.09284.stephan@tesch.cx> Am Samstag, 15. September 2007 17:38:28 schrieb Jason George: Hi Jason, > I was out for my regular beers with Theo on Wednesday and mentioned this > breakage (prefacing, of course, that I knew this isn't supported through > the regular channels). > > Since I can still repeat the error conditions running strictly as root and > with the sudo references completely eliminated, the trigger is somewhere > in the make and .mk file setup. > > Unfortunately, I think part of the solution is to checkout OPENBSD_4_1 and > selectively update the local tree week by week since about the start of > May. Then do a full rebuild and install and repeat... This will at least > reduce the window of commits to have to go through that might be > triggering the error. You might want to add MAKECONF to env_keep in /etc/sudoers and retry the build with sudo enabled. That is what worked for me (and what has changed between 4.1 and 4.2). Best regards, Stephan From stevesk at pobox.com Mon Sep 17 02:56:15 2007 From: stevesk at pobox.com (Kevin Steves) Date: Sun, 16 Sep 2007 09:56:15 -0700 Subject: [flashboot] flashboot build issue? In-Reply-To: <200709151936.09284.stephan@tesch.cx> References: <20070831073350.W14913@ingenuity.resourcechain.com> <20070909214341.GB13273@steam.sbcglobal.net> <20070915092520.C48458@ingenuity.resourcechain.com> <200709151936.09284.stephan@tesch.cx> Message-ID: <20070916165615.GA8893@steam.sbcglobal.net> On Sat, Sep 15, 2007 at 07:36:08PM +0200, Stephan Tesch wrote: : You might want to add MAKECONF to env_keep in /etc/sudoers and retry the build : with sudo enabled. That is what worked for me (and what has changed between : 4.1 and 4.2). yes, that addresses the problem. thanks for tracking it down. From rancor at dathomir.se Mon Sep 17 18:10:48 2007 From: rancor at dathomir.se (rancor at dathomir.se) Date: Mon, 17 Sep 2007 10:10:48 +0200 Subject: [flashboot] dhclient would not work if cable is disconnected Message-ID: <35588.1190016648@dathomir.se> An HTML attachment was scrubbed... URL: http://lists.mindrot.org/pipermail/flashboot/attachments/20070917/f9593292/attachment.html From rd at tilde.se Tue Sep 18 01:18:13 2007 From: rd at tilde.se (Rickard Dahlstrand) Date: Mon, 17 Sep 2007 17:18:13 +0200 Subject: [flashboot] flashboot build issue? In-Reply-To: <20070916165615.GA8893@steam.sbcglobal.net> References: <20070831073350.W14913@ingenuity.resourcechain.com> <20070909214341.GB13273@steam.sbcglobal.net> <20070915092520.C48458@ingenuity.resourcechain.com> <200709151936.09284.stephan@tesch.cx> <20070916165615.GA8893@steam.sbcglobal.net> Message-ID: <46EE9AB5.9070506@tilde.se> Kevin Steves wrote: > On Sat, Sep 15, 2007 at 07:36:08PM +0200, Stephan Tesch wrote: > : You might want to add MAKECONF to env_keep in /etc/sudoers and retry the build > : with sudo enabled. That is what worked for me (and what has changed between > : 4.1 and 4.2). > > yes, that addresses the problem. thanks for tracking it down. > Excellent work tracking this down, can you provide us with a patch so that we can update the CVS? Rickard. From jbg at masterplan.org Tue Sep 18 01:23:15 2007 From: jbg at masterplan.org (Jason George) Date: Mon, 17 Sep 2007 09:23:15 -0600 (MDT) Subject: [flashboot] flashboot build issue? In-Reply-To: <20070916165615.GA8893@steam.sbcglobal.net> References: <20070831073350.W14913@ingenuity.resourcechain.com> <20070909214341.GB13273@steam.sbcglobal.net> <20070915092520.C48458@ingenuity.resourcechain.com> <200709151936.09284.stephan@tesch.cx> <20070916165615.GA8893@steam.sbcglobal.net> Message-ID: <20070916162627.N59083@ingenuity.resourcechain.com> On Sun, 16 Sep 2007, Kevin Steves wrote: > On Sat, Sep 15, 2007 at 07:36:08PM +0200, Stephan Tesch wrote: > : You might want to add MAKECONF to env_keep in /etc/sudoers and retry the build > : with sudo enabled. That is what worked for me (and what has changed between > : 4.1 and 4.2). > > yes, that addresses the problem. thanks for tracking it down. I am running a version of the script without sudo (i.e. - references in the build-release.sh are removed). In order to get around any issues with the latest flag day because of Claudio's 64-bit changes, I installed the Sep13 i386 snapshot. Now the flashboot release build process runs fine with a cvs tree updated a few hours ago through to completion. From stephan at tesch.cx Wed Sep 19 05:17:24 2007 From: stephan at tesch.cx (Stephan Tesch) Date: Tue, 18 Sep 2007 21:17:24 +0200 Subject: [flashboot] flashboot build issue? In-Reply-To: <46EE9AB5.9070506@tilde.se> References: <20070831073350.W14913@ingenuity.resourcechain.com> <20070916165615.GA8893@steam.sbcglobal.net> <46EE9AB5.9070506@tilde.se> Message-ID: <200709182117.24699.stephan@tesch.cx> Am Montag, 17. September 2007 17:18:13 schrieb Rickard Dahlstrand: > Kevin Steves wrote: > > On Sat, Sep 15, 2007 at 07:36:08PM +0200, Stephan Tesch wrote: > > : You might want to add MAKECONF to env_keep in /etc/sudoers and retry > > : the build with sudo enabled. That is what worked for me (and what has > > : changed between 4.1 and 4.2). > > > > yes, that addresses the problem. thanks for tracking it down. > > Excellent work tracking this down, can you provide us with a patch so > that we can update the CVS? > > Rickard. How about this, it fixes at least the build problems. --- build-release.sh.orig Tue Sep 18 21:15:32 2007 +++ build-release.sh Tue Sep 18 18:44:58 2007 @@ -14,7 +14,7 @@ RELEASEDIR=${BASE}/release${_MINI} MAKECONF=${BASE}/mk${_MINI}.conf -SUDO=sudo +SUDO="sudo MAKECONF=${MAKECONF}" export BSDSRCDIR BSDOBJDIR DESTDIR RELEASEDIR MAKECONF SUDO