From alexbestms at math.uni-muenster.de Sun Nov 1 00:30:07 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Sun Nov 1 00:30:13 2009 Subject: ports/135322: Port graphics/linux_dri has incorrect packaging list causing automatic port update to fail Message-ID: <200911010030.nA10U6eZ064896@freefall.freebsd.org> The following reply was made to PR ports/135322; it has been noted by GNATS. From: Alexander Best To: , Cc: Subject: Re: ports/135322: Port graphics/linux_dri has incorrect packaging list causing automatic port update to fail Date: Sun, 01 Nov 2009 01:29:45 +0100 (CET) x11/nvidia-driver now has the following ports marked as conflicting with it: linux-dri-[0-9]* linux-f10-dri-[0-9]* linux-f8-dri-[0-9]* linux_dri-[0-9]* linux_dri-devel-[0-9]* so i believe this PR can be closed. alex From alexbestms at math.uni-muenster.de Sun Nov 1 00:50:02 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Sun Nov 1 00:50:08 2009 Subject: ports/136321: x11-toolkits/linux-pango: please update linux based port of pango Message-ID: <200911010050.nA10o2pB082492@freefall.freebsd.org> The following reply was made to PR ports/136321; it has been noted by GNATS. From: Alexander Best To: , Cc: Subject: Re: ports/136321: x11-toolkits/linux-pango: please update linux based port of pango Date: Sun, 01 Nov 2009 01:41:56 +0100 (CET) unfortunately rpms for pango-1.24.4 which includes the fix Shakir Solomon mentioned are only available for fedora >= 11. PR should be marked suspended until we have fedora 11 rpm support in the ports tree. alex From linimon at FreeBSD.org Sun Nov 1 08:23:58 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sun Nov 1 08:24:04 2009 Subject: ports/136321: x11-toolkits/linux-pango: please update linux based port of pango Message-ID: <200911010823.nA18NvSY011826@freefall.freebsd.org> Synopsis: x11-toolkits/linux-pango: please update linux based port of pango State-Changed-From-To: feedback->suspended State-Changed-By: linimon State-Changed-When: Sun Nov 1 08:23:21 UTC 2009 State-Changed-Why: Awaiting an update to v11 bits. http://www.freebsd.org/cgi/query-pr.cgi?pr=136321 From linimon at FreeBSD.org Sun Nov 1 08:27:45 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sun Nov 1 08:27:56 2009 Subject: kern/140156: [linux] cdparanoia fails to read drive data Message-ID: <200911010827.nA18RidR012071@freefall.freebsd.org> Synopsis: [linux] cdparanoia fails to read drive data Responsible-Changed-From-To: freebsd-bugs->freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Sun Nov 1 08:27:25 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=140156 From linimon at FreeBSD.org Sun Nov 1 08:29:50 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sun Nov 1 08:29:57 2009 Subject: ports/135322: Port graphics/linux_dri has incorrect packaging list causing automatic port update to fail Message-ID: <200911010829.nA18TonG012145@freefall.freebsd.org> Synopsis: Port graphics/linux_dri has incorrect packaging list causing automatic port update to fail State-Changed-From-To: feedback->closed State-Changed-By: linimon State-Changed-When: Sun Nov 1 08:28:48 UTC 2009 State-Changed-Why: Apparently the problem has been fixed. To submitter: if not, please let us know. http://www.freebsd.org/cgi/query-pr.cgi?pr=135322 From bsam at ipt.ru Sun Nov 1 15:29:17 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Sun Nov 1 15:29:24 2009 Subject: linux-f10-libidn In-Reply-To: <4AEBAE54.3060300@internode.on.net> (Robert McKenzie's message of "Sat, 31 Oct 2009 14:26:12 +1100") References: <4AEBAE54.3060300@internode.on.net> Message-ID: <99220054@h30.sp.ipt.ru> On Sat, 31 Oct 2009 14:26:12 +1100 Robert McKenzie wrote: > I am just in the process of updating my system and have noted after > having done a cvsup using server 18 that my dns ports directory > although it has an f8 version, does not have an f10 version although > the Makefile shows a conflict with f10. > You comments would be most appreciated. The port net/linux-f10-libidn existed for some time but then was incorporated into linux_base-f10. The CONFLICTS will include this port for some time. -- WBR, bsam From bugmaster at FreeBSD.org Mon Nov 2 11:06:52 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 2 11:07:48 2009 Subject: Current problem reports assigned to freebsd-emulation@FreeBSD.org Message-ID: <200911021106.nA2B6pBo033555@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/140156 emulation [linux] cdparanoia fails to read drive data o kern/139423 emulation [parallels] Networking does not work on amd64 guest on o kern/138944 emulation [parallels] [regression] Parallels no longer works in o kern/138880 emulation [linux] munmap segfaults after linux_mmap2 stresstest o kern/138860 emulation [linux] linux_socketcall() causing buffer overflow o ports/137332 emulation add caution messages to some adobe products s ports/136321 emulation x11-toolkits/linux-pango: please update linux based po o ports/136229 emulation [linux] certain linux apps look for libraries using a o ports/135337 emulation [PATCH] emulators/linux_base-f10: incorrect bash usage o kern/133144 emulation [linux] linuxulator 2.6 crashes with nvidias libGL.so. o kern/130724 emulation [linprocfs] [patch] cpuinfo in linprocfs is dated, cau o kern/129169 emulation [linux] [patch] Linux Emulation ENOTCONN error using n f ports/127018 emulation Linuxulator incapable of using FreeBSD's LDAP environm o kern/126232 emulation [linux] Linux ioctl TCGETS (0x5401) always fails o kern/73777 emulation [linux] [patch] linux emulation: root dir special hand a kern/72920 emulation [linux]: path "prefixing" is not done on unix domain s o kern/56451 emulation [linprocfs] /compat/linux/proc/cpuinfo gives wrong CPU o kern/41543 emulation [patch] [request] easier wine/w23 support o kern/39201 emulation [linux] [patch] ptrace(2) and rfork(RFLINUXTHPN) confu o kern/29698 emulation [linux] [patch] linux ipcs doesn'work o kern/21463 emulation [linux] Linux compatability mode should not allow setu o kern/11165 emulation [ibcs2] IBCS2 doesn't work correctly with PID_MAX 9999 22 problems total. From alexbestms at math.uni-muenster.de Tue Nov 3 00:00:17 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Tue Nov 3 00:00:24 2009 Subject: ports/137332: add caution messages to some adobe products Message-ID: <200911030000.nA300GDr008127@freefall.freebsd.org> The following reply was made to PR ports/137332; it has been noted by GNATS. From: Alexander Best To: , Cc: Subject: Re: ports/137332: add caution messages to some adobe products Date: Tue, 03 Nov 2009 00:54:47 +0100 (CET) is there really a need for this? just because these ports/applications aren't maintained any more this doesn't necessarily require a warning to be issued during port build/installation. the latest security bulletin for acroread8 recommends using version 8.1.7 which is the version in ports! the latest security bulletin for acroread9 recommends using version 9.2 which is the version in ports! the latest security bulletin for flash9 recommends using version 9.0.246.0 which is the version in ports! i couldn't quite catch which version of flash10 is in the ports, but the latest security bulletin recommends using version 10.0.32.18! maybe you could report exactly which ports are suffering from security flaws. these ports should then be marked IGNORE. unless there aren't any security issues present in connection with these ports i vote for closing the PR. alex From linimon at FreeBSD.org Tue Nov 3 01:12:31 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Tue Nov 3 01:12:37 2009 Subject: ports/137332: add caution messages to some adobe products Message-ID: <200911030112.nA31CUQJ076327@freefall.freebsd.org> Synopsis: add caution messages to some adobe products State-Changed-From-To: open->feedback State-Changed-By: linimon State-Changed-When: Tue Nov 3 01:11:51 UTC 2009 State-Changed-Why: Note that submitter has been asked for feedback. http://www.freebsd.org/cgi/query-pr.cgi?pr=137332 From turutani at scphys.kyoto-u.ac.jp Tue Nov 3 14:20:04 2009 From: turutani at scphys.kyoto-u.ac.jp (Tsurutani Naoki) Date: Tue Nov 3 14:36:26 2009 Subject: ports/137332: add caution messages to some adobe products Message-ID: <200911031420.nA3EK4YA088131@freefall.freebsd.org> The following reply was made to PR ports/137332; it has been noted by GNATS. From: Tsurutani Naoki To: Alexander Best Cc: Subject: Re: ports/137332: add caution messages to some adobe products Date: Tue, 03 Nov 2009 23:11:23 +0900 Alexander Best wrote: > the latest security bulletin for flash9 recommends using version 9.0.246.0 > which is the version in ports! Yes, this is available, but it is not announced officially. www/linux-flashplugin7 is not maintained. please mark as ignore. however, some linux_base might not support www/linux-flashplugin9 or newer, and some OS versions might not use new linux_base. no other ports about adobe products has trouble, as I know. From alexbestms at math.uni-muenster.de Tue Nov 3 16:10:04 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Tue Nov 3 16:10:51 2009 Subject: kern/138880: [linux] munmap segfaults after linux_mmap2 stresstest Message-ID: <200911031610.nA3GA4Nm081554@freefall.freebsd.org> The following reply was made to PR kern/138880; it has been noted by GNATS. From: Alexander Best To: Cc: Subject: Re: kern/138880: [linux] munmap segfaults after linux_mmap2 stresstest Date: Tue, 03 Nov 2009 17:01:23 +0100 (CET) here's a linux_kdump which might show more details than truss: 1478 mmapstress08 CALL linux_mmap2(0x3e800000,0x1000,0x3,0x22,0,0) 1478 mmapstress08 RET linux_mmap2 1048576000/0x3e800000 1478 mmapstress08 CALL linux_mmap2(0x3ec00000,0x1000,0x3,0x22,0,0) 1478 mmapstress08 RET linux_mmap2 1052770304/0x3ec00000 1478 mmapstress08 CALL linux_mmap2(0x3f000000,0x1000,0x3,0x22,0,0) 1478 mmapstress08 RET linux_mmap2 1056964608/0x3f000000 1478 mmapstress08 CALL linux_mmap2(0x3f400000,0x1000,0x3,0x22,0,0) 1478 mmapstress08 RET linux_mmap2 1061158912/0x3f400000 1478 mmapstress08 CALL linux_mmap2(0x3f800000,0x1000,0x3,0x22,0,0) 1478 mmapstress08 RET linux_mmap2 1065353216/0x3f800000 1478 mmapstress08 CALL linux_mmap2(0x3fc00000,0x1000,0x3,0x22,0,0) 1478 mmapstress08 RET linux_mmap2 1069547520/0x3fc00000 1478 mmapstress08 CALL munmap(0x8050000,0x37fb0000) 1478 mmapstress08 RET munmap 0 1478 mmapstress08 PSIG SIGSEGV SIG_DFL 1478 mmapstress08 NAMI "mmapstress08.core" alex From Johan at double-l.nl Tue Nov 3 16:30:36 2009 From: Johan at double-l.nl (Johan Hendriks) Date: Tue Nov 3 16:30:42 2009 Subject: Build error virtualbox (kbuild) RELENG_8 i386 Message-ID: <57200BF94E69E54880C9BB1AF714BBCBA5714B@w2003s01.double-l.local> Hello i tried to install virtualbox, but got the following error. kBuild: Compiling kmk_gmake - /usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/src/kmk/job.c kBuild: Compiling kmk_gmake - /usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/src/kmk/misc.c kBuild: Compiling kmk_gmake - /usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/src/kmk/remake.c kBuild: Compiling kmk_gmake - /usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/src/kmk/rule.c kBuild: Compiling kmk_gmake - /usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/src/kmk/signame.c kBuild: Compiling kmk_gmake - /usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/src/kmk/version.c kBuild: Compiling kmk_gmake - /usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/src/kmk/vpath.c kBuild: Compiling kmk_gmake - /usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/src/kmk/remote-stub.c /usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/kmk_ash /usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/src/ash/mkbuiltins /usr/ports/devel/kBuild/work/kBuild-0.1. 5-p1/src/ash/shell.h /usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/src/ash/builtins.def /usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/out/freebsd.x86/release/o bj/kmk_ash/ kmk: /usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/kmk_ash: Command not found kmk: *** [/usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/out/freebsd.x86/release/ob j/kmk_ash/builtins.h] Error 127 kmk: *** Waiting for unfinished jobs.... kmk: Leaving directory `/usr/ports/devel/kBuild/work/kBuild-0.1.5-p1' kmk: Entering directory `/usr/ports/devel/kBuild/work/kBuild-0.1.5-p1' kmk: *** Exiting with status 2 gmake: *** [/usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/out/freebsd.x86/release/bo otstrap/ts-stage2-build] Error 2 ./kBuild/env.sh: info: rc=2: gmake -f bootstrap.gmk *** Error code 2 Stop in /usr/ports/devel/kBuild. *** Error code 1 Stop in /usr/ports/emulators/virtualbox. *** Error code 1 Stop in /usr/ports/emulators/virtualbox. What can I do to install virtualbox. It is RELENG_8 i386 regards, Johan Hendriks From alexbestms at math.uni-muenster.de Tue Nov 3 16:40:04 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Tue Nov 3 16:40:11 2009 Subject: ports/137332: add caution messages to some adobe products Message-ID: <200911031640.nA3Ge496009073@freefall.freebsd.org> The following reply was made to PR ports/137332; it has been noted by GNATS. From: Alexander Best To: Tsurutani Naoki , Alexander Best Cc: Subject: Re: ports/137332: add caution messages to some adobe products Date: Tue, 03 Nov 2009 17:39:13 +0100 (CET) Tsurutani Naoki schrieb am 2009-11-03: > Alexander Best wrote: > > the latest security bulletin for flash9 recommends using version > > 9.0.246.0 > > which is the version in ports! > Yes, this is available, but it is not announced officially. well. this bulletin recommends using it: http://www.adobe.com/support/security/bulletins/apsb09-10.html so i guess it doesn't matter if it's an official release or just a patch-release. > www/linux-flashplugin7 is not maintained. please mark as ignore. > however, some linux_base might not support www/linux-flashplugin9 or > newer, > and some OS versions might not use new linux_base. i guess marking the port deprecated is the right thing to do. ignore should be used when there's an actual problem with the port which isn't the case. also VuXML's last entry for flash 7 is this one: http://www.vuxml.org/freebsd/562cf6c4-b9f1-11dc-a302-000102cc8983.html so according to them the version in the ports isn't affected by any security issue. however http://www.vuxml.org/freebsd/04c6187d-2d8f-11dd-98c9-00163e000016.html and http://www.vuxml.org/freebsd/78f456fd-9c87-11dd-a55e-00163e000016.html only mention flash 9 as affected port although the description says that earlier version might be affected too. might be that the adobe security bulletins dropped flash 7 support. > no other ports about adobe products has trouble, as I know. i'll try to come up with a small patch to mark flash 7 deprecated. alex From ruidc at yahoo.com Tue Nov 3 19:51:02 2009 From: ruidc at yahoo.com (RuiDC) Date: Tue Nov 3 19:51:09 2009 Subject: VirtualBox 3, FreeBSD 8 as guest, clipboard sharing Message-ID: <26163362.post@talk.nabble.com> For me, VBox guest additions fail to start as they don't detect linux components. Has anyone gotten clipboard sharing to work with FreeBSD as a guest? If so how? RuiDC -- View this message in context: http://old.nabble.com/VirtualBox-3%2C-FreeBSD-8-as-guest%2C-clipboard-sharing-tp26163362p26163362.html Sent from the freebsd-emulation mailing list archive at Nabble.com. From Johan at double-l.nl Tue Nov 3 20:17:16 2009 From: Johan at double-l.nl (Johan Hendriks) Date: Tue Nov 3 20:17:23 2009 Subject: Build error virtualbox (kbuild) RELENG_8 i386 References: <57200BF94E69E54880C9BB1AF714BBCBA5714B@w2003s01.double-l.local> <6201873e0911030846r29d09e59r97c7841ef50e523c@mail.gmail.com> Message-ID: <57200BF94E69E54880C9BB1AF714BBCBA5714D@w2003s01.double-l.local> >Hello i tried to install virtualbox, but got the following error. >kBuild: Compiling kmk_gmake - >/usr/ports/devel/kBuild/work/kBuild-0.1.5-p1/src/kmk/job.c > > > Stop in /usr/ports/devel/kBuild. >*** Error code 1 > Stop in /usr/ports/emulators/virtualbox. > *** Error code 1 > Stop in /usr/ports/emulators/virtualbox. > What can I do to install virtualbox. > It is RELENG_8 i386 > http://wiki.freebsd.org/VirtualBox > Are having issues with the portmaster stuff listed there? > Vbox compiles fine for me, is your ports tree up to date eg portsnap fetch extract No it is a clean install for virtualbox. No old version. (it stops in usr/ports/devel/kBuild.) And yes the ports tree is up to date, not with portsnap but with csup Thanks for your time, Regards, Johan From kabaev at gmail.com Tue Nov 3 21:14:25 2009 From: kabaev at gmail.com (Alexander Kabaev) Date: Tue Nov 3 21:14:31 2009 Subject: Build error virtualbox (kbuild) RELENG_8 i386 In-Reply-To: <57200BF94E69E54880C9BB1AF714BBCBA5714D@w2003s01.double-l.local> References: <57200BF94E69E54880C9BB1AF714BBCBA5714B@w2003s01.double-l.local> <6201873e0911030846r29d09e59r97c7841ef50e523c@mail.gmail.com> <57200BF94E69E54880C9BB1AF714BBCBA5714D@w2003s01.double-l.local> Message-ID: <20091103161412.050b3f9e@kan.dnsalias.net> On Tue, 3 Nov 2009 21:17:11 +0100 "Johan Hendriks" wrote: Let me guess, you are running i386 32 bit FreeBSD? This is a bug in kBuild that is provoked by FreeBSD VFS namecache peculiarity. The patch at http://people.freebsd.org/~kan/kBuild.diff should give your kBuild a fighting chance. -- Alexander Kabaev -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 188 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20091103/02e41093/signature.pgp From Johan at double-l.nl Tue Nov 3 21:43:24 2009 From: Johan at double-l.nl (Johan Hendriks) Date: Tue Nov 3 21:43:30 2009 Subject: Build error virtualbox (kbuild) RELENG_8 i386 References: <57200BF94E69E54880C9BB1AF714BBCBA5714B@w2003s01.double-l.local><6201873e0911030846r29d09e59r97c7841ef50e523c@mail.gmail.com><57200BF94E69E54880C9BB1AF714BBCBA5714D@w2003s01.double-l.local> <20091103161412.050b3f9e@kan.dnsalias.net> Message-ID: <57200BF94E69E54880C9BB1AF714BBCBA5714E@w2003s01.double-l.local> >Let me guess, you are running i386 32 bit FreeBSD? > >This is a bug in kBuild that is provoked by FreeBSD VFS namecache >peculiarity. The patch at http://people.freebsd.org/~kan/kBuild.diff >should give your kBuild a fighting chance. > >-- >Alexander Kabaev Thanks that did the trick. And yes I am running i386 FreeBSD (like the subject says ;-) ) Thank you very much again. regards, Johan Hendriks No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 8.5.424 / Virus Database: 270.14.46/2477 - Release Date: 11/02/09 19:39:00 From linimon at FreeBSD.org Thu Nov 5 00:53:50 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Thu Nov 5 00:53:56 2009 Subject: kern/140279: [linux] [patch] fix typos in sys/compat/linux/linux_ipc.c Message-ID: <200911050053.nA50roiW021842@freefall.freebsd.org> Synopsis: [linux] [patch] fix typos in sys/compat/linux/linux_ipc.c Responsible-Changed-From-To: freebsd-bugs->freebsd-emulation Responsible-Changed-By: linimon Responsible-Changed-When: Thu Nov 5 00:53:27 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=140279 From alexbestms at math.uni-muenster.de Thu Nov 5 00:54:23 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Thu Nov 5 00:54:29 2009 Subject: Bug locating path for linux_mkdir Message-ID: i'm not able to reproduce this problem anymore under 9-CURRENT. i'm using the following test code running emulators/linux_dist-gentoo-stage3 (for chroot and for compilation with cc) and linux_base-f10: #include #include #include main() { mkdir("/tmp/.test", 511 ); printf("first errno: %d\n", errno); mkdir("/tmp/.test/test2/", 511 ); printf("second errno: %d\n", errno); } the result is: first errno: 0 second errno: 0 was a problem report submitted back then? alex From alexbestms at math.uni-muenster.de Thu Nov 5 01:20:58 2009 From: alexbestms at math.uni-muenster.de (Alexander Best) Date: Thu Nov 5 01:21:04 2009 Subject: Bug locating path for linux_mkdir Message-ID: since it's been a while this thread has been started here's the post i'm referring to: http://lists.freebsd.org/pipermail/freebsd-emulation/2006-July/002336.html cheers. alex From netchild at FreeBSD.org Thu Nov 5 07:35:16 2009 From: netchild at FreeBSD.org (netchild@FreeBSD.org) Date: Thu Nov 5 07:35:22 2009 Subject: kern/140279: [linux] [patch] fix typos in sys/compat/linux/linux_ipc.c Message-ID: <200911050735.nA57ZGUY095895@freefall.freebsd.org> Synopsis: [linux] [patch] fix typos in sys/compat/linux/linux_ipc.c Responsible-Changed-From-To: freebsd-emulation-> netchild Responsible-Changed-By: netchild Responsible-Changed-When: Thu Nov 5 07:34:45 UTC 2009 Responsible-Changed-Why: I take this PR. http://www.freebsd.org/cgi/query-pr.cgi?pr=140279 From amvandemore at gmail.com Thu Nov 5 17:00:41 2009 From: amvandemore at gmail.com (Adam Vande More) Date: Thu Nov 5 17:00:56 2009 Subject: xen-tools like web interface for virtualbox Message-ID: <6201873e0911050900q1280f29bnd4bfffd53819fa84@mail.gmail.com> Hi, I'd like to start a web-based management system for virtualbox. Seeking comments on anything important to consider like licensing issues, and technical structure issues. Any features you think would be useful are welcome discussion as well. Thanks, -- Adam Vande More From rdivacky at freebsd.org Thu Nov 5 17:23:57 2009 From: rdivacky at freebsd.org (Roman Divacky) Date: Thu Nov 5 17:24:20 2009 Subject: xen-tools like web interface for virtualbox In-Reply-To: <6201873e0911050900q1280f29bnd4bfffd53819fa84@mail.gmail.com> References: <6201873e0911050900q1280f29bnd4bfffd53819fa84@mail.gmail.com> Message-ID: <20091105172252.GA31920@freebsd.org> On Thu, Nov 05, 2009 at 11:00:40AM -0600, Adam Vande More wrote: > Hi, > > I'd like to start a web-based management system for virtualbox. Seeking > comments on anything important to consider like licensing issues, and > technical structure issues. Any features you think would be useful are > welcome discussion as well. maybe you want to take a look at http://libvirt.org/ ? From decke at bluelife.at Thu Nov 5 18:36:27 2009 From: decke at bluelife.at (Bernhard Froehlich) Date: Thu Nov 5 18:36:34 2009 Subject: xen-tools like web interface for virtualbox In-Reply-To: <6201873e0911050900q1280f29bnd4bfffd53819fa84@mail.gmail.com> References: <6201873e0911050900q1280f29bnd4bfffd53819fa84@mail.gmail.com> Message-ID: <76a3e89017b18518691e568707540c27.squirrel@webmail.itac.at> On Thu, November 5, 2009 6:00 pm, Adam Vande More wrote: > Hi, > > I'd like to start a web-based management system for virtualbox. Seeking > comments on anything important to consider like licensing issues, and > technical structure issues. Any features you think would be useful are > welcome discussion as well. > You should have a look at vboxweb [1] which is probably what you are searching for. I've created a port [2] for it if you want to test it on FreeBSD. [1] http://code.google.com/p/vboxweb/ [2] http://svn.bluelife.at/index.cgi/packages/browse/blueports/www/vboxweb -- Bernhard Fr?hlich http://www.bluelife.at/ From sfourman at gmail.com Thu Nov 5 20:15:22 2009 From: sfourman at gmail.com (Sam Fourman Jr.) Date: Thu Nov 5 20:15:30 2009 Subject: xen-tools like web interface for virtualbox In-Reply-To: <20091105172252.GA31920@freebsd.org> References: <6201873e0911050900q1280f29bnd4bfffd53819fa84@mail.gmail.com> <20091105172252.GA31920@freebsd.org> Message-ID: <11167f520911051215q24651001m8dc6c01712ec96ec@mail.gmail.com> On Thu, Nov 5, 2009 at 11:22 AM, Roman Divacky wrote: > On Thu, Nov 05, 2009 at 11:00:40AM -0600, Adam Vande More wrote: >> Hi, >> >> I'd like to start a web-based management system for virtualbox. ?Seeking >> comments on anything important to consider like licensing issues, and >> technical structure issues. ?Any features you think would be useful are >> welcome discussion as well. > > maybe you want to take a look at http://libvirt.org/ ? yes http://libvirt.org is the way to go. that way it will work when Xen Dom0 support is added as well Sam Fourman Jr. Fourman Networks From amvandemore at gmail.com Fri Nov 6 18:52:15 2009 From: amvandemore at gmail.com (Adam Vande More) Date: Fri Nov 6 18:52:22 2009 Subject: xen-tools like web interface for virtualbox In-Reply-To: <76a3e89017b18518691e568707540c27.squirrel@webmail.itac.at> References: <6201873e0911050900q1280f29bnd4bfffd53819fa84@mail.gmail.com> <76a3e89017b18518691e568707540c27.squirrel@webmail.itac.at> Message-ID: <6201873e0911061052r5c90924dy58786f06ae6f0c28@mail.gmail.com> On Thu, Nov 5, 2009 at 12:36 PM, Bernhard Froehlich wrote: > On Thu, November 5, 2009 6:00 pm, Adam Vande More wrote: > > Hi, > > > > I'd like to start a web-based management system for virtualbox. Seeking > > comments on anything important to consider like licensing issues, and > > technical structure issues. Any features you think would be useful are > > welcome discussion as well. > > > > You should have a look at vboxweb [1] which is probably what you are > searching for. I've created a port [2] for it if you want to test it on > FreeBSD. > > > [1] http://code.google.com/p/vboxweb/ > [2] http://svn.bluelife.at/index.cgi/packages/browse/blueports/www/vboxweb > Thanks for the info, I have no need to reinvent the wheel. I think I'll try and add some automated iscsi support in there and it should be close to what I was thinking. -- Adam Vande More From bsam at ipt.ru Sat Nov 7 13:39:41 2009 From: bsam at ipt.ru (Boris Samorodov) Date: Sat Nov 7 13:39:50 2009 Subject: upcoming fontconfig trouble Message-ID: <88423939@bb.ipt.ru> Hello List, the upcoming change of fontconfig from 2.6.0 to 7.2.3 will break compatibility with current linux-f10-fontconfig (linux apps get SIGSEGV -- acroread, skype, realplayer were tested). Well, what shall we do to overcome it? I don't know what to do with fc4 ports as well since I didn't use them for a long time. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve From bugmaster at FreeBSD.org Mon Nov 9 11:06:50 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 9 11:07:47 2009 Subject: Current problem reports assigned to freebsd-emulation@FreeBSD.org Message-ID: <200911091106.nA9B6nm7078957@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/140156 emulation [linux] cdparanoia fails to read drive data o kern/139423 emulation [parallels] Networking does not work on amd64 guest on o kern/138944 emulation [parallels] [regression] Parallels no longer works in o kern/138880 emulation [linux] munmap segfaults after linux_mmap2 stresstest o kern/138860 emulation [linux] linux_socketcall() causing buffer overflow f ports/137332 emulation add caution messages to some adobe products s ports/136321 emulation x11-toolkits/linux-pango: please update linux based po o ports/136229 emulation [linux] certain linux apps look for libraries using a o ports/135337 emulation [PATCH] emulators/linux_base-f10: incorrect bash usage o kern/133144 emulation [linux] linuxulator 2.6 crashes with nvidias libGL.so. o kern/130724 emulation [linprocfs] [patch] cpuinfo in linprocfs is dated, cau o kern/129169 emulation [linux] [patch] Linux Emulation ENOTCONN error using n f ports/127018 emulation Linuxulator incapable of using FreeBSD's LDAP environm o kern/126232 emulation [linux] Linux ioctl TCGETS (0x5401) always fails o kern/73777 emulation [linux] [patch] linux emulation: root dir special hand a kern/72920 emulation [linux]: path "prefixing" is not done on unix domain s o kern/56451 emulation [linprocfs] /compat/linux/proc/cpuinfo gives wrong CPU o kern/41543 emulation [patch] [request] easier wine/w23 support o kern/39201 emulation [linux] [patch] ptrace(2) and rfork(RFLINUXTHPN) confu o kern/29698 emulation [linux] [patch] linux ipcs doesn'work o kern/21463 emulation [linux] Linux compatability mode should not allow setu o kern/11165 emulation [ibcs2] IBCS2 doesn't work correctly with PID_MAX 9999 22 problems total. From Johan at double-l.nl Mon Nov 9 11:57:03 2009 From: Johan at double-l.nl (Johan Hendriks) Date: Mon Nov 9 11:57:38 2009 Subject: Can not start Virtualbox Message-ID: <57200BF94E69E54880C9BB1AF714BBCB0111BF@w2003s01.double-l.local> Hello I have installed VirtualBox on My FreeBSD RELENG_8 i386. When i try to start VirtualBox as a normal user account i get the following error. VirtualBox: supR3HardenedVerifyDir: Cannot trust the directory ".": not owned by root (st_uid=1001) What am i doing wrong? regards, Johan Hendriks From adamk at voicenet.com Mon Nov 9 12:22:38 2009 From: adamk at voicenet.com (Adam K Kirchhoff) Date: Mon Nov 9 12:22:45 2009 Subject: Can not start Virtualbox In-Reply-To: <57200BF94E69E54880C9BB1AF714BBCB0111BF@w2003s01.double-l.local> References: <57200BF94E69E54880C9BB1AF714BBCB0111BF@w2003s01.double-l.local> Message-ID: <20091109070915.184f4dee@memory.visualtech.com> On Mon, 9 Nov 2009 13:00:57 +0100 "Johan Hendriks" wrote: > > Hello > I have installed VirtualBox on My FreeBSD RELENG_8 i386. > When i try to start VirtualBox as a normal user account i get the following error. > VirtualBox: supR3HardenedVerifyDir: Cannot trust the directory ".": not owned by root (st_uid=1001) > > What am i doing wrong? Your user needs to be in the vboxusers group. Adam From Johan at double-l.nl Mon Nov 9 12:55:24 2009 From: Johan at double-l.nl (Johan Hendriks) Date: Mon Nov 9 12:55:31 2009 Subject: Can not start Virtualbox References: <57200BF94E69E54880C9BB1AF714BBCB0111BF@w2003s01.double-l.local><20091109070915.184f4dee@memory.visualtech.com><57200BF94E69E54880C9BB1AF714BBCBA5718F@w2003s01.double-l.local> <20091109074518.3ab8c4be@memory.visualtech.com> Message-ID: <57200BF94E69E54880C9BB1AF714BBCBA57190@w2003s01.double-l.local> >> >> >> >> Hello >> >> I have installed VirtualBox on My FreeBSD RELENG_8 i386. >> >> When i try to start VirtualBox as a normal user account i get the >> following error. >> >> VirtualBox: supR3HardenedVerifyDir: Cannot trust the directory ".": >> not owned by root (st_uid=1001) >> >> >> >> What am i doing wrong? >> >> >Your user needs to be in the vboxusers group. >> >> >Adam >> >> I have the following line in /etc/group >> vboxusers:*:920:johan >> >Did you add your user to that group by editing the file manually? I've >noticed that when I do that, I have to reboot for the permission to >kick in for some reason. >Adam Yes i did it manually, but the machine has been restarted already. Regards, Johan No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 8.5.425 / Virus Database: 270.14.55/2490 - Release Date: 11/09/09 07:39:00 From Johan at double-l.nl Mon Nov 9 13:08:45 2009 From: Johan at double-l.nl (Johan Hendriks) Date: Mon Nov 9 13:08:52 2009 Subject: Can not start Virtualbox References: <57200BF94E69E54880C9BB1AF714BBCB0111BF@w2003s01.double-l.local><20091109070915.184f4dee@memory.visualtech.com><57200BF94E69E54880C9BB1AF714BBCBA5718F@w2003s01.double-l.local><20091109074518.3ab8c4be@memory.visualtech.com><57200BF94E69E54880C9BB1AF714BBCBA57190@w2003s01.double-l.local> <20091109080657.1d20729b@memory.visualtech.com> Message-ID: <57200BF94E69E54880C9BB1AF714BBCBA57192@w2003s01.double-l.local> >> >> >> >> >> >> Hello >> >> >> I have installed VirtualBox on My FreeBSD RELENG_8 i386. >> >> >> When i try to start VirtualBox as a normal user account i get the >> >> following error. >> >> >> VirtualBox: supR3HardenedVerifyDir: Cannot trust the directory >> ".": >> >> not owned by root (st_uid=1001) >> >> >> >> >> >> What am i doing wrong? >> >> >> >> >Your user needs to be in the vboxusers group. >> >> >> >> >Adam >> >> >> >> I have the following line in /etc/group >> >> vboxusers:*:920:johan >> >> >> >> >Did you add your user to that group by editing the file manually? I've >> >noticed that when I do that, I have to reboot for the permission to >> >kick in for some reason. >> >> >Adam >> >> Yes i did it manually, but the machine has been restarted already. >Sorry, I'm out of ideas, then. >Adam No problem, and thanks for your time. regards, Johan Hendriks No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 8.5.425 / Virus Database: 270.14.55/2490 - Release Date: 11/09/09 07:39:00 From daichi at ongs.co.jp Wed Nov 11 06:42:35 2009 From: daichi at ongs.co.jp (Daichi GOTO) Date: Wed Nov 11 06:42:41 2009 Subject: VirtualBox 3.0.51.r22902 on CURRENT/amd64 leads system freeze within bridge networking Message-ID: <20091111154233.5c9d08ed.daichi@ongs.co.jp> I have tried to use VirtualBox 3.0.51.r22902 within bridge networking. In any ways, VirtualBox gets system freeze. Environment: VirtualBox 3.0.51.r22902 FreeBSD 9.0-CURRENT (Fri Nov 6 10:09:25 JST 2009) amd64 Core2Quad Q8300 (xVT not supported version) Method #1 kldload vboxdrv kldload vboxnetflt kldload vboxnetadp VirtualBox -> Bridge Networking -> choose of re0 (re0 is used on host) GuestOS starts boot and host gets freeze immediately Method #2 kldload vboxdrv kldload vboxnetflt kldload vboxnetadp VirtualBox -> Bridge Networking -> choose of fxp0 (re0 is not used on host, just plugged) GuestOS starts boot and host gets freeze immediately Method #3 kldload vboxdrv kldload if_bridge setup tap interface setup bridge intarace VirtualBox -> Bridge Networking -> choose of tap0 GuestOS starts boot and host gets freeze immediately Method #4 kldload vboxdrv kldload vboxnetflt kldload vboxnetadp kldload if_bridge setup tap interface setup bridge intarace VirtualBox -> Bridge Networking -> choose of tap0 GuestOS starts boot and host gets freeze immediately It looks like VirtualBox on amd64 cannot use bridge feature. Could anyone use bridge networking on amd64? The lack of xVT technology leads this issue? If anyone has any ideas, please teach me. Thanks -- Daichi GOTO CEO | ONGS Inc. 81-42-316-7945 | daichi@ongs.co.jp | http://www.ongs.co.jp LinkedIn: http://linkedin.com/in/daichigoto From ivoras at freebsd.org Wed Nov 11 16:01:36 2009 From: ivoras at freebsd.org (Ivan Voras) Date: Wed Nov 11 16:01:43 2009 Subject: VirtualBox 3.0.51.r22902 on CURRENT/amd64 leads system freeze within bridge networking In-Reply-To: <20091111154233.5c9d08ed.daichi@ongs.co.jp> References: <20091111154233.5c9d08ed.daichi@ongs.co.jp> Message-ID: Daichi GOTO wrote: > I have tried to use VirtualBox 3.0.51.r22902 within bridge > networking. In any ways, VirtualBox gets system freeze. I'm using virtualbox-3.0.51.r23073 and it works fine, though with a difference to your setup: > > Environment: > VirtualBox 3.0.51.r22902 > FreeBSD 9.0-CURRENT (Fri Nov 6 10:09:25 JST 2009) amd64 Mine is 8.0-RC2 > Core2Quad Q8300 (xVT not supported version) VT is supported on mine. > Method #1 > kldload vboxdrv > kldload vboxnetflt > kldload vboxnetadp > VirtualBox -> Bridge Networking -> choose of re0 > (re0 is used on host) > GuestOS starts boot and host gets freeze immediately I'm only loading vboxdrv and vboxnetflt. My guest is WinXP 32-bit. Are you sure it's a freeze and not a panic/break to debugger in text console? From daichi at ongs.co.jp Thu Nov 12 00:33:27 2009 From: daichi at ongs.co.jp (Daichi GOTO) Date: Thu Nov 12 00:33:34 2009 Subject: VirtualBox 3.0.51.r22902 on CURRENT/amd64 leads system freeze within bridge networking In-Reply-To: References: <20091111154233.5c9d08ed.daichi@ongs.co.jp> Message-ID: <20091112093325.4d2d4d22.daichi@ongs.co.jp> On Wed, 11 Nov 2009 17:00:45 +0100 Ivan Voras wrote: > Daichi GOTO wrote: > > I have tried to use VirtualBox 3.0.51.r22902 within bridge > > networking. In any ways, VirtualBox gets system freeze. > > I'm using virtualbox-3.0.51.r23073 and it works fine, though with a > difference to your setup: How differences bewteen r22902 and r23073? # your original port? > > Environment: > > VirtualBox 3.0.51.r22902 > > FreeBSD 9.0-CURRENT (Fri Nov 6 10:09:25 JST 2009) amd64 > > Mine is 8.0-RC2 > > > Core2Quad Q8300 (xVT not supported version) > > VT is supported on mine. humm... I guess VT is key point of this issue. Can anyone use bridge networking with non-VT version CPU? > > Method #1 > > kldload vboxdrv > > kldload vboxnetflt > > kldload vboxnetadp > > VirtualBox -> Bridge Networking -> choose of re0 > > (re0 is used on host) > > GuestOS starts boot and host gets freeze immediately > > I'm only loading vboxdrv and vboxnetflt. I tried only loading vboxdrv and vboxnetflt, and the same result. > My guest is WinXP 32-bit. Sure, the same. > Are you sure it's a freeze and not a panic/break to debugger in text > console? It looks like a freeze not a panic, but I do not know well. How can I get a debugger console mode in X freezing situation? It there something of technique to get it? > _______________________________________________ > freebsd-emulation@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-emulation > To unsubscribe, send any mail to "freebsd-emulation-unsubscribe@freebsd.org" -- Daichi GOTO CEO | ONGS Inc. 81-42-316-7945 | daichi@ongs.co.jp | http://www.ongs.co.jp LinkedIn: http://linkedin.com/in/daichigoto From oberman at es.net Thu Nov 12 01:47:47 2009 From: oberman at es.net (Kevin Oberman) Date: Thu Nov 12 01:48:00 2009 Subject: VirtualBox 3.0.51.r22902 on CURRENT/amd64 leads system freeze within bridge networking In-Reply-To: Your message of "Thu, 12 Nov 2009 09:33:25 +0900." <20091112093325.4d2d4d22.daichi@ongs.co.jp> Message-ID: <20091112014746.61A371CC0E@ptavv.es.net> > Date: Thu, 12 Nov 2009 09:33:25 +0900 > From: Daichi GOTO > Sender: owner-freebsd-emulation@freebsd.org > > On Wed, 11 Nov 2009 17:00:45 +0100 > Ivan Voras wrote: > > Daichi GOTO wrote: > > > I have tried to use VirtualBox 3.0.51.r22902 within bridge > > > networking. In any ways, VirtualBox gets system freeze. > > > > I'm using virtualbox-3.0.51.r23073 and it works fine, though with a > > difference to your setup: > > How differences bewteen r22902 and r23073? > # your original port? > > > > Environment: > > > VirtualBox 3.0.51.r22902 > > > FreeBSD 9.0-CURRENT (Fri Nov 6 10:09:25 JST 2009) amd64 > > > > Mine is 8.0-RC2 > > > > > Core2Quad Q8300 (xVT not supported version) > > > > VT is supported on mine. > > humm... I guess VT is key point of this issue. > Can anyone use bridge networking with non-VT version CPU? I use it on a single CPU Pentium-M system. Works fine (or has in the past). I load ng_ether, vboxnetflt, vboxnetadp, and vboxdrv. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From office at atn.com Fri Nov 13 13:41:19 2009 From: office at atn.com (Dr. Harris Conklin) Date: Fri Nov 13 13:41:34 2009 Subject: Your Ref: SNT/ATM/822 Message-ID: <20091113134119.0B7D110656A4@hub.freebsd.org> Our Ref: FGN/SNT/RAL Your Ref: SNT/ATM/822 Attn: I am directed to inform you that your payment verification and confirmations are correct, Therefore we are happy to inform you that arrangements have been concluded to effect your payment as soon as possible and in our bid to transparency. It is my pleasure to inform you that ATM Card Number: 5428050011004432 have been approved in your favor; The ATM Card Value is $315,810.00 USD (Three Hundred and Fifteen Thousand, Eight Hundred and Ten USD Only) You are advised that a maximum withdrawal value of $5,000.00 USD is permitted on withdrawal per day and are duly Inter Switch so you can make withdrawal in any location and ATM Center of your choice. We have concluded delivery arrangement with the ups courier services. Please note that the UPS Courier Company is fully insured by Nicon Insurance Corporation. Please you advice to pay for the delivery cost of your parcel which is ($155.00USD) so that I will know how to proceed, and please be informed that the delivery will be made to your address in 48 hours (2 days) after our confirmation of this payment for delivery, as you know that the delivery fee receipt will be used to attach on your payment delivery documents to avoid being delayed by customs. Treat urgently and note that your ATM Card is ready and available for dispatch to you. Please call me immediately you receive this email. My email is dr.harrisc@gala.net Regards, Dr. Harris Conklin Office Number: +2348032312897 HEAD OF INTENTIONAL REMITTANCE DEPARTMENT From edwin at FreeBSD.org Sun Nov 15 16:50:16 2009 From: edwin at FreeBSD.org (edwin@FreeBSD.org) Date: Sun Nov 15 16:50:28 2009 Subject: ports/140573: [patch] ftp/linux-f10-curl: update to latest version Message-ID: <200911151650.nAFGoFbC030601@freefall.freebsd.org> Synopsis: [patch] ftp/linux-f10-curl: update to latest version Responsible-Changed-From-To: freebsd-ports-bugs->emulation Responsible-Changed-By: edwin Responsible-Changed-When: Sun Nov 15 16:50:15 UTC 2009 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=140573 From edwin at FreeBSD.org Sun Nov 15 17:00:16 2009 From: edwin at FreeBSD.org (edwin@FreeBSD.org) Date: Sun Nov 15 17:00:28 2009 Subject: ports/140575: [patch] devel/linux-f10-nspr: update to latest version Message-ID: <200911151700.nAFH0Gaj038504@freefall.freebsd.org> Synopsis: [patch] devel/linux-f10-nspr: update to latest version Responsible-Changed-From-To: freebsd-ports-bugs->emulation Responsible-Changed-By: edwin Responsible-Changed-When: Sun Nov 15 17:00:15 UTC 2009 Responsible-Changed-Why: Over to maintainer (via the GNATS Auto Assign Tool) http://www.freebsd.org/cgi/query-pr.cgi?pr=140575 From bsam at FreeBSD.org Sun Nov 15 20:22:47 2009 From: bsam at FreeBSD.org (bsam@FreeBSD.org) Date: Sun Nov 15 20:22:54 2009 Subject: ports/140573: [patch] ftp/linux-f10-curl: update to latest version Message-ID: <200911152022.nAFKMlrl017767@freefall.freebsd.org> Synopsis: [patch] ftp/linux-f10-curl: update to latest version State-Changed-From-To: open->closed State-Changed-By: bsam State-Changed-When: Sun Nov 15 20:22:04 UTC 2009 State-Changed-Why: Committed, thanks! PORTREVISION was nulled. http://www.freebsd.org/cgi/query-pr.cgi?pr=140573 From bsam at FreeBSD.org Sun Nov 15 20:26:01 2009 From: bsam at FreeBSD.org (bsam@FreeBSD.org) Date: Sun Nov 15 20:26:07 2009 Subject: ports/140575: [patch] devel/linux-f10-nspr: update to latest version Message-ID: <200911152026.nAFKQ0pb017839@freefall.freebsd.org> Synopsis: [patch] devel/linux-f10-nspr: update to latest version State-Changed-From-To: open->closed State-Changed-By: bsam State-Changed-When: Sun Nov 15 20:25:51 UTC 2009 State-Changed-Why: Committed, thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=140575 From dfilter at FreeBSD.ORG Sun Nov 15 20:30:03 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Sun Nov 15 20:30:14 2009 Subject: ports/140573: commit references a PR Message-ID: <200911152030.nAFKU30S017984@freefall.freebsd.org> The following reply was made to PR ports/140573; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: ports/140573: commit references a PR Date: Sun, 15 Nov 2009 20:21:46 +0000 (UTC) bsam 2009-11-15 20:21:38 UTC FreeBSD ports repository Modified files: ftp/linux-f10-curl Makefile distinfo.i386 Log: Update to version 7.19.4-6.fc10. PR: ports/140573 Submitted by: Glen Barber Revision Changes Path 1.12 +2 -3 ports/ftp/linux-f10-curl/Makefile 1.8 +9 -9 ports/ftp/linux-f10-curl/distinfo.i386 _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From dfilter at FreeBSD.ORG Sun Nov 15 20:30:05 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Sun Nov 15 20:30:14 2009 Subject: ports/140575: commit references a PR Message-ID: <200911152030.nAFKU5dZ018120@freefall.freebsd.org> The following reply was made to PR ports/140575; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: ports/140575: commit references a PR Date: Sun, 15 Nov 2009 20:25:27 +0000 (UTC) bsam 2009-11-15 20:25:13 UTC FreeBSD ports repository Modified files: devel/linux-f10-nspr Makefile distinfo.i386 Log: Update to version 4.7.6-1.fc10.1. PR: ports/140575 Submitted by: Glen Barber Revision Changes Path 1.5 +2 -2 ports/devel/linux-f10-nspr/Makefile 1.5 +6 -6 ports/devel/linux-f10-nspr/distinfo.i386 _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From dougb at FreeBSD.org Sun Nov 15 21:54:25 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Sun Nov 15 21:54:32 2009 Subject: How do I make npviewer.bin respect $TMPDIR ?? Message-ID: <4B007898.8090303@FreeBSD.org> Howdy, I'm -current, i386, linux_base-f10-10_2, and linux-f10-flashplugin-10.0r32; all with the latest firefox 35. It all works fine, until my teeny tiny (24M) memory disk /tmp gets full. I have created a wrapper script for firefox to set TMPDIR (and TMP and TEMPDIR just in case) to a large partition on local disk, which works for firefox proper, but npviewer.bin is still putting its temp files on the real /tmp. So, how do I whip it into shape? Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From daichi at ongs.co.jp Mon Nov 16 01:25:46 2009 From: daichi at ongs.co.jp (Daichi GOTO) Date: Mon Nov 16 01:25:53 2009 Subject: JFYI: VirtualBox-3.0.51.r22902_2 bridge networking freeze issue (solved) Message-ID: At last, I have found an issue situation of system freeze led by bridge networking. With Vimage enable built kernel, bridge networking feature will lead system freeze. checked environment: FreeBSD 9.0-CURRENT #44: Mon Nov 16 09:51:20 JST 2009 amd64 virtualbox-3.0.51.r22902_2 Core2 Quad Q9550 I have replaced to Q9550 instead of Q8300 to get VT feature, but this was not relevant (But from this change, I got an ability to use 64bit OS. My test environment has been extended ;-). Second, I have got rid of some compile options (e.x. CPUTYPE=core2) and ccache caches, but this was not relevant, too. Third, I have changed my BIOS settings and update thats version, yes living up to your expectations, this was not relevant, too. Finally, I have rolled back my kernel to GENERIC and bridge networking works correctly. Step by step adding kernel options, at last, I have found that Vimage feature is a cause of this problem. Thanks PS Vimage developer, do you have any ideas? Or with this issue, VirtualBox side should treat this problem? -- Daichi GOTO CEO | ONGS Inc. 81-42-316-7945 | daichi@ongs.co.jp | http://www.ongs.co.jp LinkedIn: http://linkedin.com/in/daichigoto From daichi at ongs.co.jp Mon Nov 16 02:16:01 2009 From: daichi at ongs.co.jp (Daichi GOTO) Date: Mon Nov 16 02:16:14 2009 Subject: JFYI: VirtualBox-3.0.51.r22902_2 bridge networking freeze issue (solved) In-Reply-To: References: Message-ID: <4C41BAAF-50D4-4321-BAB3-48967A049CAE@ongs.co.jp> On Nov 16, 2009, at 10:57 AM, Ryan Stone wrote: > Can you reproduce the problem with WITNESS and INVARIANTS enabled? Test case: FINE: WITNESS/INVARIANTS Enabled, Vimage Disabled FINE: WITNESS/INVARIANTS Disabled, Vimage Disabled FREEZE: WITNESS/INVARIANTS Disabled, Vimage Enabled NOT TESTED: WITNESS/INVARIANTS Enabled, Vimage Enabled I'll test last case ASAP. > It's probably a deadlock, and WITNESS is quite good at identifying > potential deadlocks. > > WITNESS sends its output to the console, so make sure that you're > watching it as you try to reproduce the freeze. Please tell me how to watch messaging to console in such a freeze situation. > Ryan -- Daichi GOTO CEO | ONGS Inc. 81-42-316-7945 | daichi@ongs.co.jp | http://www.ongs.co.jp LinkedIn: http://linkedin.com/in/daichigoto From rysto32 at gmail.com Mon Nov 16 02:25:57 2009 From: rysto32 at gmail.com (Ryan Stone) Date: Mon Nov 16 02:26:09 2009 Subject: JFYI: VirtualBox-3.0.51.r22902_2 bridge networking freeze issue (solved) In-Reply-To: References: Message-ID: Can you reproduce the problem with WITNESS and INVARIANTS enabled? It's probably a deadlock, and WITNESS is quite good at identifying potential deadlocks. WITNESS sends its output to the console, so make sure that you're watching it as you try to reproduce the freeze. Ryan From daichi at ongs.co.jp Mon Nov 16 02:35:55 2009 From: daichi at ongs.co.jp (Daichi GOTO) Date: Mon Nov 16 02:36:02 2009 Subject: JFYI: VirtualBox-3.0.51.r22902_2 bridge networking freeze issue (solved) In-Reply-To: <4C41BAAF-50D4-4321-BAB3-48967A049CAE@ongs.co.jp> References: <4C41BAAF-50D4-4321-BAB3-48967A049CAE@ongs.co.jp> Message-ID: On Nov 16, 2009, at 11:15 AM, Daichi GOTO wrote: > On Nov 16, 2009, at 10:57 AM, Ryan Stone wrote: >> Can you reproduce the problem with WITNESS and INVARIANTS enabled? > > Test case: > FINE: WITNESS/INVARIANTS Enabled, Vimage Disabled > FINE: WITNESS/INVARIANTS Disabled, Vimage Disabled > FREEZE: WITNESS/INVARIANTS Disabled, Vimage Enabled > NOT TESTED: WITNESS/INVARIANTS Enabled, Vimage Enabled FINE: WITNESS/INVARIANTS Enabled, Vimage Disabled FINE: WITNESS/INVARIANTS Disabled, Vimage Disabled FREEZE: WITNESS/INVARIANTS Disabled, Vimage Enabled FREEZE: WITNESS/INVARIANTS Enabled, Vimage Enabled Do you have any ideas? > I'll test last case ASAP. > >> It's probably a deadlock, and WITNESS is quite good at identifying >> potential deadlocks. >> >> WITNESS sends its output to the console, so make sure that you're >> watching it as you try to reproduce the freeze. > > Please tell me how to watch messaging to console in such a freeze > situation. > >> Ryan > > -- > Daichi GOTO > CEO | ONGS Inc. > 81-42-316-7945 | daichi@ongs.co.jp | http://www.ongs.co.jp > LinkedIn: http://linkedin.com/in/daichigoto > > _______________________________________________ > freebsd-emulation@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-emulation > To unsubscribe, send any mail to "freebsd-emulation-unsubscribe@freebsd.org" -- Daichi GOTO CEO | ONGS Inc. 81-42-316-7945 | daichi@ongs.co.jp | http://www.ongs.co.jp LinkedIn: http://linkedin.com/in/daichigoto From daichi at ongs.co.jp Mon Nov 16 08:49:34 2009 From: daichi at ongs.co.jp (Daichi GOTO) Date: Mon Nov 16 08:49:47 2009 Subject: FreeBSD 8.0-RC3/amd64 cannot boot on VirtualBox Message-ID: <20091116174933.4ab2354d.daichi@ongs.co.jp> FreeBSD 8.0-RC3/amd64 cannot boot on VirtualBox. Boot will stop and consume 100% cpu power during boot sequence as displaying as follow: Trying to mount rott from ufs:/dev/md0 warning: no time-of-day clock registered, system time will not be set accurately checked environment: FreeBSD 9.0-CURRENT #44: Mon Nov 16 09:51:20 JST 2009 amd64 Core2 Quad Q9550 virtualbox-3.0.51.r22902_2 cpu: Core2 Quad Q9550 1-core mem: 1024MB VT-x: enable nested paging: disable Is there anyone can boot 8.0-RC3/amd64 on VirtualBox? -- Daichi GOTO CEO | ONGS Inc. 81-42-316-7945 | daichi@ongs.co.jp | http://www.ongs.co.jp LinkedIn: http://linkedin.com/in/daichigoto From danny at cs.huji.ac.il Mon Nov 16 10:33:54 2009 From: danny at cs.huji.ac.il (Daniel Braniss) Date: Mon Nov 16 10:34:07 2009 Subject: FreeBSD 8.0-RC3/amd64 cannot boot on VirtualBox In-Reply-To: <20091116174933.4ab2354d.daichi@ongs.co.jp> References: <20091116174933.4ab2354d.daichi@ongs.co.jp> Message-ID: > FreeBSD 8.0-RC3/amd64 cannot boot on VirtualBox. > Boot will stop and consume 100% cpu power during boot sequence > as displaying as follow: > > Trying to mount rott from ufs:/dev/md0 > warning: no time-of-day clock registered, system time will not be set accurately > > checked environment: > > FreeBSD 9.0-CURRENT #44: Mon Nov 16 09:51:20 JST 2009 amd64 > Core2 Quad Q9550 > virtualbox-3.0.51.r22902_2 > cpu: Core2 Quad Q9550 1-core > mem: 1024MB > VT-x: enable > nested paging: disable > > Is there anyone can boot 8.0-RC3/amd64 on VirtualBox? it's running ok, but with slight diffs: Virtualbox-3.0.51r23006 (only mod is that I changed the boot.rom, to get pxe boot to work). and the host is 8.0-PRERELEASE From bugmaster at FreeBSD.org Mon Nov 16 11:06:51 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 16 11:07:49 2009 Subject: Current problem reports assigned to freebsd-emulation@FreeBSD.org Message-ID: <200911161106.nAGB6oaf011130@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/140156 emulation [linux] cdparanoia fails to read drive data o kern/139423 emulation [parallels] Networking does not work on amd64 guest on o kern/138944 emulation [parallels] [regression] Parallels no longer works in o kern/138880 emulation [linux] munmap segfaults after linux_mmap2 stresstest o kern/138860 emulation [linux] linux_socketcall() causing buffer overflow f ports/137332 emulation add caution messages to some adobe products s ports/136321 emulation x11-toolkits/linux-pango: please update linux based po o ports/136229 emulation [linux] certain linux apps look for libraries using a o ports/135337 emulation [PATCH] emulators/linux_base-f10: incorrect bash usage o kern/133144 emulation [linux] linuxulator 2.6 crashes with nvidias libGL.so. o kern/130724 emulation [linprocfs] [patch] cpuinfo in linprocfs is dated, cau o kern/129169 emulation [linux] [patch] Linux Emulation ENOTCONN error using n f ports/127018 emulation Linuxulator incapable of using FreeBSD's LDAP environm o kern/126232 emulation [linux] Linux ioctl TCGETS (0x5401) always fails o kern/73777 emulation [linux] [patch] linux emulation: root dir special hand a kern/72920 emulation [linux]: path "prefixing" is not done on unix domain s o kern/56451 emulation [linprocfs] /compat/linux/proc/cpuinfo gives wrong CPU o kern/41543 emulation [patch] [request] easier wine/w23 support o kern/39201 emulation [linux] [patch] ptrace(2) and rfork(RFLINUXTHPN) confu o kern/29698 emulation [linux] [patch] linux ipcs doesn'work o kern/21463 emulation [linux] Linux compatability mode should not allow setu o kern/11165 emulation [ibcs2] IBCS2 doesn't work correctly with PID_MAX 9999 22 problems total. From daichi at ongs.co.jp Tue Nov 17 01:36:53 2009 From: daichi at ongs.co.jp (Daichi GOTO) Date: Tue Nov 17 01:37:06 2009 Subject: FreeBSD 8.0-RC3/amd64 cannot boot on VirtualBox (solved) In-Reply-To: References: <20091116174933.4ab2354d.daichi@ongs.co.jp> Message-ID: <20091117103651.da7ceeb0.daichi@ongs.co.jp> On Mon, 16 Nov 2009 12:33:51 +0200 Daniel Braniss wrote: > > FreeBSD 8.0-RC3/amd64 cannot boot on VirtualBox. > > Boot will stop and consume 100% cpu power during boot sequence > > as displaying as follow: > > > > Trying to mount rott from ufs:/dev/md0 > > warning: no time-of-day clock registered, system time will not be set accurately > > > > checked environment: > > > > FreeBSD 9.0-CURRENT #44: Mon Nov 16 09:51:20 JST 2009 amd64 > > Core2 Quad Q9550 > > virtualbox-3.0.51.r22902_2 > > cpu: Core2 Quad Q9550 1-core > > mem: 1024MB > > VT-x: enable > > nested paging: disable > > > > Is there anyone can boot 8.0-RC3/amd64 on VirtualBox? > > it's running ok, but with slight diffs: > Virtualbox-3.0.51r23006 > (only mod is that I changed the boot.rom, to get pxe > boot to work). > and the host is 8.0-PRERELEASE Enabled both ACPI and IO ACPI gives FreeBSD 8.0-RC3/amd64 on VirtualBox working fine :) checked metrics: ----------------------------------------------------------- | ACPI | IO ACPI || HPET 64 | HPET 32 | HPET Disabled | -----------------------===================================== | Enabled | Enabled || WORK | WORK | WORK | | Enabled | Disabled || FAIL | FAIL | FAIL | | Disabled | Enabled || FAIL | FAIL | FAIL | | Disabled | Disabled || FAIL | FAIL | FAIL | ----------------------------------------------------------- * ACPI/IO ACPI - VirtualBox settings ** HPET - HOST PC BIOS settings > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Daichi GOTO CEO | ONGS Inc. 81-42-316-7945 | daichi@ongs.co.jp | http://www.ongs.co.jp LinkedIn: http://linkedin.com/in/daichigoto From rwatson at FreeBSD.org Tue Nov 17 11:19:33 2009 From: rwatson at FreeBSD.org (Robert Watson) Date: Tue Nov 17 11:19:45 2009 Subject: JFYI: VirtualBox-3.0.51.r22902_2 bridge networking freeze issue (solved) In-Reply-To: References: Message-ID: On Mon, 16 Nov 2009, Daichi GOTO wrote: > At last, I have found an issue situation of system freeze led by bridge > networking. With Vimage enable built kernel, bridge networking feature will > lead system freeze. This is more likely a VIMAGE bug than a VirtualBox bug, as VIMAGE is not yet well-tested or ready for real-world use. I'm not sure if the bridge code is considered productionable with VIMAGE yet? Robert > > checked environment: > FreeBSD 9.0-CURRENT #44: Mon Nov 16 09:51:20 JST 2009 amd64 > virtualbox-3.0.51.r22902_2 > Core2 Quad Q9550 > > I have replaced to Q9550 instead of Q8300 to get VT feature, but this was not > relevant (But from this change, I got an ability to use 64bit OS. My test environment > has been extended ;-). Second, I have got rid of some compile options > (e.x. CPUTYPE=core2) and ccache caches, but this was not relevant, too. > Third, I have changed my BIOS settings and update thats version, yes living > up to your expectations, this was not relevant, too. > > Finally, I have rolled back my kernel to GENERIC and bridge networking works > correctly. Step by step adding kernel options, at last, I have found that Vimage > feature is a cause of this problem. Thanks > > PS > Vimage developer, do you have any ideas? Or with this issue, VirtualBox side > should treat this problem? > > -- > Daichi GOTO > CEO | ONGS Inc. > 81-42-316-7945 | daichi@ongs.co.jp | http://www.ongs.co.jp > LinkedIn: http://linkedin.com/in/daichigoto > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From miwi at FreeBSD.org Tue Nov 17 11:46:37 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Tue Nov 17 11:46:43 2009 Subject: [ports-i386@FreeBSD.org: linux-nero-3.5.0.1 failed on i386 7] Message-ID: <20091117114635.GM33028@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - ----- Forwarded message from User Ports-i386 ----- Date: Tue, 17 Nov 2009 11:40:20 GMT From: User Ports-i386 To: erwin@FreeBSD.org, miwi@FreeBSD.org, linimon@FreeBSD.org Subject: linux-nero-3.5.0.1 failed on i386 7 X-Spam-Status: No, score=-106.5 required=5.0 tests=AWL,BAYES_00, RCVD_IN_DNSWL_MED,USER_IN_WHITELIST autolearn=ham version=3.2.5 You can also find this build log at http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/a.7.20091113232800/linux-nero-3.5.0.1.log building linux-nero-3.5.0.1 on hobson6.isc.freebsd.org in directory /usr2/pkgbuild/7/20091113232800/chroot/373 DISTDIR=/tmp/distfiles DISTDIR=/tmp/distfiles/RESTRICTED building for: 7.2-STABLE i386 maintained by: emulation@FreeBSD.org port directory: /usr/ports/sysutils/linux-nero Makefile ident: $FreeBSD: ports/sysutils/linux-nero/Makefile,v 1.4 2009/03/19 17:28:48 bsam Exp $ build started at Tue Nov 17 11:40:13 UTC 2009 FETCH_DEPENDS= PATCH_DEPENDS= EXTRACT_DEPENDS=gettext-0.17_1.tbz libiconv-1.13.1.tbz popt-1.14.tbz rpm-3.0.6_14.tbz BUILD_DEPENDS= RUN_DEPENDS=linux-atk-1.9.1_3.tbz linux-cairo-1.0.2_2.tbz linux-expat-1.95.8_2.tbz linux-fontconfig-2.2.3_9.tbz linux-gtk2-2.6.10_3.tbz linux-jpeg-6b.34_2.tbz linux-pango-1.10.2_3.tbz linux-png-1.2.8_4.tbz linux-tiff-3.7.1_2.tbz linux-xorg-libs-6.8.2_7.tbz linux_base-fc-4_15.tbz prefixes: LOCALBASE=usr/local X11BASE=usr/local add_pkg ================================================================ ======================================== => nerolinux-3.5.0.1-x86.rpm doesn't seem to exist in /tmp/distfiles/RESTRICTED/rpm. => Attempting to fetch from ftp://freebsd.isc.org/pub/FreeBSD/ports/distfiles/rpm/. fetch: ftp://freebsd.isc.org/pub/FreeBSD/ports/distfiles/rpm/nerolinux-3.5.0.1-x86.rpm: File unavailable (e.g., file not found, no access) => Attempting to fetch from ftp://pointyhat.freebsd.org/pub/FreeBSD/distfiles/rpm/. fetch: ftp://pointyhat.freebsd.org/pub/FreeBSD/distfiles/rpm/nerolinux-3.5.0.1-x86.rpm: File unavailable (e.g., file not found, no access) => Attempting to fetch from http://ftp6.usw.nero.com/software/NeroLINUX/. fetch: http://ftp6.usw.nero.com/software/NeroLINUX/nerolinux-3.5.0.1-x86.rpm: Internal Server Error => Attempting to fetch from ftp://ftp6.usw.nero.com/software/NeroLINUX/. fetch: ftp://ftp6.usw.nero.com/software/NeroLINUX/nerolinux-3.5.0.1-x86.rpm: File unavailable (e.g., file not found, no access) => Attempting to fetch from ftp://freebsd.isc.org/pub/FreeBSD/ports/distfiles/rpm/. fetch: ftp://freebsd.isc.org/pub/FreeBSD/ports/distfiles/rpm/nerolinux-3.5.0.1-x86.rpm: File unavailable (e.g., file not found, no access) => Attempting to fetch from ftp://pointyhat.freebsd.org/pub/FreeBSD/distfiles/rpm/. fetch: ftp://pointyhat.freebsd.org/pub/FreeBSD/distfiles/rpm/nerolinux-3.5.0.1-x86.rpm: File unavailable (e.g., file not found, no access) => Couldn't fetch it - please try to retrieve this => port manually into /tmp/distfiles/RESTRICTED/rpm and try again. *** Error code 1 Stop in /a/ports/sysutils/linux-nero. ================================================================ build of /usr/ports/sysutils/linux-nero ended at Tue Nov 17 11:40:18 UTC 2009 - ----- End forwarded message ----- - -- +-----------------------+-------------------------------+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAksCjRsACgkQdLJIhLHm/OnAGACfUbsNcOHOol65G6VV3GlzcUuJ zi0AnRIcCOHqa96cdrNwik7O7jd4ktJl =Jha4 -----END PGP SIGNATURE----- From julian at elischer.org Tue Nov 17 18:08:34 2009 From: julian at elischer.org (Julian Elischer) Date: Tue Nov 17 18:08:48 2009 Subject: JFYI: VirtualBox-3.0.51.r22902_2 bridge networking freeze issue (solved) In-Reply-To: References: Message-ID: <4B02E69E.40008@elischer.org> Robert Watson wrote: > > On Mon, 16 Nov 2009, Daichi GOTO wrote: > >> At last, I have found an issue situation of system freeze led by >> bridge networking. With Vimage enable built kernel, bridge networking >> feature will lead system freeze. > > This is more likely a VIMAGE bug than a VirtualBox bug, as VIMAGE is not > yet well-tested or ready for real-world use. I'm not sure if the bridge > code is considered productionable with VIMAGE yet? I believe not. we use the netgraph bridging because it can act as a reverse bridge (multiple top ends, a single physical interface) So we have not really done much with the standard if_bridge code yet. Certainly it is not well tested if it works at all. > > Robert > >> >> checked environment: >> FreeBSD 9.0-CURRENT #44: Mon Nov 16 09:51:20 JST 2009 amd64 >> virtualbox-3.0.51.r22902_2 >> Core2 Quad Q9550 >> >> I have replaced to Q9550 instead of Q8300 to get VT feature, but this >> was not >> relevant (But from this change, I got an ability to use 64bit OS. My >> test environment >> has been extended ;-). Second, I have got rid of some compile options >> (e.x. CPUTYPE=core2) and ccache caches, but this was not relevant, too. >> Third, I have changed my BIOS settings and update thats version, yes >> living >> up to your expectations, this was not relevant, too. >> >> Finally, I have rolled back my kernel to GENERIC and bridge networking >> works >> correctly. Step by step adding kernel options, at last, I have found >> that Vimage >> feature is a cause of this problem. Thanks >> >> PS >> Vimage developer, do you have any ideas? Or with this issue, >> VirtualBox side >> should treat this problem? >> >> -- >> Daichi GOTO >> CEO | ONGS Inc. >> 81-42-316-7945 | daichi@ongs.co.jp | http://www.ongs.co.jp >> LinkedIn: http://linkedin.com/in/daichigoto >> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From des at des.no Wed Nov 18 11:38:25 2009 From: des at des.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=) Date: Wed Nov 18 11:38:31 2009 Subject: FreeBSD 8.0-RC3/amd64 cannot boot on VirtualBox (solved) In-Reply-To: <20091117103651.da7ceeb0.daichi@ongs.co.jp> (Daichi GOTO's message of "Tue, 17 Nov 2009 10:36:51 +0900") References: <20091116174933.4ab2354d.daichi@ongs.co.jp> <20091117103651.da7ceeb0.daichi@ongs.co.jp> Message-ID: <861vjwvzzp.fsf@ds4.des.no> Daichi GOTO writes: > Enabled both ACPI and IO ACPI ITYM "I/O APIC". HTH, HAND! DES -- Dag-Erling Sm?rgrav - des@des.no From julian at elischer.org Wed Nov 18 17:23:06 2009 From: julian at elischer.org (Julian Elischer) Date: Wed Nov 18 17:23:13 2009 Subject: FreeBSD 8.0-RC3/amd64 cannot boot on VirtualBox (solved) In-Reply-To: <861vjwvzzp.fsf@ds4.des.no> References: <20091116174933.4ab2354d.daichi@ongs.co.jp> <20091117103651.da7ceeb0.daichi@ongs.co.jp> <861vjwvzzp.fsf@ds4.des.no> Message-ID: <4B042D79.9010809@elischer.org> Dag-Erling Sm?rgrav wrote: > Daichi GOTO writes: >> Enabled both ACPI and IO ACPI > > ITYM "I/O APIC". HTH, HAND! > > DES OMG !LEET! From fbsd at opal.com Thu Nov 19 21:01:15 2009 From: fbsd at opal.com (J.R. Oldroyd) Date: Thu Nov 19 21:01:29 2009 Subject: Emulation of Linux V4L ioctls Message-ID: <20091119153159.610debc2@shibato.opal.com> I have added support for emulation of the Linux V4L video ioctls in compat/linux/linux_ioctl.[ch]. I am not a committer; the work can be found here: http://opal.com/freebsd/sys/compat/linux/ These diffs are made to the 8.0-rc3 sources. This enables webcam video to work using the linux-skype port and a pwcbsd-based camera. I expect it will also allow any other linux-port to work now, but have only tested with skype. I have noticed, however, that flash-based webcam apps cause the npviewer.bin process to hang, so that is not yet working. Anyone with thoughts on what is going on in the various flash support layers is welcome to comment on this. -jr From rdivacky at freebsd.org Fri Nov 20 08:04:46 2009 From: rdivacky at freebsd.org (Roman Divacky) Date: Fri Nov 20 08:04:52 2009 Subject: Emulation of Linux V4L ioctls In-Reply-To: <20091119153159.610debc2@shibato.opal.com> References: <20091119153159.610debc2@shibato.opal.com> Message-ID: <20091120080317.GA18284@freebsd.org> On Thu, Nov 19, 2009 at 03:31:59PM -0500, J.R. Oldroyd wrote: > I have added support for emulation of the Linux V4L video ioctls > in compat/linux/linux_ioctl.[ch]. > > I am not a committer; the work can be found here: > http://opal.com/freebsd/sys/compat/linux/ > These diffs are made to the 8.0-rc3 sources. > > This enables webcam video to work using the linux-skype port > and a pwcbsd-based camera. I expect it will also allow any other > linux-port to work now, but have only tested with skype. > > I have noticed, however, that flash-based webcam apps cause > the npviewer.bin process to hang, so that is not yet working. > Anyone with thoughts on what is going on in the various flash > support layers is welcome to comment on this. I just glanced over it but it looks good... From Alexander at Leidinger.net Fri Nov 20 09:35:46 2009 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Fri Nov 20 09:35:53 2009 Subject: Emulation of Linux V4L ioctls In-Reply-To: <20091119153159.610debc2@shibato.opal.com> References: <20091119153159.610debc2@shibato.opal.com> Message-ID: <20091120103535.815072bwgvis0io0@webmail.leidinger.net> Quoting "J.R. Oldroyd" (from Thu, 19 Nov 2009 15:31:59 -0500): > I have added support for emulation of the Linux V4L video ioctls > in compat/linux/linux_ioctl.[ch]. Wow, great! > I am not a committer; the work can be found here: > http://opal.com/freebsd/sys/compat/linux/ > These diffs are made to the 8.0-rc3 sources. Some things I noticed and worry about: - videodev.h does not have a license, did you generate it yourself or did you take it from somewhere? - Does it needs to be named videodev.h, or can it also be linux_videodev.h? (if we may want to install this header at some point in time, it should have a name compatible with linux, else we should maybe add a linux_ prefix for consistence and for making it very obvious what we are talking about) - Why are you using __s32 and so on instead of the normal fixed size int types? We also have lint for "linux int" and so on in other files. - On which architecture has this been tested? - Will it run in linux32 emulation on amd64? - Are those structures known in userland (and as such need to have a specific size)? If yes, do they have different sizes in linux depending if the kernel is a 64bit kernel (amd64) or 32bit kernel (x86)? - Has this been run through a "make universe"? Bye, Alexander. -- WARNING TO ALL PERSONNEL: Firings will continue until morale improves. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From fbsd at opal.com Fri Nov 20 15:36:29 2009 From: fbsd at opal.com (J.R. Oldroyd) Date: Fri Nov 20 15:36:36 2009 Subject: Emulation of Linux V4L ioctls In-Reply-To: <20091120103535.815072bwgvis0io0@webmail.leidinger.net> References: <20091119153159.610debc2@shibato.opal.com> <20091120103535.815072bwgvis0io0@webmail.leidinger.net> Message-ID: <20091120103622.0db845c8@shibato.opal.com> On Fri, 20 Nov 2009 10:35:35 +0100, Alexander Leidinger wrote: > > Some things I noticed and worry about: > - videodev.h does not have a license, did you generate it > yourself or did you take it from somewhere? > - Does it needs to be named videodev.h, or can it also be > linux_videodev.h? > (if we may want to install this header at some point in time, > it should have a name compatible with linux, else we should > maybe add a linux_ prefix for consistence and for making it > very obvious what we are talking about) > - Why are you using __s32 and so on instead of the normal > fixed size int types? We also have lint for "linux int" > and so on in other files. This header is the same as the one used on Linux. In fact, I took this file from our pwcbsd driver, but it can also be found by googling for videodev.h which reveals it is /usr/include/linux/videodev.h on Linux 2.6 systems. I think it really wants to be installed in /usr/include/linux here too, since it is also useful for user apps that need these structures and definitions. But I am not sure what our policy would be for creating a /usr/include/linux dir for it. If you prefer to keep it in this dir, yes it could be renamed to linux_videodev.h. There is indeed no license in this file. The use of __s32 etc is because I used this file unchanged. > - On which architecture has this been tested? > - Will it run in linux32 emulation on amd64? Yes. I did this work on an amd64, in fact. > - Are those structures known in userland (and as such need to > have a specific size)? If yes, do they have different sizes > in linux depending if the kernel is a 64bit kernel (amd64) > or 32bit kernel (x86)? They are used in userland. Given the header's use of __s32 etc, it looks to me like the structures have the same size on both x86 and amd64. > - Has this been run through a "make universe"? > I built by compiling in sys/amd64/compile/XXX. -jr From ohreally.nl at gmail.com Fri Nov 20 15:58:08 2009 From: ohreally.nl at gmail.com (Rob la Lau) Date: Fri Nov 20 15:58:15 2009 Subject: linux-pango Message-ID: Hello, This address is listed as the maintainer address for the /usr/ports/x11-toolkits/linux-pango FreeBSD port, hence my mail. The mentioned port is listed as having vulnerabilities ( http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html), appearantly since 2009-05-08, which means www/nspluginwrapper refuses to install (I don't like setting 'DISABLE_VULNERABILITIES=yes'). Are there any plans for an update? Thanks, Rob la Lau From julian at elischer.org Fri Nov 20 18:10:52 2009 From: julian at elischer.org (Julian Elischer) Date: Fri Nov 20 18:11:00 2009 Subject: freebsd-emulation Digest, Vol 342, Issue 5 In-Reply-To: <20091120120017.C95E71065717@hub.freebsd.org> References: <20091120120017.C95E71065717@hub.freebsd.org> Message-ID: <4B06DBAA.2010101@elischer.org> freebsd-emulation-request@freebsd.org wrote: > Send freebsd-emulation mailing list submissions to > freebsd-emulation@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-emulation > or, via email, send a message with subject or body 'help' to > freebsd-emulation-request@freebsd.org > > You can reach the person managing the list at > freebsd-emulation-owner@freebsd.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-emulation digest..." > > > Today's Topics: > > 1. Emulation of Linux V4L ioctls (J.R. Oldroyd) > 2. Re: Emulation of Linux V4L ioctls (Roman Divacky) > 3. Re: Emulation of Linux V4L ioctls (Alexander Leidinger) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 19 Nov 2009 15:31:59 -0500 > From: "J.R. Oldroyd" > Subject: Emulation of Linux V4L ioctls > To: freebsd-emulation@freebsd.org > Message-ID: <20091119153159.610debc2@shibato.opal.com> > Content-Type: text/plain; charset=US-ASCII > > I have added support for emulation of the Linux V4L video ioctls > in compat/linux/linux_ioctl.[ch]. > > I am not a committer; the work can be found here: > http://opal.com/freebsd/sys/compat/linux/ > These diffs are made to the 8.0-rc3 sources. > > This enables webcam video to work using the linux-skype port > and a pwcbsd-based camera. I expect it will also allow any other > linux-port to work now, but have only tested with skype. > > I have noticed, however, that flash-based webcam apps cause > the npviewer.bin process to hang, so that is not yet working. > Anyone with thoughts on what is going on in the various flash > support layers is welcome to comment on this. > > -jr > > > ------------------------------ > > Message: 2 > Date: Fri, 20 Nov 2009 09:03:17 +0100 > From: Roman Divacky > Subject: Re: Emulation of Linux V4L ioctls > To: "J.R. Oldroyd" > Cc: freebsd-emulation@freebsd.org > Message-ID: <20091120080317.GA18284@freebsd.org> > Content-Type: text/plain; charset=us-ascii > > On Thu, Nov 19, 2009 at 03:31:59PM -0500, J.R. Oldroyd wrote: >> I have added support for emulation of the Linux V4L video ioctls >> in compat/linux/linux_ioctl.[ch]. >> >> I am not a committer; the work can be found here: >> http://opal.com/freebsd/sys/compat/linux/ >> These diffs are made to the 8.0-rc3 sources. >> >> This enables webcam video to work using the linux-skype port >> and a pwcbsd-based camera. I expect it will also allow any other >> linux-port to work now, but have only tested with skype. >> >> I have noticed, however, that flash-based webcam apps cause >> the npviewer.bin process to hang, so that is not yet working. >> Anyone with thoughts on what is going on in the various flash >> support layers is welcome to comment on this. > > I just glanced over it but it looks good... > > > ------------------------------ > > Message: 3 > Date: Fri, 20 Nov 2009 10:35:35 +0100 > From: Alexander Leidinger > Subject: Re: Emulation of Linux V4L ioctls > To: "J.R. Oldroyd" > Cc: freebsd-emulation@freebsd.org > Message-ID: <20091120103535.815072bwgvis0io0@webmail.leidinger.net> > Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" > > Quoting "J.R. Oldroyd" (from Thu, 19 Nov 2009 15:31:59 -0500): > >> I have added support for emulation of the Linux V4L video ioctls >> in compat/linux/linux_ioctl.[ch]. > > Wow, great! > >> I am not a committer; the work can be found here: >> http://opal.com/freebsd/sys/compat/linux/ >> These diffs are made to the 8.0-rc3 sources. > > Some things I noticed and worry about: > - videodev.h does not have a license, did you generate it > yourself or did you take it from somewhere? I have emails from the original V4L(2) developers statingthat the v4l include files represent an API and as such they did not copyright them and we are welcome to use them directly. > - Does it needs to be named videodev.h, or can it also be > linux_videodev.h? > (if we may want to install this header at some point in time, > it should have a name compatible with linux, else we should > maybe add a linux_ prefix for consistence and for making it > very obvious what we are talking about) > - Why are you using __s32 and so on instead of the normal > fixed size int types? We also have lint for "linux int" > and so on in other files. > - On which architecture has this been tested? > - Will it run in linux32 emulation on amd64? > - Are those structures known in userland (and as such need to > have a specific size)? If yes, do they have different sizes > in linux depending if the kernel is a 64bit kernel (amd64) > or 32bit kernel (x86)? > - Has this been run through a "make universe"? > > Bye, > Alexander. > From julian at elischer.org Fri Nov 20 18:11:59 2009 From: julian at elischer.org (Julian Elischer) Date: Fri Nov 20 18:12:05 2009 Subject: freebsd-emulation Digest, Vol 342, Issue 5 In-Reply-To: <20091120120017.C95E71065717@hub.freebsd.org> References: <20091120120017.C95E71065717@hub.freebsd.org> Message-ID: <4B06DBED.8080801@elischer.org> oops sorry for responding to an entire digest.. From fbsd at opal.com Fri Nov 20 21:34:29 2009 From: fbsd at opal.com (J.R. Oldroyd) Date: Fri Nov 20 21:34:36 2009 Subject: Emulation of Linux V4L ioctls In-Reply-To: <20091120103622.0db845c8@shibato.opal.com> References: <20091119153159.610debc2@shibato.opal.com> <20091120103535.815072bwgvis0io0@webmail.leidinger.net> <20091120103622.0db845c8@shibato.opal.com> Message-ID: <20091120163426.340ca0d8@shibato.opal.com> On Fri, 20 Nov 2009 10:36:22 -0500, "J.R. Oldroyd" wrote: > > videodev.h > Further discovery reveals that the same file is also installed in $PREFIX/include/linux/videodev.h by the multimedia/v4l_compat port, which I think is the right place for it here for apps that want to use it. So, keep this one within the source dir, renamed to linux_videodev.h if you like. -jr From nox at jelal.kn-bremen.de Sat Nov 21 00:00:59 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sat Nov 21 00:01:05 2009 Subject: FreeBSD qemu-devel git snapshot port update up for testing Message-ID: <20091120234951.GA17631@triton8.kn-bremen.de> Hi! I've made another qemu git snapshot port update, http://people.freebsd.org/~nox/qemu/qemu-devel-20091120.patch or, alternatively, http://people.freebsd.org/~nox/qemu/qemu-devel-20091120.shar and since our emulators/qemu-devel port still is older than the main port (and thus has been on IGNORE) am thinking about actually committing this version of the port if no major flaws are found. Soo, testing very much welcome! :) I'm not aware of something like a `condensed' changelog for qemu git (is there one? The Changelog file in git still stops at 0.10.2), but one of the major changes was the removal of kqemu support after the 0.11 branch was created (which I still plan to update the main emulators/qemu port to, probably after 0.11.1 has been released, so kqemu will still be available there for a little while longer.) Anyway, more emulated hw support has been added, internals have been overhauled, and probably a bunch of other interesting things happened that I forgot. Oh and the bsd-user targets (currently i386, amd64, and sparc64) are now good enough to run at least FreeBSD /rescue/bin/echo on FreeBSD, and even more (like /bin/sh or vim at least on x86) if you emulate the same arch you are running on. Whats now missing most I think is proper parameter passing of more syscalls, if someone is interested to help there I think at least some amount of code can be adapted from linux-user there... (And this time I have submitted at least some of the fixes I applied seperately on the qemu list.) Enjoy, Juergen From nox at jelal.kn-bremen.de Sat Nov 21 19:08:03 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sat Nov 21 19:08:10 2009 Subject: FreeBSD qemu-devel git snapshot port update up for testing In-Reply-To: <20091120234951.GA17631@triton8.kn-bremen.de> References: <20091120234951.GA17631@triton8.kn-bremen.de> Message-ID: <20091121190205.GA52224@triton8.kn-bremen.de> On Sat, Nov 21, 2009 at 12:49:51AM +0100, Juergen Lock wrote: > Hi! > > I've made another qemu git snapshot port update, > http://people.freebsd.org/~nox/qemu/qemu-devel-20091120.patch > or, alternatively, > http://people.freebsd.org/~nox/qemu/qemu-devel-20091120.shar > and since our emulators/qemu-devel port still is older than the main port > (and thus has been on IGNORE) am thinking about actually committing this > version of the port if no major flaws are found. Soo, testing very much > welcome! :) > > I'm not aware of something like a `condensed' changelog for qemu git > (is there one? The Changelog file in git still stops at 0.10.2), but one > of the major changes was the removal of kqemu support after the 0.11 > branch was created (which I still plan to update the main emulators/qemu > port to, probably after 0.11.1 has been released, so kqemu will still be > available there for a little while longer.) Anyway, more emulated hw > support has been added, internals have been overhauled, and probably > a bunch of other interesting things happened that I forgot. Oh and > the bsd-user targets (currently i386, amd64, and sparc64) are now good > enough to run at least FreeBSD /rescue/bin/echo on FreeBSD, and even > more (like /bin/sh or vim at least on x86) if you emulate the same arch > you are running on. Whats now missing most I think is proper parameter > passing of more syscalls, if someone is interested to help there I think > at least some amount of code can be adapted from linux-user there... > > (And this time I have submitted at least some of the fixes I applied > seperately on the qemu list.) > New version up with corrected plist. (Sorry.) Enjoy, Juergen From dougb at FreeBSD.org Sun Nov 22 06:41:11 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Sun Nov 22 06:41:17 2009 Subject: Bridged networking for virtualbox on -current? Message-ID: <4B08DD0C.3080106@FreeBSD.org> Is bridged networking for vbox supposed to work on -current? It says on the wiki that it does, but I tried it tonight and couldn't get it to work. I did see one page that suggested trying one of the Intel virtual nicks, which I did, no luck. If this is not supposed to work it would be nice to update the wiki, I spent quite a bit of time trying to get it to work that I hope was not wasted. Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From fli at shapeshifter.se Sun Nov 22 16:16:05 2009 From: fli at shapeshifter.se (Fredrik Lindberg) Date: Sun Nov 22 16:16:12 2009 Subject: Bridged networking for virtualbox on -current? In-Reply-To: <4B08DD0C.3080106@FreeBSD.org> References: <4B08DD0C.3080106@FreeBSD.org> Message-ID: <4B0963BF.1070908@shapeshifter.se> Doug Barton wrote: > Is bridged networking for vbox supposed to work on -current? It says > on the wiki that it does, but I tried it tonight and couldn't get it > to work. > > I did see one page that suggested trying one of the Intel virtual > nicks, which I did, no luck. > > If this is not supposed to work it would be nice to update the wiki, I > spent quite a bit of time trying to get it to work that I hope was not > wasted. > The short answer is that it should work. The long answer is that it depends, for example it doesn't play nice when trying to bridge a virtual nic with an if_bridge interface. A slightly more verbose description of your environment and what error messages you're seeing would probably help. Fredrik From tamaru at myn.rcast.u-tokyo.ac.jp Sun Nov 22 17:12:34 2009 From: tamaru at myn.rcast.u-tokyo.ac.jp (Hiroharu Tamaru) Date: Sun Nov 22 17:12:52 2009 Subject: Bridged networking for virtualbox on -current? In-Reply-To: <4B08DD0C.3080106@FreeBSD.org> References: <4B08DD0C.3080106@FreeBSD.org> Message-ID: Hi, At Sat, 21 Nov 2009 22:41:16 -0800, Doug Barton wrote: > Is bridged networking for vbox supposed to work on -current? It says > on the wiki that it does, but I tried it tonight and couldn't get it > to work. > > I did see one page that suggested trying one of the Intel virtual > nicks, which I did, no luck. It is working here on 8.0. Did you specifically mean -current? I do remember that it didn't work on my first trial; don't know what I did differently then, though. Working setup: host: 8.0-PRERELEASE/amd64 where VM is configured with Network Adapter 1: Intel PRO/1000 MT Desktop (Bridged adapter, nfe0) with guest OS: 8.0-RC3/i386 and within the guest: guest%ifconfig em0 em0: flags=8843 metric 0 mtu 1500 options=9b ether 08:00:27:xx:yy:zz inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 media: Ethernet autoselect (1000baseT ) status: active I can see the dhcp packets on the wire by monitoring the nfe0 on the host side: host# tcpdump -i nfe0 ether host 08:00:27:xx:yy:zz listening on nfe0, link-type EN10MB (Ethernet), capture size 96 bytes IP 192.168.1.2.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 08:00:27:xx:yy:zz (oui Unknown), length 300 IP 192.168.1.2.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 08:00:27:xx:yy:zz (oui Unknown), length 300 IP ntt.setup.bootps > 192.168.1.2.bootpc: BOOTP/DHCP, Reply, length 548 ARP, Request who-has 192.168.1.2 tell 192.168.1.2, length 28 ARP, Request who-has 192.168.1.2 tell 192.168.1.2, length 28 hope it helps. > If this is not supposed to work it would be nice to update the wiki, I > spent quite a bit of time trying to get it to work that I hope was not > wasted. > > > Doug > > -- > > Improve the effectiveness of your Internet presence with > a domain name makeover! http://SupersetSolutions.com/ -- Hiroharu Tamaru From dougb at FreeBSD.org Sun Nov 22 17:19:43 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Sun Nov 22 17:19:49 2009 Subject: Bridged networking for virtualbox on -current? In-Reply-To: <4B0963BF.1070908@shapeshifter.se> References: <4B08DD0C.3080106@FreeBSD.org> <4B0963BF.1070908@shapeshifter.se> Message-ID: <4B0972B5.40903@FreeBSD.org> Fredrik Lindberg wrote: > Doug Barton wrote: >> Is bridged networking for vbox supposed to work on -current? It says >> on the wiki that it does, but I tried it tonight and couldn't get it >> to work. >> >> I did see one page that suggested trying one of the Intel virtual >> nicks, which I did, no luck. >> >> If this is not supposed to work it would be nice to update the wiki, I >> spent quite a bit of time trying to get it to work that I hope was not >> wasted. >> > > The short answer is that it should work. The long answer is that > it depends, for example it doesn't play nice when trying to > bridge a virtual nic with an if_bridge interface. > > A slightly more verbose description of your environment and what > error messages you're seeing would probably help. Thanks. I'm using an up to date -current, and my outgoing nic is wlan0. I followed the instructions on the wiki. I first tried the default nic in OSE then I tried the first Intel nic on the list (which required downloading drivers of course). Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From fli at shapeshifter.se Sun Nov 22 20:04:02 2009 From: fli at shapeshifter.se (Fredrik Lindberg) Date: Sun Nov 22 20:04:08 2009 Subject: Bridged networking for virtualbox on -current? In-Reply-To: <4B0972B5.40903@FreeBSD.org> References: <4B08DD0C.3080106@FreeBSD.org> <4B0963BF.1070908@shapeshifter.se> <4B0972B5.40903@FreeBSD.org> Message-ID: <4B09992F.1080900@shapeshifter.se> Doug Barton wrote: > Fredrik Lindberg wrote: >> Doug Barton wrote: >>> Is bridged networking for vbox supposed to work on -current? It says >>> on the wiki that it does, but I tried it tonight and couldn't get it >>> to work. >>> >>> I did see one page that suggested trying one of the Intel virtual >>> nicks, which I did, no luck. >>> >>> If this is not supposed to work it would be nice to update the wiki, I >>> spent quite a bit of time trying to get it to work that I hope was not >>> wasted. >>> >> The short answer is that it should work. The long answer is that >> it depends, for example it doesn't play nice when trying to >> bridge a virtual nic with an if_bridge interface. >> >> A slightly more verbose description of your environment and what >> error messages you're seeing would probably help. > > Thanks. I'm using an up to date -current, and my outgoing nic is > wlan0. I followed the instructions on the wiki. I first tried the > default nic in OSE then I tried the first Intel nic on the list (which > required downloading drivers of course). > Which type of virtual interface you're using in virtualbox doesn't matter. However, it hits me that I've actually never really tested the bridging code with a wireless interface and it looks like you've hit a bug. I tried to use a wireless interface just now and it doesn't work, need to look into why though. Fredrik From dougb at FreeBSD.org Sun Nov 22 20:54:44 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Sun Nov 22 20:54:51 2009 Subject: Bridged networking for virtualbox on -current? In-Reply-To: <4B09992F.1080900@shapeshifter.se> References: <4B08DD0C.3080106@FreeBSD.org> <4B0963BF.1070908@shapeshifter.se> <4B0972B5.40903@FreeBSD.org> <4B09992F.1080900@shapeshifter.se> Message-ID: <4B09A519.4010603@FreeBSD.org> Fredrik Lindberg wrote: > Which type of virtual interface you're using in virtualbox doesn't > matter. However, it hits me that I've actually never really tested > the bridging code with a wireless interface and it looks like you've > hit a bug. I tried to use a wireless interface just now and it > doesn't work, need to look into why though. Ok, thanks! Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From nox at jelal.kn-bremen.de Sun Nov 22 23:19:12 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sun Nov 22 23:19:17 2009 Subject: bridging vs wifi, proxy arp broken on 8.0 rc? (was: Re: Bridged networking for virtualbox on -current?) In-Reply-To: <4B09992F.1080900@shapeshifter.se> References: <4B08DD0C.3080106@FreeBSD.org> <4B0963BF.1070908@shapeshifter.se> <4B0972B5.40903@FreeBSD.org> Message-ID: <200911222316.nAMNGwfV068520@triton8.kn-bremen.de> In article <4B09992F.1080900@shapeshifter.se> you write: >Doug Barton wrote: >> Fredrik Lindberg wrote: >>> Doug Barton wrote: >>>> Is bridged networking for vbox supposed to work on -current? It says >>>> on the wiki that it does, but I tried it tonight and couldn't get it >>>> to work. >>>> >>>> I did see one page that suggested trying one of the Intel virtual >>>> nicks, which I did, no luck. >>>> >>>> If this is not supposed to work it would be nice to update the wiki, I >>>> spent quite a bit of time trying to get it to work that I hope was not >>>> wasted. >>>> >>> The short answer is that it should work. The long answer is that >>> it depends, for example it doesn't play nice when trying to >>> bridge a virtual nic with an if_bridge interface. >>> >>> A slightly more verbose description of your environment and what >>> error messages you're seeing would probably help. >> >> Thanks. I'm using an up to date -current, and my outgoing nic is >> wlan0. I followed the instructions on the wiki. I first tried the >> default nic in OSE then I tried the first Intel nic on the list (which >> required downloading drivers of course). >> > >Which type of virtual interface you're using in virtualbox doesn't >matter. However, it hits me that I've actually never really tested >the bridging code with a wireless interface and it looks like you've >hit a bug. I tried to use a wireless interface just now and it >doesn't work, need to look into why though. The problem with bridging and wifi is that on wifi you usually can use only a single mac address... There are ways around this (using nat or routing), and I actually played with the latter using qemu tap networking recently, but couldn't get the most ideal solution working the way I wanted on 8.0 rc - it only worked on 7-stable. (using a sub-subnet of the lan interface for the tap interface + guest, and routing + proxy arp for the guest ip.) I just wanted to try it again on the 8.0 rc box and now even setting up the prox arp entry fails with: arp: writing to routing socket: Invalid argument Commands I tried: arp -s pub only and arp -s auto pub only (both before even configuring the tap interface this time...) Mind you my 8.0 rc checkout is a little old (Sep 29) so maybe I should try updating first (I want to test 8-stable anyway one of these days) - but looking for `arp' in the relevant commitlogs also came up empty. :( (I'm Cc'ing -net just in case, please keep me on the Cc cause I'm not subscribed there...) Cheers, Juergen From dougb at FreeBSD.org Mon Nov 23 00:41:05 2009 From: dougb at FreeBSD.org (Doug Barton) Date: Mon Nov 23 00:41:11 2009 Subject: bridging vs wifi, proxy arp broken on 8.0 rc? In-Reply-To: <200911222316.nAMNGwfV068520@triton8.kn-bremen.de> References: <4B08DD0C.3080106@FreeBSD.org> <4B0963BF.1070908@shapeshifter.se> <4B0972B5.40903@FreeBSD.org> <200911222316.nAMNGwfV068520@triton8.kn-bremen.de> Message-ID: <4B09DA1A.2050109@FreeBSD.org> Juergen Lock wrote: > The problem with bridging and wifi is that on wifi you usually can > use only a single mac address... Ok, I'm not heartbroken if it won't work, but it would be nice if the wiki were updated so that no one else wastes time on it like I did last night. Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From bugmaster at FreeBSD.org Mon Nov 23 11:06:52 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Nov 23 11:07:48 2009 Subject: Current problem reports assigned to freebsd-emulation@FreeBSD.org Message-ID: <200911231106.nANB6pAu070091@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/140156 emulation [linux] cdparanoia fails to read drive data o kern/139423 emulation [parallels] Networking does not work on amd64 guest on o kern/138944 emulation [parallels] [regression] Parallels no longer works in o kern/138880 emulation [linux] munmap segfaults after linux_mmap2 stresstest o kern/138860 emulation [linux] linux_socketcall() causing buffer overflow f ports/137332 emulation add caution messages to some adobe products s ports/136321 emulation x11-toolkits/linux-pango: please update linux based po o ports/136229 emulation [linux] certain linux apps look for libraries using a o ports/135337 emulation [PATCH] emulators/linux_base-f10: incorrect bash usage o kern/133144 emulation [linux] linuxulator 2.6 crashes with nvidias libGL.so. o kern/130724 emulation [linprocfs] [patch] cpuinfo in linprocfs is dated, cau o kern/129169 emulation [linux] [patch] Linux Emulation ENOTCONN error using n f ports/127018 emulation Linuxulator incapable of using FreeBSD's LDAP environm o kern/126232 emulation [linux] Linux ioctl TCGETS (0x5401) always fails o kern/73777 emulation [linux] [patch] linux emulation: root dir special hand a kern/72920 emulation [linux]: path "prefixing" is not done on unix domain s o kern/56451 emulation [linprocfs] /compat/linux/proc/cpuinfo gives wrong CPU o kern/41543 emulation [patch] [request] easier wine/w23 support o kern/39201 emulation [linux] [patch] ptrace(2) and rfork(RFLINUXTHPN) confu o kern/29698 emulation [linux] [patch] linux ipcs doesn'work o kern/21463 emulation [linux] Linux compatability mode should not allow setu o kern/11165 emulation [ibcs2] IBCS2 doesn't work correctly with PID_MAX 9999 22 problems total. From Alexander at Leidinger.net Mon Nov 23 13:43:02 2009 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Mon Nov 23 13:43:08 2009 Subject: Emulation of Linux V4L ioctls In-Reply-To: <20091120103622.0db845c8@shibato.opal.com> References: <20091119153159.610debc2@shibato.opal.com> <20091120103535.815072bwgvis0io0@webmail.leidinger.net> <20091120103622.0db845c8@shibato.opal.com> Message-ID: <20091123144251.11055vw9sv236voc@webmail.leidinger.net> Quoting "J.R. Oldroyd" (from Fri, 20 Nov 2009 10:36:22 -0500): > On Fri, 20 Nov 2009 10:35:35 +0100, Alexander Leidinger > wrote: >> >> Some things I noticed and worry about: >> - videodev.h does not have a license, did you generate it >> yourself or did you take it from somewhere? >> - Does it needs to be named videodev.h, or can it also be >> linux_videodev.h? >> (if we may want to install this header at some point in time, >> it should have a name compatible with linux, else we should >> maybe add a linux_ prefix for consistence and for making it >> very obvious what we are talking about) >> - Why are you using __s32 and so on instead of the normal >> fixed size int types? We also have lint for "linux int" >> and so on in other files. > > This header is the same as the one used on Linux. In fact, I > took this file from our pwcbsd driver, but it can also be found > by googling for videodev.h which reveals it is > /usr/include/linux/videodev.h > on Linux 2.6 systems. > There is indeed no license in this file. And this fact makes it a little bit hard to import into FreeBSD, at least for a person like me with not so much knowledge about copyright/license stuff. Someone out there (@FreeBSD.org) who is willing to put some official weight into this issue? > The use of __s32 etc is because I used this file unchanged. > - On which architecture has this been tested? > - Will it run in linux32 emulation on amd64? > Yes. I did this work on an amd64, in fact. > - Are those structures known in userland (and as such need to > have a specific size)? If yes, do they have different sizes > in linux depending if the kernel is a 64bit kernel (amd64) > or 32bit kernel (x86)? > They are used in userland. Given the header's use of __s32 > etc, it looks to me like the structures have the same size > on both x86 and amd64. I've seen the use of non-fixed size variables (e.g. int). It would be better to verify that they are the same size. Can you please write a little program which includes the header and prints out the size of all structures. This way we can run it on amd64 and i386 and compare. Bye, Alexander. -- Those of you who think you know everything are very annoying to those of us who do. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From fbsd at opal.com Mon Nov 23 17:54:09 2009 From: fbsd at opal.com (J.R. Oldroyd) Date: Mon Nov 23 17:54:16 2009 Subject: Emulation of Linux V4L ioctls In-Reply-To: <20091123144251.11055vw9sv236voc@webmail.leidinger.net> References: <20091119153159.610debc2@shibato.opal.com> <20091120103535.815072bwgvis0io0@webmail.leidinger.net> <20091120103622.0db845c8@shibato.opal.com> <20091123144251.11055vw9sv236voc@webmail.leidinger.net> Message-ID: <20091123125403.20e3a63e@shibato.opal.com> On Mon, 23 Nov 2009 14:42:51 +0100, Alexander Leidinger wrote: > > Quoting "J.R. Oldroyd" (from Fri, 20 Nov 2009 10:36:22 -0500): > > [videodev.h] > > > There is indeed no license in this file. > > And this fact makes it a little bit hard to import into FreeBSD, at > least for a person like me with not so much knowledge about > copyright/license stuff. Someone out there (@FreeBSD.org) who is > willing to put some official weight into this issue? > I would also like to hear from someone more into license issues about this. It would be best to keep the identical file, if possible, to avoid possible divergence problems. However, if needed, I could generate a new file, e.g., linux_videodev_compat.h, that contains just the required #defines but using structure templates that are size compatible. I could determine the sizes using a program such as you describe below. But first... any license folk care to comment on this? > [structure compatibility between i386 and amd64] > > I've seen the use of non-fixed size variables (e.g. int). It would be > better to verify that they are the same size. Can you please write a > little program which includes the header and prints out the size of > all structures. This way we can run it on amd64 and i386 and compare. > Such a program may be useful for the above reason, but I believe it is already established that the structures are compatible between the two platforms. My test app is the net/skype port which installs: /usr/local/share/skype/skype: ELF 32-bit LSB executable, Intel 80386, version 1 (GNU/Linux), dynamically linked (uses shared libs), for GNU/Linux 2.4.1, stripped I am running this on an amd64 with the code using the same videodev.h. The video is working. Ergo, the structures appear to be compatible. -jr -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20091123/9db46c9f/signature.pgp From nox at jelal.kn-bremen.de Mon Nov 23 18:32:36 2009 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Mon Nov 23 18:32:48 2009 Subject: bridging vs wifi, proxy arp broken on 8.0 rc? (was: Re: Bridged networking for virtualbox on -current?) In-Reply-To: <200911222316.nAMNGwfV068520@triton8.kn-bremen.de> References: <4B08DD0C.3080106@FreeBSD.org> <4B0963BF.1070908@shapeshifter.se> <4B0972B5.40903@FreeBSD.org> <200911222316.nAMNGwfV068520@triton8.kn-bremen.de> Message-ID: <20091123182809.GA35896@triton8.kn-bremen.de> On Mon, Nov 23, 2009 at 12:16:58AM +0100, Juergen Lock wrote: > In article <4B09992F.1080900@shapeshifter.se> you write: > >Doug Barton wrote: > >> Fredrik Lindberg wrote: > >>> Doug Barton wrote: > >>>> Is bridged networking for vbox supposed to work on -current? It says > >>>> on the wiki that it does, but I tried it tonight and couldn't get it > >>>> to work. > >>>> > >>>> I did see one page that suggested trying one of the Intel virtual > >>>> nicks, which I did, no luck. > >>>> > >>>> If this is not supposed to work it would be nice to update the wiki, I > >>>> spent quite a bit of time trying to get it to work that I hope was not > >>>> wasted. > >>>> > >>> The short answer is that it should work. The long answer is that > >>> it depends, for example it doesn't play nice when trying to > >>> bridge a virtual nic with an if_bridge interface. > >>> > >>> A slightly more verbose description of your environment and what > >>> error messages you're seeing would probably help. > >> > >> Thanks. I'm using an up to date -current, and my outgoing nic is > >> wlan0. I followed the instructions on the wiki. I first tried the > >> default nic in OSE then I tried the first Intel nic on the list (which > >> required downloading drivers of course). > >> > > > >Which type of virtual interface you're using in virtualbox doesn't > >matter. However, it hits me that I've actually never really tested > >the bridging code with a wireless interface and it looks like you've > >hit a bug. I tried to use a wireless interface just now and it > >doesn't work, need to look into why though. > > The problem with bridging and wifi is that on wifi you usually can > use only a single mac address... There are ways around this (using > nat or routing), and I actually played with the latter using qemu tap > networking recently, but couldn't get the most ideal solution working > the way I wanted on 8.0 rc - it only worked on 7-stable. (using a > sub-subnet of the lan interface for the tap interface + guest, and > routing + proxy arp for the guest ip.) I just wanted to try it again > on the 8.0 rc box and now even setting up the prox arp entry fails > with: > arp: writing to routing socket: Invalid argument > Commands I tried: > arp -s pub only > and > arp -s auto pub only > (both before even configuring the tap interface this time...) > > Mind you my 8.0 rc checkout is a little old (Sep 29) so maybe I should > try updating first (I want to test 8-stable anyway one of these days) - > but looking for `arp' in the relevant commitlogs also came up empty. :( > > (I'm Cc'ing -net just in case, please keep me on the Cc cause I'm > not subscribed there...) I meanwhile found a few arp related commits (it helps if you don't forget to ignore case when searching for `arp'... doh! :) - but I now also grabbed stable/8 and head snapshot isos and tested that arp command there, and found its still broken. :( (The same command without the `only' succeeds but can never work for _this_ use case, right?) How I tested (head snapshot livefs in qemu:) % qemu -m 256 -cdrom 9.0-HEAD-20091123-JPSNAP-i386-dvd1.iso -net nic,model=e1000 -net user -curses [In sysinstall select fixit -> cdrom/dvd, then:] Fixit# mkdir /var/db Fixit# dhclient em0 DHCPDISCOVER on em0 to 255.255.255.255 port 67 interval 8 DHCPOFFER from 10.0.2.2 DHCPREQUEST on em0 to 255.255.255.255 port 67 DHCPACK from 10.0.2.2 bound to 10.0.2.15 -- renewal in 43200 seconds. Fixit# arp -s 10.0.2.65 auto pub only using interface em0 for proxy with address 52:54:00:12:34:56 arp: writing to routing socket: Invalid argument Fixit# ifconfig em0 em0: flags=8843 metric 0 mtu 1500 options=9b ether 52:54:00:12:34:56 inet6 fe80::5054:ff:fe12:3456%em0 prefixlen 64 scopeid 0x1 inet 10.0.2.15 netmask 0xffffff00 broadcast 10.0.2.255 nd6 options=21 media: Ethernet autoselect (1000baseT ) status: active Fixit# And as I said stable/8 and 8.0 rc also suffer from the same bug. (sysinstall doesn't seem to have a way to shutdown instead of reboot by itself but you can just `killall qemu' here when finished; if you want less violent redirect the monitor or omit -curses if you have X and in the monitor do `system_powerdown' to press the virtual acpi powerbutton and then hit return in sysinstall to confirm the `abort installation' prompt that should come up.) Thanx, Juergen PS: (Coming back to the actual tap networking on wifi use case:) Of course you could still use static routes on the other lan boxen that need to talk to the guest, or only use one on one box (like your router/ap) and setup proxy arp on that, but thats not nearly as nice as doing proxy arp on the same box that runs the guest. But of course its too late for 8.0 now... PPS: btw there is another use case besides wifi for doing it this way, i.e. routing + (optionally) proxy arp instead of bridging: when you want to protect your lan from stupid guests causing arp trouble etc... From Alexander at Leidinger.net Tue Nov 24 08:12:03 2009 From: Alexander at Leidinger.net (Alexander Leidinger) Date: Tue Nov 24 08:12:10 2009 Subject: Emulation of Linux V4L ioctls In-Reply-To: <20091123125403.20e3a63e@shibato.opal.com> References: <20091119153159.610debc2@shibato.opal.com> <20091120103535.815072bwgvis0io0@webmail.leidinger.net> <20091120103622.0db845c8@shibato.opal.com> <20091123144251.11055vw9sv236voc@webmail.leidinger.net> <20091123125403.20e3a63e@shibato.opal.com> Message-ID: <20091124091151.12733pwkk9ha1yyo@webmail.leidinger.net> Quoting "J.R. Oldroyd" (from Mon, 23 Nov 2009 12:54:03 -0500): > My test app is the net/skype port which installs: > /usr/local/share/skype/skype: ELF 32-bit LSB executable, Intel > 80386, version 1 (GNU/Linux), dynamically linked (uses shared libs), > for GNU/Linux 2.4.1, stripped > > I am running this on an amd64 with the code using the same > videodev.h. The video is working. Ergo, the structures appear > to be compatible. Your "appear" is the right word. Licensing issues aside (I try to get someone to have a look at it), I would import the code as is because of this and try to fix possible edge cases afterwards. The point is, we do not really know how much of the structure is used. It may be the case that the structure is partly compatible (and skype only uses this part), or compatible by accident (automatic padding by the compiler). With the right program (printing total size, ofsset of members, and size of memebers), you can detect both and take appropriate action. Bye, Alexander. -- nc(1) (or netcat) is useful not only for redirecting input/output to TCP or UDP connections, but also for proxying them with inetd(8). http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From fbsd at opal.com Tue Nov 24 16:22:27 2009 From: fbsd at opal.com (J.R. Oldroyd) Date: Tue Nov 24 16:22:35 2009 Subject: Emulation of Linux V4L ioctls In-Reply-To: <20091124091151.12733pwkk9ha1yyo@webmail.leidinger.net> References: <20091119153159.610debc2@shibato.opal.com> <20091120103535.815072bwgvis0io0@webmail.leidinger.net> <20091120103622.0db845c8@shibato.opal.com> <20091123144251.11055vw9sv236voc@webmail.leidinger.net> <20091123125403.20e3a63e@shibato.opal.com> <20091124091151.12733pwkk9ha1yyo@webmail.leidinger.net> Message-ID: <20091124112220.6b4b742f@shibato.opal.com> On Tue, 24 Nov 2009 09:11:51 +0100, Alexander Leidinger wrote: > > Quoting "J.R. Oldroyd" (from Mon, 23 Nov 2009 12:54:03 -0500): > > > My test app is the net/skype port which installs: > > /usr/local/share/skype/skype: ELF 32-bit LSB executable, Intel > > 80386, version 1 (GNU/Linux), dynamically linked (uses shared libs), > > for GNU/Linux 2.4.1, stripped > > > > I am running this on an amd64 with the code using the same > > videodev.h. The video is working. Ergo, the structures appear > > to be compatible. > > Your "appear" is the right word. Licensing issues aside (I try to get > someone to have a look at it), I would import the code as is because > of this and try to fix possible edge cases afterwards. The point is, > we do not really know how much of the structure is used. It may be the > case that the structure is partly compatible (and skype only uses this > part), or compatible by accident (automatic padding by the compiler). > With the right program (printing total size, ofsset of members, and > size of memebers), you can detect both and take appropriate action. > > Bye, > Alexander. > OK, I have placed such a program together with its output on an amd64 and i386 here: http://opal.com/freebsd/sys/compat/linux/linux_vidsize.c http://opal.com/freebsd/sys/compat/linux/linux_vidsize_out.amd64 http://opal.com/freebsd/sys/compat/linux/linux_vidsize_out.i386 There are differences in sizes in the following: video_tuner unsigned long rangelow video_tuner unsigned long rangehigh video_window struct video_clip * clips video_buffer void * base video_code __u8 * data All are 8 bytes on the amd64 and 4 bytes on the i386. -jr -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 196 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-emulation/attachments/20091124/01e37798/signature.pgp From julian at elischer.org Tue Nov 24 18:26:27 2009 From: julian at elischer.org (Julian Elischer) Date: Tue Nov 24 18:26:34 2009 Subject: Emulation of Linux V4L ioctls Message-ID: <4B0C2551.7040308@elischer.org> .. videodev.h > > There is indeed no license in this file. > > And this fact makes it a little bit hard to import into FreeBSD, at > least for a person like me with not so much knowledge about > copyright/license stuff. Someone out there (@FreeBSD.org) who is > willing to put some official weight into this issue? As I mentioned before, I have emails from the authors of this file to the effect that as an API definition they believe it is uncopyrightable, and in fact that they specifically want no copyright on it so that other people can use it. (e.g. us). julian From oberman at es.net Tue Nov 24 18:52:08 2009 From: oberman at es.net (Kevin Oberman) Date: Tue Nov 24 18:52:14 2009 Subject: Emulation of Linux V4L ioctls In-Reply-To: Your message of "Tue, 24 Nov 2009 10:26:25 PST." <4B0C2551.7040308@elischer.org> Message-ID: <20091124185136.6B8471CC2E@ptavv.es.net> > Date: Tue, 24 Nov 2009 10:26:25 -0800 > From: Julian Elischer > Sender: owner-freebsd-emulation@freebsd.org > > .. videodev.h > > > > > There is indeed no license in this file. > > > > And this fact makes it a little bit hard to import into FreeBSD, at > > least for a person like me with not so much knowledge about > > copyright/license stuff. Someone out there (@FreeBSD.org) who is > > willing to put some official weight into this issue? > > > As I mentioned before, I have emails from the authors of this file > to the effect that as an API definition they believe it is > uncopyrightable, and in fact that they specifically want no > copyright on it so that other people can use it. (e.g. us). Julian, If the author could add a note that the file is believed not subject to copyright but, if it is determined to be, that it is dedicated to the public domain, that would cover the issue quite well. (E.g. the "sticky" bit was explicitly dedicated to the public domain.) -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From miwi at FreeBSD.org Tue Nov 24 21:36:48 2009 From: miwi at FreeBSD.org (Martin Wilke) Date: Tue Nov 24 21:36:57 2009 Subject: [ports-i386@FreeBSD.org: linux-flashplugin-9.0r246 failed on i386 7-exp] Message-ID: <20091124213644.GG1709@bsdcrew.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - ----- Forwarded message from User Ports-i386 ----- Date: Tue, 24 Nov 2009 20:57:27 GMT From: User Ports-i386 To: erwin@FreeBSD.org, miwi@FreeBSD.org, linimon@FreeBSD.org Subject: linux-flashplugin-9.0r246 failed on i386 7-exp X-Spam-Status: No, score=-106.5 required=5.0 tests=AWL,BAYES_00, RCVD_IN_DNSWL_MED,USER_IN_WHITELIST autolearn=ham version=3.2.5 You can also find this build log at http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/a.7-exp.20091123145152/linux-flashplugin-9.0r246.log building linux-flashplugin-9.0r246 on gohan29.freebsd.org in directory /x/tmp/7-exp/20091123145152/chroot/230 DISTDIR=/tmp/distfiles DISTDIR=/tmp/distfiles/RESTRICTED building for: 7.2-STABLE i386 maintained by: emulation@freebsd.org port directory: /usr/ports/www/linux-flashplugin9 Makefile ident: $FreeBSD: ports/www/linux-flashplugin9/Makefile,v 1.35 2009/08/07 11:49:43 bsam Exp $ build started at Tue Nov 24 20:57:08 UTC 2009 FETCH_DEPENDS= PATCH_DEPENDS= EXTRACT_DEPENDS= BUILD_DEPENDS= RUN_DEPENDS=linux-openssl-0.9.7f_2.tbz linux_base-fc-4_15.tbz prefixes: LOCALBASE=usr/local X11BASE=usr/local add_pkg ================================================================ ======================================== => install_flash_player_9.tar.gz doesn't seem to exist in /tmp/distfiles/RESTRICTED/flashplugin/9.0r246. => Attempting to fetch from ftp://ftp-master.freebsd.org/pub/FreeBSD/ports/distfiles/flashplugin/9.0r246/. fetch: ftp://ftp-master.freebsd.org/pub/FreeBSD/ports/distfiles/flashplugin/9.0r246/install_flash_player_9.tar.gz: File unavailable (e.g., file not found, no access) => Attempting to fetch from ftp://pointyhat.freebsd.org/pub/FreeBSD/ports/distfiles/flashplugin/9.0r246/. fetch: ftp://pointyhat.freebsd.org/pub/FreeBSD/ports/distfiles/flashplugin/9.0r246/install_flash_player_9.tar.gz: File unavailable (e.g., file not found, no access) => Attempting to fetch from http://download.macromedia.com/pub/flashplayer/installers/current/9/. install_flash_player_9.tar.gz 2986 kB 5527 kBps => libflashsupport.so doesn't seem to exist in /tmp/distfiles/RESTRICTED/flashplugin/9.0r246. => Attempting to fetch from ftp://ftp-master.freebsd.org/pub/FreeBSD/ports/distfiles/flashplugin/9.0r246/. fetch: ftp://ftp-master.freebsd.org/pub/FreeBSD/ports/distfiles/flashplugin/9.0r246/libflashsupport.so: File unavailable (e.g., file not found, no access) => Attempting to fetch from ftp://pointyhat.freebsd.org/pub/FreeBSD/ports/distfiles/flashplugin/9.0r246/. fetch: ftp://pointyhat.freebsd.org/pub/FreeBSD/ports/distfiles/flashplugin/9.0r246/libflashsupport.so: File unavailable (e.g., file not found, no access) => Attempting to fetch from http://tijl.ulyssis.be/mirror/. fetch: http://tijl.ulyssis.be/mirror/libflashsupport.so: Moved Temporarily => Attempting to fetch from ftp://ftp-master.freebsd.org/pub/FreeBSD/ports/distfiles/flashplugin/9.0r246/. fetch: ftp://ftp-master.freebsd.org/pub/FreeBSD/ports/distfiles/flashplugin/9.0r246/libflashsupport.so: File unavailable (e.g., file not found, no access) => Attempting to fetch from ftp://pointyhat.freebsd.org/pub/FreeBSD/ports/distfiles/flashplugin/9.0r246/. fetch: ftp://pointyhat.freebsd.org/pub/FreeBSD/ports/distfiles/flashplugin/9.0r246/libflashsupport.so: File unavailable (e.g., file not found, no access) => Couldn't fetch it - please try to retrieve this => port manually into /tmp/distfiles/RESTRICTED/flashplugin/9.0r246 and try again. *** Error code 1 Stop in /a/ports/www/linux-flashplugin9. ================================================================ build of /usr/ports/www/linux-flashplugin9 ended at Tue Nov 24 20:57:21 UTC 2009 - ----- End forwarded message ----- - -- +-----------------------+-------------------------------+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAksMUesACgkQdLJIhLHm/OmRAgCeLgyCFnlOXxiMCHSJFUIiYqSw pMoAn2SOfm5j5nzvgZIMvJmREV/dRtrq =Ms9j -----END PGP SIGNATURE----- From emerlinsky at gmail.com Wed Nov 25 21:21:31 2009 From: emerlinsky at gmail.com (Yevgen Merlinsky) Date: Wed Nov 25 21:22:37 2009 Subject: problem with getting linux-f8-flashsupport-9.0.1.i386.tar.gz Message-ID: Hi, I've got a problem with getting distfile for the port /usr/ports/www/linux-f8-flashplugin10: => linux-f8-flashsupport-9.0.1.i386.tar.gz doesn't seem to exist in /usr/ports/distfiles/flashplugin/10.0r32. => Attempting to fetch from http://tijl.ulyssis.be/mirror/. fetch: http://tijl.ulyssis.be/mirror/linux-f8-flashsupport-9.0.1.i386.tar.gz: Moved Temporarily => Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/flashplugin/10.0r32/. fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/flashplugin/10.0r32/linux-f8-flashsupport-9.0.1.i386.tar.gz: File unavailable (e.g., file not found, no access) => Couldn't fetch it - please try to retrieve this => port manually into /usr/ports/distfiles/flashplugin/10.0r32 and try again. *** Error code 1 It seems like account was disabled for tijl.ulyssis.be. Could you please provide alternative URL for getting linux-f8-flashsupport-9.0.1.i386.tar.gz? Thank you. From tijl at fastmail.fm Wed Nov 25 22:58:32 2009 From: tijl at fastmail.fm (Tijl Coosemans) Date: Wed Nov 25 22:58:39 2009 Subject: problem with getting linux-f8-flashsupport-9.0.1.i386.tar.gz In-Reply-To: References: Message-ID: <200911252325.40912.tijl@fastmail.fm> > It seems like account was disabled for tijl.ulyssis.be. Yes, and it got disabled faster than I expected. You can fetch the file here for now: http://mirror.tijl.fastmail.fm/linux-f8-flashsupport-9.0.1.i386.tar.gz