In message [EMAIL PROTECTED], Matthew Jacob writes:
Well, I don't agree with the design here, but it is what it is. I'll
make the change that you've added a requirement for.
This is nothing new, but it is new that we can and do enforce it.
--
Poul-Henning Kamp | UNIX since Zilog Zeus
I have two -current boxes, one from yesterday, one from a week ago. The most recent is
the NFS server which locks whenever the other one performs a 'make extract' in the
NFS-mounted /usr partition. The exports file is the following:
/usr -alldirs -maproot=root
and the mount options in
While build kernel on RELENG_4 machine I have following warnings (they
prevent success build unless -Werror disabled)
/ext/current/src# make -j8 buildkernel
...
/ext/current/src/sys/kern/kern_descrip.c:1914: warning: inlining failed
in call to `_fgetvp'
if you use portupgrade and you want to pass make arguments you should look at
/usr/local/etc/pkgtools.conf
my example :
MAKE_ARGS = {
'irc/bitchx-*' = 'WITH_SSL=1 WITH_IPV6=1',
'net/samba*' = 'WITHOUT_CUPS=1',
'databases/mysql323-server*' = 'SKIP_INSTALL_DB=1',
Peter Jeremy wrote:
As with the Linux driver, communication happens at the ethernet link
layer, using protocol number 0x0666 (entertaining choice).
If Linux is using 0x0666, we should probably pick a different number
since we're not wire compatible. Though coming up with a common
protocol
There seems to be an inconsistency between release 4.9-RC and 5.1 ufs
support. If I fsck the same ufs (type 1 of course) file system on
both releases, each claims that the other has left incorrect
summary data in the superblock. Presumably only one can be correct.
I just don't know which to
On Wed, Oct 22, 2003 at 12:30:41AM -0700, Terry Lambert wrote:
Peter Jeremy wrote:
As with the Linux driver, communication happens at the ethernet link
layer, using protocol number 0x0666 (entertaining choice).
If Linux is using 0x0666, we should probably pick a different number
since
Hi,
(Not quite for current@, but that's where leading edge is going on)
For the new house we are building I'm looking into EIB.
(European Installation Bus).
And I'm searching for EIB/IP gateways and applications on FreeBSD.
Has anybody used these kinds of tools with FBSD (or Linux)
Or even
Hello.
On 2003/10/13 02:09:54, Oliver Fischer wrote:
My notebook was a little bit panic this night. After rebooting I found
this message in my system log:
panic: softdep_deallocate_dependencies: dangling deps
I've been seeing this panic on NetFinity 6000R since end of September.
-CURRENT
Hi,
Urgend question, wanna help a collegue, who secured a router,
but trying to scan ports fails with -current.
I don't want to blame anybody, I know what the policy of current
is. If I can't get quick help on this I use a Windows tool,
no problem. I only want to save me the work to install this
thanks alot for your reply...
but, after patched my FreeBSD with your patch, i still get errors
root pwd
/home/fajri/data/usr/src/release
root patch genesis-patch-ae
root make release CHROOTDIR=/home/fajri/data/root BUILDNAME=FAJRI
CVSROOT=/home/fajri/data/usr
On Tue, 2003-10-21 at 07:59, Terry Lambert wrote:
Christian Brueffer wrote:
I don't think so. I tried that on my A7M266D with no effect. I believe
something in recent pmap code doesn't like this mobo, or maybe dual
athlons in general. I can run RELENG_5_1 rock solid, and -current from
On Wednesday 22 October 2003 22:15, Anthony Fajri wrote:
thanks alot for your reply...
but, after patched my FreeBSD with your patch, i still get errors
Err the patch isn't designed to fix your problem, it is just written by me to
make things a bit easier.
I suggest re-reading my
Dan Strick wrote:
There seems to be an inconsistency between release 4.9-RC and 5.1 ufs
support. If I fsck the same ufs (type 1 of course) file system on
both releases, each claims that the other has left incorrect
summary data in the superblock. Presumably only one can be correct.
I just don't
It isn't the cannot sleep from geometry calls that is twitting me a
bit, it's the I cannot tell at my call depth in the stack whether some
dork above can't tolerate a sleep[1]. If I've missed some usage point
with the SMP stuff that I *can* tell this with ease, enlighten me.
-matt
[1]: by
On Tue, Oct 21, 2003 at 11:49:41AM -0700, Kris Kennaway wrote:
On Tue, Oct 21, 2003 at 10:46:12PM +0400, Yar Tikhiy wrote:
This particular LOR happened upon getting out of swap.
My knowledge is insufficient to tell if it's a sign of
a real problem or just a false positive.
See my message
From: Doug Rabson [EMAIL PROTECTED]
I also get random segfaults and ICEs on my dual 1900+ system with recent
current. It certainly isn't hardware problems since older kernels work
very nicely. I haven't got around to trying to diagnose what is causing
it yet though. I was planning to try
Andreas Klemm wrote:
Hi,
Urgend question, wanna help a collegue, who secured a router,
but trying to scan ports fails with -current.
I don't want to blame anybody, I know what the policy of current
is. If I can't get quick help on this I use a Windows tool,
no problem. I only want to save me the
Hi,
I tried to use geom_fox to implement multipathing on my machine. The setup
is: Dell PowerEdge 2600, 2 QLogic 2312 FC Adapters, 2 Brocade 2800 Switches,
1 Compaq HSG 80 FC array with 2 redundant FC controllers. I wrote the magic
labels on the disks, according to the script in the announce
In message [EMAIL PROTECTED], =?iso-8859-2?q?S=B3awek_=AFak?=
writes:
Hi,
I tried to use geom_fox to implement multipathing on my machine. The setup
is: Dell PowerEdge 2600, 2 QLogic 2312 FC Adapters, 2 Brocade 2800 Switches,
1 Compaq HSG 80 FC array with 2 redundant FC controllers. I wrote the
On Wed, Oct 22, 2003 at 03:30:41PM +0100, Peter Edwards wrote:
The patch applied by the port appears bogus. It adds braces around an
if that stops it executing the way it was intended. I've a sneaking
suspicion that the braces were added for clarity, but the indentation
in the original file
Some (kde) applications now have a warning appear in xconsole:
Warning: pid 595 used static ldt allocation.
See the i386_set_ldt man page for more info
Warning: pid 596 used static ldt allocation.
See the i386_set_ldt man page for more info
Should I worry about that? Rebuild KDE?
--
Chris
On Wed, 2003-10-22 at 11:31, Andreas Klemm wrote:
On Wed, Oct 22, 2003 at 03:30:41PM +0100, Peter Edwards wrote:
The patch applied by the port appears bogus. It adds braces around an
if that stops it executing the way it was intended. I've a sneaking
suspicion that the braces were added
On Wed, 22 Oct 2003, C. Kukulies wrote:
Some (kde) applications now have a warning appear in xconsole:
Warning: pid 595 used static ldt allocation.
See the i386_set_ldt man page for more info
Warning: pid 596 used static ldt allocation.
See the i386_set_ldt man page for more info
Should
System from about a week ago just panic'd (unfortunately do not have
kernel.debug lying around). The panic string was:
Lock (sleep mutext)
Srslock not locked
In /usr/src/sys/netsmb/smb_iod.c:97
While down, I put on a new kernel with sources from yesterday. But looks like
said file hasn't been
On Wed, Oct 22, 2003 at 12:09:43PM -0400, Daniel Eischen wrote:
On Wed, 22 Oct 2003, C. Kukulies wrote:
Some (kde) applications now have a warning appear in xconsole:
Warning: pid 595 used static ldt allocation.
See the i386_set_ldt man page for more info
Warning: pid 596 used static
I found easy way to ugen problem:
in /etc/devfs.rules I added
[local_ruleset=10]
add path 'ugen*' mode 664
then in /etc/rc.conf
devfs_system_ruleset=local_ruleset
And this is it. Now user can acces camera (PowerShots50) with gtkam. The
resolution was given by
In the last episode (Oct 22), Steve Kargl said:
On Wed, Oct 22, 2003 at 12:09:43PM -0400, Daniel Eischen wrote:
On Wed, 22 Oct 2003, C. Kukulies wrote:
Some (kde) applications now have a warning appear in xconsole:
Warning: pid 595 used static ldt allocation.
See the i386_set_ldt
I upgraded my PC yesterday and have experienced hangs in boot. It seems
like something has changed in the SCSI or GEOM code. I have an Advansys SCSI
controller with two plextor CD drivers attached as well as a HP scanner.
When the CD drives are detected the system hangs. Booting with verbose
On Wed, Oct 22, 2003 at 07:47:14PM +0200, Sven Esbjerg wrote:
I upgraded my PC yesterday and have experienced hangs in boot. It seems
like something has changed in the SCSI or GEOM code. I have an Advansys SCSI
controller with two plextor CD drivers attached as well as a HP scanner.
When the
On Wed, Oct 22, 2003 at 07:59:32PM +0200, Bernd Walter wrote:
On Wed, Oct 22, 2003 at 07:47:14PM +0200, Sven Esbjerg wrote:
I upgraded my PC yesterday and have experienced hangs in boot. It seems
like something has changed in the SCSI or GEOM code. I have an Advansys SCSI
controller with
On Wed, 22 Oct 2003, Dan Nelson wrote:
In the last episode (Oct 22), Steve Kargl said:
On Wed, Oct 22, 2003 at 12:09:43PM -0400, Daniel Eischen wrote:
On Wed, 22 Oct 2003, C. Kukulies wrote:
Some (kde) applications now have a warning appear in xconsole:
Warning: pid 595 used
Hi everybody,
I have a VIA EPIA-M 1 board which works mostly when I disable
ACPI in the bios. Unfortunately the parallel port is controlled by
some Super-IO chip and is not recognized during boot. The same holds
true for serial ports and the floppy controller.
When I enable ACPI in the bios
In the last episode (Oct 22), Andre Guibert de Bruet said:
This could also be accomplished by enabling process accounting and
grepping the output of lastcomm. But yes, this patch is most welcome
nonetheless. :)
lastcomm doesn't include the pid, so that would be most difficult :)
--
Greetings,
When I use kvm_getprocs() together with KERN_PROC_PID to get process
information, the structure it returns contains an inaccurate ki_tsize (text
segment size) variable. On my machine, it seems to alternate--seemingly at
random--between 1 and 168, neither of which is correct. The
What upgrade path did you use to get to 5.x/CURRENT?
Did you remember to
clear out /usr/include/g++ and perform an
installworld as stated in
current if you've come from 4.x (or a mid-2002
CURRENT)?
I have identical errors while compiling the kde port
(cvsuped on 2003/10/20). The base system was
On Wed, 22 Oct 2003, C. Kukulies wrote:
Some (kde) applications now have a warning appear in xconsole:
Warning: pid 595 used static ldt allocation.
See the i386_set_ldt man page for more info
Warning: pid 596 used static ldt allocation.
See the i386_set_ldt man page for more info
Should
On Mon, 20 Oct 2003, othermark wrote:
I have a strange panic during the isa pnp code that does not occur with a
5.0-release kernel. I have tried enabling and disabling acpi. it does
not effect this panic one way or another. This is a kernel from -current
10/20 (today). I'm not sure how to
On Wed, 22 Oct 2003, Vladimir B. Grebenschikov wrote:
While build kernel on RELENG_4 machine I have following warnings (they
prevent success build unless -Werror disabled)
Is there some reason you're trying to compile RELENG_4 with gcc 3.3, which
won't work?
/ext/current/src# make -j8
On Mon, Oct 20, 2003 at 09:10:39PM -0400, David Gilbert wrote:
This all started screwing up with ATAng. At first, ATAng didn't
support atapicam, but that was rectified. Now the dvd+rw port
(growisofs) doesn't work at all ... it finishes with an error that I'm
loathe to coaster another
Hi There.
With the debug on in hte kernel ZABU I found this when my Atheros card
crash:
lock order reversal
1st 0xc36c1e84 rl0 (network driver) @ pci/if_rl.c:1485
2nd 0xc0766280 bridge (bridge) @ net/bridge.c:777
Stack backtrace:
lock order reversal
1st 0xc0768540 ifnet (ifnet) @
On Wed, 22 Oct 2003, Daniel Eischen wrote:
On Wed, 22 Oct 2003, C. Kukulies wrote:
Some (kde) applications now have a warning appear in xconsole:
Warning: pid 595 used static ldt allocation.
See the i386_set_ldt man page for more info
Warning: pid 596 used static ldt allocation.
See
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 22 October 2003 10:06 pm, Bruce Evans wrote:
On Wed, 22 Oct 2003, Daniel Eischen wrote:
On Wed, 22 Oct 2003, C. Kukulies wrote:
It is effectively binary only, since current versions of wine don't
run my application correctly and
Daniel Eischen wrote:
On Mon, 20 Oct 2003, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Scott Long [EMAIL PROTECTED] writes:
: We need to resolve this before 5.2 in some fashion. It looks like the
: easiest thing to do is bump libm. Is this advisable?
The
On Wed, 22 Oct 2003, Doug White wrote:
On Wed, 22 Oct 2003, Vladimir B. Grebenschikov wrote:
While build kernel on RELENG_4 machine I have following warnings (they
prevent success build unless -Werror disabled)
Is there some reason you're trying to compile RELENG_4 with gcc 3.3, which
Peter Wemm wrote:
Daniel Eischen wrote:
On Mon, 20 Oct 2003, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Scott Long [EMAIL PROTECTED] writes:
: We need to resolve this before 5.2 in some fashion. It looks like the
: easiest thing to do is bump libm. Is this advisable?
The
On Wednesday 22 October 2003 07:36 pm, Marcos Biscaysaqu wrote:
Hi There.
With the debug on in hte kernel ZABU I found this when my Atheros card
crash:
lock order reversal
1st 0xc36c1e84 rl0 (network driver) @ pci/if_rl.c:1485
2nd 0xc0766280 bridge (bridge) @ net/bridge.c:777
Stack
On Thu, 23 Oct 2003, Bruce Evans wrote:
On Wed, 22 Oct 2003, Daniel Eischen wrote:
On Wed, 22 Oct 2003, C. Kukulies wrote:
Some (kde) applications now have a warning appear in xconsole:
Warning: pid 595 used static ldt allocation.
See the i386_set_ldt man page for more info
On Wed, 22 Oct 2003, Peter Wemm wrote:
Daniel Eischen wrote:
If it's just __fpclassifyd(), can you just add a compatability
hack to libm so it works with both libc 4.0 and 5.x? You
can make __fpclassifyd a weak definition to the hack in libm.
I suppose you could also add __fpclassfyd()
49 matches
Mail list logo
