On Tue, 19 Sep 2000, Matthew Jacob wrote:
>
>Oh- don't get me wrong. Valuable info. Thanks.
What would be very cool is to feed this into another script which strips
these unnecesary includes out. Then do a test build of LINT in your
local tree and if it succeeds commit a mass removal of them.
In message <[EMAIL PROTECTED]>, Matthew J
acob writes:
>
>How did you manage to generate this list. You're smoking
>crack on this one
>
>> dev/isp/isp_target.c
>>
>>
>
>as the isp_OS_PLATFORM.h includes is the only include this file has.
Well,
According to src/tools/tools/kernincl
On Wed, 20 Sep 2000, Brandon D. Valentine wrote:
> On Tue, 19 Sep 2000, Matthew Jacob wrote:
>
> >
> >Oh- don't get me wrong. Valuable info. Thanks.
>
> What would be very cool is to feed this into another script which strips
> these unnecesary includes out. Then do a test build of LINT in you
In message <[EMAIL PROTECTED]>, Matthew J
acob writes:
>
>How did you manage to generate this list. You're smoking
>crack on this one
>
>> dev/isp/isp_target.c
>>
>>
>
>as the isp_OS_PLATFORM.h includes is the only include this file has.
Oh, forgot to say: it could also be indicati
Yes, but no. Let the MAINTAINERS shoot their own lines. A script with nag mail
is good though.
On Wed, 20 Sep 2000, Brandon D. Valentine wrote:
> On Tue, 19 Sep 2000, Matthew Jacob wrote:
>
> >
> >Oh- don't get me wrong. Valuable info. Thanks.
>
> What would be very cool is to feed this int
In message <[EMAIL PROTECTED]>, "Br
andon D. Valentine" writes:
>On Tue, 19 Sep 2000, Matthew Jacob wrote:
>
>>
>>Oh- don't get me wrong. Valuable info. Thanks.
>
>What would be very cool is to feed this into another script which strips
>these unnecesary includes out. Then do a test build of LINT
On Wed, 20 Sep 2000, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Matthew J
> acob writes:
> >
> >How did you manage to generate this list. You're smoking
> >crack on this one
> >
> >> dev/isp/isp_target.c
> >>
> >>
> >
> >as the isp_OS_PLATFORM.h includes is the only
On Wed, 20 Sep 2000, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Matthew J
> acob writes:
> >
> >How did you manage to generate this list. You're smoking
> >crack on this one
> >
> >> dev/isp/isp_target.c
> >>
> >>
> >
> >as the isp_OS_PLATFORM.h includes is the only
On 20-Sep-00 Poul-Henning Kamp wrote:
>
> UNNEEDED #includes in the FreeBSD kernel
Err, how exactly are you generating these?
> i386/i386/db_interface.c
>
If you compile a kernel with KTR and DDB. *bewm*
If you are using LINT for these tests, then it probably
means that the KTR
On Wed, Sep 20, 2000 at 04:06:24 +0100, Brian Somers wrote:
> > On 17 Sep 2000, Jason Evans wrote:
> >
> > > On Fri, Sep 15, 2000 at 03:40:12PM +0100, Konstantin Chuguev wrote:
> > > > Udo Schweigert wrote:
> > > >
> > > > > after a fresh build of -current openssh does not work if connecting to
On Tue, 19 Sep 2000 18:40:43 +0400, "Andrey A. Chernov" wrote:
> With very latest kernel I got lots of
>
> microuptime() went backwards (1.3624050 -> 1.998840)
>
> messages just before
I've also seen them for the first time with today's kernel.
Interestingly, today's kernel also seems to att
* Poul-Henning Kamp <[EMAIL PROTECTED]> [000919 23:51] wrote:
>
> UNNEEDED #includes in the FreeBSD kernel
>
> agp_if.c
>
>
[snip]
These reports would be a lot more useful if you included the last person
to touch these files along with the first line of the Copyright.
-Alfred
periodic is broken in current
# /usr/sbin/periodic daily
/usr/sbin/periodic: 43: Syntax error: ")" unexpected (expecting ";;")
==
|| [EMAIL PROTECTED] ||
|| Ph. (415) 681-6235 ||
==
To Unsubscribe: send m
Hello freebsd-current!
The loader or the kernel crashed badly on my Gericom Overdose II notebook.
I was trying to boot from the bootdisk-set. The mfsroot image is successfuly
loaded and the "bootcountdown" ist displayed.
After that it looks like there are some cpu-registers dumped.
unfortunalty
On Wed, 20 Sep 2000, John Baldwin wrote:
> On 19-Sep-00 Bruce Evans wrote:
> > It really does go backwards. This is caused by the giant lock preventing
> > the clock interrupt task from running soon enough. The giant lock can
> > also prevent the clock interrupt task from running often enough e
In message <[EMAIL PROTECTED]>, John Baldwin writes:
>As for the micruptime()
>messages on boot, they only occur here on a UP kernel. On an SMP kernel I
>don't get them. Also, they always occur during mi_switch() when an interrupt
>thread is finishing and going back to sleep. The first such th
Hello everybody!
I have upgraded to this morning's (CEST) -CURRENT (must have been around
07:00 UTC). Build and installworld went fine, kernel built succesfully. I
did not change anything in the kernel config from the previous run
(which was on 15th September) but when I rebooted with the new ke
John,
I get these on an SMP kernel, which locks up the box, I can't even
figure out where exactly its happening. Maybe I'm just missing something
in my kernel config file? I assumed (from UPDATING) that no real change
was
needed to the SMP options?
The hardware is an Intel N440BX motherbo
more info,
the N440BX has a symbios scsi card on board and an fxp card onboard.
I'm using relatively old scsi drives (4500 RPM seagates and HP drives)
I have softupdates on, and I'm now using COMPAT_OLDPCI for now, although I
only turned it back on after seeing that was the only real change I made
Hi,
since this morning, the SysVR4 modules appear to be broken:
[...]
===> streams
make: don't know how to make @/svr4/svr4_types.h. Stop
*** Error code 2
Stop in /usr/src/sys/modules.
*** Error code 1
Stop in /usr/src/sys/compile/BOFH.
Anyone know how to fix this?
TIA,
s.
To Unsubscri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 20 Sep 2000, Szilveszter Adam wrote:
> floppy drive was not probed, and the fdc simply said:
>
> fdc0: cannot reserve I/O port range
You don't happen to have a DPT raid card in that do you? Just
wondering if on the off chance it is
On Wed, Sep 20, 2000 at 10:34:31AM -0500, Visigoth wrote:
> On Wed, 20 Sep 2000, Szilveszter Adam wrote:
> > floppy drive was not probed, and the fdc simply said:
> >
> > fdc0: cannot reserve I/O port range
>
> You don't happen to have a DPT raid card in that do you? Just
> wondering if o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 20 Sep 2000, Adam Szilveszter wrote:
>
> Uhm, no:-)
Oh well... *sigh* no end in sight...
It was worth a try ;)
Visigoth
Damieon Stark
Sr. Unix Systems Administrator
[EMAIL PROTECTED]
PGP Public Key: www.telemere.net/~visigoth/vi
[ OpenSSH failure with particular malloc.conf flags ]
> Got it !
>
> See version 1.6 of src/lib/libc/stdlib/setenv.c. This took me all
> night - Up for work in two hours !!! :-(
Good catch!
Nate
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body
Sniff! I feel so left out, I have so little time to play these days.
You guys are all doing really exciting work, congratulations!
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of t
On 20-Sep-00 Siobhan Patricia Lynch wrote:
> John,
> I get these on an SMP kernel, which locks up the box, I can't even
> figure out where exactly its happening. Maybe I'm just missing something
> in my kernel config file? I assumed (from UPDATING) that no real change
> was
> needed to the
In message <94952.969433843@critter> Poul-Henning Kamp writes:
: Oh, forgot to say: it could also be indicative of options not
: excercised by NOTES/LINT...
There are a few NEWCARD/OLDCARD issues that you catch here I'll
fix the rest. Thanks!
Warner
To Unsubscribe: send mail to [EMAIL PR
In message <[EMAIL PROTECTED]>, Warner Losh writes:
>In message <94952.969433843@critter> Poul-Henning Kamp writes:
>: Oh, forgot to say: it could also be indicative of options not
>: excercised by NOTES/LINT...
>
>There are a few NEWCARD/OLDCARD issues that you catch here I'll
>fix the rest.
In message <98558.969478759@critter> Poul-Henning Kamp writes:
: In message <[EMAIL PROTECTED]>, Warner Losh writes:
: >In message <94952.969433843@critter> Poul-Henning Kamp writes:
: >: Oh, forgot to say: it could also be indicative of options not
: >: excercised by NOTES/LINT...
: >
: >There ar
Can the configuration for bootup and initial installation be configured to
detect (and configure) a serial console. This would be very useful for
rackmount systems. Yes, I know it can be done manually after the
installation is completed with a monitor; but this would save some time.
If I'm m
* Forrest Aldrich <[EMAIL PROTECTED]> [000920 12:46] wrote:
> Can the configuration for bootup and initial installation be configured to
> detect (and configure) a serial console. This would be very useful for
> rackmount systems. Yes, I know it can be done manually after the
> installation i
> It seems that recent (the last two weeks?) changes to periodic have
> changed things so that non-root users of it no longer get any output.
>
> A simple fix would be to change the default output to $USER (not yet
> tested). However, having a user-specific periodic.conf would be a lot
> more use
> Can the configuration for bootup and initial installation be configured to
> detect (and configure) a serial console. This would be very useful for
> rackmount systems. Yes, I know it can be done manually after the
> installation is completed with a monitor; but this would save some time.
> periodic is broken in current
>
> # /usr/sbin/periodic daily
> /usr/sbin/periodic: 43: Syntax error: ")" unexpected (expecting ";;")
Oops, fixed. Thanks.
> ==
> || [EMAIL PROTECTED] ||
> || Ph. (415) 681-6235 ||
> =
> Can the configuration for bootup and initial installation be configured to
> detect (and configure) a serial console. This would be very useful for
The current installation "detects" serial console situations if you
have a BIOS capable of properly instructing the loader about this or
if you
> UNNEEDED #includes in the FreeBSD kernel
:
:
> dev/randomdev/harvest.c
>
>
>
>
> dev/randomdev/hash.c
>
>
>
> dev/randomdev/randomdev.c
>
>
>
> dev/randomdev/yarrow.c
>
>
From: "Roman Shterenzon" <[EMAIL PROTECTED]>
> On Tue, 19 Sep 2000 [EMAIL PROTECTED] wrote:
> > Yeah probably should...perhaps suggest it to -docs. Someone (from
> > something.edu, perhaps rpi.edu) posted a URL to one of the lists of a
> > working but untested rpc.lockd. You might like to try it..
On 19-Sep-00 Bruce Evans wrote:
> On Tue, 19 Sep 2000, Andrey A. Chernov wrote:
>
>> With very latest kernel I got lots of
>>
>> microuptime() went backwards (1.3624050 -> 1.998840)
>>
>> messages just before
>>
>> Mounting root from ufs:/dev/da0s1a
>
> It really does go backwards. This is
38 matches
Mail list logo
