Re: Do we still need portmap(8)?

2002-10-10 Thread Sheldon Hearn

On (2002/10/09 22:03), Terry Lambert wrote:

> The other problem with an mtree.obsolete is that it assumes
> the the upgrade process completes successfully.  This doesn't
> mean that it completes without an error in the upgrade process,
> it means that the resulting system functions.

Why not just let Warner (or whoever) make this "solution" available and
see how it flies?

People like you and me who have our own simple and effective ways of
pruning stale files can just ignore it or hack it out.

Ciao,
Sheldon.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: KDE 3.0 broken in current??

2002-10-10 Thread Terry Lambert

Alex Zepeda wrote:
> Admittedly I run development versions of both FreeBSD and KDE, and the
> kde-freebsd team uses stable overwhelmingly so the combination doesn't
> receive the testing that others do.
> 
> That said, I'm more than willing to review stuff and commit reasonable
> changes.  Anything regarding port specific tweaks should go to the
> kde-freebsd team, I don't use the ports or packages of KDE or Qt.

What are the chances of getting every file that comes back from:

ls /usr/ports/*/kde*/*/patch*

rolled into the KDE code itself?

These are all the FreeBSD specific patches that are needed to make
KDE happy on FreeBSD.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Do we still need portmap(8)?

2002-10-10 Thread Terry Lambert

Sheldon Hearn wrote:
> On (2002/10/09 22:03), Terry Lambert wrote:
> > The other problem with an mtree.obsolete is that it assumes
> > the the upgrade process completes successfully.  This doesn't
> > mean that it completes without an error in the upgrade process,
> > it means that the resulting system functions.
> 
> Why not just let Warner (or whoever) make this "solution" available and
> see how it flies?

It was discussed already, the last 3 times this topic came up.
I believe that the only inoffensive thing that everyone could
agree to was: "do it however you want, as long as it requires
a special (non-default) target to make it do its thing".

No one wanted a "make install" or "make installworld" or whatever
deleting things, especially if it failed.


> People like you and me who have our own simple and effective ways of
> pruning stale files can just ignore it or hack it out.

I do it manually, just like everyone else.  Normally, I build a
world, mount the image read-only, and do a full install onto a
"pingpong" partition via NFS, which buys me a clean install, and
the ability to go back to the previous root partition, if the new
image is too broken to use.

I used to have an extra target for "/bin/sysinstall" to be created
on the CDROM image, so that I could do a full upgrade via NFS from
a CDROM image (instead of booting from one, particularly on machines
that didn't netboot and had no CDROM -- read: appliances), but that
doesn't work if you have to actually delete files for things to not
break on you (the source of the current controversy: "stale" files
not removed).

Personally, I have absolutley no objection to a mtree "stale file"
removal script.  I just think it will be nearly impossible to
maintain... and if it's not active by default, it's not going to
stop the people who post about problems, especially problems with
ports.  And since it *can't* be active by default... catch-22.


-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: src/games bikeshed time.

2002-10-10 Thread Jose M. Alcaide

On Wed, Oct 09, 2002 at 10:42:46AM -0700, Nate Lawson wrote:
> On Wed, 9 Oct 2002, Jose M. Alcaide wrote:
> > What do you think about moving fortune, primes, factor, grdc, pom, etc. to
> > /usr/bin, and then removing /usr/games?
> 
> The most clever way to axe one change is to suggest an additional, more
> controversial and less necessary change, and then insist they be bundled
> together.
> 
> Too bad I have seen through your nefarious plan.

Rats!  ;-)

-- 
** Jose M. Alcaide  //  [EMAIL PROTECTED]  //  [EMAIL PROTECTED] **
** "Beware of Programmers who carry screwdrivers" --  Leonard Brandwein **

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



alpha tinderbox failure

2002-10-10 Thread Dag-Erling Smorgrav

--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
--
>>> stage 2: rebuilding the object tree
--
>>> stage 2: build tools
--
>>> stage 3: cross tools
--
>>> stage 4: populating /home/des/tinderbox/alpha/obj/h/des/src/alpha/usr/include
--
>>> stage 4: building libraries
--
>>> stage 4: make dependencies
--
>>> stage 4: building everything..
--
>>> Kernel build for GENERIC started on Thu Oct 10 03:09:06 PDT 2002
--
>>> Kernel build for GENERIC completed on Thu Oct 10 03:36:09 PDT 2002
--
>>> Kernel build for LINT started on Thu Oct 10 03:36:10 PDT 2002
--
===> vinum
"Makefile", line 4194: warning: duplicate script for target "geom_bsd.o" ignored
cc1: warnings being treated as errors
/h/des/src/sys/dev/aic7xxx/ahd_pci.c: In function `ahd_pci_map_registers':
/h/des/src/sys/dev/aic7xxx/ahd_pci.c:171: warning: implicit declaration of function 
`bus_space_subregion'
*** Error code 1

Stop in /h/des/obj/h/des/src/sys/LINT.
*** Error code 1

Stop in /h/des/src.
*** Error code 1

Stop in /h/des/src.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: HEADSUP: GCC 3.2.1 update is coming

2002-10-10 Thread Martin Blapp


Hi Alexander,

> I am going to import a new GCC 3.2.1 snapshot in about 10 minutes.
> This update fixes the problem with cpp0 dumping core while building a
> kernels many people reported on the list.

Yes, this is fixed. Just tested it with my config :P

> There might still be a problem with libm and -march=pentium4. I do not
> have P4 myself and I cannot reproduce the problem locally.

This problem is also solved. libm compiles again fine with -march=pentium4.
OpenOffice and xmms, mpg123 work as they did before.

Thank you very very much for your work !

Martin

Martin Blapp, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
ImproWare AG, UNIXSP & ISP, Zurlindenstrasse 29, 4133 Pratteln, CH
Phone: +41 061 826 93 00: +41 61 826 93 01
PGP: 
PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E
--


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



disk running out of space

2002-10-10 Thread Naga Suresh B

Hai,

  I am facing a problem in disk space, when I say df -h on my server, it
is giving the following results:-

FilesystemSize   Used  Avail Capacity  Mounted on
/dev/ad0s2a   9.6G   8.5G   337M96%/
/dev/ad2s1e55G39G11G77%/data
/dev/ad0s1e   9.6G   2.0K   8.8G 0%/data2
/dev/ad0s3e26G   1.0G23G 4%/data3
/dev/ad0s2e   9.6G   1.9G   6.9G22%/usr
procfs4.0K   4.0K 0B   100%/proc

I went into / and measured all the folders it is coming around 2GB as usable
space.

What might be the problem???

Plz give me solution as early as possible.

Suresh


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: disk running out of space

2002-10-10 Thread Ian Lister

On Thu, 10 Oct 2002, Naga Suresh B wrote:
>I went into / and measured all the folders it is coming around 2GB as usable
>space.
>
>What might be the problem???

