> In message <38EBB04B.13877.3416842@localhost> [EMAIL PROTECTED] writes:
> : Is this problem just with current? I am having the same type of
> : problem with the sshd daemon on 4.0-STABLE
>
> We found that the records were confusing our local name server.
> Kill and restart it and it was
In message <38EBB04B.13877.3416842@localhost> [EMAIL PROTECTED] writes:
: Is this problem just with current? I am having the same type of
: problem with the sshd daemon on 4.0-STABLE
We found that the records were confusing our local name server.
Kill and restart it and it was fine again f
> On 6 Apr 2000, at 12:53, Yoshinobu Inoue wrote:
> Is this problem just with current? I am having the same type of
> problem with the sshd daemon on 4.0-STABLE
The problem also happens on 4.0-STABLE, and my patch also
applies to it.
I'll MFC it to 4.0-STABLE after I confirmed it on the current
On 6 Apr 2000, at 12:53, Yoshinobu Inoue wrote:
Is this problem just with current? I am having the same type of
problem with the sshd daemon on 4.0-STABLE
David DeTinne
> > > On 6 Apr 2000, at 12:53, Yoshinobu Inoue wrote:
> > > I applied it and am running with it now, but I can't say one way
On Wed, 5 Apr 2000, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Andrzej
>Bialecki writes:
> : The reason I'm asking is that I'm looking for a method to easily
> : clone/upgrade a bunch of servers without having to do 'make world' on all
> : of them. I'm not satisfied either with using dd
In message <[EMAIL PROTECTED]> Brooks Davis writes:
: http://www.one-eyed-alien.net/~brooks/FreeBSD/if_vx.diff
+irq = bus_alloc_resource(dev, SYS_RES_IRQ, &rid,
+ 0, ~0, 1, RF_ACTIVE);
irq = bus_alloc_resource(dev, SYS_RES_IRQ, &rid,
In message <[EMAIL PROTECTED]> Andrzej Bialecki
writes:
: The reason I'm asking is that I'm looking for a method to easily
: clone/upgrade a bunch of servers without having to do 'make world' on all
: of them. I'm not satisfied either with using dd - the machines are not
: identical, there are so
> > > > Sorry for the inconvenience and I'll try the fix.
> > >
> > > Sorry to be late, but I tried resolver fix and it seems to work.
> > > This should remove such 75 seconds delay in apps which use
> > > getaddrinfo().
> > >
> > > Please review and try this patches.
> >
> > I applied it and a
On Thu, 6 Apr 2000, Yu Guo/PEK/Lotus wrote:
>
> Just do a
> make DESTDIR=/mnt/installdir installworld
>
Or remotely mount /usr/obj and /usr/src, and do 15 make installworlds on
15 machines. In fact, I'm not totally sure that first method works,
because I think that perl, at least, record
Just do a
make DESTDIR=/mnt/installdir installworld
Thanks & Best Regards,
Yu Guo
Lotus Development, China PD
Tel: +86-10-68025588 ext 603
Email: [EMAIL PROTECTED]
On Wed, Apr 05, 2000 at 09:35:31PM -0400, Eric D. Futch wrote:
> I figured it would take more work than I put into it. It was just a shot
> in the dark. I think I have one of these cars in my Linux box at home
> which I wouldn't mind ripping out and sticking in this machine. Let me
> know if it
I figured it would take more work than I put into it. It was just a shot
in the dark. I think I have one of these cars in my Linux box at home
which I wouldn't mind ripping out and sticking in this machine. Let me
know if it's still worth me poking around in, or if you're going ahead
with the r
On Wed, Apr 05, 2000 at 08:43:30PM -0400, Eric D. Futch wrote:
> Ok.. I figured I'd take this on on my way to getting more comfy with
> FreeBSD. Check out my patch and let me know how far I've gone off the
> deep end :)
>
> http://quake.nyct.net/~efutch/FreeBSD/if_vx_pci.c.patch
>
> Unfortunate
On Wed, Apr 05, 2000 at 08:43:30PM -0400, Eric D. Futch wrote:
> Ok.. I figured I'd take this on on my way to getting more comfy with
> FreeBSD. Check out my patch and let me know how far I've gone off the
> deep end :)
>
> http://quake.nyct.net/~efutch/FreeBSD/if_vx_pci.c.patch
>
> Unfortunate
Ok.. I figured I'd take this on on my way to getting more comfy with
FreeBSD. Check out my patch and let me know how far I've gone off the
deep end :)
http://quake.nyct.net/~efutch/FreeBSD/if_vx_pci.c.patch
Unfortunately I do not have the acutal card to test this patch. It did
survive a buildk
On Wednesday, 5 April 2000 at 11:42:40 -0700, Matthew Dillon wrote:
>> Matt,
>> help me understand your patch. this is how i read it at this
>> time:
>>
>>
>> Matt has just made available an early patch that corrects the vinum
>> panic. is this the same vinum panic that people are claiming
Hi all,
I can't for the life of me get my new gateway computer
to make any noise (at least with FreeBSD). I've tried
all the PNP/nonPNP combinations from LINT (and then some).
The card is a "Creative Labs Soundblaster Live!" PCI card.
The gateway blurb is found on:
http://www.gateway.com/mes
On Thu, Apr 06, 2000 at 12:00:53AM +0200, Stephan van Beerschoten wrote:
> Maybe there are some people with the same problem .. or maybe someone
> who knows what this could be and how this problem sneaked into the system.
> I'm cunning -CURRENT for ages but since March 19 I am unable to compile
>
Maybe there are some people with the same problem .. or maybe someone
who knows what this could be and how this problem sneaked into the system.
I'm cunning -CURRENT for ages but since March 19 I am unable to compile
myself a new kernel. I'm cunning 5.0-CURRENT but somehow I don't think
that matte
On Wed, 05 Apr 2000, in a never-ending search for enlightenment, J McKitrick wrote:
> Does anyone recall seeing or making a remark about a group of interrupts or
> hardware port locations that could be causing this problem? I was searching
> my email and i can't find it.
>
> Someone said 4.0 all
In message <[EMAIL PROTECTED]>, Maxim Sobolev wrote:
} Frank Nobis wrote:
}
} > On Wed, Apr 05, 2000 at 07:13:29AM -0500, Jon Hamilton wrote:
} > >
} > > up clean. I think you have a hardware problem somewhere :(
} >
} > That is very likely a hardwre problem. I have a nfs server under 3.4-S
} >
:
:At 12:21 PM -0700 2000/4/5, Alfred Perlstein wrote:
:
:> Last I checked, doing so is dangerous because by default the userland
:> components of vinum have debugging on which is incompatible with
:> a kernel running vinum without debug (the default when linked in).
:
: Correct, I belie
[note: followups directed to -current]
David Holloway wrote:
>
> What is the exact error message when using rvplayer 5?
Here it is:
General error. An error occurred.
For more information, please see Error 1 at:
http://www.realaudio.com/help/error
After I press OK, I get this:
a
On Wed, Mar 29, 2000 at 04:44:08AM +1000, David Gilbert wrote:
>Also... I have noticed that several modules don't want to compile in
>the kernel without -O, including kern_synch.c (undefined reference to
>__cursig) and atomic.c (inconsistent operand constraints in an `asm').
I am aware of problem
On Fri, Mar 31, 2000 at 12:50:51AM +1000, Alfred Perlstein wrote:
>What I'm calling for is a vote if we'll rely on this type of behavior
>(32 bit stores being atomic with respect to readers) or not, or
>perhaps to rely on it but mark it somehow so people can "fix it"
>if the need arises later by u
The pcm driver has been much more stable than before. Congrats. But,
one note: I think that in /sys/dev/sound/isa/ess.c, on line 41, the
buffer size should be bumped down to 12288. Before, it was set to
16k, and my ESS 1868 would not work properly.
Also, there's some new problems that have cr
At 12:21 PM -0700 2000/4/5, Alfred Perlstein wrote:
> Last I checked, doing so is dangerous because by default the userland
> components of vinum have debugging on which is incompatible with
> a kernel running vinum without debug (the default when linked in).
Correct, I believe that t
* Matthew Dillon <[EMAIL PROTECTED]> [000405 12:12] wrote:
>
> :
> :> Also, as a general note to everyone, make sure you are building vinum
> :> into the kernel directly and not using it as a kld, just to ensure that
> :> it stays in sync with the kernel.
> :
> : Isn't this in
At 11:43 AM -0700 2000/4/5, Matthew Dillon wrote:
> This is my personal recommendation - if you are messing around with
> something that is under development or test, it is best to build it
> into the kernel to avoid getting out of sync without knowing it.
Ahh, okay. Soun
Andrzej Bialecki wrote:
> Is it possible to do an installworld not to / of existing system, but to,
> say, subdirs somewhere, which could be mountpoints for another disk?
Yes. Do something like:
make installworld DESTDIR=/where/ever/you/want/it/installed
HTH,
--
Marcel Moolenaar
ma
:
:> Also, as a general note to everyone, make sure you are building vinum
:> into the kernel directly and not using it as a kld, just to ensure that
:> it stays in sync with the kernel.
:
: Isn't this in direct conflict with the instructions given for
:normally using vinum?
:Matt,
: help me understand your patch. this is how i read it at this
:time:
:
:
:Matt has just made available an early patch that corrects the vinum
:panic. is this the same vinum panic that people are claiming phk
:created with the bio/buf changes? i dont know the vinum code. i dont
:k
Thus spake Andrzej Bialecki ([EMAIL PROTECTED]):
> The reason I'm asking is that I'm looking for a method to easily
> clone/upgrade a bunch of servers without having to do 'make world' on all
make DESTDIR=/mnt installworld
Same counts for kernel-build.
This belongs to -questions, not -current.
On Wed, 5 Apr 2000, Andrzej Bialecki wrote:
> Is it possible to do an installworld not to / of existing system, but to,
> say, subdirs somewhere, which could be mountpoints for another disk?
DESTDIR?
Kris
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsy
Hi,
Is it possible to do an installworld not to / of existing system, but to,
say, subdirs somewhere, which could be mountpoints for another disk?
Something like:
/mnt/installdir/
/mnt/installdir/compat
/mnt/installdir/etc
/mnt/installdir/usr
/mnt/installdir/var
/mnt/installdir/
The reason I'm
>
> I'm trying to install 4.0-RELEASE on a COMPAQ Proliant 1850R
> with the root disk on a SMART-2SL raid controller. The install
> works perfectly, but boot/loader fails to load the kernel.
>
> Booting "kernel" fails with 'Don't know how to load module
> "/kernel"', and boot kernel.GENERIC
* Greg Lehey <[EMAIL PROTECTED]> [000403 18:07] wrote:
> On Sunday, 2 April 2000 at 17:23:49 -0700, Alfred Perlstein wrote:
> > * Matthew Dillon <[EMAIL PROTECTED]> [000402 17:04] wrote:
> >>
> >> :I did look at the code, struct proc is allocated from a zone,
> >> :meaning it won't "go away" once
Thus spake Soren Schmidt ([EMAIL PROTECTED]):
> Hmm, I guess I'll have to try to locate a 8100 somewhere and
> try to find out what it doesn't like...
The Mitsumi 4801 does the same thing.
If you can't fine a 8100, I could take a look at it - in a month or
such.
Alex
To Unsubscribe: send mai
At 9:49 AM -0700 2000/4/5, Matthew Dillon wrote:
> Also, as a general note to everyone, make sure you are building vinum
> into the kernel directly and not using it as a kld, just to ensure that
> it stays in sync with the kernel.
Isn't this in direct conflict with the ins
John Hay wrote:
> The CD writer is an HP 8100 and I have used it before without problems
> with a much older version of 4-CURRENT, that is before the ata driver.
>
> Does anybody else have problems with the HP 8100 series? I have included
> dmesg.boot at the end.
Someone else reported problems
>
> I've tracked down two bugs in vinum's raid5 implementation and
> submitted a tentitive patch to Greg for evaluation. It seems
> to fix the panics I was able to reproduce. The patch is available
> (but note that once Greg commits the real fix, you need to wipe it
> befor
:
:On Apr 05, Matthew Dillon wrote:
:> (needless to say, the patch I posted is relative to FreeBSD-4.x, not 5)
:>
:> -Matt
:> Matthew Dillon
:> <[EMAIL PROTECTED]>
:>
:
: He
Mike Smith once wrote:
>> After doing a cvsup yesterday evening i can't seem to boot on
>my
>> raid cotroller using the same kernel config.
>>
>> Is -current probing hardware i a different way now or ??
>
>This is a consequence of a defect in the way that the ida driver
>works,
>and new code w
On Apr 05, Matthew Dillon wrote:
> (needless to say, the patch I posted is relative to FreeBSD-4.x, not 5)
>
> -Matt
> Matthew Dillon
> <[EMAIL PROTECTED]>
>
Here's wha
Hi,
I've got FreeBSD 4.0 RELEASE running on a Compaq Deskpro with an Intel 810
motherboard. I'm running the machine as a POP3 server using Qmail's POP3D
daemon. For some unknown reason, the machine keeps rebooting every 3 - 4
hours. I'm not sure how to get it to log the details of the panic so I
subscribe freebsd-current
--
-
G Douglas Davidson | CityNet, Inc.
[EMAIL PROTECTED]| Pittsburgh, PA
voice: 412.481.5406 | fax: 412.431.1315
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the
(needless to say, the patch I posted is relative to FreeBSD-4.x, not 5)
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsu
I've tracked down two bugs in vinum's raid5 implementation and
submitted a tentitive patch to Greg for evaluation. It seems
to fix the panics I was able to reproduce. The patch is available
(but note that once Greg commits the real fix, you need to wipe it
before you cvs upd
Folks,
I'd like to extend my thanks and give kudos to all who have been
involved in the process of creating FreeBSD 4.0, from -CURRENT up
through -STABLE, and beyond to wherever that might take us.
We had a new Dell PowerEdge 6350/500 server that arrived here
yesterday, and a
As described in i386/17228, the following patch, which disables DMA on ATAPI
if not explicitely enabled, makes my Compaq Aramada V300 laptop able to boot
-CURRENT.
While this patch may not be correct, it shows once again that DMA is
playing an active role in the lockup described in the PR. I'll p
This is the same way that OS servers under Mach3 were developed and debugged!
John
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> Hmm you are the second to report that, but I also have reports that
> says it works. Maybe we are facing different firmaware versions...
>
> However I cannot reproduce the problem on any of my drives (but
> I dont have access to a 8100), so I'm not sure what to do about
> it. There was a change
Does anyone recall seeing or making a remark about a group of interrupts or
hardware port locations that could be causing this problem? I was searching
my email and i can't find it.
Someone said 4.0 allocates a group of hardware locations (0x380-0x3f0?)
differently from 3.4, and that this may af
From: Visigoth <[EMAIL PROTECTED]>
Subject: Re: Is current.freebsd.org running Linux?
Date: Wed, 5 Apr 2000 09:32:21 -0500 (CDT)
Message-ID: <[EMAIL PROTECTED]>
visigoth>
visigoth> > current.jp.freebsd.org is another stable/current build machine.
visigoth> >
visigoth> > /\ Hidetoshi Shimokawa
vi
It seems Maxim Sobolev wrote:
>
> I've tried it on my home machine and failed to reproduce also. However it is
> strange, because if it is the CPU/Memory problem, then there should be other signs
> - random applications crashes, spontaneous reboots etc., but machine is pretty
> stable - up and ru
It seems John Hay wrote:
> Hi,
>
> I have installed 4.0-STABLE on our machine with the CD burner and when
> I tried to burn a CD, the session went as follows:
>
> ===
> tien# burncd -s 4 -f /dev/acd0c data 4.0-install.iso fixate
> next writeable LBA 0
> writing from file 4.0-install.iso siz
> current.jp.freebsd.org is another stable/current build machine.
>
> /\ Hidetoshi Shimokawa
Thanks Hidetoshi, but I think my meager 3 years of nihongo in highschool
are not going to be enough to run a Japanese snapshot just yet...
Damieon Stark
Sr. Unix Systems Administrator
[EMAIL PROTECTE
Maxim Didenko wrote:
>
> Hello everybody,
>
> I try to install FreeBSD 4.0-RELEASE on Dell PowerEdge SP 5100 with
> integrated PCI SCSI NCR controller (chip label is "Symbols Logic
> 53C810a 609-0392140 DR00218 9627N"). At boot time controller outputs
> "NCR SDMS (TM) v3.0 PCI SCSI BIOS
Jon Hamilton wrote:
> In message <[EMAIL PROTECTED]>, Maxim Sobolev wrote:
> } This is a multi-part message in MIME format.
> } --3D64CAE46133EFA188180FFD
> } Content-Type: text/plain; charset=koi8-r
> } Content-Transfer-Encoding: 7bit
> }
> } Hi,
> }
> } I've tried to track down why
Greg Lehey wrote:
> Technical explanation: A buffer header gets corrupted between the
> time the top half of the driver issues the request to the disk
> driver, and when the I/O completes. Currently, the evidence is
> pointing towards the disk driver, but the corruption is of such an
> u
Could anyone who uses a Parallel Zip drive with FreeBSD 4.0 and up ('and
better' I almost wrote there :-) send me a message wether it works?
I'm trying to resolve PR 16153, but have no clue where to look
If it does not work, please tell me
- what version of the OS you are using
- at which poi
Hi,
I have installed 4.0-STABLE on our machine with the CD burner and when
I tried to burn a CD, the session went as follows:
===
tien# burncd -s 4 -f /dev/acd0c data 4.0-install.iso fixate
next writeable LBA 0
writing from file 4.0-install.iso size 641174 KB
written this track 641174 KB (1
Frank Nobis wrote:
> On Wed, Apr 05, 2000 at 07:13:29AM -0500, Jon Hamilton wrote:
> >
> > up clean. I think you have a hardware problem somewhere :(
>
> That is very likely a hardwre problem. I have a nfs server under 3.4-S
> here running, It was easy to crash the system with much I/O over nfs
On Wed, Apr 05, 2000 at 07:13:29AM -0500, Jon Hamilton wrote:
>
> up clean. I think you have a hardware problem somewhere :(
That is very likely a hardwre problem. I have a nfs server under 3.4-S
here running, It was easy to crash the system with much I/O over nfs
on a 100M Ethernet connection.
In message <[EMAIL PROTECTED]>, Maxim Sobolev wrote:
} This is a multi-part message in MIME format.
} --3D64CAE46133EFA188180FFD
} Content-Type: text/plain; charset=koi8-r
} Content-Transfer-Encoding: 7bit
}
} Hi,
}
} I've tried to track down why my own script which is cleaning non-
Hello everybody,
I try to install FreeBSD 4.0-RELEASE on Dell PowerEdge SP 5100 with
integrated PCI SCSI NCR controller (chip label is "Symbols Logic
53C810a 609-0392140 DR00218 9627N"). At boot time controller outputs
"NCR SDMS (TM) v3.0 PCI SCSI BIOS PCI Rev. 2.0 NCRPCI-3.07.02".
Afte
> > Why does this sound like the warning that is written in the manual of
> > the Iomega Zip drive:
> >
> > do not connect more than one Zip drive to the same USB host data
> > might corrupted.
> >
> > Or something similar...
>
> But.. but.. I only have the one drive connected.
It coul
On Tue, Apr 04, 2000 at 10:05:32PM +0800, Adrian Chadd wrote:
> On Tue, Apr 04, 2000, Kris Kennaway wrote:
> > On Tue, 4 Apr 2000, Timo Geusch wrote:
> >
> > > Here be dragons, I know :-). Got myself a nice juicy & reproducable
> > > crash here, so I thought I might as well try to track down this
On Tue 2000-04-04 (21:14), Thomas D. Dean wrote:
> I installed the 3.4 normal user, bin and docs on the new disk. I
> copied /etc, /usr/src and /usr/ports from the old -current disk. I
> did a make world to upgrade to -current.
>
> 'make world' had two problems. The buildworld phase completed
For those following along, it's definately kue-related.
On Tue, Apr 04, 2000 at 06:40:22PM -0400, Christopher Masto wrote:
> Next time I get a chance, I'll try:
>
> Filesystem-intensive activity without using kue at all, then a
> reboot and fsck.
Tested, absolutely no problems. In fact, I'
Hi all,
When I do installworld, it fails in src/sbin/routed/rtquery:
install -c -s -o root -g wheel -m 555 rtquery
usage: install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 file2
install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 ...
fileN d
It is down right now. It will be back soon. Thanks for asking
so loudly.
> Why is this machine (current.freebsd.org) always rejecting guest privileges
> and why won't ANYBODY answer the question?
>
> Thanks in advance,
>
> Tom Veldhouse
> [EMAIL PROTECTED]
>
>
>
> To Unsubscribe: send mail
72 matches
Mail list logo
