Re: random woes (no RSA support in libssl and libcrypto)

2001-03-27 Thread Valentin Nechayev

 Mon, Mar 19, 2001 at 16:02:08, mark (Mark Murray) wrote about "Re: random woes ("no 
RSA support in libssl and libcrypto")": 

  ssh: no RSA support in libssl and libcrypto.  See ssl(8)
[...]
  It seems the compatibility with the previous minor of urandom has
  been silently removed (I assume this happened with the last
  update/cleanup of the random device). It took me two hours to figure
  it out.
 
 See src/UPDATING 2624

Well, but it says about `options RANDOMDEV'. Later, `device random' was
invented instead of it. A few days ago I installed -CURRENT
(date=2001.03.25.12.00.00) with removing all previous content of /usr/lib
(which contained legacy since 3.1-RELEASE) and /usr/sbin/sshd began to refuse
supporting protocol 1 with identical message
(`no RSA support in libssl and libcrypto.  See ssl(8)'). Also,
kernel was build with `device random', and

netch@iv:/usr/HEAD/src/sys/i386/confegrep '(RSA|USA)' /etc/make.conf
# If you're resident in the USA, this will help various ports to determine
USA_RESIDENT=   NO
WITH_RSA=YES

And, my questions are
1) What can happen to refuse RSA support in libcrypto, with environment
described above?
2) How can one diagnose reason of such problems without abusing studying
of libcrypto internals?
3) Can anybody provide more descriptive message when random device
works improperly?


/netch

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



Re: random woes (no RSA support in libssl and libcrypto)

2001-03-27 Thread George Reid

On Tue, 27 Mar 2001, Valentin Nechayev wrote:

 And, my questions are
 1) What can happen to refuse RSA support in libcrypto, with environment
 described above?

I suspect you need to remake /dev/urandom. Copy /usr/src/etc/MAKEDEV from
-current into /etc and remake the device. /dev/urandom is now a symlink to
/dev/random.

G


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



Re: random woes (no RSA support in libssl and libcrypto)

2001-03-27 Thread Mark Murray

  See src/UPDATING 2624
 
 Well, but it says about `options RANDOMDEV'. Later, `device random' was
 invented instead of it. A few days ago I installed -CURRENT
 (date=2001.03.25.12.00.00) with removing all previous content of /usr/lib
 (which contained legacy since 3.1-RELEASE) and /usr/sbin/sshd began to refuse
 supporting protocol 1 with identical message
 (`no RSA support in libssl and libcrypto.  See ssl(8)'). Also,
 kernel was build with `device random', and
 
 netch@iv:/usr/HEAD/src/sys/i386/confegrep '(RSA|USA)' /etc/make.conf
 # If you're resident in the USA, this will help various ports to determine
 USA_RESIDENT=   NO
 WITH_RSA=YES

You missed (and deleted) the bit where it tells you to rerun MAKEDEV
to rebuild your devices.

 And, my questions are
 1) What can happen to refuse RSA support in libcrypto, with environment
 described above?

An incorrect /dev/urandom

 2) How can one diagnose reason of such problems without abusing studying
 of libcrypto internals?

More reading of UPDATING? I'll see if I can get it clarified.

 3) Can anybody provide more descriptive message when random device
 works improperly?

Yes. I'm working on making the random device itself moan at you.

M
-- 
Mark Murray
Warning: this .sig is umop ap!sdn

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



top output broked?

2001-03-27 Thread Alfred Perlstein


  PID USERNAME PRI NICE   SIZERES STATE  C   TIME   WCPUCPU COMMAND
  824 root  -80  1048K   596K biord  0   0:38  0.00%  0.00% find
  385 root   40 32740K 31944K select 1   0:32  0.00%  0.00% XFree86
  836 root  -80   532K   276K biord  1   0:07  0.00%  0.00% nfsd
14848 root  960 26912K 26832K RUN1   0:04  0.00%  0.00% ld
  424 bright 40  2120K  1340K select 0   0:04  0.00%  0.00% rxvt


no cpu time, known issue?


-- 
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
Represent yourself, show up at BABUG http://www.babug.org/

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



usr.bin/kdump - 'make world' broken?

2001-03-27 Thread Eckhard Kantz

What could be the reason for the following problem?