This would probably be better on questions@ but it is possible that you
have files on the root partition under /usr that are being hidden by the
/usr partition (or any of your other partitions). Check there's nothing
`under' your mounts.

Jamie's comment about the reserved margin is also correct, but it doesn't
account for 2GB.

Ian



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: disk running out of space

2002-10-10 Thread Naga Suresh B

Thank you for your suggestion I restarted apache on my server my df -h is
giving

FilesystemSize   Used  Avail Capacity  Mounted on
/dev/ad0s2a   9.6G   1.0G   7.8G12%/
/dev/ad2s1e55G39G11G77%/data
/dev/ad0s1e   9.6G   2.0K   8.8G 0%/data2
/dev/ad0s3e26G   1.0G23G 4%/data3
/dev/ad0s2e   9.6G   1.9G   6.9G22%/usr
procfs4.0K   4.0K 0B   100%/proc

What might be the problem??? In future how can I overcome this type of
problems without restarting the service.

Suresh
- Original Message -
From: "Maxim Konovalov" <[EMAIL PROTECTED]>
To: "Naga Suresh B" <[EMAIL PROTECTED]>
Sent: Thursday, October 10, 2002 3:21 PM
Subject: Re: disk running out of space


>
> Try killall -HUP syslogd
>
> On 13:49+0400, Oct 10, 2002, Naga Suresh B wrote:
>
> > Hai,
> >
> >   I am facing a problem in disk space, when I say df -h on my
server, it
> > is giving the following results:-
> >
> > FilesystemSize   Used  Avail Capacity  Mounted on
> > /dev/ad0s2a   9.6G   8.5G   337M96%/
> > /dev/ad2s1e55G39G11G77%/data
> > /dev/ad0s1e   9.6G   2.0K   8.8G 0%/data2
> > /dev/ad0s3e26G   1.0G23G 4%/data3
> > /dev/ad0s2e   9.6G   1.9G   6.9G22%/usr
> > procfs4.0K   4.0K 0B   100%/proc
> >
> > I went into / and measured all the folders it is coming around 2GB as
usable
> > space.
> >
> > What might be the problem???
> >
> > Plz give me solution as early as possible.
> >
> > Suresh
> >
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the body of the message
> >
> >
>
> --
> Maxim Konovalov, [EMAIL PROTECTED]
>


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: disk running out of space

2002-10-10 Thread Ian Lister

On Thu, 10 Oct 2002, Naga Suresh B wrote:
>What might be the problem??? In future how can I overcome this type of
>problems without restarting the service.

Sounds like you moved/rotated/deleted your Apache log file but Apache
still had it open and continued logging to it. The space on disk will not
be freed until everything has closed the file. Check out the rotatelogs(8)
man page that comes with Apache for information about how to properly
rotate its logs.

Ian


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



2 patches for src/share/misc/bsd-family-tree

2002-10-10 Thread Sergey A. Osokin

Hello.
Please review 2 patches for src/share/misc/bsd-family-tree.

The first (original idea from Greg Lehey) sorts references
in a "Time" section by alphabet and removes U25, because it
is never referenced.

The second - adds Mac OS X 10.1 and 10.2, NetBSD 1.6,
FreeBSD 4.6.2, adds link from FreeBSD 4.4 to Mac OS X 10.2.

Thanks.
-- 

Rgdz,/"\  ASCII RIBBON CAMPAIGN
Sergey Osokin aka oZZ,   \ /AGAINST HTML MAIL
http://ozz.pp.ru/ X  AND NEWS
 / \


Index: src/share/misc/bsd-family-tree
===
RCS file: /home/ncvs/src/share/misc/bsd-family-tree,v
retrieving revision 1.63
diff -u -r1.63 bsd-family-tree
--- src/share/misc/bsd-family-tree  2002/10/10 08:57:39 1.63
+++ src/share/misc/bsd-family-tree  2002/10/10 09:46:53
@@ -171,24 +171,23 @@
and John Quarterman. The Design and Implementation of
the 4.4BSD Operating System.
 [APL] Apple website [http://www.apple.com/macosx/]
+[BSDI] Berkeley Software Design, Inc.
 [DOC] README, COPYRIGHT on tape.
-[QCU] Salus, Peter H. A quarter century of UNIX.
-[U25] Peter H. Salus. Unix at 25.
-[USE] Usenet announcement.
+[FBD] FreeBSD Project, The.
+[KB]  Keith Bostic. BSD2.10 available from Usenix. comp.unix.sources,
+   Volume 11, Info 4, April, 1987.
 [KSJ] Michael J. Karels, Carl F. Smith, and William F. Jolitz.
Changes in the Kernel in 2.9BSD. Second Berkeley Software
Distribution UNIX Version 2.9, July, 1983.
-[KB]  Keith Bostic. BSD2.10 available from Usenix. comp.unix.sources,
-   Volume 11, Info 4, April, 1987.
 [KKK] Mike Karels, Kirk McKusick, and Keith Bostic. tahoe announcement.
comp.bugs.4bsd.ucb-fixes, June 15, 1988.
-[SMS] Steven M. Schultz. 2.11BSD, UNIX for the PDP-11.
-[FBD] FreeBSD Project, The.
 [NBD] NetBSD Project, The.
 [OBD] OpenBSD Project, The.
-[dmr] Dennis Ritchie, via E-Mail
-[BSDI] Berkeley Software Design, Inc.
+[QCU] Salus, Peter H. A quarter century of UNIX.
+[SMS] Steven M. Schultz. 2.11BSD, UNIX for the PDP-11.
+[USE] Usenet announcement.
 [WRS] Wind River Systems, Inc.
+[dmr] Dennis Ritchie, via E-Mail
 
 Multics 1965
 UNIXSummer 1969


Index: share/misc/bsd-family-tree
===
RCS file: /home/ncvs/src/share/misc/bsd-family-tree,v
retrieving revision 1.63
diff -u -r1.63 bsd-family-tree
--- share/misc/bsd-family-tree  2002/10/10 08:57:39 1.63
+++ share/misc/bsd-family-tree  2002/10/10 11:20:29
@@ -145,22 +145,26 @@
  |  | |  ||OpenBSD 2.9   |
  |  | |  | NetBSD 1.5.1| |
  |  | |  ||| |
- |   FreeBSD 4.4  |  | NetBSD 1.5.2| |
- |  | |  ||| |
- |  | |  ||OpenBSD 3.0   |
- |   FreeBSD 4.5  |  ||| |
- |  | |  |||   BSD/OS 4.3
- |   FreeBSD 4.6  |  ||OpenBSD 3.1   |
- |  | |  | NetBSD 1.5.3| v
- |   FreeBSD 4.7  |  |||
- |  | |  |||
- |  v |  |v|
+ |   FreeBSD 4.4-.|  | NetBSD 1.5.2| |
+ |  || Mac OS X  ||| |
+ |  ||   10.1||OpenBSD 3.0   |
+ |   FreeBSD 4.5 ||  ||| |
+ |  | \   |  |||   BSD/OS 4.3
+ |   FreeBSD 4.6   \  |  ||OpenBSD 3.1   |
+ |  |   \ |  | NetBSD 1.5.3| v
+ |  |  Mac OS X  |||
+ |   FreeBSD 4.6.2   10.2|v|
+ |  | |  | |
+ |  | |   NetBSD 1.6   |
+ |   FreeBSD 4.7  |  | |
+ |  | |  | |
+ |  v |  | |
  ||  | |
 FreeBSD 5.0-current   |   NetBSD -current  OpenBSD -current
  ||  | |
- v Mac OS X  v v
- 10.1
+ vv  v v
 
 Time
 
 
@@ -359,6 +362,9 @@
 OpenBSD 3.12002-05-19 [OBD]
 FreeBSD 4.62002-06-15 [FBD]
 NetBSD 1.5.32002-07-22 [NBD] (patch release)
+FreeBSD 4.6.2  2002-08-15 [FBD] (patch release)
+Mac OS X 10.2  2002-09-04 [APL]
+NetBSD 1.6 2002-09-14 [NBD]
 FreeBSD 4.72002-10-08 [FBD]
 
 Bibliography



GEOM related swap errors

2002-10-10 Thread Michael McGoldrick

Since GEOM became default, I've been getting a lot of errors like these:
Oct  9 17:02:19 uriel kernel: swap_pager: I/O error - pageout failed; blkno
3240
,size 4096, error 5
Oct  9 17:02:19 uriel kernel: swap_pager: I/O error - pageout failed; blkno
1254
4,size 8192, error 5
Oct  9 17:02:19 uriel kernel: swap_pager: I/O error - pageout failed; blkno
1257
6,size 8192, error 5

These seem to go away when the kernel is built with NO_GEOM.
I added a panic just below this message in swap_pager.c - backtrace attached.
I haven't really looked at it yet and I won't be able to use this machine for
a few hours. Any assistance appreciated.

-- 
Michael McGoldrick: [EMAIL PROTECTED] 


Script started on Thu Oct 10 12:20:07 2002
uriel# gdb -k /usr/obj/usr/src/sys/URIEL/kernel.debug vmcore.0

GNU gdb 5.2.0 (FreeBSD) 20020627
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-undermydesk-freebsd"...
panic: bremfree: bp 0xc4aac768 not locked
panic messages:
---
panic: Damn swap error!


syncing disks... panic: bremfree: bp 0xc4aac768 not locked
Uptime: 2m40s
pfs_vncache_unload(): 1 entries remaining
Dumping 127 MB
ata1: resetting devices ..
ata1: mask=03 ostat0=50 ostat2=7f
ad2: ATAPI 00 00
ata1-slave: ATAPI 7f 7f
ata1: mask=03 stat0=50 stat1=7f
ad2: ATA 01 a5
ata1-slave: ATA 2d 7f
ata1: devices=01
ad2: success setting PIO4 on Acer chip
done
 16 32 48 64 80 96 112
---
#0  doadump () at /usr/src/sys/kern/kern_shutdown.c:223
223 dumping++;
(kgdb) bt
#0  doadump () at /usr/src/sys/kern/kern_shutdown.c:223
#1  0xc0222165 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:355
#2  0xc02223b3 in panic () at /usr/src/sys/kern/kern_shutdown.c:508
#3  0xc0261177 in bremfree (bp=0xc4aac768) at /usr/src/sys/kern/vfs_bio.c:632
#4  0xc0262c98 in vfs_bio_awrite (bp=0x3) at /usr/src/sys/kern/vfs_bio.c:1633
#5  0xc01ec777 in spec_fsync (ap=0xc982eac8)
at /usr/src/sys/fs/specfs/spec_vnops.c:459
#6  0xc01ebc18 in spec_vnoperate (ap=0x0)
at /usr/src/sys/fs/specfs/spec_vnops.c:124
#7  0xc0318569 in VOP_FSYNC (vp=0x0, cred=0x0, waitfor=0, td=0x0)
at vnode_if.h:612
#8  0xc0317c77 in ffs_sync (mp=0xc23c8200, waitfor=2, cred=0xc0bbae80, 
td=0xc03f2740) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:1155
#9  0xc0274fa8 in sync (td=0xc03f2740, uap=0x0)
at /usr/src/sys/kern/vfs_syscalls.c:130
#10 0xc0221dac in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:264
#11 0xc02223b3 in panic () at /usr/src/sys/kern/kern_shutdown.c:508
#12 0xc0325c89 in swp_pager_async_iodone (bp=0xc4a9b1a8)
at /usr/src/sys/vm/swap_pager.c:1471
#13 0xc0264a51 in bufdone (bp=0xc4a9b1a8) at /usr/src/sys/kern/vfs_bio.c:2983
#14 0xc0264924 in bufdonebio (bp=0x0) at /usr/src/sys/kern/vfs_bio.c:2931
#15 0xc02646c9 in biodone (bp=0x0) at /usr/src/sys/kern/vfs_bio.c:2831
#16 0xc01ee13e in g_dev_done (bp2=0xc28fe300)
---Type  to continue, or q  to quit---
at /usr/src/sys/geom/geom_dev.c:353
#17 0xc02646c9 in biodone (bp=0x0) at /usr/src/sys/kern/vfs_bio.c:2831
#18 0xc01f07f0 in g_io_schedule_up (tp=0xc0bd1d00)
at /usr/src/sys/geom/geom_io.c:343
#19 0xc01f09e8 in g_up_procbody () at /usr/src/sys/geom/geom_kern.c:91
#20 0xc020e835 in fork_exit (callout=0xc01f0960 , arg=0x0, 
frame=0x0) at /usr/src/sys/kern/kern_fork.c:851
(kgdb) uriel# ^Dexit

Script done on Thu Oct 10 12:21:49 2002



Re: 2 patches for src/share/misc/bsd-family-tree

2002-10-10 Thread Sergey A. Osokin

On Thu, Oct 10, 2002 at 03:26:21PM +0400, Sergey A. Osokin wrote:
> Hello.
> Please review 2 patches for src/share/misc/bsd-family-tree.

A little bug: release date of MacOSX 10.2 is 2002-08-23
http://www.apple.com/pr/library/2002/aug/23jaguar.html

-- 

Rgdz,/"\  ASCII RIBBON CAMPAIGN
Sergey Osokin aka oZZ,   \ /AGAINST HTML MAIL
http://ozz.pp.ru/ X  AND NEWS
 / \

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: ATTN: people who were getting CVSup crashes under -current

2002-10-10 Thread Giorgos Keramidas

On 2002-10-09 20:37, John Polstra <[EMAIL PROTECTED]> wrote:
> I am trying to understand the CVSup crashes that were reported by some
> -current users during the past week or two.  I realize the crashes
> had to do with changes in the ucontext structure, but I am trying to
> understand why those changes mattered.  My theory is that the changes
> would matter to the old pm3 port, but not to the newer ezm3 port.  If
> you experienced the crashes, please check which Modula-3 version you
> have using pkg_info and let me know.

None at all, here.  I just grabbed and pkg_added the precompiled
binaries of cvsup-without-gui-16.1f.  This isn't really helpful in
debugging the problem, but you might want to make a note about a newer
version (16.1g perhaps?) after the problems have been resolved.

Thanks for the time and effort you are putting into CVSup,

Giorgos.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Get Star Wars Episode II & a Haunted House Screensaver - Free

2002-10-10 Thread Dana

Great Free Offers:

1) Free "Star Wars: Episode II - Attack of the Clones" DVD
Click here to redeem your FREE DVD - Act now while supplies last.
http://www.freeyankee.com/cgi/fy2/to.cgi?l=1010starwars

2) Just in time for Halloween!!
Free Haunted House Screen Saver Trial!
http://govojo.freezefinds.com/cgi-bin/linktrack/go.cgi?HHouseFYruss

Interesting Low Cost Offers:

3) Make $6000/month Working from Home
We are so sure we offer an Unconditional, No-Risk Guarantee!
http://www.netbizideas.com/yankee

4) Travel Now - Pay Later
Get a $3000 travel credit line with Guaranteed Approval!
Imagine:  Cancun, Mexico $78 down or Hawaii $115 down!
http://travel.freeze.com/fyrusspvc

Offer Manager
UNSUBSCRIBE INSTRUCTIONS: If you no longer wish to receive this
newsletter, you can unsubscribe by going here:
http://tilw.net/unsub.php?client=freeyankee&msgid=9100200023
and entering your email address.


TRCK:freeyankee;Fxuuhqw*Iuhhevg!Ruj;1;






Re: Do we still need portmap(8)?

2002-10-10 Thread Danny J. Zerkel

On Wednesday 09 October 2002 17:00, Terry Lambert wrote:
> "Danny J. Zerkel" wrote:
> > And a list of files to delete would have saved many emails about the
> > GCC being broken when the old headers just needed to be deleted.
>
> No, it wouldn't.
>
> The same people who failed to read the mailing list, and see the
> first time the problem came up, and was solved, would fail to read
> the file.  The information was available after the first time the
> problem was successfully and publically addressed.

Sigh...  there should be a file listing incompatible files that is part of
the source tree.  Every file in this list would be deleted as a pre-install
step.  Perl would not have been in this list because it was not
incompatible.  But the old C++ headers clearly were.  There have
no doubt been other instances of incompatible files in the installation
or examples of files moving.  It will happen to any software system
and should be accounted for in the installation mechanism.

> I challenge you to contact everyone who has posted complaining
> about the "stale header file problem" in the last 6 months, and
> ask them what resources they looked to for a solution, before
> they contacted the mailing list.
>
> I will be incredibly surprised if you find that they have any
> single "README" or other file in common, where such information
> could have been placed.
>
> If you *do* find such a file, then you should create a patch, so
> that there will be no more postings of the question by users as
> they run into it.
>
>
> The reasons volunteers automate processes are (1) "for their own
> use", (2) "to advocate something", or (3) "to get other people to
> shut up".
>
> The reasons the topic of automating this process keep coming up
> are the same; I would say that 90% of the people involved in the
> discussion (including myself) are in camp #3.
>
> Yes, it would be nice if this were automatic, but not if it screws
> up the ability to run perl scripts (as one example).
>
>
> If you want to address it systematically, then what you can do
> *right now* is cause a file containing a build identifier to be
> installed as part of the "install world" or "install from CDROM"
> process that will allow the current system to be recreated.
>
> A delta management system is only as good as the timestamp from
> which the deltas are managed, relative to the current timestamp.
>
> Personally, I suggest a file "/etc/BUILD" be created to contain
> the CVS tag and a timestamp indicating the checkout time, created
> as part of the build process (maybe the tag from the output of a
> "CVS stat" on the Makefile in /usr/src, processed to deal with
> sticky tags, and the date stamp on the file itself, otherwise).
>

Yuck.  Let's NOT not use CVS (Cantakerous Version Scrambler) tags.

> Everything else can be hung off that.
>
> -- Terry

Danny
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Big bezier ramblings

2002-10-10 Thread walt

I trotted out xfontsel to use as a sharp stick to poke at this
bug.  I certainly succeeded at crashing the X server with it
repeatedly, but the crashes are non-deterministic.  The same
choice of font and fontsize will not reliably crash each time.

The wierd thing I did find is that, after crashing the X
server and then restarting it, I would find anywhere up to
six instances of xfontsel on the desktop instead of just one.
(Using gnome2, FWIW.)

Dunno what that means, but maybe someone else can use it as
a clue?



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: I can't compile GENERIC, please let's fix this

2002-10-10 Thread John Baldwin


On 09-Oct-2002 Kris Kennaway wrote:
> On Wed, Oct 09, 2002 at 04:36:39PM -0400, John Baldwin wrote:
>> > make
>> cc -c -O -pipe -march=pentium3 -Wall -Wredundant-decls -Wnested-externs 
>-Wstrict-prototypes 
>> -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions 
>-ansi -g
>> -nostdinc
>> -I-  -I. -I../../.. -I../../../dev -I../../../contrib/dev/acpica 
>-I../../../contrib/ipfilter
>> -D_KERNEL -include opt_global.h -fno-common  -mno-align-long-strings
>> -mpreferred-stack-boundary=2
>> -ffreestanding -Werror  ../../../netinet6/raw_ip6.c
>> cc: Internal error: Illegal instruction (program cc1)
>> Please submit a full bug report.
>> See http://www.gnu.org/software/gcc/bugs.html> for instructions.
>> *** Error code 1
>> 
>> > ll raw_ip6.o
>> -rw-rw-r--  1 john  src  441 Oct  9 16:34 raw_ip6.o
>> 
>> Even leaves a truncated .o file around.
> 
> kan posted a patch the other day.

I know, I'm begging for that patch to be committed so that people
can use -current.

> Kris

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: src/games bikeshed time.

2002-10-10 Thread James Howard


On Thu, 10 Oct 2002, Mark Murray wrote:

> > So if someone were willing to take over the lot and manage them as Ports,
> > how would anyone feel about this?
> >
> > FreeGrep uses the FreeBSD build style and is easily a Port.  I could
> > Port-ify the entire directory in, say, two days.  Anyone interested?
>
> I've got the port-ifying job 90% done, in the style of ports/net/freebsd-uucp.
>
> If you want to maintain it, I'd be delighted! Are you a committer?

I could use a new hobby, but I am not a committer.

Jamie


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: KDE 3.0 broken in current??

2002-10-10 Thread The Gupta Age


Thanks a bunch for the replies
Terry's workaround works fine.
I am not sure what the real culprit is?
If the two of you guys could elaborate a little bit
may be i will learn a thing or two.
Anyways Mike if you need a amateur helping hand, I
will be glad to help!

best regards,
On Wed, 9 Oct 2002, Mike Barcroft wrote:

|Terry Lambert <[EMAIL PROTECTED]> writes:
|> KDE is broken; it's assuming promisucous headers.
|
|This could be our fault.  We advertise ourselves as POSIX.1-2001
|conformant, but only about 2/3 of our standard headers are.  I'm
|systematically working my through them, but some issues take longer to
|solve than others.
|
|> Workaround:
|>
|>  mv netdev.c netdev.c.broken
|>  echo "#include " > netdev.c
|>  cat netdev.c.broken >> netdev.c
|>
|> Probably, this should be handled by sending a patch back to the KDE
|> folks, whose servers were dead and being repaired yesterday.  You
|> could also make a port path that patched netdev.c, as an interim
|> fix (include the header before including the  header).
|>
|> Unfortunately, It still has not been 72 hours for the download, so
|> I still do not have the KDE sources available locally.
|
|Best regards,
|Mike Barcroft
|



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: KDE 3.0 broken in current??

2002-10-10 Thread Michael Nottebrock

Alex Zepeda wrote:
> On Wed, Oct 09, 2002 at 10:17:01PM -0700, Terry Lambert wrote:
> 
> 
>>FWIW: Thanks.  It sometimes feels like people intentionally go
>>out of their way to put Linux-isms (or whatever-isms) into code
>>to make it not run on BSD platforms.
> 
> 
> I'm quite suprised how this managed to avoid detection for so long
> (webcvs.kde.org indicated that the last commit to this branch was > 12
> months ago).

Becaused it all used to compile just fine until a very short time ago.


Regards,
-- 
Michael Nottebrock
"And the reasons? There are no reasons."



msg44478/pgp0.pgp
Description: PGP signature


Re: KDE 3.0 broken in current??

2002-10-10 Thread Wesley Morgan

On Wed, 9 Oct 2002, Alex Zepeda wrote:

> I'm quite suprised how this managed to avoid detection for so long
> (webcvs.kde.org indicated that the last commit to this branch was > 12
> months ago).  It's that whole feeling of fixing the same problems over and
> over again.

Most likely this is a problem that was uncovered by some change in our
headers. I've seen a lot of commits come down the pipes removing
"unneeded" includes from one header or another... Which of course is the
correct thing to do and it encourages better coding practices to make
people put headers in the right order.


> Admittedly I run development versions of both FreeBSD and KDE, and the
> kde-freebsd team uses stable overwhelmingly so the combination doesn't
> receive the testing that others do.

Last I checked, Will was at the very least testing each release on
-current. KDE is such a big package I can't imagine it being very popular
with testers, although with the new GCC snapshot imported I will probably
rebuilt it.

Would it be possible to modify the bento cluster to have another slice
with the minimal -current install, and (using boot0cfg, or modifying a
GRUB boot menu) reboot into -current for an automated package build? Or
maybe this is already done.


-- 
   _ __ ___   ___ ___ ___
  Wesley N Morgan   _ __ ___ | _ ) __|   \
  [EMAIL PROTECTED] _ __ | _ \._ \ |) |
  FreeBSD: The Power To Serve  _ |___/___/___/
Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message




Re: 2 patches for src/share/misc/bsd-family-tree

2002-10-10 Thread Sergey A. Osokin

On Thu, Oct 10, 2002 at 03:57:37PM +0400, Sergey A. Osokin wrote:
> On Thu, Oct 10, 2002 at 03:26:21PM +0400, Sergey A. Osokin wrote:
> > Hello.
> > Please review 2 patches for src/share/misc/bsd-family-tree.
> 
> A little bug: release date of MacOSX 10.2 is 2002-08-23
> http://www.apple.com/pr/library/2002/aug/23jaguar.html

Here is a latest version of patch:
http://ozz.pp.ru/patches/patch-bsd-family-tree

In addition of previous 2 patches is:
1) use tabs vs. spaces near NetBSD 1.5.3
2) fix "Unix history" URL
3) fix Mac OS X 10.1 release date
(from http://www.apple.com/pr/library/2001/sep/25osxserver.html)

Thanks.

-- 

Rgdz,/"\  ASCII RIBBON CAMPAIGN
Sergey Osokin aka oZZ,   \ /AGAINST HTML MAIL
http://ozz.pp.ru/ X  AND NEWS
 / \

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



RE: panic: blockable sleep lock (sleep mutex) sellck @ /usr/src/

2002-10-10 Thread John Baldwin


On 10-Oct-2002 David Wolfskill wrote:
> I'm including [EMAIL PROTECTED] because there may well be some
> interaction with the recently-imported acpica-unix-20021002.  Please
> be judicious with respect to where replies are directed.

This isn't ACPI related I don't think.  You got a stray interrupt and
sched_ithd() tried to call printf().  Unfortunately, cpu_unpend() seems
to be executing while it is still in a critical section, so when printf()
calls into select() it breaks.  Probably printf() needs work to be made
more intelligent so it doesn't get into select() in that case but defers
it.
 
> The panic occurred with -CURRENT CVSupped around 0347 hrs. US/Pacific (7
> hrs. west of GMT, at this time of year).  The machine is my laptop, a
> Dell Inspiron 5000e, after I had logged in to xdm, but switched to vty1,
> then used the keyboard chord (Fn+Esc, in this case) to request a suspend
> (to RAM).  Although I tried to use "panic" (in the debugger) to get a
> crash dump, that effort was unsuccessful.  I do, however, have the
> following (hand-transcribed -- twice!) trace:
> 
> panic: blockable sleep lock (sleep mutex) sellck @ 
>/usr/src/sys/kern/sys_generic.c:1191
> Debugger("panic")
> Stoppd at Debugger+0x54:  xchgl   %ebx, in_Debugger.0
> db> tr
> Debugger(c047a4cd,c0529600,c047d6d9,cdbf57ec,1) at Debugger+0x54
> panic(c047d6d9,c04795bf,c047e00d,c047dfe0,4a7) at panic+0xab
> witness_lock(c04ec5e0,8,c047dfe0,4a7,cdbf5858) at witness_lock+0x97
> _mtx_lock_flags(c04ec5e0,0,c047dfe0,4a7,cdbf5858) at _mtx_lock_flags+0xb1
> Selwakeup(c26cbe04,c26cbe30,73,c26cbe30,cdbf5858) at Selwakeup+0x2f
> ptcwakeup(c26cbe30,1,cdbf58a4,c02e42cb,c26cbe30) at ptcwakeup+0x2e
> ptsstart(c26cbe30,cdbf58bc,c02e5fa4,c26cbe30,c26cbe30) at ptsstart+0x37
> ttstart(c26cbe30,c26cbe307,cdbf59b4,cdbf5858) at ttstart+0x1b
> tputchar(73,c26cbe30,1,c049c473,7d0) at tputchar+0x54
> kvprrintf(c049c472,c02d0310,cdbf59b4,a,cdbf59d4) at kvprrintf+0x8d
> printf(c049c472,b,1,b,296) at printf+0x57
> sched_ithd(b,c02d6631,c052a7c0,0,c047d4f9) at sched_ithd+0x63
> i386_unpend(c052c3f0,c0506d40,15,cdbf5a30,c02ba0a5) at i386_unpend+0xb7
> cpu_unpend(197,cdbf5a3c,c02b9d34,7d0,cdbf5a5c) at cpu_unpend+0x2a
> cpu_critical_exit(7d0,cdbf5a5c,c02aab5d,c0506d40,1) at cpu_critical_exit+0x15
> critical_exit(c0506d40,1,c04795d6,1b2,cdc34000) at critical_exit+0x24
> _mtx_unlock_spin_flags(c0506d40,0,c049b3e,19f,70) at _mtx_unlock_spin_flags+0xbd
> getit(10,c04e7460,c2633090,cdbf5abc,70) at getit+0x62
> DELAY(7d0,c2611500,c2629f00,c2629f00) at DELAY+0x30
> cbb_pcic_power_disable_socket(c262bb00,c2629f00,c25502b0,cdbf5b00) at
> cbb_pcic_power_disable_socket+0x8f
> cbb_power_disable_socket(c262bb00,c2629f00,cdbf5aec,0,0) at 
>cbb_power_disable_socket+0x2f
> cardbus_detach_card(c2629f00,1,cdbf5b38,c02c8076,c2629f00) at 
>cardbus_detach_card+0x9c
> cardbus_suspend(c2629f00,c2623cc0,c2623b00,c2623b00,c2623cc0) at cardbus_suspend+0x19
> bus_generic_suspend(c262bb00,c2623cc0,c2623b00,c2550058,c262bb00) at 
>bus_generic_suspend+0x5b
> cbb_suspend(c262bb00,c2550058,c04a51a8,c2b01c40,0) at cbb_suspend+0x7a
> bus_generic_suspend(c2629500,c2608058,c04a51a8,c2609058,c0f07700) at 
>bus_generic_suspend+0x5b
> bus_generic_suspend(c0f07500,c2607058,c04a51a8,0,0) at bus_generic_suspend+0x5b
> bus_generic_suspend(c2611500,c25e7058,c04a51a8,cdbf5c3a,0) at 
>bus_generic_suspend+0x5b
> bus_generic_suspend(c0f06c80,c25b8058,c04a51a8,cdbf5c10,c2618a40) at 
>bus_generic_suspend+0x5b
> bus_generic_suspend(c0f06f00,c0efa058,c04a51a8,c05293c8,4040) at 
>bus_generic_suspend+0x5b
> acpi_SetSleepState(c2611480,1,cdbf5c78,c0647562,c2611480) at acpi_SetSleepState+0x106
> acpi_system_eventhandler_sleep(c2611480,1,5da,c2611480c2625e20) at
> acpi_system_eventhandler_sleep+0x1d
> 
>acpi_eventhandler_sleep_button_for_sleep(c2611480,c0656514,c27fd400,c27fd400,cdbf5ca4)
> at
> acpi_eventhandler_sleep_button_for_sleep+0x62
> acpi_button_notify_pressed_for_sleep(c2625e20,c27fd400,1,cdbf5cd0,c02d3f2c) at
> acpi_button_notify_pressed_for_sleep+0x9a
> AcpiOsExecuteQueue(c27fd400,1,c047d265,c9,c0f06d1c) at AcpiOsExecuteQueue+0x17
> taskqueue_run(c0f06d00,cdbf5d08,c02a1d92,0,0) at taskqueue_run+0x9c
> taskqueue_acpi_run(0,0,c0477f04,215,c260f370) at taskqueue_acpi_run+0x13
> ithread_loop(c0ef7d00,cdbf5d48,c0477c63,34b,efbfff64) at ithread_loop+0x182
> fork_exit(c02a1c10,c0ef7d00,cdbf5d48) at fork_exit+0xa7
> fork_tramploine() at fork_tramploine+0x1a
> --- trap 0x1, eip = 0, esp = 0xcdbf5d7c, ebp = 0
> db> show locks
> exclusive sx acpi_sleep_event r=0 (0xc0f07c88) locked @ 
>/usr/src/sys/dev/acpica/acpi.c:1498
> exclusive sleep mutex Giant r=0 (0xc04e9100) locked @ 
>/usr/src/sys/kern/kern_intr.c:533
> db>
> 
> 
> And that's all I have.
> 
> I'll "clone" the system from slice 3 to slice 2, in order to be
> able to reproduce the symptom, in case that helps.  (I run recent -STABLE
> on slice 1, recent -CURRENT on slice 3, and whatever has my attention for
> hacking on slice 2.)
> 
> Thanks,
> david
> -- 

RE: 2 patches for src/share/misc/bsd-family-tree

2002-10-10 Thread John Baldwin


On 10-Oct-2002 Sergey A. Osokin wrote:
> Hello.
> Please review 2 patches for src/share/misc/bsd-family-tree.
> 
> The first (original idea from Greg Lehey) sorts references
> in a "Time" section by alphabet and removes U25, because it
> is never referenced.
> 
> The second - adds Mac OS X 10.1 and 10.2, NetBSD 1.6,
> FreeBSD 4.6.2, adds link from FreeBSD 4.4 to Mac OS X 10.2.

Committed with correct date for OS X 10.2.  Thanks!

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: 2 patches for src/share/misc/bsd-family-tree

2002-10-10 Thread John Baldwin


On 10-Oct-2002 Sergey A. Osokin wrote:
> On Thu, Oct 10, 2002 at 03:57:37PM +0400, Sergey A. Osokin wrote:
>> On Thu, Oct 10, 2002 at 03:26:21PM +0400, Sergey A. Osokin wrote:
>> > Hello.
>> > Please review 2 patches for src/share/misc/bsd-family-tree.
>> 
>> A little bug: release date of MacOSX 10.2 is 2002-08-23
>> http://www.apple.com/pr/library/2002/aug/23jaguar.html
> 
> Here is a latest version of patch:
> http://ozz.pp.ru/patches/patch-bsd-family-tree
> 
> In addition of previous 2 patches is:
> 1) use tabs vs. spaces near NetBSD 1.5.3
> 2) fix "Unix history" URL
> 3) fix Mac OS X 10.1 release date
> (from http://www.apple.com/pr/library/2001/sep/25osxserver.html)

Hmm, another PR on the same day says that OS X 10.1 was released on
September 29, but that OS X Server 10.1 was released on September
25.  Also, the UNIX History page uses September 29.  However, it treats
OS X and OS X Server as different operating systems and it also uses
Sept 29 for both OS's.

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: 2 patches for src/share/misc/bsd-family-tree

2002-10-10 Thread Sergey A. Osokin

On Thu, Oct 10, 2002 at 10:49:58AM -0400, John Baldwin wrote:
> On 10-Oct-2002 Sergey A. Osokin wrote:
> > On Thu, Oct 10, 2002 at 03:57:37PM +0400, Sergey A. Osokin wrote:
> >> On Thu, Oct 10, 2002 at 03:26:21PM +0400, Sergey A. Osokin wrote:
> >> 
> >> A little bug: release date of MacOSX 10.2 is 2002-08-23
> >> http://www.apple.com/pr/library/2002/aug/23jaguar.html
> > 
> > Here is a latest version of patch:
> > http://ozz.pp.ru/patches/patch-bsd-family-tree
> > 
> > In addition of previous 2 patches is:
> > 1) use tabs vs. spaces near NetBSD 1.5.3
> > 2) fix "Unix history" URL
> > 3) fix Mac OS X 10.1 release date
> > (from http://www.apple.com/pr/library/2001/sep/25osxserver.html)
> 
> Hmm, another PR on the same day says that OS X 10.1 was released on
> September 29, but that OS X Server 10.1 was released on September
> 25.  Also, the UNIX History page uses September 29.  However, it treats
> OS X and OS X Server as different operating systems and it also uses
> Sept 29 for both OS's.

But I find one more annonce about release date of Mac OS X 10.1:
http://www.apple.com/pr/library/2001/sep/25osx_available.html

Quotation:
"SEYBOLD SF 2001, SAN FRANCISCO, Californiar-September 25, 2001-Apple(c)
 today announced that Mac(c) OS X version 10.1..."

-- 

Rgdz,/"\  ASCII RIBBON CAMPAIGN
Sergey Osokin aka oZZ,   \ /AGAINST HTML MAIL
http://ozz.pp.ru/ X  AND NEWS
 / \

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: I can't compile GENERIC, please let's fix this

2002-10-10 Thread Kris Kennaway

On Thu, Oct 10, 2002 at 09:30:20AM -0400, John Baldwin wrote:

> > kan posted a patch the other day.
> 
> I know, I'm begging for that patch to be committed so that people
> can use -current.

It was committed already last night.

Kris



msg44485/pgp0.pgp
Description: PGP signature


Re: 3+ days: syntax error in makedevs.c (sysinstall)

2002-10-10 Thread Kris Kennaway

On Wed, Oct 09, 2002 at 03:01:49AM +, Daniel Flickinger wrote:
> 
>   ===> sysinstall
> 
>   makedevs.c:60: syntax error before ',' token
>   *** Error code 1
>   `all' not remade because of errors.

