On Wed, Mar 03, 2004 at 03:00:01PM -0800, Julian Elischer wrote:
> I have not checked this with 5.x but...
>
>
> /dev/ad0s1a on / (ufs, local)
> /dev/ad0s1f on /usr (ufs, local)
> /dev/ad0s1e on /var (ufs, local)
> 10.42.0.1:/usr/ports on /usr/ports (nfs, read-only)
> 10.42.0.1:/usr/src on /usr/s
On Wed, 3 Mar 2004, Julian Elischer wrote:
> On Wed, 3 Mar 2004, William Grim wrote:
> > Julian Elischer wrote:
> > >There in fact was a time problem.
> > I don't know how it was determined that there was a time sync problem;
> > however, in general, "make" creates updated object files depending
On Wed, 3 Mar 2004, William Grim wrote:
> Julian Elischer wrote:
>
> >The prize goes to Kris Kennaway who suggested that it was a time sync
> >problem between the NFS server and client..
> >
> >There in fact was a time problem.
> >
> >wierd..
> >
> >
> I don't know how it was determined tha
Julian Elischer wrote:
The prize goes to Kris Kennaway who suggested that it was a time sync
problem between the NFS server and client..
There in fact was a time problem.
wierd..
I don't know how it was determined that there was a time sync problem;
however, in general, "make" creates updat
On Wed, 3 Mar 2004, Tim Kientzle wrote:
> Julian Elischer wrote:
> >
> > 10.42.0.1:/usr/src on /usr/src (nfs, read-only)
> > 10.42.0.1:/usr/obj on /usr/obj (nfs, read-only)
> >
> > /usr/src and /usr/obj were precompiled on the other (NFS server) machine
> > with "make buildworld".
> >
> > then
Julian Elischer wrote:
10.42.0.1:/usr/src on /usr/src (nfs, read-only)
10.42.0.1:/usr/obj on /usr/obj (nfs, read-only)
/usr/src and /usr/obj were precompiled on the other (NFS server) machine
with "make buildworld".
then on this machine:
"Make installworld" with /usr/src and/usr/obj NFS mounted re
David,
I just tried them out on my machine (-stable, PIII 450, TNT2 Ultra) and
they worked fine! I successfully played a DVD with xine and ogle; xine
was dropping frames (that might be a threads issue) but ogle played it
without dropping any frames.
When X started there was some garbage in a rec
Vladimir Kushnir wrote:
> Well, since nobody seems to be interested (I can't for the life of mine
> understand why), thanks and a couple of (perhaps silly) questions.
I'm interested, I've just been busy thats all. I haven't had a chance to play
with the drivers yet.
Thanks David!
To Unsubscrib
On Saturday 17 November 2001 12:41 am, you wrote:
> Hi,
Hey,
> Well, since nobody seems to be interested (I can't for the life of mine
> understand why), thanks and a couple of (perhaps silly) questions.
>
>
> i) any plans on porting to -CURRENT? On GLX stuff? And does it work with
> DEVFS?
I
Hi,
Well, since nobody seems to be interested (I can't for the life of mine
understand why), thanks and a couple of (perhaps silly) questions.
On Thu, 15 Nov 2001, David Rufino wrote:
> Hi,
>
> Just thought I would mention my -STABLE NVidia drivers have been working for
> the past week, as far
Julian Elischer wrote:
> Who is the expert on apache, modules and shlibs?
> (I'll go offline to discuss the problem if I can find
> an appropriate person.. (can't get ldap module to work with apache
> under freebsd.)
Build Apache from your own sources, and not from ports.
You will also need to u
On Tuesday 07 August 2001 4:05 am, Geoff Mohler wrote:
> Whats a good reference guide on how to install a -STABLE release?
The handbook
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html
and the freebsd-stable mailing list, which you should subscribe to and read
in
On Thursday, 28 December 2000 at 14:03:31 +, Josef Karthauser wrote:
> On Tue, Dec 26, 2000 at 05:30:09PM -0500, David E. Cross wrote:
>> I have run across a problem since updating to -STABLE a week or so ago...
>> my CVS vinum partition would go corrupt after a few updates. I have been
>> ru
No, I am just using vinum stripes. The problem seems to have fixed itself
when I got a ufs_readwrite.c update from Matt after it was committed.
This is an interesting problem, since I am not entirely sure what fixed it,
if it is really fixed, etc...
Sigh, oh well.
--
David Cross
On Tue, Dec 26, 2000 at 05:30:09PM -0500, David E. Cross wrote:
> I have run across a problem since updating to -STABLE a week or so ago...
> my CVS vinum partition would go corrupt after a few updates. I have been
> running with no softupdates on my system for a day now and no problems.
> Has an
On Tuesday, 26 December 2000 at 17:30:09 -0500, David E. Cross wrote:
> I have run across a problem since updating to -STABLE a week or so ago...
> my CVS vinum partition would go corrupt after a few updates. I have been
> running with no softupdates on my system for a day now and no problems.
>
It seems Dimitar V. Peikov wrote:
>
> Yesterday, I've CVSuped -STABLE and UPGRADE using information in
> /usr/src/UPDATING from 4.1.1-STABLE.
Re-cvsup, this has been fixed...
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Mon, 17 Jul 2000, Jaye Mathisen wrote:
> newsfeed-inn2# Jul 17 10:14:07 newsfeed-inn2
> /kernel: pmap_collect: collecting pv entries -- suggest increasing
> PMAP_SHPGPERPROC
>
> Don't see this one in LINT.
>
> Anybody have any wild guesses as to good values?
>
> newsfeed-inn2# sysctl -a | g
Trevor Johnson wrote:
> Gerald Pfeifer wrote:
>
> > Is there a way to
> [...]
> > b) mark a port to notify users not to try using it on -STABLE and
> > -CURRENT?
>
> After a look at
> http://www.freebsd.org/porters-handbook/porting-versions.html and at
> src/sys/sys/param.h,v in the CVS tre
Gerald Pfeifer wrote:
> Is there a way to
[...]
> b) mark a port to notify users not to try using it on -STABLE and
> -CURRENT?
After a look at
http://www.freebsd.org/porters-handbook/porting-versions.html and at
src/sys/sys/param.h,v in the CVS tree, I made the appended patch.
--
Trevor Jo
[ Jordan, I'm Cc:ing you as release engineer as -STABLE has been partially
broken for nearly three weeks now. ]
On Sat, 3 Jun 2000, Gerald Pfeifer wrote:
> This causes clear breakage in -STABLE and lots of wasted time for users
> of the Wine port and myself (answering support requests), for exa
On Sun, 4 Jun 2000, Andrey A. Chernov wrote:
> Ask Peter to commit this patch at least...
Thanks!
Note that Peter has been Cc:ed on all messages concerning this issue, but
didn't reply yet, so I just opened PR misc/19077 and included your patch
there.
Gerald
--
Gerald "Jerry" [EMAIL PROTECTED]
"Andrey A. Chernov" wrote:
>
> On Mon, Jun 05, 2000 at 08:42:47AM +0900, Daniel C. Sobral wrote:
> > Huh? I'm obviously missing something here... Why would the branches be
> > damaged by this?
>
> Because they forked. It cause merge troubles on the next import into the
> vendor branch forever.
On Mon, Jun 05, 2000 at 08:42:47AM +0900, Daniel C. Sobral wrote:
> Huh? I'm obviously missing something here... Why would the branches be
> damaged by this?
Because they forked. It cause merge troubles on the next import into the
vendor branch forever.
--
Andrey A. Chernov
<[EMAIL PROTECTED]>
"Andrey A. Chernov" wrote:
>
> On Sun, Jun 04, 2000 at 11:36:47PM +0900, Daniel C. Sobral wrote:
> > You revert to the original by applying the reverse patch of your changes
> > and committing that. This can be easily done with cvs. And then you
>
> Are you joking? CVS branches will be damaged b
On Sat, Jun 03, 2000 at 07:10:56PM +0200, Gerald Pfeifer wrote:
> However you do it, please fix this ASAP, and be it by reverting the
Ask Peter to commit this patch at least...
--- include/curses.h.in.bak Wed May 24 14:44:45 2000
+++ include/curses.h.in Mon Jun 5 02:28:33 2000
@@ -1313,8 +1
On Sun, Jun 04, 2000 at 11:36:47PM +0900, Daniel C. Sobral wrote:
> You revert to the original by applying the reverse patch of your changes
> and committing that. This can be easily done with cvs. And then you
Are you joking? CVS branches will be damaged by this again.
> changes in the past fir
"Andrey A. Chernov" wrote:
>
> > However you do it, please fix this ASAP, and be it by reverting the
> > original, broken patch!
>
> I wish but I can't. If I'll touch those misterious CVS branches structure
> again, everyone shoot at me as in previous time. I think it is enough for
> me. Nowd
On Sat, Jun 03, 2000 at 07:10:56PM +0200, Gerald Pfeifer wrote:
> On Fri, 26 May 2000, Andrey A. Chernov wrote:
> > Yes, #define was a quick solution.
> > We need either to add a stub or to import ncurses author fix (removing
> > all trace function from production library).
> >
> > Latest is bet
On Wed, 22 Mar 2000, p_a_r wrote:
> Hello were can i dównload freebsd3.4-stable as an iso image ??
This should be on FreeBSD-questions.
ftp://ftp.freebsd.org/.0/FreeBSD/releases/i386/ISO-IMAGES/3.4-install.iso
Or one of the MANY mirrors, as specified on www.freebsd.org
--
Lloyd Rennie
> Hello were can i dównload freebsd3.4-stable as an iso image ??
do a "freebsd*.iso" search on
http://ftpsearch.lycos.com
--
Markus DoehrTel: +49 6503 917 152
IT AdminFax: +49 6503 917 190
SAP R/3 Basis e-Mail: [EMAIL PROTECTED]
AUBI Baubeschläge GmbH http
Hi,
On Tue, 28 Sep 1999, Jordan K. Hubbard wrote:
> I'd suggest trying a 3.3-stable snapshot, just as soon as I can
> get those rolling off of releng3.freebsd.org again. If it still
> occurs, we're now at least debugging the latest and greatest.
Isn't -STABLE tracking OK ?
Unfortunately I do
I'd suggest trying a 3.3-stable snapshot, just as soon as I can
get those rolling off of releng3.freebsd.org again. If it still
occurs, we're now at least debugging the latest and greatest.
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body o
And - to add to this - I still can freeze up my pentium
laptop rather quickly (3.2-RELEASE, 40meg memory, P90) running
setiathome.
And - I've got DDB in the kernel, and ensured it's not overheating
(it will freeze up in less than a minute from a _very_ cold start.)
I don't get a panic, ddb promp
Hi,
On Sat, 25 Sep 1999, Chris Costello wrote:
> On Sat, Sep 25, 1999, Adrian Penisoara wrote:
> > PS: I could have filed a PR but I can't figure any way of reproducing
> > this -- just a double panic caught by my co-worker, details posted on
> > -stable on 19th Sep with "3.2-STABLE hang
Hi,
On Sat, 25 Sep 1999, The Hermit Hacker wrote:
>
> Just to confirm...I've had similar problems, but *only* after moving to
> INN-CURRENT, which makes *very* heavy use of MMAP() :(
>
> What version of INN are you running?
I'm not running any kind of INN -- but lately I have been playing w
Just to confirm...I've had similar problems, but *only* after moving to
INN-CURRENT, which makes *very* heavy use of MMAP() :(
What version of INN are you running?
On Sat, 25 Sep 1999, Adrian Penisoara wrote:
> Hi,
>
> On Fri, 24 Sep 1999, Mark Powell wrote:
>
> > I have INN v2.2 running ha
On Sat, Sep 25, 1999, Adrian Penisoara wrote:
> PS: I could have filed a PR but I can't figure any way of reproducing
> this -- just a double panic caught by my co-worker, details posted on
> -stable on 19th Sep with "3.2-STABLE hangs after several hours" in
> the subject...
When i
>It seemmed to work fine for us too, but if there is a possibility
>of some problem it's probably worth working around "properly". It
>only takes about 4 lines of code. (Unless someone can say this
>is definitely harmless in the SMP case)
Ok, here's the proper fix. Turns out that this 4xPPro box
>It seemmed to work fine for us too, but if there is a possibility
>of some problem it's probably worth working around "properly". It
>only takes about 4 lines of code. (Unless someone can say this
>is definitely harmless in the SMP case)
Ok, here's the proper fix. Turns out that this 4xPPro box
> >The code which figures out the bushigh stuff for your machine
> >probably needs a similar kludge, unless someone can say for certain
> >that it isn't harful for the SMP case.
>
> Probably not worth the effort, since for this system at least, SMP works
> just fine after probing for 253 non-exist
> >The code which figures out the bushigh stuff for your machine
> >probably needs a similar kludge, unless someone can say for certain
> >that it isn't harful for the SMP case.
>
> Probably not worth the effort, since for this system at least, SMP works
> just fine after probing for 253 non-exis
On Tue, 07 Sep 1999 19:48:59 BST, David Malone wrote:
>
>The code which figures out the bushigh stuff for your machine
>probably needs a similar kludge, unless someone can say for certain
>that it isn't harful for the SMP case.
Probably not worth the effort, since for this system at least, SMP wor
On Tue, Sep 07, 1999 at 10:24:53AM -0700, Parag Patel wrote:
> So I think my patch for simply wrapping the "Probing PCI bus" message
> with an "if (bootverbose)" is the right solution/workaround for systems
> like mine running STABLE. Not that it's a big deal - it's easy enough
> for me to patch
On Tue, 07 Sep 1999 19:48:59 BST, David Malone wrote:
>
>The code which figures out the bushigh stuff for your machine
>probably needs a similar kludge, unless someone can say for certain
>that it isn't harful for the SMP case.
Probably not worth the effort, since for this system at least, SMP wo
On Tue, Sep 07, 1999 at 10:24:53AM -0700, Parag Patel wrote:
> So I think my patch for simply wrapping the "Probing PCI bus" message
> with an "if (bootverbose)" is the right solution/workaround for systems
> like mine running STABLE. Not that it's a big deal - it's easy enough
> for me to patch
Thanks conrad..
All the appropriate FreeBSD people were at usenix..
(didn't see you there..)
julian
On Fri, 11 Jun 1999, Conrad Minshall wrote:
> >So far my conclusions
> >have led me to a race in unlink and NFS somewhere (still have no clue where).
> >And it is only from Sun clients to da
Ok, I am hot on the trail... I have found a comonality(sp?) between at least
2 of the Panics. (the 2 I listed)...
it is as follows:
request: create cp1
request: create cp1
reply: ok
reply: error, file exists
request: lookup
request: lookup
(never any response to those.)
I am guessting that: th
Update, even smaller... 6.5K file, patoot.2 now exists in the same location.
--
David Cross | email: cro...@cs.rpi.edu
Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd
Rensselaer Polytechnic Institute, | Ph: 518.276.2860
Yes, I have determined (just today) that the PANIC is only Solaris, and only
with NFSv3 (It may be posssible with NFSv2, but my program doesn't do it
as quickly.). I have a NFS traffic dump of a mere 19K of all nfs traffic to
the machine before the panic. Also, it does NOT ALWAYS cause a panic.
>So far my conclusions
>have led me to a race in unlink and NFS somewhere (still have no clue where).
>And it is only from Sun clients to date. Also, this started happening in
>ernest arround when we put the latest patches on our Suns (this hadn't been
>mentioned before.) seeing how I can reliably
51 matches
Mail list logo