=== usr.bin/kdump
cc -O -pipe  -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../
..   -I/usr/obj/usr/src/i386/usr/include -c ioctl.c
In file included from ioctl.c:96:
/usr/obj/usr/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE'
redefined
/usr/obj/usr/src/i386/usr/include/pccard/cardinfo.h:81: warning: this is the
location of the previous definition
In file included from ioctl.c:52:
/usr/obj/usr/src/i386/usr/include/machine/i4b_rbch_ioctl.h:45: `TELNO_MAX'
undeclared here (not in a function)
*** Error code 1

Stop in /usr/src/usr.bin/kdump.
*** Error code 1

Stop in /usr/src/usr.bin.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.


Thanks for any advice.

Eckhard



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



Re: ** HEADS UP ** portmap daemon renamed to rpcbind

2001-03-27 Thread Karsten W. Rohrbach

Warner Losh([EMAIL PROTECTED])@Tue, Mar 27, 2001 at 12:40:18AM -0700:
 In message [EMAIL PROTECTED] Greg Lehey writes:
 :  Play the ball, not the man.
 : 
 : I don't have an objection to the change, I was just asking.  And
 : "because System V does it this way" has never been a good answer for
 : us.  And no, I'm not picking on Doug, just making a point.
 
 I see no reason why the name can't remain portmap.
 
does it take parameters?
then it would make sense to have it named rpcbind...
/k

-- 
 "Dope will get you through times of no money better that money will get
 you through times of no dope." -- Gilbert Shelton
KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de


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



Can't build current...

2001-03-27 Thread Gabriel Ambuehl

-BEGIN PGP SIGNED MESSAGE-

Hello,
I can't seem to be able to build 5-CURRENT since several days. I just
cvsupped again (tracking everything on CURRENT branch) but I always
run
into the following:

sh /usr/src/tools/install.sh -c -o root -g wheel -m 444   libmd.a
/usr/obj/usr/src/i386/usr/lib
sh /usr/src/tools/install.sh -c -o root -g wheel -m 444   libmd_p.a
/usr/obj/usr/src/i386/usr/lib
sh /usr/src/tools/install.sh -c -s -o root -g wheel -m 444
libmd.so.2 /usr/obj/usr/src/i386/usr/lib
ln -sf libmd.so.2 /usr/obj/usr/src/i386/usr/lib/libmd.so
cd /usr/src/lib/libcrypt;  make depend;  make all;  make install
make: don't know how to make crypt-blowfish.c. Stop
*** Error code 2

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.


when trying to do make buildworld. Machine is a K6-2 500 running
15.3.01
5-CURRENT snapshot. Am I too stupid (haven't run into any problems on
4.X for a long time so ;-) or is this broken?




Best regards,
 Gabriel

-BEGIN PGP SIGNATURE-
Version: PGP 6.0.2i

iQEVAwUBOsCglsZa2WpymlDxAQGcJggAsRBFAA/W8kaVKJSPzaPUFH00XI8vq4SV
vjNjWNk65HKNyeG1ceVU7nVETBpENsLqXM0hZ04FLTBR5ii5snqfBm+JVpAvMLMa
NHpnfXFImDNOsIai0LSArx86uT4jIBGer26odpnJQV0yEffdyzqdXAMMIHg2Gh2/
QJNnSjXA9Mccgkfr/W8V1DWAJaaBRfgczy3HolwhjWOpNXm6V+5ZSW3LW1tIvra/
n7N2eR7liwW/LHNbVKejbJUKc11pu9tlY59Uq9fmXFYdfV4R2R3Wrv0SvZgW9uyV
YTOzBqSH9LJVjNkVMgvOjmIQ2AZgjs1N8y+ThDuAGDXLn5izlgsaUA==
=AmSS
-END PGP SIGNATURE-



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



Re: page fault in mpu.c

2001-03-27 Thread Szilveszter Adam

On Mon, Mar 26, 2001 at 09:42:34PM -0500, Jim Bloom wrote:
 I finally tracked down the page fault I was seeing while probing the mpu.
 The mutex was not being initialized before it was used.  I have included a
 patch below which fixes the problem.  Will someone please review the style
 and commit the fix.

I can confirm that this fixes the problem (as in the kernel builds and
boots with options midi and sequencer.)

Thanks!
-- 
Regards:

Szilveszter ADAM
Szeged University
Szeged Hungary

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



Can't build current...

2001-03-27 Thread Gabriel Ambuehl

-BEGIN PGP SIGNED MESSAGE-

Hello,
I can't seem to be able to build 5-CURRENT since several days. I just
cvsupped again (tracking everything on CURRENT branch) but I always
run
into the following:

sh /usr/src/tools/install.sh -c -o root -g wheel -m 444   libmd.a
/usr/obj/usr/src/i386/usr/lib
sh /usr/src/tools/install.sh -c -o root -g wheel -m 444   libmd_p.a
/usr/obj/usr/src/i386/usr/lib
sh /usr/src/tools/install.sh -c -s -o root -g wheel -m 444
libmd.so.2 /usr/obj/usr/src/i386/usr/lib
ln -sf libmd.so.2 /usr/obj/usr/src/i386/usr/lib/libmd.so
cd /usr/src/lib/libcrypt;  make depend;  make all;  make install
make: don't know how to make crypt-blowfish.c. Stop
*** Error code 2

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.


when trying to do make buildworld. Machine is a K6-2 500 running
15.3.01
5-CURRENT snapshot. Am I too stupid (haven't run into any problems on
4.X for a long time so ;-) or is this broken?




Best regards,
 Gabriel

-BEGIN PGP SIGNATURE-
Version: PGP 6.0.2i

iQEVAwUBOsCkO8Za2WpymlDxAQF+0gf/da0BeB8FWe+6revJQHYX9RwCFFr2/u7w
AH4CO6PnK3YieMD4SHm05Ng3I1MiIcj0inZevR7jIsGAVrsnHN8i9OgCxtDANaFt
cYnP+kyhSWW/qQB6wATidWxaCVMK8IdXrouAdOtyGmtaa2jVIc5tUqlgx27R9sT0
jTZl0Wu1lEmrEIKu+I2Wp9K1MUdXtiBktcDmYtj08nIe5dh160/UUh5c9ZqS41IR
s+5ggR3Kcx70kitu16eRJ2IyQbwl/zl3QUOSGWKrJTJtE18tGYqjXqklC6cVFPWl
TK9q5s41NwUT8U5fK+Y23p6Gzrwb5gsEvY889PAMV7VOT7MzH9fCtg==
=xBW5
-END PGP SIGNATURE-



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



Re: usr.bin/kdump - 'make world' broken?

2001-03-27 Thread Sergey A. Osokin

On Tue, Mar 27, 2001 at 01:22:51PM +0200, Eckhard Kantz wrote:
 What could be the reason for the following problem?
 
 === usr.bin/kdump
 cc -O -pipe  -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../
 ..   -I/usr/obj/usr/src/i386/usr/include -c ioctl.c
 In file included from ioctl.c:96:
 /usr/obj/usr/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE'
 redefined
 /usr/obj/usr/src/i386/usr/include/pccard/cardinfo.h:81: warning: this is the
 location of the previous definition
 In file included from ioctl.c:52:
 /usr/obj/usr/src/i386/usr/include/machine/i4b_rbch_ioctl.h:45: `TELNO_MAX'
 undeclared here (not in a function)
 *** Error code 1
 
 Stop in /usr/src/usr.bin/kdump.
 *** Error code 1

I reported about this problem more then 3 months ago.
(http://www.freebsd.org/cgi/getmsg.cgi?fetch=434185+436356+/usr/local/www/db/text/2001/freebsd-current/20010128.freebsd-current)

I think this problem may resolve with following steps:
1) rm -rf /usr/src
2) re-sup
3) try to make buildworld
But i haven't -current @ fast channel for this...

Also, you may do following:
1) vi /usr/src/usr.bin/kdump/Makefile and remove ${DESTDIR} at line 11
2) vi /usr/src/usr.bin/truss/Makefile remove ${DESTDIR} at line 32
3) try to make buildworld