Sounds like failure to properly run 'make depend' (makedevs is a
generated file).  sysinstall builds fine here.

Kris



msg44486/pgp0.pgp
Description: PGP signature


Re: 2 patches for src/share/misc/bsd-family-tree

2002-10-10 Thread John Baldwin


On 10-Oct-2002 Sergey A. Osokin wrote:
> On Thu, Oct 10, 2002 at 10:49:58AM -0400, John Baldwin wrote:
>> On 10-Oct-2002 Sergey A. Osokin wrote:
>> > On Thu, Oct 10, 2002 at 03:57:37PM +0400, Sergey A. Osokin wrote:
>> >> On Thu, Oct 10, 2002 at 03:26:21PM +0400, Sergey A. Osokin wrote:
>> >> 
>> >> A little bug: release date of MacOSX 10.2 is 2002-08-23
>> >> http://www.apple.com/pr/library/2002/aug/23jaguar.html
>> > 
>> > Here is a latest version of patch:
>> > http://ozz.pp.ru/patches/patch-bsd-family-tree
>> > 
>> > In addition of previous 2 patches is:
>> > 1) use tabs vs. spaces near NetBSD 1.5.3
>> > 2) fix "Unix history" URL
>> > 3) fix Mac OS X 10.1 release date
>> > (from http://www.apple.com/pr/library/2001/sep/25osxserver.html)
>> 
>> Hmm, another PR on the same day says that OS X 10.1 was released on
>> September 29, but that OS X Server 10.1 was released on September
>> 25.  Also, the UNIX History page uses September 29.  However, it treats
>> OS X and OS X Server as different operating systems and it also uses
>> Sept 29 for both OS's.
> 
> But I find one more annonce about release date of Mac OS X 10.1:
> http://www.apple.com/pr/library/2001/sep/25osx_available.html
> 
> Quotation:
> "SEYBOLD SF 2001, SAN FRANCISCO, Californiar-September 25, 2001-Apple(c)
>  today announced that Mac(c) OS X version 10.1..."

Read the whole thing, it says it will be available in stores that Saturday,
Sept 29. :)

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: KDE 3.0 broken in current??

2002-10-10 Thread Kris Kennaway

On Thu, Oct 10, 2002 at 10:10:50AM -0400, Wesley Morgan wrote:

> Would it be possible to modify the bento cluster to have another slice
> with the minimal -current install, and (using boot0cfg, or modifying a
> GRUB boot menu) reboot into -current for an automated package build? Or
> maybe this is already done.

Er, this is how we build packages for 5.0 ;-) (Well, both 4.x and 5.0
packages are built in a chroot on a 5.0 system)

Kris



msg44488/pgp0.pgp
Description: PGP signature


Re: src/games bikeshed time.

2002-10-10 Thread Sheldon Hearn

On (2002/10/10 06:55), James Howard wrote:

> > If you want to maintain it, I'd be delighted! Are you a committer?
> 
> I could use a new hobby, but I am not a committer.

Have you given up on your grep implementation? :-)

Quite a few folks were really looking forward to it.

Ciao,
Sheldon.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: 2 patches for src/share/misc/bsd-family-tree

2002-10-10 Thread Sergey A. Osokin

On Thu, Oct 10, 2002 at 11:26:36AM -0400, John Baldwin wrote:
> On 10-Oct-2002 Sergey A. Osokin wrote:
> > On Thu, Oct 10, 2002 at 10:49:58AM -0400, John Baldwin wrote:
> >> On 10-Oct-2002 Sergey A. Osokin wrote:
> >> > On Thu, Oct 10, 2002 at 03:57:37PM +0400, Sergey A. Osokin wrote:
> >> >> On Thu, Oct 10, 2002 at 03:26:21PM +0400, Sergey A. Osokin wrote:
> >> >> 
> >> >> A little bug: release date of MacOSX 10.2 is 2002-08-23
> >> >> http://www.apple.com/pr/library/2002/aug/23jaguar.html
> >> > 
> >> > Here is a latest version of patch:
> >> > http://ozz.pp.ru/patches/patch-bsd-family-tree
> >> > 
> >> > In addition of previous 2 patches is:
> >> > 1) use tabs vs. spaces near NetBSD 1.5.3
> >> > 2) fix "Unix history" URL
> >> > 3) fix Mac OS X 10.1 release date
> >> > (from http://www.apple.com/pr/library/2001/sep/25osxserver.html)
> >> 
> >> Hmm, another PR on the same day says that OS X 10.1 was released on
> >> September 29, but that OS X Server 10.1 was released on September
> >> 25.  Also, the UNIX History page uses September 29.  However, it treats
> >> OS X and OS X Server as different operating systems and it also uses
> >> Sept 29 for both OS's.
> > 
> > But I find one more annonce about release date of Mac OS X 10.1:
> > http://www.apple.com/pr/library/2001/sep/25osx_available.html
> > 
> > Quotation:
> > "SEYBOLD SF 2001, SAN FRANCISCO, Californiar-September 25, 2001-Apple(c)
> >  today announced that Mac(c) OS X version 10.1..."
> 
> Read the whole thing, it says it will be available in stores that Saturday,
> Sept 29. :)

