On Wed, Mar 08, 2006 at 11:15:11PM -0800, Rob wrote:
>
> Hi,
>
> I have uploaded today 6-Stable.
> The 'make installworld' fails with an error
> message on a missing 'audit group' and refers
> to /usr/src/UPDATING.
> However, there's no information in UPDATING
> about this issue!
It's taken care
On Thu, Mar 09, 2006 at 12:14:20PM +0600, Pavel Gubin wrote:
> On Mon, Mar 06, 2006 at 02:03:19AM -0500, Kris Kennaway wrote:
>
> > Well, that's what you posted, but it was nonsensical. However, gdb is
> > sometimes confused about stack traces, which is why I asked for a
> > trace from DDB instea
On Thursday 09 March 2006 01:09, Sam Leffler wrote:
> Daniel O'Connor wrote:
> > In any case I imagine there is no point forcing it to use 54Mbit - it
> > will negotiate the highest speed it can manage based on signal strength
> > and hardware support (for the AP and the card) automatically.
> >
>
On 3/9/06, Rob <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I have uploaded today 6-Stable.
> The 'make installworld' fails with an error
> message on a missing 'audit group' and refers
> to /usr/src/UPDATING.
> However, there's no information in UPDATING
> about this issue!
> Please add.
>
mergemaster
Hi,
I have uploaded today 6-Stable.
The 'make installworld' fails with an error
message on a missing 'audit group' and refers
to /usr/src/UPDATING.
However, there's no information in UPDATING
about this issue!
Please add.
Rob.
__
Do You Yahoo!?
T
On Mon, Mar 06, 2006 at 02:03:19AM -0500, Kris Kennaway wrote:
> Well, that's what you posted, but it was nonsensical. However, gdb is
> sometimes confused about stack traces, which is why I asked for a
> trace from DDB instead.
So, I've compiled in DDB and after two days uptime got another pa
On Mon, Mar 06, 2006 at 11:24:36AM +0200, Dmitry Pryanishnikov wrote:
> What kind of ppp do you use: kernel (devices ppp + process pppd) or user
> (devices tun + process ppp)? It seems to me that kernel ppp is seriously
> broken in RELENG_6, but I've never succeeded in getting a crashdump (my
On Thu, Mar 09, 2006 at 03:53:19AM +, Miguel Lopes Santos Ramos wrote:
> > Can you try to narrow down this problem some more? e.g. look up the
> > port used by rpc.lockd with rpcinfo on client and server and tcpdump
> > to see what locking requests are being passed back and forth (you
> > shou
JoaoBR wrote:
On Wednesday 08 March 2006 13:00, Sam Leffler wrote:
"simply stops" says little. Are beacon frames transmitted? Can you see
inbound traffic? Is the ap configured in a bridge and can you see
outbound traffic from the wired interface? What does ifconfig show for
the device?
I
Daniel O'Connor wrote:
On Thursday 09 March 2006 10:41, JoaoBR wrote:
It looks like "man ath" does not list all media and mediaopt values.
sure not because there are lots of different cards out with different
mediaopts so you need to read your hw-manual or your card can answer
ifconfig -m ath0
> Can you try to narrow down this problem some more? e.g. look up the
> port used by rpc.lockd with rpcinfo on client and server and tcpdump
> to see what locking requests are being passed back and forth (you
> should see the request from client -> server and the reply granting
> the lock; or not
On Thu, Mar 09, 2006 at 03:12:24AM +, Miguel Lopes Santos Ramos wrote:
> > From: Kris Kennaway <[EMAIL PROTECTED]>
> > Subject: Re: rpc.lockd brokenness (2)
> >
> > Yeah, the file is still locked on the server, and will never be
> > unlocked unless you stop and restart the rpc.lockd on the serv
> From: Kris Kennaway <[EMAIL PROTECTED]>
> Subject: Re: rpc.lockd brokenness (2)
>
> Yeah, the file is still locked on the server, and will never be
> unlocked unless you stop and restart the rpc.lockd on the server
> (which releases all the locks it holds).
I did that. Lots of times. And I remov
If the software you're using gets the version in the same manner as
uname, then all you should need is a new kernel.
Or maybe just LD_PRELOAD a replacement for uname() that fakes out the
release information?
--lyndon
___
freebsd-stable@freebsd.o
On Thu, Mar 09, 2006 at 02:14:59AM +, Miguel Lopes Santos Ramos wrote:
> > From: Kris Kennaway <[EMAIL PROTECTED]>
> >
> > The bug is triggered because the file is locked in the parent
> > (i.e. the daemon process, which creates the pidfile) but unlocked by
> > the child after the fork (in this
> From: Kris Kennaway <[EMAIL PROTECTED]>
>
> The bug is triggered because the file is locked in the parent
> (i.e. the daemon process, which creates the pidfile) but unlocked by
> the child after the fork (in this case, when the child is killed). On
> the server, rpc.lockd compares the svid (=3D
> From: Kris Kennaway <[EMAIL PROTECTED]>
> Subject: Re: rpc.lockd brokenness (2)
>
[...]
> OK, I misunderstood. The rc.d script will signal cron to kill it,
> which should be closing the file descriptors and causing rpc.lockd to
> release the lock. Perhaps this part is broken. OK, I tested this
On Wed, Mar 08, 2006 at 07:57:22PM -0500, Kris Kennaway wrote:
> On Thu, Mar 09, 2006 at 12:26:44AM +, Miguel Lopes Santos Ramos wrote:
> > > From: Kris Kennaway <[EMAIL PROTECTED]>
> > > Subject: Re: rpc.lockd brokenness (2)
> > >
> > > This is intentional. It's how pidfile_*() tests whether
On Thu, Mar 09, 2006 at 12:26:44AM +, Miguel Lopes Santos Ramos wrote:
> > From: Kris Kennaway <[EMAIL PROTECTED]>
> > Subject: Re: rpc.lockd brokenness (2)
> >
> > This is intentional. It's how pidfile_*() tests whether the process
> > is still running. The intention is that if someone tries
On Thursday 09 March 2006 10:41, JoaoBR wrote:
> > It looks like "man ath" does not list all media and mediaopt values.
>
> sure not because there are lots of different cards out with different
> mediaopts so you need to read your hw-manual or your card can answer
> ifconfig -m ath0
In any case I
> From: Kris Kennaway <[EMAIL PROTECTED]>
> Subject: Re: rpc.lockd brokenness (2)
>
> This is intentional. It's how pidfile_*() tests whether the process
> is still running. The intention is that if someone tries to open the
> pidfile again while the first process is still running, the lock
> acq
On Wednesday 08 March 2006 20:59, Holger Kipp wrote:
> On Thu, Mar 09, 2006 at 12:31:46AM +0100, Joan Picanyol i Puig wrote:
> > * Damian Gerow <[EMAIL PROTECTED]> [20060309 00:12]:
> > > # ifconfig ath0 media DS/54Mbps
> > > ifconfig: unknown media subtype: DS/54Mbps
> >
> > DS/54 doesn't
On Thu, Mar 09, 2006 at 12:31:46AM +0100, Joan Picanyol i Puig wrote:
> * Damian Gerow <[EMAIL PROTECTED]> [20060309 00:12]:
> > # ifconfig ath0 media DS/54Mbps
> > ifconfig: unknown media subtype: DS/54Mbps
>
> DS/54 doesn't exist. Try OFDM/54Mbps instead.
Is this documented anywhere?
I
* Damian Gerow <[EMAIL PROTECTED]> [20060309 00:12]:
> # ifconfig ath0 media DS/54Mbps
> ifconfig: unknown media subtype: DS/54Mbps
> #
DS/54 doesn't exist. Try OFDM/54Mbps instead.
qvb
--
pica
___
freebsd-stable@freebsd.org mailing list
htt
On Wednesday 08 March 2006 20:15, Damian Gerow wrote:
> So, with the updated HAL, I'm now able to negotiate an IP address via DHCP
> over the WLAN. Huzzah!
>
> But I've got two questions (now that I can use the card):
>
> ath(4) doesn't contain a list of media nor mediaopt settings that can be
> u
On Wednesday 08 March 2006 13:00, Sam Leffler wrote:
> "simply stops" says little. Are beacon frames transmitted? Can you see
> inbound traffic? Is the ap configured in a bridge and can you see
> outbound traffic from the wired interface? What does ifconfig show for
> the device?
>
I agree but
So, with the updated HAL, I'm now able to negotiate an IP address via DHCP
over the WLAN. Huzzah!
But I've got two questions (now that I can use the card):
ath(4) doesn't contain a list of media nor mediaopt settings that can be
used. Some are detailed down in EXAMPLES, but there's no comprehen
On Wed, Mar 08, 2006 at 02:01:24PM +, Miguel Lopes Santos Ramos wrote:
> > I wonder if something else is going wrong and it's not rpc.lockd at
> > all.
>
> Oh, it's a locking problem alright. But perhaps not in rpc.lockd...
OK, I think I understand what is going on now...sort of.
> > It loo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, Mar 08, 2006 at 04:24:44PM -0500, Kris Kennaway wrote:
> On Wed, Mar 08, 2006 at 01:51:57PM -0600, Sam Stein wrote:
> > So prerelease is stable now...? Why exactly..
>
> Read the handbook.
An explanation that some people have found helpful i
On Wed, Mar 08, 2006 at 03:40:24PM -0500, Mike Tancsa wrote:
+> At 02:39 PM 08/03/2006, Pawel Jakub Dawidek wrote:
+> >On Wed, Mar 08, 2006 at 01:50:42PM -0500, Mike Tancsa wrote:
+> >+> At 05:28 PM 06/03/2006, Pawel Jakub Dawidek wrote:
+> >+> >Hi.
+> >+> >
+> >+> >Here you can find patches with c
On Wed, Mar 08, 2006 at 01:51:57PM -0600, Sam Stein wrote:
> So prerelease is stable now...? Why exactly..
Read the handbook.
Kris
pgpyRagrEXm82.pgp
Description: PGP signature
On 3/8/06, Rob <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Yesterday I updated to -stable. I think that I did a decent job merging the
> /etc files and configuring
> rc.conf but I am getting some errors.
>
> /etc/rc.d/Makefile: 44: Syntax error: "(" unexpected.
>
> Perhaps that error is what is causing
At 12:25 PM 3/8/2006, Mike Jakubik wrote:
Glenn Dawson wrote:
At 12:06 PM 3/8/2006, you wrote:
Does anyone know how to change the release version of the source
code? I have some brain dead software (Plesk) that insists on
FreeBSD 5.3, while it will work just fine on 5.5 and even 6. I am
wonde
At 02:39 PM 08/03/2006, Pawel Jakub Dawidek wrote:
On Wed, Mar 08, 2006 at 01:50:42PM -0500, Mike Tancsa wrote:
+> At 05:28 PM 06/03/2006, Pawel Jakub Dawidek wrote:
+> >Hi.
+> >
+> >Here you can find patches with changes to gmirror(8) and graid3(8):
+> >
+> >http://people.freebsd.org/~pj
Hi,
Yesterday I updated to -stable. I think that I did a decent job merging the
/etc files and configuring
rc.conf but I am getting some errors.
First, the scripts in /usr/local/etc/rc.d are not starting. I do have the
following line in rc.conf:
local_startup="/usr/local/etc/rc.d"
The synta
Glenn Dawson wrote:
At 12:06 PM 3/8/2006, you wrote:
Does anyone know how to change the release version of the source
code? I have some brain dead software (Plesk) that insists on FreeBSD
5.3, while it will work just fine on 5.5 and even 6. I am wondering i
can change the version of RELENG_5 c
Scot Hetzel wrote:
On 3/8/06, Mike Jakubik <[EMAIL PROTECTED]> wrote:
Does anyone know how to change the release version of the source code? I
have some brain dead software (Plesk) that insists on FreeBSD 5.3, while
it will work just fine on 5.5 and even 6. I am wondering i can change
the ver
On 3/8/06, Mike Jakubik <[EMAIL PROTECTED]> wrote:
> Does anyone know how to change the release version of the source code? I
> have some brain dead software (Plesk) that insists on FreeBSD 5.3, while
> it will work just fine on 5.5 and even 6. I am wondering i can change
> the version of RELENG_5
Does anyone know how to change the release version of the source code? I
have some brain dead software (Plesk) that insists on FreeBSD 5.3, while
it will work just fine on 5.5 and even 6. I am wondering i can change
the version of RELENG_5 code so that this software will think its 5.3-R
and let
So prerelease is stable now...? Why exactly..
--
b1tt3r -- You know, like sugar?
Sam Stein
Computer TeXnician/Programmer
pgpZ1EjMDER6Z.pgp
Description: PGP signature
On Wed, Mar 08, 2006 at 01:50:42PM -0500, Mike Tancsa wrote:
+> At 05:28 PM 06/03/2006, Pawel Jakub Dawidek wrote:
+> >Hi.
+> >
+> >Here you can find patches with changes to gmirror(8) and graid3(8):
+> >
+> >http://people.freebsd.org/~pjd/patches/gmirror.7.patch
+> >http://people.f
At 05:28 PM 06/03/2006, Pawel Jakub Dawidek wrote:
Hi.
Here you can find patches with changes to gmirror(8) and graid3(8):
http://people.freebsd.org/~pjd/patches/gmirror.7.patch
http://people.freebsd.org/~pjd/patches/graid3.patch
Hi,
Against stable, this patch fails in places.
Steven Hartland wrote:
I've been trying to get a problem fixed with a Highpoint 1820a crashing
out with errors like:
kernel: IAL: COMPLETION ERROR, adapter 0, channel 2, flags=104
kernel: ATA regs: error 10, sector count 20, LBA low ff, LBA mid ff,
LBA high ff, device 4f, status 51
which result
On Wed, 2006-Mar-08 16:30:23 +, Pete French wrote:
>Is there any way of telling from this line whether the processor is capable
>of supporting amd64/emt64 ? Am trying to doo an audit of our FreeBSD machines
>to see whcih ones will need replacing if and when we move to 64 bits.
For amd64, the '
On Wednesday 08 March 2006 11:51, Mike Tancsa wrote:
> At 11:03 AM 08/03/2006, John Baldwin wrote:
> >On Tuesday 07 March 2006 19:45, Mike Tancsa wrote:
> > > At 07:29 PM 07/03/2006, Mike Tancsa wrote:
> > > >At 03:02 PM 07/03/2006, John Baldwin wrote:
> > > >>I have a somewhat large patch that MFC
At 11:03 AM 08/03/2006, John Baldwin wrote:
On Tuesday 07 March 2006 19:45, Mike Tancsa wrote:
> At 07:29 PM 07/03/2006, Mike Tancsa wrote:
> >At 03:02 PM 07/03/2006, John Baldwin wrote:
> >>I have a somewhat large patch that MFC's some of the cleanups to the
> >>interrupt code that needs some te
On Tuesday 07 March 2006 19:45, Mike Tancsa wrote:
> At 07:29 PM 07/03/2006, Mike Tancsa wrote:
> >At 03:02 PM 07/03/2006, John Baldwin wrote:
> >>I have a somewhat large patch that MFC's some of the cleanups to the
> >>interrupt code that needs some testing before it is MFC'd.
> >
> >
> >It seems
Is there any way of telling from this line whether the processor is capable
of supporting amd64/emt64 ? Am trying to doo an audit of our FreeBSD machines
to see whcih ones will need replacing if and when we move to 64 bits.
thanks,
-pete.
___
freebsd-st
JoaoBR wrote:
Hi
the atheros cards are stopping communication after some time
before I got still device timeouts in messages but the lates version on
releng_6 from yesterday simply stops
"simply stops" says little. Are beacon frames transmitted? Can you see
inbound traffic? Is the ap conf
I am sorry that the patch did not work.
use the same method, I turn on the debug mode and and it said that
[00:20:e0:8a:8d:79] probe_resp on chan 11 (bss chan 11) "aaa"
ipw0: ipw0: notify scan done
ipw0: ipw0: notify scan done
repeatly.
2006/3/8, Denis Shaposhnikov <[EMAIL PROTECTED]>:
>
> From: Kris Kennaway <[EMAIL PROTECTED]>
> Subject: Re: rpc.lockd brokenness (2)
>
> I wonder if something else is going wrong and it's not rpc.lockd at
> all.
Oh, it's a locking problem alright. But perhaps not in rpc.lockd...
> It looks like this wasn't made using -s 0 - sorry if I wasn't
> ex
> From: "Nick Price" <[EMAIL PROTECTED]>
> Subject: RE: Remote Installworld
>
> >I'm currently administering a machine about 1500mi from me with nobody
> >local to the machine to assist me. Anyways, my only access to this
> >machine is via SSH, no remote serial console or anything.
> >
On Tue, Mar 07, 2006 at 07:11:25PM -0800, Doug Hardie wrote:
> I am building a tool to identify the file that has a specific LBA.
> The approach I am using is to search through each inode from number 2
> up. This approach works well with UFS1 file systems as then
> preinitialize all the ino
Hi
the atheros cards are stopping communication after some time
before I got still device timeouts in messages but the lates version on
releng_6 from yesterday simply stops
I can not say much about client or adhoc mode because I have only freebsd
hostap APs running atheros cards a/b/g (Dlink A
54 matches
Mail list logo