I recommend first way.
It looks like mkioctls do something wrong at ${DESTDIR} at
buildworld time.
-- 

Rgdz,/"\ 
Sergey Osokin aka oZZ,   \ /  ASCII RIBBON CAMPAIGN
[EMAIL PROTECTED]X AGAINST HTML MAIL
http://freebsd.org.ru/~osa/  / \

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



Re: usr.bin/kdump - 'make world' broken?

2001-03-27 Thread Ruslan Ermilov

On Tue, Mar 27, 2001 at 07:34:49PM +0400, Sergey A. Osokin wrote:
 On Tue, Mar 27, 2001 at 01:22:51PM +0200, Eckhard Kantz wrote:
  What could be the reason for the following problem?
  
  === usr.bin/kdump
  cc -O -pipe  -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../
  ..   -I/usr/obj/usr/src/i386/usr/include -c ioctl.c
  In file included from ioctl.c:96:
  /usr/obj/usr/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE'
  redefined
  /usr/obj/usr/src/i386/usr/include/pccard/cardinfo.h:81: warning: this is the
  location of the previous definition
  In file included from ioctl.c:52:
  /usr/obj/usr/src/i386/usr/include/machine/i4b_rbch_ioctl.h:45: `TELNO_MAX'
  undeclared here (not in a function)
  *** Error code 1
  
  Stop in /usr/src/usr.bin/kdump.
  *** Error code 1
 
 I reported about this problem more then 3 months ago.
 
(http://www.freebsd.org/cgi/getmsg.cgi?fetch=434185+436356+/usr/local/www/db/text/2001/freebsd-current/20010128.freebsd-current)
 
 I think this problem may resolve with following steps:
 1) rm -rf /usr/src
 2) re-sup
 3) try to make buildworld
 But i haven't -current @ fast channel for this...
 
 Also, you may do following:
 1) vi /usr/src/usr.bin/kdump/Makefile and remove ${DESTDIR} at line 11
 2) vi /usr/src/usr.bin/truss/Makefile remove ${DESTDIR} at line 32
 3) try to make buildworld
 
 I recommend first way.
 It looks like mkioctls do something wrong at ${DESTDIR} at
 buildworld time.
 
Should be fixed in usr.bin/kdump/mkioctls,v 1.20.


Cheers,
-- 
Ruslan Ermilov  Oracle Developer/DBA,
[EMAIL PROTECTED]   Sunbay Software AG,
[EMAIL PROTECTED]  FreeBSD committer,
+380.652.512.251Simferopol, Ukraine

http://www.FreeBSD.org  The Power To Serve
http://www.oracle.com   Enabling The Information Age

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



Re: top output broked?

2001-03-27 Thread David Wolfskill

Date: Tue, 27 Mar 2001 03:18:10 -0800
From: Alfred Perlstein [EMAIL PROTECTED]


  PID USERNAME PRI NICE   SIZERES STATE  C   TIME   WCPUCPU COMMAND
  824 root  -80  1048K   596K biord  0   0:38  0.00%  0.00% find
  385 root   40 32740K 31944K select 1   0:32  0.00%  0.00% XFree86
  836 root  -80   532K   276K biord  1   0:07  0.00%  0.00% nfsd
14848 root  960 26912K 26832K RUN1   0:04  0.00%  0.00% ld
  424 bright 40  2120K  1340K select 0   0:04  0.00%  0.00% rxvt


no cpu time, known issue?

I get non-zero values from time to time; in particular, I fired up an
xterm  did a "while (1)" loop in it, and the CPU times increased in a
gratifying manner.  :-}

However, the usual values I'm seeing are rather lower than I would
expect, and lower than the same machine running -STABLE (within the last
several days, by my recollection).

As a reality check, I'm trying "vmstat 5", and it's consistently
reporting either 99 or 100% idle.  There -- I got both it  top to
report something noticeable:  I fired up netscape

Maybe it really *is* using CPU much more efficiently...?  No, I didn't
think so, but it was a nice thought  :-)

Oh:  recent CVSup history (I hadn't noticed the behavior in the
-CURRENNT I built yesterday):

CVSup started at Sun Mar 25 23:47:00 PST 2001
CVSup ended at Sun Mar 25 23:52:25 PST 2001
CVSup started at Mon Mar 26 23:47:00 PST 2001
CVSup ended at Mon Mar 26 23:53:39 PST 2001

Cheers,
david
-- 
David H. Wolfskill  [EMAIL PROTECTED]
As a computing professional, I believe it would be unethical for me to
advise, recommend, or support the use (save possibly for personal
amusement) of any product that is or depends on any Microsoft product.

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



RE: top output broked?

2001-03-27 Thread John Baldwin


On 27-Mar-01 Alfred Perlstein wrote:
 
   PID USERNAME PRI NICE   SIZERES STATE  C   TIME   WCPUCPU COMMAND
   824 root  -80  1048K   596K biord  0   0:38  0.00%  0.00% find
   385 root   40 32740K 31944K select 1   0:32  0.00%  0.00% XFree86
   836 root  -80   532K   276K biord  1   0:07  0.00%  0.00% nfsd
 14848 root  960 26912K 26832K RUN1   0:04  0.00%  0.00% ld
   424 bright 40  2120K  1340K select 0   0:04  0.00%  0.00% rxvt
 
 
 no cpu time, known issue?

Not one that I've seen:

  PID USERNAME PRI NICE   SIZERES STATE  C   TIME   WCPUCPU COMMAND
   11 root -160 0K 0K CPU0   0  79.5H 49.37% 49.37% idle: cpu0
   10 root -160 0K 0K RUN1  79.4H 48.19% 48.19% idle: cpu1
   13 root -48 -167 0K 0K WAIT   0  62:53  0.00%  0.00% swi6: tty:s
   15 root  760 0K 0K sleep  0   6:07  0.00%  0.00% random
5 root  200 0K 0K syncer 1   2:47  0.00%  0.00% syncer
   20 root -68 -187 0K 0K WAIT   1   1:18  0.00%  0.00% irq18: fxp0
   19 root -64 -183 0K 0K WAIT   0   0:53  0.00%  0.00% irq16: ahc0
   12 root -44 -163 0K 0K WAIT   0   0:52  0.00%  0.00% swi1: net
   18 root -36 -155 0K 0K WAIT   1   0:49  0.00%  0.00% swi3: cambi
4 root -160 0K 0K psleep 0   0:41  0.00%  0.00% bufdaemon
  283 root   40   552K   388K select 0   0:10  0.00%  0.00% dhclient

If you run 'top -S' does all your time show up in the idle processes like it
does here?

-- 

John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"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: top output broked?

2001-03-27 Thread David Wolfskill

Date: Tue, 27 Mar 2001 08:33:10 -0800 (PST)
From: John Baldwin [EMAIL PROTECTED]

Not one that I've seen:

  PID USERNAME PRI NICE   SIZERES STATE  C   TIME   WCPUCPU COMMAND
   11 root -160 0K 0K CPU0   0  79.5H 49.37% 49.37% idle: cpu0
   10 root -160 0K 0K RUN1  79.4H 48.19% 48.19% idle: cpu1
   13 root -48 -167 0K 0K WAIT   0  62:53  0.00%  0.00% swi6: tty:s
   15 root  760 0K 0K sleep  0   6:07  0.00%  0.00% random
5 root  200 0K 0K syncer 1   2:47  0.00%  0.00% syncer
   20 root -68 -187 0K 0K WAIT   1   1:18  0.00%  0.00% irq18: fxp0
   19 root -64 -183 0K 0K WAIT   0   0:53  0.00%  0.00% irq16: ahc0
   12 root -44 -163 0K 0K WAIT   0   0:52  0.00%  0.00% swi1: net
   18 root -36 -155 0K 0K WAIT   1   0:49  0.00%  0.00% swi3: cambi
4 root -160 0K 0K psleep 0   0:41  0.00%  0.00% bufdaemon
  283 root   40   552K   388K select 0   0:10  0.00%  0.00% dhclient

If you run 'top -S' does all your time show up in the idle processes like it
does here?

Hmm... mine loks like that (modulo #CPUs), except when I'm actually
making it do some work (re-building the kernel, in this case).  What I
see ("top -S") looks like:

last pid:  9546;  load averages:  0.97,  0.64,  0.30up 0+00:08:32  08:51:47
77 processes:  3 running, 57 sleeping, 2 zombie, 15 waiting
CPU states: 91.1% user,  0.0% nice,  5.4% system,  0.4% interrupt,  3.1% idle
Mem: 32M Active, 78M Inact, 27M Wired, 96K Cache, 35M Buf, 110M Free
Swap: 1024M Total, 4168K Used, 1020M Free

  PID USERNAME PRI NICE   SIZERES STATETIME   WCPUCPU COMMAND
   10 root -160 0K 0K RUN  3:43  2.15%  2.15% idle
 9545 root 1210  3428K  3304K RUN  0:00  2.00%  0.10% cc1
  514 root   40 27148K 26128K select   0:03  0.00%  0.00% XFree86
  212 root   40   420K   304K select   0:03  0.00%  0.00% pccardd
  610 david  40  4200K  3332K select   0:01  0.00%  0.00% xterm
   12 root -48 -167 0K 0K WAIT 0:01  0.00%  0.00% swi6: tty:sio
 7601 root   80  5112K  4764K wait 0:01  0.00%  0.00% make
   16 root -64 -183 0K 0K WAIT 0:01  0.00%  0.00% irq14: ata0
  312 root   40   976K   556K select   0:00  0.00%  0.00% moused
  603 david  40  2348K  1968K select   0:00  0.00%  0.00% ssh
   11 root -44 -163 0K 0K WAIT 0:00  0.00%  0.00% swi1: net
 1193 david 960  1964K  1208K RUN  0:00  0.00%  0.00% top
5 root  200 0K 0K syncer   0:00  0.00%  0.00% syncer
  288 root   40  2256K  1504K select   0:00  0.00%  0.00% sshd
  620 david  40  4200K  3332K select   0:00  0.00%  0.00% xterm
   14 root  760 0K 0K sleep0:00  0.00%  0.00% random
  350 root -68 -187 0K 0K WAIT 0:00  0.00%  0.00% irq3: an0


I confess a degree of skepticism  :-}

Here's output from "vmstat -5" around that time:

 1 2 0   43184104456  306   0   0   0 121   0   0   0  402  599 419 99  1  0
 1 2 0   37772109324 1209   0   0   0 1498   0   1   0  432 2032 549 91  6  2
 1 2 0   43032104124  918   0   0   0 669   0   1   0  394 1053 422 96  4  0
 1 2 0   44540102584  289   0   0   0 188   0   0   0  348  402 307 99  1  0
 2 1 0   39272108032 1123   0   0   0 1446   0   8   0  356 1515 362 90  5  5
 1 2 0   38448107844 1047   0   0   0 1066   0  10   0  368 1428 388 88  5  7
 1 1 0   36596108380 1240   0   0   0 1310   0   1   0  354 1643 362 94  5  2
 2 1 0   32264110776 1334   0   0   0 1504   0   2   0  381 1851 431 92  6  2
 1 0 0   30376110236 1850   0   0   0 1892   0   7   0  389 2506 462 86  8  6
 1 2 0   34904107064 1786   0   0   0 1692   0   4   0  360 2339 394 88  7  5
 2 0 0   30040108884 2437   0   0   0 2634   0  12   0  384 3194 466 77 10 14
 1 2 0   35544104636 1885   0   0   0 1734   0  27   0  405 2556 490 81  9 10
 1 2 0   34528104520 2339   0   0   0 2432   0   3   0  378 3136 455 85 10  5
 1 1 0   34620103844 2066   0   0   0 2115   0   2   0  370 2787 432 91  8  1
 procs  memory pagedisks faults  cpu
 r b w avm   fre  flt  re  pi  po  fr  sr ad0 md10   in   sy  cs us sy id
 2 0 0   28532106216 2618   0   0   0 2876   0   8   0  394 3524 514 83 13  4
 2 0 0   36172102488 2071   0   0   0 1967   0   7   0  402 2910 507 89  9  2


Cheers,
david
-- 
David H. Wolfskill  [EMAIL PROTECTED]
As a computing professional, I believe it would be unethical for me to
advise, recommend, or support the use (save possibly for personal
amusement) of any product that is or depends on any Microsoft product.

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



BROKEN DRIVER: pcm0: Yamaha DS-1E (YMF744) mem 0xfedf0000-0xfedf7fffirq 9 at device 9.0 on pci0

2001-03-27 Thread Daniel

Hi, I upgraded my kernel today, it was a week old, and when I try to
listen anything it sais:
pcm0: play interrupt timeout, channel dead
I'm in a Sony VAIO XG38.

---
PD: Is anyone still working with in the CFS/mount_nfs problem?


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



Re: usr.bin/kdump - 'make world' broken?

2001-03-27 Thread Sergey A. Osokin

On Tue, Mar 27, 2001 at 07:17:48PM +0300, Ruslan Ermilov wrote:
 On Tue, Mar 27, 2001 at 07:34:49PM +0400, Sergey A. Osokin wrote:
  On Tue, Mar 27, 2001 at 01:22:51PM +0200, Eckhard Kantz wrote:
   What could be the reason for the following problem?
   
   === usr.bin/kdump
   cc -O -pipe  -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../
   ..   -I/usr/obj/usr/src/i386/usr/include -c ioctl.c
   In file included from ioctl.c:96:
   /usr/obj/usr/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE'
   redefined
   /usr/obj/usr/src/i386/usr/include/pccard/cardinfo.h:81: warning: this is the
   location of the previous definition
   In file included from ioctl.c:52:
   /usr/obj/usr/src/i386/usr/include/machine/i4b_rbch_ioctl.h:45: `TELNO_MAX'
   undeclared here (not in a function)
   *** Error code 1
   
   Stop in /usr/src/usr.bin/kdump.
   *** Error code 1
  
 Should be fixed in usr.bin/kdump/mkioctls,v 1.20.