:-)
OK, following this way: FreeBSD 4.7 still not avaliable
at stores, but bsd-family-tree say that it already avaliable :-)
Does it correct?

-- 

Rgdz,/"\  ASCII RIBBON CAMPAIGN
Sergey Osokin aka oZZ,   \ /AGAINST HTML MAIL
http://ozz.pp.ru/ X  AND NEWS
 / \

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: src/games bikeshed time.

2002-10-10 Thread James Howard

On Thu, 10 Oct 2002, Sheldon Hearn wrote:

> Have you given up on your grep implementation? :-)
>
> Quite a few folks were really looking forward to it.

The big objection to it was it was not as fast as GNU Grep.  A few times,
I've trimmed a few cycles here and there, but it is still 1/2 the speed or
worse.  :(

Jamie


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



(no subject)

2002-10-10 Thread suken woo

unsubcribe freebsd-current


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: disk running out of space

2002-10-10 Thread Guezou Philippe

[Charset iso-8859-1 unsupported, filtering to ASCII...]
> Thank you for your suggestion I restarted apache on my server my df -h is
> giving
> 
> FilesystemSize   Used  Avail Capacity  Mounted on
> /dev/ad0s2a   9.6G   1.0G   7.8G12%/
> /dev/ad2s1e55G39G11G77%/data
> /dev/ad0s1e   9.6G   2.0K   8.8G 0%/data2
> /dev/ad0s3e26G   1.0G23G 4%/data3
> /dev/ad0s2e   9.6G   1.9G   6.9G22%/usr
> procfs4.0K   4.0K 0B   100%/proc
> 
> What might be the problem??? In future how can I overcome this type of
> problems without restarting the service.

oh well, here, we stop all apache around 23h45, then rotate the logs (moving them into
an other directory log/cold//) before restarting.. It take approximately 3 seconds
to stop, move and restart.. Your users shouldn't notice the stop/start..

hope this helps..
fifi..

> 
> Suresh

-- 
Guezou Philippe [EMAIL PROTECTED]
FreeBSD, The power to serve.

Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: 2 patches for src/share/misc/bsd-family-tree

2002-10-10 Thread John Baldwin


On 10-Oct-2002 Sergey A. Osokin wrote:
> On Thu, Oct 10, 2002 at 11:26:36AM -0400, John Baldwin wrote:
>> On 10-Oct-2002 Sergey A. Osokin wrote:
>> > On Thu, Oct 10, 2002 at 10:49:58AM -0400, John Baldwin wrote:
>> >> On 10-Oct-2002 Sergey A. Osokin wrote:
>> >> > On Thu, Oct 10, 2002 at 03:57:37PM +0400, Sergey A. Osokin wrote:
>> >> >> On Thu, Oct 10, 2002 at 03:26:21PM +0400, Sergey A. Osokin wrote:
>> >> >> 
>> >> >> A little bug: release date of MacOSX 10.2 is 2002-08-23
>> >> >> http://www.apple.com/pr/library/2002/aug/23jaguar.html
>> >> > 
>> >> > Here is a latest version of patch:
>> >> > http://ozz.pp.ru/patches/patch-bsd-family-tree
>> >> > 
>> >> > In addition of previous 2 patches is:
>> >> > 1) use tabs vs. spaces near NetBSD 1.5.3
>> >> > 2) fix "Unix history" URL
>> >> > 3) fix Mac OS X 10.1 release date
>> >> > (from http://www.apple.com/pr/library/2001/sep/25osxserver.html)
>> >> 
>> >> Hmm, another PR on the same day says that OS X 10.1 was released on
>> >> September 29, but that OS X Server 10.1 was released on September
>> >> 25.  Also, the UNIX History page uses September 29.  However, it treats
>> >> OS X and OS X Server as different operating systems and it also uses
>> >> Sept 29 for both OS's.
>> > 
>> > But I find one more annonce about release date of Mac OS X 10.1:
>> > http://www.apple.com/pr/library/2001/sep/25osx_available.html
>> > 
>> > Quotation:
>> > "SEYBOLD SF 2001, SAN FRANCISCO, Californiar-September 25, 2001-Apple(c)
>> >  today announced that Mac(c) OS X version 10.1..."
>> 
>> Read the whole thing, it says it will be available in stores that Saturday,
>> Sept 29. :)
> 
>:-)
> OK, following this way: FreeBSD 4.7 still not avaliable
> at stores, but bsd-family-tree say that it already avaliable :-)
> Does it correct?

The FreeBSD Project releases FreeBSD via FTP.  The official release
date for FreeBSD is thus when the announcement goes out on -announce
and the bits show up on ftp.FreeBSD.org.  Other companies sell FreeBSD
CD's and are not related to the Project.  OS X, on the other hand, is
a commercial product sold by a company.  The official release date for
commercial products is when it is released to customers via stores,
etc.  Even FreeBSD works in that model when you realize that FreeBSD
releases releases to customers when it puts them up on the FTP site.

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: 2 patches for src/share/misc/bsd-family-tree

2002-10-10 Thread Sergey A. Osokin

On Thu, Oct 10, 2002 at 12:16:07PM -0400, John Baldwin wrote:
> 
> On 10-Oct-2002 Sergey A. Osokin wrote:
> > On Thu, Oct 10, 2002 at 11:26:36AM -0400, John Baldwin wrote:
> >> On 10-Oct-2002 Sergey A. Osokin wrote:
> >> > On Thu, Oct 10, 2002 at 10:49:58AM -0400, John Baldwin wrote:
> >> >> On 10-Oct-2002 Sergey A. Osokin wrote:
> >> >> > On Thu, Oct 10, 2002 at 03:57:37PM +0400, Sergey A. Osokin wrote:
> >> >> >> On Thu, Oct 10, 2002 at 03:26:21PM +0400, Sergey A. Osokin wrote:
> >> >> >> 
> >> >> >> A little bug: release date of MacOSX 10.2 is 2002-08-23
> >> >> >> http://www.apple.com/pr/library/2002/aug/23jaguar.html
> >> >> > 
> >> >> > Here is a latest version of patch:
> >> >> > http://ozz.pp.ru/patches/patch-bsd-family-tree
> >> >> > 
> >> >> > In addition of previous 2 patches is:
> >> >> > 1) use tabs vs. spaces near NetBSD 1.5.3
> >> >> > 2) fix "Unix history" URL
> >> >> > 3) fix Mac OS X 10.1 release date
> >> >> > (from http://www.apple.com/pr/library/2001/sep/25osxserver.html)
> >> >> 
> >> >> Hmm, another PR on the same day says that OS X 10.1 was released on
> >> >> September 29, but that OS X Server 10.1 was released on September
> >> >> 25.  Also, the UNIX History page uses September 29.  However, it treats
> >> >> OS X and OS X Server as different operating systems and it also uses
> >> >> Sept 29 for both OS's.
> >> > 
> >> > But I find one more annonce about release date of Mac OS X 10.1:
> >> > http://www.apple.com/pr/library/2001/sep/25osx_available.html
> >> > 
> >> > Quotation:
> >> > "SEYBOLD SF 2001, SAN FRANCISCO, Californiar-September 25, 2001-Apple(c)
> >> >  today announced that Mac(c) OS X version 10.1..."
> >> 
> >> Read the whole thing, it says it will be available in stores that Saturday,
> >> Sept 29. :)
> > 
> >:-)
> > OK, following this way: FreeBSD 4.7 still not avaliable
> > at stores, but bsd-family-tree say that it already avaliable :-)
> > Does it correct?
> 
> The FreeBSD Project releases FreeBSD via FTP.  The official release
> date for FreeBSD is thus when the announcement goes out on -announce
> and the bits show up on ftp.FreeBSD.org.  Other companies sell FreeBSD
> CD's and are not related to the Project.  OS X, on the other hand, is
> a commercial product sold by a company.  The official release date for
> commercial products is when it is released to customers via stores,
> etc.  Even FreeBSD works in that model when you realize that FreeBSD
> releases releases to customers when it puts them up on the FTP site.

OK. I understand your position. What do your think about following
patch?
1) (real) sort "Time" section by alphabet
2) use 's vs. 's near NetBSD 1.5.3
3) change Mac OS X 10.1 release date to 2001-09-2x :-)

Thanks.

-- 

Rgdz,/"\  ASCII RIBBON CAMPAIGN
Sergey Osokin aka oZZ,   \ /AGAINST HTML MAIL
http://ozz.pp.ru/ X  AND NEWS
 / \


Index: src/share/misc/bsd-family-tree
===
RCS file: /home/ncvs/src/share/misc/bsd-family-tree,v
retrieving revision 1.66
diff -u -r1.66 bsd-family-tree
--- src/share/misc/bsd-family-tree  2002/10/10 14:47:03 1.66
+++ src/share/misc/bsd-family-tree  2002/10/10 16:18:59
@@ -179,11 +179,11 @@
 [FBD] FreeBSD Project, The.
 [KB]  Keith Bostic. BSD2.10 available from Usenix. comp.unix.sources,
Volume 11, Info 4, April, 1987.
+[KKK] Mike Karels, Kirk McKusick, and Keith Bostic. tahoe announcement.
+   comp.bugs.4bsd.ucb-fixes, June 15, 1988.
 [KSJ] Michael J. Karels, Carl F. Smith, and William F. Jolitz.
Changes in the Kernel in 2.9BSD. Second Berkeley Software
Distribution UNIX Version 2.9, July, 1983.
-[KKK] Mike Karels, Kirk McKusick, and Keith Bostic. tahoe announcement.
-   comp.bugs.4bsd.ucb-fixes, June 15, 1988.
 [NBD] NetBSD Project, The.
 [OBD] OpenBSD Project, The.
 [QCU] Salus, Peter H. A quarter century of UNIX.
@@ -354,13 +354,13 @@
 NetBSD 1.5.1   2001-07-11 [NBD] (patch release)
 NetBSD 1.5.2   2001-09-13 [NBD] (patch release)
 FreeBSD 4.42001-09-18 [FBD]
-Mac OS X 10.1  2001-09-xx [APL]
+Mac OS X 10.1  2001-09-2x [APL]
 OpenBSD 3.02001-12-01 [OBD]
 FreeBSD 4.52002-01-29 [FBD]
 BSD/OS 4.3 2002-03-14 [WRS]
 OpenBSD 3.12002-05-19 [OBD]
 FreeBSD 4.62002-06-15 [FBD]
-NetBSD 1.5.32002-07-22 [NBD] (patch release)
+NetBSD 1.5.3   2002-07-22 [NBD] (patch release)
 FreeBSD 4.6.2  2002-08-15 [FBD] (patch release)
 Mac OS X 10.2  2002-08-23 [APL]
 NetBSD 1.6 2002-09-14 [NBD]



Re: 2 patches for src/share/misc/bsd-family-tree

2002-10-10 Thread John Baldwin


On 10-Oct-2002 Sergey A. Osokin wrote:
> On Thu, Oct 10, 2002 at 12:16:07PM -0400, John Baldwin wrote:
>> 
>> On 10-Oct-2002 Sergey A. Osokin wrote:
>> > On Thu, Oct 10, 2002 at 11:26:36AM -0400, John Baldwin wrote:
>> >> On 10-Oct-2002 Sergey A. Osokin wrote:
>> >> > On Thu, Oct 10, 2002 at 10:49:58AM -0400, John Baldwin wrote:
>> >> >> On 10-Oct-2002 Sergey A. Osokin wrote:
>> >> >> > On Thu, Oct 10, 2002 at 03:57:37PM +0400, Sergey A. Osokin wrote:
>> >> >> >> On Thu, Oct 10, 2002 at 03:26:21PM +0400, Sergey A. Osokin wrote:
>> >> >> >> 
>> >> >> >> A little bug: release date of MacOSX 10.2 is 2002-08-23
>> >> >> >> http://www.apple.com/pr/library/2002/aug/23jaguar.html
>> >> >> > 
>> >> >> > Here is a latest version of patch:
>> >> >> > http://ozz.pp.ru/patches/patch-bsd-family-tree
>> >> >> > 
>> >> >> > In addition of previous 2 patches is:
>> >> >> > 1) use tabs vs. spaces near NetBSD 1.5.3
>> >> >> > 2) fix "Unix history" URL
>> >> >> > 3) fix Mac OS X 10.1 release date
>> >> >> > (from http://www.apple.com/pr/library/2001/sep/25osxserver.html)
>> >> >> 
>> >> >> Hmm, another PR on the same day says that OS X 10.1 was released on
>> >> >> September 29, but that OS X Server 10.1 was released on September
>> >> >> 25.  Also, the UNIX History page uses September 29.  However, it treats
>> >> >> OS X and OS X Server as different operating systems and it also uses
>> >> >> Sept 29 for both OS's.
>> >> > 
>> >> > But I find one more annonce about release date of Mac OS X 10.1:
>> >> > http://www.apple.com/pr/library/2001/sep/25osx_available.html
>> >> > 
>> >> > Quotation:
>> >> > "SEYBOLD SF 2001, SAN FRANCISCO, Californiar-September 25, 2001-Apple(c)
>> >> >  today announced that Mac(c) OS X version 10.1..."
>> >> 
>> >> Read the whole thing, it says it will be available in stores that Saturday,
>> >> Sept 29. :)
>> > 
>> >:-)
>> > OK, following this way: FreeBSD 4.7 still not avaliable
>> > at stores, but bsd-family-tree say that it already avaliable :-)
>> > Does it correct?
>> 
>> The FreeBSD Project releases FreeBSD via FTP.  The official release
>> date for FreeBSD is thus when the announcement goes out on -announce
>> and the bits show up on ftp.FreeBSD.org.  Other companies sell FreeBSD
>> CD's and are not related to the Project.  OS X, on the other hand, is
>> a commercial product sold by a company.  The official release date for
>> commercial products is when it is released to customers via stores,
>> etc.  Even FreeBSD works in that model when you realize that FreeBSD
>> releases releases to customers when it puts them up on the FTP site.
> 
> OK. I understand your position. What do your think about following
> patch?
> 1) (real) sort "Time" section by alphabet
> 2) use 's vs. 's near NetBSD 1.5.3
> 3) change Mac OS X 10.1 release date to 2001-09-2x :-)
> 
> Thanks.

Well, I actually went with the 29th for 10.1. (i.e., go with
OS X, not OS X Server dates).

-- 

John Baldwin <[EMAIL PROTECTED]>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



KSE talk

2002-10-10 Thread Julian Elischer


Anyone in the SF Bay area who isn't on the Bafug lists..
I'll be giving a pretty detailed talk on KSE and how
it works tonight at the bafug meeting.. I'll try put up handouts on the
web for others.


Julian



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



XL0 Driver Errors in FreeBSD 5

2002-10-10 Thread G D McKee

Hi

Been running 5 fine since DP1 and have done a cvsup and a buildworld every
week or so since.  Last week the kernel kept panicing so I cvsup and
makeworld yesterday just to see if the problems have been fixed and I still
get the following error when I boot up.  If someone tells me what to do I
will get as much info is as needed out of the box, kernel debug info etc.

Uname -a output:
FreeBSD speedy.gdmckee.local 5.0-CURRENT FreeBSD 5.0-CURRENT #5: Wed Oct  9
20:55:47 BST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SPEEDY
i386
speedy#


Errors in /var/log/messages

