[Please CC: me on any replies, as I check my inbox more frequently
than I check this list.]
I have three servers running 9.3-STABLE which are designed to be
able to exchange jails so that a virtual host can be readily moved
to a different physical host. Because physical NIC names could
differ, th
On Wed, Jan 31, 2007 at 09:30:56AM +0200, Stefan Lambrev wrote:
> Hello,
>
> >>pass out on (stf0) inet6 from any to any keep state
> >>
> >
> >Just for my edification, what is the point of "keep state" on an
> >"any-to-any" rule?
> >
> >
> imagine that you have only 2 rules -
> block in
> Date: Mon, 29 Jan 2007 12:02:52 +
> From: Pete French <[EMAIL PROTECTED]>
> Subject: Re: impossible rc.d ordering problem with stf and pf ?
> To: freebsd-stable@freebsd.org, [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
> Message-ID: <[EMAIL PROTECTED]>
>
> > 1) You use the in
> Date: Wed, 17 Jan 2007 13:47:37 +0100
> From: Richard <[EMAIL PROTECTED]>
> Subject: Failover-HA-Setup
> To: freebsd-stable@freebsd.org
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain
>
> Hi there!
>
> I am looking for a solution for a small problem regarding a high
> availability
> Date: Sun, 17 Dec 2006 13:44:05 +0100 (CET)
> From: patrick <[EMAIL PROTECTED]>
> Subject: loader freezes system during timer autoboot
> To: [EMAIL PROTECTED]
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
>
>
> Hi,
>
> I have a supermicro system
> Date: Sun, 16 Apr 2006 17:43:58 +0300
> From: Evren Yurtesen <[EMAIL PROTECTED]>
> Subject: CPUTYPE=athlon-xp and loader
> To: freebsd-stable@freebsd.org
> Message-ID: <[EMAIL PROTECTED]>
>
> Hello,
>
> I have a problem which I have found out from mailing lists that some
> other people had. Ho
> Date: Wed, 01 Mar 2006 11:05:13 +
> From: Pete French <[EMAIL PROTECTED]>
> Subject: New ports on older stable (4.11)
> To: freebsd-stable@freebsd.org
> Message-ID: <[EMAIL PROTECTED]>
>
> I dont know how backward compatible ports are ggenerally, but I
> have a 4.11 machine that I really wan
> Date: Wed, 8 Feb 2006 06:46:37 -0600
> From: Michael Ekstrand <[EMAIL PROTECTED]>
> Subject: Re: Trouble with mounting USB stick as user
> To: freebsd-stable@freebsd.org
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=US-ASCII
>
> On Wed, 8 Feb 2006 22:40:04 +1100
> Rob <[E
> Date: Sun, 29 Jan 2006 15:08:21 + (GMT)
> From: Gavin Atkinson <[EMAIL PROTECTED]>
> Subject: Re: nVidia RAID + FreeBSD 6.0
> To: Christian Brueffer <[EMAIL PROTECTED]>
> Cc: freebsd-stable@freebsd.org, [EMAIL PROTECTED]
>
> On Sun, 29 Jan 2006, Christian Brueffer wrote:
> > On Sun, Jan 29,
I am trying to create bootable installation media for 6.0-RELEASE.
This is my first attempt at doing this, so I am learning a lot and
fumbling even more as I go.
First, I wish to thank Masafumi Watari for his helpful step-by-step
procedure, based on RELENG_4, found at
http://www.sfc.wide.ad.jp/~
On Fri, Jan 06, 2006 at 10:22:43AM -0500, Vivek Khera wrote:
>
> On Jan 6, 2006, at 4:40 AM, James Long wrote:
>
> >>Yeah, I noticed that little tiny "UDP requests" note in the -h docs
> >>too. There's no reason to bind to all tcp addresses, and it i
> Date: Thu, 5 Jan 2006 10:31:33 -0500
> From: Vivek Khera <[EMAIL PROTECTED]>
> Subject: Re: rpcbind lingering on IP no longer specified on command
> line
> To: [EMAIL PROTECTED]
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
>
>
For some reason, this script:
#!/bin/sh
DEV=$(md_config -a -t malloc -s 500m)
newfs -i 512 -U /dev/$DEV
mount /dev/$DEV /mnt
cp -Rp /usr/src /mnt/
will kill my machine. I get zillions (well, hundreds at
least, without a serial console I can't count them)
of:
Dec 21 19:16:27 test kernel: g_v
> Date: Mon, 12 Dec 2005 09:39:44 +0100 (CET)
> From: Trond Endrest?l <[EMAIL PROTECTED]>
> Subject: Re: puzzling "ipfw show" output
> To: FreeBSD stable
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: TEXT/PLAIN; charset=ISO-8859-1
>
> On Mon, 12 Dec 2005 19:09+1100, Graham Menhennitt wrote:
>
On Tue, Nov 15, 2005 at 07:56:33PM -0800, David Wolfskill wrote:
> On Tue, Nov 15, 2005 at 07:49:10PM -0800, James Long wrote:
> >
> > ===> xorg-clients-6.8.2_1 depends on package: xterm>0 - not found
> >
> > and investigated the Makefile to find why the
On Tue, Nov 15, 2005 at 07:32:45PM -0800, David Wolfskill wrote:
> On Tue, Nov 15, 2005 at 07:26:16PM -0800, James Long wrote:
> > After hours of head-banging over the past couple of days,
> > I have finally succeeded in installing EITHER
> > xorg-clients-6.8.2_1 OR xte
After hours of head-banging over the past couple of days,
I have finally succeeded in installing EITHER
xorg-clients-6.8.2_1 OR xterm-206_1. Previously,
installing either port told me that it conflicted
with the other, in spite of having cvsupped my
ports tree twice to ensure I was getting the m
> On Fri, 28 Oct 2005 10:05, James Long wrote:
> > > Date: Thu, 27 Oct 2005 13:05:23 +0930
> > > From: "Daniel O'Connor" <[EMAIL PROTECTED]>
> > > Subject: Re: RFC: proposed patch for
> > > /usr/src/usr.sbin/wicontrol/wico
> Date: Thu, 27 Oct 2005 13:05:23 +0930
> From: "Daniel O'Connor" <[EMAIL PROTECTED]>
> Subject: Re: RFC: proposed patch for
> /usr/src/usr.sbin/wicontrol/wicontrol.c
>
> > The command I use most is wicontrol -L
>
> Try ifconfig ath0 list scan
# ifconfig ath0 list scan
ifconfig: list: bad
> wicontrol is obsolete and you should not need to use it, particularly
> for ath(4) devices. Why are you using it? Is some feature you need
> missing from ifconfig?
The command I use most is wicontrol -L
___
freebsd-stable@freebsd.org mailing list
ht
wicontrol.c defaults to the "wi" interface. I used to have a
wi device, but it eventually took a dump and I bought a new
ath-based card, which works flawlessly AFAIK, after four months
or so.
But I grow weary of having to specify "-i ath0" every time I
run wicontrol.
Please review the following
> > > Should these two commands produce identical output?
> > >
> > > $ bzegrep "38436|41640" /var/log/maillog.0.bz2 | wc -l
> > >0
> > > $ bzcat /var/log/maillog.0.bz2 | egrep "38436|41640" | wc -l
> > > 121
>
> Can you try the patch for src/gnu/usr.bin/grep/grep.c?
The patch appears
Should these two commands produce identical output?
$ bzegrep "38436|41640" /var/log/maillog.0.bz2 | wc -l
0
$ bzcat /var/log/maillog.0.bz2 | egrep "38436|41640" | wc -l
121
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.o
On Tue, Aug 26, 2003 at 10:03:25AM -0700, James Long wrote:
>
> So I'm conffused as to why sendmail would need to be patched
> on 8/25 when 8.12.9 has been in the base distribution since
> April.
D'oh!
"4-STABLE prior to Mar 29 19:33:18 2003 UTC"
> Tha
The advisory states that the problem was fixed on 8/25 approx.
22:35. The security also states that the problem afflicts
sendmail 8.12.0 through 8.12.8. However, I have a system
which had its world built on April 9, 2003, and it is running
sendmail 8.12.9, according to the 220 banner it gives whe
On Thu, Jun 05, 2003 at 06:37:55AM +0200, Noor Dawod wrote:
>
> The panic's details are as follows:
>
> Fatal trap 12 = page fault while in kernel mode
I'd test memory thoroughly next.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org
On Sun, Jan 26, 2003 at 08:58:32AM +0100, Zoran Kolic wrote:
>Dear FreeBSD!
>Hope that someone on the list has
> expirience with external Zoltrix modem
> named Rainbow. It should change my
> nightmare: lucent winmodem. Maker
> has a lot of data about windows com-
> pability, but freeBSD is
t from ufs:/dev/da0s1a
On Mon, Jan 20, 2003 at 02:08:29PM -0800, James Long wrote:
> I have a Compaq ProLiant ML310, with an integrated ATA RAID controller
> controlling two 40G Seagate ST340016A drives.
>
> >From some Googling, I have learned:
>
> The ML310 uses the Se
On Wed, Jan 22, 2003 at 11:05:15AM -0800, Glendon M. Gross wrote:
>
> I am getting the following when attempting "make buildworld". Is there
> a known fix for this error? Please reply to me directly, as I am not
> currently subscribed to the list.
>
>
> cc -O -pipe
> -I/usr/src/lib/libpam/m
In the security run output notifications from most nearly every machine
I monitor, I see lines in the kernel log messages section similar to:
example.com kernel log messages:
> .14.232:48342 506.29.618.239:80 in via dc0
That's just a reconstructed example, but the pattern is that first, the
log
In doing some merges lately, I've gotten into situations where mergemaster
gives me a choice between old lines I want to keep on the left, and new
lines which I want to add on the right. A specific example was in merging
my /etc/group and /etc/passwd files, I had the choice between some existing
31 matches
Mail list logo