Re: ieee denormal on ia64?
On Fri, Feb 25, 2011, Anton Shterenlikht wrote: Can somebody please confirm that denormal are not available on ia64, see below. [...] The FreeBSD manpage for fpsetmask() at http://tinyurl.com/64oo7zh says: #define FP_X_DNML 0x02/* denormal */ The FreeBSD manpage for fpsetmask() also says that it's deprecated. The standard way to do this is with the routines described in fenv(3), which has included an FE_DENORMAL flag since it was added in 2004. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: HEADS UP: ZFSv28 is in!
Wiadomość napisana przez Steve Wills w dniu 2011-03-06, o godz. 05:11: [..] Thanks for your work on this, I'm very happy to have ZFS v28. I just updated my -CURRENT system from a snapshot from about a month ago to code from today. I have 3 pools and one of them is for ports tinderbox. I only upgraded that pool. When I try to build something using tinderbox, I get this error: cp: failed to set acl entries for /usr/local/tinderbox/9-CURRENT-amd64-FreeBSD/buildscript: Operation not supported What does mount show? -- If you cut off my head, what would I say? Me and my head, or me and my body? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [PANIC] ffs_alloccg: map corrupted (w/SU+J)
On Sat, Mar 05, 2011 at 03:33:01PM -0800, David O'Brien wrote: Feb 24 19:43:16 : FreeBSD 9.0-CURRENT #662 r218815:218845M: Tue Feb 22 00:13:31 PST 2011 Feb 24 19:43:16 : /sys/i386/compile/DRAGON i386 [..] Mar 5 14:41:38 : start = 0, len = 1659, fs = /storage Mar 5 14:41:38 : panic: ffs_alloccg: map corrupted Mar 5 14:41:38 : cpuid = 0 Mar 5 14:41:38 : KDB: stack backtrace: Mar 5 14:41:38 : db_trace_self_wrapper(c084242b,65676172,a0d,4,0,...) at 0xc04ebf46 = db_trace_self_wrapper+0x26 Mar 5 14:41:38 : kdb_backtrace(c0860edc,0,c085531a,eaf4870c,0,...) at 0xc05ff87a = kdb_backtrace+0x2a Mar 5 14:41:38 : panic(c085531a,0,67b,c65230d4,e000c000,...) at 0xc05d1d67 = panic+0x117 Mar 5 14:41:38 : ffs_mapsearch(4462ea0,0,8,0,0,...) at 0xc0759163 = ffs_mapsearch+0x153 Mar 5 14:41:38 : ffs_alloccgblk(4462ea0,0,4000,5ae,0,...) at 0xc075935c = ffs_alloccgblk+0xec Mar 5 14:41:38 : ffs_alloccg(c99c29f8,2fa,4462ea0,0,4000,...) at 0xc0759c83 = ffs_alloccg+0x1b3 Mar 5 14:41:38 : ffs_hashalloc(4462ea0,0,4000,4000,c0759ad0,...) at 0xc0756321 = ffs_hashalloc+0x41 Mar 5 14:41:38 : ffs_alloc(c99c29f8,100e,0,4462ea0,0,...) at 0xc075acff = ffs_alloc+0x19f Mar 5 14:41:38 : ffs_balloc_ufs2(ca740110,4038000,0,4000,c8bc7400,...) at 0xc075cff9 = ffs_balloc_ufs2+0x1949 Mar 5 14:41:38 : ffs_write(eaf48b90,eaf48b4c,eaf48b10,c0780ac2,ca740168,...) at 0xc077fc66 = ffs_write+0x276 Mar 5 14:41:38 : VOP_WRITE_APV(c08bb080,eaf48b90,ca740110,264,0,...) at 0xc08036e4 = VOP_WRITE_APV+0xe4 Mar 5 14:41:38 : vn_write(c7cfcc78,eaf48c24,c8bc7400,0,cddd05c0,...) at 0xc0663ad3 = vn_write+0x1c3 Mar 5 14:41:38 : dofilewrite(eaf48c24,,,0,c7cfcc78,...) at 0xc060fe55 = dofilewrite+0x95 Mar 5 14:41:38 : kern_writev(cddd05c0,4,eaf48c24,eaf48c44,1,...) at 0xc06100e8 = kern_writev+0x58 Mar 5 14:41:38 : write(cddd05c0,eaf48cec,cddd05c0,eaf48d28,4,...) at 0xc061016f = write+0x4f Mar 5 14:41:38 : syscallenter(cddd05c0,eaf48ce4,eaf48ce4,0,3,...) at 0xc060b363 = syscallenter+0x2c3 Mar 5 14:41:38 : syscall(eaf48d28) at 0xc07e3114 = syscall+0x34 Mar 5 14:41:38 : Xint0x80_syscall() at 0xc07cf121 = Xint0x80_syscall+0x21 Mar 5 14:41:38 : --- syscall (4, FreeBSD ELF32, write), eip = 0x2818c60b, esp = 0xbfbfe86c, ebp = 0xbfbfe8d8 --- Changes since my last reported SU+J panic: 1. Newer revision of ahd(4) ASIC 2. New U320 SCA enclosures (different vendor + model). 3. New motherboard -- -- David (obr...@freebsd.org) P.S. I am using this UFS patch: Both changes you are using were superseded by proper fixes committed into HEAD for some time. For me, this indeed sounds as disk corruption. Could you somehow verify that the disks read the data that was written to ? E.g, putting some iso image with known sha checksum onto the disk with dd, and then reading that part and checksumming it ? pgprYtAFSWDPc.pgp Description: PGP signature
Re: HEADS UP: ZFSv28 is in!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/06/11 04:22, Edward Tomasz Napierała wrote: Wiadomość napisana przez Steve Wills w dniu 2011-03-06, o godz. 05:11: [..] Thanks for your work on this, I'm very happy to have ZFS v28. I just updated my -CURRENT system from a snapshot from about a month ago to code from today. I have 3 pools and one of them is for ports tinderbox. I only upgraded that pool. When I try to build something using tinderbox, I get this error: cp: failed to set acl entries for /usr/local/tinderbox/9-CURRENT-amd64-FreeBSD/buildscript: Operation not supported What does mount show? /dev/md4 12186190 332724 11853466 3% /usr/local/tinderbox/9-CURRENT-amd64-FreeBSD Sorry, I forgot about the mdmfs hacks I had in my local tinderd. Without them, it works fine. So the problem seems to be in mfs rather than zfs. Steve -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (FreeBSD) iQEcBAEBAgAGBQJNc42wAAoJEPXPYrMgexuhYiwH/0k+HYFiWHgDlpbEZL5xEYHS +ZlOZ19kW58A648iVbzuBgGWcQIEkylflJc23pigue+Qm5gvUR9PYZmr20hleCow 96pOxlQOyu1yJ/w90yJsfOTnVXfwdgEZWrHwiW+dDQp1YCGjnXqiocHT6gjukCNV HSm6hEMI9YD5y75tVZVep/en6VmSwywsLlHEL5T8M+x1bsUUkawCltNUcbYLfJWS NMuyG1ZudwscTj1bZHKyz+1bu5sToBj/w8aU7vASn5wvIjnKhMo/DDiCICyykbQ1 7Qa3i+BfG7ugvq6WxV7OiiCTYzx8f8R2D9QOtz6wmAPLkQbItRfdX7i0lxG+nig= =h6fT -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
can somebody explains OFDM in FreeBSD?
Hi, as the subject line implies, can someone explains why OFDM (Orthogonal Frequency Division Multiplexing) is required for running run(4) ? Is there any (safer) alternative to OFDM? If not, could the FreeBSD security team verify the the safety of OFDM derived drivers (in particular wireless ethernet based nics) so that no ones get hurt being a WLAN (802.11ng ethernet-class) subcarrier ? -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: please (re) test if_ath in -HEAD
Which versions did you have stable versus unstable AR9285 behaviour? I'd like to establish at least a range of subversion revisions so we can start binary searching which one(s) caused instabilities. Thanks, Adrian On 6 March 2011 22:24, Ian FREISLICH i...@clue.co.za wrote: Adrian Chadd wrote: Hi all, For those of you who are testing out my if_ath changes, I'd really appreciate it if you'd update to -HEAD and re-test. Since running the new code, I get a slew of these: Mar 6 14:41:53 mini wpa_supplicant[422]: Trying to associate with 00:30:4f:58:bf:94 (SSID='quasar' freq=2437 MHz) Mar 6 14:41:53 mini wpa_supplicant[422]: Associated with 00:30:4f:58:bf:94 Mar 6 14:41:53 mini kernel: wlan0: link state changed to UP Mar 6 14:41:54 mini wpa_supplicant[422]: WPA: Key negotiation completed with 00:30:4f:58:bf:94 [PTK=TKIP GTK=TKIP] Mar 6 14:41:54 mini wpa_supplicant[422]: CTRL-EVENT-CONNECTED - Connection to 00:30:4f:58:bf:94 completed (reauth) [id=7 id_str=] Mar 6 14:46:59 mini wpa_supplicant[422]: CTRL-EVENT-DISCONNECTED bssid=00:30:4f:58:bf:94 reason=0 Mar 6 14:46:59 mini kernel: wlan0: link state changed to DOWN Mar 6 14:47:02 mini wpa_supplicant[422]: Trying to associate with 00:30:4f:58:bf:94 (SSID='quasar' freq=2437 MHz) Mar 6 14:47:02 mini wpa_supplicant[422]: Associated with 00:30:4f:58:bf:94 Mar 6 14:47:02 mini kernel: wlan0: link state changed to UP Mar 6 14:47:03 mini wpa_supplicant[422]: WPA: Key negotiation completed with 00:30:4f:58:bf:94 [PTK=TKIP GTK=TKIP] Mar 6 14:47:03 mini wpa_supplicant[422]: CTRL-EVENT-CONNECTED - Connection to 00:30:4f:58:bf:94 completed (reauth) [id=7 id_str=] Mar 6 14:49:31 mini ntpd[1848]: kernel time sync status change 2001 Mar 6 14:56:53 mini wpa_supplicant[422]: CTRL-EVENT-DISCONNECTED bssid=00:30:4f:58:bf:94 reason=0 Mar 6 14:56:53 mini kernel: wlan0: link state changed to DOWN Mar 6 14:56:56 mini wpa_supplicant[422]: Trying to associate with 00:30:4f:58:bf:94 (SSID='quasar' freq=2437 MHz) Mar 6 14:56:56 mini wpa_supplicant[422]: Associated with 00:30:4f:58:bf:94 Mar 6 14:56:56 mini kernel: wlan0: link state changed to UP Mar 6 14:56:57 mini wpa_supplicant[422]: WPA: Key negotiation completed with 00:30:4f:58:bf:94 [PTK=TKIP GTK=TKIP] Mar 6 14:56:57 mini wpa_supplicant[422]: CTRL-EVENT-CONNECTED - Connection to 00:30:4f:58:bf:94 completed (reauth) [id=7 id_str=] Mar 6 16:18:28 mini kernel: ath0: bb hang detected (0x80), resetting My hardware is: ath0@pci0:1:0:0:class=0x028000 card=0x7167144f chip=0x002b168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'Atheros AR9285 Wireless LAN 802.11 a/b/g/n Controller (AR928x)' class = network It's also only able to maintain an 18-24Mbps connection, where before I had stable 54Mbps. Ian -- Ian Freislich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: can somebody explains OFDM in FreeBSD?
On Sunday 06 March 2011 15:23:02 Etienne Robillard wrote: Hi, as the subject line implies, can someone explains why OFDM (Orthogonal Frequency Division Multiplexing) is required for running run(4) ? Is there any (safer) alternative to OFDM? If not, could the FreeBSD security team verify the the safety of OFDM derived drivers (in particular wireless ethernet based nics) so that no ones get hurt being a WLAN (802.11ng ethernet-class) subcarrier ? As per my knowledge OFDM is a carrier format which is handled by the hardware. Is there anything in particular you want to high-light? --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
RFC: graid, first step done.
Hi. I would like to present for review and testing results of my and M. Warner Losh work on new GEOM-based ataraid(4) replacement - graid. At this moment we have implemented all required core functionality and the first set of transformation and metadata modules. Now we have implemented transformation modules to support such RAID levels: RAID0, RAID1, RAID1E, RAID10 and CONCAT. For all these levels all such features as reading, writing, rebuilding, I/O errors recovery and kernel dumping are supported. Metadata modules now written for Intel and JMicron RAID BIOS formats. JMicron format is minimalistic by itself, while Intel format is much more sophisticated, and now we support all of it features, except RAID level migration. Work on Promise (used by AMD) and SiliconImage formats is now in progress. Support for other metadata formats and RAID levels planned later. If somebody wants to help -- feel free to contact me to coordinate work. Patches are existing for HEAD, 8-STABLE and 7-STABLE branches: http://people.freebsd.org/~mav/graid/graid-head-20110305.diff http://people.freebsd.org/~mav/graid/graid-8-20110305.diff http://people.freebsd.org/~mav/graid/graid-7-20110305.diff Patches for HEAD and 8-STABLE are not very invasive and, if everything goes well, going to be committed to HEAD in few weeks. Patch for 7-STABLE, except graid, also includes massive update of the ATA and CAM code from 9-CURRENT. It will not be committed due to numerous ABI breakages, but can be interesting to some people. Just be aware that main focus there was on ATA subsystem -- SCSI drivers were not tested. Once completed, this project should remove last major show stopper for enabling CAM-based ATA subsystem by default in 9.x branch. I would really like it to be done before 9.0 release. Special thanks to Cisco Systems, Inc. and iXsystems, Inc. for sponsoring this project. -- Alexander Motin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ACL issue (Was Re: HEADS UP: ZFSv28 is in!)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/06/11 08:35, Steve Wills wrote: On 03/06/11 04:22, Edward Tomasz NapieraBa wrote: Wiadomo[ napisana przez Steve Wills w dniu 2011-03-06, o godz. 05:11: [..] Thanks for your work on this, I'm very happy to have ZFS v28. I just updated my -CURRENT system from a snapshot from about a month ago to code from today. I have 3 pools and one of them is for ports tinderbox. I only upgraded that pool. When I try to build something using tinderbox, I get this error: cp: failed to set acl entries for /usr/local/tinderbox/9-CURRENT-amd64-FreeBSD/buildscript: Operation not supported What does mount show? /dev/md4 12186190 332724 11853466 3% /usr/local/tinderbox/9-CURRENT-amd64-FreeBSD Sorry, I forgot about the mdmfs hacks I had in my local tinderd. Without them, it works fine. So the problem seems to be in mfs rather than zfs. I should have said mdmfs, but all that's doing is running mdconfig and newfs for me. I've reproduced the issue without mdmfs: % mdconfig -a -t swap -s 12G -u 4 % newfs -m 0 -o time /dev/md4 [...] % mount /dev/md4 /tmp/foobar % cp -p /usr/local/tinderbox/scripts/lib/buildscript /tmp/foobar cp: failed to set acl entries for /tmp/foobar/buildscript: Operation not supported Without -p it works fine. FWIW: % getfacl /usr/local/tinderbox/scripts/lib/buildscript # file: /usr/local/tinderbox/scripts/lib/buildscript # owner: root # group: wheel owner@:--:--:deny owner@:rwxp---A-W-Co-:--:allow group@:-w-p--:--:deny group@:r-x---:--:allow everyone@:-w-p---A-W-Co-:--:deny everyone@:r-x---a-R-c--s:--:allow Any suggestions on where the problem could be? Thanks, Steve -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (FreeBSD) iQEcBAEBAgAGBQJNc52WAAoJEPXPYrMgexuhayoH/ROak0Vj2Ezh3t0ViqeZ8n/v Pa60x/MDvHcoqtEUM6CQulvf88pAjat07JCwoZKf2qlNgZgrcoK5gPjSeDsN+9jW LJxuFIyTOAmNxVC3FJgRuynTv06nAXDJu9f8psYVQS8EW56UQ9gmvKWNA3v80w2F bre2qzHneA42+5ZvVLnK6sSMJ2IBoyk9F1FXamUsP74TKygDL3iijatWWROJ+lQ+ HdY+TnmKEkZcXbl5qhya4etpPOxKcuTCD/VqYvUJXqkseIny9SE60xVhGyQWlDkU xEtjHQL8oRkc5CTHpCVJQMFiVGNFpBKutZq56wAaG0xgcDuWhvHJ3hcv8m93VYg= =c86J -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: please (re) test if_ath in -HEAD
Adrian Chadd wrote: Hi all, For those of you who are testing out my if_ath changes, I'd really appreciate it if you'd update to -HEAD and re-test. Since running the new code, I get a slew of these: Mar 6 14:41:53 mini wpa_supplicant[422]: Trying to associate with 00:30:4f:58:bf:94 (SSID='quasar' freq=2437 MHz) Mar 6 14:41:53 mini wpa_supplicant[422]: Associated with 00:30:4f:58:bf:94 Mar 6 14:41:53 mini kernel: wlan0: link state changed to UP Mar 6 14:41:54 mini wpa_supplicant[422]: WPA: Key negotiation completed with 00:30:4f:58:bf:94 [PTK=TKIP GTK=TKIP] Mar 6 14:41:54 mini wpa_supplicant[422]: CTRL-EVENT-CONNECTED - Connection to 00:30:4f:58:bf:94 completed (reauth) [id=7 id_str=] Mar 6 14:46:59 mini wpa_supplicant[422]: CTRL-EVENT-DISCONNECTED bssid=00:30:4f:58:bf:94 reason=0 Mar 6 14:46:59 mini kernel: wlan0: link state changed to DOWN Mar 6 14:47:02 mini wpa_supplicant[422]: Trying to associate with 00:30:4f:58:bf:94 (SSID='quasar' freq=2437 MHz) Mar 6 14:47:02 mini wpa_supplicant[422]: Associated with 00:30:4f:58:bf:94 Mar 6 14:47:02 mini kernel: wlan0: link state changed to UP Mar 6 14:47:03 mini wpa_supplicant[422]: WPA: Key negotiation completed with 00:30:4f:58:bf:94 [PTK=TKIP GTK=TKIP] Mar 6 14:47:03 mini wpa_supplicant[422]: CTRL-EVENT-CONNECTED - Connection to 00:30:4f:58:bf:94 completed (reauth) [id=7 id_str=] Mar 6 14:49:31 mini ntpd[1848]: kernel time sync status change 2001 Mar 6 14:56:53 mini wpa_supplicant[422]: CTRL-EVENT-DISCONNECTED bssid=00:30:4f:58:bf:94 reason=0 Mar 6 14:56:53 mini kernel: wlan0: link state changed to DOWN Mar 6 14:56:56 mini wpa_supplicant[422]: Trying to associate with 00:30:4f:58:bf:94 (SSID='quasar' freq=2437 MHz) Mar 6 14:56:56 mini wpa_supplicant[422]: Associated with 00:30:4f:58:bf:94 Mar 6 14:56:56 mini kernel: wlan0: link state changed to UP Mar 6 14:56:57 mini wpa_supplicant[422]: WPA: Key negotiation completed with 00:30:4f:58:bf:94 [PTK=TKIP GTK=TKIP] Mar 6 14:56:57 mini wpa_supplicant[422]: CTRL-EVENT-CONNECTED - Connection to 00:30:4f:58:bf:94 completed (reauth) [id=7 id_str=] Mar 6 16:18:28 mini kernel: ath0: bb hang detected (0x80), resetting My hardware is: ath0@pci0:1:0:0:class=0x028000 card=0x7167144f chip=0x002b168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'Atheros AR9285 Wireless LAN 802.11 a/b/g/n Controller (AR928x)' class = network It's also only able to maintain an 18-24Mbps connection, where before I had stable 54Mbps. Ian -- Ian Freislich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: can somebody explains OFDM in FreeBSD?
OFDM is part of 11g, 11a, and 11n (2/5ghz.) I don't understand why you're asking about it in a security context. Adrian On 6 March 2011 22:23, Etienne Robillard e...@gthcfoundation.org wrote: Hi, as the subject line implies, can someone explains why OFDM (Orthogonal Frequency Division Multiplexing) is required for running run(4) ? Is there any (safer) alternative to OFDM? If not, could the FreeBSD security team verify the the safety of OFDM derived drivers (in particular wireless ethernet based nics) so that no ones get hurt being a WLAN (802.11ng ethernet-class) subcarrier ? -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: can somebody explains OFDM in FreeBSD?
On 06/03/11 09:33 AM, Hans Petter Selasky wrote: On Sunday 06 March 2011 15:23:02 Etienne Robillard wrote: Hi, as the subject line implies, can someone explains why OFDM (Orthogonal Frequency Division Multiplexing) is required for running run(4) ? Is there any (safer) alternative to OFDM? If not, could the FreeBSD security team verify the the safety of OFDM derived drivers (in particular wireless ethernet based nics) so that no ones get hurt being a WLAN (802.11ng ethernet-class) subcarrier ? As per my knowledge OFDM is a carrier format which is handled by the hardware. Is there anything in particular you want to high-light? --HPS Yes, from a security perspective, could radiance from ELF/VLF operating devices as ethernet-class subcarriers which is part of the OFDM spec be considered harmful? if not is there any OFDM code in OpenBSD? Cheers, references: 1. Orthogonal Frequency Division Multiplexing (OFDM) https://gthc.org/investigations/pub/armstrong.pdf -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: can somebody explains OFDM in FreeBSD?
OpenBSD has driver support for OFDM chips. Anything that speaks 11a, 11g or 11n == OFDM. You'd have to speak to an RF related person about your definition of harmful. I mean, think about it - 802.11 devices are supposed to give off EMR that a receiver can decode. So your question about whether OFDM being harmful requires more context, as unlike wired solutions (say wired ethernet) which may give off EMR which could then be snooped, 802.11 is supposed to be received through EMF. :) Also, that paper you referenced talks about ERLANG, it doesn't mention OFDM anywhere. HTH, Adrian On 6 March 2011 22:56, Etienne Robillard e...@gthcfoundation.org wrote: On 06/03/11 09:33 AM, Hans Petter Selasky wrote: On Sunday 06 March 2011 15:23:02 Etienne Robillard wrote: Hi, as the subject line implies, can someone explains why OFDM (Orthogonal Frequency Division Multiplexing) is required for running run(4) ? Is there any (safer) alternative to OFDM? If not, could the FreeBSD security team verify the the safety of OFDM derived drivers (in particular wireless ethernet based nics) so that no ones get hurt being a WLAN (802.11ng ethernet-class) subcarrier ? As per my knowledge OFDM is a carrier format which is handled by the hardware. Is there anything in particular you want to high-light? --HPS Yes, from a security perspective, could radiance from ELF/VLF operating devices as ethernet-class subcarriers which is part of the OFDM spec be considered harmful? if not is there any OFDM code in OpenBSD? Cheers, references: 1. Orthogonal Frequency Division Multiplexing (OFDM) https://gthc.org/investigations/pub/armstrong.pdf -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: can somebody explains OFDM in FreeBSD?
On 06/03/11 10:01 AM, Adrian Chadd wrote: OpenBSD has driver support for OFDM chips. Anything that speaks 11a, 11g or 11n == OFDM. You'd have to speak to an RF related person about your definition of harmful. I mean, think about it - 802.11 devices are supposed to give off EMR that a receiver can decode. So your question about whether OFDM being harmful requires more context, as unlike wired solutions (say wired ethernet) which may give off EMR which could then be snooped, 802.11 is supposed to be received through EMF. :) Also, that paper you referenced talks about ERLANG, it doesn't mention OFDM anywhere. HTH, Adrian Orthogonal Frequency Division Multiplexing: https://gthc.org/investigations/OFDM/72_armstrong_ofdm.pdf @Diane: I'm worried from a amateur computer scientist point-of-view about the harmfulness of EMF fields; in particular the ELF/VLF frequencies as defined in OFDM, for operating WLAN devices as 'ethernet-class subcarriers'.. Kind regards, -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: can somebody explains OFDM in FreeBSD?
On Sun, Mar 06, 2011 at 03:33:32PM +0100, Hans Petter Selasky wrote: On Sunday 06 March 2011 15:23:02 Etienne Robillard wrote: Hi, as the subject line implies, can someone explains why OFDM (Orthogonal Frequency Division Multiplexing) is required for running run(4) ? Is there any (safer) alternative to OFDM? Orthogonal Frequency Domain Multiplexing (OFDM) Is simply the transmission of multiple carriers in one spectrum. It is used for DSL modems for example. Each carrier contributes a portion of the bandwidth. Coded Orthogonal Frequency Domain Multiplexing is a newer form of OFDM where the signals are coded to minimise interference with other carriers. Look for articles on COFDM Here is one such that looks pretty complete. http://www.andreas-schwope.de/ ASIC_s/Schnittstellen/Data_Lines/body_multiplexing.html This is a nice article as well: http://www.digitalradiotech.co.uk/cofdm.htm If not, could the FreeBSD security team verify the the safety of OFDM derived drivers (in particular wireless ethernet based nics) so that no ones get hurt being a WLAN (802.11ng ethernet-class) subcarrier ? Security is not a problem. COFDM is a hardware level transmission layer 1 and some layer 2. Amusingly OFDM is a form of spread spectrum which originally had military uses, it's harder to jam or decrypt. As per my knowledge OFDM is a carrier format which is handled by the hardware. Is there anything in particular you want to high-light? Yep. I think they are worried about the encryption (WEP vs. WMA etc.). --HPS - Diane (VA3DB) -- - d...@freebsd.org d...@db.net http://www.db.net/~db ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: can somebody explains OFDM in FreeBSD?
On Sun, Mar 06, 2011 at 09:56:05AM -0500, Etienne Robillard wrote: On 06/03/11 09:33 AM, Hans Petter Selasky wrote: On Sunday 06 March 2011 15:23:02 Etienne Robillard wrote: .. Yes, from a security perspective, could radiance from ELF/VLF operating devices as ethernet-class subcarriers which is part of the OFDM spec be considered harmful? No. It's twisted pair so will not radiate that far, it's not an antenna. DSL is sent via twisted pair as well and should not radiate very far. if not is there any OFDM code in OpenBSD? It's in the hardware not BSD. You could also look at gnuradio. Your link should have been: https://gthc.org/investigations/OFDM/72_armstrong_ofdm.pdf Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell Oh dear oh dear. https://gthc.org/investigations/chemtrails-volume2/ You are one of 'those'. You are one of the conspiracy nutters. I think this guy should be blocked from this list. - Diane (VA3DB) -- - d...@freebsd.org d...@db.net http://www.db.net/~db ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: can somebody explains OFDM in FreeBSD?
No. It's twisted pair so will not radiate that far, it's not an antenna. DSL is sent via twisted pair as well and should not radiate very far. Twisted pair? Sorry I don't understand this... Wireless USB dongles are being operating as EMF/RF devices and forcingly will radiate with objects close to the carrier... Your link should have been: https://gthc.org/investigations/OFDM/72_armstrong_ofdm.pdf Thats correct link sorry for the confusion :-) Oh dear oh dear. https://gthc.org/investigations/chemtrails-volume2/ You are one of 'those'. You are one of the conspiracy nutters. I think this guy should be blocked from this list. - Diane (VA3DB) This is out-of-scope but I respect your opinion to call me a name attempting to shed some lights on the security aspect of implict uses of OFDM in FreeBSD... :-) -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Fwd: Re: can somebody explains OFDM in FreeBSD?
my best bet is that VLF/ELF frequencies are using FFT (Fast Fourier Transform) algorithm to increase compression ratio of WLAN devices operating with OFDM-enabled hardware. If that is true then not all WLAN devices can do OFDM thus explaining why you could use 802.11g without it... Original Message Return-Path:abi...@abitos.org X-Original-To: e...@gthcfoundation.org Delivered-To: e...@gthcfoundation.org Received: from mail-fx0-f42.google.com (mail-fx0-f42.google.com [209.85.161.42]) by gthcfoundation.org (Postfix) with ESMTP id 7F93B9C488 for e...@gthcfoundation.org; Sun, 6 Mar 2011 15:33:37 + (UTC) Received: by fxm20 with SMTP id 20so3451200fxm.29 for e...@gthcfoundation.org; Sun, 06 Mar 2011 07:33:26 -0800 (PST) Received: by 10.223.106.1 with SMTP id v1mr3580291fao.21.1299425606490; Sun, 06 Mar 2011 07:33:26 -0800 (PST) Received: from [192.168.4.20] (pD9FCB6B4.dip.t-dialin.net [217.252.182.180]) by mx.google.com with ESMTPS id 5sm545591fak.47.2011.03.06.07.33.24 (version=SSLv3 cipher=OTHER); Sun, 06 Mar 2011 07:33:25 -0800 (PST) Message-ID: 4d73a943.90...@abitos.org Date: Sun, 06 Mar 2011 16:33:23 +0100 From: Tobias Blersch abi...@abitos.org User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7 MIME-Version: 1.0 To: e...@gthcfoundation.org Subject:Re: can somebody explains OFDM in FreeBSD? References: 4d7398c6.8030...@gthcfoundation.org 201103061533.32138.hsela...@c2i.net 4d73a085.4030...@gthcfoundation.org 20110306151548.gb29...@night.db.net 4d73a74a.7040...@gthcfoundation.org In-Reply-To:4d73a74a.7040...@gthcfoundation.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi, your post mentioned ELF/VLF radiation, thats electromagnetic waves the frequency range below 30kHz. How should a modulation scheme (OFDM) used in the 2.4/5GHz range be related to radiation in such a low frequency band? Tobias ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: can somebody explains OFDM in FreeBSD?
I've moved this off of freebsd-current into private e-mail folks. Twisted pair? Sorry I don't understand this... Wireless USB dongles are ... This is out-of-scope but I respect your opinion to call me a name attempting It is not an ad hominem when it is factually true. These are not chemical trails you are seeing. http://en.wikipedia.org/wiki/Chemtrail_conspiracy_theory You are a nutter if you believe they are chemical trails. QED P.S. Have you noticed the colours from a sprinkler in the Sun? (I will not reply to any more postings about this on freebsd-current) - Diane (VA3DB) -- - d...@freebsd.org d...@db.net http://www.db.net/~db ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: can somebody explains OFDM in FreeBSD?
I would appreciate if you try not to disrupt this thread anymore on freebsd-current. Thank you. On 06/03/11 10:42 AM, Diane Bruce wrote: I've moved this off of freebsd-current into private e-mail folks. Twisted pair? Sorry I don't understand this... Wireless USB dongles are ... This is out-of-scope but I respect your opinion to call me a name attempting It is not an ad hominem when it is factually true. These are not chemical trails you are seeing. http://en.wikipedia.org/wiki/Chemtrail_conspiracy_theory You are a nutter if you believe they are chemical trails. QED P.S. Have you noticed the colours from a sprinkler in the Sun? (I will not reply to any more postings about this on freebsd-current) - Diane (VA3DB) -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ACL issue (Was Re: HEADS UP: ZFSv28 is in!)
On Sun, Mar 06, 2011 at 09:43:34AM -0500, Steve Wills wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/06/11 08:35, Steve Wills wrote:
On 03/06/11 04:22, Edward Tomasz NapieraBa wrote:
Wiadomo[ napisana przez Steve Wills w dniu 2011-03-06, o godz. 05:11:
[..]
Thanks for your work on this, I'm very happy to have ZFS v28. I just
updated my -CURRENT system from a snapshot from about a month ago to
code from today. I have 3 pools and one of them is for ports tinderbox.
I only upgraded that pool. When I try to build something using
tinderbox, I get this error:
cp: failed to set acl entries for
/usr/local/tinderbox/9-CURRENT-amd64-FreeBSD/buildscript: Operation not
supported
What does mount show?
/dev/md4 12186190 332724 11853466 3%
/usr/local/tinderbox/9-CURRENT-amd64-FreeBSD
Sorry, I forgot about the mdmfs hacks I had in my local tinderd. Without
them, it works fine. So the problem seems to be in mfs rather than zfs.
I should have said mdmfs, but all that's doing is running mdconfig and
newfs for me. I've reproduced the issue without mdmfs:
% mdconfig -a -t swap -s 12G -u 4
% newfs -m 0 -o time /dev/md4
[...]
% mount /dev/md4 /tmp/foobar
% cp -p /usr/local/tinderbox/scripts/lib/buildscript /tmp/foobar
cp: failed to set acl entries for /tmp/foobar/buildscript: Operation not
supported
Without -p it works fine. FWIW:
% getfacl /usr/local/tinderbox/scripts/lib/buildscript
# file: /usr/local/tinderbox/scripts/lib/buildscript
# owner: root
# group: wheel
owner@:--:--:deny
owner@:rwxp---A-W-Co-:--:allow
group@:-w-p--:--:deny
group@:r-x---:--:allow
everyone@:-w-p---A-W-Co-:--:deny
everyone@:r-x---a-R-c--s:--:allow
Any suggestions on where the problem could be?
At first glance it looks like acl_set_fd_np(3) isn't working on an
md-backed filesystem; specifically, it's returning EOPNOTSUPP. You
should be able to reproduce the problem by doing a setfacl on something
in /tmp/foobar.
Looking through src/bin/cp/utils.c, this is the code:
420 if (acl_set_fd_np(dest_fd, acl, acl_type) 0) {
421 warn(failed to set acl entries for %s, to.p_path);
422 acl_free(acl);
423 return (1);
424 }
EOPNOTSUPP for acl_set_fd_np(3) is defined as:
[EOPNOTSUPP] The file system does not support ACL retrieval.
This would be referring to the destination filesystem.
Looking through the md(4) source for references to EOPNOTSUPP, we do
find some references:
$ egrep -n -r EOPNOTSUPP|ENOTSUP /usr/src/sys/dev/md
/usr/src/sys/dev/md/md.c:423: return (EOPNOTSUPP);
/usr/src/sys/dev/md/md.c:475: error = EOPNOTSUPP;
/usr/src/sys/dev/md/md.c:523: return (EOPNOTSUPP);
/usr/src/sys/dev/md/md.c:601: return (EOPNOTSUPP);
/usr/src/sys/dev/md/md.c:731: error = EOPNOTSUPP;
Line 423 is within mdstart_malloc(), and it returns EOPNOTSUPP on any
BIO operation other than READ/WRITE/DELETE. Line 475 is a continuation
of that.
Line 508 is within mdstart_vnode(), behaving effectively the same as
line 423. Line 601 is within mdstart_swap(), behaving effectively the
same as line 423.
Line 731 is within md_kthread(), and indicates only BIO operation
BIO_GETATTR is supported. This would not be an ACL attribute thing,
but rather getting attributes of the backing device itself. The code
hints at that:
722 if (bp-bio_cmd == BIO_GETATTR) {
723 if ((sc-fwsectors sc-fwheads
724 (g_handleattr_int(bp, GEOM::fwsectors,
725 sc-fwsectors) ||
726 g_handleattr_int(bp, GEOM::fwheads,
727 sc-fwheads))) ||
728 g_handleattr_int(bp, GEOM::candelete, 1))
729 error = -1;
730 else
731 error = EOPNOTSUPP;
732 } else {
This leaves me with some ideas; just tossing them out here...
1. Maybe/somehow this is caused by swap being used as the backing
type/store for md(4)? Try using mdconfig -t malloc -o reserve
instead, temporarily anyway.
2. Are you absolutely 100% sure the kernel you're using was built
with options UFS_ACL defined in it? Doing a strings -a
/boot/kernel/kernel | grep UFS_ACL should suffice.
--
| Jeremy Chadwick j...@parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP 4BD6C0CB |
___
freebsd-current@freebsd.org mailing list
Re: can somebody explains OFDM in FreeBSD?
. https://gthc.org/investigations/OFDM/72_armstrong_ofdm.pdf That paper is a basic paper. COFDM is being used just about everywhere now. OFDM was used in the Telebit modems of years gone by. To this day (last I checked) it is superiour to the v32.bis format used today on third world phone lines, because of its ability to ignore dead spots in the frequency spectrums used. ... Reference(s) please? I'm worried from a amateur computer scientist point-of-view about the harmfulness of EMF fields; in particular the ELF/VLF frequencies as defined in OFDM, for operating WLAN devices as 'ethernet-class subcarriers'.. I personally would not worry about DSL and ethernet. The fields are self cancelling due to the twisted pair. It's a transmission line. I do worry much more about cell phone and wifi signals. I advise others not to use cellphones for long periods of time without a remote earpiece. (And of course, do likewise). Cell phone towers provided they are up high enough do not bother me. Keep in mind the inverse square law here. I would also suggest you look for the papers on double blind studies of so-called RF sensitive individuals. (ES) I am very sceptical personally of the effects. That said, I would not want to be within the near field of any high power transmitter. This is why broadcast stations have fences around their antennas and warning signs. The high power stuff is dangerous. Its not phone lines who are the main issue, rather the radiation levels of OFDM ethernet class devices (including USB devices and routers) using ELF/VLF frequencies below 30khz as per the newer 802.11(ng) drafts... ;-) -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ACL issue (Was Re: HEADS UP: ZFSv28 is in!)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/06/11 10:37, Jeremy Chadwick wrote:
At first glance it looks like acl_set_fd_np(3) isn't working on an
md-backed filesystem; specifically, it's returning EOPNOTSUPP. You
should be able to reproduce the problem by doing a setfacl on something
in /tmp/foobar.
Looking through src/bin/cp/utils.c, this is the code:
420 if (acl_set_fd_np(dest_fd, acl, acl_type) 0) {
421 warn(failed to set acl entries for %s, to.p_path);
422 acl_free(acl);
423 return (1);
424 }
EOPNOTSUPP for acl_set_fd_np(3) is defined as:
[EOPNOTSUPP] The file system does not support ACL retrieval.
This would be referring to the destination filesystem.
Looking through the md(4) source for references to EOPNOTSUPP, we do
find some references:
$ egrep -n -r EOPNOTSUPP|ENOTSUP /usr/src/sys/dev/md
/usr/src/sys/dev/md/md.c:423: return (EOPNOTSUPP);
/usr/src/sys/dev/md/md.c:475: error = EOPNOTSUPP;
/usr/src/sys/dev/md/md.c:523: return (EOPNOTSUPP);
/usr/src/sys/dev/md/md.c:601: return (EOPNOTSUPP);
/usr/src/sys/dev/md/md.c:731: error = EOPNOTSUPP;
Line 423 is within mdstart_malloc(), and it returns EOPNOTSUPP on any
BIO operation other than READ/WRITE/DELETE. Line 475 is a continuation
of that.
Line 508 is within mdstart_vnode(), behaving effectively the same as
line 423. Line 601 is within mdstart_swap(), behaving effectively the
same as line 423.
Line 731 is within md_kthread(), and indicates only BIO operation
BIO_GETATTR is supported. This would not be an ACL attribute thing,
but rather getting attributes of the backing device itself. The code
hints at that:
722 if (bp-bio_cmd == BIO_GETATTR) {
723 if ((sc-fwsectors sc-fwheads
724 (g_handleattr_int(bp, GEOM::fwsectors,
725 sc-fwsectors) ||
726 g_handleattr_int(bp, GEOM::fwheads,
727 sc-fwheads))) ||
728 g_handleattr_int(bp, GEOM::candelete, 1))
729 error = -1;
730 else
731 error = EOPNOTSUPP;
732 } else {
Thanks for the investigation! So this seems to be a bug in md? That's
too bad, I was enjoying using it to make my tinderbox builds faster.
This leaves me with some ideas; just tossing them out here...
1. Maybe/somehow this is caused by swap being used as the backing
type/store for md(4)? Try using mdconfig -t malloc -o reserve
instead, temporarily anyway.
Seems to be the same.
2. Are you absolutely 100% sure the kernel you're using was built
with options UFS_ACL defined in it? Doing a strings -a
/boot/kernel/kernel | grep UFS_ACL should suffice.
Yep, it does:
% strings -a /boot/kernel/kernel | grep UFS_ACL
options UFS_ACL
(My kernel config is just include GENERIC then a bunch of nooptions
for KDB, DDB, GDB, INVARIANTS, WITNESS, etc.)
Steve
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.16 (FreeBSD)
iQEcBAEBAgAGBQJNc7DxAAoJEPXPYrMgexuh3gsH/0L474FitZMdLLrTLiDiU7jR
D+9syg0boUYcWbv6pA1j1r8LvXMrw0rIxvZOPB4BauY/u8nL5n0YgDgv7tjb69+D
n/m7ce6r1tm6JtBSl/d+MIYfmcnj1E9B8ibgeGwPApKnhe4lmmyLpFHW98tcU1EL
Be+koxDiaKloryyfHrlcIfmSmXMUZ8lP7MFHfFeS39KbE+sf7xXHHLjFE7bcPSi4
qKyBFDcw/ykRjsrM3+YDIanhLUHg8ZjKhlrzbPUgMpzlXXe2QbmLkQELa9SmhVzH
juYywb7JOe5uHuefFQxnTLkSWuDjTlxLW6M+FuNEDejfA91sGIil7m+1nMcdCFg=
=nsSt
-END PGP SIGNATURE-
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: can somebody explains OFDM in FreeBSD?
I'm no expert in Wifi or in FFT so I'm forwarding your reply to the list hoping someone with experience with FFT could share lights on OFDM uses of FFT functions below the 30khz range... In other words could FreeBSD be used to control the electromagnetic energy input from out-of-band VLF/ELF waves ? Thanks, On Sun, Mar 06, 2011 at 10:38:30AM -0500, Etienne Robillard wrote: my best bet is that VLF/ELF frequencies are using FFT (Fast Fourier Transform) algorithm to increase compression ratio of WLAN devices No. FFT has nothing to do with this. FFT is a mathematical transform. Nothing more, nothing less. your post mentioned ELF/VLF radiation, thats electromagnetic waves the frequency range below 30kHz. How should a modulation scheme (OFDM) used in the 2.4/5GHz range be related to radiation in such a low frequency band? It is not. A modulation scheme can be used at any frequency. Nothing to do with the frequency itself. - Diane -- - d...@freebsd.org d...@db.net http://www.db.net/~db ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: can somebody explains OFDM in FreeBSD?
On 06/03/11 09:49 AM, Adrian Chadd wrote: OFDM is part of 11g, 11a, and 11n (2/5ghz.) I don't understand why you're asking about it in a security context. Adrian Approaching security can be seen with onion paradigm: True paranoids will want to have multiple layers of security whether its physical or hardware related. In this case, one could ask reasonably whether its 'safe' to be close to a wireless router (802.11 ethernet-class) for a long-term period while OFDM is enabled at the transport level. Thanks, Etienne ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ACL issue (Was Re: HEADS UP: ZFSv28 is in!)
On 6 Mar 2011, at 16:30, Jeremy Chadwick wrote: 2. Are you absolutely 100% sure the kernel you're using was built with options UFS_ACL defined in it? Doing a strings -a /boot/kernel/kernel | grep UFS_ACL should suffice. Yep, it does: % strings -a /boot/kernel/kernel | grep UFS_ACL options UFS_ACL (My kernel config is just include GENERIC then a bunch of nooptions for KDB, DDB, GDB, INVARIANTS, WITNESS, etc.) Cool, good to rule out the obvious. Thanks. The only other thing I can think of off the top of my head would be to ktrace -t+ -i the cp -p, then provide output of kdump -s -t+ after. I wouldn't say go about this quite yet (it may not even help determine what's going on); maybe wait for Robert to take a look first. It would help if I actually added Robert to the CC list, wouldn't it? :-) There's a lot of information in that post, perhaps it would be useful for someone to clarify what's going on exactly. If you're using ACLs on UFS, have you turned them on using tunefs? What flavour of ACLs are you using -- POSIX.1e or NFSv4? Robert___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ACL issue (Was Re: HEADS UP: ZFSv28 is in!)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/06/11 11:30, Jeremy Chadwick wrote: On Sun, Mar 06, 2011 at 08:23:42AM -0800, Jeremy Chadwick wrote: On Sun, Mar 06, 2011 at 11:06:09AM -0500, Steve Wills wrote: Sorry, I should have been more clear -- my investigation wasn't to determine if the issue you're reporting was a bug or not, but more along the lines of hmm, where is userland getting EOPNOTSUPP from in the kernel in this situation? It could be that some piece hasn't been implemented somewhere yet (more an incomplete than a bug :-) ). I tend to trace source the way I did above in hopes that someone (kernel dev, etc.) will chime in and go Oh, yes, THAT... let me tell you about that! It's also for educational purposes; I figure sharing the innards along with some simple descriptions might help people feel more comfortable (vs. thinking everything is a black box; don't let the magic smoke out!). Sometimes digging through the code helps. Definitely. I had started looking at cp(1) source, but got a bit lost. This leaves me with some ideas; just tossing them out here... 1. Maybe/somehow this is caused by swap being used as the backing type/store for md(4)? Try using mdconfig -t malloc -o reserve instead, temporarily anyway. Seems to be the same. I'm not too surprised, but at least that rules out swap vs. non-block-device stuff being somehow responsible. I'm not a user of ACLs myself, but Robert Watson might know what's up with this, or where to go looking. I've CC'd him here. 2. Are you absolutely 100% sure the kernel you're using was built with options UFS_ACL defined in it? Doing a strings -a /boot/kernel/kernel | grep UFS_ACL should suffice. Yep, it does: % strings -a /boot/kernel/kernel | grep UFS_ACL options UFS_ACL (My kernel config is just include GENERIC then a bunch of nooptions for KDB, DDB, GDB, INVARIANTS, WITNESS, etc.) Cool, good to rule out the obvious. Thanks. The only other thing I can think of off the top of my head would be to ktrace -t+ -i the cp -p, then provide output of kdump -s -t+ after. I wouldn't say go about this quite yet (it may not even help determine what's going on); maybe wait for Robert to take a look first. It would help if I actually added Robert to the CC list, wouldn't it? :-) That's OK, kib@ enlightened me (via IRC) that the issue is that I failed to enable NFSv4 ACLs on the FS. I had tried this, but somehow got an error, and then when I tried again I had the wrong ACL type (POSIX.1e). Steve -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (FreeBSD) iQEcBAEBAgAGBQJNc7mdAAoJEPXPYrMgexuhhZUIAId0nmh4YTJbjzv3NDmxXVt3 16ZIx+wOQON9Sln0vrpKIDJGk95KzvuLnbVBPg7Oxhaa11llkEeYFFqMEVWn6Esa hqwDe5yYJYWWyF7ulCmHDbAE2gEF5q2rVy0KrV+aI9x5DLeB607dpmZqVV6TeQky mQb1zOcw165galYhI3S4juPK6z5nq5pnTc+l05590CcAkWtxOFwQjlDZiQtrxdg2 YhFhtrMeGubRdKtJyG0r17kJzlGCBwIYBg7SgnmORVB64W0N0zkVcC+ZrIhioR6Z FoucxqelZ4VDt6IlmxZ3DzTNUGKWulCeCrus8+lDBPL1M92AfFgMF89i5n0Ot8Y= =302p -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: can somebody explains OFDM in FreeBSD?
On 06/03/11 11:31 AM, Etienne Robillard wrote: On 06/03/11 09:49 AM, Adrian Chadd wrote: OFDM is part of 11g, 11a, and 11n (2/5ghz.) I don't understand why you're asking about it in a security context. Adrian and finally I almost forgot... there seems to be another aspect of false security in OFDM design in what bi-directional IIP packets could be transfered out-of-band using ELF/VLF ranges and reverse FFT functions.. -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ACL issue (Was Re: HEADS UP: ZFSv28 is in!)
On Sun, Mar 06, 2011 at 11:06:09AM -0500, Steve Wills wrote:
On 03/06/11 10:37, Jeremy Chadwick wrote:
At first glance it looks like acl_set_fd_np(3) isn't working on an
md-backed filesystem; specifically, it's returning EOPNOTSUPP. You
should be able to reproduce the problem by doing a setfacl on something
in /tmp/foobar.
Looking through src/bin/cp/utils.c, this is the code:
420 if (acl_set_fd_np(dest_fd, acl, acl_type) 0) {
421 warn(failed to set acl entries for %s, to.p_path);
422 acl_free(acl);
423 return (1);
424 }
EOPNOTSUPP for acl_set_fd_np(3) is defined as:
[EOPNOTSUPP] The file system does not support ACL retrieval.
This would be referring to the destination filesystem.
Looking through the md(4) source for references to EOPNOTSUPP, we do
find some references:
$ egrep -n -r EOPNOTSUPP|ENOTSUP /usr/src/sys/dev/md
/usr/src/sys/dev/md/md.c:423: return (EOPNOTSUPP);
/usr/src/sys/dev/md/md.c:475: error = EOPNOTSUPP;
/usr/src/sys/dev/md/md.c:523: return (EOPNOTSUPP);
/usr/src/sys/dev/md/md.c:601: return (EOPNOTSUPP);
/usr/src/sys/dev/md/md.c:731: error = EOPNOTSUPP;
Line 423 is within mdstart_malloc(), and it returns EOPNOTSUPP on any
BIO operation other than READ/WRITE/DELETE. Line 475 is a continuation
of that.
Line 508 is within mdstart_vnode(), behaving effectively the same as
line 423. Line 601 is within mdstart_swap(), behaving effectively the
same as line 423.
Line 731 is within md_kthread(), and indicates only BIO operation
BIO_GETATTR is supported. This would not be an ACL attribute thing,
but rather getting attributes of the backing device itself. The code
hints at that:
722 if (bp-bio_cmd == BIO_GETATTR) {
723 if ((sc-fwsectors sc-fwheads
724 (g_handleattr_int(bp, GEOM::fwsectors,
725 sc-fwsectors) ||
726 g_handleattr_int(bp, GEOM::fwheads,
727 sc-fwheads))) ||
728 g_handleattr_int(bp, GEOM::candelete, 1))
729 error = -1;
730 else
731 error = EOPNOTSUPP;
732 } else {
Thanks for the investigation! So this seems to be a bug in md? That's
too bad, I was enjoying using it to make my tinderbox builds faster.
Sorry, I should have been more clear -- my investigation wasn't to
determine if the issue you're reporting was a bug or not, but more along
the lines of hmm, where is userland getting EOPNOTSUPP from in the
kernel in this situation? It could be that some piece hasn't been
implemented somewhere yet (more an incomplete than a bug :-) ).
I tend to trace source the way I did above in hopes that someone (kernel
dev, etc.) will chime in and go Oh, yes, THAT... let me tell you about
that! It's also for educational purposes; I figure sharing the innards
along with some simple descriptions might help people feel more
comfortable (vs. thinking everything is a black box; don't let the magic
smoke out!). Sometimes digging through the code helps.
This leaves me with some ideas; just tossing them out here...
1. Maybe/somehow this is caused by swap being used as the backing
type/store for md(4)? Try using mdconfig -t malloc -o reserve
instead, temporarily anyway.
Seems to be the same.
I'm not too surprised, but at least that rules out swap vs.
non-block-device stuff being somehow responsible.
I'm not a user of ACLs myself, but Robert Watson might know what's up
with this, or where to go looking. I've CC'd him here.
2. Are you absolutely 100% sure the kernel you're using was built
with options UFS_ACL defined in it? Doing a strings -a
/boot/kernel/kernel | grep UFS_ACL should suffice.
Yep, it does:
% strings -a /boot/kernel/kernel | grep UFS_ACL
options UFS_ACL
(My kernel config is just include GENERIC then a bunch of nooptions
for KDB, DDB, GDB, INVARIANTS, WITNESS, etc.)
Cool, good to rule out the obvious. Thanks.
The only other thing I can think of off the top of my head would be to
ktrace -t+ -i the cp -p, then provide output of kdump -s -t+ after.
I wouldn't say go about this quite yet (it may not even help determine
what's going on); maybe wait for Robert to take a look first.
--
| Jeremy Chadwick j...@parodius.com |
| Parodius Networking http://www.parodius.com/ |
| UNIX Systems Administrator Mountain View, CA, USA |
| Making life hard for others since 1977. PGP 4BD6C0CB |
___
freebsd-current@freebsd.org mailing list
Re: can somebody explains OFDM in FreeBSD?
On 06/03/11 11:46 AM, David Wolfskill wrote: On Sun, Mar 06, 2011 at 11:31:00AM -0500, Etienne Robillard wrote: On 06/03/11 09:49 AM, Adrian Chadd wrote: OFDM is part of 11g, 11a, and 11n (2/5ghz.) I don't understand why you're asking about it in a security context. Adrian Approaching security can be seen with onion paradigm: True paranoids will want to have multiple layers of security whether its physical or hardware related. In this case, one could ask reasonably whether its 'safe' to be close to a wireless router (802.11 ethernet-class) for a long-term period while OFDM is enabled at the transport level. Thanks, Etienne ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org As various folks have tried to point out to you: * OFDM is a modulation technique that all RF devices of certain types must not only support, but use, in order to work (as the specifications for their use require the use of OFDM). * As such, this has nothing to do with FreeBSD at all, and is therefore off-topic for thr FreeBSD.org technical mailing lists, of which freebsd-current@freebsd.org is one. A non-technical mailing list at FreeBSD.org is freebsd-c...@freebsd.org, in case you insist on carrying on this off-topic thread on a FreeBSD.org mailing list. In my opinion, however, you, as well as anyone interested in the topic, would be better served by moving the discussion to a venue for which it would be on-topic. I cannot identify such a venue for you, but readily confirm that there is no FreeBSD.org mailing list that satisfies the requirement. Finally, I am sending this note off-list because not only is the thread off-topic for the venue, but this message (in particlar) has nothing to do with FreeBSD, either. Please honor the reqwest to move the thread. Further attempts to post to a technical FreeBSD.org list on this thread will be treated as spam. Peace, david (current hat: postmas...@freebsd.org) hey this was kinda impolite and unecessary. Please don't disrupts the thread whenever you don't agree with and because you have authority! Thanks, Etienne -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ACL issue (Was Re: HEADS UP: ZFSv28 is in!)
On Sun, Mar 06, 2011 at 08:23:42AM -0800, Jeremy Chadwick wrote:
On Sun, Mar 06, 2011 at 11:06:09AM -0500, Steve Wills wrote:
On 03/06/11 10:37, Jeremy Chadwick wrote:
At first glance it looks like acl_set_fd_np(3) isn't working on an
md-backed filesystem; specifically, it's returning EOPNOTSUPP. You
should be able to reproduce the problem by doing a setfacl on something
in /tmp/foobar.
Looking through src/bin/cp/utils.c, this is the code:
420 if (acl_set_fd_np(dest_fd, acl, acl_type) 0) {
421 warn(failed to set acl entries for %s, to.p_path);
422 acl_free(acl);
423 return (1);
424 }
EOPNOTSUPP for acl_set_fd_np(3) is defined as:
[EOPNOTSUPP] The file system does not support ACL retrieval.
This would be referring to the destination filesystem.
Looking through the md(4) source for references to EOPNOTSUPP, we do
find some references:
$ egrep -n -r EOPNOTSUPP|ENOTSUP /usr/src/sys/dev/md
/usr/src/sys/dev/md/md.c:423: return (EOPNOTSUPP);
/usr/src/sys/dev/md/md.c:475: error = EOPNOTSUPP;
/usr/src/sys/dev/md/md.c:523: return (EOPNOTSUPP);
/usr/src/sys/dev/md/md.c:601: return (EOPNOTSUPP);
/usr/src/sys/dev/md/md.c:731: error =
EOPNOTSUPP;
Line 423 is within mdstart_malloc(), and it returns EOPNOTSUPP on any
BIO operation other than READ/WRITE/DELETE. Line 475 is a continuation
of that.
Line 508 is within mdstart_vnode(), behaving effectively the same as
line 423. Line 601 is within mdstart_swap(), behaving effectively the
same as line 423.
Line 731 is within md_kthread(), and indicates only BIO operation
BIO_GETATTR is supported. This would not be an ACL attribute thing,
but rather getting attributes of the backing device itself. The code
hints at that:
722 if (bp-bio_cmd == BIO_GETATTR) {
723 if ((sc-fwsectors sc-fwheads
724 (g_handleattr_int(bp, GEOM::fwsectors,
725 sc-fwsectors) ||
726 g_handleattr_int(bp, GEOM::fwheads,
727 sc-fwheads))) ||
728 g_handleattr_int(bp, GEOM::candelete,
1))
729 error = -1;
730 else
731 error = EOPNOTSUPP;
732 } else {
Thanks for the investigation! So this seems to be a bug in md? That's
too bad, I was enjoying using it to make my tinderbox builds faster.
Sorry, I should have been more clear -- my investigation wasn't to
determine if the issue you're reporting was a bug or not, but more along
the lines of hmm, where is userland getting EOPNOTSUPP from in the
kernel in this situation? It could be that some piece hasn't been
implemented somewhere yet (more an incomplete than a bug :-) ).
I tend to trace source the way I did above in hopes that someone (kernel
dev, etc.) will chime in and go Oh, yes, THAT... let me tell you about
that! It's also for educational purposes; I figure sharing the innards
along with some simple descriptions might help people feel more
comfortable (vs. thinking everything is a black box; don't let the magic
smoke out!). Sometimes digging through the code helps.
This leaves me with some ideas; just tossing them out here...
1. Maybe/somehow this is caused by swap being used as the backing
type/store for md(4)? Try using mdconfig -t malloc -o reserve
instead, temporarily anyway.
Seems to be the same.
I'm not too surprised, but at least that rules out swap vs.
non-block-device stuff being somehow responsible.
I'm not a user of ACLs myself, but Robert Watson might know what's up
with this, or where to go looking. I've CC'd him here.
2. Are you absolutely 100% sure the kernel you're using was built
with options UFS_ACL defined in it? Doing a strings -a
/boot/kernel/kernel | grep UFS_ACL should suffice.
Yep, it does:
% strings -a /boot/kernel/kernel | grep UFS_ACL
options UFS_ACL
(My kernel config is just include GENERIC then a bunch of nooptions
for KDB, DDB, GDB, INVARIANTS, WITNESS, etc.)
Cool, good to rule out the obvious. Thanks.
The only other thing I can think of off the top of my head would be to
ktrace -t+ -i the cp -p, then provide output of kdump -s -t+ after.
I wouldn't say go about this quite yet (it may not even help determine
what's going on); maybe wait for Robert to take a look first.
It would help if I actually added Robert to the CC list, wouldn't it?
:-)
--
| Jeremy Chadwick j...@parodius.com |
| Parodius Networking http://www.parodius.com/ |
|
Re: can somebody explains OFDM in FreeBSD?
On 06/03/11 11:58 AM, Hans Petter Selasky wrote: and finally I almost forgot... there seems to be another aspect of false security in OFDM design in what bi-directional IIP packets could be transfered out-of-band using ELF/VLF ranges and reverse FFT functions.. My point is that if you use, let's say software OFDM, then what leaks is then not important. Existing WLAN drivers can all be programmed for software OFDM probably by modifying a few lines of code. Is that what you want to say? --HPS yes, the difference with 'software OFDM' and hardware OFDM - as in run(4) - is the latter exploits 'objects' and 'peoples' as subcarriers units with bi-directional data when software OFDM could be used to securely convert the raw ELF/VLF energy input to a external server (the Power Server).. could then this not require a security advisory for hardware OFDM devices circulating in the wild to boost 802.11 'speeds' and 'ranges' ? Thanks, -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: can somebody explains OFDM in FreeBSD?
On Sunday 06 March 2011 18:19:31 Etienne Robillard wrote: On 06/03/11 11:58 AM, Hans Petter Selasky wrote: yes, the difference with 'software OFDM' and hardware OFDM - as in run(4) - is the latter exploits 'objects' and 'peoples' as subcarriers units with bi-directional data when software OFDM could be used to securely convert the raw ELF/VLF energy input to a external server (the Power Server).. could then this not require a security advisory for hardware OFDM devices circulating in the wild to boost 802.11 'speeds' and 'ranges' ? Hi Etienne, I think you are reading too much into too little and that further discussion into the details you suggest is not appropriate for this list. I believe that developers on the -current list are serious people, wanting to remove problems in this world rather than create them. Exploits are possible when the developers are not given enough time to research good solutions. Maybe you want to support FreeBSD developers by donating some money via the FreeBSD foundation, so that we can do a better job, removing your fears of software exploits in interaction with humans :-) --HPS BTW: Our slogan is The power to serve and not the power server :-) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: can somebody explains OFDM in FreeBSD?
On 06/03/11 12:36 PM, Hans Petter Selasky wrote: On Sunday 06 March 2011 18:19:31 Etienne Robillard wrote: On 06/03/11 11:58 AM, Hans Petter Selasky wrote: yes, the difference with 'software OFDM' and hardware OFDM - as in run(4) - is the latter exploits 'objects' and 'peoples' as subcarriers units with bi-directional data when software OFDM could be used to securely convert the raw ELF/VLF energy input to a external server (the Power Server).. could then this not require a security advisory for hardware OFDM devices circulating in the wild to boost 802.11 'speeds' and 'ranges' ? Hi Etienne, I think you are reading too much into too little and that further discussion into the details you suggest is not appropriate for this list. I believe that developers on the -current list are serious people, wanting to remove problems in this world rather than create them. Exploits are possible when the developers are not given enough time to research good solutions. Maybe you want to support FreeBSD developers by donating some money via the FreeBSD foundation, so that we can do a better job, removing your fears of software exploits in interaction with humans :-) --HPS BTW: Our slogan is The power to serve and not the power server :-) you must be kidding? this kind of security exploits should be not regarded as friendly. However I'd like to see a FreeBSD based OFDM kernel to allow conveying ELF/VLF input stream to things like 'electricity'... Freebsd: the power to serve the world with free electricity! Isn't that ironic? ;-) -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ACL issue (Was Re: HEADS UP: ZFSv28 is in!)
Wiadomość napisana przez Steve Wills w dniu 2011-03-06, o godz. 15:43: On 03/06/11 08:35, Steve Wills wrote: On 03/06/11 04:22, Edward Tomasz NapieraBa wrote: Wiadomo[ napisana przez Steve Wills w dniu 2011-03-06, o godz. 05:11: [..] Thanks for your work on this, I'm very happy to have ZFS v28. I just updated my -CURRENT system from a snapshot from about a month ago to code from today. I have 3 pools and one of them is for ports tinderbox. I only upgraded that pool. When I try to build something using tinderbox, I get this error: cp: failed to set acl entries for /usr/local/tinderbox/9-CURRENT-amd64-FreeBSD/buildscript: Operation not supported What does mount show? /dev/md4 12186190 332724 11853466 3% /usr/local/tinderbox/9-CURRENT-amd64-FreeBSD Sorry, I forgot about the mdmfs hacks I had in my local tinderd. Without them, it works fine. So the problem seems to be in mfs rather than zfs. I should have said mdmfs, but all that's doing is running mdconfig and newfs for me. I've reproduced the issue without mdmfs: % mdconfig -a -t swap -s 12G -u 4 % newfs -m 0 -o time /dev/md4 [...] % mount /dev/md4 /tmp/foobar % cp -p /usr/local/tinderbox/scripts/lib/buildscript /tmp/foobar cp: failed to set acl entries for /tmp/foobar/buildscript: Operation not supported Without -p it works fine. FWIW: % getfacl /usr/local/tinderbox/scripts/lib/buildscript # file: /usr/local/tinderbox/scripts/lib/buildscript # owner: root # group: wheel owner@:--:--:deny owner@:rwxp---A-W-Co-:--:allow group@:-w-p--:--:deny group@:r-x---:--:allow everyone@:-w-p---A-W-Co-:--:deny everyone@:r-x---a-R-c--s:--:allow Any suggestions on where the problem could be? The above looks like old-style, canonical six trivial ACL. Now, cp(1) shouldn't even try to copy the ACL in this case, since there is nothing to copy. So, for some reason, something failed between cp(1), acl_is_trivial_np(3) and the kernel. What does ls -al /usr/local/tinderbox/scripts/lib/buildscript show? -- If you cut off my head, what would I say? Me and my head, or me and my body? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: please (re) test if_ath in -HEAD
2011/3/6 Ian FREISLICH i...@clue.co.za: Adrian Chadd wrote: Hi all, For those of you who are testing out my if_ath changes, I'd really appreciate it if you'd update to -HEAD and re-test. Since running the new code, I get a slew of these: Mar 6 14:41:53 mini wpa_supplicant[422]: Trying to associate with 00:30:4f:58:bf:94 (SSID='quasar' freq=2437 MHz) Mar 6 14:41:53 mini wpa_supplicant[422]: Associated with 00:30:4f:58:bf:94 Mar 6 14:41:53 mini kernel: wlan0: link state changed to UP Mar 6 14:41:54 mini wpa_supplicant[422]: WPA: Key negotiation completed with 00:30:4f:58:bf:94 [PTK=TKIP GTK=TKIP] Mar 6 14:41:54 mini wpa_supplicant[422]: CTRL-EVENT-CONNECTED - Connection to 00:30:4f:58:bf:94 completed (reauth) [id=7 id_str=] Mar 6 14:46:59 mini wpa_supplicant[422]: CTRL-EVENT-DISCONNECTED bssid=00:30:4f:58:bf:94 reason=0 Mar 6 14:46:59 mini kernel: wlan0: link state changed to DOWN Mar 6 14:47:02 mini wpa_supplicant[422]: Trying to associate with 00:30:4f:58:bf:94 (SSID='quasar' freq=2437 MHz) Mar 6 14:47:02 mini wpa_supplicant[422]: Associated with 00:30:4f:58:bf:94 Mar 6 14:47:02 mini kernel: wlan0: link state changed to UP Mar 6 14:47:03 mini wpa_supplicant[422]: WPA: Key negotiation completed with 00:30:4f:58:bf:94 [PTK=TKIP GTK=TKIP] Mar 6 14:47:03 mini wpa_supplicant[422]: CTRL-EVENT-CONNECTED - Connection to 00:30:4f:58:bf:94 completed (reauth) [id=7 id_str=] Mar 6 14:49:31 mini ntpd[1848]: kernel time sync status change 2001 Mar 6 14:56:53 mini wpa_supplicant[422]: CTRL-EVENT-DISCONNECTED bssid=00:30:4f:58:bf:94 reason=0 Mar 6 14:56:53 mini kernel: wlan0: link state changed to DOWN Mar 6 14:56:56 mini wpa_supplicant[422]: Trying to associate with 00:30:4f:58:bf:94 (SSID='quasar' freq=2437 MHz) Mar 6 14:56:56 mini wpa_supplicant[422]: Associated with 00:30:4f:58:bf:94 Mar 6 14:56:56 mini kernel: wlan0: link state changed to UP Mar 6 14:56:57 mini wpa_supplicant[422]: WPA: Key negotiation completed with 00:30:4f:58:bf:94 [PTK=TKIP GTK=TKIP] Mar 6 14:56:57 mini wpa_supplicant[422]: CTRL-EVENT-CONNECTED - Connection to 00:30:4f:58:bf:94 completed (reauth) [id=7 id_str=] Mar 6 16:18:28 mini kernel: ath0: bb hang detected (0x80), resetting fyi; same issue. My hardware is: ath0@pci0:1:0:0: class=0x028000 card=0x7167144f chip=0x002b168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'Atheros AR9285 Wireless LAN 802.11 a/b/g/n Controller (AR928x)' class = network same card. It's also only able to maintain an 18-24Mbps connection, where before I had stable 54Mbps. Ian -- Ian Freislich sorry, but i have no stable versions with me. it's a fresh and new freebsd install into an asus eeepc 1005pe (running 9current, clang compiled). later i will spend some time with real tests. unfortunately i'm not at home right now.. and running a gentoo based o.s. btw, ty for your work, chadd. ['s] -- Vinícius Zavam profiles.google.com/egypcio ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
OFDM kernel (Re: can somebody explains OFDM in FreeBSD?)
On 06/03/11 12:46 PM, Etienne Robillard wrote: On 06/03/11 12:36 PM, Hans Petter Selasky wrote: On Sunday 06 March 2011 18:19:31 Etienne Robillard wrote: On 06/03/11 11:58 AM, Hans Petter Selasky wrote: yes, the difference with 'software OFDM' and hardware OFDM - as in run(4) - is the latter exploits 'objects' and 'peoples' as subcarriers units with bi-directional data when software OFDM could be used to securely convert the raw ELF/VLF energy input to a external server (the Power Server).. could then this not require a security advisory for hardware OFDM devices circulating in the wild to boost 802.11 'speeds' and 'ranges' ? Hi Etienne, I think you are reading too much into too little and that further discussion into the details you suggest is not appropriate for this list. I believe that developers on the -current list are serious people, wanting to remove problems in this world rather than create them. Exploits are possible when the developers are not given enough time to research good solutions. Maybe you want to support FreeBSD developers by donating some money via the FreeBSD foundation, so that we can do a better job, removing your fears of software exploits in interaction with humans :-) --HPS BTW: Our slogan is The power to serve and not the power server :-) you must be kidding? this kind of security exploits should be not regarded as friendly. However I'd like to see a FreeBSD based OFDM kernel to allow conveying ELF/VLF input stream to things like 'electricity'... Freebsd: the power to serve the world with free electricity! Isn't that ironic? ;-) The more I let myself thinking about this possibility the more obvious it becomes. Sure I would like to see this project adopted by the FreeBSD foundation so that it becomes officialy supported in FreeBSD! :-) Any takers? Best, -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ACL issue (Was Re: HEADS UP: ZFSv28 is in!)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/06/11 12:49, Edward Tomasz Napierała wrote: The above looks like old-style, canonical six trivial ACL. Now, cp(1) shouldn't even try to copy the ACL in this case, since there is nothing to copy. So, for some reason, something failed between cp(1), acl_is_trivial_np(3) and the kernel. What does ls -al /usr/local/tinderbox/scripts/lib/buildscript show? It looks like: - -rwxr-xr-x+ 1 root wheel 12547 Feb 1 21:21 /usr/local/tinderbox/scripts/lib/buildscript Steve -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.16 (FreeBSD) iQEcBAEBAgAGBQJNc9IMAAoJEPXPYrMgexuhMmQH/jU7Zsay7fDmYP4UY60P63TH Zbq3jyitlhgh3BNyibbbJ3O0OsEUWEJ+xO5jz04g32Kvv/NFWqQD9tPygkABeBb2 v50K/uOS8VskcMoJaxzkOIDz2Y/0PNKHo+/Cft7/hMbW1W5h7ebe7peKn7FA/F6R MzFY6RMe6sY4x00gxpo/f3DQAB5VR6MqQl5SbDMUE8dP7ut5gUe9f+QvJPc2OgMA thCLqxEfjKohWtpmuctr1c8Ap3UKvAAzwUVT6qs+CNidaxb3qzXLDyA9Z614GVAy 1WQxTsEtfiByMm6N1qUqIkNZNFmFSO0cEuRyK8Z4FJ0ZA5X4smk8gicATp/wAPQ= =Y/S+ -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Introduce myself and question about getting CURRENT
On Mar 5, 2011, at 4:16 PM, Nerius Landys wrote: Anyhow, first things are first. I need to get CURRENT. So, what is the preferred way to get CURRENT on your system? As mentioned, there are a lot of variations. Personally, I bootstrap current systems by installing a minimal STABLE distribution first (today, that's 8.2) from the CD. Then use SVN to checkout the CURRENT sources to /usr/src. Then following the instructions in /usr/src/UPGRADING. The trickiest issue is whether you want to build any additional ports before or after you upgrade. That basically depends on whether you want to debug FreeBSD or debug ports. ;-) Tim ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: please (re) test if_ath in -HEAD
Adrian Chadd wrote: I'd like to establish at least a range of subversion revisions so we can start binary searching which one(s) caused instabilities. Is this all the source? Old: $FreeBSD: src/sys/dev/ath/if_ath.c,v 1.300 2011/02/21 19:22:45 adrian Exp $ $FreeBSD: src/sys/dev/ath/if_ath_debug.c,v 1.1 2011/01/29 05:08:21 adrian Exp $ $FreeBSD: src/sys/dev/ath/if_ath_tx.c,v 1.6 2011/02/22 00:37:53 adrian Exp $ $FreeBSD: src/sys/dev/ath/if_ath_tx_ht.c,v 1.9 2011/02/22 04:41:04 adrian Exp $ $FreeBSD: src/sys/dev/ath/if_ath_pci.c,v 1.25 2009/05/15 17:02:11 imp Exp $ $FreeBSD: src/sys/dev/ath/ath_rate/sample/sample.c,v 1.35 2011/02/17 05:16:59 adrian Exp $ $FreeBSD: src/sys/dev/ath/ath_rate/sample/tx_schedules.h,v 1.1 2011/01/28 08:57:58 adrian Exp $ $FreeBSD: src/sys/dev/usb/wlan/if_uath.c,v 1.23 2010/09/02 03:28:03 thompsa Exp $ New: $FreeBSD: src/sys/dev/ath/if_ath.c,v 1.302 2011/03/02 17:19:54 adrian Exp $ $FreeBSD: src/sys/dev/ath/if_ath_debug.c,v 1.1 2011/01/29 05:08:21 adrian Exp $ $FreeBSD: src/sys/dev/ath/if_ath_keycache.c,v 1.1 2011/03/02 17:19:54 adrian Exp $ $FreeBSD: src/sys/dev/ath/if_ath_tx.c,v 1.6 2011/02/22 00:37:53 adrian Exp $ $FreeBSD: src/sys/dev/ath/if_ath_tx_ht.c,v 1.10 2011/03/03 03:02:06 adrian Exp $ $FreeBSD: src/sys/dev/ath/if_ath_sysctl.c,v 1.1 2011/03/02 16:03:19 adrian Exp $ $FreeBSD: src/sys/dev/ath/if_ath_pci.c,v 1.25 2009/05/15 17:02:11 imp Exp $ $FreeBSD: src/sys/dev/ath/ath_rate/sample/sample.c,v 1.37 2011/03/03 20:41:59 adrian Exp $ $FreeBSD: src/sys/dev/ath/ath_rate/sample/tx_schedules.h,v 1.1 2011/01/28 08:57:58 adrian Exp $ $FreeBSD: src/sys/dev/usb/wlan/if_uath.c,v 1.23 2010/09/02 03:28:03 thompsa Exp $ Ian -- Ian Freislich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: please (re) test if_ath in -HEAD
On 7 March 2011 03:21, Ian FREISLICH i...@clue.co.za wrote: Adrian Chadd wrote: I'd like to establish at least a range of subversion revisions so we can start binary searching which one(s) caused instabilities. Is this all the source? Old: $FreeBSD: src/sys/dev/ath/if_ath.c,v 1.300 2011/02/21 19:22:45 adrian Exp $ New: $FreeBSD: src/sys/dev/ath/if_ath.c,v 1.302 2011/03/02 17:19:54 adrian Exp $ Ok, so between r219318 (today) and r218779 (2011-02-18). Would you please first test r218779 and verify that performance is (back to) fine? Thanks, Adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: ACL issue (Was Re: HEADS UP: ZFSv28 is in!)
Wiadomość napisana przez Steve Wills w dniu 2011-03-06, o godz. 19:27: On 03/06/11 12:49, Edward Tomasz Napierała wrote: The above looks like old-style, canonical six trivial ACL. Now, cp(1) shouldn't even try to copy the ACL in this case, since there is nothing to copy. So, for some reason, something failed between cp(1), acl_is_trivial_np(3) and the kernel. What does ls -al /usr/local/tinderbox/scripts/lib/buildscript show? It looks like: - -rwxr-xr-x+ 1 root wheel 12547 Feb 1 21:21 /usr/local/tinderbox/scripts/lib/buildscript r219272 introduced an error which made libc treat the canonical six ACLs as nontrivial. I backed it out; you need to rebuild libc. Sorry. -- If you cut off my head, what would I say? Me and my head, or me and my body? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: can somebody explains OFDM in FreeBSD?
On 06/03/11 12:36 PM, Hans Petter Selasky wrote: On Sunday 06 March 2011 18:19:31 Etienne Robillard wrote: On 06/03/11 11:58 AM, Hans Petter Selasky wrote: yes, the difference with 'software OFDM' and hardware OFDM - as in run(4) - is the latter exploits 'objects' and 'peoples' as subcarriers units with bi-directional data when software OFDM could be used to securely convert the raw ELF/VLF energy input to a external server (the Power Server).. could then this not require a security advisory for hardware OFDM devices circulating in the wild to boost 802.11 'speeds' and 'ranges' ? Hi Etienne, I think you are reading too much into too little and that further discussion into the details you suggest is not appropriate for this list. I believe that developers on the -current list are serious people, wanting to remove problems in this world rather than create them. Exploits are possible when the developers are not given enough time to research good solutions. Maybe you want to support FreeBSD developers by donating some money via the FreeBSD foundation, so that we can do a better job, removing your fears of software exploits in interaction with humans :-) --HPS BTW: Our slogan is The power to serve and not the power server :-) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org X-UID: 11883 Status: X-Keywords: Content-Length: 0 I've put a wiki page for anyone interested in the topic of building a OFDM-based kernel here: https://gthc.org/wiki/FreeBSD/OFDM_Kernel and I still think hardware OFDM is inherently insecure as-is in FreeBSD even if not everyone seems to agree or willing to debate the idea with strong arguments to prove the contrary. -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: can somebody explains OFDM in FreeBSD?
FreeBSD doesn't implement OFDM in the kernel. The various chipsets implement OFDM, not FreeBSD. There's no software OFDM. The 802.11 chipsets out there take care of it, not FreeBSD. Adrian On 7 March 2011 04:42, Etienne Robillard e...@gthcfoundation.org wrote: On 06/03/11 12:36 PM, Hans Petter Selasky wrote: On Sunday 06 March 2011 18:19:31 Etienne Robillard wrote: On 06/03/11 11:58 AM, Hans Petter Selasky wrote: yes, the difference with 'software OFDM' and hardware OFDM - as in run(4) - is the latter exploits 'objects' and 'peoples' as subcarriers units with bi-directional data when software OFDM could be used to securely convert the raw ELF/VLF energy input to a external server (the Power Server).. could then this not require a security advisory for hardware OFDM devices circulating in the wild to boost 802.11 'speeds' and 'ranges' ? Hi Etienne, I think you are reading too much into too little and that further discussion into the details you suggest is not appropriate for this list. I believe that developers on the -current list are serious people, wanting to remove problems in this world rather than create them. Exploits are possible when the developers are not given enough time to research good solutions. Maybe you want to support FreeBSD developers by donating some money via the FreeBSD foundation, so that we can do a better job, removing your fears of software exploits in interaction with humans :-) --HPS BTW: Our slogan is The power to serve and not the power server :-) ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org X-UID: 11883 Status: X-Keywords: Content-Length: 0 I've put a wiki page for anyone interested in the topic of building a OFDM-based kernel here: https://gthc.org/wiki/FreeBSD/OFDM_Kernel and I still think hardware OFDM is inherently insecure as-is in FreeBSD even if not everyone seems to agree or willing to debate the idea with strong arguments to prove the contrary. -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
missing files in readdir(3) on NFS export of ZFS volume (since v28?)
Hello, I'm running a 9-current server as compiled on Sat Mar 5 02:17:14 CET 2011. Since I upgraded to ZFS v28 I noticed missing files from NFS. The files are still accessible through NFS but they don't show up on a readdir(3). On the NFS server (files are stored on a ZFS v15 volume, not yet upgraded to the v28 format): % cd /usr/ports/devel/autoconf % ls -i 311401 Makefile 204505 files204509 pkg-plist 204504 distinfo 204508 pkg-descr On the NFS client side (FreeBSD 8.2-RELEASE): % cd /usr/ports/devel/autoconf % ls -i 204504 distinfo 204508 pkg-descr 204505 files204509 pkg-plist Yet the missing file can be accessed: % head -3 Makefile # New ports collection makefile for:autoconf # Date created: 7th December 2006 # Whom: a...@freebsd.org Note that the missing files are scattered throughout the volume, no relation to the inode number, as shown on a diff: @@ -1,8 +1,6 @@ 37 drwxr-xr-x 70 pb staff 93 4 mar 19:11 /usr/ports - 42 -rw-r--r--1 pb staff 241 24 jan 2007 /usr/ports/astro/tclgeomap/pkg-plist 53 drwxr-xr-x2 pb staff 6 22 fév 12:04 /usr/ports/astro/tkgeomap 63 drwxr-xr-x4 pb staff 6 29 jul 2008 /usr/ports/Tools - 75 drwxr-xr-x 33 pb staff 34 25 nov 15:59 /usr/ports/accessibility 83 drwxr-xr-x 12 pb staff 14 9 fév 2009 /usr/ports/arabic 11 51 drwxr-xr-x 900 pb staff 901 6 mar 14:36 /usr/ports/audio 123 -rw-r--r--1 pb staff 584 25 aoû 2006 /usr/ports/astro/tkgeomap/pkg-descr @@ -16,10 +14,8 @@ 233 drwxr-xr-x3 pb staff 7 24 mar 2010 /usr/ports/astro/wcslib 244 -rw-r--r--1 pb staff1414 5 jan 2010 /usr/ports/astro/wcslib/Makefile 255 drwxr-xr-x 31 pb staff 33 1 jan 23:16 /usr/ports/french -262 -rw-r--r--1 pb staff 197 5 jan 2010 /usr/ports/astro/wcslib/distinfo 27 63 drwxr-xr-x 1110 pb staff 23 fév 15:37 /usr/ports/games 283 drwxr-xr-x2 pb staff 4 24 mar 2010 /usr/ports/astro/wcslib/files -292 -rw-r--r--1 pb staff 236 5 jan 2010 /usr/ports/astro/wcslib/files/6-patch-configure 303 -rw-r--r--1 pb staff 677 5 jan 2010 /usr/ports/astro/wcslib/files/patch-GNUmakefile 312 -rw-r--r--1 pb staff 401 17 jul 2009 /usr/ports/astro/wcslib/pkg-descr 324 -rw-r--r--1 pb staff1515 5 jan 2010 /usr/ports/astro/wcslib/pkg-plist ... Reverting to an old 9-current kernel (January 10, before the ZFS v28 patches) fixes the problem... -- Sent from my FreeBSD server Pierre Beyssac p...@fasterix.frmug.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: please (re) test if_ath in -HEAD
On 7 March 2011 07:27, daren dare...@daelive.com wrote: On Thu, 2011-03-03 at 14:31 -0800, Adrian Chadd wrote: Hi all, For those of you who are testing out my if_ath changes, I'd really appreciate it if you'd update to -HEAD and re-test. I've done a variety of changes to the radio setup and found/fixed a few bugs in the TX path. It's quite possible these have introduced regressions. I'd like to make sure that I haven't broken legacy (11abg) support in weird/wonderful ways. I'd also like to make sure that I haven't broken/changed the behaviour or performance of the NICs in any way. Please give things a good thrashing and let me know the results. I'm still working towards debugging and enabling basic 11n support, but I need to first make sure that I haven't broken legacy operation in any way. Do these changes support the AR2427? On Mon, 2011-03-07 at 08:07 +0800, Adrian Chadd wrote: The AR2427 support in HEAD is still unstable. I'm just fleshing out the AR9280 support and finding/fixing regressions that have been introduced before I continue fixing up the AR9285/AR2427 support. Basically, 11g modes on the AR2427 start off fine but they stop being successfully TXed after a few hours. Maybe if you run it in 11b only mode it'll be stable enough for use. I do have an AR2427 in a laptop here so I can actually test it. :) adrian Ok great, thanks. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[head tinderbox] failure on ia64/ia64
TB --- 2011-03-07 00:25:55 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-03-07 00:25:55 - starting HEAD tinderbox run for ia64/ia64 TB --- 2011-03-07 00:25:55 - cleaning the object tree TB --- 2011-03-07 00:26:06 - cvsupping the source tree TB --- 2011-03-07 00:26:06 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/ia64/ia64/supfile TB --- 2011-03-07 00:26:19 - building world TB --- 2011-03-07 00:26:19 - MAKEOBJDIRPREFIX=/obj TB --- 2011-03-07 00:26:19 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-03-07 00:26:19 - TARGET=ia64 TB --- 2011-03-07 00:26:19 - TARGET_ARCH=ia64 TB --- 2011-03-07 00:26:19 - TZ=UTC TB --- 2011-03-07 00:26:19 - __MAKE_CONF=/dev/null TB --- 2011-03-07 00:26:19 - cd /src TB --- 2011-03-07 00:26:19 - /usr/bin/make -B buildworld World build started on Mon Mar 7 00:26:20 UTC 2011 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies [...] mkdep -f .depend -a /src/sbin/growfs/growfs.c echo growfs: /obj/ia64.ia64/src/tmp/usr/lib/libc.a .depend === sbin/gvinum (depend) rm -f .depend mkdep -f .depend -a-I/src/sbin/gvinum/../../sys /src/sbin/gvinum/gvinum.c /src/sbin/gvinum/../../sys/geom/vinum/geom_vinum_share.c echo gvinum: /obj/ia64.ia64/src/tmp/usr/lib/libc.a /obj/ia64.ia64/src/tmp/usr/lib/libreadline.a /obj/ia64.ia64/src/tmp/usr/lib/libtermcap.a /obj/ia64.ia64/src/tmp/usr/lib/libdevstat.a /obj/ia64.ia64/src/tmp/usr/lib/libkvm.a /obj/ia64.ia64/src/tmp/usr/lib/libgeom.a .depend === sbin/hastctl (depend) make: don't know how to make hast_compression.c. Stop *** Error code 2 Stop in /src/sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2011-03-07 01:06:11 - WARNING: /usr/bin/make returned exit code 1 TB --- 2011-03-07 01:06:11 - ERROR: failed to build world TB --- 2011-03-07 01:06:11 - 1863.11 user 381.72 system 2416.12 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-ia64-ia64.full ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Request: AR9285 EEPROM dumps (was Re: More if_ath churn coming your way!)
Which version of the driver are you using? Adrian 2011/3/7 Vinícius Zavam egyp...@googlemail.com 2011/1/23 Adrian Chadd adrian.ch...@gmail.com: You'll have to compile in the diag api. Just add these: options ATH_DIAGAPI Adrian 2011/1/23 Dima Panov flu...@fluffy.khv.ru: Hello! 23.01.2011, 09:47, Adrian Chadd adrian.ch...@gmail.com: Hi all, I've just committed a new tool in src/tools/tools/ath/ called ath_prom_dump . It dumps the contents of the atheros EEPROM into a text file for later analysis. I don't have any AR9285's handy; if you have an AR9285, would you please send me a hexdump of the EEPROM along with the contents of pciconf and dmesg | grep ath (so I can get the MAC/PHY version numbers?) You meant ath_prom_read? [root@Beastie] ~# ath_prom_read -h ath_prom_read: illegal option -- h ath_prom_read [-i ifname] -d dumpfile [root@Beastie] ~# ath_prom_read -d ar9285 ath_prom_read: ath0: Invalid argument [root@Beastie] ~# FreeBSD 9.0-900030-CURRENT #0 r217695M: Sat Jan 22 13:57:57 VLAT 2011 -- Dima Panov (flu...@freebsd.org) _AR9285.txt = associated ath0: bb hang detected (0x80), resetting -- Vinícius Zavam profiles.google.com/egypcio ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [head tinderbox] failure on ia64/ia64
On Mon, Mar 07, 2011 at 01:06:11AM +, FreeBSD Tinderbox wrote: TB --- 2011-03-07 00:25:55 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2011-03-07 00:25:55 - starting HEAD tinderbox run for ia64/ia64 TB --- 2011-03-07 00:25:55 - cleaning the object tree TB --- 2011-03-07 00:26:06 - cvsupping the source tree TB --- 2011-03-07 00:26:06 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/ia64/ia64/supfile TB --- 2011-03-07 00:26:19 - building world TB --- 2011-03-07 00:26:19 - MAKEOBJDIRPREFIX=/obj TB --- 2011-03-07 00:26:19 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2011-03-07 00:26:19 - TARGET=ia64 TB --- 2011-03-07 00:26:19 - TARGET_ARCH=ia64 TB --- 2011-03-07 00:26:19 - TZ=UTC TB --- 2011-03-07 00:26:19 - __MAKE_CONF=/dev/null TB --- 2011-03-07 00:26:19 - cd /src TB --- 2011-03-07 00:26:19 - /usr/bin/make -B buildworld World build started on Mon Mar 7 00:26:20 UTC 2011 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies [...] mkdep -f .depend -a /src/sbin/growfs/growfs.c echo growfs: /obj/ia64.ia64/src/tmp/usr/lib/libc.a .depend === sbin/gvinum (depend) rm -f .depend mkdep -f .depend -a-I/src/sbin/gvinum/../../sys /src/sbin/gvinum/gvinum.c /src/sbin/gvinum/../../sys/geom/vinum/geom_vinum_share.c echo gvinum: /obj/ia64.ia64/src/tmp/usr/lib/libc.a /obj/ia64.ia64/src/tmp/usr/lib/libreadline.a /obj/ia64.ia64/src/tmp/usr/lib/libtermcap.a /obj/ia64.ia64/src/tmp/usr/lib/libdevstat.a /obj/ia64.ia64/src/tmp/usr/lib/libkvm.a /obj/ia64.ia64/src/tmp/usr/lib/libgeom.a .depend === sbin/hastctl (depend) make: don't know how to make hast_compression.c. Stop *** Error code 2 Interesting race. hast_compression.c was added in the same commit it was added to hastctl Makefile. -- Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://yomoli.com pgpFDhVqWe1wK.pgp Description: PGP signature