OK. I try buildworld now.

-- 

Rgdz,/"\ 
Sergey Osokin aka oZZ,   \ /  ASCII RIBBON CAMPAIGN
[EMAIL PROTECTED]X AGAINST HTML MAIL
http://freebsd.org.ru/~osa/  / \

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



Re: Can't build current...

2001-03-27 Thread Makoto MATSUSHITA


gabriel_ambuehl I can't seem to be able to build 5-CURRENT since several days.

You should have src/secure/lib/libcrypt/crypt-blowfish.c. If you don't
have, it's your problem. The CVS repository has this file already:
http://www.freebsd.org/cgi/cvsweb.cgi/src/secure/lib/libcrypt/crypt-blowfish.c

Have you update (or checkout) your src/secure, or which CVSup server you use?

-- -
Makoto MATSUSHITA

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



Re[2]: Can't build current...

2001-03-27 Thread Gabriel Ambuehl

-BEGIN PGP SIGNED MESSAGE-

Hello Makoto,

Tuesday, March 27, 2001, 7:55:15 PM, you wrote:


gabriel_ambuehl I can't seem to be able to build 5-CURRENT since
several days.

 You should have src/secure/lib/libcrypt/crypt-blowfish.c. If you
don't
 have, it's your problem. The CVS repository has this file already:

