Re: HEADS UP: cvs commit: src/sys/conf kern.pre.mk (fwd)

On Tue, 26 Feb 2002, Peter Wemm wrote: > Peter Dufault wrote: > > When it is too twisty to fix at the moment I use macros such as: > > > > #define BOGUSLY_CAST_AWAY_VOLATILITY(T,P) ((T)(unsigned int)(P)) > > > > ... > > > > volatile int conspeed; int *foo = > > BOGUSLY_CAST_AWAY_VOLATILITY(in

Re: Broken (?) unistd.h

On Tue, 26 Feb 2002, Bill Fenner wrote: > Here's a patch for bind's port/freebsd/include/port_before.h . > > --- port_before.h.origTue Feb 26 20:57:35 2002 > +++ port_before.h Tue Feb 26 21:02:18 2002 > @@ -15,6 +15,7 @@ > #define SETPWENT_VOID > #endif > > +#include > #include

Re: NetBSD-style rc.d Project

On Wed, 27 Feb 2002, Kevin Way wrote: > * Sheldon Hearn <[EMAIL PROTECTED]> [27-02-02 03:58]: > > > At this point, I'm very willing to help anybody who is doing the > > > main development, with either coding or testing, but I have no > > > interest being a lead developer on the project. > > > >

Re: NetBSD-style rc.d Project

> > I'm about to dive into doing some work for an rc system for the ports > > (${PREFIX}/etc/defaults && ${PREFIX}/etc/rc.conf) and have an interest > > in learning about the way they've done things. Does their paradigm > > completely obsolete the rc.conf concept? Were there any docs/project > >

setpgrp(1, 1) does not FAIL

