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
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
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
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
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:
> >
> >
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
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)
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
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, 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
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, 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
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
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
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
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
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
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
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
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}:
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
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 /
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: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
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 "[
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
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
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 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 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
101 - 130 of 130 matches
Mail list logo