http://www.freebsd.org/cgi/cvsweb.cgi/src/secure/lib/libcrypt/crypt-blo
wfish.c

 Have you update (or checkout) your src/secure, or which CVSup server
you use?


I'm using cvsup.de.FreeBSD.org which appears to be a cname
cvsup.uk.FreeBSD.org.
But it looks like, that for some reason, src-secure didn't get added
to
the cvsupfile (hmm. might be related to the fact that cvsupit
creates cvsup.intl for that purpose and I forgot to add that one to
make.conf...). Mea culpa (hope it will work now).


While I'm writing this: what is the general opinion about having
CURRENT on production servers (I'd really love to deploy the ACLs
ASAP)? I don't plan to use SMP and can wait for snapshots til the
RELEASE comes...


Best regards,
 Gabriel

-BEGIN PGP SIGNATURE-
Version: PGP 6.0.2i

iQEVAwUBOsDJzsZa2WpymlDxAQGYMAf9E/gzHUM6H3897O9XJTRWKIyrEdW5eE6G
RvRU5FK+SxLa+FucsjU9dN4Yh41VD5C+mrq6nnTppBf7Wnt2QjyRx+7q7Hs12qdC
QMItugL+2iGGU6gioF0WZPeh1MrcWO6dbCn1o95QyYS/Sw9ePM+I4EA2Iiikh1EV
Rf7At5/zyQfnHtab2CSn4fQCGc/onfpmYSEZd4ezj2ykD9J9BQdRZtX7IqDodCZm
djhc6UYU9RFtUVzdCgXW8pYG9be9HNiUdZwnsi2GmEuSqhx05bUVJ0m1lL4t7Dwx
wJNVnkzCURmxjFtjc4d6am5wjyPOXOj2nrWoO96ZfybNLoT1g6rh0A==
=BB0w
-END PGP SIGNATURE-



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



Re: ** HEADS UP ** portmap daemon renamed to rpcbind

2001-03-27 Thread Doug Barton

"Karsten W. Rohrbach" wrote:
 
 Warner Losh([EMAIL PROTECTED])@Tue, Mar 27, 2001 at 12:40:18AM -0700:
  In message [EMAIL PROTECTED] Greg Lehey writes:
  :  Play the ball, not the man.
  :
  : I don't have an objection to the change, I was just asking.  And
  : "because System V does it this way" has never been a good answer for
  : us.  And no, I'm not picking on Doug, just making a point.
 
  I see no reason why the name can't remain portmap.
 
 does it take parameters?
 then it would make sense to have it named rpcbind...

Pardon me being dense, but what does that have to do with anything?
portmap took a -v flag, or are you talking about something different? 

-- 
Perhaps the greatest damage the American system of education has done
to its children is to teach them that their opinions are relevant
simply because they are their opinions.

Do YOU Yahoo!?

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



Re: ** HEADS UP ** portmap daemon renamed to rpcbind

2001-03-27 Thread Doug Barton

Warner Losh wrote:
 
 In message [EMAIL PROTECTED] Greg Lehey writes:
 :  Play the ball, not the man.
 :
 : I don't have an objection to the change, I was just asking.  And
 : "because System V does it this way" has never been a good answer for
 : us.  And no, I'm not picking on Doug, just making a point.
 
 I see no reason why the name can't remain portmap.

