Verba Volant 05-02-02,
Every day a new quotation translated into many languages.
_
Quotation of the day:
Author - Albert
Einstein
English - we are all very ignorant,
but not all ignorant of the same things
Italian -
siamo tutti molto ignoranti, ma non
tutti ignoriamo le stesse c
On Mon, 4 Feb 2002, John Baldwin wrote:
> Date: Mon, 04 Feb 2002 18:47:25 -0500 (EST)
> From: John Baldwin <[EMAIL PROTECTED]>
> To: Michael Reifenberger <[EMAIL PROTECTED]>
> Cc: FreeBSD-Current <[EMAIL PROTECTED]>
> Subject: RE: Making bootable recovery CD using cdboot/loader fails
...
> and le
Hi Kris,
The commit to libexec/Makefile.inc to add WFORMAT?= 1 breaks releases
because telnetd does not compile without warnings.
John
--
John Hay -- [EMAIL PROTECTED] / [EMAIL PROTECTED]
===> libexec/telnetd
cc -nostdinc -O -pipe -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD_ENVIRON -DE
NV_H
The following email address, "[EMAIL PROTECTED]" has been removed from the Verba
Volant Newsletter list.
If you did not cancel your email address or you wish to continue receiving Verba
Volant, please send an e-mail to [EMAIL PROTECTED]
Thank you and best regards,
Verba Volant
To Unsubscribe
World is breaking for me at:
===> usr.sbin/rpc.yppasswdd
cc -nostdinc -O -pipe -I/usr/src/usr.sbin/rpc.yppasswdd/../../usr.sbin/vipw
-I/usr/src/usr.sbin/rpc.yppasswdd/../../usr.sbin/ypserv
-I/usr/src/usr.sbin/rpc.yppasswdd/../../libexec/ypxfr
-I/usr/src/usr.sbin/rpc.yppasswdd/../../usr.bin/chp
On Mon, Feb 04, 2002 at 07:06:54PM -0800, Kris Kennaway wrote:
> If you use the argument that one shouldn't set WARNS because a new
> compiler will cause the tree to break, then there's no point having it
> at all since that condition will always be true.
The difference is _impending_.
--
-- D
I have a new current system that is having the strangest problem.
using vi or its clones often abruptly powers the system down, no panics,
no syslog messages. the computer is an ABIT BP6 w/ 2 500 mhz cellerons
(NOT OVERCLOCKED), two harddrives, a cdrom drive and 256M ram.
The bizzare bits..
On Fri, Jan 25, 2002 at 10:50:58AM +0200, Ruslan Ermilov wrote:
> Hi!
>
> Some background first.
>
> I am currently working on cleaning up the "false dependencies"
> issue for secure/. The attached patch p1 fixes this. This is
> done by moving the false dependencies from secure/ utilities
> di
On Tue, Feb 05, 2002 at 07:20:46AM -0800, David O'Brien wrote:
> On Mon, Feb 04, 2002 at 07:06:54PM -0800, Kris Kennaway wrote:
> > If you use the argument that one shouldn't set WARNS because a new
> > compiler will cause the tree to break, then there's no point having it
> > at all since that co
>Date: Tue, 5 Feb 2002 06:21:34 -0800
>From: Edwin Culp <[EMAIL PROTECTED]>
>World is breaking for me at:
>===> usr.sbin/rpc.yppasswdd
>...
Following patch got through it for me:
Index: usr.sbin/rpc.yppasswdd/pw_util.c
===
RCS fi
Garrett Wollman wrote:
> <
>
>>I noticed a patch on freebsd-scsi a while back that
>>added a not very complete form of atapi as scsi support
>>to the freebsd kernel. Are there plans to complete
>>this and add it to -current sometime before -current
>>turns into 5.0-RELEASE? Thanks for any
> Is there a place where I can find this updated patch which will work for
> me in the current -current? Thanks.
I put up updated patches at
http://www.cuivre.fr.eu.org/~thomas/atapicam/
For -CURRENT, you should be using the latest one (of today)
which fixes a silly line inversion.
I'd be v
Hi!
I checked and compiled the recent -CURRENT tree,
buildworld and buildkernel goes all fine.
When booting it seems to crash on initialization of my
Promise controller and get "bad ivar request (4)". I
stripped all possible drivers out of the kernelconfig,
except for the ata driver, and it stil
Non x86 FreeBSD developers:
I have posted to http://www.freebsd.org/~julian/adiff
a set of 'semi-cosmetic' "mechanical" diffs.
The effect of the diffs is to remove all the places in the code
which assume that the thread structure is embedded in the process
structure, without doing any major alg
ata-raid.o: In function `ar_attach':
ata-raid.o(.text+0xc0): multiple definition of `ar_attach'
if_ar.o(.text+0x10): first defined here
/usr/libexec/elf/ld: Warning: size of symbol `ar_attach' changed from
663 to 777 in ata-raid.o
The ata-raid author should have checked whether there was already
On 05-Feb-02 Michael Reifenberger wrote:
> On Mon, 4 Feb 2002, John Baldwin wrote:
>
>> Date: Mon, 04 Feb 2002 18:47:25 -0500 (EST)
>> From: John Baldwin <[EMAIL PROTECTED]>
>> To: Michael Reifenberger <[EMAIL PROTECTED]>
>> Cc: FreeBSD-Current <[EMAIL PROTECTED]>
>> Subject: RE: Making bootable
On Tuesday, February 5, 2002, at 01:04 , Kris Kennaway wrote:
> On Tue, Feb 05, 2002 at 07:20:46AM -0800, David O'Brien wrote:
>> On Mon, Feb 04, 2002 at 07:06:54PM -0800, Kris Kennaway wrote:
>>> If you use the argument that one shouldn't set WARNS because a new
>>> compiler will cause the tree
On Tue, Feb 05, 2002 at 10:12:15PM -0500, Jeroen C.van Gelderen wrote:
> > On Tue, Feb 05, 2002 at 07:20:46AM -0800, David O'Brien wrote:
> >> On Mon, Feb 04, 2002 at 07:06:54PM -0800, Kris Kennaway wrote:
> >>> If you use the argument that one shouldn't set WARNS because a new
> >>> compiler wil
In message: <[EMAIL PROTECTED]>
Kris Kennaway <[EMAIL PROTECTED]> writes:
: On Tue, Feb 05, 2002 at 07:20:46AM -0800, David O'Brien wrote:
: > On Mon, Feb 04, 2002 at 07:06:54PM -0800, Kris Kennaway wrote:
: > > If you use the argument that one shouldn't set WARNS because a new
: > > c
At 8:08 PM -0800 2/5/02, Kris Kennaway wrote:
>On Tue, Feb 05, 2002 at 10:12:15PM -0500, Jeroen C.van Gelderen wrote:
>
>> David is about to switch to GCC 3.0 and I guess he does not like moving
>> targets. I would expect that for the GCC 4.0 upgrade a similar freeze
> > request will go out. An
***
$B!*9-9p!*?7$7$$!!JXMx$JJ!;c$N!!pJs$H;W$$$*Aw$j?=$7>e$2$^$7$?!#(B
***
$B$3$N%a!<%k$rITMW$H$5$l$kJ}$O62$lF~$j$^$9$,(B
$B$3$N$^$^JVAw$/$@$5$$!#%a!<%k$NAw?.$r$R$+$($5$;$F$$$?$@$-$^$9!#
With 4.5-release out the door, I thought I'd start trying to use
5.0-current on my "main freebsd machine" instead of 4.x-stable. I
figure at some point we (as developers) have got to try to migrate
to that release as much as possible.
I had been doing some stuff with 5.0-current at home. That s
In message:
Garance A Drosihn <[EMAIL PROTECTED]> writes:
: Could it be due to the DDB, INVARIANTS & WITNESS options in the
: kernel? If it is that's fine with me, I'm just wondering where
: that magnitude of a slowdown would be coming from.
No
At 11:54 PM -0500 2/5/02, Garance A Drosihn wrote:
>At 8:08 PM -0800 2/5/02, Kris Kennaway wrote:
>>All David has to do is set WARNS=0 or NO_WERROR=1 in or
>>/etc/defaults/make.conf temporarily when he tests and commits the
>>changeover, and he'll sidestep all the problems.
>
>I would assume that
I asked BDE about the same thing off-list:
Yes, the debug options (INVARIANTS and WITNESS,
especially the latter)
slow down the kernel by a factor of 10 or so. Only
progams that don't
make many syscalls run reasonably fast. I only turn
on these options
for debugging (not often). Without them, s
>
> All David has to do is set WARNS=0 or NO_WERROR=1 in or
> /etc/defaults/make.conf temporarily when he tests and commits the
> changeover, and he'll sidestep all the problems. There's no need to
> impose restrictions on the activities of other committers.
>
> It's really not a big deal, IMO
On 06-Feb-02 Garance A Drosihn wrote:
> Could it be due to the DDB, INVARIANTS & WITNESS options in the
> kernel? If it is that's fine with me, I'm just wondering where
> that magnitude of a slowdown would be coming from.
WITNESS can really hurt. Quite possibly I should turn it off in GENERIC
On Wed, Feb 06, 2002 at 07:58:53AM +0200, John Hay wrote:
> >
> > All David has to do is set WARNS=0 or NO_WERROR=1 in or
> > /etc/defaults/make.conf temporarily when he tests and commits the
> > changeover, and he'll sidestep all the problems. There's no need to
> > impose restrictions on the
It seems Tom Servo wrote:
> Hi!
>
> I checked and compiled the recent -CURRENT tree,
> buildworld and buildkernel goes all fine.
>
> When booting it seems to crash on initialization of my
> Promise controller and get "bad ivar request (4)". I
> stripped all possible drivers out of the kernelconf
The following files under sys/ still use MFREE():
alpha/tc/am7990.c
netatm/port.h
security/lomac/kernel_socket.c
Please fix.
Cheers,
--
Ruslan Ermilov Sysadmin and DBA,
[EMAIL PROTECTED] Sunbay Software AG,
[EMAIL PROTECTED] FreeBSD committer,
+380.652.512.251
30 matches
Mail list logo