Hi,
I was adviced to forward here, so that more poeple
can see it. It was originally posted to fs@ and [EMAIL PROTECTED]
Regards,
- Forwarded message from "R. Imura" <[EMAIL PROTECTED]> -
Date: Mon, 3 Nov 2003 01:42:18 +0900
From: "R. Imura" <[EMAIL PROTECTED]>
Subject: [patch] combine
TB --- 2003-11-03 05:00:01 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-11-03 05:00:01 - starting CURRENT tinderbox run for alpha/alpha
TB --- 2003-11-03 05:00:01 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha
TB --- /usr/bin/cvs -f -R -q -d/home/
On 03 Nov 2003, Mark Nipper wrote:
> Uh oh! It's that last part where there are the two extra
> entries for the two ACL added groups, but no GID seems to have
> been stored with each entry, whereas the example in the daemon
> news article does actually show GID's in these places.
Of
I think I might have found a bug in ACL's under UFS2 with
5.1-RELEASE-p10. I have been using ACL's successfully for awhile
now, but I'd never played with default ACL's for directories and
files you create underneath said directories until I came across
the daemon news article at:
---
http:
On Sunday 02 November 2003 03:40 pm, Harald Schmalzbauer wrote:
> Hello, grumpf,
>
> after having had the first spontanous reboot with -current for a long time
> I wanted to look for hw.ata.atapi_dma (since the machine crashed (without
> ANY report) when I tried to access the CD) and found it's gon
Jeff Roberson wrote:
I'm not able to reproduce this at all. Could any of you folks that are
experiencing this problem update to sched_ule.c rev 1.75 and tell me if it
persists?
I just cvsupped again today, so I'm now on rev 1.75 and using moused
again with no problems. Whatever was broke seems f
TB --- 2003-11-03 00:13:02 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-11-03 00:13:02 - starting CURRENT tinderbox run for sparc64/sparc64
TB --- 2003-11-03 00:13:02 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/sparc64/sparc64
TB --- /usr/bin/cvs -f -R -q
On Mon, 03 Nov 2003 01:13:54 +0100, Sebastijan Vacun
<[EMAIL PROTECTED]> wrote:
Helo!
I wanna install opendchub on my FreeBSD server.
My system is: 4.9-STABLE FreeBSD
I have installed perl-5.6.1_14.
But when I want to make net/opendchub I got this:
###
Helo!
I wanna install opendchub on my FreeBSD server.
My system is: 4.9-STABLE FreeBSD
I have installed perl-5.6.1_14.
But when I want to make net/opendchub I got this:
# make
===> opendchub-0.7.12 needs at least perl 5.6.1 to build.
#
###
TB --- 2003-11-02 22:44:26 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-11-02 22:44:26 - starting CURRENT tinderbox run for ia64/ia64
TB --- 2003-11-02 22:44:26 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs
You can use ident(1) to extract the CVS version numbers of the files
that were used to compile your respective kernels.
Try this for a list of files and their respective versions:
'ident /boot/kernel/kernel /boot/kernel.old/kernel | sort'
Seeya...Q
On Sun, 2003-11-02 at 08:07, Tamás R. wrote:
Hello, grumpf,
after having had the first spontanous reboot with -current for a long time I
wanted to look for hw.ata.atapi_dma (since the machine crashed (without ANY
report) when I tried to access the CD) and found it's gone.
The man page still tells my stories about that sysctl.
What news di
Jeff Roberson <[EMAIL PROTECTED]> wrote:
> On Fri, 31 Oct 2003, Bruno Van Den Bossche wrote:
[...]
> > I recently had to complete a little piece of software in a course on
> > parallel computing. I've put it online[1] (we only had to write the
> > pract2.cpp file). It calculates the inverse of a
Heum cvsuped earlier today (Sun 2 Nov 2003), after buildworld/installworld ive have
noticed a few things i cant get working right.. First off the system seams to panic on
background fsck
i get this message:
dev = ad1s1, block = 1, fs = /mnt/mellan
panic: ffs_blkfree: freeing free block
irq 1 atk
Hello. I just had a panic here. I'm running CURRENT as of 31st of October,
platform is i386. I have a crashdump available if anyone wants to take a
look at this.
Here's some output from gdb -k:
[EMAIL PROTECTED]:~/tmp/debug/2003-10-31 > gdb -k kernel.debug vmcore.6
GNU gdb 5.2.1 (FreeBSD)
Copyr
On Sun, 2 Nov 2003, Schnoopay wrote:
> >> Are you using moused? Is this SMP or UP? What CPUs are you using?
> > >
> > > Thanks,
> > > Jeff
> >
> > I am having similar problems after my last cvsup (10-31-03) also using a
> > USB MS Intellimouse. Mouse is slow to respond under ULE but fine unde
On Sun, 2 Nov 2003, sebastian ssmoller wrote:
> On Sun, 2003-11-02 at 15:18, Andre Guibert de Bruet wrote:
> > On Sun, 2 Nov 2003, sebastian ssmoller wrote:
> >
> > > recently i installed freebsd 5 current on an asus m2400n notebook. most
> > > things work fine so far, but one ugly problem left:
On Sat, Nov 01, 2003 at 01:26:10PM -0800, Steve Wingate wrote:
> STABLE taking the entire first disk (works fine)
> CURRENT taking the first 1/3 of the second disk and
> backup data taking the remaining 2/3 of the second disk.
>
> I have installed CURRENT (at least 8 times) but I cannot get it to
wsgroups that
suggests that this incompatibility between 4.x and 5.x has in some
sense been corrected in -current. I don't know any details.
See also:
<http://www.freebsd.org/cgi/getmsg.cgi?fetch=446102+449665+/usr/local/www/db/text/2003/freebsd-current/20031102.freebsd-current>
Hi
The matcd(4) driver needs an active maintainer. Do we have any
volunteers? Without active maintenance/use, the driver will rot,
die and be removed from the tree.
Speak up now!
M
--
Mark Murray
iumop ap!sdn w,I idlaH
___
[EMAIL PROTECTED] mailing lis
Date: Sat, 1 Nov 2003 12:23:37 -0800 (PST)
From: Jean-Marc Zucconi <[EMAIL PROTECTED]>
Subject: Re: buildworld error: rm: tar: is a directory
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
eculp writes:
> Mensaje citado por Ruslan Ermilov <[EMAIL PROTECTED]>:
> |
On Sunday 02 November 2003 17:01, Soren Schmidt wrote:
> It seems Harald Schmalzbauer wrote:
> > Ha, stop. Today it doesn't work as non-root anymore.
> > I'm sure with -current some days ago and the same patch it worked without
> > root privileges.
> > I can't follow that.
>
> Thats a feature of at
Is this available anywhere ?
-Søren
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Sun, 2003-11-02 at 15:18, Andre Guibert de Bruet wrote:
> On Sun, 2 Nov 2003, sebastian ssmoller wrote:
>
> > hi,
> > recently i installed freebsd 5 current on an asus m2400n notebook. most
> > things work fine so far, but one ugly problem left: every time i plug in
> > my usb mouse the system
Hi,
Yesterday I upgraded -current on my Ultra5 from a August 24th -current,
and now it hangs on boot, after logging error messages like these:
ad0: WARNING - SETFEATURES recovered from missing interrupt
ad0: WARNING - SETFEATURES recovered from missing interrupt
ad0: WARNING - SET_MULTI recovered
It seems Harald Schmalzbauer wrote:
>
> Ha, stop. Today it doesn't work as non-root anymore.
> I'm sure with -current some days ago and the same patch it worked without root
> privileges.
> I can't follow that.
Thats a feature of atapi-cd now being under GEOM..
The device nodes are now mode 640
On Sat, Nov 01, 2003 at 06:24:18PM -0500, Barney Wolff wrote:
> Er, how is it possible to send a UDP packet > 65535? Last time I looked
> it was a 16-bit field.
This is explained in section 4. of RFC 2675, "IPv6 Jumbograms",
http://www.ietf.org/rfc/rfc2675.txt
--
Craig Rodrigues
http:/
On Sun, 2 Nov 2003, sebastian ssmoller wrote:
> hi,
> recently i installed freebsd 5 current on an asus m2400n notebook. most
> things work fine so far, but one ugly problem left: every time i plug in
> my usb mouse the system freezes. the system is really dead then (needs
> to be rebooted) - eve
On Saturday 01 November 2003 23:06, Artem 'Zazoobr' Ignatjev wrote:
> On Sat, 01.11.2003, at 11:08, Harald Schmalzbauer ÐÉÛÅÔ:
*SNIP*
> > There were great tools which could do that automatically but they don't
> > work any more for a reason I cannot follow.
>
> I've ran accross this one some time
Are you using moused? Is this SMP or UP? What CPUs are you using?
>
> Thanks,
> Jeff
I am having similar problems after my last cvsup (10-31-03) also using a
USB MS Intellimouse. Mouse is slow to respond under ULE but fine under
4BSD. The mouse feels like it's being sampled at a slow rate.
>Submitter-Id: current-users
>Originator:Kostyuk Oleg
>Organization:
>Confidential: no
>Synopsis: /etc/rc.d/ipsec starts not in time
>Severity: serious
>Priority: medium
>Category: conf
>Class: sw-bug
>Release: FreeBSD 5.1-CURRENT i386
>Environment:
hi,
recently i installed freebsd 5 current on an asus m2400n notebook. most
things work fine so far, but one ugly problem left: every time i plug in
my usb mouse the system freezes. the system is really dead then (needs
to be rebooted) - even the light on the optical mouse is swiched off.
Any idea
On Sat, 1 Nov 2003, Terry Lambert wrote:
> I think at this point, you are going to have to look at the
> sources; IMO, it's a problem in some code that calls the
> ether_output() function directly with too large a packet, and
> since NFS doesn't manually implement TCP, that's not it.
>
> Hmmm. Is
I'm running -CURRENT as of Nov 1. I recall this 56x IDE drive working without too much
trouble on 4.8, but it's having some serious issues now. Are the following a result
from the drive being sketchy, or -CURRENT? I don't think it's a very high quality
drive, but it seemed to work okay before. A
On Fri, 31 Oct 2003, Sam Leffler wrote:
> On Friday 31 October 2003 09:04 am, Bruce Evans wrote:
>
> > My simple make benchmark now takes infinitely longer with ULE under SMP,
> > since make -j 16 with ULE under SMP now hangs nfs after about a minute.
> > 4BSD works better. However, some networki
Hello.
Simlar one was reported but not exactly this one:
lock order reversal
1st 0xc4516e90 rtentry (rtentry) @ /usr/src/sys/net/rtsock.c:388
2nd 0xc43e327c radix node head (radix node head) @ /usr/src/sys/net/route.c:133
Stack backtrace:
backtrace(c05c6672,c43e327c,c05cb651,c05cb651,c05cb6a7)
Hello.
Kernel from October 31st, while doing 'killall ssh'.
panic: mtx_lock() of spin mutex @ /usr/src/sys/net/route.c:99
db> trace
Debugger [...]
panic [...]
_mtx_lock_flags [...]
[...] rtalloc_ign+0x4b
[...] rtalloc+0x19
[...] tcp_rtlookup+0x39
[...] tcp_gettaocache+0x11
[...] tcp_output+0x161
Hello.
I got this panic while doing 'killall -9 ppp' on FreeBSD 5-CURRENT (kernel
from October 31st):
panic: mtx_lock() of spin mytex @ /usr/src/sys/netinet/in_pcb.c:866
[...]
db> trace
[...]
Debugger [...]
panic [...]
_mtx_lock_flags [...]
[...] in_losing+0x40
[...] tcp_timer_rexmt+0x23e
[...] s
TB --- 2003-11-02 10:46:59 - tinderbox 2.2 running on cueball.rtp.FreeBSD.org
TB --- 2003-11-02 10:46:59 - starting CURRENT tinderbox run for ia64/ia64
TB --- 2003-11-02 10:46:59 - checking out the source tree
TB --- cd /home/des/tinderbox/CURRENT/ia64/ia64
TB --- /usr/bin/cvs -f -R -q -d/home/ncvs
On Sat, 1 Nov 2003, Bruce Evans wrote:
> On Fri, 31 Oct 2003, Jeff Roberson wrote:
>
> > I have commited my SMP fixes. I would appreciate it if you could post
> > update results. ULE now outperforms 4BSD in a single threaded kernel
> > compile and performs almost identically in a 16 way make. I
On Sun, 2 Nov 2003, 11:18+0200, Valentin Nechayev wrote:
> Wed, Oct 22, 2003 at 03:14:33, strick (Dan Strick) wrote about "UFS file system
> problem in either stable or current":
>
> DS> There seems to be an inconsistency between release 4.9-RC and 5.1 ufs
> DS> support. If I fsck the same ufs
Wed, Oct 22, 2003 at 03:14:33, strick (Dan Strick) wrote about "UFS file system
problem in either stable or current":
DS> There seems to be an inconsistency between release 4.9-RC and 5.1 ufs
DS> support. If I fsck the same ufs (type 1 of course) file system on
DS> both releases, each claims t
Sat, Nov 01, 2003 at 20:38:36, s.wingate (Steve Wingate) wrote about "Re: Dualbooting
STABLE & CURRENT":
> >> I don't like the sound of that. I'll just stick with STABLE until 5.x is
> >> really ready.
>> -STABLE will have the same problem since its in boot0 and the BIOS, not
>> the OS on the p
43 matches
Mail list logo