Oct  9 21:18:36 speedy kernel: Copyright (c) 1992-2002 The FreeBSD Project.
Oct  9 21:18:36 speedy kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988,
1989, 1991, 1992, 1993, 1994
Oct  9 21:18:36 speedy kernel: The Regents of the University of California.
All rights reserved.
Oct  9 21:18:36 speedy kernel: FreeBSD 5.0-CURRENT #5: Wed Oct  9 20:55:47
BST 2002
Oct  9 21:18:36 speedy kernel:
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SPEEDY
Oct  9 21:18:36 speedy kernel: Preloaded elf kernel "/boot/kernel/kernel" at
0xc04a2000.
Oct  9 21:18:36 speedy kernel: Preloaded elf module "/boot/kernel/acpi.ko"
at 0xc04a20a8.
Oct  9 21:18:36 speedy kernel: Timecounter "i8254"  frequency 1193182 Hz
Oct  9 21:18:36 speedy kernel: Timecounter "TSC"  frequency 595997032 Hz
Oct  9 21:18:36 speedy kernel: CPU: Pentium III/Pentium III Xeon/Celeron
(596.00-MHz 686-class CPU)
Oct  9 21:18:36 speedy kernel: Origin = "GenuineIntel"  Id = 0x683  Stepping
= 3
Oct  9 21:18:36 speedy kernel:
Features=0x387fbff
Oct  9 21:18:36 speedy kernel: real memory  = 133816320 (130680K bytes)
Oct  9 21:18:36 speedy kernel: avail memory = 124862464 (121936K bytes)
Oct  9 21:18:36 speedy kernel: Pentium Pro MTRR support enabled
Oct  9 21:18:36 speedy kernel: npx0:  on motherboard
Oct  9 21:18:36 speedy kernel: npx0: INT 16 interface
Oct  9 21:18:36 speedy kernel: acpi0:  on motherboard
Oct  9 21:18:36 speedy kernel: Using $PIR table, 9 entries at 0xc00fbbc0
Oct  9 21:18:36 speedy kernel: acpi0: power button is handled as a fixed
feature programming model.
Oct  9 21:18:36 speedy kernel: Timecounter "ACPI-fast"  frequency 3579545 Hz
Oct  9 21:18:36 speedy kernel: acpi_timer0: <24-bit timer at 3.579545MHz>
port 0x808-0x80b on acpi0
Oct  9 21:18:36 speedy kernel: acpi_cpu0:  on acpi0
Oct  9 21:18:36 speedy kernel: acpi_cpu1:  on acpi0
Oct  9 21:18:36 speedy kernel: pcib0:  port
0xcf8-0xcff on acpi0
Oct  9 21:18:36 speedy kernel:  initial
configuration 
Oct  9 21:18:36 speedy kernel:  before setting priority for
links 
Oct  9 21:18:36 speedy kernel:  before fixup boot-disabled
links -
Oct  9 21:18:36 speedy kernel:  after fixup boot-disabled
links --
Oct  9 21:18:36 speedy kernel:  arbitrated
configuration -
Oct  9 21:18:36 speedy kernel: pci0:  on pcib0
Oct  9 21:18:36 speedy kernel: agp0:  mem
0xec00-0xefff at device 0.0 on pci0
Oct  9 21:18:36 speedy kernel: pcib1:  at device 1.0
on pci0
Oct  9 21:18:36 speedy kernel: pci1:  on pcib1
Oct  9 21:18:36 speedy kernel: pci1:  at device 0.0 (no driver
attached)
Oct  9 21:18:36 speedy kernel: pcib2:  at device 30.0
on pci0
Oct  9 21:18:36 speedy kernel:  initial
configuration 
Oct  9 21:18:36 speedy kernel:  before setting priority for
links 
Oct  9 21:18:36 speedy kernel:  before fixup boot-disabled
links -
Oct  9 21:18:36 speedy kernel:  after fixup boot-disabled
links --
Oct  9 21:18:36 speedy kernel:  arbitrated
configuration -
Oct  9 21:18:36 speedy kernel: pci2:  on pcib2
Oct  9 21:18:36 speedy kernel: xl0: <3Com 3c905C-TX Fast Etherlink XL> port
0xec80-0xecff mem 0xfafffc00-0xfafffc7f irq 5 at device
12.0 on pci2
Oct  9 21:18:36 speedy kernel: /usr/src/sys/vm/uma_core.c:1307: could sleep
with "xl0" locked from /usr/src/sys/pci/if_xl.c:1264
Oct  9 21:18:36 speedy kernel: /usr/src/sys/vm/uma_core.c:1307: could sleep
with "xl0" locked from /usr/src/sys/pci/if_xl.c:1264
Oct  9 21:18:36 speedy kernel: lock order reversal
Oct  9 21:18:36 speedy kernel: 1st 0xc1876bd4 xl0 (network driver) @
/usr/src/sys/pci/if_xl.c:1264
Oct  9 21:18:36 speedy kernel: 2nd 0xc0364360 allproc (allproc) @
/usr/src/sys/kern/kern_fork.c:318
Oct  9 21:18:36 speedy kernel: /usr/src/sys/vm/uma_core.c:1307: could sleep
with "xl0" locked from /usr/src/sys/pci/if_xl.c:1264
Oct  9 21:18:36 speedy last message repeated 2 times
Oct  9 21:18:36 speedy kernel: xl0: Ethernet address: 00:b0:d0:23:4f:e8
Oct  9 21:18:36 speedy kernel: miibus0:  on xl0
Oct  9 21:18:36 speedy kernel: xlphy0: <3c905C 10/100 internal PHY> on
miibus0
Oct  9 21:18:36 speedy kernel: xlphy0:  10baseT, 10baseT-FDX, 100baseTX,
100baseTX-FDX, auto
Oct  9 21:18:36 speedy kernel: /usr/src/sys/vm/uma_core.c:1307: could sleep
with "xl0" locked from /usr/src/sys/pci/if_xl.c:647
Oct  9 21:18:36 speedy kernel:

RE: panic: blockable sleep lock (sleep mutex) sellck @ /usr/src/

2002-10-10 Thread Bruce Evans

On Thu, 10 Oct 2002, John Baldwin wrote:

> On 10-Oct-2002 David Wolfskill wrote:
> > I'm including [EMAIL PROTECTED] because there may well be some
> > interaction with the recently-imported acpica-unix-20021002.  Please
> > be judicious with respect to where replies are directed.
>
> This isn't ACPI related I don't think.  You got a stray interrupt and
> sched_ithd() tried to call printf().  Unfortunately, cpu_unpend() seems
> to be executing while it is still in a critical section, so when printf()
> calls into select() it breaks.  Probably printf() needs work to be made
> more intelligent so it doesn't get into select() in that case but defers
> it.

The printf part of the bug is just the old one that TIOCCONS never
actually worked and cannot be made to work.  Calling the pty driver
from arbitrary interrupt handlers is invalid.  Even if it were, the
application that reads the pty would not be able to run and print what
it read before printf(9) returns, as is required for printfs in some
contexts.

cpu_unpend() (actually its callee i386_unpend()) enters the critical
section itself (and KASSERT()s that it is not already in a critical
section).  I think this is just to prevent ithread_schedule() switching
away from us when we call it (indirectly via sched_ithd()).  This lets
a single thread clear all the pending interrupts as soon as possible,
which is good for various reasons (especially for fast interrupts).
Entering the critical region is not necessary from preventing preemption,
since we run with interrupts disabled (provided we don't let
ithread_schedule() enable them when it switches away from us).

Bruce


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: ATTN: people who were getting CVSup crashes under -current

2002-10-10 Thread Archie Cobbs

John Polstra writes:
> I am trying to understand the CVSup crashes that were reported by some
> -current users during the past week or two.  I realize the crashes
> had to do with changes in the ucontext structure, but I am trying to
> understand why those changes mattered.  My theory is that the changes
> would matter to the old pm3 port, but not to the newer ezm3 port.  If
> you experienced the crashes, please check which Modula-3 version you
> have using pkg_info and let me know.

I didn't get a signal-type crash, but instead just got this:

>  Edit src/release/doc/en_US.ISO_8859-1/installation/Makefile,v -> Attic
>  Edit src/release/doc/en_US.ISO_8859-1/installation/alpha/Makefile,v -> Attic
>  Edit src/release/doc/en_US.ISO_8859-1/installation/alpha/article.sgml,v -> Attic
>  Edit src/release/doc/en_US.ISO_8859-1/installation/common/artheader.sgml,v -> Attic
>  Edit src/release/doc/en_US.ISO_8859-1/installation/common/floppies.sgml,v -> Attic
>  Edit src/release/doc/en_US.ISO_8859-1/installation/common/install.ent,v -> Attic
> 
> 
> ***
> *** runtime error:
> ***Value out of range
> ***file 
>"/tmp/a/ports/lang/ezm3/work/ezm3-1.0/libs/libm3/src/uid/Common/TimeStamp.m3", line 70
> ***
> 
>   use option @M3stackdump to get a stack trace
> Abort (core dumped)

This is a -current machine with cvsup-without-gui-16.1f installed
(and no separate modula3 stuff).

-Archie

__
Archie Cobbs * Packet Design * http://www.packetdesign.com

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



imake-4 build broken

2002-10-10 Thread Vallo Kallaste

Hi

imake-4 port building is broken. I guess that's because
xc/config/makedepend/main.c defines _POSIX_SOURCE before including
. Signal.h includes  which has conditional
#if !defined(_POSIX_SOURCE) and NSIG will be left undefined. Don't
know who is in fault here, imake sources or our headers, my
knowledge happens to end there.


rm -f main.o
LD_LIBRARY_PATH=../../exports/lib cc -c -O -pipe -march=pentiumpro -march=pentiumpro  
-ansi -pedantic -Dasm=__asm -Wall -Wpointer-arith   -I../../config/imake 
-I../../include -I../../exports/include/X11  -I../.. -I../../exports/include   
-DCSRG_BASED  -DFUNCPROTO=15 -DNARROWPROTO -DPREINCDIR=\"/usr/include\" 
-DINCLUDEDIR=\"/usr/include\" -DOBJSUFFIX=\".o\" main.c
In file included from ../../include/Xos.h:229,
 from def.h:29,
 from main.c:29:
/usr/include/sys/time.h: In function `timespec2bintime':
/usr/include/sys/time.h:133: warning: ISO C89 forbids long long integer constants
/usr/include/sys/time.h: In function `timeval2bintime':
/usr/include/sys/time.h:150: warning: ISO C89 forbids long long integer constants
In file included from main.c:43:
/usr/include/signal.h: At top level:
/usr/include/signal.h:46: `NSIG' undeclared here (not in a function)
/usr/include/signal.h:46: confused by earlier errors, bailing out
*** Error code 1

Stop in /usr/local/src/portbuild/usr/ports/devel/imake-4/work/xc/config/makedepend.
*** Error code 1

Stop in /usr/local/src/portbuild/usr/ports/devel/imake-4/work/xc/config.
*** Error code 1

Stop in /usr/ports/devel/imake-4.
*** Error code 1

Stop in /usr/ports/x11/XFree86-4-libraries.
*** Error code 1

Stop in /usr/ports/x11/XFree86-4.
-- 

Vallo Kallaste
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Again: panic kmem_malloc()

2002-10-10 Thread Ben Stuyts

Hi,

A couple of days ago I reported a panic, which I just got again:

panic: kmem_malloc(4096): kmem_map too small: 28246016 total allocated.

I don't know where to start looking for this, so I'd appreciate some help. 
This is on a lightly loaded server. I've pasted the dmesg below. Latest 
cvsup is oct 5.

Thanks,
Ben

Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
 The Regents of the University of California. All rights reserved.
FreeBSD 5.0-CURRENT #5: Sun Oct  6 01:50:54 CEST 2002
 [EMAIL PROTECTED]:/var/obj/usr/src/sys/TERMINUS
Preloaded elf kernel "/boot/kernel/kernel" at 0xc04dc000.
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 233864867 Hz
CPU: Pentium II/Pentium II Xeon/Celeron (233.86-MHz 686-class CPU)
   Origin = "GenuineIntel"  Id = 0x634  Stepping = 4
   Features=0x80f9ff
real memory  = 67108864 (65536K bytes)
avail memory = 59920384 (58516K bytes)
Pentium Pro MTRR support enabled
npx0:  on motherboard
npx0: INT 16 interface
Using $PIR table, 6 entries at 0xc00fdc00
pcib0:  at pcibus 0 on motherboard
pci0:  on pcib0
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
isab0:  at device 7.0 on pci0
isa0:  on isab0
atapci0:  port 0xf000-0xf00f at device 7.1 on 
pci0
atapci0: Busmastering DMA not supported
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0:  port 0x6400-0x641f irq 11 
at device 7.2 on pci0
usb0:  on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
pci0:  at device 7.3 (no driver attached)
sym0: <875> port 0x6800-0x68ff mem 
0xe800-0xe8000fff,0xe8001000-0xe80010ff irq 12 at device 11.0 on pci0
sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking
sym0: open drain IRQ line driver, using on-chip SRAM
sym0: using LOAD/STORE-based firmware.
xl0: <3Com 3c905-TX Fast Etherlink XL> port 0x6c00-0x6c3f irq 9 at device 
13.0 on pci0
/usr/src/sys/vm/uma_core.c:1307: could sleep with "xl0" locked from 
/usr/src/sys/pci/if_xl.c:1264
/usr/src/sys/vm/uma_core.c:1307: could sleep with "xl0" locked from 
/usr/src/sys/pci/if_xl.c:1264
lock order reversal
  1st 0xc0ba1bd4 xl0 (network driver) @ /usr/src/sys/pci/if_xl.c:1264
  2nd 0xc03d2b00 allproc (allproc) @ /usr/src/sys/kern/kern_fork.c:318
/usr/src/sys/vm/uma_core.c:1307: could sleep with "xl0" locked from 
/usr/src/sys/pci/if_xl.c:1264
/usr/src/sys/vm/uma_core.c:1307: could sleep with "xl0" locked from 
/usr/src/sys/pci/if_xl.c:1264
/usr/src/sys/vm/uma_core.c:1307: could sleep with "xl0" locked from 
/usr/src/sys/pci/if_xl.c:1264
xl0: Ethernet address: 00:60:08:a5:d4:ff
miibus0:  on xl0
nsphy0:  on miibus0
nsphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
/usr/src/sys/vm/uma_core.c:1307: could sleep with "xl0" locked from 
/usr/src/sys/pci/if_xl.c:647
pci0:  at device 15.0 (no driver attached)
orm0:  at iomem 0xc8000-0xcbfff,0xc-0xc7fff on isa0
atkbdc0:  at port 0x64,0x60 on isa0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
fdc0:  at port 
0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0:  at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
lpt0:  on ppbus0
lpt0: Interrupt-driven port
sc0:  on isa0
sc0: VGA <16 virtual consoles, flags=0x200>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
unknown:  can't assign resources (port)
unknown:  can't assign resources (port)
unknown:  can't assign resources (port)
unknown:  can't assign resources (port)
unknown:  can't assign resources (port)
Timecounters tick every 10.000 msec
ipfw2 initialized, divert enabled, rule-based forwarding enabled, default 
to deny, logging unlimited
Waiting 5 seconds for SCSI devices to settle
(noperiph:sym0:0:-1:-1): SCSI BUS reset delivered.
Mounting root from ufs:/dev/da0s1a
da2 at sym0 bus 0 target 3 lun 0
da2:  Fixed Direct Access SCSI-2 device
da2: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled
da2: 3067MB (6281856 512 byte sectors: 255H 63S/T 391C)
da1 at sym0 bus 0 target 2 lun 0
da1:  Fixed Direct Access SCSI-2 device
da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled
da1: 3090MB (6328861 512 byte sectors: 255H 63S/T 393C)
da0 at sym0 bus 0 target 1 lun 0
da0:  Fixed Direct Access SCSI-2 device
da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit)
da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C)
WARNING: / was not properly dismounted
cd0 at sym0 bus 0 target 4 lun 0
cd0:  Removable CD-ROM SCSI-2 device
cd0: 20.000MB/s transfers (20.000MHz, offset 15)
cd0: Attempt to query device size failed: NOT READY, Medium not present
WARNING: /usr was not properly dismounted
WARNING: /var was not properly dismounted
/var: mount pending error: blocks 2 files 1

Re: KDE 3.0 broken in current??

2002-10-10 Thread Terry Lambert

The Gupta Age wrote:
> Thanks a bunch for the replies
> Terry's workaround works fine.
> I am not sure what the real culprit is?
> If the two of you guys could elaborate a little bit
> may be i will learn a thing or two.
> Anyways Mike if you need a amateur helping hand, I
> will be glad to help!
[ ... ]
> |This could be our fault.  We advertise ourselves as POSIX.1-2001
> |conformant, but only about 2/3 of our standard headers are.  I'm
> |systematically working my through them, but some issues take longer to
> |solve than others.


There are conflicting standards.

The argument about POSIX.1-2001 conformance is actually specious,
in this case, because the code in question does not use a feature
test for it in order to make its "#include" decisions.

Basically, my workaround is facetious; it causes the header file
that defines the types used in sys/socket.h to be included before
sys/socket.h is included.  I could have just as easily said "edit
the file and add ``#include '' before the include that
was failing".

This fix was in the KDE 3.1 tree, and has been put in the KDE 3.0
tree as a result of this discussion.

If you have older ports code, continue using the workaround, it's
harmless.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: KDE 3.0 broken in current??

2002-10-10 Thread Terry Lambert

Wesley Morgan wrote:
> On Wed, 9 Oct 2002, Alex Zepeda wrote:
> > I'm quite suprised how this managed to avoid detection for so long
> > (webcvs.kde.org indicated that the last commit to this branch was > 12
> > months ago).  It's that whole feeling of fixing the same problems over and
> > over again.
> 
> Most likely this is a problem that was uncovered by some change in our
> headers. I've seen a lot of commits come down the pipes removing
> "unneeded" includes from one header or another... Which of course is the
> correct thing to do and it encourages better coding practices to make
> people put headers in the right order.

There are two issues.  The first is that in order to be POSIX
1003.1-2001 compliant, we have to get rid of some promiscuous
includes that are remaining.  The second is that in order to be
POSIX 1003.1-2001 compliant, some headers are required to define
their own types for use in structure declarations.

This is like the move from Draft 4 pthreads conformance to standard
pthreads conformance, which defined PTHREAD_MTEX_INITIALIZER, but
didn't make the rest of the required conformance changes at the
same time: many programs (e.g. OpenLDAP) used PTHREAD_MUTEX_INITIALIZER
as one of the few manifest constants that was available to distinguish
between these two implementations (other code included the Moscow
center for supercomputing activities Standard Template Library, and
by extension, the ACAP reference implementation).


The bottom line is that it is better to be fully conformant with
an old standard, than partially conformant with a new standard.


It's unfortunate that these type of changes that move FreeBSD away
from that maxim are going in this close to the 5.0 release date;
they are likely to break a *lot* of code (IMO).

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Do we still need portmap(8)?

2002-10-10 Thread Terry Lambert

"Danny J. Zerkel" wrote:
> Sigh...  there should be a file listing incompatible files that is part of
> the source tree.  Every file in this list would be deleted as a pre-install
> step.  Perl would not have been in this list because it was not
> incompatible.  But the old C++ headers clearly were.  There have
> no doubt been other instances of incompatible files in the installation
> or examples of files moving.  It will happen to any software system
> and should be accounted for in the installation mechanism.


1)  It has to be a post-install, in case the install fails,
part way through.

2)  It has to be optional: the user has to specifically ask
for the deletion; that way, most of us can ignore it.

3)  Feel free to get together with Warner Losh on this, and
submit the code.

> > Personally, I suggest a file "/etc/BUILD" be created to contain
> > the CVS tag and a timestamp indicating the checkout time, created
> > as part of the build process (maybe the tag from the output of a
> > "CVS stat" on the Makefile in /usr/src, processed to deal with
> > sticky tags, and the date stamp on the file itself, otherwise).
> 
> Yuck.  Let's NOT not use CVS (Cantakerous Version Scrambler) tags.

Feel free to use whatever you want, so long as the value can be
used as an input to a process which will result in the binaries
for the system being recreated identically, except for date stamps.
8-).

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: [PATCH] Re: Junior Kernel Hacker page updated...

2002-10-10 Thread Stefan Farfeleder

On Wed, Oct 09, 2002 at 04:07:45PM -0700, Terry Lambert wrote:
> Stefan Farfeleder wrote:
> > Is it just a warning or does it pose a real problem?
> > 
> > I think the problem with the current code is that knote_{en,de}queue can
> > be executed in parallel (on another CPU, spl*() can't prevent that, can
> > it?) with kqueue_scan and that kq->kq_head thus can be corrupted.
> > Or am I totally wrong?
> 
> My patch would have worked, in that case, since it would ensure
> one marker entry with a unique stack address per simultaneous
> scanner.
> 
> It has to be that the queue itself is being deleted out from
> under it: the problem is not the scan, nor the insert or the
> delete.
> 
> Most likely, this is for an object whose queue is not tracked
> by process, or for a process queue that's being examined by
> another process (e.g. kevent's on fork/exit/etc.).
> 
> You can verify this for your own satisfaction by looking at the
> pointer manipulation order for the insertion and deletion; the
> insertion sets the next pointer before setting the pointer to
> the inserted object, and the deletion sets the pointer that
> used to point to the deleted object to the delete object's next,
> before deleting the object.  Thus, traversals in progress should
> not result in an error.

Imagine this scenario where CPU 0 inserts a knote kn1 (the marker) in
knote_scan and CPU 1 kn2 in kqueue_enqueue:


CPU 0   |   CPU 1
+---
kn1->kn_tqe.tqe_next = NULL;|
|
+---
kn1->kn_tqe.tqe_prev =  |   kn2->kn_tqe.tqe_next = NULL;
kq_head.tqh_last;   |
+---
*kq_head.tqh_last = kn1;|   kn2->kn_tqe.tqe_prev =
|   kq_head.tqh_last;
+---
kq_head.tqh_last =  |   *kq_head.tqh_last = kn2;
&kn1->kn_tqe.tqe_next;  |
+---
|   kq_head.tqh_last =
|   &kn2->kn_tqe.tqe_next;

The marker would never appear on the queue.

Regards,
Stefan Farfeleder

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: 3+ days: syntax error in makedevs.c (sysinstall)

2002-10-10 Thread Kris Kennaway

On Thu, Oct 10, 2002 at 08:19:20PM +, Daniel Flickinger wrote:

> make $TFLG $TDEF installincludes >${CDATE}.installincludes.${RDATE} 2>&1 &&\
>   make $TFLG $TDEF $TOUT buildworld >${CDATE}.buildworld.${RDATE} 2>&1 &
> 
>   which "should" take care of that ... Note that I also
>   update all includes.

The 'installincludes' thing appears to be unnecessary and can possibly
cause problems.

>   going for it manually:
> 
>   cd usr.sbin/sysinstall
>   make clean
>   make depend
>   make all

This isn't enough..you have to 'make cleandir' (not 'make clean')
twice to remove all cruft from the obj and build dir (the first time
removes the obj dir completely, the second time picks up any remaining
cruft in the build directory itself.  Stale generated files in your
build directory can certainly cause buildworld failures.

Kris



msg44507/pgp0.pgp
Description: PGP signature


Re: [PATCH] Re: Junior Kernel Hacker page updated...

2002-10-10 Thread Terry Lambert

Stefan Farfeleder wrote:
> Imagine this scenario where CPU 0 inserts a knote kn1 (the marker) in
> knote_scan and CPU 1 kn2 in kqueue_enqueue:
> 
> CPU 0   |   CPU 1
> +---
> kn1->kn_tqe.tqe_next = NULL;|
> |
> +---
> kn1->kn_tqe.tqe_prev =  |   kn2->kn_tqe.tqe_next = NULL;
> kq_head.tqh_last;   |
> +---
> *kq_head.tqh_last = kn1;|   kn2->kn_tqe.tqe_prev =
> |   kq_head.tqh_last;
> +---
> kq_head.tqh_last =  |   *kq_head.tqh_last = kn2;
> &kn1->kn_tqe.tqe_next;  |
> +---
> |   kq_head.tqh_last =
> |   &kn2->kn_tqe.tqe_next;
> 
> The marker would never appear on the queue.

The macro is broken.  Here is a fix.

#define TAILQ_INSERT_TAIL(head, elm, field) do {\
void **savepp;  \
(elm)->field.tqe_next = NULL;   \
(elm)->field.tqe_prev = (head)->tqh_last;   \
savepp = (head)->tqh_last;  \
(head)->tqh_last = &(elm)->field.tqe_next;  \
(elm)->field.tqe_prev = savepp; \
*savepp = (elm);\
} while (0)

I'm not sure that it's possible to totally close the race; I think the
way you would have to do it is to traverse the tqh_last pointer until
the tqh_last->file.tqe_next == NULL, before reference it (ugly).  The
failure mode with the race is an inverted insertion order, which I
think, in this case, is not a problem.  The double setting of the prev
guarantees it has a "harmless" value for a traversal during insertion;
it acts as if the insertion had not occurred, if there are two that
occurred simultaneously, until both sets of data are valid.

This is doable in Intel assembly, I think (CMPXCHGL).  Ugh.  On other
architectures, there's no way to avoid a mutex (e.g. MIPS).

I hate tailq's.  8-(.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: mpd: resource deadlock avoided?

2002-10-10 Thread Archie Cobbs

Lars Eggert writes:
> I'm trying to connect to a Cisco VPN server using mpd under -current. 
> While the connection setup seems to work fine (see attached log), when I 
> try to send traffic over the tunnel, I see these messages:
> 
>   PING hbo.isi.edu (128.9.160.75): 56 data bytes
>   ping: sendto: Resource deadlock avoided
>   ping: sendto: No buffer space available
>   ping: sendto: No buffer space available
>   ping: sendto: No buffer space available
>   ^C
>   --- hbo.isi.edu ping statistics ---
>   4 packets transmitted, 0 packets received, 100% packet loss
> 
> For the first packet after the tunnel comes up, I always get "resource 
> deadlock avoided", for all later packets "no buffer space".

This is because the remote external IP address of the VPN tunnel
is equal to the remote internal IP address, and mpd/FreeBSD is
not smart enough to avoid trying to send the encapsulated packet
back through the tunnel.

Try configuring the Cisco box to use separate internal and external
IP addresses, or adding a host route to the remote peer first before
starting mpd.

-Archie

__
Archie Cobbs * Packet Design * http://www.packetdesign.com

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: Again: panic kmem_malloc()

2002-10-10 Thread Robert Watson

I've run into this on a couple of boxes, but those boxes were diskless
root boxes, and used md backed ffs for /tmp and /var.  Apparently if you
do that, you're likely to exceed the kernel's auto-tuned kmem map size.
That said, they didn't do it as frequently, so perhaps there's been a
chance.  A glance at the malloc buckets on the machine suggested that this
wasn't a memory leak (the normal candidate in this sort of scenario).

Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
[EMAIL PROTECTED]  Network Associates Laboratories

On Thu, 10 Oct 2002, Ben Stuyts wrote:

> Hi,
> 
> A couple of days ago I reported a panic, which I just got again:
> 
> panic: kmem_malloc(4096): kmem_map too small: 28246016 total allocated.
> 
> I don't know where to start looking for this, so I'd appreciate some help. 
> This is on a lightly loaded server. I've pasted the dmesg below. Latest 
> cvsup is oct 5.
> 
> Thanks,
> Ben
> 
> Copyright (c) 1992-2002 The FreeBSD Project.
> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
>  The Regents of the University of California. All rights reserved.
> FreeBSD 5.0-CURRENT #5: Sun Oct  6 01:50:54 CEST 2002
>  [EMAIL PROTECTED]:/var/obj/usr/src/sys/TERMINUS
> Preloaded elf kernel "/boot/kernel/kernel" at 0xc04dc000.
> Timecounter "i8254"  frequency 1193182 Hz
> Timecounter "TSC"  frequency 233864867 Hz
> CPU: Pentium II/Pentium II Xeon/Celeron (233.86-MHz 686-class CPU)
>Origin = "GenuineIntel"  Id = 0x634  Stepping = 4
>Features=0x80f9ff
> real memory  = 67108864 (65536K bytes)
> avail memory = 59920384 (58516K bytes)
> Pentium Pro MTRR support enabled
> npx0:  on motherboard
> npx0: INT 16 interface
> Using $PIR table, 6 entries at 0xc00fdc00
> pcib0:  at pcibus 0 on motherboard
> pci0:  on pcib0
> pcib1:  at device 1.0 on pci0
> pci1:  on pcib1
> isab0:  at device 7.0 on pci0
> isa0:  on isab0
> atapci0:  port 0xf000-0xf00f at device 7.1 on 
> pci0
> atapci0: Busmastering DMA not supported
> ata0: at 0x1f0 irq 14 on atapci0
> ata1: at 0x170 irq 15 on atapci0
> uhci0:  port 0x6400-0x641f irq 11 
> at device 7.2 on pci0
> usb0:  on uhci0
> usb0: USB revision 1.0
> uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
> uhub0: 2 ports with 2 removable, self powered
> pci0:  at device 7.3 (no driver attached)
> sym0: <875> port 0x6800-0x68ff mem 
> 0xe800-0xe8000fff,0xe8001000-0xe80010ff irq 12 at device 11.0 on pci0
> sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking
> sym0: open drain IRQ line driver, using on-chip SRAM
> sym0: using LOAD/STORE-based firmware.
> xl0: <3Com 3c905-TX Fast Etherlink XL> port 0x6c00-0x6c3f irq 9 at device 
> 13.0 on pci0
> /usr/src/sys/vm/uma_core.c:1307: could sleep with "xl0" locked from 
> /usr/src/sys/pci/if_xl.c:1264
> /usr/src/sys/vm/uma_core.c:1307: could sleep with "xl0" locked from 
> /usr/src/sys/pci/if_xl.c:1264
> lock order reversal
>   1st 0xc0ba1bd4 xl0 (network driver) @ /usr/src/sys/pci/if_xl.c:1264
>   2nd 0xc03d2b00 allproc (allproc) @ /usr/src/sys/kern/kern_fork.c:318
> /usr/src/sys/vm/uma_core.c:1307: could sleep with "xl0" locked from 
> /usr/src/sys/pci/if_xl.c:1264
> /usr/src/sys/vm/uma_core.c:1307: could sleep with "xl0" locked from 
> /usr/src/sys/pci/if_xl.c:1264
> /usr/src/sys/vm/uma_core.c:1307: could sleep with "xl0" locked from 
> /usr/src/sys/pci/if_xl.c:1264
> xl0: Ethernet address: 00:60:08:a5:d4:ff
> miibus0:  on xl0
> nsphy0:  on miibus0
> nsphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> /usr/src/sys/vm/uma_core.c:1307: could sleep with "xl0" locked from 
> /usr/src/sys/pci/if_xl.c:647
> pci0:  at device 15.0 (no driver attached)
> orm0:  at iomem 0xc8000-0xcbfff,0xc-0xc7fff on isa0
> atkbdc0:  at port 0x64,0x60 on isa0
> atkbd0:  irq 1 on atkbdc0
> kbd0 at atkbd0
> fdc0:  at port 
> 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0
> fdc0: FIFO enabled, 8 bytes threshold
> fd0: <1440-KB 3.5" drive> on fdc0 drive 0
> ppc0:  at port 0x378-0x37f irq 7 on isa0
> ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
> lpt0:  on ppbus0
> lpt0: Interrupt-driven port
> sc0:  on isa0
> sc0: VGA <16 virtual consoles, flags=0x200>
> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
> sio0: type 16550A
> sio1 at port 0x2f8-0x2ff irq 3 on isa0
> sio1: type 16550A
> vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
> unknown:  can't assign resources (port)
> unknown:  can't assign resources (port)
> unknown:  can't assign resources (port)
> unknown:  can't assign resources (port)
> unknown:  can't assign resources (port)
> Timecounters tick every 10.000 msec
> ipfw2 initialized, divert enabled, rule-based forwarding enabled, default 
> to deny, logging unlimited
> Waiting 5 seconds for SCSI devices to settle
> (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered.
> Mounting root from ufs:/dev/da0s1a
> da2 at sym0 bus 0 target 3 lun 0
> da2:  Fixed Direct Access SCSI-2 device
> da2: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queuei

Re: Again: panic kmem_malloc()

2002-10-10 Thread Ben Stuyts

At 23:55 10/10/2002, Robert Watson wrote:
>On Thu, 10 Oct 2002, Ben Stuyts wrote:
>
> > panic: kmem_malloc(4096): kmem_map too small: 28246016 total allocated.

>I've run into this on a couple of boxes, but those boxes were diskless
>root boxes, and used md backed ffs for /tmp and /var.  Apparently if you
>do that, you're likely to exceed the kernel's auto-tuned kmem map size.
>That said, they didn't do it as frequently, so perhaps there's been a
>chance.  A glance at the malloc buckets on the machine suggested that this
>wasn't a memory leak (the normal candidate in this sort of scenario).

There's nothing special going on here. No diskless, no md, not many 
processes. Here's a process list in case this helps:

USERPID %CPU %MEM   VSZ  RSS  TT  STAT STARTED  TIME COMMAND
dnetc   502 98.0  0.8   960  508  ??  RNs   9:27PM 159:14.77 
/usr/local/distributed.net/dnetc -quiet
root 10  0.0  0.0 0   12  ??  DL1Jan70   0:00.00  (ktrace)
root  1  0.0  0.4   700  220  ??  ILs   1Jan70   0:00.32 /sbin/init --
root 11  0.0  0.0 0   12  ??  RL1Jan70   1:19.57  (idle)
root 12  0.0  0.0 0   12  ??  WL1Jan70   0:06.32  (swi1: net)
root 13  0.0  0.0 0   12  ??  WL1Jan70   0:48.51  (swi6: 
tty:sio clock)
root 15  0.0  0.0 0   12  ??  DL1Jan70   0:02.37  (random)
root 18  0.0  0.0 0   12  ??  WL1Jan70   0:05.64  (swi3: cambio)
root 23  0.0  0.0 0   12  ??  DL1Jan70   0:03.42  (usb0)
root 24  0.0  0.0 0   12  ??  DL1Jan70   0:00.00  (usbtask)
root 25  0.0  0.0 0   12  ??  WL1Jan70   0:03.83  (irq12: sym0)
root 26  0.0  0.0 0   12  ??  WL1Jan70   0:02.96  (irq9: xl0)
root 27  0.0  0.0 0   12  ??  WL1Jan70   0:00.00  (irq1: atkbd0)
root 28  0.0  0.0 0   12  ??  WL1Jan70   0:00.00  (irq6: fdc0)
root 30  0.0  0.0 0   12  ??  WL1Jan70   0:00.02  (swi0: tty:sio)
root  2  0.0  0.0 0   12  ??  DL1Jan70   0:01.28  (pagedaemon)
root  3  0.0  0.0 0   12  ??  DL1Jan70   0:00.00  (vmdaemon)
root  4  0.0  0.0 0   12  ??  RL1Jan70   0:00.95  (pagezero)
root  5  0.0  0.0 0   12  ??  DL1Jan70   0:00.32  (bufdaemon)
root  6  0.0  0.0 0   12  ??  DL1Jan70   0:06.65  (syncer)
root  7  0.0  0.0 0   12  ??  DL1Jan70   0:00.00  (vnlru)
root123  0.0  0.1   220   76  ??  Is   11:27PM   0:00.00 adjkerntz -i
root194  0.0  0.3   628  180  ??  Is9:27PM   0:01.16 /sbin/natd 
-dynamic -log -n tun0
root241  0.0  1.1  1180  688  ??  Ss9:27PM   0:01.09 
/usr/sbin/syslogd -s -v
root255  0.0  3.0  2536 1788  ??  Ss9:27PM   0:04.59 
/usr/sbin/named -d 1
root263  0.0  1.3  1332  768  ??  Is9:27PM   0:00.06 /usr/sbin/rpcbind
root340  0.0  1.1  1204  684  ??  Is9:27PM   0:00.03 
/usr/sbin/mountd -r
root342  0.0  1.2  1164  704  ??  Is9:27PM   0:00.30 nfsd: master 
(nfsd)
root343  0.0  1.0  1116  620  ??  I 9:27PM   0:00.00 nfsd: server 
(nfsd)
root344  0.0  1.0  1116  620  ??  I 9:27PM   0:00.00 nfsd: server 
(nfsd)
root345  0.0  1.0  1116  620  ??  I 9:27PM   0:00.00 nfsd: server 
(nfsd)
root346  0.0  1.0  1116  620  ??  I 9:27PM   0:00.00 nfsd: server 
(nfsd)
root376  0.0  1.1  1188  664  ??  Is9:27PM   0:00.05 /usr/sbin/lpd
root395  0.0  1.5  1552  920  ??  Ss9:27PM   0:02.51 /usr/sbin/ntpd 
-p /var/run/ntpd.pid
root401  0.0  1.6  1616  972  ??  I 9:27PM   0:00.17 /usr/sbin/ntpd 
-p /var/run/ntpd.pid
root417  0.0  0.9  1132  552  ??  Is9:27PM   0:00.09 /usr/sbin/usbd
root436  0.0  2.7  3036 1624  ??  Ss9:27PM   0:02.26 sendmail: 
accepting connections (sendmail)
smmsp   439  0.0  2.5  3012 1480  ??  Is9:27PM   0:00.06 sendmail: 
Queue runner@00:30:00 for /var/spool/clientmqueue (sendmail)
root466  0.0  2.7  2332 1652  ??  Ss9:27PM   0:02.34 
/usr/local/sbin/httpd
www 484  0.0  2.8  2356 1676  ??  I 9:27PM   0:00.01 
/usr/local/sbin/httpd
www 485  0.0  2.8  2356 1676  ??  I 9:27PM   0:00.01 
/usr/local/sbin/httpd
www 486  0.0  2.8  2356 1676  ??  I 9:27PM   0:00.01 
/usr/local/sbin/httpd
www 487  0.0  2.8  2356 1676  ??  I 9:27PM   0:00.01 
/usr/local/sbin/httpd
www 488  0.0  2.8  2356 1676  ??  I 9:27PM   0:00.01 
/usr/local/sbin/httpd
root489  0.0  2.0  1960 1228  ??  Is9:27PM   0:00.11 
/usr/local/sbin/dhcpd
news494  0.0  1.1  1372  688 con- I 9:27PM   0:00.03 nntpd: 
accepting connections: loadav -1 (nntpd)
root500  0.0  1.9  2672 1168  ??  Is9:27PM   0:00.01 
/usr/local/sbin/smbd -D
root503  0.0  2.0  2232 1224  ??  Ss9:27PM   0:01.70 
/usr/local/sbin/nmbd -D
root507  0.0  2.0  2248 1196  ??  I 9:27PM   0:00.02 
/usr/local/sbin/nmbd -D
root509  0.0  1.3  2452  804  ??  Is9:27PM   0:00.02 /usr/X11R6/bin/xdm
root522  0.0  1.3  1324  768  ??  Is9:27PM   0:00.18 
/usr/sbin/inetd -wW
root533  0

mkmagic

2002-10-10 Thread Colin Harford

Alright, I'm new to FreeBSD-current (been using freebsd stable for 4 
years now) and trying to buildworld (installed Snaphost 
20020917-JPSNAP) and used cvsup to update.

Things are fine until it tries to build /usr/src/usr.bin/file and that 
is where she chokes...


Any ideas?  Is this just a newbie error or something more.  I have gone
into the archives on MARC and have not found anything about it


Thanks,

CH



cat /usr/src/usr.bin/file/../../contrib/file/Header
/usr/src/usr.bin/file/../../contrib/file/Localstuff
/usr/src/usr.bin/file/../../contrib/file/Magdir/uuencode,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/sysex
/usr/src/usr.bin/file/../../contrib/file/Magdir/sccs
/usr/src/usr.bin/file/../../contrib/file/Magdir/allegro
/usr/src/usr.bin/file/../../contrib/file/Magdir/xdelta
/usr/src/usr.bin/file/../../contrib/file/Magdir/zyxel
/usr/src/usr.bin/file/../../contrib/file/Magdir/netbsd,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/vicar
/usr/src/usr.bin/file/../../contrib/file/Magdir/riff,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/fsav
/usr/src/usr.bin/file/../../contrib/file/Magdir/citrus
/usr/src/usr.bin/file/../../contrib/file/Magdir/archive
/usr/src/usr.bin/file/../../contrib/file/Magdir/mlssa
/usr/src/usr.bin/file/../../contrib/file/Magdir/grace,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/images,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/tuxedo,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/timezone,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/wordperfect
/usr/src/usr.bin/file/../../contrib/file/Magdir/cisco,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/mach,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/mkid,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/mathematica
/usr/src/usr.bin/file/../../contrib/file/Magdir/macintosh
/usr/src/usr.bin/file/../../contrib/file/Magdir/fonts
/usr/src/usr.bin/file/../../contrib/file/Magdir/claris
/usr/src/usr.bin/file/../../contrib/file/Magdir/animation
/usr/src/usr.bin/file/../../contrib/file/Magdir/interleaf,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/pbm,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/teapot
/usr/src/usr.bin/file/../../contrib/file/Magdir/gimp
/usr/src/usr.bin/file/../../contrib/file/Magdir/diff
/usr/src/usr.bin/file/../../contrib/file/Magdir/amigaos,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/database,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/gringotts,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/pdp,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/ctags,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/pulsar,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/freebsd
/usr/src/usr.bin/file/../../contrib/file/Magdir/hp
/usr/src/usr.bin/file/../../contrib/file/Magdir/encore
/usr/src/usr.bin/file/../../contrib/file/Magdir/commands
/usr/src/usr.bin/file/../../contrib/file/Magdir/blender,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/sendmail,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/netscape
/usr/src/usr.bin/file/../../contrib/file/Magdir/lif
/usr/src/usr.bin/file/../../contrib/file/Magdir/acorn
/usr/src/usr.bin/file/../../contrib/file/Magdir/alliant,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/epoc,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/zyxel,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/xdelta,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/sysex,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/sccs,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/unknown
/usr/src/usr.bin/file/../../contrib/file/Magdir/allegro,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/vicar,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/sun
/usr/src/usr.bin/file/../../contrib/file/Magdir/hitachi-sh
/usr/src/usr.bin/file/../../contrib/file/Magdir/archive,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/citrus,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/fsav,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/mlssa,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/wordperfect,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/clipper
/usr/src/usr.bin/file/../../contrib/file/Magdir/os2
/usr/src/usr.bin/file/../../contrib/file/Magdir/animation,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/claris,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/fonts,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/macintosh,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/mathematica,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/teapot,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/motorola
/usr/src/usr.bin/file/../../contrib/file/Magdir/diff,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/gimp,v
/usr/src/usr.bin/file/../../contrib/file/Magdir/sc
/usr/src/usr.bin/file/../../contrib/file/Magdir/pyramid
/usr/src/usr.bin/file/../../contrib/file/Magdir/parix
/usr/src/usr.bin/file/../../contrib/file/Magdir/adventure
/usr/src/usr.bin/file/../../contrib/file/Magdir/xenix
/usr/src/usr.bin/file/../../contrib/file/Magdir/tgif
/usr/src/usr.bin/file/../../contrib/fi

Re: Again: panic kmem_malloc()

2002-10-10 Thread Terry Lambert

Robert Watson wrote:
> I've run into this on a couple of boxes, but those boxes were diskless
> root boxes, and used md backed ffs for /tmp and /var.  Apparently if you
> do that, you're likely to exceed the kernel's auto-tuned kmem map size.
> That said, they didn't do it as frequently, so perhaps there's been a
> chance.  A glance at the malloc buckets on the machine suggested that this
> wasn't a memory leak (the normal candidate in this sort of scenario).

Use of swapping on additional space not known to the kernel at
boot time, will also cause this; the auto-sizing of the map can
only know about the things it knows about, so adding more later
with consume the available KVA space, without growing it (all
physical memory and all swap is assumed to have mappings allocated
since the mappings need to be filled in at fault time.

It's very tempting to seperate the mapping allocations; this
would be a pretty big chore.  8-(.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



alpha tinderbox failure

2002-10-10 Thread Dag-Erling Smorgrav

--
>>> Rebuilding the temporary build tree
--
>>> stage 1: bootstrap tools
--
>>> stage 2: cleaning up the object tree
--
>>> stage 2: rebuilding the object tree
--
>>> stage 2: build tools
--
>>> stage 3: cross tools
--
>>> stage 4: populating /home/des/tinderbox/alpha/obj/h/des/src/alpha/usr/include
--
>>> stage 4: building libraries
--
>>> stage 4: make dependencies
--
>>> stage 4: building everything..
--
>>> Kernel build for GENERIC started on Thu Oct 10 15:12:56 PDT 2002
--
>>> Kernel build for GENERIC completed on Thu Oct 10 15:44:25 PDT 2002
--
>>> Kernel build for LINT started on Thu Oct 10 15:44:25 PDT 2002
--
===> vinum
"Makefile", line 4198: warning: duplicate script for target "geom_bsd.o" ignored
cc1: warnings being treated as errors
/h/des/src/sys/dev/aic7xxx/ahd_pci.c: In function `ahd_pci_map_registers':
/h/des/src/sys/dev/aic7xxx/ahd_pci.c:171: warning: implicit declaration of function 
`bus_space_subregion'
*** Error code 1

Stop in /h/des/obj/h/des/src/sys/LINT.
*** Error code 1

Stop in /h/des/src.
*** Error code 1

Stop in /h/des/src.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: HEADSUP: GCC 3.2.1 update is coming

2002-10-10 Thread Andrew Gallatin


Martin Blapp writes:
 > 
 > > There might still be a problem with libm and -march=pentium4. I do not
 > > have P4 myself and I cannot reproduce the problem locally.
 > 
 > This problem is also solved. libm compiles again fine with -march=pentium4.
 > OpenOffice and xmms, mpg123 work as they did before.
 > 

Looks like we win some and we loose some.  I just noticed something
weird on my P4 desktop using:

gcc version 3.2.1 [FreeBSD] 20021009 (prerelease)


If I build libm with -march=pentium4, then the mozilla theme "Oribit"
looks corrupt.  If I use -march=pentium3, the problem goes away.  I've
left xwindow dumps on freefall in ~gallatin/mozilla.bad.xwd
~gallatin/mozilla.good.xwd

This is a terrible example in that its impossible to tell what
happened, but it sure shows that something is wrong.

Is there a floating point regression suite that you can point me at?
That would be more useful for debugging.  

Drew

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: HEADSUP: GCC 3.2.1 update is coming

2002-10-10 Thread Steve Kargl

On Thu, Oct 10, 2002 at 07:10:44PM -0400, Andrew Gallatin wrote:
> 
> This is a terrible example in that its impossible to tell what
> happened, but it sure shows that something is wrong.
> 
> Is there a floating point regression suite that you can point me at?
> That would be more useful for debugging.  
> 

ftp://ftp.netlib.org/fp/ucbtest.tgz

This is Kahan and his students floating point testsuite.
It normally check for conformance to IEEE-754.

-- 
Steve

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: HEADSUP: GCC 3.2.1 update is coming

2002-10-10 Thread Martin Blapp


Hi,

> Looks like we win some and we loose some.  I just noticed something
> weird on my P4 desktop using:

I reported it too soon. I forgot that on remote Desktops the problem doesn't
happen
:P

So OpenOffice is still broken.

Yes, now mpg123 plays sound, but the output is horribly noisy. I'm at home
now and can hear the sound. From work I just saw that it played something,
since the output was not anymore zero.

> Is there a floating point regression suite that you can point me at?
> That would be more useful for debugging.

Yes please !

Martin


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: HEADSUP: GCC 3.2.1 update is coming

2002-10-10 Thread Steve Kargl

On Fri, Oct 11, 2002 at 01:26:47AM +0200, Martin Blapp wrote:
> 
> > Is there a floating point regression suite that you can point me at?
> > That would be more useful for debugging.
> 

I forgot another test suite.  See
http://www.cs.berkeley.edu/~jhauser/arithmetic/TestFloat.html

-- 
Steve

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: disk running out of space

2002-10-10 Thread Scott M. Nolde

That's what newsyslog is for, and you don't have to stop apache:
/path/to/httpd-access.log   640  7  *  $W0D0 B /var/run/httpd.pid 30

- Scott

Guezou Philippe([EMAIL PROTECTED])@2002.10.10 10:05:10 +:
> [Charset iso-8859-1 unsupported, filtering to ASCII...]
> > Thank you for your suggestion I restarted apache on my server my df -h is
> > giving
> > 
> > FilesystemSize   Used  Avail Capacity  Mounted on
> > /dev/ad0s2a   9.6G   1.0G   7.8G12%/
> > /dev/ad2s1e55G39G11G77%/data
> > /dev/ad0s1e   9.6G   2.0K   8.8G 0%/data2
> > /dev/ad0s3e26G   1.0G23G 4%/data3
> > /dev/ad0s2e   9.6G   1.9G   6.9G22%/usr
> > procfs4.0K   4.0K 0B   100%/proc
> > 
> > What might be the problem??? In future how can I overcome this type of
> > problems without restarting the service.
> 
> oh well, here, we stop all apache around 23h45, then rotate the logs (moving them 
>into
> an other directory log/cold//) before restarting.. It take approximately 3 
>seconds
> to stop, move and restart.. Your users shouldn't notice the stop/start..
> 
> hope this helps..
> fifi..
> 
> > 
> > Suresh
> 
> -- 
> Guezou Philippe   [EMAIL PROTECTED]
> FreeBSD, The power to serve.
> 
> Buying an operating system without source is like buying
> a self-assembly Space Shuttle with no instructions.
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message

-- 
Scott Nolde
GPG Key 0xD869AB48

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: disk running out of space

2002-10-10 Thread David Wright

> That's what newsyslog is for, and you don't have to stop apache:
> /path/to/httpd-access.log   640  7  *  $W0D0 B /var/run/httpd.pid 30

Yep, and there's also the rotatelogs(8) utility that comes with apache, 
e.g. to rotate once a week:

CustomLog   "| rotatelogs /path/to/log/fileprefix 604800" combined

David

> Guezou Philippe([EMAIL PROTECTED])@2002.10.10 10:05:10 +:
>> [Charset iso-8859-1 unsupported, filtering to ASCII...]
>>> Thank you for your suggestion I restarted apache on my server my df 
>>> -h is
>>> giving
>>>
>>> FilesystemSize   Used  Avail Capacity  Mounted on
>>> /dev/ad0s2a   9.6G   1.0G   7.8G12%/
>>> /dev/ad2s1e55G39G11G77%/data
>>> /dev/ad0s1e   9.6G   2.0K   8.8G 0%/data2
>>> /dev/ad0s3e26G   1.0G23G 4%/data3
>>> /dev/ad0s2e   9.6G   1.9G   6.9G22%/usr
>>> procfs4.0K   4.0K 0B   100%/proc
>>>
>>> What might be the problem??? In future how can I overcome this type 
>>> of
>>> problems without restarting the service.
>>
>> oh well, here, we stop all apache around 23h45, then rotate the logs 
>> (moving them into
>> an other directory log/cold//) before restarting.. It take 
>> approximately 3 seconds
>> to stop, move and restart.. Your users shouldn't notice the 
>> stop/start..
>>
>> hope this helps..
>> fifi..
>>
>>>
>>> Suresh
>>
>> -- 
>> Guezou Philippe  [EMAIL PROTECTED]
>> FreeBSD, The power to serve.
>>
>> Buying an operating system without source is like buying
>> a self-assembly Space Shuttle with no instructions.
>>
>>
>>
>> To Unsubscribe: send mail to [EMAIL PROTECTED]
>> with "unsubscribe freebsd-stable" in the body of the message
>
> -- 
> Scott Nolde
> GPG Key 0xD869AB48
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message
>
>


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: imake-4 build broken

2002-10-10 Thread Mike Barcroft

Vallo Kallaste <[EMAIL PROTECTED]> writes:
> Hi
> 
> imake-4 port building is broken. I guess that's because
> xc/config/makedepend/main.c defines _POSIX_SOURCE before including
> . Signal.h includes  which has conditional
> #if !defined(_POSIX_SOURCE) and NSIG will be left undefined. Don't
> know who is in fault here, imake sources or our headers, my
> knowledge happens to end there.

I don't really understand how this is happening.  The uses of NSIG are
also conditionalized.  If _POSIX_SOURCE is defined, line 46 should not
be visible.  What rev is your /usr/include/sys/cdefs.h and
/usr/include/signal.h?

Best regards,
Mike Barcroft

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: HEADSUP: GCC 3.2.1 update is coming

2002-10-10 Thread Alexander Kabaev

On Fri, 11 Oct 2002 01:26:47 +0200 (CEST)
Martin Blapp <[EMAIL PROTECTED]> wrote:

> 
> Hi,
> 
> > Looks like we win some and we loose some.  I just noticed something
> > weird on my P4 desktop using:
> 
> I reported it too soon. I forgot that on remote Desktops the problem
> doesn't happen
> :P

Could you please try to compile libmsun with with GCC 3.3 snapshot David
just committed and see if that changes anything?

-- 
Alexander Kabaev

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: HEADSUP: GCC 3.2.1 update is coming

2002-10-10 Thread David O'Brien

On Thu, Oct 10, 2002 at 08:38:58PM -0400, Alexander Kabaev wrote:
> Could you please try to compile libmsun with with GCC 3.3 snapshot David
> just committed and see if that changes anything?

It doesn't compile on -current.  Mike and the standards guys are suspose
to undo the breakage that crept into out headers.  For the daring, try to
build the port and then change the two "u_long" that is complained about
to "unsigned long".

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: mkmagic

2002-10-10 Thread David O'Brien

On Thu, Oct 10, 2002 at 04:23:54PM -0600, Colin Harford wrote:
> Any ideas?  Is this just a newbie error or something more.  I have gone
> into the archives on MARC and have not found anything about it

Something is wrong with your sources.
 
> cat /usr/src/usr.bin/file/../../contrib/file/Header
> /usr/src/usr.bin/file/../../contrib/file/Localstuff
> /usr/src/usr.bin/file/../../contrib/file/Magdir/uuencode,v

Why do you have ,v files in your /usr/src directory?

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: HEADSUP: GCC 3.2.1 update is coming

2002-10-10 Thread Don Lewis

On 10 Oct, Steve Kargl wrote:
> On Thu, Oct 10, 2002 at 07:10:44PM -0400, Andrew Gallatin wrote:
>> 
>> This is a terrible example in that its impossible to tell what
>> happened, but it sure shows that something is wrong.
>> 
>> Is there a floating point regression suite that you can point me at?
>> That would be more useful for debugging.  
>> 
> 
> ftp://ftp.netlib.org/fp/ucbtest.tgz
> 
> This is Kahan and his students floating point testsuite.
> It normally check for conformance to IEEE-754.

For something a bit older, see .


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: 3+ days: syntax error in makedevs.c (sysinstall)

2002-10-10 Thread Kris Kennaway

On Thu, Oct 10, 2002 at 11:02:52PM +, Daniel Flickinger wrote:

> + The 'installincludes' thing appears to be unnecessary and can possibly
> + cause problems.
> 
>   well, you can rattle that around with phk, too! [g]
> 
>   installincludes puts the corresponding headers in
>   place for the compiler. theoretically, buildworld
>   -I declarations cover the game... but

Yes, buildworld builds includes itself, so at best this is a NOP, and
it should under no circumstances be required.

> + This isn't enough..you have to 'make cleandir' (not 'make clean')
> + twice to remove all cruft from the obj and build dir (the first time
> + removes the obj dir completely, the second time picks up any remaining
> + cruft in the build directory itself.  Stale generated files in your
> + build directory can certainly cause buildworld failures.
> 
>   even if there are stray files after 'clean' (which there were
>   not since I checked the obj tree, the function of 'depend' is
>   to check the time stamps as well.

Assuming the makefiles are non-broken.  Some of the 'depend' targets
in the source tree are very dubious.  kdump, ktrace and sysinstall are
three targets which usually refuse to rebuild generated files when
dependencies change (and 'make depend' does nothing).

>   running cleandir twice still left me after 'make all' with:
> 
>   makedevs.c:54: syntax error before ',' token
>   makedevs.c:60: syntax error before ',' token
>   *** Error code 1

What is the relevant part of the file?

Kris



msg44526/pgp0.pgp
Description: PGP signature


Re: HEADSUP: GCC 3.2.1 update is coming

2002-10-10 Thread Kris Kennaway

On Thu, Oct 10, 2002 at 04:29:33PM -0700, Steve Kargl wrote:
> On Fri, Oct 11, 2002 at 01:26:47AM +0200, Martin Blapp wrote:
> > 
> > > Is there a floating point regression suite that you can point me at?
> > > That would be more useful for debugging.
> > 
> 
> I forgot another test suite.  See
> http://www.cs.berkeley.edu/~jhauser/arithmetic/TestFloat.html

Are these suitable for importing as a regression suite?

Kris



msg44527/pgp0.pgp
Description: PGP signature


Re: HEADSUP: GCC 3.2.1 update is coming

2002-10-10 Thread Steve Kargl

On Thu, Oct 10, 2002 at 08:36:19PM -0700, Don Lewis wrote:
> On 10 Oct, Steve Kargl wrote:
> > On Thu, Oct 10, 2002 at 07:10:44PM -0400, Andrew Gallatin wrote:
> >> 
> >> This is a terrible example in that its impossible to tell what
> >> happened, but it sure shows that something is wrong.
> >> 
> >> Is there a floating point regression suite that you can point me at?
> >> That would be more useful for debugging.  
> >> 
> > 
> > ftp://ftp.netlib.org/fp/ucbtest.tgz
> > 
> > This is Kahan and his students floating point testsuite.
> > It normally check for conformance to IEEE-754.
> 
> For something a bit older, see .
> 
> 

Paranoia only checks things like rounding and epsilon.
ucbtest tests corner cases for the standard intrinsics.
ucbtest should be a much better test of libm than
paranoia.

-- 
Steve

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: HEADSUP: GCC 3.2.1 update is coming

2002-10-10 Thread David O'Brien

On Thu, Oct 10, 2002 at 08:47:15PM -0700, Kris Kennaway wrote:
> Are these suitable for importing as a regression suite?

We could just import the GCC testsuite... it would add 25 MB (checked
out, more w/in /home/ncvs/src :-( )

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: HEADSUP: GCC 3.2.1 update is coming

2002-10-10 Thread Kris Kennaway

On Thu, Oct 10, 2002 at 10:32:15PM -0700, David O'Brien wrote:
> On Thu, Oct 10, 2002 at 08:47:15PM -0700, Kris Kennaway wrote:
> > Are these suitable for importing as a regression suite?
> 
> We could just import the GCC testsuite... it would add 25 MB (checked
> out, more w/in /home/ncvs/src :-( )

Hmm, perhaps this should go in a new cvsup collection or somewhere
else optional-but-accessible.

Kris






msg44530/pgp0.pgp
Description: PGP signature


who building sucessed zhcon under current

2002-10-10 Thread suken woo

I wanna to buid it ,but always get failed. thanks any information.
best regards
===>  Building for zh-zhcon-0.2_4
gmake  all-recursive
gmake[1]: Entering directory `/usr/ports/chinese/zhcon/work/zhcon-0.2'
Making all in src
gmake[2]: Entering directory `/usr/ports/chinese/zhcon/work/zhcon-0.2/src'
Making all in display
gmake[3]: Entering directory 
`/usr/ports/chinese/zhcon/work/zhcon-0.2/src/displa
y'
gmake[3]: Nothing to be done for `all'.
gmake[3]: Leaving directory 
`/usr/ports/chinese/zhcon/work/zhcon-0.2/src/display
'
gmake[3]: Entering directory `/usr/ports/chinese/zhcon/work/zhcon-0.2/src'
c++  -O2 -DNDEBUG -funsigned-char -Wall  -Wl,-rpath=/usr/lib/unicon -o 
zhcon  -L
/usr/lib/unicon  basefont.o big52gbdecoder.o big5decoder.o configfile.o 
console.
o gb2big5decoder.o gbdecoder.o gbkdecoder.o graphdev.o hzdecoder.o 
jisdecoder.o
kscmdecoder.o main.o window.o winime.o zhcon.o overspotclient.o 
nativeinputserve
r.o inputclient.o inputmanager.o inputserver.o candilist.o 
uniconinputserver.o c
onfigserver.o nativebarclient.o display/libdisplay.a -lutil -lc -lintl  
-L/usr/l
ib/unicon -L/usr/local/lib
overspotclient.o: In function `OverSpotClient::Update()':
overspotclient.o(.text+0x536): undefined reference to 
`InputServer::IsFullChar()
'
overspotclient.o(.text+0x57e): undefined reference to 
`InputServer::IsFullComma(
)'
overspotclient.o: In function `OverSpotClient::AdjustWinPos(int, int, 
int, int)'
:
overspotclient.o(.text+0xa74): undefined reference to `Window::ColsOvered()'
overspotclient.o(.text+0xa7e): undefined reference to `Window::RowsOvered()'
inputmanager.o: In function `InputManager::ProcessInputKey(char)':
inputmanager.o(.text+0xbf9): undefined reference to 
`InputServer::IsFullChar()'
inputmanager.o(.text+0xc30): undefined reference to 
`InputServer::IsFullComma()'
nativebarclient.o: In function `NativeBarClient::Update()':
nativebarclient.o(.text+0x6fb): undefined reference to 
`InputServer::IsFullChar(
)'
nativebarclient.o(.text+0x73e): undefined reference to 
`InputServer::IsFullComma
()'
gmake[3]: *** [zhcon] Error 1
gmake[3]: Leaving directory `/usr/ports/chinese/zhcon/work/zhcon-0.2/src'
gmake[2]: *** [all-recursive] Error 1
gmake[2]: Leaving directory `/usr/ports/chinese/zhcon/work/zhcon-0.2/src'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/ports/chinese/zhcon/work/zhcon-0.2'
gmake: *** [all-recursive-am] Error 2
*** Error code 2

Stop in /usr/ports/chinese/zhcon.



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: imake-4 build broken

2002-10-10 Thread Vallo Kallaste

On Thu, Oct 10, 2002 at 08:03:00PM -0400, Mike Barcroft <[EMAIL PROTECTED]> wrote:

> > imake-4 port building is broken. I guess that's because
> > xc/config/makedepend/main.c defines _POSIX_SOURCE before including
> > . Signal.h includes  which has conditional
> > #if !defined(_POSIX_SOURCE) and NSIG will be left undefined. Don't
> > know who is in fault here, imake sources or our headers, my
> > knowledge happens to end there.
> 
> I don't really understand how this is happening.  The uses of NSIG are
> also conditionalized.  If _POSIX_SOURCE is defined, line 46 should not
> be visible.  What rev is your /usr/include/sys/cdefs.h and
> /usr/include/signal.h?

/usr/include/sys/cdefs.h:
 $FreeBSD: src/sys/sys/cdefs.h,v 1.67 2002/10/07 02:50:44 mike Exp $
 $FreeBSD: src/sys/sys/cdefs.h,v 1.67 2002/10/07 02:50:44 mike Exp $

/usr/include/signal.h:
 $FreeBSD: src/include/signal.h,v 1.19 2002/10/06 21:54:08 mike Exp $

The same error happens several times down the road of XFree86-4 port
compilation and all the problematic source files contain
#include  surrounded by _POSIX_SOURCE. Removing this
_POSIX_SOURCE thing got the XFree86-4 port compile to me.
-- 

Vallo Kallaste
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message