On Tue, Apr 24, 2001 at 10:25:47PM +0200, Riccardo Torrini wrote:
# man man
Formatting page, please wait...mdoc error: end-macro (.em)
respecification is not allowed. (#20)
Should this have been `.Em ...'?
User Abort.
Done.
This happens over last week. World of this night (after
On Tue, 24 Apr 2001 22:25:47 +0200, Riccardo Torrini wrote:
This happens over last week. World of this night (after
cvsup with also make kernel and mergemaster, for 4 times).
I have also tryed to remove all */man/cat*/*gz compiled
manuals with but luck :( Any hints? Thanks.
Check for
On Tue, 24 Apr 2001, Bruce A. Mah wrote:
[...]
There are two disadvantages to going this route. I think they're
fairly minor:
1. Generating a set of release notes requires the DocBook toolchain
to be built, as well as the doc/ subtree. Note that RELNOTESng
will have
On Mon, Apr 23, 2001 at 11:33:24AM -0700, John W. De Boskey wrote:
After some feedback, I have changed the patch slightly. Rename
-d to -t and remove the requirement for the option to have a
value.
I thought people generally agreed the right fix was to add functionality
to `xargs', not
On 25-Apr-01 (01:31:59/GMT) Garrett Wollman wrote:
The ``can't assign resources'' messages indicate that the
devices are legacy ISA devices for which a non-PnP-aware
driver is compiled into the kernel. These include devices
such as keyboard...
This means that I can remove this lines?
On 25-Apr-01 (07:55:22/GMT) Sheldon Hearn wrote:
Check for catpages in */man/en.ISO_8859-1/cat* as well,
using your own locale-dependent directory, of course.
Only have /usr/share/man/en.ISO_8859-1/ but all dirs under
this path (cat[1-9n] and cat1aout) are empty :-(
# gzip -l cat1/man.1.gz
On 25-Apr-01 (07:18:57/GMT) Ruslan Ermilov wrote:
There was a problem caused by broken `make cleandir' behavior.
Make sure you have src/share/mk/bsd.obj.mk, revision 1.35.
# $FreeBSD: src/share/mk/bsd.obj.mk,v 1.35 2001/04/23 14:47:40 ru Exp $
Going to make another world this night :(
On Wed, 25 Apr 2001 10:17:22 +0200, Riccardo Torrini wrote:
Even removing cat1/man.1.gz man re-create same empty file.
Also making man formatting by hand show same error:
Then Ruslan's comments stand. I built and installed world from the
updated sources that Ruslan's suggesting and still
On Mon, Apr 23, 2001 at 11:33:24AM -0700, John W. De Boskey wrote:
After some feedback, I have changed the patch slightly. Rename
-d to -t and remove the requirement for the option to have a
value.
I thought people generally agreed the right fix was to add functionality
to `xargs',
takhus Perhaps the *.TXT files could be periodically regenerated to their
takhus current location to 1) avoid a POLA violation and 2) allow for at
takhus least some RELNOTES without needing DocBook and doc/ (even if they
takhus may be slightly out of date).
I second this.
It is true that
On Wed, 25 Apr 2001 10:01:18 -0400, John W. De Boskey wrote:
I am dealing with a production process that currently runs
approximately 10 hours. (on 28 866Mhz processors, 2 Netapps).
This process fell into my lap about 2 months ago.
Something to consider is that you're trying to solve a
Hi David, Brian,
Thank you for taking the time to reply. I hope you were
able to review the patch also.
I am dealing with a production process that currently runs
approximately 10 hours. (on 28 866Mhz processors, 2 Netapps).
This process fell into my lap about 2 months ago.
After
John W. De Boskey wrote:
Hi David, Brian,
Thank you for taking the time to reply. I hope you were
able to review the patch also.
I am dealing with a production process that currently runs
approximately 10 hours. (on 28 866Mhz processors, 2 Netapps).
This process fell into my lap
Hi,
It seems that recent lint modifications made impossible to build the
-current world on 4-stable system, thus breaking source upgrade path
from -stable to -current.
Please fix.
-Maxim
=== usr.bin/xlint
=== usr.bin/xlint/lint1
cc -pipe -mpreferred-stack-boundary=2 -O -march=k6 -I.
[Please keep me as one of the explicit recipients of this email.
Thanks.]
If memory serves me right, Makoto MATSUSHITA wrote:
takhus Perhaps the *.TXT files could be periodically regenerated to their
takhus current location to 1) avoid a POLA violation and 2) allow for at
takhus least
On Wed, Apr 25, 2001 at 09:58:40AM -0700, Bruce A. Mah wrote:
[Please keep me as one of the explicit recipients of this email.
Removing *.TXT files also makes some difficulties when ordinally make
buildworld/installworld users want to know what changes are made
(they should change their
On Wed, 25 Apr 2001 09:57:14 +0200 (CEST), Riccardo Torrini [EMAIL PROTECTED]
said:
This means that I can remove this lines? Sure?
device atkbdc 1
No, I said nothing of the sort.
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the
At 10:01 AM -0400 4/25/01, John W. De Boskey wrote:
Hi David, Brian,
Thank you for taking the time to reply. I hope you were
able to review the patch also.
Every time you have asked for people's opinions, they have
said that it seems wrong to made add a specific option to
the 'cp' command
Hello,
i've discovered that now the world cannot be built without any
optimization options (-Oxx) due to a 'dirty' code in some places. one of
good examples is usr.sbin/rpc.lockd. without -Oxx options kern.c fails
compilation:
cc -pipe -march=k6 -I. -I/usr/include/rpcsvc -g-o rpc.lockd
However, a specific hack to cp(1) is what a lot of people don't like.
If FreeBSD contained every little hack every committer had used to
address specific problems, it'd be a mess.
I was told that the hack everyone is referring to is already
implemented in several other operating systems, but
It seems to me that these things are not boot-time tunable, and
should be (really, they should be runtime tunable, but there
$ sysctl -a | grep maxf
kern.maxfiles: 360
kern.maxfilesperproc: 360
`maxfiles' and `maxfilesperproc' have been runtime tunable for more
than 5 years (but
I originally sent this to freebsd-stable but didn't get any replies. It
has been reworded.
I ran across this while playing with the INSTALL knob in make.conf. In
almost all of the Makefiles in src/ there is either -C or -c hard coded as
an argument to install. This means that changes you make
[.]
The xargs weenies have also offered an explicit patch that
could be tried, but that patch is being ignored by you. It
is not a matter of talking ourselves to death, it's a matter
that we're looking for feedback from anyone who wants to
respond to the proposed xargs changes.
If
It is inconceivable that the proposed patch to 'xargs' would
increase your running time. I don't mean the standard '-I'
change, which would certainly destroy performance, but the
proposed patch to 'xargs' which solves your specific problem
in a general way.
I'm still curious as to why
Here's my thoughts...for the record, I'm weakly opposed to regen-ing
*.TXT versions: First, I don't want to bloat the repository with oodles
of builds to the *.TXT files. If we do this, it ought to be be fairly
infrequently, like maybe once or twice a month.
Bad idea..
Hey whatever. Let's just keep a rendered TXT version where it always
(ie. in the src/release... cvs) was but keep the originial as a sgml
version in the doc tree.
Just like ports/INDEX. Only better.
I think it is important to solve the duplication problem we have. It
would be very sad to see a
On Wed, Apr 25, 2001 at 09:42:07PM +0200, Leif Neland wrote:
Here's my thoughts...for the record, I'm weakly opposed to regen-ing
*.TXT versions: First, I don't want to bloat the repository with oodles
of builds to the *.TXT files. If we do this, it ought to be be fairly
If memory serves me right, Wilko Bulte wrote:
On Wed, Apr 25, 2001 at 09:42:07PM +0200, Leif Neland wrote:
As UPDATING may contain information nessecary to run make world, it can't b
e built by make world.
Chicken and egg, methinks...
Possibly. But I was not refering to UPDATING.
Just
On Wed, Apr 25, 2001 at 09:42:07PM +0200, Leif Neland wrote:
Here's my thoughts...for the record, I'm weakly opposed to regen-ing
*.TXT versions: First, I don't want to bloat the repository with oodles
of builds to the *.TXT files. If we do this, it ought to be be fairly
In message [EMAIL PROTECTED] Dima Dorfman writes:
: Riccardo Torrini [EMAIL PROTECTED] writes:
:pca1: AT-style speaker sound at port 0x61 on isa0
:WARNING: Driver mistake: repeat make_dev(pcaudio)
:WARNING: Driver mistake: repeat make_dev(pcaudioctl)
:
: As it says, this is a driver
aIn message [EMAIL PROTECTED] John W. De Boskey writes:
:I must say at this point, I tend to agree with him. Basically,
: my review request was skipped over and folks simply went on to
: discuss/argue the merits/demerits of various patchs to xargs. The
: question of whether xargs is
In message [EMAIL PROTECTED] Maxim Sobolev writes:
: It seems that recent lint modifications made impossible to build the
: -current world on 4-stable system, thus breaking source upgrade path
: from -stable to -current.
Agreed! I have a few fixes to -current/-stable so that you can build
In message [EMAIL PROTECTED] Antoine Beaupre (LMC) writes:
: Hey whatever. Let's just keep a rendered TXT version where it always
: (ie. in the src/release... cvs) was but keep the originial as a sgml
: version in the doc tree.
UPDATING will continue to be a flat file, or I will no longer
In message [EMAIL PROTECTED] Warner Losh writes:
: In message [EMAIL PROTECTED] Antoine Beaupre (LMC) writes:
: : Hey whatever. Let's just keep a rendered TXT version where it always
: : (ie. in the src/release... cvs) was but keep the originial as a sgml
: : version in the doc tree.
:
:
On 25-Apr-01 Warner Losh wrote:
In message [EMAIL PROTECTED] Dima Dorfman
writes:
: Riccardo Torrini [EMAIL PROTECTED] writes:
:pca1: AT-style speaker sound at port 0x61 on isa0
:WARNING: Driver mistake: repeat make_dev(pcaudio)
:WARNING: Driver mistake: repeat make_dev(pcaudioctl)
Weird, I installed the April 19 snap here locally on a testbox without any
problems.
Rgr, I'll try Apr 19th and send another note with some debug info if it is
still dying.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
In message [EMAIL PROTECTED] John Baldwin writes:
:
: On 25-Apr-01 Warner Losh wrote:
: In message [EMAIL PROTECTED] Dima Dorfman
: writes:
: : Riccardo Torrini [EMAIL PROTECTED] writes:
: :pca1: AT-style speaker sound at port 0x61 on isa0
: :WARNING: Driver mistake: repeat
On Sun, Apr 22, 2001 at 11:24:42AM -0500, Michael Harnois wrote:
In file included from ../../dev/bktr/bktr_audio.c:52:
../../sys/vnode.h:571: conflicting types for `vaccess_acl_posix1e'
../../sys/vnode.h:568: previous declaration of `vaccess_acl_posix1e'
../../sys/vnode.h:571: warning:
On Tue, 24 Apr 2001 16:19:59 -0700, Dima Dorfman [EMAIL PROTECTED] said:
This is not a bug. This is an FAQ. So much that it's actually
documented in (*gasp!*) the FAQ:
Unfortunately, the A in the FAQ is wrong.
The ``can't assign resources'' messages indicate that the devices are
If memory serves me right, Dima Dorfman wrote:
On a slightly related note, do you object, or
have plans to, build the release notes with the web site? It would
solve this problem very nicely.
Hi Dima--
No objections, but no plans right now either. Mostly because I don't
know enough about
Garance A Drosihn [EMAIL PROTECTED] writes:
At 10:01 AM -0400 4/25/01, John W. De Boskey wrote:
I have reduced the runtime of the process so far by a solid
hour. My change to cp is the lowest level/minimal change fix
which allows me to maintain a O(1) time constraint. I've played
with
Alfred Perlstein wrote:
* Terry Lambert [EMAIL PROTECTED] [010424 11:59] wrote:
It seems to me that these things are not boot-time tunable, and
should be (really, they should be runtime tunable, but there
are some nasty pageable region allocations for networking that
appear to require
Curious if anyone else has been having problems with pmap_remove_pages()
recently? In the past week or so, I've found that heavy load on my dual p3 600
testbox can usually trigger a page fault (prolly a null pointer deref of some
kind) in pmap_remove_pages() called from exit1(). Just now I was
Bruce A. Mah [EMAIL PROTECTED] writes:
If memory serves me right, Makoto MATSUSHITA wrote:
takhus Perhaps the *.TXT files could be periodically regenerated to their
takhus current location to 1) avoid a POLA violation and 2) allow for at
takhus least some RELNOTES without needing
Sorry for late reply.
bmah My first reaction is, is doing doc.1 *that* much of a problem? When
bmah I was testing, it didn't seem like building this consumed much time or
bmah disk space compared to the rest of the make release process (i.e.
bmah building world and several kernels). A
On Wed, 25 Apr 2001 16:57:56 -0600, Warner Losh [EMAIL PROTECTED] said:
Actually, it is a bug. The drivers in the tree should grok these pnp
ids.
Actually, no, it is not a bug. The FreeBSD drivers for these devices
manage their resources differently from the way the Windows drivers
do, and
On Wed, 25 Apr 2001 16:57:56 -0600, Warner Losh [EMAIL PROTECTED] said:
Actually, it is a bug. The drivers in the tree should grok these pnp
ids.
Actually, no, it is not a bug. The FreeBSD drivers for these devices
manage their resources differently from the way the Windows drivers
In message [EMAIL PROTECTED] Garrett Wollman writes:
: On Wed, 25 Apr 2001 16:57:56 -0600, Warner Losh [EMAIL PROTECTED] said:
:
: Actually, it is a bug. The drivers in the tree should grok these pnp
: ids.
:
: Actually, no, it is not a bug. The FreeBSD drivers for these devices
: manage
Hi,
I have a Dell Optiplex GXi 200Mhz machine which will not
boot after installing 4.3-RELEASE. After rebooting, the normal
F1 FreeBSD prompt comes up with a beep. Pressing F1 causes
the machine to beep again. I believe the following code
sequence is the failure location:
On Wed, 25 Apr 2001, Eric D. Futch wrote:
I originally sent this to freebsd-stable but didn't get any replies. It
has been reworded.
I ran across this while playing with the INSTALL knob in make.conf. In
almost all of the Makefiles in src/ there is either -C or -c hard coded as
an
50 matches
Mail list logo
