Re: make release problem with -current
Op 6 nov. 2013 om 05:23 heeft Scott McEachern sc...@blackstaff.ca het volgende geschreven: On 11/05/13 23:02, Philip Guenther wrote: On Tue, Nov 5, 2013 at 7:33 PM, Scott McEachern sc...@blackstaff.ca wrote: On 11/05/13 22:29, Ted Unangst wrote: On Tue, Nov 05, 2013 at 22:18, Scott McEachern wrote: Anyone else running into this when running make release with -current? vnconfig -v -c vnd0 /var/tmp/image.11200 vnconfig: VNDIOCSET: Device busy Are you already using vnd0? No, not intentionally at least. So you've used vnconfig -l to see what it's currently bound to and... # vnconfig -l vnd0: covering /var/tmp/image.28401 on sd0e, inode 12 vnd1: not in use vnd2: not in use vnd3: not in use I'm not sure if that's from something earlier in the build process, or possibly from a failed build the other night. Either way, I'm going to just nuke it all, install from scratch, and see how that goes. I'll bet it will work just fine.. Unconfig and restart should do it. -Otto -- Scott McEachern https://www.blackstaff.ca Beware the Four Horsemen of the Information Apocalypse: terrorists, drug dealers, kidnappers, and child pornographers. Seems like you can scare any public into allowing the government to do anything with those four. -- Bruce Schneier
Re: make release problem with -current
On Tue, Nov 05, 2013 at 11:23:26PM -0500, Scott McEachern wrote: On 11/05/13 23:02, Philip Guenther wrote: On Tue, Nov 5, 2013 at 7:33 PM, Scott McEachern sc...@blackstaff.ca wrote: On 11/05/13 22:29, Ted Unangst wrote: On Tue, Nov 05, 2013 at 22:18, Scott McEachern wrote: Anyone else running into this when running make release with -current? vnconfig -v -c vnd0 /var/tmp/image.11200 vnconfig: VNDIOCSET: Device busy Are you already using vnd0? No, not intentionally at least. So you've used vnconfig -l to see what it's currently bound to and... # vnconfig -l vnd0: covering /var/tmp/image.28401 on sd0e, inode 12 vnd1: not in use vnd2: not in use vnd3: not in use This is why I ended up with /sbin/umount /mnt /sbin/vnconfig -u vnd0 in the script I use to invoke make build make release. :-) Ken I'm not sure if that's from something earlier in the build process, or possibly from a failed build the other night. Either way, I'm going to just nuke it all, install from scratch, and see how that goes. I'll bet it will work just fine.. -- Scott McEachern https://www.blackstaff.ca Beware the Four Horsemen of the Information Apocalypse: terrorists, drug dealers, kidnappers, and child pornographers. Seems like you can scare any public into allowing the government to do anything with those four. -- Bruce Schneier
make release problem with -current
Anyone else running into this when running make release with -current?
cc -Werror -Wall -Wstrict-prototypes -Wmissing-prototypes -Wno-main
-Wno-uninitialized -Wno-format -Wstack-larger-than-2047
-fno-builtin-printf -fno-builtin-snprintf -fno-builtin-vsnprintf
-fno-builtin-log -fno-builtin-log2 -fno-builtin-malloc
-fno-stack-protector -Os -mtune=i486 -pipe -nostdinc -I../../../.. -I.
-I../../../../arch -DSCSITERSE -DSMALL_KERNEL -DNO_PROPOLICE
-DTIMEZONE=0 -DDST=0 -DFFS -DFFS2 -DEXT2FS -DNFSCLIENT -DCD9660
-DUDF -DMSDOSFS -DINET -DINET6 -DBOOT_CONFIG -DCRYPTO -DRAMDISK_HOOKS
-DMINIROOTSIZE=0xf20 -DPCIVERBOSE -DMAXUSERS=4 -D_KERNEL -MD -MP -c
vers.c
ld -Ttext 0xD0200120 -e start -N --warn-common -nopie -S -x -o bsd
${SYSTEM_HEAD} vers.o ${OBJS}
textdatabss dec hex
3982420 2045352 434916 6462688 629ce0
cp
/usr/src/distrib/i386/ramdisk_cd/../../../sys/arch/i386/compile/RAMDISK_CD/bsd
bsd
cc -o rdsetroot
/usr/src/distrib/i386/ramdisk_cd/../../common/elfrdsetroot.c
/usr/src/distrib/i386/ramdisk_cd/../../common/elf32.c
/usr/src/distrib/i386/ramdisk_cd/../../common/elf64.c
cp bsd bsd.rd
/usr/src/distrib/i386/ramdisk_cd/obj/rdsetroot bsd.rd mr.fs
cp bsd.rd bsd.strip
strip bsd.strip
strip -R .comment bsd.strip
gzip -c9n bsd.strip bsd.gz
dd if=/dev/zero of=/var/tmp/image.11200 bs=512 count=5760
5760+0 records in
5760+0 records out
2949120 bytes transferred in 0.013 secs (226855385 bytes/sec)
vnconfig -v -c vnd0 /var/tmp/image.11200
vnconfig: VNDIOCSET: Device busy
*** Error 1 in /usr/src/distrib/i386/ramdisk_cd
(../common/Makefile.inc:31 'cdrom54.fs')
*** Error 1 in /usr/src/distrib/i386 (bsd.subdir.mk:48 'all')
*** Error 1 in /usr/src/distrib (bsd.subdir.mk:48 'all')
*** Error 1 in /usr/src/etc (Makefile:322 'distrib')
snipped dmesg:
OpenBSD 5.4-current (GENERIC.MP) #0: Tue Nov 5 21:05:57 EST 2013
r...@blackstaff.blackstaff.ca:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: AMD Phenom(tm) II X6 1100T Processor (AuthenticAMD 686-class,
512KB L2 cache) 3.32 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,SSE3,MWAIT,CX16,POPCNT,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,WDT,ITSC
real mem = 3487690752 (3326MB)
avail mem = 3418877952 (3260MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 07/23/10, BIOS32 rev. 0 @ 0xf0010,
SMBIOS rev. 2.5 @ 0x9f400 (68 entries)
bios0: vendor American Megatrends Inc. version 2105 date 07/23/2010
bios0: ASUSTeK Computer INC. M4A785TD-V EVO
--
Scott McEachern
https://www.blackstaff.ca
Beware the Four Horsemen of the Information Apocalypse: terrorists, drug dealers,
kidnappers, and child pornographers. Seems like you can scare any public into allowing
the government to do anything with those four. -- Bruce Schneier
Re: make release problem with -current
On Tue, Nov 05, 2013 at 22:18, Scott McEachern wrote: Anyone else running into this when running make release with -current? vnconfig -v -c vnd0 /var/tmp/image.11200 vnconfig: VNDIOCSET: Device busy Are you already using vnd0?
Re: make release problem with -current
On 11/05/13 22:29, Ted Unangst wrote: On Tue, Nov 05, 2013 at 22:18, Scott McEachern wrote: Anyone else running into this when running make release with -current? vnconfig -v -c vnd0 /var/tmp/image.11200 vnconfig: VNDIOCSET: Device busy Are you already using vnd0? No, not intentionally at least. -- Scott McEachern https://www.blackstaff.ca Beware the Four Horsemen of the Information Apocalypse: terrorists, drug dealers, kidnappers, and child pornographers. Seems like you can scare any public into allowing the government to do anything with those four. -- Bruce Schneier
Re: make release problem with -current
On Tue, Nov 5, 2013 at 7:33 PM, Scott McEachern sc...@blackstaff.ca wrote: On 11/05/13 22:29, Ted Unangst wrote: On Tue, Nov 05, 2013 at 22:18, Scott McEachern wrote: Anyone else running into this when running make release with -current? vnconfig -v -c vnd0 /var/tmp/image.11200 vnconfig: VNDIOCSET: Device busy Are you already using vnd0? No, not intentionally at least. So you've used vnconfig -l to see what it's currently bound to and...
Re: make release problem with -current
On 11/05/13 23:02, Philip Guenther wrote: On Tue, Nov 5, 2013 at 7:33 PM, Scott McEachern sc...@blackstaff.ca wrote: On 11/05/13 22:29, Ted Unangst wrote: On Tue, Nov 05, 2013 at 22:18, Scott McEachern wrote: Anyone else running into this when running make release with -current? vnconfig -v -c vnd0 /var/tmp/image.11200 vnconfig: VNDIOCSET: Device busy Are you already using vnd0? No, not intentionally at least. So you've used vnconfig -l to see what it's currently bound to and... # vnconfig -l vnd0: covering /var/tmp/image.28401 on sd0e, inode 12 vnd1: not in use vnd2: not in use vnd3: not in use I'm not sure if that's from something earlier in the build process, or possibly from a failed build the other night. Either way, I'm going to just nuke it all, install from scratch, and see how that goes. I'll bet it will work just fine.. -- Scott McEachern https://www.blackstaff.ca Beware the Four Horsemen of the Information Apocalypse: terrorists, drug dealers, kidnappers, and child pornographers. Seems like you can scare any public into allowing the government to do anything with those four. -- Bruce Schneier
