M. Warner Losh wrote:
I've fixed a few of the low hanging fruit, but I don't know how to get
rid of warnings like:
const char *foo = blah;
char *baz = foo;
when I know they are safe.
Un-const foo. The compiler assumes strings are const unless
you go out of your way to do
Mark Peek wrote:
At 9:34 AM -0800 2/25/02, David O'Brien wrote:
On Mon, Feb 25, 2002 at 11:51:54AM +0200, Maxim Sobolev wrote:
I've noticed that after a recent make world gdb started producing
warnings during startup. Please fix.
Please send patch. This will require gdb to be
Matthew Dillon wrote:
As it is, I have invested a great
deal of time and effort on this patch and it is damn well going to go
in so I can move on.
Too bad you don't have your own P4 branch... then this would
not hold you up.
(ducks)
;^)
-- Terry
To Unsubscribe: send mail to
Hi Warner,
a simple cast
char *baz = (char*)foo;
works for me.
--
Regards,
Georg.
At Mon, 25 Feb 2002 21:59:23 -0700 (MST),
M. Warner Losh [EMAIL PROTECTED] wrote:
In message: [EMAIL PROTECTED]
Peter Wemm [EMAIL PROTECTED] writes:
: There are a couple of offending files in
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
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, after
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
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 hack
I cvsuped and built world and kernel this morning, and the kernel hangs
at atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0.
--
Michael D. Harnois bilocational bivocational
Pastor, Redeemer Lutheran ChurchWashburn, Iowa
1L, UST School of Law
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 warnings
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
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
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
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 alpha and
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
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 that #3
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
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 -current.
It
:..
: 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
On Mon, 25 Feb 2002 23:35:12 -0700 (MST), M. Warner Losh [EMAIL PROTECTED] 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
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
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,
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 show
On Tue, 26 Feb 2002, Garrett Wollman wrote:
On Mon, 25 Feb 2002 23:35:12 -0700 (MST), M. Warner Losh [EMAIL PROTECTED] 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
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: AT Keyboard flags 0x1 irq 1 on atkbdc0.
I didn't see that problem. Indeed, my (desktop) build machine built
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 OpenOffice
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: sc0
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 many
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
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 so
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.
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
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
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
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 body of
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
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()
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
[[ moved to current ]]
In message Pine.BSF.4.21.0202261326390.98715-10@beppo 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
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 a
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
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,
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) a
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't
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
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
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
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't know how
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
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 THAT
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
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 expand
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. I've
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
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.
Because
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 my
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
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
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 as I can
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 using
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 anything
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 repo
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
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 infrastructure,
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 happens
[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]; [EMAIL
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 relatively sane
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 manpage doesn't
The following:
http://www.freebsd.org/cgi/cvsweb.cgi/src/include/unistd.h.diff?r1=1.46r2=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
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 model and
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 someone
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 period of
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 or
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 August or
In message: p05101401b8a1ee73f02d@[128.113.24.47]
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
mechanisms (fwd)
In-Reply-To: p05101402b8a1ffde0552@[128.113.24.47]
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 when
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
* Doug Barton [EMAIL PROTECTED] [020226 19:12] wrote:
The following:
http://www.freebsd.org/cgi/cvsweb.cgi/src/include/unistd.h.diff?r1=1.46r2=1.47
Broke compilation of bind 8 on -current built 2/24:
mkdir threaded 2 /dev/null || test -d threaded -a -w threaded
(cc
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 PROTECTED]
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 going
:
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 the term
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, or
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:
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
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 sys/param.h
#include sys/types.h
#define GROUP_R_RETURN struct group *
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 see_ms to help.
* 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 rc.conf
* 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 deliver
a
* 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 how he's
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 vnode
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 for
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
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
pages
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.
Have you been
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 sys/param.h
#include
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(int *, conspeed);
96 matches
Mail list logo