My previous comment was mostly an attempt at humor, in case anyone missed
that. :) I have no problem with keeping the name the same as it is in
netbsd to make code sharing easier. If this were something that users
interacted with directly I'd fight harder, but as it is portmap is
basically always started from rc*. We'll have another round of pain from
people who fail to properly update /etc, but we have enough land mines
there already to make this point moot. 

Doug
-- 
Perhaps the greatest damage the American system of education has done
to its children is to teach them that their opinions are relevant
simply because they are their opinions.

Do YOU Yahoo!?

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



cvsupit assumptions (was: Re: Re[2]: Can't build current...)

2001-03-27 Thread Robert Watson


On Tue, 27 Mar 2001, Gabriel Ambuehl wrote:

 I'm using cvsup.de.FreeBSD.org which appears to be a cname
 cvsup.uk.FreeBSD.org.  But it looks like, that for some reason,
 src-secure didn't get added to the cvsupfile (hmm. might be related to
 the fact that cvsupit creates cvsup.intl for that purpose and I forgot
 to add that one to make.conf...). Mea culpa (hope it will work now). 

I've actually heard that from a couple of other people lately -- that
cvsupit still assumes that crypto should not be pulled down, and the
crypto code is now assumed in the default build.  This may just be a
product of the packagized version of cvsupit shipped in the past, but it
might also be the case that cvsupit needs to be updated to take into
account changes in our cvsup policies and source layout.

Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED]  NAI Labs, Safeport Network Services



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



Re: Can't build current...

2001-03-27 Thread Kris Kennaway

On Wed, Mar 28, 2001 at 02:55:15AM +0900, Makoto MATSUSHITA wrote:

 You should have src/secure/lib/libcrypt/crypt-blowfish.c. If you don't
 have, it's your problem. The CVS repository has this file already:
 http://www.freebsd.org/cgi/cvsweb.cgi/src/secure/lib/libcrypt/crypt-blowfish.c
 
 Have you update (or checkout) your src/secure, or which CVSup server you use?

I believe Mark's intention was to keep crypt-blowfish.c optional for
those who don't want to install crypto.  Perhaps this is broken.

Kris

 PGP signature


Current for production?

2001-03-27 Thread John Baldwin


On 27-Mar-01 Gabriel Ambuehl wrote:
 While I'm writing this: what is the general opinion about having
 CURRENT on production servers (I'd really love to deploy the ACLs
 ASAP)? I don't plan to use SMP and can wait for snapshots til the
 RELEASE comes...

Don't.  ACL's are still not production quality yet, and the SMP work breaks UP
kernels just as bad as SMP kernels when it breaks.

-- 

John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"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: top output broked?

2001-03-27 Thread David Wolfskill

Date: Tue, 27 Mar 2001 10:21:46 -0800 (PST)
From: John Baldwin [EMAIL PROTECTED]

 Hmm... mine loks like that (modulo #CPUs), except when I'm actually
 making it do some work (re-building the kernel, in this case).  What I
 see ("top -S") looks like:

 last pid:  9546;  load averages:  0.97,  0.64,  0.30up 0+00:08:32 
 08:51:47
 77 processes:  3 running, 57 sleeping, 2 zombie, 15 waiting
 CPU states: 91.1% user,  0.0% nice,  5.4% system,  0.4% interrupt,  3.1% idle

This is probably right..

Yes; that much of it "feels" about right.

I don't know why you are seeing such weirdness however.  Is your world and
kernel out of sync.

Assuredly not, but I understand the rationale behind the question.  :-)
(I have the "script" log available for perusal)

It's a nice (mis)feature now that if items in the middle
of kinfo_proc change size it still tries to use the misordered data rather than
complaining about it like it used to. :-P  See my other e-mail where top on my
laptop doles out time to userland tasks ok.

 I confess a degree of skepticism  :-}

I agree.

:-)

Date: Tue, 27 Mar 2001 10:21:45 -0800 (PST)
From: John Baldwin [EMAIL PROTECTED]

Keep in mind that we no longer charge interrupt time to the process being
interrupted, instead all that interrupt handling has been pushed off into
ithreads.  Same for software interrupt threads.

OK; that's a good  useful thing to keep in mind.  And I did see some
IRQ-related entries in top's output.

That said, I don't see how X is so idle, it's certainly not on my laptop:

  PID USERNAME PRI NICE   SIZERES STATETIME   WCPUCPU COMMAND
  454 john   40 0K 43464K select   1:57  4.05%  4.05% XFree86
  461 john   40 17076K 16144K select   0:35  0.39%  0.39% enlightenment
  492 john   4   10  3072K  2040K select   0:28  0.10%  0.10% E-ScreenSave.

Eh... the "enlightenment" line may provide a clue there.  I use tvtwm as
a window manager.  :-}  (I figure anything that could be marginally
acceptable on a (maxed out) 24 MB Sun 3/60 ought to be adequate for this
750 MHz/256 MB laptop)

Cheers,
david
-- 
David H. Wolfskill  [EMAIL PROTECTED]
As a computing professional, I believe it would be unethical for me to
advise, recommend, or support the use (save possibly for personal
amusement) of any product that is or depends on any Microsoft product.

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



Re: ** HEADS UP ** portmap daemon renamed to rpcbind

2001-03-27 Thread Karsten W. Rohrbach

Doug Barton([EMAIL PROTECTED])@Tue, Mar 27, 2001 at 10:05:40AM -0800:
 "Karsten W. Rohrbach" wrote:
  
  Warner Losh([EMAIL PROTECTED])@Tue, Mar 27, 2001 at 12:40:18AM -0700:
   In message [EMAIL PROTECTED] Greg Lehey writes:
   :  Play the ball, not the man.
   :
   : I don't have an objection to the change, I was just asking.  And
   : "because System V does it this way" has never been a good answer for
   : us.  And no, I'm not picking on Doug, just making a point.
  
   I see no reason why the name can't remain portmap.
  
  does it take parameters?
  then it would make sense to have it named rpcbind...
 
   Pardon me being dense, but what does that have to do with anything?
 portmap took a -v flag, or are you talking about something different? 

