After discussing it with Peter we agreed that we will do the milestone 3
commi in several stages.
First will be a diff-reduction commit, in which we make very little
functional differnce to current but add and use various macros and structure
renamings
that are needed for KSE/3 but which ar
Hi
I am trying to build -CURRENT world on 4.4-RELEASE machine:
walder#/ext/current/src 129_ make buildworld
--
Rebuilding the temporary build tree
--
rm -rf
CHOI Junho wrote:
KS == KT Sin [EMAIL PROTECTED] writes:
KS If you have usbd running, just hot attach the USB device (serial, etc).
KS You are probably using devfs on your -CURRENT. The correct /dev/* entries
KS will be created automagically once the hardware device is probed
Thus spake Miguel Mendez [EMAIL PROTECTED]:
On Sat, 02 Feb 2002 03:29:50 -0800
Terry Lambert [EMAIL PROTECTED] wrote:
Hi Terry et al,
Let me know the form you want the hierarchy to take, so
you can stick it into the GTK hierarchy thingy; I'll be
happy to crank out some quick yacc and
On Fri, 1 Feb 2002, Peter Wemm wrote:
- AMD write cache allocation due to speculative writes being cancelled and
then written back later vs no cache snooping on AGP regions. I'm somewhat
perplexed about this issue, there's lots of conflicting info going around,
a good deal of it which
IdlePTD at phsyical address 0x00487000
initial pcb at physical address 0x003702c0
panicstr: bremfree: bp 0xd3bf08d0 not locked
panic messages:
---
panic: softdep_setup_inomapdep: found inode
syncing disks... panic: bremfree: bp 0xd3bf08d0 not locked
Uptime: 1h49m20s
pccbb0: pccbb_power:
Narvi wrote:
Speculative writes can only happen to pages in the TLB (so you don't get
speculative TLB misses and replacements), not having a large amount of 4M
pages around in the TLB means that addresses covered by these can't
possibly be involved in speculative writes.
I personaly
On Sun, 3 Feb 2002, John Polstra wrote:
The kernel from today's current (CVSupped 3 Feb 2002 around 17:40
PST) can't stay up for more than a few minutes without getting a
page-not-present panic at line 1815 of ufs/ffs/ffs_alloc.c revision
1.86. It is in this code:
/*
*
On Sun, Feb 03, 2002 at 07:51:52AM -0800, Mark Murray wrote:
markm 2002/02/03 07:51:52 PST
Modified files:
lib/libpam Makefile.inc
Log:
Turn on fascist warning mode.
Revision ChangesPath
1.4 +3 -1 src/lib/libpam/Makefile.inc
This delta
Andrew Cowan wrote:
However, I have previously thought that a system that used xml files to
store application configs (that would then be used to generate valid conf
files) would be useful.
I was on the verge of doing so the other day. Basically, I wanted to
have standard configuration
On Mon, 4 Feb 2002, Terry Lambert wrote:
Narvi wrote:
Speculative writes can only happen to pages in the TLB (so you don't get
speculative TLB misses and replacements), not having a large amount of 4M
pages around in the TLB means that addresses covered by these can't
possibly be
We have been requested to insert the following email address, [EMAIL PROTECTED],
in the Verba Volant Newsletter database. Through this daily service you will receive a
quotation, selected from amongst the most celebrated philosophers, writers and poets
of all time and translated into many
If this fixes a problem, then please go ahead and commit it. :-)
M
On Sun, 3 Feb 2002, John Polstra wrote:
The kernel from today's current (CVSupped 3 Feb 2002 around 17:40
PST) can't stay up for more than a few minutes without getting a
page-not-present panic at line 1815 of
In message: [EMAIL PROTECTED]
Vladimir B. Grebenschikov [EMAIL PROTECTED] writes:
: I am trying to build -CURRENT world on 4.4-RELEASE machine:
...
: Any suggestions ?
I can tell you that 4.5-release will work.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
Hi,
I don't know whether the suggested approach is really a good one or not, but
as far as implementing some registry-like features in FreeBSD, we have
developped something that proves to be useful. The idea was to extend the
sysctl mechanism to make it dynamic from the user-land point of view.
In article [EMAIL PROTECTED],
Alfred Perlstein [EMAIL PROTECTED] wrote:
* Bruce Evans [EMAIL PROTECTED] [020204 05:26] wrote:
This was broken by a recent change to the type of NBBY.
`start' is apparently negative (it would be for blkno == 0). Small
negative values of `start' used to
On Tue, Jan 29, 2002 at 12:02:18PM -0800, David O'Brien wrote:
On Tue, Jan 29, 2002 at 07:08:21PM +0200, Ruslan Ermilov wrote:
David!
After the latest binutils import, attempts to cross-compile
Alpha fail at the cross-tools stage of buildworld as shown
below. Please also note sed(1)
The kernel from today's current (CVSupped 3 Feb 2002 around 17:40
PST) can't stay up for more than a few minutes without getting a
page-not-present panic at line 1815 of ufs/ffs/ffs_alloc.c revision
1.86. It is in this code:
/*
* Find the size of the cluster going
I'm experiencing the following error while bulding world:
Fix committed.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Mon, Feb 04, 2002 at 06:43:23PM +0200, Ruslan Ermilov wrote:
The fix was as simple as this:
Thanks!! Committed.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Mon, Feb 04, 2002 at 03:30:32PM +0200, Ruslan Ermilov wrote:
This delta breaks buildworld. gcc(1) has a known bug-feature
of hiding some errors in standard system headers, making them
invisible without -I.
...
and compile now can't survive the WARNS=4.
Not to mention there is ZERO way
* Bruce Evans [EMAIL PROTECTED] [020204 05:26] wrote:
On Sun, 3 Feb 2002, John Polstra wrote:
The kernel from today's current (CVSupped 3 Feb 2002 around 17:40
PST) can't stay up for more than a few minutes without getting a
page-not-present panic at line 1815 of ufs/ffs/ffs_alloc.c
On Mon, 4 Feb 2002, Alfred Perlstein wrote:
* Bruce Evans [EMAIL PROTECTED] [020204 05:26] wrote:
This patch just backs out the change to NBBY.
Wouldn't this make more sense:
Index: ffs/ffs_alloc.c
===
RCS file:
On Mon, Feb 04, 2002 at 03:56:45PM +, Mark Murray wrote:
If this fixes a problem, then please go ahead and commit it. :-)
Many reasons to not rush this:
Maybe because we are in the middle of a discussion.
Maybe to educate others why the change was bad so others will not attempt
the same
Hi!
Alpha buildworld is still broken due to the WARNS=4 change:
: cc -O -pipe -nostdinc
:-I/CURRENT/usr/src/lib/libpam/libpam/../../../contrib/libpam/libpam/include
:-I/CURRENT/usr/src/lib/libpam/libpam/../../../contrib/libpam/libpam_misc/include
On Mon, Feb 04, 2002 at 09:06:56AM -0800, David O'Brien wrote:
On Mon, Feb 04, 2002 at 06:43:23PM +0200, Ruslan Ermilov wrote:
The fix was as simple as this:
Thanks!! Committed.
Great! /me fires up the DS10..
--
| / o / /_ _ [EMAIL PROTECTED]
|/|/ / / /( (_) Bulte
David O'Brien [EMAIL PROTECTED] writes:
Not to mention there is ZERO way this code will pass WARNS=4 for GCC 3.
Please Committers, do not try to WARNS code right now -- there just is no
use. It will only get in the way later.
Well, of course feel free to make the code changes, but PLEASE
The patch is attached.
Thanks! Committed.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
In order to make some real progress on the ATA RAID support code I've
also made some rather trivial but many changes all over the ATA subsystem,
so if behavior changes on ordinary system I'd like to know...
In short - you have been warned ...
-Søren
To Unsubscribe: send mail to [EMAIL
Now that current on Alpha builds a lot better than a
few days back it fails in:
cc -nostdinc -O -pipe -mcpu=ev4 -mcpu=ev4
-I/usr/src/lib/libpam/libpam/../../../contrib/libpam/libpam/include
-I/usr/src/lib/libpam/libpam/../../../contrib/libpam/libpam_misc/include
M. Warner Losh [EMAIL PROTECTED] writes:
I just upgraded my laptop to -current to start working on some
lingering newcard + acpi problems (like the panic on boot due to
interrupt issues). So I notice a new message on my console when I log
in via xdm:
Feb 3 16:18:44 hammer : PAM unable to
On Mon, 2002-02-04 at 19:00, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Vladimir B. Grebenschikov [EMAIL PROTECTED] writes:
: I am trying to build -CURRENT world on 4.4-RELEASE machine:
...
: Any suggestions ?
I can tell you that 4.5-release will work.
What happens
On Tue, Feb 05, 2002 at 01:30:53AM +1030, Mike Gratton wrote:
However, I have previously thought that a system that used xml files to
store application configs (that would then be used to generate valid conf
files) would be useful.
I was on the verge of doing so the other day. Basically,
Narvi wrote:
I wasn't aware that I was contradicting Peter 8-)
Sorry; looked like it to me... 8-).
It may even well be possible to get different results with aligned vs.
misaligned reads and writes, or a proper mix thereof. It may be possible
to build a model to track down the what is
David O'Brien wrote:
If this fixes a problem, then please go ahead and commit it. :-)
Many reasons to not rush this:
Maybe because we are in the middle of a discussion.
Maybe to educate others why the change was bad so others will not attempt
the same change later.
Maybe the person
Hi All,
I've
been battling with building current for a few days now, I've noticed that
some of the errors I've been seeing have been fixed, but today in
desperation I deleted my /usr/src tree and cvs'd it up again from the cvsup.au.freebsd.org
server.
Todays error:
===
On Mon, 2002-02-04 at 11:03, Patrick Bihan-Faou wrote:
Some may argue that storing userland data in the kernel space is Not A Nice
Thing(tm) but it certainly makes things a lot easier.
Why am I reminded of when terminal type information was bodged into the
stty settings as a 2-character code?
From: [EMAIL PROTECTED]
Date: Tue, 5 Feb 2002 11:45:32 +1100
Hi All,
I've been battling with building current for a few days now, I've noticed
that some of the errors I've been seeing have been fixed, but today in desperation I
deleted my /usr/src tree and cvs'd it up again from
Wilko Bulte [EMAIL PROTECTED] wrote:
Now that current on Alpha builds a lot better than a
few days back it fails in:
/usr/src/lib/libpam/libpam/pam_get_pass.c:60: warning: type mismatch in
implicit declaration for built-in function `memset'
/usr/src/lib/libpam/libpam/pam_get_pass.c:60:
On 02-Feb-02 Michael Reifenberger wrote:
Hi,
a CD created using the following commands fails during loading
/boot/kernel/kernel (just freezes up) under a recent current:
cd /usr/tmp
mkdir root
dump -0a -f - / | ( cd root; restore -r -f - )
dd if=/dev/zero of=root/boot/boot.catalog
Now that current on Alpha builds a lot better than a
few days back it fails in:
cc -nostdinc -O -pipe -mcpu=ev4 -mcpu=ev4
-I/usr/src/lib/libpam/libpam/../../../contrib/libpam/libpam/include
Already fixed.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this
Hi All,
I've been battling with building current for a few days now, I've
noticed that some of the errors I've been seeing have been fixed, but today in
desperation I deleted my /usr/src tree and cvs'd it up again from the
cvsup.au.freebsd.org server.
Please turn off HTML in
On Mon, Feb 04, 2002 at 09:17:17AM -0800, David O'Brien wrote:
On Mon, Feb 04, 2002 at 03:30:32PM +0200, Ruslan Ermilov wrote:
This delta breaks buildworld. gcc(1) has a known bug-feature
of hiding some errors in standard system headers, making them
invisible without -I.
...
and
FreeBSD does not want to work with my USB mouse. I believe it to be a
problem with the motherboard, a Tyan S1834. The mouse does work under
BeOS and Windows so I know it's not toast. Also, the mouse works with
FreeBSD on my Tyan S1832 motherboard so that's a good sign too.
Here's my kernel
Hi David,
I've cvsupd again using src-all and it seems to be working again now.
Thanks,
Anthony
-Original Message-
From: David Wolfskill [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, 5 February 2002 12:48 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: buildworld
On 20-Jan-02 Robert Watson wrote:
On Sat, 19 Jan 2002, Alp Atici wrote:
Is gcc 3.x going to be the default compiler starting from FBSD 5.x
series? Is the development on current branch compiled using gcc 3.0 (or
up)?
Is 5.x series going to be based on a preemptible kernel?
Can't
46 matches
Mail list logo