Hello, The following will succeed in non privilege user. I think it should fail. main() { printf("%d\n", setpgrp(1, 1)); } -- HIROSHI OOTA [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freeb

Re: Today's panic on boot problem

On Wed, 27 Feb 2002, Mike Silbersack wrote: > Disabling PG_G allows it to work here again as well. Given the problems > we're experiencing, backing out the pmap changes of the last two days > seems like a good idea. > > Mike "Silby" Silbersack Well, I sorta take that back. The box has been up

Re: Today's panic on boot problem

On Tue, 26 Feb 2002, Peter Wemm wrote: > FWIW, turning off PG_G see_ms to help. Change in pmap.c: > #if !defined(SMP) || defined(ENABLE_PG_G) > to: > #if /*!defined(SMP) ||*/ defined(ENABLE_PG_G) > and see how you go. This got me past atkbd0, but it is a very worrying > sign. I now get a vnod

Re: NetBSD-style rc.d Project

* Sheldon Hearn <[EMAIL PROTECTED]> [27-02-02 03:58]: > > At this point, I'm very willing to help anybody who is doing the > > main development, with either coding or testing, but I have no > > interest being a lead developer on the project. > > Have you been in contact with Gordon Tetlow to see

Re: NetBSD-style rc.d Project

* David O'Brien <[EMAIL PROTECTED]> [27-02-02 04:39]: > I may have dropped the ball on this. I was waiting for a tarball from > you, that you were happy with. You may have told me where to pick one up > that I failed to do. Thanks for offering yourself up as an excuse, but the failure to delive

Re: NetBSD-style rc.d Project

* Sean Chittenden <[EMAIL PROTECTED]> [27-02-02 04:05]: > I'm about to dive into doing some work for an rc system for the ports > (${PREFIX}/etc/defaults && ${PREFIX}/etc/rc.conf) and have an interest > in learning about the way they've done things. Does their paradigm > completely obsolete the r

Re: Today's panic on boot problem

Mike Silbersack wrote: > > On Tue, 26 Feb 2002, Peter Wemm wrote: > > > Mike Silbersack wrote: > > >_ > > > Hm, sounds like UP got optimized out. > > > > Gah! That would be a first. :( > > Well, until I can build a working kernel, I'll just assume that it's a > feature. FWIW, turning off PG_G

Re: Broken (?) unistd.h

Here's a patch for bind's port/freebsd/include/port_before.h . --- port_before.h.orig Tue Feb 26 20:57:35 2002 +++ port_before.h Tue Feb 26 21:02:18 2002 @@ -15,6 +15,7 @@ #define SETPWENT_VOID #endif +#include #include #define GROUP_R_RETURN struct group * @@ -26,8 +27,13 @@ #d

Re: NetBSD-style rc.d Project

At 6:48 PM -0800 2/26/02, Kris Kennaway wrote: >On Tue, Feb 26, 2002 at 10:00:52AM -0500, Kevin Way wrote: > >> I, for one, lost interest in doing the work when I realized I was >> receiving, quite literally, 5 times more complaints than combined >> patches, constructive criticism or positive f

Re: NetBSD-style rc.d Project

On Tue, Feb 26, 2002 at 10:17:49AM -0800, Gregory Neil Shapiro wrote: > Should committers be updating those files when they update /etc/rc? If so, > I'll need to change the sendmail startup routines. No. That will pull them off the vendor branch before we are ready for that. To Unsubscribe: se

Re: NetBSD-style rc.d Project

On Tue, Feb 26, 2002 at 10:00:52AM -0500, Kevin Way wrote: > As one of the many people who've done some initial work on the port, > I can tell you that it seems to me that there's not a lot of interest > in this project, beyond criticizing the work of those who've made > attempts to do any work, o

Re: Discussion of guidelines for additional version control

At 7:27 PM -0800 2/26/02, Julian Elischer wrote: >On Tue, 26 Feb 2002, Garance A Drosihn wrote: > >> That would be me... >> > > I meant "lock" in the sense of expecting no one to make any > > major changes in the same area of code. I seem to remember > > you asking for such a "lock" (to use t

Re: Discussion of guidelines for additional version controlmechanisms (fwd)

In message: <[EMAIL PROTECTED]> Robert Watson <[EMAIL PROTECTED]> writes: : > I meant "lock" in the sense of expecting no one to make any major : > changes in the same area of code. I seem to remember you asking for : > such a "lock" (to use the term loosely) in July, and the KSE work

Re: Today's panic on boot problem

On Tue, 26 Feb 2002, Peter Wemm wrote: > Mike Silbersack wrote: > > > > Hm, sounds like UP got optimized out. > > Gah! That would be a first. :( Well, until I can build a working kernel, I'll just assume that it's a feature. Mike "Silby" Silbersack To Unsubscribe: send mail to [EMAIL PROTEC

Re: Broken (?) unistd.h

* Doug Barton <[EMAIL PROTECTED]> [020226 19:12] wrote: > The following: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/include/unistd.h.diff?r1=1.46&r2=1.47 > > Broke compilation of bind 8 on -current built 2/24: > > mkdir threaded 2> /dev/null || test -d threaded -a -w threaded > (cc -I../../p

Re: Discussion of guidelines for additional version control mechanisms(fwd)

On Tue, 26 Feb 2002, Robert Watson wrote: > > On Tue, 26 Feb 2002, Julian Elischer wrote: > > > > On the other hand, you could easily argue that the expectations might be > > > much lower for smaller pieces of work. For example, the move to td_ucred > > > required a substantial amount of inf

Re: Discussion of guidelines for additional version control

mechanisms (fwd) In-Reply-To: Message-ID: <[EMAIL PROTECTED]> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 26 Feb 2002, Garance A Drosihn wrote: > At 6:55 PM -0800 2/26/02, Julian Elischer wrote: > > > (1) The timeout begins wh

Re: Discussion of guidelines for additional version controlmechanisms (fwd)

In message: Garance A Drosihn <[EMAIL PROTECTED]> writes: : I think the main issue here is how long the real repository can be : "locked" while waiting for some change to show up. If work can : keep going into the main repository, then what does

Re: Discussion of guidelines for additional version control mechanisms (fwd)

On Tue, 26 Feb 2002, Garance A Drosihn wrote: > That would be me... > > I meant "lock" in the sense of expecting no one to make any major > changes in the same area of code. I seem to remember you asking for > such a "lock" (to use the term loosely) in July, and the KSE work going > in around

Re: NetBSD-style rc.d Project

> I spent some time in the fall learning the NetBSD system > (unfortunately I'm not running any NetBSD boxes at the moment or > this would probably be a _lot_ easier), but have not really done any > work. I thought some people were working on it, but not in the > tree. I did not want to duplicate

Re: Discussion of guidelines for additional version control mechanisms (fwd)

>>Some things are too impractically large to do incrementally and are an >>all-or-nothing thing. I recall seeing your early VM commits which were huge, >>you had been working on for months, and were not incremental things. > > Actually, most VM system work that was done was developed over a per

Re: Discussion of guidelines for additional version controlmechanisms (fwd)

At 6:55 PM -0800 2/26/02, Julian Elischer wrote: > > (1) The timeout begins when contention occurs, of the lock has been >> declared. This means that if you seriously intend to do some work, >> you can say "I'm going to do the work", but you don't risk losing the >> lock until som

Re: Discussion of guidelines for additional version control mechanisms (fwd)

>>Anyway, my point is that the Perforce repo itself isn't the problem. The >> problem is that people are maintaining private patch sets for long periods >> and making claims to the areas that their patches cover. Step-wise evolution >> is the only way to go in this distributed development mode

Broken (?) unistd.h

The following: http://www.freebsd.org/cgi/cvsweb.cgi/src/include/unistd.h.diff?r1=1.46&r2=1.47 Broke compilation of bind 8 on -current built 2/24: mkdir threaded 2> /dev/null || test -d threaded -a -w threaded (cc -I../../port/freebsd/include -I../../include -g -Wall -c getgrent.c -o threaded

Re: Today's panic on boot problem

Mike Silbersack wrote: > > On Tue, 26 Feb 2002, David Wolfskill wrote: > > > >Date: Tue, 26 Feb 2002 19:46:59 + (GMT) > > >From: Mike Silbersack <[EMAIL PROTECTED]> > > > > >Using ACPI doesn't help here either. Hmph. Can I get a kernel dump that > > >early in the boot process? The dumpon

Re: Discussion of guidelines for additional version control mechanisms (fwd)

On Tue, 26 Feb 2002, Julian Elischer wrote: > > On the other hand, you could easily argue that the expectations might be > > much lower for smaller pieces of work. For example, the move to td_ucred > > required a substantial amount of infrastructure, but the patches > > themselves are relativel

Re: panic: bad pte

[EMAIL PROTECTED] wrote: > I got the following panic while building X with today's current: > > TPTE at 0xbfc201a0 IS ZERO @ VA 08068000 > panic: bad pte I've had this about an hour ago too. I'm looking at it right now.. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMA

Re: Discussion of guidelines for additional version control mechanisms (fwd)

David Greenman wrote: > >In the past week, a number of comments have been made both for and against > >additional version control mechanisms being used to supplement the FreeBSD > >Project official CVS server. Proponents of additional mechanisms, such as > >It's my view that work that happen

Re: Discussion of guidelines for additional version control mechanisms(fwd)

On Tue, 26 Feb 2002, Robert Watson wrote: > > On Tue, 26 Feb 2002, Garance A Drosihn wrote: > > > On the other hand, you could easily argue that the expectations might be > much lower for smaller pieces of work. For example, the move to td_ucred > required a substantial amount of infrastruc

panic: bad pte

I got the following panic while building X with today's current: TPTE at 0xbfc201a0 IS ZERO @ VA 08068000 panic: bad pte db> trace Debugger(x029a31b) at Debugger+0x40 panic(c02b617f,c02b6160,bfc201a0,8068000,d909fa00) at panic+0x70 pmap_remove_pages(d909fa6c,0,bfc0,d8e3bd20,d8d81e00) at pma

Re: Discussion of guidelines for additional version control mechanisms (fwd)

>In the past week, a number of comments have been made both for and against >additional version control mechanisms being used to supplement the FreeBSD >Project official CVS server. Proponents of additional mechanisms, such as It's my view that work that happens outside of our official CVS re

Re: NetBSD-style rc.d Project

On Tue, Feb 26, 2002 at 10:00:52AM -0500, Kevin Way wrote: > I, for one, lost interest in doing the work when I realized I was > receiving, quite literally, 5 times more complaints than combined > patches, constructive criticism or positive feedback. Well, for what it's worth I didn't say anythi

Re: Discussion of guidelines for additional version control mechanisms (fwd)

On Tue, 26 Feb 2002, Garance A Drosihn wrote: > I think the main issue here is how long the real repository can be > "locked" while waiting for some change to show up. If work can keep > going into the main repository, then what does anyone care if someone is > tracking their own personal work

Re: Today's panic on boot problem

On Tue, 26 Feb 2002, David Wolfskill wrote: > >Date: Tue, 26 Feb 2002 19:46:59 + (GMT) > >From: Mike Silbersack <[EMAIL PROTECTED]> > > >Using ACPI doesn't help here either. Hmph. Can I get a kernel dump that > >early in the boot process? The dumpon manpage doesn't suggest a way as > >far

Re: Discussion of guidelines for additional version controlmechanisms (fwd)

At 4:53 PM -0500 2/26/02, Robert Watson wrote: >The purpose of this message is to initiate a serious discussion >of what guidelines might be put in place to help facilitate the >use of additional version control mechanisms [...]. I've mixed >in some suggested things to think about as possible ans

Re: Today's panic on boot problem

On Tue, 26 Feb 2002, Mike Silbersack wrote: > I reverted that change, and the double panic still occured. :| > > FWIW, you're correct in that I'm not using the acpi module. > > Mike "Silby" Silbersack Using ACPI doesn't help here either. Hmph. Can I get a kernel dump that early in the boot p

Re: -current hangs with SMP enabled

Kenneth D. Merry writes: > > Wow, I didn't actually expect my config would make things work > > differenty on your box. I'm very interested in whatever you > > turn up. > > The answer is...the USB code. > > [ Nick and Joe CCed ] > > If I comment out the following lines in

Re: cvs commit: src/sys/i386/i386 exception.s genassym.c machdep.cmp_machdep.c mpapic.c swtch.s vm_machdep.c src/sys/i386/include cpufunc.hpcb.h src/sys/i386/isa apic_vector.s clock.c icu_vector.s intr_machdep.cintr_machdep.h npx.c src/sys/kern ...

Matthew Jacob writes: > > > How is it different than publishing patches on a web site? There are > > a number of tools that one needs to have to get the patches, just like > > in P4. The P4 repo is available from cvsup10, so you don't even need > > to install P4 to see the patches. > >

Re: Today's panic on boot problem

On Tue, 2002-02-26 at 17:38, Peter Wemm wrote: > You may like to try reverting this change: A great idea, but unfortunately, incorrect ... -- Michael D. Harnois bilocational bivocational Pastor, Redeemer Lutheran ChurchWashburn, Iowa 1L, UST School of Law

Re: Today's panic on boot problem

On Tue, 26 Feb 2002, Peter Wemm wrote: > Mike Silbersack wrote: > > I'm experiencing the same double panic on boot that PHK is now; are we the > > only ones, or is it just that nobody else has updated recently? > > If you are not using acpica, then you're probably using vm86 for pcibios > calls

Re: NetBSD-style rc.d Project

On Tue, 26 Feb 2002, Kevin Way wrote: > As one of the many people who've done some initial work on the port, I > can tell you that it seems to me that there's not a lot of interest in > this project, beyond criticizing the work of those who've made attempts > to do any work, or attempting to exp

RE: Today's panic on boot problem

On 26-Feb-2002 (17:27:19/GMT) Mike Silbersack wrote: > I'm experiencing the same double panic on boot that PHK is > now; are we the only ones, or is it just that nobody else > has updated recently? Mee too, just survied to 4 auto-reboot without messages... Trying with a boot -v I see a keyboard

Re: cvs commit: src/sys/i386/i386 exception.s genassym.c machdep.c mp_machdep.c mpapic.c swtch.s vm_machdep.c src/sys/i386/include cpufunc.h pcb.h src/sys/i386/isa apic_vector.s clock.c icu_vector.s intr_machdep.c intr_machdep.h npx.c src/sys/kern ...

Julian Elischer wrote: > On Tue, 26 Feb 2002, Warner Losh wrote: > > Our CVS meisters have told us in the past that branches on the CVS > > tree are bad, and NetBSD's experience is that not more than one or two > > are sustainable in the long run. > > UMM they are not supposed to be there for T

Re: Today's panic on boot problem

Mike Silbersack wrote: > I'm experiencing the same double panic on boot that PHK is now; are we the > only ones, or is it just that nobody else has updated recently? If you are not using acpica, then you're probably using vm86 for pcibios calls. I've been told that I've broken bios.c.. You may

Re: HEADS UP: cvs commit: src/sys/conf kern.pre.mk (fwd)

Peter Dufault wrote: > On Mon, Feb 25, 2002 at 11:35:12PM -0700, M. Warner Losh wrote: > > In message: <[EMAIL PROTECTED]> > > Mike Makonnen <[EMAIL PROTECTED]> writes: > > : On Mon, 2002-02-25 at 20:59, M. Warner Losh wrote: > > : > I've fixed a few of the low hanging fruit, but I don

Today's panic on boot problem

I'm experiencing the same double panic on boot that PHK is now; are we the only ones, or is it just that nobody else has updated recently? Mike "Silby" Silbersack To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: FreeBSD/i386 "make release" breakage

On Tue, Feb 26, 2002 at 05:30:50AM -0800, [EMAIL PROTECTED] wrote: >2. Use the existing boot_crunch.conf, but move sbin/dhclient/* back > to a single top-level Makefile. This does not work at the > moment, because the objects in each subdirectory are built with > different c

Re: FreeBSD/i386 "make release" breakage

On Tue, Feb 26, 2002 at 06:39:22PM +0900, Makoto Matsushita wrote: > Note that new dhclient requires some libraries which are *not* > installed to /usr/lib (libdhcp, libres, libomapi, and libdst). They are built and linked statically. This is not possible with crunch_gen? To Unsubscribe: send m

Re: cvs commit: src/sys/i386/i386 exception.s genassym.c machdep.c mp_machdep.c mpapic.c swtch.s vm_machdep.c src/sys/i386/include cpufunc.h pcb.h src/sys/i386/isa apic_vector.s clock.c icu_vector.s intr_machdep.c intr_machdep.h npx.c src/sys/kern ...

On Tue, Feb 26, 2002 at 02:43:02PM -0700, Warner Losh wrote: > : > the same as publishing it. P4 is an aid to the developer to do PRIVATE > : > work. As long as the work is in P4 it is up to the developer to > : > keep it in sync with -current. From the project's perspective > : > work in P4 doesn

Re: cvs commit: src/sys/i386/i386 exception.s genassym.c machdep.cmp_machdep.c mpapic.c swtch.s vm_machdep.c src/sys/i386/include cpufunc.hpcb.h src/sys/i386/isa apic_vector.s clock.c icu_vector.s intr_machdep.cintr_machdep.h npx.c src/sys/kern ...

On Tue, 26 Feb 2002, Warner Losh wrote: > [[ moved to current ]] > > In message Matthew Jacob writes: > : > I would also like to have core take a stand that having code in P4 isn NOT > : > the same as publishing it. P4 is an aid to the developer to do PRIVATE > : > work. As long as the work i

Re: cvs commit: src/sys/i386/i386 exception.s genassym.c machdep.cmp_machdep.c mpapic.c swtch.s vm_machdep.c src/sys/i386/include cpufunc.hpcb.h src/sys/i386/isa apic_vector.s clock.c icu_vector.s intr_machdep.cintr_machdep.h npx.c src/sys/kern ...

> How is it different than publishing patches on a web site? There are > a number of tools that one needs to have to get the patches, just like > in P4. The P4 repo is available from cvsup10, so you don't even need > to install P4 to see the patches. Because it encourages (and has encouraged)

Re: Why is xe building while commented out?

You know, I've been building -currents off and on since 3.0-current, and never realized that. I guess since I usualy start a build and either background it, or walk away... I'll play with the MODULES_OVERRIDE option, and thanks for the pointer. I gave it another run with out the -j4 option, and

Discussion of guidelines for additional version control mechanisms (fwd)

Apparently a number of people missed this post, so I'm resending. To recap: this is an attempt to brainstorm for ideas about how we can improve our use of version control, while responding to concerns about access the resulting work. The goal is to formulate a set of guidelines based on whateve

Re: Why is xe building while commented out?

On Tue, Feb 26, 2002 at 03:28:19PM -0600, Stephen L. Palmer wrote: > Kernel build on a fresh (26 Feb 2002 - ~15:00 CDT) -current is failing > with an "*** Error code 2" in the xe module. This module is commented out of my > config. Why would 'make -j4 buildkernel KERNCONF=MIDEARTH' try to build

Re: cvs commit: src/sys/i386/i386 exception.s genassym.c machdep.c mp_machdep.c mpapic.c swtch.s vm_machdep.c src/sys/i386/include cpufunc.h pcb.h src/sys/i386/isa apic_vector.s clock.c icu_vector.s intr_machdep.c intr_machdep.h npx.c src/sys/kern ...

[[ moved to current ]] In message Matthew Jacob writes: : > I would also like to have core take a stand that having code in P4 isn NOT : > the same as publishing it. P4 is an aid to the developer to do PRIVATE : > work. As long as the work is in P4 it is up to the developer to : > keep it in syn

Why is xe building while commented out?

Kernel build on a fresh (26 Feb 2002 - ~15:00 CDT) -current is failing with an "*** Error code 2" in the xe module. This module is commented out of my config. Why would 'make -j4 buildkernel KERNCONF=MIDEARTH' try to build a driver for a pccard I've commented out of the config? I don't have any

Re: calcru: negative time of XXX

>FreeBSD 5.0-CURRENT #1: Sun Feb 24 22:06:53 CET 2002 This is not a -current kernel when we talk about ACPI timecounters, you want a kernel with this commit in it: phk 2002/02/25 01:51:18 PST Modified files: sys/dev/acpica acpi_timer.c Log: Add a new test_counter() fun

Re: calcru: negative time of XXX

On Tue, 26 Feb 2002, Poul-Henning Kamp wrote: > please send me /var/run/dmesg.boot from a "boot -v" on a current kernel > and output from "sysctl kern.timecounter" please ? $ sysctl kern.timecounter kern.timecounter.nmicrotime: 3838 kern.timecounter.nnanotime: 3 kern.timecounter.nmicrouptime: 1

Re: libc_r patches and some questions

Hi Alfred, > > if (errno != 0) { > > if (dp == NULL) > > The above patch should be committed. Can you please commit it and I'll close PR misc/30631 after it has been MFC'd, ok ? Martin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the bo

you broke current in some weird way...

My machine panics somewhere inside the BIOS after your commit today. Tree checked out "2002/02/25 15:45:52 PST" boots fine, one from "2002/02/25 16:05:52 PST" tanks like this: ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it pcm: pcm0 already exists; skipping it sc: s

Re: libc_r patches and some questions

On Tue, 26 Feb 2002, Martin Blapp wrote: > Hi all, > > I've recieved patches from Carlos Fernando Assis Paniago <[EMAIL PROTECTED]> > to get Openoffice Build 641 running. > > Since I'm not familiar, I hope someone else can look at them and point me > to the right direction to have a working Open

Re: this morning's kernel hangs

Michael Nottebrock wrote: [...] > iicbb + iicbus kernel with a few modules specified for preloading in > /etc/loader.conf bails out immediately (not even CLK calibration comes That's /boot/loader.conf, of course. -- Michael Nottebrock To Unsubscribe: send mail to [EMAIL PROTECTED] with "u

Re: this morning's kernel hangs

David Wolfskill wrote: >>From: "Michael D. Harnois" <[EMAIL PROTECTED]> >>Date: 26 Feb 2002 08:38:22 -0600 >> > >>I cvsuped and built world and kernel this morning, and the kernel hangs >>at atkbd0: flags 0x1 irq 1 on atkbdc0. >> > > I didn't see that problem. Indeed, my (desktop) build machin

perl5.6.1

Hi, It would be nice to see this version of perl in -CURRENT. It would help ease the development of mod_perl-2.0 by not having to install the port and it just makes sense considering the bleeding-edge of the rest of the system. Thanks, Pete... To Unsubscribe: send mail to [EMAIL PROTECTED] w

Re: Are there periodic "GOOD" tags in CVS for -CURRENT?

I was suggesting this at the kernel meeting To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Known good date for -current

Ooops... my previous answer (sorry, I was too fast with the delete key, so no real reply) was from a wrong source tree (a RELENG_4_5 one, good by definition), my known good -current world is from 200202251130 (german mirror). Sorry, Alexander. -- ...and that is how we know the Earth to b

Re: ddb panics ( getdiskbyname() issue)

In message <67E0BE167008D31185F60008C7289DA0E1313F@MCHH218E>, Reifenberger Mich ael EXT writes: >Hi, >while searching the cause why "set vfs.root.mountfrom=cd9660:acd0c" >fails I found that when I do a "show disk/ad0" (when /dev/ad0* exists) >causes a panic: ( repeated make_dev("ad0")...) >while

Re: Are there periodic "GOOD" tags in CVS for -CURRENT?

Hmm. Well, part of the goal of the upcoming development snapshots is to provide that. On the other hand, I think the reason there has been less focus on that of late is that -CURRENT is actually quite stable, leaving aside a few tiny windows (for example, when I broke booting due to messing up a

Re: Patch for critical_enter()/critical_exit() & interrupt assem

On Tue, 26 Feb 2002, John Baldwin wrote: > > My suggestion will be to back it out. I would rather not have to make said > suggestion. Can you please try to fit this into the existing framework rather > than ripping it all up? We need to finalize and test the design before we > hardcode too m

ddb panics ( getdiskbyname() issue)

Hi, while searching the cause why "set vfs.root.mountfrom=cd9660:acd0c" fails I found that when I do a "show disk/ad0" (when /dev/ad0* exists) causes a panic: ( repeated make_dev("ad0")...) while "show disk/acd0" doesn't. So we have two unrelated problems here: 1.) getdiskbyname() panics the sys

Re: Are there periodic "GOOD" tags in CVS for -CURRENT?

Hello, What I've done this WE was updating a very recent -Stable box to -Current (as described in UPDATING): this sems mostly not risky : as long as the make buildworld + make buildkernel does not succeed, you keep your valid -Stable machine. this is for the upgrade to a -Current. Afterwards, t

Re: NetBSD-style rc.d Project

Should committers be updating those files when they update /etc/rc? If so, I'll need to change the sendmail startup routines. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

Re: Are there periodic "GOOD" tags in CVS for -CURRENT?

On 26 Feb, George V. Neville-Neil wrote: >> These do exist, but are very rare. > > Oh well, I'm trying to use date specs in CVS instead. 200202191650 (cvsup from a german mirror) works for me. Bye, Alexander. -- Failure is not an option. It comes bundled with your Microsoft product. http://w

Re: this morning's kernel hangs

>From: "Michael D. Harnois" <[EMAIL PROTECTED]> >Date: 26 Feb 2002 08:38:22 -0600 >I cvsuped and built world and kernel this morning, and the kernel hangs >at atkbd0: flags 0x1 irq 1 on atkbdc0. I didn't see that problem. Indeed, my (desktop) build machine built and ran today's -CURRENT just f

Re: HEADS UP: cvs commit: src/sys/conf kern.pre.mk (fwd)

On Tue, 26 Feb 2002, Garrett Wollman wrote: > < said: > > > volatile int conspeed; > > int *foo = &conspeed; > > The answer to this is > > Not all warnings are indicative of errors. It is unreasonable to > expect all warnings to be removed, since the compiler has insufficient > knowledge to

libc_r patches and some questions

Hi all, I've recieved patches from Carlos Fernando Assis Paniago <[EMAIL PROTECTED]> to get Openoffice Build 641 running. Since I'm not familiar, I hope someone else can look at them and point me to the right direction to have a working OpenOffice port. > This patch solves a readdir_r bug that

Re: Are there periodic "GOOD" tags in CVS for -CURRENT?

> These do exist, but are very rare. Oh well, I'm trying to use date specs in CVS instead. > Something like that would be lovely, mind you. > But would require some work to validate things and a bit more formality than perhaps people want. Thanks for the info though. Later, George -- Georg

Re: Are there periodic "GOOD" tags in CVS for -CURRENT?

These do exist, but are very rare. IIRC, the last such tag was pre-SMPNG. Something like that would be lovely, mind you. On Tue, Feb 26, 2002 at 09:24:30AM -0800, George V. Neville-Neil wrote: > Hi Folks, > I'm wondering if anyone has been laying down periodic "good" tags in > -CURRENT

Are there periodic "GOOD" tags in CVS for -CURRENT?

Hi Folks, I'm wondering if anyone has been laying down periodic "good" tags in -CURRENT so that people who are just starting with it have a place to start that is reasonably stable. Yes, I know about -STABLE but that's not what I mean. Thanks, George -- George V. Neville-Neil

Re: HEADS UP: cvs commit: src/sys/conf kern.pre.mk (fwd)

< said: > volatile int conspeed; > int *foo = &conspeed; The answer to this is Not all warnings are indicative of errors. It is unreasonable to expect all warnings to be removed, since the compiler has insufficient knowledge to be able to determine whether this usage is safe or not. -GAWo

Re: Patch for critical_enter()/critical_exit() & interrupt assem

:.. :> cpu_critical_enter() to a null version to prevent spinlocks masking :> interrupts doesn't work very well because it is used for other things :> that really do need to mask interrupts. Having 2 levels for :> cpu_critical_enter() (on that masks normal interrupts and one that :> masks fast i

Re: Patch for critical_enter()/critical_exit() & interrupt assem

:> rather then make it more complex. You have your fingers in just about :> every single goddamn file in the system and you and others have cried :> wolf one too many times. I am through with playing that game. :> :> The commit goes in. I am open to any suggestions you have for

Re: calcru: negative time of XXX

please send me /var/run/dmesg.boot from a "boot -v" on a current kernel and output from "sysctl kern.timecounter" please ? In message <[EMAIL PROTECTED]>, Frode Nordahl writ es: >Hey, > >I've had the microuptime problem some time, and I have somewhat followed >the discussion about this on -curr

calcru: negative time of XXX

Hey, I've had the microuptime problem some time, and I have somewhat followed the discussion about this on -current. It seems like the patch committed removed the messages, but they are now replaced by messages like: Feb 24 17:28:26 gandalf kernel: calcru: negative time of -680109 usec for pid 9

Re: FreeBSD/i386 "make release" breakage

On Wed, Feb 27, 2002 at 12:19:01AM +0900, Makoto Matsushita wrote: > murray> I'm currently looking into #2 and #3, as well as working with Ted > murray> Lemon from the ISC to fix some symbol pollution that this whole mess > murray> has exposed. Any other ideas? > > Currently nothing, it seems th

Re: NetBSD-style rc.d Project

On Tue, 26 Feb 2002 10:00:52 EST, Kevin Way wrote: > At this point, I'm very willing to help anybody who is doing the > main development, with either coding or testing, but I have no > interest being a lead developer on the project. Have you been in contact with Gordon Tetlow to see how he's f

Re: FreeBSD/i386 "make release" breakage

murray> I'm currently looking into #2 and #3, as well as working with Ted murray> Lemon from the ISC to fix some symbol pollution that this whole mess murray> has exposed. Any other ideas? Currently nothing, it seems that #3 (or its variant) is better IMHO. -- - Makoto `MAR' Matsushita To Uns

Re: NetBSD-style rc.d Project

As one of the many people who've done some initial work on the port, I can tell you that it seems to me that there's not a lot of interest in this project, beyond criticizing the work of those who've made attempts to do any work, or attempting to expand the scope of the project requirements beyon

Re: Patch for critical_enter()/critical_exit() & interrupt assem

On 26-Feb-02 Bruce Evans wrote: > On Tue, 26 Feb 2002, John Baldwin wrote: > >> The critical section stuff currently in current is part of the original >> preemption patches I wrote at Usenix last year. They aren't in the tree >> because they aren't stable yet. We still have problems on the al

Re: Patch for critical_enter()/critical_exit() & interrupt assem

On 26-Feb-02 Matthew Dillon wrote: >:1) I had an ugly panic testing it on the alpha. After a good deal of >:sleuthing, >: I've determined that we still have some preemption related bugs in >: possibly >: the alpha pmap, but that td_ucred isn't the problem. >:2) I've been thinking about the

Re: HEADS UP: cvs commit: src/sys/conf kern.pre.mk (fwd)

On Mon, Feb 25, 2002 at 11:35:12PM -0700, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > Mike Makonnen <[EMAIL PROTECTED]> writes: > : On Mon, 2002-02-25 at 20:59, M. Warner Losh wrote: > : > I've fixed a few of the low hanging fruit, but I don't know how to get > : > rid of

this morning's kernel hangs

I cvsuped and built world and kernel this morning, and the kernel hangs at atkbd0: flags 0x1 irq 1 on atkbdc0. -- Michael D. Harnois bilocational bivocational Pastor, Redeemer Lutheran ChurchWashburn, Iowa 1L, UST School of Law Minneapolis, Mi

Re: FreeBSD/i386 "make release" breakage

On Tue, Feb 26, 2002 at 06:39:22PM +0900, Makoto Matsushita wrote: > Note that new dhclient requires some libraries which are *not* > installed to /usr/lib (libdhcp, libres, libomapi, and libdst). Installing them to /usr/lib wouldn't help for the crunched case anyway. > I have tried a quick hac

NetBSD-style rc.d Project

Looking at the repository, I have not really seen anything done with building a NetBSD-style rc.d system that will provide FreeBSD functionality for a long time. In fact, I can find very little aside from the initial import. I also noticed there was no mention in the last Monthly Report. Did any o

Re: ACPI timecounter help needed!

In message <[EMAIL PROTECTED]>, Yann Berthier writes: > > FYI, the increase from 15 to 31 in acpi_timer.c was needed for me to > have my kernel boot with acpi loaded (ie no hang during boot). Thanks, this was the kind of info I needed! > Anyway, my system died after 2 hours or so of use, a

Re: ACPI timecounter help needed!

On Mon, 25 Feb 2002, Poul-Henning Kamp wrote: > > Machines with ACPI timecounters will now print 10 lines at boot when > the timer is tested. > > If you are lucky you will see ten times something like: > ACPI timer looks GOOD min = 3, max = 3, width = 1 > That means that you have well imp

  1   2   >