On 02/28/2013 09:36 AM, rihad wrote:
On 02/27/2013 08:59 PM, John Baldwin wrote:
On Wednesday, February 27, 2013 12:58:11 am rihad wrote:
Now about this part taken from here
http://lists.freebsd.org/pipermail/freebsd-scsi/2011-March/004839.html
> By issuing a dummy read operation (t
On 02/27/2013 08:59 PM, John Baldwin wrote:
On Wednesday, February 27, 2013 12:58:11 am rihad wrote:
Now about this part taken from here
http://lists.freebsd.org/pipermail/freebsd-scsi/2011-March/004839.html
> By issuing a dummy read operation (thus forcing a flush of data
buffers), t
On 02/27/2013 03:39 AM, Steven Hartland wrote:
- Original Message - From: "rihad"
On 28/10/2011 04:14, Jan Mikkelsen wrote:
>/ Hi,
/>/
/>/ There is a patch linked to from this PR, which seems very similar:
/>/
/>/ http://www.freebsd.org/cgi/qu
On 02/27/2013 12:48 AM, John Baldwin wrote:
On Tuesday, February 26, 2013 1:31:44 pm rihad wrote:
On 28/10/2011 04:14, Jan Mikkelsen wrote:
/ Hi,
/>/
/>/ There is a patch linked to from this PR, which seems very similar:
/>/
/>/ http://www.freebsd.org/cgi/query-pr.cgi?pr
On 28/10/2011 04:14, Jan Mikkelsen wrote:
>/ Hi,
/>/
/>/ There is a patch linked to from this PR, which seems very similar:
/>/
/>/ http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/140416
/>/
/>/ http://lists.freebsd.org/pipermail/freebsd-scsi/2011-March/004839.html
/>/
/>/ The problem is also
-- Stanislav Sedov wrote :
On Wed, 5 Aug 2009 00:30:20 -0700 (PDT)
alexpalias-bsdsta...@yaho... mentioned:
>> dev.em.0.rx_processing_limit=300
>> dev.em.1.rx_processing_limit=300
>> dev.em.2.rx_processing_limit=300
>> dev.em.3.rx_processing_limit=300
> This tunables only affects polling mode. D
On 05/14/2010 04:13 AM, Doug Ambrisko wrote:
rihad writes:
| Hi, I'm thinking of enabling the watchdog on our Dell PowerEdge 2950 /
| FreeBSD 8.0 amd64, so that it reboots the machine in case of lockups.
| Right now it doesn't work:
|
| # watchdog
| watchdog: patting the dog: Ope
Hi, I'm thinking of enabling the watchdog on our Dell PowerEdge 2950 /
FreeBSD 8.0 amd64, so that it reboots the machine in case of lockups.
Right now it doesn't work:
# watchdog
watchdog: patting the dog: Operation not supported
#
Looking through the kernel configuration I found two relevant s
Greg Byshenk wrote:
On Tue, Oct 23, 2007 at 11:08:27PM +0200, Per olof Ljungmark wrote:
rihad wrote:
How risky is it to start using 7.0-BETA1 in production, with the
intention of upgrading to release as soon as possible? Thanks.
We've used 7-CURRENT since January on a couple of produ
How risky is it to start using 7.0-BETA1 in production, with the
intention of upgrading to release as soon as possible? Thanks.
BTW, where can I find 7-STABLE release notes? It's not here:
http://www.freebsd.org/relnotes.html
___
freebsd-stable@freebsd
Imagine: Foo 1.2.3 that
was current at the time of FreeBSD 6.0 release gets a severe vuln after
some time. Some admins upgrade to the latest and greatest Foo 1.2.9,
others to Foo 1.2.7 (probably with not recently updated ports tree)...
If 1.2.7 is secure, there is no problem. If 1.2.7 is not,
Imagine: Foo 1.2.3 that
was current at the time of FreeBSD 6.0 release gets a severe vuln after
some time. Some admins upgrade to the latest and greatest Foo 1.2.9,
others to Foo 1.2.7 (probably with not recently updated ports tree)...
If 1.2.7 is secure, there is no problem. If 1.2.7 is not,
Marwan Burelle wrote:
On Tue, Dec 20, 2005 at 02:18:13PM +0400, rihad wrote:
A very interesting script for its own purpose, but I'm afraid this
doesn't answer my question at all. Perhaps seeing the way that e.g.
Debian deals with the upgrade problem might shed some light on the
i
Yann Golanski wrote:
Quoth rihad on Tue, Dec 20, 2005 at 10:25:59 +0400
Is there a security branch for the FreeBSD ports collection? Let's say,
I installed FreeBSD 6.0 together with all needed -RELEASE ports/packages
(i.e., those on the CD). Running security/portaudit after a while
re
Is there a security branch for the FreeBSD ports collection? Let's say,
I installed FreeBSD 6.0 together with all needed -RELEASE ports/packages
(i.e., those on the CD). Running security/portaudit after a while
reveals that some of the installed packages have vulnerabilities. Am I
on my own to go
Hello all,
I'm trying to configure a firewall with carp + ipfw, but I encountered the
strange problem.
Packets are bypassing carp interface, instead ipfw log shows packet flow
to/from physical interface, e.g.:
http://www.countersiege.com/doc/pfsync-carp/
"it is important to keep in mind that
FreeBSD 6-STABLE has imported dhclient from OpenBSD:
OpenBSD dhclient as of OpenBSD 3.7 has been imported. It replaces the
ISC DHCP client used in prior versions of FreeBSD.
(http://www.freebsd.org/relnotes/6-STABLE/relnotes/i386/article.html)
making /etc/dhclient.conf no longer accept this sy
I have a FreeBSD 5.3 box and its two HDD's are setup as one GEOM mirror
unit /dev/mirror/gm0 (c.f. http://people.freebsd.org/~rse/mirror/). Now
Now I want to do a binary upgrade to FreeBSD 5.4, but the new
sysinstall's disklabel editor only recognizes the IDE disks and does not
consider the GEO
18 matches
Mail list logo