the idea is, that if rpcbind takes parameters different from portmap it
would make sense to call rpcbind rpcbind because people's boxes will
start to barf when rpcbind is called portmap, they make world, and skip
reading the rpcbind paragraph in UPDATING ;-)

does this make sense?

/k

-- 
 Hugh Hefner is a virgin.
KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de


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



Re: top output broked?

2001-03-27 Thread David Wolfskill

Also, I happened to note that as I'm doing a "make buildworld" (for today's
-STABLE, running in yesterday's -STABLE), my "top -S" output shows a
large number of "0.00" entries for CPU (on the same laptop as my
previously-reported results).  So it may be odd, but at least -- in my
case -- it appears to be moderately consistent (modulo known  expected
changes between -STABLE  -CURRENT).

Cheers,
david
-- 
David H. Wolfskill  [EMAIL PROTECTED]
As a computing professional, I believe it would be unethical for me to
advise, recommend, or support the use (save possibly for personal
amusement) of any product that is or depends on any Microsoft product.

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



Re: Current for production?

2001-03-27 Thread Michael Lucas

I'd like to reinforce this:

I'm not a hacker, but have a -current box so I can write about it.
(It's difficult to write a book targeting 5.1-release and time it for
5.1-R, when you don't have 5-current.  This is one definite advantage
Greg Lehey has over the rest of us authorial sorts.)  With five years
fairly hardcore FreeBSD experience, tracking -current is a *pain*.

At any given point in time, 90% of the system works.  The 10% that
doesn't changes almost daily.

If you want to invest your time in finding a particular date of
-current that meets your needs, and you make a management decision
that you will never, never, *never* upgrade without going through the
same audit, go for it.

Plus, I've made a management decision to never whine about what's
broken, just live with it.  (Okay, I do report broken buildworlds, but
that's it.)  My Pilot software locks the machine up; the web browser
has been known to hang forever; the web server occasionally screams
obscenities; other miscellanous ports just puke.  Heck, I'm waiting
for this laptop to phone the police and report me as a kiddie porn
devotee, then anonymously transfer my bank balance to the Linux
Foundation.  It'll be for a technically sound reason, I know, but that
still makes it a pain.

I would run unionfs on a 3-stable production box before running
-current in production right now.

==ml

PS: You could also make a management decision to hire a kernel hacker
to work on the part of -current that you need.  :)



On Tue, Mar 27, 2001 at 10:21:47AM -0800, John Baldwin wrote:
 
 On 27-Mar-01 Gabriel Ambuehl wrote:
  While I'm writing this: what is the general opinion about having
  CURRENT on production servers (I'd really love to deploy the ACLs
  ASAP)? I don't plan to use SMP and can wait for snapshots til the
  RELEASE comes...
 
 Don't.  ACL's are still not production quality yet, and the SMP work breaks UP
 kernels just as bad as SMP kernels when it breaks.
 
 -- 
 
 John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
 PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
 "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

-- 
Michael Lucas
[EMAIL PROTECTED]
http://www.blackhelicopters.org/~mwlucas/
Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons

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



HEADS UP!! New PAM functionaity in CURRENT!

2001-03-27 Thread Mark Murray

Hello all!

I have just added new PAM functionality to CURRENT. There is now
better support for account management and sessions. If you foul
up your pam.conf merging, you may not be able to get into your
system.

PLEASE MERGE /etc/pam.conf WITH CARE!

At the least, your login section should look like:

login   authrequiredpam_unix.so try_first_pass
login   account requiredpam_unix.so
login   password required   pam_permit.so
login   session requiredpam_permit.so

and your sshd section should look like:

sshdauthrequiredpam_unix.so try_first_pass
sshdaccount requiredpam_unix.so
sshdpassword required   pam_permit.so
sshdsession requiredpam_permit.so

M
-- 
Mark Murray
Warning: this .sig is umop ap!sdn

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



Re: top output broked?

2001-03-27 Thread John Baldwin


On 27-Mar-01 David Wolfskill wrote:
Date: Tue, 27 Mar 2001 10:21:45 -0800 (PST)
From: John Baldwin [EMAIL PROTECTED]
 
Keep in mind that we no longer charge interrupt time to the process being
interrupted, instead all that interrupt handling has been pushed off into
ithreads.  Same for software interrupt threads.
 
 OK; that's a good  useful thing to keep in mind.  And I did see some
 IRQ-related entries in top's output.

Are they getting %CPU though.  When running top -S, the CPU %'s should always
add up to about 100 (with fudges for rounding errors).

That said, I don't see how X is so idle, it's certainly not on my laptop:
 
  PID USERNAME PRI NICE   SIZERES STATETIME   WCPUCPU COMMAND
  454 john   40 0K 43464K select   1:57  4.05%  4.05% XFree86
  461 john   40 17076K 16144K select   0:35  0.39%  0.39%
  enlightenment
  492 john   4   10  3072K  2040K select   0:28  0.10%  0.10%
  E-ScreenSave.
 
 Eh... the "enlightenment" line may provide a clue there.  I use tvtwm as
 a window manager.  :-}  (I figure anything that could be marginally
 acceptable on a (maxed out) 24 MB Sun 3/60 ought to be adequate for this
 750 MHz/256 MB laptop)

Heh, but I figured Alfred was in X when he was running top, so X must've been
doing _some_ screen updates, and not just have 0.00% CPU time. :-P

-- 

John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"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: top output broked?

2001-03-27 Thread David Wolfskill

Date: Tue, 27 Mar 2001 11:56:38 -0800 (PST)
From: John Baldwin [EMAIL PROTECTED]

 OK; that's a good  useful thing to keep in mind.  And I did see some
 IRQ-related entries in top's output.

Are they getting %CPU though.  When running top -S, the CPU %'s should always
add up to about 100 (with fudges for rounding errors).

Well, as noted in another note a little prior to this one, the -CURRENT
behavior I'm seeing isn't all *that* different from the -STABLE behavior
-- in each case, the sum of what "top" reports for CPU % is normally small.

 Eh... the "enlightenment" line may provide a clue there.  I use tvtwm as
 a window manager.  :-}  (I figure anything that could be marginally
 acceptable on a (maxed out) 24 MB Sun 3/60 ought to be adequate for this
 750 MHz/256 MB laptop)

