Re: Best way to switch from Linux to BSD
On Wed 30 Mar 2011 at 08:10:23 PDT Michal Varga wrote: On Wed, 2011-03-30 at 16:26 +0200, Oliver Pinter wrote: http://hup.hu/node/94286 ;) 1. $ portinstall -v www/epiphany $ epiphany http://www.youtube.com/html5; $ epiphany http://www.youtube.com/watch?v=XBH1dcHoL6Y; Firefox4 is now in ports, and also supports html5. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.2-PRERELEASE generating warnings re my hard drive
On Sun 13 Feb 2011 at 16:37:04 PST Charlie Kester wrote: I'm running 8-STABLE, i386 architecture, and yesterday I updated to the latest version with cvsup. After installing the kernel and rebooting, I see the following messages on the console: ad4: WARNING - SETFEATURES SET TRANSFER MODE requeued due to channel reset ad4: interrupt on idle channel ignored ad4: WARNING - SETFEATURES SET TRANSFER MODE requeued due to channel reset ad4: interrupt on idle channel ignored (repeated several times, and then the following:) ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad4: 238475MB Seagate ST3250410AS 3.AAF at ata2-master UDMA100 SATA 1.5Gb/s (shortly afterwards, I see this:) Trying to mount root from ufs:/dev/ad4s1a ad4: WARNING - READ_DMA requeued due to channel reset LBA=33963227 ata2: FAILURE - already active DMA on this device ata2: setting up DMA failed g_vfs_done():ad4s1f[READ(offset=12103825408, length=2048)]error = 5 ad4: WARNING - READ_DMA requeued due to channel reset LBA=705199 ata2: FAILURE - already active DMA on this device ata2: setting up DMA failed (which then repeats many times with different LBA and offset values.) Similar messages appear after bootup is completed and I've logged in. They seem to appear whenever any process accesses the hard drive. I reverted back to my previous build of the kernel, dated 3 Feb 2011, and these messages no longer appear. smartctl reports that the drive is running without any errors or incipient failures. So my question is, what's going on here? Is this something I should worry about? If it's a problem with my kernel config, what parameters should I be looking at? Motherboard: Intel D510MO with builtin IDE controller (NM10). Anyone? If this isn't the best forum for this question, I'd appreciate a redirection. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
8.2-PRERELEASE generating warnings re my hard drive
I'm running 8-STABLE, i386 architecture, and yesterday I updated to the latest version with cvsup. After installing the kernel and rebooting, I see the following messages on the console: ad4: WARNING - SETFEATURES SET TRANSFER MODE requeued due to channel reset ad4: interrupt on idle channel ignored ad4: WARNING - SETFEATURES SET TRANSFER MODE requeued due to channel reset ad4: interrupt on idle channel ignored (repeated several times, and then the following:) ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad4: 238475MB Seagate ST3250410AS 3.AAF at ata2-master UDMA100 SATA 1.5Gb/s (shortly afterwards, I see this:) Trying to mount root from ufs:/dev/ad4s1a ad4: WARNING - READ_DMA requeued due to channel reset LBA=33963227 ata2: FAILURE - already active DMA on this device ata2: setting up DMA failed g_vfs_done():ad4s1f[READ(offset=12103825408, length=2048)]error = 5 ad4: WARNING - READ_DMA requeued due to channel reset LBA=705199 ata2: FAILURE - already active DMA on this device ata2: setting up DMA failed (which then repeats many times with different LBA and offset values.) Similar messages appear after bootup is completed and I've logged in. They seem to appear whenever any process accesses the hard drive. I reverted back to my previous build of the kernel, dated 3 Feb 2011, and these messages no longer appear. smartctl reports that the drive is running without any errors or incipient failures. So my question is, what's going on here? Is this something I should worry about? If it's a problem with my kernel config, what parameters should I be looking at? Motherboard: Intel DM510 with builtin IDE controller. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 8.2-PRERELEASE generating warnings re my hard drive
On Sun 13 Feb 2011 at 16:37:04 PST Charlie Kester wrote: Motherboard: Intel DM510 with builtin IDE controller. Oops, I shouldn't have tried to write that from memory. It's actually an Intel D510MO mobo, which uses the NM10 chipset for I/O. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Policy on static linking ?
On Fri 14 Jan 2011 at 06:07:37 PST Pete French wrote: I recently wanted to use libdespatch, but I found that the port didn't install the static libraries. I filed a PR, and found out from the reponse that this was deliberate, and that a number of other ports were deliberately excluding static libraries too. Some good reasons where given, which I wont reporduce here, as you can read them at: http://www.freebsd.org/cgi/query-pr.cgi?pr=151306 Interesting reading. One thing bothers me, however, about the reasons given against static linking. Surely, if a port statically links to a library, it calls out that library on a LIB_DEPENDS line and the dependency is reflected in the package database? So, if a security issue comes up with the library, it wouldn't be difficult to flag the dependent port as one that needs to be recompiled using the newly-patched library? The user only gets the patches to the shared library after he reads and responds to the security notice, or when he's doing a normal update of his ports. Correct? Well then, what's different about the scenario when it's a static library? What am I missing here? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: [HEADSUP]: ports feature freeze now in effect
On Mon 15 Feb 2010 at 14:11:47 PST Steven Friedrich wrote: I suspect this means we won't get KDE 4.4 for quite some time... I don't think that it was ever in the plan to get it in before the freeze. Here's what Martin Wilke said in the call for testing: Before you ask we don't want to put KDE 4.4.0 in the ports tree before FreeBSD 7.3 was released. But there's no reason to think it will be quite some time before we see it in the portstree. Given the past history of the KDE porting team, I would expect to see it shortly after the 7.3 release. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: [HEADSUP]: ports feature freeze now in effect
On Mon 15 Feb 2010 at 15:05:09 PST Charlie Kester wrote: On Mon 15 Feb 2010 at 14:11:47 PST Steven Friedrich wrote: I suspect this means we won't get KDE 4.4 for quite some time... I don't think that it was ever in the plan to get it in before the freeze. Here's what Martin Wilke said in the call for testing: Before you ask we don't want to put KDE 4.4.0 in the ports tree before FreeBSD 7.3 was released. But there's no reason to think it will be quite some time before we see it in the portstree. Given the past history of the KDE porting team, I would expect to see it shortly after the 7.3 release. Sorry, this was supposed to go to ports@ instead. Looks like I need to debug my muttrc. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Open Vs Free BSD
On Fri 19 Jun 2009 at 11:23:26 PDT Michael R. Wayne wrote: OK, I'm going to take a guess here that English may not be Michal's primary language and re-ask his question: Given the several versions of *BSD, I have been led to understand that each excells in different ways. How do I select which one is right for my application, what are the underlying reasons that would lead me to that choice and what are the the disadvantages I am risking? This is, actually, not an inappropriate question coming from a potential new user who is not familiar with the history surrounding the various versions and would make an outstanding FAQ. As an example, we run FreeBSD on our firewalling machines because it works well enough and we prefer the reduced support costs of using a single O/S across our network. I am unsure of what the advantage of moving to OpenBSD might be and would find it very difficult to quantify the advantages (if any) versus the increased support resources required. This is a very real issue. Linux has a similar problem; I've personally been in meetings where clients examined the myriad Linux distributions and say It's very likely that we will make the incorrect choice. So we'll go with Windows. I suspect similar events have occurred with *BSD. So, rather than jumping on people about them bringing up religous wars (because, face it, you CAN edit a file perfectly well in either vi or emacs :-), we'd all be better served by giving them enough information to make the right choice in their situation while realizing the tradeoffs they are making. I agree, this shouldn't necessarily be treated as flamebait or trolling. But shouldn't the question be redirected to the advocacy mailing list/team? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
