On Fri, Jun 06, 2003 at 09:46:07PM -0700, Tim Kientzle wrote:
> The compiler in 4.7 does not like this:
>
> -std=gnu99
>
> As a result, buildworld of -CURRENT fails
> rather early.
Committers are not required to support building 5-CURRENT, post
5.0-RELEASE on a 4.7 machine. So this is not g
On Sat, 7 Jun 2003, Brad Knowles wrote:
> This is a rather different statement than you previously gave.
I've been extremely consistent in saying that I'm talking about the right
thing to do _now_. I purposely tried to avoid confusing the issue with
detailed plans for the future, however no
On Fri, Jun 06, 2003 at 10:04:34PM +, Sujan Gautam wrote:
> Hi
> I cvsupped to the -current tree for FreeBSD 5.1.
> I am trying to 'make buildworld' but I keep getting these errors.
>
> #make -j4 buildworld
-j4 obscures the error..try again without it. However, as you'd know
by reading this
On Thu, Jun 05, 2003 at 07:41:11PM +, Jan Stocker wrote:
> Another thing with this code.
>
> > > #include
> > > typedef long long longlong;
> > > main()
> > > {
> > > longlong ll=1;
> > > float f;
> > > FILE *file=fopen("conftestval", "w");
> > > f = (float) ll;
> > > fprintf(fi
Alexander Leidinger wrote:
> Isn't this "the famous VIA bug" which every computer magazine reported
> about? I thought we already have a fix in the tree for this:
>
> (2) [EMAIL PROTECTED] # dmesg |grep south
> atapci0: Correcting VIA config for southbridge data corruption bug
It's not the "VIA c
The compiler in 4.7 does not like this:
-std=gnu99
As a result, buildworld of -CURRENT fails
rather early.
Tim Kientzle
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[
TB --- 2003-06-07 04:24:20 - starting CURRENT tinderbox run for i386/pc98
TB --- 2003-06-07 04:24:20 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/i386/pc98
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-06-07 04:26:27 - building world
TB --- cd /home
TB --- 2003-06-07 04:09:09 - starting CURRENT tinderbox run for i386/i386
TB --- 2003-06-07 04:09:09 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/i386/i386
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-06-07 04:11:41 - building world
TB --- cd /home
TB --- 2003-06-07 04:00:18 - starting CURRENT tinderbox run for alpha/alpha
TB --- 2003-06-07 04:00:18 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-06-07 04:02:45 - building world
TB --- cd /
Hi
I cvsupped to the -current tree for FreeBSD 5.1.
I am trying to 'make buildworld' but I keep getting these errors.
#make -j4 buildworld
Running test variables^M
PASS: Test variables detected no regression, output matches.^M
Running test targets^M
PASS: Test targets detected no regression.^M
Ru
On Fri, Jun 06, 2003 at 09:20:16PM -0700, walt wrote:
> cc -O -pipe -mcpu=pentiumpro -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_ -std=gnu99
> -c i387_e_acos.S -o i387_e_acos.o
> {standard input}: Assembler messages:
> {standard input}:19: Error: junk `(__ieee754_acos)' after expression
> {standard input}:
cc -O -pipe -mcpu=pentiumpro -D_IEEE_LIBM -D_ARCH_INDIRECT=i387_ -std=gnu99 -c
i387_e_acos.S -o i387_e_acos.o
{standard input}: Assembler messages:
{standard input}:19: Error: junk `(__ieee754_acos)' after expression
{standard input}:19: Error: junk `(__ieee754_acos)' after expression
*** Error
I guess I'm not the only one with hardware that is unusable with FreeBSD
5.x, but FreeBSD 5.x simply is not installable on Dell PowerEdge 6350
servers. FreeBSD 4.8 works fine on the same hardware. FreeBSD 5.0,
5.1-BETA1, 5.1-BETA2, and 5.1-RC1 all die in sysinstall is detecting
hardware and dr
I've been running freenet (successfully) under jdk 1.4.1 for several weeks
now. Strangely, I keep seeing the following in freenet's logs:
Jun 6, 2003 8:59:31 PM (freenet.node.IPAddressDetector, FThread-22, ERROR):
SocketExceptio
n trying to detect NetworkInterfaces
java.net.SocketException: Bad a
At 6:02 PM -0700 2003/06/06, Doug Barton wrote:
You've failed to grasp the distinction I made between "adventursome bits
in contrib" vs. "adventursome bits in the rest of src/." Also, SMPng is a
really good example of my point... it's a major API change IN FREEBSD CODE
that definitely belongs
At 5:31 PM -0700 2003/06/06, Doug Barton wrote:
On Fri, 6 Jun 2003, Paul Robinson wrote:
let me just ask for clarification on something. Are you stating as the
BIND maintainer around these parts that FreeBSD will never have BIND 9?
No, that's not what I'm saying at all. Someone else already po
Tonight I'v installed a devel/newfile. When it's build it run nawk. In
that time my computer was a very slow reaction without disk operation.
When I'v runned top command I'v seen:
--
last pid: 38039; load averages: 1.58, 1.80, 1.73up 0+01:21:08
05:22:28
53 processes: 3 running, 50 s
On Fri, 06 Jun 2003 10:26:01 -0700
Adam <[EMAIL PROTECTED]> wrote:
> I found a bug in the /ports/net/naios port. More correctly, I think it
> would be in /ports/net/nagios-plugins.
>
> I had Postgres 7.2 installed on my system. I did this manually from source.
> It seems that when you choose to
On Fri, 6 Jun 2003, Per Kristian Hove wrote:
> I've nailed it down to this: geom_vol_ffs assumes that a file system
> is able to fill the partition completely. That's not a valid
> assumption, since the file system size is a multiple of the file
> system block size (in my case 16k bytes = 32 block
Wow you've so completely missed the point that I hesitate to respond
to this, but I suppose I should try.
On Fri, 6 Jun 2003, Brad Knowles wrote:
> At 3:01 AM -0700 2003/06/06, Doug Barton wrote:
>
> > Regardless of whether I agree with the points you make here or not, the
> > FreeBSD devel
On Fri, 6 Jun 2003, Andrew P. Lentvorski, Jr. wrote:
> I seem to remember that part of the issue is that FreeBSD pulls in the
> resolver libraries from BIND.
Only indirectly. The resolver code actually hasn't been updated in a
while, unfortunately.
> I actually would like to see BIND completely
On Fri, 6 Jun 2003, Paul Robinson wrote:
> On Fri, Jun 06, 2003 at 03:01:02AM -0700, Doug Barton wrote:
>
> > FreeBSD development model requires that what we import in -current, for
> > the most part, be what we plan to eventually MFC. That factor alone
> > eliminates the possibility of importing
On Fri, 6 Jun 2003, John Baldwin wrote:
> On 06-Jun-2003 David P. Reese Jr. wrote:
> > I've been getting a lot of these for the last two weeks on my SMP box.
> > This panic is on -CURRENT from earlier today. Scheduler is ULE.
> >
> > lock order reversal
> > 1st 0xc047f820 sched lock (sched lock
Hey Everyone,
I've been MIA with regards to the current list lately, but was checking
the backlog for gbde stuff and came across this thread. Anyway, I've
been running gbde (thanks to Poul for helping me out along the way) on a
SMP (2x2.0ghz Xeon) box with a 3ware RAID 5 (8 drive ATA-133 array)
At 3:01 AM -0700 2003/06/06, Doug Barton wrote:
Regardless of whether I agree with the points you make here or not, the
FreeBSD development model requires that what we import in -current, for
the most part, be what we plan to eventually MFC. That factor alone
eliminates the possibility of impo
On Fri, Jun 06, 2003 at 05:10:21PM +0400, Yar Tikhiy wrote:
> > As far as I can see, this is a client-side problem of CURRENT's
> > ftp(1). FreeBSD ftp(1) was completely replaced with "lukemftp,"
> > ftp client from NetBSD, in CURRENT a year ago. The commit message
> > was promising:
> >
> >
On Fri, 6 Jun 2003, Daniel C. Sobral wrote:
> > I probably am, actually :-). Is the file system in question UFS or UFS2?
>
> [1] [EMAIL PROTECTED]:/opt/home/dcs$ sudo dumpfs /dev/ad0s2f
> magic 19540119 (UFS2) timeFri Jun 6 14:06:59 2003
Hmm. Ok. Well, UFS_EXTATTR_AUTOSTART doesn't rea
imgact_gzip.c seems to be pretty stale. Has anyone considered fixing this? If this
were fixed
then kldload() / linker_load_module() could deal with a gzipped .ko file, and gzipped
elf
executables would work also?
Regards,
David Yeske
__
Do you Yahoo!?
Yahoo! Ca
Hm... Getting a core wont be that easy. After the previously mentionsed
sched_choose() panic:
db> call doadump
Dumping 383 MB
ata0: resetting devices ..
panic: blockable sleep lock (sleep mutex) PCPU 512 @ /usr/src/sys/vm/uma_core.c:1343
cpuid = 0; lapic.id =
Debugger("panic")
Fatal t
Robert Watson wrote:
On Fri, 6 Jun 2003, Daniel C. Sobral wrote:
Robert, I cc'ed you because you are usually guilty anyway... (besides,
there's a ea thingy there :)
I probably am, actually :-). Is the file system in question UFS or UFS2?
[1] [EMAIL PROTECTED]:/opt/home/dcs$ sudo dumpfs /dev/a
On Fri, 6 Jun 2003, Daniel C. Sobral wrote:
> Robert, I cc'ed you because you are usually guilty anyway... (besides,
> there's a ea thingy there :)
I probably am, actually :-). Is the file system in question UFS or UFS2?
To summarize the context of the crash: when UFS_EXTATTR_AUTOSTART is
pres
On Fri, Jun 06, 2003 at 12:39:46PM -0400, John Baldwin wrote:
>
> On 06-Jun-2003 David P. Reese Jr. wrote:
> > I've been getting a lot of these for the last two weeks on my SMP box.
> > This panic is on -CURRENT from earlier today. Scheduler is ULE.
> >
> > lock order reversal
> > 1st 0xc047f8
[Gordon Tetlow, 2003-06-06]
| Thanks for doing this analysis. I've run into the same thing here at
| work but I just haven't had any time to debug it. I'll see if I can
| work something up that'll address this problem.
Given that it should be OK to have a file system smaller than the
partition
Robert, I cc'ed you because you are usually guilty anyway... (besides,
there's a ea thingy there :)
[EMAIL PROTECTED]:/opt/home/dcs$ gdb -k /dos/crash/kernel.17 /dos/crash/vmcore.17
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU Gene
On Fri, Jun 06, 2003 at 01:17:43PM -0600, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Bernd Walter <[EMAIL PROTECTED]> writes:
> : I already wondered how you could route interrupts without ACPI until I
> : booted my printserver with a recent kernel.
>
> PCIBIOS!
Well - I
On Fri, 6 Jun 2003, Bill Moran wrote:
> So, as I see it, the FreeBSD developers carefully evaluate claims of "newer,
> better" and make decisions based on internal testing and experience - not
> marketing hype. Of course, the BIND folks don't want to continue to maintain
> BIND 8, so it's only na
In message: <[EMAIL PROTECTED]>
Bernd Walter <[EMAIL PROTECTED]> writes:
: I already wondered how you could route interrupts without ACPI until I
: booted my printserver with a recent kernel.
PCIBIOS!
Warner
___
[EMAIL PROTECTED] mailing lis
In message: <[EMAIL PROTECTED]>
Bernd Walter <[EMAIL PROTECTED]> writes:
: On Fri, Jun 06, 2003 at 12:36:54PM -0600, M. Warner Losh wrote:
: > In message: <[EMAIL PROTECTED]>
: > John Baldwin <[EMAIL PROTECTED]> writes:
: > : I have a small tweak to the PCI code that re-rout
On Fri, Jun 06, 2003 at 03:04:43PM -0400, John Baldwin wrote:
>
> On 06-Jun-2003 M. Warner Losh wrote:
> > In message: <[EMAIL PROTECTED]>
> > John Baldwin <[EMAIL PROTECTED]> writes:
> > Also, we haven't
> > recorded our info in the underlying pci register. Don't know if that
> > wi
On Fri, Jun 06, 2003 at 12:36:54PM -0600, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> John Baldwin <[EMAIL PROTECTED]> writes:
> : I have a small tweak to the PCI code that re-routes PCI interrupts.
> : Basically, it does two things, 1) make the comment less ia64-specific
On Fri, Jun 06, 2003 at 02:13:31PM -0400, John Baldwin wrote:
> I have a small tweak to the PCI code that re-routes PCI interrupts.
> Basically, it does two things, 1) make the comment less ia64-specific
> and 2) if the interrupt route returns an invalid IRQ (i.e. 255), then
> we don't change the i
TB --- 2003-06-06 18:49:32 - starting CURRENT tinderbox run for i386/pc98
TB --- 2003-06-06 18:49:32 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/i386/pc98
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src
TB --- 2003-06-06 18:51:51 - building world
TB --- cd /home
On 06-Jun-2003 M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> John Baldwin <[EMAIL PROTECTED]> writes:
>: I have a small tweak to the PCI code that re-routes PCI interrupts.
>: Basically, it does two things, 1) make the comment less ia64-specific
>: and 2) if the interrupt r
In message: <[EMAIL PROTECTED]>
John Baldwin <[EMAIL PROTECTED]> writes:
: I have a small tweak to the PCI code that re-routes PCI interrupts.
: Basically, it does two things, 1) make the comment less ia64-specific
: and 2) if the interrupt route returns an invalid IRQ (i.e. 255), then
On Fri Jun 06, 2003 at 11:23:37AM -0700, Gordon Tetlow wrote:
> On Wed, Jun 04, 2003 at 06:57:09PM -0400, The Anarcat wrote:
> > Hi!
> >
> > Recently, I noticed that my samba shares were not automounted on
> > boot.
> >
> > What I understand of it is that netfs_types is defined in
> > rc.d/mountc
On Fri, Jun 06, 2003 at 02:13:31PM -0400, John Baldwin wrote:
> I have a small tweak to the PCI code that re-routes PCI interrupts.
> Basically, it does two things, 1) make the comment less ia64-specific
> and 2) if the interrupt route returns an invalid IRQ (i.e. 255), then
> we don't change the i
On Wed, Jun 04, 2003 at 06:57:09PM -0400, The Anarcat wrote:
> Hi!
>
> Recently, I noticed that my samba shares were not automounted on
> boot.
>
> What I understand of it is that netfs_types is defined in
> rc.d/mountcritlocal, but not in rc.d/mountcritremote, which makes the
> code:
You are a
On Fri, Jun 06, 2003 at 07:38:36PM +0200, Per Kristian Hove wrote:
> I've nailed it down to this: geom_vol_ffs assumes that a file system
> is able to fill the partition completely. That's not a valid
> assumption, since the file system size is a multiple of the file
> system block size (in my case
I have a small tweak to the PCI code that re-routes PCI interrupts.
Basically, it does two things, 1) make the comment less ia64-specific
and 2) if the interrupt route returns an invalid IRQ (i.e. 255), then
we don't change the intline. In other words, if we can't route the
interrupt, we just assu
I thought it was the Monica Lewinsky edition of FreeBSD.
On Thursday, June 5, 2003, at 07:20 PM, Mike Barcroft wrote:
[EMAIL PROTECTED] <[EMAIL PROTECTED]> writes:
What does "i386-undermydesk-freebsd" refer to? What is it used for?
Is there
an "i386-inthedrawer-freebsd", or "i386-intheXbox-freeb
On Thu, 5 Jun 2003, Mike Barcroft wrote:
> [EMAIL PROTECTED] <[EMAIL PROTECTED]> writes:
> > What does "i386-undermydesk-freebsd" refer to? What is it used for? Is there
> > an "i386-inthedrawer-freebsd", or "i386-intheXbox-freebsd"?
>
> As a general rule of thumb, FreeBSD boxes should be kept un
[EMAIL PROTECTED] <[EMAIL PROTECTED]> writes:
> What does "i386-undermydesk-freebsd" refer to? What is it used for? Is there
> an "i386-inthedrawer-freebsd", or "i386-intheXbox-freebsd"?
As a general rule of thumb, FreeBSD boxes should be kept under desks.
If your system isn't under a desk, consid
I've nailed it down to this: geom_vol_ffs assumes that a file system
is able to fill the partition completely. That's not a valid
assumption, since the file system size is a multiple of the file
system block size (in my case 16k bytes = 32 blocks), and the
partition size is/should be a multiple of
Adam wrote:
I found a bug in the /ports/net/naios port. More correctly, I think it
would be in /ports/net/nagios-plugins.
I had Postgres 7.2 installed on my system. I did this manually from
source. It seems that when you choose to have postgres support for
nagios, it doesn't check to see if th
What does "i386-undermydesk-freebsd" refer to? What is it used for? Is there
an "i386-inthedrawer-freebsd", or "i386-intheXbox-freebsd"?
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
I found a bug in the /ports/net/naios port. More correctly, I think it
would be in /ports/net/nagios-plugins.
I had Postgres 7.2 installed on my system. I did this manually from source.
It seems that when you choose to have postgres support for nagios, it
doesn't check to see if the library exi
Dear Hackers,
please find attached patch for the hcsecd(8) Bluetooth link keys/PIN
codes management daemon. this patch is against the latest release
http://www.geocities.com/m_evmenkin/ngbt-fbsd-20030604.tar.gz
hcsecd(8) is now able to cache link keys that were generated from the
PIN codes. to p
John Baldwin wrote:
>
>
>Please try:
>
>Index: pci.c
>===
>RCS file: /usr/cvs/src/sys/dev/pci/pci.c,v
>retrieving revision 1.215
>diff -u -r1.215 pci.c
>--- pci.c 31 May 2003 20:34:36 - 1.215
>+++ pci.c 2 Jun 2003
> Maybe you could show us your /etc/make.conf and the exact
> command line (and environment) to build world then?
>
it now dies with the appended error.
make.conf:
# -- use.perl generated deltas -- #
# Created: Tue May 20 15:18:24 2003
# Setting to use base perl from ports:
PERL_VER=5.6.1
PERL_VE
Thanks for the suggestion about recompiling the nvidia driver, but I do after
each kernel compile and install, so that isn't the answer, though not a bad
idea. Recompiles of both the Linux-nvidia-port and the standalone-nvidia
driver failed, so I am in the process, now, of backing out of everything
On 06-Jun-2003 David P. Reese Jr. wrote:
> I've been getting a lot of these for the last two weeks on my SMP box.
> This panic is on -CURRENT from earlier today. Scheduler is ULE.
>
> lock order reversal
> 1st 0xc047f820 sched lock (sched lock) @ /usr/src/sys/kern/kern_intr.c:548
> 2nd 0xc04b
On 05-Jun-2003 Alexander Leidinger wrote:
> On Thu, 05 Jun 2003 11:33:13 -0400 (EDT)
> John Baldwin <[EMAIL PROTECTED]> wrote:
>
>>
>> On 05-Jun-2003 Alexander Leidinger wrote:
>> > Hi,
>> >
>> > is there a way to teach our ACPI implementation about
>> >
>> > [EMAIL PROTECTED]:7:4: class=0x068
If you started X (by itself) and the screen flickered on and off, then I
would suspect that it is being told to use a video mode that your card, or
more likely - monitor, won't support. If that is true, then you could be in
danger of damaging your monitor.
1) Got all available documentation avail
Hello,
I am having an issue with using acpi on a Compaq Armada M700. Without ACPI
everything work's great with the exception of APM. (I had it working on a
prior install, now for some reason it isn't). I've just lived with the fact
that ACPI + PCMCIA didn't appear to like each other. It does ran
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 06 June 2003 14.21, Soeren Schmidt wrote:
>
> Get me a 3112 based controller on my desk :)
>
If this is an option, let me know what make and model you would need and I
will make sure we get a sponsor for such a controller from the sponsor o
Can't say I've ever had a problem with my HP DJ5550 on a USB port.
On Thu, 5 Jun 2003 16:26:25 +0200
Bernd Walter <[EMAIL PROTECTED]> wrote:
> On Thu, Jun 05, 2003 at 04:11:23PM +0200, Alexander Leidinger wrote:
> > On Thu, 5 Jun 2003 13:49:25 +0200
> > Bernd Walter <[EMAIL PROTECTED]> wrote:
> >
same error.
On Thu, Jun 05, 2003 at 11:17:07PM +0300, Ruslan Ermilov wrote:
> On Thu, Jun 05, 2003 at 03:28:01PM -0400, Anthony Schneider wrote:
> > kerberos5 sources cvsup'd from about 30 minutes ago.
> >
> [...]
> > cc -O -pipe -mcpu=pentiumpro
> > -I/usr/src/kerberos5/lib/libkrb5/../../../cry
On Fri, 6 Jun 2003 10:25:55 -0400 (EDT)
"Matthew N. Dodd" <[EMAIL PROTECTED]> wrote:
> This is what I'll likely commit in the short term.
[globally disable the check with a sysctl]
To have this at boot time we have to set it in loader.conf, but then we
not only do not check for viapm, we also do
Paul Robinson wrote:
On Fri, Jun 06, 2003 at 03:01:02AM -0700, Doug Barton wrote:
FreeBSD development model requires that what we import in -current, for
the most part, be what we plan to eventually MFC. That factor alone
eliminates the possibility of importing BIND 9 at this time.
Sorry to wade i
On Fri, 6 Jun 2003, Alexander Leidinger wrote:
> This problem is under investigation. We already know why this error gets
> printed, but there is still a discussion how to fix it cleanly.
This is what I'll likely commit in the short term.
Index: pci.c
=
On Fri, Jun 06, 2003 at 03:01:02AM -0700, Doug Barton wrote:
> On Fri, 6 Jun 2003, Brad Knowles wrote:
>
> > At 12:09 AM -0700 2003/06/06, Doug Barton wrote:
> >
> > > FYI, for those wondering why I'm not considering BIND 9 for import, please
> > > see http://people.freebsd.org/~dougb/whybind8.h
It seems dave wrote:
> > It seems David Leimbach wrote:
> >> So... I have this nice SATA drive and controller which I believe is
> >> supported
> >> by FreeBSD but not in the default build for releases.
> >>
> >> What is the best way to cross-build a version of FreeBSD's release
> >> ISOs
> >> th
On Friday, June 6, 2003, at 08:53 AM, Soeren Schmidt wrote:
It seems David Leimbach wrote:
So... I have this nice SATA drive and controller which I believe is
supported
by FreeBSD but not in the default build for releases.
What is the best way to cross-build a version of FreeBSD's release
ISOs
t
On Fri, 6 Jun 2003 08:48:17 -0400
"Robin P. Blanchard" <[EMAIL PROTECTED]> wrote:
> Upon launching samba-2.2.8a (via ports) on the below system, the machine
> immediately hard freezes. I've included interesting portions of kernel
> config. Any suggestions how I can acquire more useful information
It seems David Leimbach wrote:
> So... I have this nice SATA drive and controller which I believe is
> supported
> by FreeBSD but not in the default build for releases.
>
> What is the best way to cross-build a version of FreeBSD's release ISOs
> that
> will include drivers not included in the d
On 2003.06.06 14:36:44 +0100, Paul Robinson wrote:
> This is almost as bad as OpenBSD sticking with BIND 4...
OpenBSD has actually uses BIND 9 now...
--
Simon L. Nielsen
pgp0.pgp
Description: PGP signature
On Fri, Jun 06, 2003 at 03:01:02AM -0700, Doug Barton wrote:
> FreeBSD development model requires that what we import in -current, for
> the most part, be what we plan to eventually MFC. That factor alone
> eliminates the possibility of importing BIND 9 at this time.
Sorry to wade in here - let m
On Thu, Jun 05, 2003 at 03:28:01PM -0400, Anthony Schneider wrote:
> kerberos5 sources cvsup'd from about 30 minutes ago.
>
[...]
> cc -O -pipe -mcpu=pentiumpro
> -I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/krb5
> -I/usr/src/kerberos5/lib/libkrb5/../../../crypto/heimdal/lib/asn
On Thu, 05 Jun 2003 13:56:15 -0500, Jeremy Messenger <[EMAIL PROTECTED]> wrote:
On Thu, 5 Jun 2003 20:56:50 +0200, Michael Nottebrock
<[EMAIL PROTECTED]> wrote:
On Thursday 05 June 2003 20:10, Jeremy Messenger wrote:
I own the same chipest here, which it is support in 4.x and no longer
in
5.x.
On Sat, Feb 15, 2003 at 05:46:37PM +0300, Yar Tikhiy wrote:
> On Fri, Feb 14, 2003 at 03:37:49PM -0800, Kris Kennaway wrote:
> > On Fri, Feb 14, 2003 at 03:34:06PM -0800, Kris Kennaway wrote:
> > > Since upgrading bento to running 5.0, it appears that I can no longer
> > > download multiple files f
So... I have this nice SATA drive and controller which I believe is
supported
by FreeBSD but not in the default build for releases.
What is the best way to cross-build a version of FreeBSD's release ISOs
that
will include drivers not included in the default distribution? Or is
it possible
to s
On Thu, 05 Jun 2003 10:14:39 -0700
Terry Lambert <[EMAIL PROTECTED]> wrote:
> Here's the German page:
>
> http://www.hardtecs4u.com/reviews/2001/ep8kta3-mod/index12.php
>
> Basically:
>
> o Disable PCI master read caching
> o Lower PCI latency to "0-32"
> o Disable PCI delay t
Another thing with this code.
> > #include
> > typedef long long longlong;
> > main()
> > {
> > longlong ll=1;
> > float f;
> > FILE *file=fopen("conftestval", "w");
> > f = (float) ll;
> > fprintf(file,"%g\n",f);
> > close(file);
I think this has to be "fclose"
> > exit (
Upon launching samba-2.2.8a (via ports) on the below system, the machine
immediately hard freezes. I've included interesting portions of kernel
config. Any suggestions how I can acquire more useful information ?
# uname -a
FreeBSD darwin 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Thu Jun 5 12:28:54 EDT
kerberos5 sources cvsup'd from about 30 minutes ago.
thanks.
-Anthony.
FreeBSD tool. 5.1-BETA FreeBSD 5.1-BETA #1: Wed May 21 10:11:40 EDT 2003 [EMAIL
PROTECTED]:/usr/src/sys/i386/compile/TOOL i386
===> doc
===> lib
===> lib/libroken
===> lib/libvers
===> lib/libasn1
===> lib/libhdb
===> l
On Thu, 5 Jun 2003 20:56:50 +0200, Michael Nottebrock
<[EMAIL PROTECTED]> wrote:
On Thursday 05 June 2003 20:10, Jeremy Messenger wrote:
I own the same chipest here, which it is support in 4.x and no longer in
5.x.. :-( Note that, I only check in the 5.x's NOTES
You didn't check in the right NOT
On Thursday 05 June 2003 20:10, Jeremy Messenger wrote:
> I own the same chipest here, which it is support in 4.x and no longer in
> 5.x.. :-( Note that, I only check in the 5.x's NOTES
You didn't check in the right NOTES then. 5-CURRENT has different NOTES files,
one general, machine independen
On Thu, 05 Jun 2003 13:10:35 -0500, Jeremy Messenger <[EMAIL PROTECTED]> wrote:
On Thu, 5 Jun 2003 16:14:25 +0200, Alexander Leidinger
<[EMAIL PROTECTED]> wrote:
Hi,
is there a way to teach our ACPI implementation about
[EMAIL PROTECTED]:7:4: class=0x068000 card=0x chip=0x30571106 rev=
On Thu, 5 Jun 2003 16:14:25 +0200, Alexander Leidinger
<[EMAIL PROTECTED]> wrote:
Hi,
is there a way to teach our ACPI implementation about
[EMAIL PROTECTED]:7:4: class=0x068000 card=0x chip=0x30571106 rev=0x40
hdr=0x00
vendor = 'VIA Technologies Inc'
device = 'VT82C686A/B ACPI Pow
Lars Eggert writes:
> Robert Watson wrote: |
> >|---++---+--
> -|
> >| || | The 20030228 vendor
> |
> >| Fresh ACPI-CA | -- | --| sources have been
On Thu, 05 Jun 2003 10:14:39 -0700
Terry Lambert <[EMAIL PROTECTED]> wrote:
> Alexander Leidinger wrote:
> > Terry Lambert <[EMAIL PROTECTED]> wrote:
> > > Be aware that if your machine is a "B" (82C686B), then you have
> >
> > It is.
I'm not that sure anymore... see below.
> > > the buggy vers
After having installed 5.1-RC1, the nvidia driver, and named, are
back in full operation. Yeah!
On Thu, 5 Jun 2003 [EMAIL PROTECTED] wrote:
> Thanks for the suggestion about recompiling the nvidia driver, but I do after
> each kernel compile and install, so that isn't the answer, though not a b
On Thu, 05 Jun 2003 14:57:19 -0500
Jeremy Messenger <[EMAIL PROTECTED]> wrote:
> > Do'h! You are right that I didn't check in /usr/src/sys/conf/.. It does
> > exist and I am doing the rebuild kernel right now.. Thanks..
>
> Here's the result:
>
> # dmesg | grep v
On Thu, 5 Jun 2003, Scott Long wrote:
> Larry Rosenman wrote:
> > For the record, yesterday's sources STILL produce the panic at 0x7 for
> > me on transition to battery.
> >
> > I can get more crashdumps/kernels if someone asks.
> > I've mentioned this for the last ~1.5 months.
>
> The official pos
Alexander Leidinger wrote:
> On Thu, 05 Jun 2003 11:33:13 -0400 (EDT)
> John Baldwin <[EMAIL PROTECTED]> wrote:
> > It doesn't really need to know about it. Perhaps acpi should include
> > a dummy driver similar to the 'hostb' driver to "eat" such devices.
>
> Does this mean it should already dis
I was playing with libkse and got the follow LOR:
lock order reversal
1st 0xc6ce0aa8 sigacts (sigacts) @ /local/usr.src/sys/kern/subr_trap.c:248
2nd 0xc6cbc250 process lock (process lock) @ /local/usr.src/sys/kern/kern_threa
d.c:1439
Stack backtrace:
backtrace(c04fd0b6,c6cbc250,c04f9a3a,c04f9a3a
Alexander Leidinger wrote:
> Terry Lambert <[EMAIL PROTECTED]> wrote:
> > Be aware that if your machine is a "B" (82C686B), then you have
>
> It is.
>
> > the buggy version of the chip; you need to eiter not use the
> > second IDE channel for anything, or you need a BIOS update, or
>
> Not using
On Wed, Jun 04, 2003 at 09:32:32AM -0700, Maksim Yevmenkin wrote:
> Dear Hackers,
>
> Another release is available for download at
>
> http://www.geocities.com/m_evmenkin/ngbt-fbsd-20030604.tar.gz
>
> I am regret to announce that this is probably the last release.
> My company has announced tha
Larry Rosenman wrote:
--On Thursday, June 05, 2003 18:59:49 +0200 Erik Paulsen Skaalerud
<[EMAIL PROTECTED]> wrote:
> FYI, I still see the ACPI messages described in the "Re: ACPI-0293
> (and
> 0166) errors"-thread on -current ca. 5/9/2003 on
yesterday's -current.
>
> Lars
Yeah, ACPI is causing
--On Thursday, June 05, 2003 18:59:49 +0200 Erik Paulsen Skaalerud
<[EMAIL PROTECTED]> wrote:
> FYI, I still see the ACPI messages described in the "Re: ACPI-0293
> (and
> 0166) errors"-thread on -current ca. 5/9/2003 on
yesterday's -current.
>
> Lars
Yeah, ACPI is causing many problems these d
1 - 100 of 130 matches
Mail list logo