Heh, but I figured Alfred was in X when he was running top, so X must've been
doing _some_ screen updates, and not just have 0.00% CPU time. :-P

Well, that gets into a matter of perspective, since the amount of CPU
resource required to do the screen updates (vs. what is available) could
well be 0.00 (to 2 decimals)  :-)  (Kinda like the ratio of a
circle's circumference to its diameter is "3" to a single significant
figure.)

(I was in X at the time, too.)

Cheers,
david
-- 
David H. Wolfskill  [EMAIL PROTECTED]
As a computing professional, I believe it would be unethical for me to
advise, recommend, or support the use (save possibly for personal
amusement) of any product that is or depends on any Microsoft product.

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



Re: top output broked?

2001-03-27 Thread John Baldwin


On 27-Mar-01 David Wolfskill wrote:
Date: Tue, 27 Mar 2001 11:56:38 -0800 (PST)
From: John Baldwin [EMAIL PROTECTED]
 
 OK; that's a good  useful thing to keep in mind.  And I did see some
 IRQ-related entries in top's output.
 
Are they getting %CPU though.  When running top -S, the CPU %'s should always
add up to about 100 (with fudges for rounding errors).
 
 Well, as noted in another note a little prior to this one, the -CURRENT
 behavior I'm seeing isn't all *that* different from the -STABLE behavior
 -- in each case, the sum of what "top" reports for CPU % is normally small.

-STABLE doesn't have idle processes. :)

 Eh... the "enlightenment" line may provide a clue there.  I use tvtwm as
 a window manager.  :-}  (I figure anything that could be marginally
 acceptable on a (maxed out) 24 MB Sun 3/60 ought to be adequate for this
 750 MHz/256 MB laptop)
 
Heh, but I figured Alfred was in X when he was running top, so X must've been
doing _some_ screen updates, and not just have 0.00% CPU time. :-P
 
 Well, that gets into a matter of perspective, since the amount of CPU
 resource required to do the screen updates (vs. what is available) could
 well be 0.00 (to 2 decimals)  :-)  (Kinda like the ratio of a
 circle's circumference to its diameter is "3" to a single significant
 figure.)
 
 (I was in X at the time, too.)

Fair enough..

-- 

John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"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: Re[2]: Can't build current...

2001-03-27 Thread J Wunsch

Gabriel Ambuehl [EMAIL PROTECTED] wrote:

 I'm using cvsup.de.FreeBSD.org which appears to be a cname
 cvsup.uk.FreeBSD.org.

Huh?  That would be a mistake if it happened.  But it isn't:

j@uriah 159% nslookup cvsup.de.freebsd.org
Server:  uriah.heep.sax.de
Address:  0.0.0.0

Non-authoritative answer:
Name:ftp.ecrc.net
Address:  62.208.224.162
Aliases:  cvsup.de.freebsd.org

j@uriah 160% nslookup cvsup.uk.freebsd.org
Server:  uriah.heep.sax.de
Address:  0.0.0.0

Non-authoritative answer:
Name:cvsup.plig.net
Address:  195.40.6.42
Aliases:  cvsup.uk.freebsd.org


cvsup.de.freebsd.org is a cname for cvsup5.de.freebsd.org, which is a
cname for ftp.ecrc.net.

-- 
cheers, J"org   .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)

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



Re: top output broked?

2001-03-27 Thread Alex Zepeda

On Tue, Mar 27, 2001 at 03:18:10AM -0800, Alfred Perlstein wrote:

   PID USERNAME PRI NICE   SIZERES STATE  C   TIME   WCPUCPU COMMAND
   824 root  -80  1048K   596K biord  0   0:38  0.00%  0.00% find
   385 root   40 32740K 31944K select 1   0:32  0.00%  0.00% XFree86
   836 root  -80   532K   276K biord  1   0:07  0.00%  0.00% nfsd
 14848 root  960 26912K 26832K RUN1   0:04  0.00%  0.00% ld
   424 bright 40  2120K  1340K select 0   0:04  0.00%  0.00% rxvt

Hmm, I just rebuilt world recently (this morning), and I'm seeing this:

  PID USERNAME PRI NICE   SIZERES STATE  C   TIME   WCPUCPU COMMAND
  311 root 1260   600K   264K CPU1   0  24:11 52.39% 52.39% nfsd
  503 postfix40  1604K   904K select 0   0:02  0.15%  0.15% qmgr
 8069 root  960  2088K  1240K CPU0   0   0:00  0.00%  0.00% top

Eek.  nfsd is sucking up CPU, even while it's idle (its only nfs client is
down for a few quick repairs).  I think it's been doing this since the
TI-RPC stuff was imported.

But, back to your problem, no 0.0% CPU time problem here.

- alex

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



No Subject

2001-03-27 Thread Ralph Hogge



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



HEADS UP: I'm breaking the kernel again

2001-03-27 Thread John Baldwin

That's right, more SMPng breakage is on the way.  Well, hopefully not bad
breakage.  On a more serious note, I've just spammed sys/alpha/alpha with parts
of the critical_enter/exit change which I meant to commit anyways, so I'm going
to go ahead and finish committing that right now.  The kernel probably won't
compile until it is all checked in.  Once I get this in I will hopefully also
get a chance to check in the new witness code tonight (or tomorrow morning as 
the case may be) as well.

-- 

John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"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: ** HEADS UP ** portmap daemon renamed to rpcbind

2001-03-27 Thread Doug Barton

"Karsten W. Rohrbach" wrote:

 the idea is, that if rpcbind takes parameters different from portmap it
 would make sense to call rpcbind rpcbind because people's boxes will
 start to barf when rpcbind is called portmap, they make world, and skip
 reading the rpcbind paragraph in UPDATING ;-)
 
 does this make sense?

Yes. "Takes parameters different from portmap," makes much more sense than
"takes parameters." :)

Thanks,

Doug
-- 
Perhaps the greatest damage the American system of education has done
to its children is to teach them that their opinions are relevant
simply because they are their opinions.

Do YOU Yahoo!?

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