Re: openssl version - how to verify
On Tue, Nov 16, 2010 at 1:28 AM, c0re nr1c...@gmail.com wrote: Jerry, I'm not about that :) base openssl are OK. But I need proves that it has got no security problems - it's external IT auditors request. And I'm interested how I can know what patchlevel there on base openssl version and prove them (auditors) that freebsd base openssl are not vulnerable. Please don't top-post, thanks. http://security.freebsd.org/advisories/ The files say which version it's corrected in. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: openssl version - how to verify
2010/11/16 Adam Vande More amvandem...@gmail.com: On Tue, Nov 16, 2010 at 1:28 AM, c0re nr1c...@gmail.com wrote: Jerry, I'm not about that :) base openssl are OK. But I need proves that it has got no security problems - it's external IT auditors request. And I'm interested how I can know what patchlevel there on base openssl version and prove them (auditors) that freebsd base openssl are not vulnerable. Please don't top-post, thanks. Sorry. Wont will in future. But why? http://security.freebsd.org/advisories/ The files say which version it's corrected in. -- Adam Vande More Thanks, it's better then nothing :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: openssl version - how to verify
On Tue, Nov 16, 2010 at 9:49 AM, c0re nr1c...@gmail.com wrote: 2010/11/16 Adam Vande More amvandem...@gmail.com: Please don't top-post, thanks. Sorry. Wont will in future. But why? Because it messes up the flow of reading. I prefer to bottom-post. How come? What do you do instead? No. Do you like top-posting? -- chs, ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: History of C (Re: Why do you use a devil as a mascot?)
Wojciech Puchar woj...@tensor.gdynia.pl wrote: there will no no next language. there is no need to have C follower. C is perfect Which C are you referring to here? The original KR, ANSI, or some other variant? ANSI C is different enough from KR C -- in strength of typing if nothing else -- that some would say ANSI C _is_ the next language following KR C. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: History of C (Re: Why do you use a devil as a mascot?)
per...@pluto.rain.com wrote: Wojciech Puchar woj...@tensor.gdynia.pl wrote: there will no no next language. there is no need to have C follower. C is perfect Which C are you referring to here? The original KR, ANSI, or some other variant? ANSI C is different enough from KR C -- in strength of typing if nothing else -- that some would say ANSI C _is_ the next language following KR C. Chat about flavours of C, better on chat@ not questi...@. ( The daemons noise was enough old FAQ ) http://www.freebsd.org/doc/en_US.ISO8859-1/articles/freebsd-questions/x92.html Before submitting a question You can (and should) do some things yourself before asking a question on one of the mailing lists: http://www.freebsd.org/search/search.html#mailinglists Chat: Random topics (sometimes) related to FreeBSD. Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail plain text; Not HTML, quoted-printable base 64 spam formats. Avoid top posting, it cripples itemised cumulative responses. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 'Broadcom Wireless b/g (BCM4315/BCM22062000)'
I have the following card: siba_b...@pci0:12:0:0: class=0x028000 card=0x000c1028 chip=0x431514e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' class = network And it doesn't work with bwn driver (perhaps that's a configuration issue though) on 8.1. On Tue, Nov 16, 2010 at 7:17 AM, b. f. bf1...@googlemail.com wrote: Chris Brennan wrote: ... My Hiccup as the subject suggests is about my Wireless Card. I have been following the handbook ( http://www.freebsd.org/doc/handbook/config-network-setup.html) on how to use 64-bit Windows drivers coupled w/ ndisgen to get my wireless card working. I got ndisgen to generate a kernel module but it immediately caused my laptop to reboot when the kernel was loaded. This left me scratching my head. I think I might need firmware (I remember having to extract firmware from the driver for linux). pciconf shows the following: [root at BlackDragon [~]# pciconf -lv | grep -A3 0x4315 none8 at pci0:8:0:0: class=0x028000 card=0x137c103c chip=0x431514e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' class = network [root at BlackDragon [~]# The laptop is an HP dv2845SE and it's running FreebSD64-8.1. Let me know if I missed anything. I'm assuming that by FreebSD64, you mean the amd64 version of FreeBSD. Have you tried using a recent version of the native bwn(4) driver, together with the net/bwn-firmware-kmod port, rather than ndis(4)? b. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [freebsd] pecl-imagick - Segmentation fault: 11 (core dumped) on php -i under freebsd 7.3
Le 12 nov. 2010 à 01:04, Olivier Mueller a écrit : Good evening, On Tue, 2010-06-22 at 10:45 +0200, Olivier Mueller wrote: Problem: [...@pandora ~]$ php -v -c /usr/local/etc/php.ini-production PHP 5.3.2 with Suhosin-Patch (cli) (built: Jun 14 2010 18:11:48) Copyright (c) 1997-2009 The PHP Group Zend Engine v2.3.0, Copyright (c) 1998-2010 Zend Technologies Segmentation fault: 11 (core dumped) Here's what did it for me : remove the following lines from /usr/ports/textproc/libxml2/files/patch-configure and rebuild+reinstall libxml2 @@ -20678,6 +20679,8 @@ fi fi fi ;; + *freebsd*) THREAD_LIBS= + ;; esac if test $WITH_THREADS = 1 ; then THREAD_CFLAGS=$THREAD_CFLAGS -D_REENTRANT I found this somewhere but cannot remember the thread url unfortunately... NZ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [solved] Re: [freebsd] pecl-imagick - Segmentation fault: 11 (core dumped) on php -i under freebsd 7.3
Olivier Mueller ha scritto: Brillant! It fixed the issue, many thanks. This is not the correct fix, the correct fix is to enable threads in php, using the appropriate OPTION. -- Alex Dupre ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS and 4k sector drives
On 11/15/10 20:24, Wojciech Puchar wrote: work with ZFS raidz2 pools. It seems that most of the 4k sector drives are using emulation, and reporting 512 byte sectors to the OS instead of their native 4k size. I know someone who had an issue trying to insert one of these drives into a running ZFS pool with other 512 byte sector drives with bad results. ZFS use 4k blocks. Actually, no, it's much worse: ZFS uses variable block size upto 128 KiB, meaning not only does it not write or align data on a sensible boundary like 4 KiB, both its metadata and data IO can write on any offset and length which is a multiple of 512 bytes. References: http://www.solarismen.de/archives/5-Solaris-and-the-new-4K-Sector-Disks-e.g.-WDxxEARS-Part-2.html http://permalink.gmane.org/gmane.os.freebsd.devel.geom/4318 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
*default release=cvs tag=RELENG_8 in both standard-supfile and stable-supfile
I was wondering why both the stable standard supfiles on FreeBSD-8.1 / amd64 both have the exact release tag: *default release=cvs tag=RELENG_8 Shouldn't they be different? What would be the correct tab for each supfile respectively? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: *default release=cvs tag=RELENG_8 in both standard-supfile and stable-supfile
On Tue, Nov 16, 2010 at 01:09:30PM -0500, pigskinwhite...@icqmail.com thus spake: I was wondering why both the stable standard supfiles on FreeBSD-8.1 / amd64 both have the exact release tag: *default release=cvs tag=RELENG_8 From: http://www.freebsd.org/doc/handbook/cvs-tags.html RELENG_8 The line of development for FreeBSD-8.X, also known as FreeBSD 8-STABLE Shouldn't they be different? What would be the correct tab for each supfile respectively? Since 8.0 and 8.1 fall under 8.x, I would think this is by design according to the documentation. -jgh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: *default release=cvs tag=RELENG_8 in both standard-supfile and stable-supfile
On Tue, Nov 16, 2010 at 1:09 PM, pigskinwhite...@icqmail.com wrote: I was wondering why both the stable standard supfiles on FreeBSD-8.1 / amd64 both have the exact release tag: *default release=cvs tag=RELENG_8 Shouldn't they be different? What would be the correct tab for each supfile respectively? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org IIRC, you could do RELENG_8_1, for ex: *default release=cvs tag=RELENG_7_3 is the tag on my currently running 7.3 box and *default release=cvs tag=RELENG_8_1 is on my 8.1 box. I didn't notice defaults perse but copied my working csup-standard file to the new box and updated the tag as necessary and was off on my merry way. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: *default release=cvs tag=RELENG_8 in both standard-supfile and stable-supfile
On 16 November 2010 18:09, pigskinwhite...@icqmail.com wrote: I was wondering why both the stable standard supfiles on FreeBSD-8.1 / amd64 both have the exact release tag: *default release=cvs tag=RELENG_8 Shouldn't they be different? What would be the correct tab for each supfile respectively? On my machine, it's not; they're different (and I have RELENG_8_1). However, if you checkout RELENG_8 then standard-supfile will be for RELENG_8 which is the same for STABLE, so I assume you've actually checked out RELENG_8, not RELENG_8_1. Were you to checkout RELENG_8_1 you'd have that tag in standard-supfile. If you get what I mean... I'm supposed to be a teacher too! Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Does MAC version of iTunes work on FreeBSD?
-- System Name: laptop2.StevenFriedrich.org Hardware: 2.80GHz Intel Pentium 4 (HTT) with 2 GB memory OS version:FreeBSD 8.1-RELEASE-p1 i386 (6.4 MB kernel) manager(s):kde4-4.5.3 X windows: xorg-7.5X.Org X Server 1.7.5 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Is ZFS ready for prime time?
On Tue, Nov 16, 2010 at 8:11 AM, Ivan Voras ivo...@freebsd.org wrote: Actually, I don't see anything incorrect in the above archive post. I do. Cherry picking ZFS deficiencies without addressing the proper documented way to work around them or at even acknowledging it's possible to do so is FUD. It's not like traditional RAID doesn't have it's own set of gotcha's and proper usage environment. Dismissing the value of checksumming your data seems foolhardy to say the least. The place where silent data corruption most frequently occurs, in large archive type filesystems, also happens to be one of the prime usage candidates of RAIDZ. As for specific problems with ZFS, I'm also pessimistic right now - it's enough to read the freebsd-fs @ freebsd.org and zfs-discuss @ opensolaris.org lists to see that there are frequent problems and outstanding issues. You can almost grep for people losing data on ZFS weekly. Compare this to the volume of complaints about UFS in both OSes (almost none). There are actually very few stories of ZFS/zpool loss on the FreeBSD list(some are misidentifications of issues like this: http://lists.freebsd.org/pipermail/freebsd-fs/2010-September/009417.html), another source I would point you to is http://forums.freebsd.org/. The single recent valid one I can find involves a pool on geli, but I will grant you that it happens at all is quite disconcerting. There have been a lot of other ZFS issues ranging from performance, NFS troubles, quirks on storage controllers not present when using UFS, to other as-yet unexplained oddities. Many of these are corner cases, and I think they have mostly been resolved. If you've happened to encouter one, I'm sure it's left a sour taste though. UFS has it's own set of issues/limitations so regardless of what you pick make sure you're aware of them and take issues to address them before problems occur. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Does MAC version of iTunes work on FreeBSD?
On Tue, Nov 16, 2010 at 2:09 PM, Steven Friedrich free...@insightbb.com wrote: -- System Name: laptop2.StevenFriedrich.org Hardware: 2.80GHz Intel Pentium 4 (HTT) with 2 GB memory OS version: FreeBSD 8.1-RELEASE-p1 i386 (6.4 MB kernel) manager(s): kde4-4.5.3 X windows: xorg-7.5 X.Org X Server 1.7.5 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org No. The Mac version of iTunes depends on the Cocoa application framework, which is a set of Objective C objects that, as far as I am aware of, has no compatible framework under FreeBSD. -- Nathan Vidican nat...@vidican.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Does MAC version of iTunes work on FreeBSD?
On 16 November 2010 19:26, Nathan Vidican nat...@vidican.com wrote: On Tue, Nov 16, 2010 at 2:09 PM, Steven Friedrich free...@insightbb.com wrote: -- System Name: laptop2.StevenFriedrich.org Hardware: 2.80GHz Intel Pentium 4 (HTT) with 2 GB memory OS version: FreeBSD 8.1-RELEASE-p1 i386 (6.4 MB kernel) manager(s): kde4-4.5.3 X windows: xorg-7.5 X.Org X Server 1.7.5 No. The Mac version of iTunes depends on the Cocoa application framework, which is a set of Objective C objects that, as far as I am aware of, has no compatible framework under FreeBSD. -- Nathan Vidican nat...@vidican.com Neither does the Windows version. http://appdb.winehq.org/objectManager.php?sClass=applicationiId=1347 You could however try gtkpod, rhythmbox or Amarok if your goal is to sync your iPod. Also, please don't write X windows, its name is the X Window System [1]. Chris [1] http://en.wikipedia.org/wiki/X_Window_System#Nomenclature ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ZFS and 4k sector drives
i was sure it have variable sizes but multiplies of 4k, anyway i dont care ;) using 32 or 64K blocks (means 4 or 8K fragments) with UFS and full disks, or partitions aligned to 4K solves all problems ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Is ZFS ready for prime time?
On Mon, Nov 15, 2010 at 10:28 AM, Wojciech Puchar woj...@tensor.gdynia.pl wrote: no. ZFS is not usable and will never be usable for anything more than a toy. This is a result of that design. Actually I find the basics of its design pretty simple (cow/txg/zil) and for that reason I think it is going to become very robust in the near future, if it isn't already. What is complex is the various journal and soft-updates code that traditional file systems use. But yes it has performance problems in some workloads and needs more cpu/ram than usual. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Rebuilding perl with threads
Hello! I'm in a process of installing a new server. I have already built and installed a lot of ports over the past weeks, and now that I'm almost done I discovered that one of the last things I need to install (misc/amanda-server) needs Perl installed with threads support, whereas I have it installed without threads. For this kind of change, is it safe to reinstall just the Perl port, or do I also need to rebuild all ports that depend on Perl? That would be a *lot* of rebuilding. The version I currently have installed is perl-5.12.2_2, lang/perl5.12 seems to currently be at 5.12_4. -- Toomas Aas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Is ZFS ready for prime time?
snip ... Actually I find the basics of its design pretty simple (cow/txg/zil) and for that reason I think it is going to become very robust in the near future, if it isn't already. What is complex is the various journal and soft-updates code that traditional file systems use. But yes it has performance problems in some workloads and needs more cpu/ram than usual. ... All I know is the DOW is down almost 200 pts, so ZFS isn't a real priority for me right now. Novell v4+ FS was / is the best ever - period! If only they would make it OSS! Gary PS: Yes, I'm blowing on the flames... -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of App Deb Sent: Tuesday, November 16, 2010 2:32 PM To: Wojciech Puchar Cc: freebsd-questions@freebsd.org; Modulok Subject: Re: Is ZFS ready for prime time? On Mon, Nov 15, 2010 at 10:28 AM, Wojciech Puchar woj...@tensor.gdynia.pl wrote: no. ZFS is not usable and will never be usable for anything more than a toy. This is a result of that design. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org font size=1 div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in' /div This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system. /font ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: *default release=cvs tag=RELENG_8 in both standard-supfile and stable-supfile
On 16 November 2010 18:45, Chris Rees utis...@gmail.com wrote: On 16 November 2010 18:09, pigskinwhite...@icqmail.com wrote: I was wondering why both the stable standard supfiles on FreeBSD-8.1 / amd64 both have the exact release tag: *default release=cvs tag=RELENG_8 Shouldn't they be different? What would be the correct tab for each supfile respectively? On my machine, it's not; they're different (and I have RELENG_8_1). However, if you checkout RELENG_8 then standard-supfile will be for RELENG_8 which is the same for STABLE, so I assume you've actually checked out RELENG_8, not RELENG_8_1. Were you to checkout RELENG_8_1 you'd have that tag in standard-supfile. If you get what I mean... I'm supposed to be a teacher too! Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org there does seem to be a bit of duplication going on here, which could cause confusion. Maybe we could have a security sup file that has the relevant tag for the release # grep -v # /usr/share/examples/cvsup/stable-supfile *default host=CHANGE_THIS.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_8 *default delete use-rel-suffix *default compress src-all # grep -v # /usr/share/examples/cvsup/standard-supfile *default host=CHANGE_THIS.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_8 *default delete use-rel-suffix *default compress src-all ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
X resolution
Hello. I've configured my X to use a 1600x1200 resolution (or so I thought...). It used to work until the last X.Org upgrade; after that it *usually* worked: very rarely it would start at 2048x1536, but a couple of Ctrl-Alt-Backspace was normally enough. Since a couple of day, it always start at 2048x1536, and there is no way to get 1600x1200 unless I login and change resolution afterwards (which is however enought to mess all my KDE fonts up). I've got this in my xorg.conf: Section Screen Identifier SyncMaster Device Card0 MonitorSyncMaster SubSection Display Viewport 0 0 Depth 32 Modes 1600x1200 EndSubSection EndSection Is it ok? Any other hint? Of course I can provide full xorg.conf and Xorg.0.log, but they are quite long... Card is a Radeon HD 4200. bye Thanks av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: 'Broadcom Wireless b/g (BCM4315/BCM22062000)'
On Tue, Nov 16, 2010 at 5:17 AM, b. f. bf1...@googlemail.com wrote: Chris Brennan wrote: ... My Hiccup as the subject suggests is about my Wireless Card. I have been following the handbook ( http://www.freebsd.org/doc/handbook/config-network-setup.html) on how to use 64-bit Windows drivers coupled w/ ndisgen to get my wireless card working. I got ndisgen to generate a kernel module but it immediately caused my laptop to reboot when the kernel was loaded. This left me scratching my head. I think I might need firmware (I remember having to extract firmware from the driver for linux). pciconf shows the following: [root at BlackDragon [~]# pciconf -lv | grep -A3 0x4315 none8 at pci0:8:0:0: class=0x028000 card=0x137c103c chip=0x431514e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' class = network [root at BlackDragon [~]# The laptop is an HP dv2845SE and it's running FreebSD64-8.1. Let me know if I missed anything. I'm assuming that by FreebSD64, you mean the amd64 version of FreeBSD. Have you tried using a recent version of the native bwn(4) driver, together with the net/bwn-firmware-kmod port, rather than ndis(4)? b. Don't know about amd64 but on i386 it works* with siba_bwn-driver. siba_b...@pci0:16:0:0: class=0x028000 card=0x137d103c chip=0x431514e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' class = network FreeBSD flapbsd 8.1-STABLE FreeBSD 8.1-STABLE #0: Tue Jul 27 23:05:54 CEST 2010 r...@flapbsd:/usr/obj/usr/src/sys/FLAPBSD i386 Id Refs AddressSize Name 1 23 0xc040 811778 kernel 21 0xc0c12000 2d8f0linux.ko 31 0xc0c4 371d4if_bwn.ko 42 0xc0c78000 a1dc siba_bwn.ko 51 0xc5ef4000 2c000bwn_v4_lp_ucode15 61 0xc617c000 9000 i915.ko 71 0xc6185000 14000drm.ko works*: I have problems reassociating after suspend to ram/hibernate This card worked through ndis on freebsd7/i386. /E ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Is ZFS ready for prime time?
On 11/16/10 20:23, Adam Vande More wrote: On Tue, Nov 16, 2010 at 8:11 AM, Ivan Vorasivo...@freebsd.org wrote: Actually, I don't see anything incorrect in the above archive post. I do. Cherry picking ZFS deficiencies without addressing the proper documented way to work around them or at even acknowledging it's possible to do so is FUD. It's not like traditional RAID doesn't have it's own set of gotcha's and proper usage environment. Well, you are also doing cherry picking of *good* features so I'd say there's no conceptual difference here :) NHF, I'm not attacking you; as with everything else, people need to test technologies they are going to use and decide if they are good enough. Dismissing the value of checksumming your data seems foolhardy to say the least. The place where silent data corruption most frequently occurs, in large archive type filesystems, also happens to be one of the prime usage candidates of RAIDZ. Now if only the default checksum wasn't so weak: http://opensolaris.org/jive/thread.jspa?threadID=69655tstart=30 http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6740597 There are no details about its fixed status so I think the problem is still there. (of course, stronger options are available, etc. - and it's better than nothing) As for specific problems with ZFS, I'm also pessimistic right now - it's enough to read the freebsd-fs @ freebsd.org and zfs-discuss @ opensolaris.org lists to see that there are frequent problems and outstanding issues. You can almost grep for people losing data on ZFS weekly. Compare this to the volume of complaints about UFS in both OSes (almost none). There are actually very few stories of ZFS/zpool loss on the FreeBSD list(some are misidentifications of issues like this: http://lists.freebsd.org/pipermail/freebsd-fs/2010-September/009417.html), another source I would point you to is http://forums.freebsd.org/. The single recent valid one I can find involves a pool on geli, but I will grant you that it happens at all is quite disconcerting. Yes, especially since GELI is very sensitive to corruption. But I'm also counting cases like the inability to replace a drive which failed, log device corruptions and similar things which will, if not result in a totally broken file system, result in a file system which is wedged in a way that requires it to be re-created. In many of those, though, it's not clear if the error is in ZFS or FreeBSD. UFS has it's own set of issues/limitations so regardless of what you pick make sure you're aware of them and take issues to address them before problems occur. Of course, UFS *is* old and classical in its implementation - it would be just as wrong to expect fancy features from UFS like to expect such time-tested stability from ZFS. And new technologies need time to settle down: there are still occasional reports of SUJ problems. Personally, I have encountered only stability issues and currently have only one server with ZFS in production (reduction from several of them about a year ago), but I'm constantly testing it in staging. If the v28 import doesn't destabilize it in 9, I'm going to give it another chance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: X resolution
On Tue, 16 Nov 2010, Andrea Venturoli wrote: Hello. I've configured my X to use a 1600x1200 resolution (or so I thought...). It used to work until the last X.Org upgrade; after that it *usually* worked: very rarely it would start at 2048x1536, but a couple of Ctrl-Alt-Backspace was normally enough. Since a couple of day, it always start at 2048x1536, and there is no way to get 1600x1200 unless I login and change resolution afterwards (which is however enought to mess all my KDE fonts up). It sounds like the EDID information isn't always working. Check your video cable to see if a pin is bent over, or try a different one. I've got this in my xorg.conf: Section Screen Identifier SyncMaster Device Card0 MonitorSyncMaster SubSection Display Viewport 0 0 Depth 32 Modes 1600x1200 EndSubSection EndSection 32 is not a valid depth, according to xorg.conf(5). Of course I can provide full xorg.conf and Xorg.0.log, but they are quite long... xorg.conf is usually not a problem. Log files can be posted on the web somewhere, like pastebin.com. Card is a Radeon HD 4200. What is the monitor? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
ejabberd won't startup
Hi everybody dealing with ejabberd and/or erlang in a FreeBSD8-Jail ! I've built the ejabberd port (with ODBC support / the Erlang MySQL driver) two days ago but can't get it to run. # ejabberdctl start spits out a huge bunch of Erlang error messages (unreadable for most humans), obviously saying that it can't connect properly to the loopback interface on Port 4369 (respectively connects but then immediately stops, causing a crash dump and not able to register it's node). Tcpdump shows 8 pakets captured when pointing to the lo0 interface. The jail is an ordinary Jail with no special configuration (just 1 IP and a proper hostname, running Postfix/Dovecot with MySQL just fine). PF or it's ruleset too seems not to be the cause as Erlang's behaviour is the same even with a switched off PF. Restarting the Jail and triple-checking it's parameters did not help too. As the error can be reproduced solely with Erlang (without even starting ejabberd), the ejabberd.cfg file however does not seem to play any role. I was told, this actually was an Erlang issue and so I first went to the Erlang folks (erlang mailing list). At least until now, they unfortunately could not help me making a real step. So, I got stuck and now am in search for people successfully running ejabberd in a Jail. I have seen reports from the web on success and even I too had a test installation in a Jail running half a year ago (unfortunately did not note all details before I wiped that testing machine). My suggestion is, it might have something to do with the file /usr/locaal/etc/ejabberd/inetrc (responsible for name resolution for Erlang) So, are there any Jail/ejabberd experts out there ? Or just people having it up and running ? kind regards Tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD on Rackspace Could
Try www.rootbsd.net - FreeBSD VM's backed by great service. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Building kdiff3 for kde 3.5
Apparently only the version for kde4 is on the ports and I could not find a package for 3.5. Building the available source had some interesting results but ultimate did not work. What I finally did was google the 3.5 package name I had installed and found a copy at the University of Kent. There must be a better way to find older ports/packages. What should I have done? _ Douglas Denault http://www.safeport.com d...@safeport.com Voice: 301-217-9220 Fax: 301-217-9277 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
