From owner-freebsd-stable  Sun Jul  4  4:12:14 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from arc.hq.cti.ru (arc.hq.cti.ru [195.34.40.3])
	by hub.freebsd.org (Postfix) with ESMTP id EE74414BFE
	for <freebsd-stable@FreeBSD.ORG>; Sun,  4 Jul 1999 04:12:01 -0700 (PDT)
	(envelope-from dima@tejblum.dnttm.rssi.ru)
Received: (from uucp@localhost)
	by arc.hq.cti.ru (8.9.3/8.9.3) with UUCP id PAA28211;
	Sun, 4 Jul 1999 15:11:27 +0400 (MSD)
	(envelope-from dima@tejblum.dnttm.rssi.ru)
Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1])
	by tejblum.dnttm.rssi.ru (8.9.3/8.9.3) with ESMTP id PAA01808;
	Sun, 4 Jul 1999 15:13:52 +0400 (MSD)
	(envelope-from dima@tejblum.dnttm.rssi.ru)
Message-Id: <199907041113.PAA01808@tejblum.dnttm.rssi.ru>
X-Mailer: exmh version 2.0gamma 1/27/96
To: Michael Robinson <robinson@netrinsics.com>
Cc: freebsd-stable@FreeBSD.ORG
From: Dmitrij Tejblum <tejblum@arc.hq.cti.ru>
Subject: Re: Multi-byte locales 
In-reply-to: Your message of "Sun, 04 Jul 1999 11:31:50 +0800."
             <199907040331.LAA02964@netrinsics.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sun, 04 Jul 1999 15:13:52 +0400
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Michael Robinson wrote:
> On a -STABLE system (3.2-PAO kernel), every call to setlocale(LC_CTYPE, "<CJK>")
> returns with an error, where <CJK> is one of:
> 
> ja_JP.EUC
> ja_JP.SJIS
> ko_KR.EUC
> zh_CN.EUC
> zh_TW.BIG5

If you link your program with -lxpg4, the CJK locales may work better.

> All single-byte locales work fine.

You are optimist :-|.

Dima




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul  4  6:43: 2 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from cr575310-a.shprd1.on.wave.home.com (cr575310-a.shprd1.on.wave.home.com [24.112.185.167])
	by hub.freebsd.org (Postfix) with SMTP id 236F514C36
	for <freebsd-stable@freebsd.org>; Sun,  4 Jul 1999 06:42:55 -0700 (PDT)
	(envelope-from dark@idiotswitch.org)
Received: (qmail 9941 invoked from network); 4 Jul 1999 09:42:06 -0000
Received: from unknown (HELO a11.idiotswitch.org) (10.0.0.11)
  by 10.0.0.1 with SMTP; 4 Jul 1999 09:42:06 -0000
From: Rod Taylor <dark@idiotswitch.org>
To: freebsd-stable@freebsd.org
Subject: Huge Problem
Date: Sun, 4 Jul 1999 09:36:07 +0000
X-Mailer: KMail [version 1.0.21]
Content-Type: Multipart/Mixed;
  boundary="Boundary-=_WfAZyzAZOHsNGHcxSfUBSnsNWfUJ"
MIME-Version: 1.0
Message-Id: <99070409451500.00294@a11.idiotswitch.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


--Boundary-=_WfAZyzAZOHsNGHcxSfUBSnsNWfUJ
Content-Type: text/plain
Content-Transfer-Encoding: 8bit

Around 2 weeks ago I started running into problems.  This followed changing the
default login.conf to something a little more limiting for users.  

My server (2 FreeBSD clients with several NFS mounts) goes down atleast once a
day, normally during the night.  Unless of course I stay up for most of the
night with a bunch of stats windows open to see if I can catch the problem.  
The system will either reboot, or it will lock up completely (network,
keyboard, and display).

I'm running stable as of yesterday, and it continues to happen.  I can't see
anything obvious in login.conf that would cause this.  Twice I've had it lock
up 5 minutes after booting, sometimes it lasts 48 hours.

Are there any known problems which could cause this?

I personally think it's just coincidental that the file was changed before the
crashing started happening.  But it's attached anyway, as is my DMesg output. 
Ignore the labelling stuff.  It's been like that for a year now, and I haven't
figured out how to relabel something without having to boot with a bsd floppy. 
(No floppy drive here).

Thanks!

--
The early cat gets the bird if the early dog hasn't already eaten it. 
--

Rod Taylor


--Boundary-=_WfAZyzAZOHsNGHcxSfUBSnsNWfUJ
Content-Type: text/x-c++;
  name="login.conf"
Content-Transfer-Encoding: base64
Content-Description: My Login.Conf File
Content-Disposition: attachment; filename="login.conf"

IyBTYW1wbGUgbG9naW4uY29uZiAtIGxvZ2luIGNsYXNzIGNhcGFiaWxpdGllcyBkYXRhYmFzZS4K
IyBUbyBzcGVlZCB1cCBhY2Nlc3MgdG8gdGhpcyBkYXRhLCB5b3UgY2FuIHVzZSAvdXNyL2Jpbi9j
YXBfbWtkYgojIHRvIGNyZWF0ZSBhIGRhdGFiYXNlIGZvcm0gb2YgdGhpcyBmaWxlOgojCiMJY2Fw
X21rZGIgL2V0Yy9sb2dpbi5jb25mCiMKIyBEb24ndCBmb3JnZXQgdG8gZG8gdGhpcyBhZnRlciBl
YWNoIGVkaXQgYXMgd2VsbCEKIwojIFRoaXMgZmlsZSBjb250cm9scyByZXNvdXJjZSBsaW1pdHMs
IGFjY291bnRpbmcgbGltaXRzIGFuZAojIGRlZmF1bHQgdXNlciBlbnZpcm9ubWVudCBzZXR0aW5n
cy4KIwojCSRJZDogbG9naW4uY29uZix2IDEuOS4yLjcgMTk5OC8wMy8wOSAwMzowMzoyMyBzdGV2
ZSBFeHAgJAojCgoKIyBBdXRoZW50aWNhdGlvbiBtZXRob2RzCgphdXRoLWRlZmF1bHRzOlwKCTph
dXRoPWtyYl9za2V5X29yX3Bhc3N3ZCxwYXNzd2Qsa2VyYmVyb3Msc2tleToKCmF1dGgtcm9vdC1k
ZWZhdWx0czpcCgk6YXV0aC1sb2dpbj1rcmJfc2tleV9vcl9wYXNzd2QscGFzc3dkLGtlcmJlcm9z
LHNrZXk6XAoJOmF1dGgtcmxvZ2luPWtyYl9vcl9za2V5LGtlcmJlcm9zLHNrZXk6CgphdXRoLWZ0
cC1kZWZhdWx0czpcCgk6YXV0aD1za2V5X29yX3B3ZCxwYXNzd2Qsc2tleToKCgojIEV4YW1wbGUg
ZGVmYXVsdHMKIyBUaGVzZSBzZXR0aW5ncyBhcmUgdXNlZCBieSBsb2dpbigxKSBieSBkZWZhdWx0
IGZvciBjbGFzc2xlc3MgdXNlcnMKIyBOb3RlIHRoYXQgZW50cmllcyBsaWtlICJjcHV0aW1lIiBz
ZXQgYm90aCAiY3B1dGltZS1jdXIiIGFuZCAiY3B1dGltZS1tYXgiCgpkZWZhdWx0OlwKCTpjb3B5
cmlnaHQ9L2V0Yy9DT1BZUklHSFQ6XAoJOndlbGNvbWU9L2V0Yy9tb3RkOlwKCTpzZXRlbnY9TUFJ
TD0vdmFyL21haWwvJCxCTE9DS1NJWkU9SyxFRElUT1I9L3Vzci9iaW4vZWU6XAoJOnBhdGg9fi9i
aW4gL2JpbiAvdXNyL2JpbiAvdXNyL2xvY2FsL2JpbjpcCgk6bWFucGF0aD0vdXNyL3NoYXJlL21h
biAvdXNyL2xvY2FsL21hbiAvdXNyL1gxMVI2L21hbjpcCgk6bm9sb2dpbj0vZXRjL25vbG9naW46
XAoJOmNwdXRpbWU9aW5maW5pdHk6XAoJOmRhdGFzaXplPWluZmluaXR5OlwKCTpzdGFja3NpemU9
aW5maW5pdHk6XAoJOm1lbW9yeWxvY2tlZD00TTpcCgk6bWVtb3J5dXNlPWluZmluaXR5OlwKCTpm
aWxlc2l6ZT1pbmZpbml0eTpcCgk6Y29yZWR1bXBzaXplPTBNOlwKCTpwcmlvcml0eT0wOlwKCTpy
ZXF1aXJlaG9tZTpcCgk6cGFzc3dvcmRwZXJpb2Q9OTBkOlwKCTp1bWFzaz0wMDI6XAoJOmlnbm9y
ZXRpbWVAOlwKCTptYXhwcm9jPWluZmluaXR5OlwKCTpvcGVuZmlsZXM9aW5maW5pdHk6XAoJOmlk
bGV0aW1lPTMwbTpcCgk6YXV0aD10Yy1kZWZhdWx0czoKCiMKIyBzdGFuZGFyZCAtIHN0YW5kYXJk
IHVzZXIgZGVmYXVsdHMKIwpzdGFuZGFyZDpcCgk6Y29weXJpZ2h0PS9ldGMvQ09QWVJJR0hUOlwK
CTp3ZWxjb21lPS9ldGMvbW90ZDpcCgk6c2V0ZW52PU1BSUw9L3Zhci9tYWlsLyQsQkxPQ0tTSVpF
PUssRURJVE9SPS91c3IvYmluL2VlOlwKCTpwYXRoPX4vYmluIC9iaW4gL3Vzci9iaW4gL3Vzci9s
b2NhbC9iaW4gfi9zYmluIC9zYmluIC91c3Ivc2JpbiAvdXNyL2xvY2FsL3NiaW46XCAKCTptYW5w
YXRoPS91c3Ivc2hhcmUvbWFuIC91c3IvbG9jYWwvbWFuIC91c3IvWDExUjYvbWFuOlwKCTpub2xv
Z2luPS9ldGMvbm9sb2dpbjpcCgk6ZGF0YXNpemU9MzJNOlwKCTpzdGFja3NpemU9NE06XAoJOm1l
bW9yeWxvY2tlZD04TTpcCgk6bWVtb3J5dXNlPTE2TTpcCgk6ZmlsZXNpemU9MjBNOlwKCTpjb3Jl
ZHVtcHNpemU9ME06XAoJOnJlcXVpcmVob21lOlwKCTpwYXNzd29yZHBlcmlvZD05MGQ6XAoJOnVt
YXNrPTAwMjpcCgk6aWRsZXRpbWU9MzBtOlwKCTphdXRoPXRjLWRlZmF1bHRzOgojCiMgc2hlbGwg
dXNlcnMKIwpzaGVsbDpcCgk6Y3B1dGltZT01MG06XAoJOnByaW9yaXR5PTU6XAoJOm1heHByb2M9
NjpcCgk6b3BlbmZpbGVzPTEyOlwKCTp0Yz1zdGFuZGFyZDoKCnByaXZpbGFnZWQ6XAoJOmNwdXRp
bWU9MWgyMG06XAoJOnByaW9yaXR5PTM6XAoJOm1heHByb2M9MTI6XAoJOm9wZW5maWxlcz0yNDpc
Cgk6dGM9c3RhbmRhcmQ6CiMKIyB1c2VycyBvZiBYIChuZWVkcyBtb3JlIHJlc291cmNlcyEpCiMK
eHVzZXI6XAoJOmNwdXRpbWU9NGg6XAoJOm9wZW5maWxlcz0zMjpcCgk6bWF4cHJvYz0yNDpcCgk6
cHJpb3JpdHk9NzpcCgk6dGM9c3RhbmRhcmQ6CgoKIwojIFN0YWZmIHVzZXJzIC0gZmV3IHJlc3Ry
aWN0aW9ucyBhbmQgYWxsb3cgbG9naW4gYW55dGltZQojCnN0YWZmOlwKCTppZ25vcmVub2xvZ2lu
OlwKCTppZ25vcmV0aW1lOlwKCTpyZXF1aXJlaG9tZUA6XAoJOmFjY291bnRlZEA6XAoJOnRjPXN0
YW5kYXJkOgoKCiMKIyByb290IC0gZmFsbGJhY2sgZm9yIHJvb3QgbG9naW5zCiMKcm9vdDpcCgk6
cGF0aD1+L2JpbiAvYmluIC9zYmluIC91c3IvYmluIC91c3Ivc2JpbiAvdXNyL2xvY2FsL2JpbiAv
dXNyL2xvY2FsL3NiaW46XAoJOmNwdXRpbWU9aW5maW5pdHk6XAoJOmRhdGFzaXplPWluZmluaXR5
OlwKCTpzdGFja3NpemU9aW5maW5pdHk6XAoJOm1lbW9yeWxvY2tlZD1pbmZpbml0eTpcCgk6bWVt
b3J5dXNlPWluZmluaXR5OlwKCTpmaWxlc2l6ZT1pbmZpbml0eTpcCgk6Y29yZWR1bXBzaXplPWlu
ZmluaXR5OlwKCTpvcGVuZmlsZXM9aW5maW5pdHk6XAoJOm1heHByb2M9aW5maW5pdHk6XAoJOm1l
bW9yeXVzZS1jdXI9MzJNOlwKCTptYXhwcm9jLWN1cj02NDpcCgk6b3BlbmZpbGVzLWN1cj0xMDI0
OlwKCTpwcmlvcml0eT0wOlwKCTpyZXF1aXJlaG9tZUA6XAoJOnVtYXNrPTAyMjpcCgk6dGM9YXV0
aC1yb290LWRlZmF1bHRzOgoKbm9ib2R5OlwKCTpjcHV0aW1lPWluZmluaXR5OlwKICAgICAgICA6
ZGF0YXNpemU9aW5maW5pdHk6XAoJOnRjPWRlZmF1bHQ6CgojCiMgU2V0dGluZ3MgdXNlZCBieSAv
ZXRjL3JjCiMKZGFlbW9uOlwKCTpjb3JlZHVtcHNpemVAOlwKCTpjb3JlZHVtcHNpemUtY3VyPTA6
XAoJOmRhdGFzaXplPWluZmluaXR5OlwKCTpkYXRhc2l6ZS1jdXJAOlwKCTptYXhwcm9jPTUxMjpc
Cgk6bWF4cHJvYy1jdXJAOlwKCTptZW1vcnl1c2UtY3VyPTY0TTpcCgk6bWVtb3J5bG9ja2VkLWN1
cj02NE06XAoJOm9wZW5maWxlcz0xMDI0OlwKCTpvcGVuZmlsZXMtY3VyQDpcCgk6c3RhY2tzaXpl
PTE2TTpcCgk6c3RhY2tzaXplLWN1ckA6XAoJOnRjPWRlZmF1bHQ6Cgo=

--Boundary-=_WfAZyzAZOHsNGHcxSfUBSnsNWfUJ
Content-Type: text/english;
  name="dmesg"
Content-Transfer-Encoding: base64
Content-Description: Dmesg
Content-Disposition: attachment; filename="dmesg"

Q29weXJpZ2h0IChjKSAxOTkyLTE5OTkgRnJlZUJTRCBJbmMuCkNvcHlyaWdodCAoYykgMTk4Miwg
MTk4NiwgMTk4OSwgMTk5MSwgMTk5MwoJVGhlIFJlZ2VudHMgb2YgdGhlIFVuaXZlcnNpdHkgb2Yg
Q2FsaWZvcm5pYS4gQWxsIHJpZ2h0cyByZXNlcnZlZC4KRnJlZUJTRCAzLjItU1RBQkxFICM4OiBU
aHUgSnVsICAxIDE5OjU1OjAyIEdNVCAxOTk5CiAgICByb290QHd3dy5pZGlvdHN3aXRjaC5vcmc6
L3Vzci9zcmMvc3lzL2NvbXBpbGUvQ0VOVFJBTApUaW1lY291bnRlciAiaTgyNTQiICBmcmVxdWVu
Y3kgMTE5MzE4MiBIegpDUFU6IFBlbnRpdW0vUDU1QyAoMTY2LjQwLU1IeiA1ODYtY2xhc3MgQ1BV
KQogIE9yaWdpbiA9ICJHZW51aW5lSW50ZWwiICBJZCA9IDB4NTQzICBTdGVwcGluZz0zCiAgRmVh
dHVyZXM9MHg4MDAxYmY8RlBVLFZNRSxERSxQU0UsVFNDLE1TUixNQ0UsQ1g4LE1NWD4KcmVhbCBt
ZW1vcnkgID0gNjcxMDg4NjQgKDY1NTM2SyBieXRlcykKYXZhaWwgbWVtb3J5ID0gNjE2NjExODQg
KDYwMjE2SyBieXRlcykKUHJlbG9hZGVkIGVsZiBrZXJuZWwgImtlcm5lbCIgYXQgMHhjMDM0ZjAw
MC4KUHJvYmluZyBmb3IgZGV2aWNlcyBvbiBQQ0kgYnVzIDA6CmNoaXAwOiA8SW50ZWwgODI0MzlU
WCBTeXN0ZW0gQ29udHJvbGxlciAoTVRYQyk+IHJldiAweDAxIG9uIHBjaTAuMC4wCmNoaXAxOiA8
SW50ZWwgODIzNzFBQiBQQ0kgdG8gSVNBIGJyaWRnZT4gcmV2IDB4MDEgb24gcGNpMC43LjAKaWRl
X3BjaTA6IDxJbnRlbCBQSUlYNCBCdXMtbWFzdGVyIElERSBjb250cm9sbGVyPiByZXYgMHgwMSBv
biBwY2kwLjcuMQpjaGlwMjogPEludGVsIDgyMzcxQUIgUG93ZXIgbWFuYWdlbWVudCBjb250cm9s
bGVyPiByZXYgMHgwMSBvbiBwY2kwLjcuMwp2Z2EwOiA8U2lTIG1vZGVsIDAyMDQgVkdBLWNvbXBh
dGlibGUgZGlzcGxheSBkZXZpY2U+IHJldiAweDIxIG9uIHBjaTAuOC4wCnhsMDogPDNDb20gM2M5
MDVCLVRYIEZhc3QgRXRoZXJsaW5rIFhMPiByZXYgMHgzMCBpbnQgYSBpcnEgOSBvbiBwY2kwLjku
MAp4bDA6IEV0aGVybmV0IGFkZHJlc3M6IDAwOjUwOjA0OjExOjVmOjE2CnhsMDogYXV0b25lZyBj
b21wbGV0ZSwgbGluayBzdGF0dXMgZ29vZCAoaGFsZi1kdXBsZXgsIDEwME1icHMpCmVkMTogPE5F
MjAwMCBQQ0kgRXRoZXJuZXQgKFJlYWxUZWsgODAyOSk+IHJldiAweDAwIGludCBhIGlycSAxMSBv
biBwY2kwLjEwLjAKZWQxOiBhZGRyZXNzIDAwOjgwOmM4OmYzOjFkOjEyLCB0eXBlIE5FMjAwMCAo
MTYgYml0KSAKUHJvYmluZyBmb3IgZGV2aWNlcyBvbiB0aGUgSVNBIGJ1czoKc2MwIG9uIGlzYQpz
YzA6IFZHQSBjb2xvciA8MTYgdmlydHVhbCBjb25zb2xlcywgZmxhZ3M9MHgwPgplZDAgbm90IGZv
dW5kIGF0IDB4MjgwCmF0a2JkYzAgYXQgMHg2MC0weDZmIG9uIG1vdGhlcmJvYXJkCmF0a2JkMCBp
cnEgMSBvbiBpc2EKcHNtMCBub3QgZm91bmQKc2lvMCBhdCAweDNmOC0weDNmZiBpcnEgNCBmbGFn
cyAweDEwIG9uIGlzYQpzaW8wOiB0eXBlIDE2NTUwQQpzaW8xIGF0IDB4MmY4LTB4MmZmIGlycSAz
IG9uIGlzYQpzaW8xOiB0eXBlIDE2NTUwQQpmZGMwIGF0IDB4M2YwLTB4M2Y3IGlycSA2IGRycSAy
IG9uIGlzYQp3ZGMwIGF0IDB4MWYwLTB4MWY3IGlycSAxNCBvbiBpc2EKd2RjMDogdW5pdCAwICh3
ZDApOiA8SUJNLURUVEEtMzUxMDEwPgp3ZDA6IDk2NzFNQiAoMTk4MDcyMDAgc2VjdG9ycyksIDE5
NjUwIGN5bHMsIDE2IGhlYWRzLCA2MyBTL1QsIDUxMiBCL1MKd2RjMDogdW5pdCAxICh3ZDEpOiA8
U0FNU1VORyBWRzM4NDA0QT4Kd2QxOiA4MDU2TUIgKDE2NDk4OTQ0IHNlY3RvcnMpLCAxNjM2OCBj
eWxzLCAxNiBoZWFkcywgNjMgUy9ULCA1MTIgQi9TCndkYzEgbm90IGZvdW5kIGF0IDB4MTcwCnd0
MCBub3QgZm91bmQgYXQgMHgzMDAKbWNkMCBub3QgZm91bmQgYXQgMHgzMDAKbWF0Y2RjMCBub3Qg
Zm91bmQgYXQgMHgyMzAKc2NkMCBub3QgZm91bmQgYXQgMHgyMzAKcHBjMCBhdCAweDI3OCBpcnEg
NyBmbGFncyAweDQwIG9uIGlzYQpwcGMwOiBHZW5lcmljIGNoaXBzZXQgKE5JQkJMRS1vbmx5KSBp
biBDT01QQVRJQkxFIG1vZGUKbHB0MDogPGdlbmVyaWMgcHJpbnRlcj4gb24gcHBidXMgMApscHQw
OiBJbnRlcnJ1cHQtZHJpdmVuIHBvcnQKcHBpMDogPGdlbmVyaWMgcGFyYWxsZWwgaS9vPiBvbiBw
cGJ1cyAwCnBsaXAwOiA8UExJUCBuZXR3b3JrIGludGVyZmFjZT4gb24gcHBidXMgMAphZHYwIG5v
dCBmb3VuZCBhdCAweDMzMApidF9pc2FfcHJvYmU6IFByb2JlIGZhaWxlZCBmb3IgY2FyZCBhdCAw
eDMzMApidF9pc2FfcHJvYmU6IFByb2JlIGZhaWxlZCBmb3IgY2FyZCBhdCAweDMzNApidF9pc2Ff
cHJvYmU6IFByb2JlIGZhaWxlZCBmb3IgY2FyZCBhdCAweDIzMApidF9pc2FfcHJvYmU6IFByb2Jl
IGZhaWxlZCBmb3IgY2FyZCBhdCAweDIzNApidF9pc2FfcHJvYmU6IFByb2JlIGZhaWxlZCBmb3Ig
Y2FyZCBhdCAweDEzMApidF9pc2FfcHJvYmU6IFByb2JlIGZhaWxlZCBmb3IgY2FyZCBhdCAweDEz
NApidDAgbm90IGZvdW5kIGF0IDB4MTM0CmFoYTAgbm90IGZvdW5kIGF0IDB4MTM0CnZnYTAgYXQg
MHgzYjAtMHgzZGYgbWFkZHIgMHhhMDAwMCBtc2l6ZSAxMzEwNzIgb24gaXNhCm5weDAgb24gbW90
aGVyYm9hcmQKbnB4MDogSU5UIDE2IGludGVyZmFjZQpJbnRlbCBQZW50aXVtIGRldGVjdGVkLCBp
bnN0YWxsaW5nIHdvcmthcm91bmQgZm9yIEYwMEYgYnVnCklQIHBhY2tldCBmaWx0ZXJpbmcgaW5p
dGlhbGl6ZWQsIGRpdmVydCBlbmFibGVkLCBydWxlLWJhc2VkIGZvcndhcmRpbmcgZGlzYWJsZWQs
IGRlZmF1bHQgdG8gYWNjZXB0LCBsb2dnaW5nIGRpc2FibGVkCklQIEZpbHRlcjogaW5pdGlhbGl6
ZWQuICBEZWZhdWx0ID0gcGFzcyBhbGwsIExvZ2dpbmcgPSBkaXNhYmxlZApjaGFuZ2luZyByb290
IGRldmljZSB0byB3ZDBzMmEKd2QwOiBjYW5ub3QgZmluZCBsYWJlbCAobm8gZGlzayBsYWJlbCkK
d2QwczE6IGNhbm5vdCBmaW5kIGxhYmVsIChubyBkaXNrIGxhYmVsKQpXQVJOSU5HOiAvIHdhcyBu
b3QgcHJvcGVybHkgZGlzbW91bnRlZAp3ZDA6IGNhbm5vdCBmaW5kIGxhYmVsIChubyBkaXNrIGxh
YmVsKQp3ZDBzMTogY2Fubm90IGZpbmQgbGFiZWwgKG5vIGRpc2sgbGFiZWwpCndkMDogY2Fubm90
IGZpbmQgbGFiZWwgKG5vIGRpc2sgbGFiZWwpCndkMHMxOiBjYW5ub3QgZmluZCBsYWJlbCAobm8g
ZGlzayBsYWJlbCkKd2QwOiBjYW5ub3QgZmluZCBsYWJlbCAobm8gZGlzayBsYWJlbCkKd2QwczE6
IGNhbm5vdCBmaW5kIGxhYmVsIChubyBkaXNrIGxhYmVsKQp3ZDA6IGNhbm5vdCBmaW5kIGxhYmVs
IChubyBkaXNrIGxhYmVsKQp3ZDBzMTogY2Fubm90IGZpbmQgbGFiZWwgKG5vIGRpc2sgbGFiZWwp
CndkMDogY2Fubm90IGZpbmQgbGFiZWwgKG5vIGRpc2sgbGFiZWwpCndkMHMxOiBjYW5ub3QgZmlu
ZCBsYWJlbCAobm8gZGlzayBsYWJlbCkKd2QwOiBjYW5ub3QgZmluZCBsYWJlbCAobm8gZGlzayBs
YWJlbCkKd2QwczE6IGNhbm5vdCBmaW5kIGxhYmVsIChubyBkaXNrIGxhYmVsKQp3ZDA6IGNhbm5v
dCBmaW5kIGxhYmVsIChubyBkaXNrIGxhYmVsKQp3ZDBzMTogY2Fubm90IGZpbmQgbGFiZWwgKG5v
IGRpc2sgbGFiZWwpCndkMDogY2Fubm90IGZpbmQgbGFiZWwgKG5vIGRpc2sgbGFiZWwpCndkMHMx
OiBjYW5ub3QgZmluZCBsYWJlbCAobm8gZGlzayBsYWJlbCkKd2QwOiBjYW5ub3QgZmluZCBsYWJl
bCAobm8gZGlzayBsYWJlbCkKd2QwczE6IGNhbm5vdCBmaW5kIGxhYmVsIChubyBkaXNrIGxhYmVs
KQo=

--Boundary-=_WfAZyzAZOHsNGHcxSfUBSnsNWfUJ--


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul  4 10:21:41 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1])
	by hub.freebsd.org (Postfix) with ESMTP id 2CA0214CAF
	for <stable@FreeBSD.ORG>; Sun,  4 Jul 1999 10:21:39 -0700 (PDT)
	(envelope-from cdillon@wolves.k12.mo.us)
Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1])
	by mail.wolves.k12.mo.us (8.9.3/8.9.2) with ESMTP id MAA66062;
	Sun, 4 Jul 1999 12:21:10 -0500 (CDT)
	(envelope-from cdillon@wolves.k12.mo.us)
Date: Sun, 4 Jul 1999 12:21:10 -0500 (CDT)
From: Chris Dillon <cdillon@wolves.k12.mo.us>
To: Mike Smith <mike@smith.net.au>
Cc: Marcel Moolenaar <marcel@scc.nl>, stable@FreeBSD.ORG
Subject: Re: Linux emulation 
In-Reply-To: <199907040057.RAA02543@dingo.cdrom.com>
Message-ID: <Pine.BSF.4.10.9907041220020.66035-100000@mail.wolves.k12.mo.us>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, 3 Jul 1999, Mike Smith wrote:

> > 
> > In the event that messing with /etc/rc.serial does the trick, does
> > anyone know of any ports that modify anything in /etc to use as an
> > example?  I'm not so sure that is an acceptable thing for a port to
> > do, but if it is, it would make things a lot easier.
> 
> Don't.  You're writing a daemon, so you'll have a shellscript in 
> /usr/local/etc/rc.d.  Everything that rc.serial does can be done by 
> your shellscript...

After I looked at rc.serial I noticed that.  Thanks!


-- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net
   FreeBSD: The fastest and most stable server OS on the planet.
   For Intel x86 and Alpha architectures (SPARC under development).
   ( http://www.freebsd.org )

   "One should admire Windows users.  It takes a great deal of
    courage to trust Windows with your data."



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul  4 11:17:34 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by hub.freebsd.org (Postfix) with ESMTP id E0DD914EF9
	for <freebsd-stable@freebsd.org>; Sun,  4 Jul 1999 11:17:32 -0700 (PDT)
	(envelope-from randy@psg.com)
Received: from localhost (1010 bytes) by rip.psg.com
	via sendmail with P:stdio/R:inet_resolve/T:smtp
	(sender: <randy>) (ident <randy> using unix)
	id <m110qpX-0008G4C@rip.psg.com>
	for <freebsd-stable@freebsd.org>; Sun, 4 Jul 1999 11:17:31 -0700 (PDT)
	(Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1)
Message-Id: <m110qpX-0008G4C@rip.psg.com>
Date: Sun, 4 Jul 1999 11:17:31 -0700 (PDT)
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Randall Hopper <aa8vb@ipass.net>
Cc: FreeBSD Stable <freebsd-stable@freebsd.org>
Subject: Re: Splash Screens (was Re: 3.2-RELEASE Feedback)
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

so, i hacked my /boot/loader.conf.local to be

    splash_bmp_load="YES"
    vesa_load="YES"
    bitmap_load="YES"
    bitmap_name="/boot/splash.bmp"
    bitmap_type="splash_image_data"

install a 1024x768 /boot/spalsh.bmp

but i get

    Preloaded elf kernel "kernel" at 0xc04df000.
    Preloaded elf module "splash_bmp.ko" at 0xc04df09c.
    Preloaded elf module "vesa.ko" at 0xc04df140.
    link_elf: symbol vm86_intcall undefined
    Preloaded splash_image_data "/boot/splash.bmp" at 0xc04df1dc.
    module_register_init: module_register(splash_bmp, c0295624, 0) error 19
    Probing for devices on PCI bus 0:

and no spash, of course.

3.2-stable+pao
vaio 505tx

randy


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul  4 11:25:13 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5])
	by hub.freebsd.org (Postfix) with ESMTP id D28EF14D6A
	for <freebsd-stable@freebsd.org>; Sun,  4 Jul 1999 11:25:10 -0700 (PDT)
	(envelope-from rhh@ipass.net)
Received: from stealth.ipass.net. (ppp-1-149.dialup.rdu.ipass.net [209.170.132.149])
	by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id OAA20863;
	Sun, 4 Jul 1999 14:25:07 -0400 (EDT)
Received: (from rhh@localhost)
	by stealth.ipass.net. (8.9.3/8.8.8) id OAA02467;
	Sun, 4 Jul 1999 14:27:03 -0400 (EDT)
	(envelope-from rhh)
Date: Sun, 4 Jul 1999 14:27:03 -0400
From: Randall Hopper <aa8vb@ipass.net>
To: Randy Bush <randy@psg.com>
Cc: FreeBSD Stable <freebsd-stable@freebsd.org>
Subject: Re: Splash Screens (was Re: 3.2-RELEASE Feedback)
Message-ID: <19990704142703.A2153@ipass.net>
References: <m110qpX-0008G4C@rip.psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <m110qpX-0008G4C@rip.psg.com>; from Randy Bush on Sun, Jul 04, 1999 at 11:17:31AM -0700
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Randy Bush:
 |so, i hacked my /boot/loader.conf.local to be
 |
 |    splash_bmp_load="YES"
 |    vesa_load="YES"
 |    bitmap_load="YES"
 |    bitmap_name="/boot/splash.bmp"
 |    bitmap_type="splash_image_data"
 |
 |install a 1024x768 /boot/spalsh.bmp
                           ^^^^^^

I assume this is just a typo (?)

 |and no spash, of course.
 |
 |3.2-stable+pao
 |vaio 505tx

Splash wise, you have everything I do, though I'm using PCX.  Maybe splash
doesn't grok that BMP:

     splash_bmp.ko   W*ndows BMP file decoder.  While the BMP file format al-
                     lows images of various color depths, this decoder cur-
                     rently only handles 256 color bitmaps.  Bitmaps of other
                     color depths will not be displayed.

Randall


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul  4 11:46:17 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31])
	by hub.freebsd.org (Postfix) with ESMTP id EB50D14D08
	for <freebsd-stable@FreeBSD.ORG>; Sun,  4 Jul 1999 11:46:13 -0700 (PDT)
	(envelope-from des@flood.ping.uio.no)
Received: (from des@localhost)
	by flood.ping.uio.no (8.9.3/8.9.1) id UAA91909;
	Sun, 4 Jul 1999 20:46:10 +0200 (CEST)
	(envelope-from des)
To: Randy Bush <randy@psg.com>
Cc: Randall Hopper <aa8vb@ipass.net>,
	FreeBSD Stable <freebsd-stable@FreeBSD.ORG>
Subject: Re: Splash Screens (was Re: 3.2-RELEASE Feedback)
References: <m110qpX-0008G4C@rip.psg.com>
From: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Date: 04 Jul 1999 20:46:09 +0200
In-Reply-To: Randy Bush's message of "Sun, 4 Jul 1999 11:17:31 -0700 (PDT)"
Message-ID: <xzp1zeow8we.fsf@flood.ping.uio.no>
Lines: 14
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Randy Bush <randy@psg.com> writes:
>     Preloaded elf kernel "kernel" at 0xc04df000.
>     Preloaded elf module "splash_bmp.ko" at 0xc04df09c.
>     Preloaded elf module "vesa.ko" at 0xc04df140.
>     link_elf: symbol vm86_intcall undefined
>     Preloaded splash_image_data "/boot/splash.bmp" at 0xc04df1dc.
>     module_register_init: module_register(splash_bmp, c0295624, 0) error 19
>     Probing for devices on PCI bus 0:

RTFM vesa. Clue on line four above.

DES
-- 
Dag-Erling Smorgrav - des@flood.ping.uio.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul  4 12: 6:47 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [134.102.38.17])
	by hub.freebsd.org (Postfix) with ESMTP id 586D414EA2
	for <freebsd-stable@freebsd.org>; Sun,  4 Jul 1999 12:06:42 -0700 (PDT)
	(envelope-from nox@saturn.kn-bremen.de)
Received: from saturn.kn-bremen.de (uucp@localhost)
	by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id VAA31680;
	Sun, 4 Jul 1999 21:03:51 +0200
Received: (from nox@localhost)
	by saturn.kn-bremen.de (8.9.3/8.8.5) id UAA23493;
	Sun, 4 Jul 1999 20:28:34 +0200 (MET DST)
Date: Sun, 4 Jul 1999 20:28:34 +0200 (MET DST)
From: Juergen Lock <nox@jelal.kn-bremen.de>
Message-Id: <199907041828.UAA23493@saturn.kn-bremen.de>
To: wilko@yedi.iaf.nl
Cc: freebsd-stable@freebsd.org
Subject: Re: Is the CD driver supposed to attach() now regardless of media?
X-Newsgroups: local.list.freebsd.stable
In-Reply-To: <199906131005.MAA72055@yedi.iaf.nl>
References: <19990612234414.E17731@paert.tse-online.de>
Organization: home
Cc: 
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In article <199906131005.MAA72055@yedi.iaf.nl> you write:
>As Andreas Braukmann wrote ...

>> The 3.1-release installation kernel wasn't able to attach
>> the yamaha drive to cd0.
>
>Maybe the Yamaha, being a CDRW drive does not report itself as a CD after
>boot/SCSI bus reset? Just guessing here..

I only saw this now so sorry for the late answer...

 My Yamaha 4416S reports itself as a CD, did so with firmware 1.0f and now
does with 1.0g.  If i try to mount a CD in it while its still reading the
TOC (which takes a while, left LED flashing green), the mount command just
waits until the LED stops flashing, then mounts it as it should be.  So if
sysinstall is simply using a `normal' mount it *should* not have any
problems?  this is on 3.2-stable.

 HTH,
-- 
Juergen Lock <nox.foo@jelal.kn-bremen.de>
(remove dot foo from address to reply)


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul  4 12:37:19 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from rip.psg.com (rip.psg.com [147.28.0.39])
	by hub.freebsd.org (Postfix) with ESMTP id CDD4A150DC
	for <freebsd-stable@FreeBSD.ORG>; Sun,  4 Jul 1999 12:37:16 -0700 (PDT)
	(envelope-from randy@psg.com)
Received: from localhost (970 bytes) by rip.psg.com
	via sendmail with P:stdio/R:inet_resolve/T:smtp
	(sender: <randy>) (ident <randy> using unix)
	id <m110s4f-0008G4C@rip.psg.com>
	for <freebsd-stable@FreeBSD.ORG>; Sun, 4 Jul 1999 12:37:13 -0700 (PDT)
	(Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1)
Message-Id: <m110s4f-0008G4C@rip.psg.com>
Date: Sun, 4 Jul 1999 12:37:13 -0700 (PDT)
From: Randy Bush <randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Cc: Randall Hopper <aa8vb@ipass.net>,
	FreeBSD Stable <freebsd-stable@FreeBSD.ORG>
Subject: Re: Splash Screens (was Re: 3.2-RELEASE Feedback)
References: <m110qpX-0008G4C@rip.psg.com>
	<xzp1zeow8we.fsf@flood.ping.uio.no>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>     Preloaded elf kernel "kernel" at 0xc04df000.
>>     Preloaded elf module "splash_bmp.ko" at 0xc04df09c.
>>     Preloaded elf module "vesa.ko" at 0xc04df140.
>>     link_elf: symbol vm86_intcall undefined
>>     Preloaded splash_image_data "/boot/splash.bmp" at 0xc04df1dc.
>>     module_register_init: module_register(splash_bmp, c0295624, 0) error 19
>>     Probing for devices on PCI bus 0:
> RTFM vesa. Clue on line four above.

<doh>

building new kernel with vesa and vm86 now.

thanks.

randy


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul  4 14: 8:17 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from mercury.webnology.com (mercury.webnology.com [209.155.51.2])
	by hub.freebsd.org (Postfix) with ESMTP id 4977114D00
	for <freebsd-stable@freebsd.org>; Sun,  4 Jul 1999 14:08:14 -0700 (PDT)
	(envelope-from jooji@webnology.com)
Received: from localhost (jooji@localhost)
	by mercury.webnology.com (8.9.2/8.9.2) with SMTP id PAA04732
	for <freebsd-stable@freebsd.org>; Sun, 4 Jul 1999 15:10:36 -0500 (CDT)
Date: Sun, 4 Jul 1999 15:10:36 -0500 (CDT)
From: "Jasper O'Malley" <jooji@webnology.com>
To: freebsd-stable@freebsd.org
Subject: Re: ARP Problem? Need confirmation...
In-Reply-To: <19990703172751.A70755@mervyn.stade.co.uk>
Message-ID: <Pine.LNX.4.02.9907041508090.4687-100000@mercury.webnology.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Sat, 3 Jul 1999, Adrian Wontroba wrote:

> # arp -s 192.168.1.13 auto pub
> using interface ep0 for proxy with address 0:10:5a:ae:33:86
> arp: writing to routing socket: File exists
> 
> This is on a RELENG_3 box with a make world run on June 30th.

This is the second independent confirmation I've gotten for this bug. I've
tried to locate the offending code in the source tree, but it's beyond my
limited programming abilities, I'm afraid. Anyone have any ideas?

Cheers,
Mick

The Reverend Jasper P. O'Malley          dotdot:jooji@webnology.com
    Systems Administrator                  ringring:asktheadmiral
	Webnology, LLC               woowoo:http://www.webnology.com/~jooji



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul  4 15:28:12 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10])
	by hub.freebsd.org (Postfix) with ESMTP id 2BD9E14FB3
	for <freebsd-stable@FreeBSD.ORG>; Sun,  4 Jul 1999 15:28:06 -0700 (PDT)
	(envelope-from jeremyp@gsmx07.alcatel.com.au)
Received: by border.alcanet.com.au id <40334>; Mon, 5 Jul 1999 08:10:31 +1000
Date: Mon, 5 Jul 1999 08:27:59 +1000
From: Peter Jeremy <jeremyp@gsmx07.alcatel.com.au>
Subject: Re: MMX
In-reply-to: <377C84BF.33E147F2@cs.strath.ac.uk>
To: freebsd-stable@FreeBSD.ORG
Message-Id: <99Jul5.081031est.40334@border.alcanet.com.au>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Roger Hardiman <roger@cs.strath.ac.uk> wrote:
>Here is the almost proper way to determine if a CPU has MMX support.
>I say _alomost_ because it uses the CPU-ID instruction.
>This instruction is not on 386 machines or some early 486 machines.

The Intel 486 manual (that I have at home) includes `official' code
for determining what processor (8086 thru pre-CPUID 80486) you are
running on.  I'd suspect a later version would include testing for
the presence of CPUID.  I believe the code will run in user-mode.

That said, I think the correct approach is a hook to allow a user-mode
program to query the kernel (which has already determined what CPU
it's running on).  I'm not sure whether this should be an extension
of an existing syscall, or a sysctl variable.

Peter


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul  4 16: 3:56 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from yamuna.dalai-nor.de (yamuna.dalai-nor.de [194.231.227.71])
	by hub.freebsd.org (Postfix) with ESMTP id 376481517F
	for <freebsd-stable@FreeBSD.ORG>; Sun,  4 Jul 1999 16:03:45 -0700 (PDT)
	(envelope-from pruess@yamuna.dalai-nor.de)
Received: (from pruess@localhost)
          by yamuna.dalai-nor.de (8.8.7/8.8.5) id BAA16780;
          Mon, 5 Jul 1999 01:03:41 +0200 (CEST)
Message-Id: <199907042303.BAA16780@yamuna.dalai-nor.de>
Subject: double panic
To: freebsd-stable@FreeBSD.ORG
Date: Mon, 5 Jul 1999 01:03:41 +0200 (CEST)
Cc: pruess@yamuna.dalai-nor.de (G P)
From: "G.P." <G.P@chatcity.de>
Reply-To: G.P@chatcity.de
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi!
Since I am not use to join a newsgroup, please correct me if I
misbehave
(since I already posted a similiar message and nobody answered, maybe
I
already  did ...). I installed 19990630-SNAP (3.2) and 3.[12]-RELEASE.
All systems behave the same, but the following lines are tested only
on
3.2-RELEASE:

I used /usr/src/sys/i386/conf/GENERIC, copied it to CUSTOM, increased
maxusers to 512, compiled and installed the kernel. After boot, I
started
the following code as a simple user:

#include <unistd.h>
#include <sys/types.h>

int main(int argc, char *argv[])
{
pid_t p;

while ((p=fork())>0);
if (p==0) pause();
return(0);
}

The systems panics (double fault). I am not able to debug the core:
kernel symbol `gd_curpcb' not found.
No stack.


My configuration is as follows:
Asus P2B-LS (with IBM DGHS18U and DGHS09U attachted)
PII-450
512 MB ECC
Adaptec - 2940B UW (with IBM DGHS09U, PIONEER CD-ROM and HP C1533A
attachted)
ZNYX ZX34X with DEC 21140A
Intel EtherExpress Pro 10/100B Ethernet

Please help me!

Gunnar
--


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul  4 17: 4:39 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3])
	by hub.freebsd.org (Postfix) with SMTP id 2B3F815140
	for <freebsd-stable@freebsd.org>; Sun,  4 Jul 1999 17:04:36 -0700 (PDT)
	(envelope-from tom@uniserve.com)
Received: from shell.uniserve.ca [204.244.186.218] 
	by pop.uniserve.com with smtp (Exim 1.82 #4)
	id 110wFJ-0003a0-00; Sun, 4 Jul 1999 17:04:29 -0700
Date: Sun, 4 Jul 1999 17:04:26 -0700 (PDT)
From: Tom <tom@uniserve.com>
X-Sender: tom@shell.uniserve.ca
To: "G.P." <G.P@chatcity.de>
Cc: freebsd-stable@FreeBSD.ORG, G P <pruess@yamuna.dalai-nor.de>
Subject: Re: double panic
In-Reply-To: <199907042303.BAA16780@yamuna.dalai-nor.de>
Message-ID: <Pine.BSF.4.02A.9907041702340.8930-100000@shell.uniserve.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 5 Jul 1999, G.P. wrote:

> already  did ...). I installed 19990630-SNAP (3.2) and 3.[12]-RELEASE.
> All systems behave the same, but the following lines are tested only
> on
> 3.2-RELEASE:
> 
> I used /usr/src/sys/i386/conf/GENERIC, copied it to CUSTOM, increased
> maxusers to 512, compiled and installed the kernel. After boot, I

  maxusers > 128 can be troublesome.  Lower it to 128.

> started the following code as a simple user:

  "simple user"?  What is that?  "root"?

> 
> #include <unistd.h>
> #include <sys/types.h>
> 
> int main(int argc, char *argv[])
> {
> pid_t p;
> 
> while ((p=fork())>0);
> if (p==0) pause();
> return(0);
> }

  That just forks over and over again.

> The systems panics (double fault). I am not able to debug the core:
> kernel symbol `gd_curpcb' not found.
> No stack.

  You probably can't debug the core, because maxusers is so large.

Tom



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sun Jul  4 17:50:59 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from netrinsics.com (unknown [210.74.174.41])
	by hub.freebsd.org (Postfix) with ESMTP id D753714DA7
	for <freebsd-stable@FreeBSD.ORG>; Sun,  4 Jul 1999 17:50:33 -0700 (PDT)
	(envelope-from robinson@netrinsics.com)
Received: (from robinson@localhost)
	by netrinsics.com (8.9.3/8.8.7) id IAA03747;
	Mon, 5 Jul 1999 08:49:48 +0800 (CST)
	(envelope-from robinson)
Date: Mon, 5 Jul 1999 08:49:48 +0800 (CST)
From: Michael Robinson <robinson@netrinsics.com>
Message-Id: <199907050049.IAA03747@netrinsics.com>
To: tejblum@arc.hq.cti.ru
Subject: Re: Multi-byte locales
Cc: freebsd-stable@FreeBSD.ORG
In-Reply-To: <199907041113.PAA01808@tejblum.dnttm.rssi.ru>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Dmitrij Tejblum <tejblum@arc.hq.cti.ru> writes:
>If you link your program with -lxpg4, the CJK locales may work better.

Thanks.  This is indeed the case (actually, I just set LD_PRELOAD).  Maybe
a mention of libxpg4 in the "bugs" section of the setlocale man page would
be appropriate?

	-Michael Robinson



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul  5  2:29:34 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.swlct.sthames.nhs.uk (hide14.nhs.uk [194.6.81.14])
	by hub.freebsd.org (Postfix) with ESMTP
	id 17A6F151E2; Mon,  5 Jul 1999 02:29:27 -0700 (PDT)
	(envelope-from greg@swlct.sthames.nhs.uk)
Received: from greg (gquinlan [194.81.0.56])
	by mail.swlct.sthames.nhs.uk (8.9.3/8.9.3) with SMTP id KAA88983;
	Mon, 5 Jul 1999 10:26:30 +0100 (BST)
Message-ID: <004f01bec6c8$cfbecf20$380051c2@qmpgmc.ac.uk>
Reply-To: "Greg Quinlan" <greg@swlct.sthames.nhs.uk>
From: "Greg Quinlan" <greg@swlct.sthames.nhs.uk>
To: "Ron Rosson" <insane@lunatic.oneinsane.net>
Cc: <freebsd-ipfw@freebsd.org>, <freebsd-stable@freebsd.org>
References: <19990701164347.B22149@lunatic.oneinsane.net> <000901bec4d8$1f12fa30$0400a8c0@bahianet.com.br> <19990702160558.A66717@lunatic.oneinsane.net>
Subject: Re: NATD/VPN using -pptpalias
Date: Mon, 5 Jul 1999 10:28:58 +0100
Organization: Queen Mary's Hospital (SWLCT)
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Ron,

----- Original Message -----
From: Ron 'The InSaNe One' Rosson <insane@lunatic.oneinsane.net>

> Still no solution that works. I am still seeing if anyone else has any
ideas.
> I have not given up. I am lucky to have an understandable client.
>

I thought you may have already sorted a simple problem like this. :)

> > > I am tring to get a FreeBSD 3.2-STABLE as of Last week to pass a VPN
> > connection
> > > from a client behind the NATD box to a Server out on the internet. At
this
> > time
> > > I am getting erro, timeout exceeded while waiting for reply.
> > >
> > > excerpt from rc.conf
> > > natd_enable="YES"
> > > natd_interface="ed0"
> > > natd_flags="-pptpalias 192.168.2.7"
> > >
> > > excerpt  from rc.firewall
> > > if [ "X${natd_enable}" = X"YES" -a "X${natd_interface}" != X"" ]; then
> > > $fwcmd add divert natd all from any to any via ${natd_interface}

In the firewall rules you are using the "natd" port (ie. /etc/serviices ..
port 8668)
I assume that you have set up "ptpalias" in the same file.
like:
natd          8668   # Original entry.in /etc/services
ptpalias    8669

Just change the firewall command to:

$fwcmd add divert ptpalias all from any to any via ${natd_interface}

What is the "192.168.2.7" in natd_flags for?

I hope it wasn't meant to be "-a 192.168.2.7"
(192.168.x.x will not route over the internet)

:)

Greg






To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul  5  6:19: 8 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129])
	by hub.freebsd.org (Postfix) with ESMTP id 4937F14BED
	for <freebsd-stable@freebsd.org>; Mon,  5 Jul 1999 06:19:04 -0700 (PDT)
	(envelope-from talon@lpthe.jussieu.fr)
Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1])
          by shiva.jussieu.fr (8.9.3/jtpda-5.3.2) with ESMTP id PAA29138
          ; Mon, 5 Jul 1999 15:19:00 +0200 (CEST)
Received: from niobe.lpthe.jussieu.fr (niobe.lpthe.jussieu.fr [134.157.10.41])
          by parthe.lpthe.jussieu.fr (8.9.1a/jtpda-5.3.1) with ESMTP id PAA04283
          ; Mon, 5 Jul 1999 15:19:00 +0200 (MET DST)
From: talon@lpthe.jussieu.fr (Michel TALON)
Received: from (talon@localhost)
          by niobe.lpthe.jussieu.fr (8.9.3/jtpda-5.3.1) id PAA56824
          ; Mon, 5 Jul 1999 15:18:59 +0200 (CEST)
Message-Id: <199907051318.PAA56824@niobe.lpthe.jussieu.fr>
Subject: Re: ARP Problem? Need confirmation...
In-Reply-To: <Pine.LNX.4.02.9907041508090.4687-100000@mercury.webnology.com> from "Jasper O'Malley" at "Jul 4, 1999  3:10:36 pm"
To: jooji@webnology.com (Jasper O'Malley)
Date: Mon, 5 Jul 1999 15:18:59 +0200 (CEST)
Cc: freebsd-stable@freebsd.org
Lab: L.P.T.H.E. Universite Paris VI, Tour 16, 1 etage PARIS 75005
Tel: (33) 1 44 27 73 98
Fax: (33) 1 44 27 70 88
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In reply to the message from Jasper O'Malley
> On Sat, 3 Jul 1999, Adrian Wontroba wrote:
> 
> > # arp -s 192.168.1.13 auto pub
> > using interface ep0 for proxy with address 0:10:5a:ae:33:86
> > arp: writing to routing socket: File exists
> > 
> > This is on a RELENG_3 box with a make world run on June 30th.
> 
> This is the second independent confirmation I've gotten for this bug. I've
> tried to locate the offending code in the source tree, but it's beyond my
> limited programming abilities, I'm afraid. Anyone have any ideas?

Here on my machine running 3.2-STABLE i get the following result:

su-2.02# arp -s 134.157.10.68 auto pub
using interface xl0 for proxy with address 0:10:5a:3b:ae:3

note however that the ethernet adress here obtained is incorrect
since this is my own mac adress and not that of the printer
134.157.10.68  But after all i used auto!
After a couple of arp -d the situation is restored to normal.

arp -a
ariane.lpthe.jussieu.fr (134.157.10.68) at 0:60:b0:bf:49:96

It seems that there is no bug here.




-- 

Michel TALON



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul  5  6:47:36 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from dslab7.cs.uit.no (dslab7.cs.UiT.No [129.242.16.27])
	by hub.freebsd.org (Postfix) with ESMTP id BA1AB14DA7
	for <stable@freebsd.org>; Mon,  5 Jul 1999 06:47:26 -0700 (PDT)
	(envelope-from frodef@dslab7.cs.uit.no)
Received: (from frodef@localhost)
	by dslab7.cs.uit.no (8.9.3/8.9.1) id PAA00373;
	Mon, 5 Jul 1999 15:45:08 +0200 (CEST)
	(envelope-from frodef)
To: stable@freebsd.org
Subject: "can't allocate llinfo"
From: Frode Vatvedt Fjeld <frodef@acm.org>
Date: 05 Jul 1999 15:45:07 +0200
Message-ID: <2hlncvw6qk.fsf@dslab7.cs.uit.no>
Lines: 24
User-Agent: Gnus/5.070084 (Pterodactyl Gnus v0.84) Emacs/20.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I'm trying to netboot another pc. It used to work, but now I get this
not-so-informative message on the server-side (FreeBSD) when the
netbooted kernel (NetBSD) tries to find its root:

arplookup 129.242.13.129 failed: could not allocate llinfo
arpresolve: can't allocate llinfo for 129.242.13.129rt

What does these messages mean, and can it be fixed?

It appears that the client kernel never sees any kind of reply from
the server.

The one funny thing about the setup is that the two machines are on
different logical nets, but the same physical net. On the server, I
have added a static route to the client's logical net via the local
ethernet, so this _should_ work.

Thanks,
-- 
Frode Vatvedt Fjeld





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul  5  9:22: 3 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150])
	by hub.freebsd.org (Postfix) with ESMTP id 47E4314FB2
	for <freebsd-stable@freebsd.org>; Mon,  5 Jul 1999 09:21:47 -0700 (PDT)
	(envelope-from gjp@noop.colo.erols.net)
Received: from localhost ([127.0.0.1] helo=noop.colo.erols.net)
	by noop.colo.erols.net with esmtp (Exim 2.12 #1)
	id 111BVX-000Hia-00; Mon, 5 Jul 1999 12:22:15 -0400
To: JMS Internet <webmaster@jmsinternet.com>
Cc: Alfred Perlstein <bright@rush.net>, freebsd-stable@FreeBSD.ORG
From: "Gary Palmer" <gpalmer@freebsd.org>
Subject: Re: Server Slowdown 
In-reply-to: Your message of "Sat, 03 Jul 1999 09:53:09 PDT."
             <4.1.19990703094749.00abc430@mail.sirius.com> 
Date: Mon, 05 Jul 1999 12:22:13 -0400
Message-ID: <68110.931191733@noop.colo.erols.net>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

JMS Internet wrote in message ID
<4.1.19990703094749.00abc430@mail.sirius.com>:
> Here is some more information about my system: Intel PII 350, 384
> Megs of RAM, 2 Multi-Gig hard drives (neither at capacity) .  My
> co-location company and myself know that there is more transfer
> trying to get through because we see it hitting a "roof" on it's
> transfer at about 3200kbps, and it won't go past that, and there is
> no steady up and downs, it's flat lining at that type of transfer,
> so we know something is wrong, and speed for transfers is VERY
> slow...  I ran a test at netmechanic.com, and it rated it as "poor".
> A site to look at for yourself would be www.sitepalace.com.  Thanks
> for your help...  Here is the information requested below:

Although you say you bumped up your apache limits, I bet you're
running across the hardcoded process limit. I think in apache.h there
is a #define which hard-limits the number of processes in the code.
That certainly seems to be your problem ... a fast connect and
sleeping for a few seconds before returning the page.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul  5  9:36:44 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from tranq1.tranquility.net (tranq1.tranquility.net [206.156.230.1])
	by hub.freebsd.org (Postfix) with ESMTP id 9B47C14DB6
	for <freebsd-stable@freebsd.org>; Mon,  5 Jul 1999 09:36:31 -0700 (PDT)
	(envelope-from stephen@math.missouri.edu)
Received: from math.missouri.edu (stephen.tranquility.net [206.156.230.78])
	by tranq1.tranquility.net (8.9.2/8.9.2) with ESMTP id LAA04796
	for <freebsd-stable@freebsd.org>; Mon, 5 Jul 1999 11:36:28 -0500 (CDT)
Message-ID: <3780DF0D.E0C6CA82@math.missouri.edu>
Date: Mon, 05 Jul 1999 11:36:29 -0500
From: Stephen Montgomery-Smith <stephen@math.missouri.edu>
X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.2-STABLE i386)
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
Subject: ttyv4 problems
References: <199905281651.JAA00994@dingo.cdrom.com> <374ECFB6.9AAC572B@newsguy.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I did a make world today.

Upon rebooting, I got error messages about getty not being able to find
/dev/ttyv4
through /dev/ttyv7.  Also startx would not work, reporting that /dev/ttyv4 was
missing.

I traced it down to /etc/ttys, which was updated.  Upon replacing this with the
old /etc/ttys, all these bad problems disappeared.

> diff /etc-new/ttys /etc/ttys 
2c2
< #     $Id: ttys,v 1.2.2.2 1999/07/04 17:18:50 des Exp $
---
> #     $Id: ttys,v 1.2.2.1 1999/02/12 04:03:39 wes Exp $
37,42c37
< ttyv3 "/usr/libexec/getty Pc"         cons25  on  secure
< ttyv4 "/usr/libexec/getty Pc"         cons25  on  secure
< ttyv5 "/usr/libexec/getty Pc"         cons25  on  secure
< ttyv6 "/usr/libexec/getty Pc"         cons25  on  secure
< ttyv7 "/usr/libexec/getty Pc"         cons25  on  secure
< ttyv8 "/usr/X11R6/bin/xdm -nodaemon"  xterm   off secure
---
> ttyv3 "/usr/X11R6/bin/xdm -nodaemon"  xterm   off secure
> 

-- 

Stephen Montgomery-Smith              stephen@math.missouri.edu
307 Math Science Building             stephen@showme.missouri.edu
Department of Mathematics             stephen@missouri.edu
University of Missouri-Columbia
Columbia, MO 65211
USA

Phone (573) 882 4540
Fax   (573) 882 1869

http://math.missouri.edu/~stephen


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul  5  9:48:32 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from grizzly.fas.com (cc69528-a.mtpls1.sc.home.com [24.6.61.166])
	by hub.freebsd.org (Postfix) with ESMTP id 96A0D15020
	for <freebsd-stable@FreeBSD.ORG>; Mon,  5 Jul 1999 09:48:17 -0700 (PDT)
	(envelope-from stanb@awod.com)
Received: by grizzly.fas.com
	($Revision: 1.37.109.23 $/16.2) id AA190423294; Mon, 5 Jul 1999 12:48:14 -0400
Subject: Broken ports
To: freebsd-stable@FreeBSD.ORG (FreeBSD Stable Mailing List)
Date: Mon, 5 Jul 1999 12:48:13 -0400 (EDT)
From: "Stan Brown" <stanb@awod.com>
X-Mailer: ELM [version 2.4 PL24]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1277      
Message-Id: <19990705164825.96A0D15020@hub.freebsd.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

	I am in the process of building a new machine for work. I started with
	the 32 CD, cvsuped, and proceded to build the needed ports.

	Several of the ones tah I use seem to have bee marked a sbroken lately.

	xscrabble is marked as broke because of the tar file. While the tar
	file on the original site has been wrong for some perios of time, the
	last time I simply grabed it from teh FreeBSD site by hand, and it
	built liek a charm. BTW the difference is probably a fix for 4 players
	that was pushed back upstream from the HP porting cneter.

	xgrab ws marked as broken, ecause of needing to run xrdb. Huh, what;s
	wrong with runing xrdb? Is anyone aware of a screen printign program
	that works from the ports colection other than this one?

	How can I overide the "broken" flag, and try to build xscrabble?

-- 
Stan Brown     stanb@netcom.com                                    843-745-3154
Westvaco
Charleston SC.
-- 
Windows 98: n.
	useless extension to a minor patch release for 32-bit extensions and
	a graphical shell for a 16-bit patch to an 8-bit operating system
	originally coded for a 4-bit microprocessor, written by a 2-bit 
	company that can't stand for 1 bit of competition.
-
(c) 1999 Stan Brown.  Redistribution via the Microsoft Network is prohibited.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul  5 10:17: 8 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from david.siemens.de (david.siemens.de [192.35.17.14])
	by hub.freebsd.org (Postfix) with ESMTP id C648614A2D
	for <freebsd-stable@FreeBSD.ORG>; Mon,  5 Jul 1999 10:16:54 -0700 (PDT)
	(envelope-from ust@cert.siemens.de)
X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer david.siemens.de)
Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.14])
	by david.siemens.de (8.9.3/8.9.3) with ESMTP id TAA27545
	for <freebsd-stable@FreeBSD.ORG>; Mon, 5 Jul 1999 19:16:46 +0200 (MET DST)
Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17])
	by mail2.siemens.de (8.9.3/8.9.3) with ESMTP id TAA06395
	for <freebsd-stable@FreeBSD.ORG>; Mon, 5 Jul 1999 19:16:46 +0200 (MET DST)
Received: from alaska.cert.siemens.de (alaska.cert.siemens.de [139.23.202.134])
	by mars.cert.siemens.de (8.9.3/8.9.3/Siemens CERT [ $Revision: 1.9 ]) with ESMTP id TAA06499
	for <freebsd-stable@FreeBSD.ORG>; Mon, 5 Jul 1999 19:18:02 +0200 (CEST)
Received: (from ust@localhost)
	by alaska.cert.siemens.de (8.9.3/8.9.3/alaska [ $Revision: 1.2 ]) id RAA02929
	for freebsd-stable@FreeBSD.ORG; Mon, 5 Jul 1999 17:18:02 GMT
	(envelope-from ust)
Date: Mon, 5 Jul 1999 19:18:02 +0200
From: Udo Schweigert <ust@cert.siemens.de>
To: freebsd-stable@FreeBSD.ORG
Subject: Re: ttyv4 problems
Message-ID: <19990705191802.A2902@alaska.cert.siemens.de>
Mail-Followup-To: freebsd-stable@FreeBSD.ORG
References: <199905281651.JAA00994@dingo.cdrom.com> <374ECFB6.9AAC572B@newsguy.com> <3780DF0D.E0C6CA82@math.missouri.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
In-Reply-To: <3780DF0D.E0C6CA82@math.missouri.edu>; from Stephen Montgomery-Smith on Mon, Jul 05, 1999 at 11:36:29AM -0500
X-Operating-System: FreeBSD 3.2-STABLE
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, Jul 05, 1999 at 11:36:29AM -0500, Stephen Montgomery-Smith wrote:
> I did a make world today.
> 
> Upon rebooting, I got error messages about getty not being able to find
> /dev/ttyv4
> through /dev/ttyv7.  Also startx would not work, reporting that /dev/ttyv4 was
> missing.
> 
> I traced it down to /etc/ttys, which was updated.  Upon replacing this with the
> old /etc/ttys, all these bad problems disappeared.
> 
> > diff /etc-new/ttys /etc/ttys 
> 2c2
> < #     $Id: ttys,v 1.2.2.2 1999/07/04 17:18:50 des Exp $
> ---
> > #     $Id: ttys,v 1.2.2.1 1999/02/12 04:03:39 wes Exp $
> 37,42c37
> < ttyv3 "/usr/libexec/getty Pc"         cons25  on  secure
> < ttyv4 "/usr/libexec/getty Pc"         cons25  on  secure
> < ttyv5 "/usr/libexec/getty Pc"         cons25  on  secure
> < ttyv6 "/usr/libexec/getty Pc"         cons25  on  secure
> < ttyv7 "/usr/libexec/getty Pc"         cons25  on  secure
> < ttyv8 "/usr/X11R6/bin/xdm -nodaemon"  xterm   off secure
> ---
> > ttyv3 "/usr/X11R6/bin/xdm -nodaemon"  xterm   off secure
> > 
> 

You can use the new /etc/ttys after

# cd /dev
# sh MAKEDEV vty12

or 

# sh MAKEDEV all

Regards
-------------------------------------------------------------------------------
Udo Schweigert              || Voice      : +49 89 636 42170
Siemens AG, Siemens CERT    || Fax        : +49 89 636 48000
ZT IK 3                     || email      : Udo.Schweigert@mchp.siemens.de
D-81730 Muenchen / Germany  ||            : ust@cert.siemens.de
PGP fingerprint             || 2A 53 F6 A6 30 59 64 02  6B C4 E0 73 B2 C9 6C E7
-------------------------------------------------------------------------------


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul  5 10:52:22 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from tranq1.tranquility.net (tranq1.tranquility.net [206.156.230.1])
	by hub.freebsd.org (Postfix) with ESMTP id 7DBF914F8A
	for <freebsd-stable@freebsd.org>; Mon,  5 Jul 1999 10:52:15 -0700 (PDT)
	(envelope-from stephen@math.missouri.edu)
Received: from math.missouri.edu (stephen.tranquility.net [206.156.230.78])
	by tranq1.tranquility.net (8.9.2/8.9.2) with ESMTP id MAA07681
	for <freebsd-stable@freebsd.org>; Mon, 5 Jul 1999 12:52:13 -0500 (CDT)
Message-ID: <3780F0CC.FBA7626C@math.missouri.edu>
Date: Mon, 05 Jul 1999 12:52:12 -0500
From: Stephen Montgomery-Smith <stephen@math.missouri.edu>
X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 3.2-STABLE i386)
MIME-Version: 1.0
To: freebsd-stable@freebsd.org
Subject: Re: ttyv4 problems and suggested change to FreeBSD Stable
References: <199905281651.JAA00994@dingo.cdrom.com> <374ECFB6.9AAC572B@newsguy.com> <3780DF0D.E0C6CA82@math.missouri.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

OK, since /etc/ttys has changed, it would seem to me appropriate to change
MAKEDEV as well.  So how about changing the sources for FreeBSD-STABLE so that
the line in MAKEDEV that looks like

        sh MAKEDEV vty4                                 # cdev, virtual tty
becomes
        sh MAKEDEV vty9                                 # cdev, virtual tty



-- 

Stephen Montgomery-Smith              stephen@math.missouri.edu
307 Math Science Building             stephen@showme.missouri.edu
Department of Mathematics             stephen@missouri.edu
University of Missouri-Columbia
Columbia, MO 65211
USA

Phone (573) 882 4540
Fax   (573) 882 1869

http://math.missouri.edu/~stephen


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul  5 12:53:10 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from mercury.webnology.com (mercury.webnology.com [209.155.51.2])
	by hub.freebsd.org (Postfix) with ESMTP id 2F5D314BE9
	for <freebsd-stable@FreeBSD.ORG>; Mon,  5 Jul 1999 12:53:07 -0700 (PDT)
	(envelope-from jooji@webnology.com)
Received: from localhost (jooji@localhost)
	by mercury.webnology.com (8.9.2/8.9.2) with SMTP id NAA17650;
	Mon, 5 Jul 1999 13:55:38 -0500 (CDT)
Date: Mon, 5 Jul 1999 13:55:37 -0500 (CDT)
From: "Jasper O'Malley" <jooji@webnology.com>
To: Michel TALON <talon@lpthe.jussieu.fr>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: ARP Problem? Need confirmation...
In-Reply-To: <199907051318.PAA56824@niobe.lpthe.jussieu.fr>
Message-ID: <Pine.LNX.4.02.9907051329260.17326-100000@mercury.webnology.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 5 Jul 1999, Michel TALON wrote:

> Here on my machine running 3.2-STABLE

When did you last run a make world?

> i get the following result:
> 
> su-2.02# arp -s 134.157.10.68 auto pub
> using interface xl0 for proxy with address 0:10:5a:3b:ae:3
> 
> note however that the ethernet adress here obtained is incorrect
> since this is my own mac adress and not that of the printer
> 134.157.10.68  But after all i used auto!

This is the desired behavior when using the "auto" and "pub" parameters.
The machine will then perform proxy ARP for the IP address, responding to
ARP requests for the address with the MAC address of one of its own
network interfaces.

The problem is this:

root@urchin:~ {2} ifconfig ed1
ed1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 192.168.54.1 netmask 0xffffff00 broadcast 192.168.54.255
        ether 00:e0:29:32:21:ee

root@urchin:~ {3} arp -a
? (192.168.54.133) at 0:a0:c9:70:4c:1c [ethernet]
? (192.168.54.254) at 0:e0:1e:b9:7d:c1 [ethernet]

root@urchin:~ {4} arp -s 192.168.54.5 auto pub
using interface ed1 for proxy with address 0:e0:29:32:21:ee
arp: writing to routing socket: File exists
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

[snip]

192.168.54.5 is an unused IP address on the same IP subnet as
interface ed1 (which has a MAC address of 0:e0:29:32:21:ee). 
What's supposed to happen--and what did in fact happen on this box running
3.2-RELEASE until I cvsupped the latest -STABLE sources and remade the
world--is this:

root@urchin:~ {1} arp -s 192.168.54.5 auto pub
using interface ed1 for proxy with address 0:e0:29:32:21:ee

root@urchin:~ {2} arp -a
? (192.168.54.5) at 0:e0:29:32:21:ee [ethernet] permanent published
? (192.168.54.133) at 0:a0:c9:70:4c:1c [ethernet]
? (192.168.54.254) at 0:e0:1e:b9:7d:c1 [ethernet]

[snip]

The problem is the "arp: writing to routing socket: File exists" error,
which suggests that an ARP entry (or link-level route, actually) for
192.168.54.5 already exists, which it does not:

root@urchin:~ {7} netstat -nr
Routing tables

Internet:
Destination        Gateway            Flags     Refs     Use     Netif Expire
default            192.168.54.254     UGSc        2        0      ed1
127.0.0.1          127.0.0.1          UH          0        4      lo0
192.168.27         link#1             UC          0        0     fxp0
192.168.54         link#2             UC          0        0      ed1
192.168.54.133     0:a0:c9:70:4c:1c   UHLW        1      128      ed1    818
192.168.54.254     0:e0:1e:b9:7d:c1   UHLW        1        0      ed1    818

> It seems that there is no bug here.

It's a bug. It worked fine in 3.2-RELEASE and it broke somewhere along the
way.

Cheers,
Mick

The Reverend Jasper P. O'Malley          dotdot:jooji@webnology.com
    Systems Administrator                  ringring:asktheadmiral
	Webnology, LLC               woowoo:http://www.webnology.com/~jooji



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul  5 12:56:11 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from bureau6.utcc.utoronto.ca (bureau6.utcc.utoronto.ca [128.100.132.16])
	by hub.freebsd.org (Postfix) with ESMTP id 9992314F1A
	for <freebsd-stable@freebsd.org>; Mon,  5 Jul 1999 12:55:55 -0700 (PDT)
	(envelope-from a.ponnampalam@utoronto.ca)
Received: from log3.in.utoronto.ca ([128.100.100.195] HELO log3.in.utoronto.ca ident: NO-IDENT-SERVICE [port 54669]) by bureau6.utcc.utoronto.ca with SMTP id <464412-29329>; Mon, 5 Jul 1999 15:55:35 -0400
Date:	Mon, 5 Jul 1999 15:55:31 -0400 (EDT)
From: a.ponnampalam@utoronto.ca
X-Sender: 03664424@log3.in.utoronto.ca
To: freebsd-stable@freebsd.org
Subject: synchronous transfers vs. asynchronous transfers
Message-ID: <Pine.GSO.3.96.990705155432.5352G-100000@log3.in.utoronto.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

I just recently used CVS to move from 3.2 release to 3.2 stable and i get
this message:
  "ahc0:A:3: refuses synchronous negotiation. Using asynchronous transfers"

any idea why i would get this for a stable build? i basically followed the
steps listed in
http://www.nothing-going-on.demon.co.uk/FreeBSD/make-world/make-world.html
1. get new files
2. make buildworld
3. make insallworld
4. recompile kernel
5. upgrade new files in /etc...

This is my dmesg:
Copyright (c) 1992-1999 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
	The Regents of the University of California. All rights reserved.
FreeBSD 3.2-STABLE #16: Mon Jul  5 00:11:19 EDT 1999
    root@fantasia:/usr/src/sys/compile/FANTASIA
Timecounter "i8254"  frequency 1193182 Hz
Timecounter "TSC"  frequency 199432705 Hz
CPU: Pentium Pro (199.43-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x617  Stepping=7
  Features=0xf9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV>
real memory  = 100663296 (98304K bytes)
avail memory = 94908416 (92684K bytes)
Preloaded elf kernel "kernel" at 0xc02ca000.
Probing for devices on PCI bus 0:
chip0: <Intel 82440FX (Natoma) PCI and memory controller> rev 0x02 on
pci0.0.0
chip1: <Intel 82371SB PCI to ISA bridge> rev 0x01 on pci0.7.0
ide_pci0: <Intel PIIX3 Bus-master IDE controller> rev 0x00 on pci0.7.1
ed1: <NE2000 PCI Ethernet (ProLAN)> rev 0x00 int a irq 11 on pci0.8.0
ed1: address 00:20:78:17:8b:f1, type NE2000 (16 bit)
vga0: <Matrox MGA 2064W graphics accelerator> rev 0x01 int a irq 10 on
pci0.9.0
ahc0: <Adaptec aic7850 SCSI adapter> rev 0x01 int a irq 12 on pci0.10.0
ahc0: aic7850 Single Channel A, SCSI Id=7, 3/255 SCBs
es1: <AudioPCI ES1370> rev 0x00 int a irq 5 on pci0.11.0
pcm1: using I/O space register mapping at 0x6300
Probing for PnP devices:
CSN 1 Vendor ID: INT1030 [0x3010d425] Serial 0x00ba5ea3 Comp ID: @@@0000
[0x00000000]
Probing for devices on the ISA bus:
sc0 on isa
sc0: VGA color <16 virtual consoles, flags=0x0>
ed0 not found at 0x280
atkbdc0 at 0x60-0x6f on motherboard
atkbd0 irq 1 on isa
sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fd0: 1.44MB 3.5in
wdc1 at 0x170-0x177 irq 15 on isa
wdc1: unit 0 (wd2): <JTS Corp. CHAMP Model C2000-3AF>
wd2: 1910MB (3913056 sectors), 3882 cyls, 16 heads, 63 S/T, 512 B/S
wdc1: unit 1 (atapi): <E285X/1.02>, removable, dma, iordis
acd0: drive speed 1367KB/sec, 240KB cache
acd0: supported read types: CD-DA
acd0: Audio: play, 255 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: CD-ROM 120mm audio disc loaded, unlocked
ex0 at 0x210-0x21f irq 9 on isa
ex0: Intel EtherExpress Pro/10, address 00:aa:00:ba:5e:a3, connector TPE
wdc0 at 0x1f0-0x1f7 irq 14 flags 0xb0ffb0ff on isa
wdc0: unit 0 (wd0): <QUANTUM FIREBALL ST3.2A>, LBA, DMA, 32-bit,
multi-block-16
wd0: 3079MB (6306048 sectors), 782 cyls, 128 heads, 63 S/T, 512 B/S
vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa
npx0 on motherboard
npx0: INT 16 interface
IP Filter: initialized.  Default = pass all, Logging = disabled
ahc0:A:3: refuses synchronous negotiation. Using asynchronous transfers
ahc0:A:3: refuses synchronous negotiation. Using asynchronous transfers
ahc0:A:3: refuses synchronous negotiation. Using asynchronous transfers
ahc0:A:3: refuses synchronous negotiation. Using asynchronous transfers
ahc0:A:3: refuses synchronous negotiation. Using asynchronous transfers
ahc0:A:3: refuses synchronous negotiation. Using asynchronous transfers
ahc0:A:3: refuses synchronous negotiation. Using asynchronous transfers
ahc0:A:3: refuses synchronous negotiation. Using asynchronous transfers
changing root device to wd0s3a
cd0 at ahc0 bus 0 target 3 lun 0
cd0: <YAMAHA CRW4260 1.0h> Removable CD-ROM SCSI-2 device
cd0: 3.300MB/s transfers
cd0: Attempt to query device size failed: NOT READY, Medium not present -
tray closed
ffs_mountfs: superblock updated for soft updates



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul  5 15:22: 1 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from grizzly.fas.com (cc69528-a.mtpls1.sc.home.com [24.6.61.166])
	by hub.freebsd.org (Postfix) with ESMTP id AF3B614EEB
	for <freebsd-stable@FreeBSD.ORG>; Mon,  5 Jul 1999 15:21:37 -0700 (PDT)
	(envelope-from stanb@awod.com)
Received: by grizzly.fas.com
	($Revision: 1.37.109.23 $/16.2) id AA238643295; Mon, 5 Jul 1999 18:21:35 -0400
Subject: ATAPI_STATIC ?
To: freebsd-stable@FreeBSD.ORG (FreeBSD Stable Mailing List)
Date: Mon, 5 Jul 1999 18:21:34 -0400 (EDT)
From: "Stan Brown" <stanb@awod.com>
X-Mailer: ELM [version 2.4 PL24]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 873       
Message-Id: <19990705222138.AF3B614EEB@hub.freebsd.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

	Putting  together a new -STABLE mahcine today. I was choping sown the
	kernel to the minimum, when I noticed that the ATAPI CDROM was no
	longer working. Well to make a long earch short, I found out that if I
	left the ATAPI_STATIC out of the kernel config, the CD was not found at
	boot up.

	Is this the expected behavio? If so what use is makeint this a loadable
	module, if it won't be found at power up?

-- 
Stan Brown     stanb@netcom.com                                    843-745-3154
Westvaco
Charleston SC.
-- 
Windows 98: n.
	useless extension to a minor patch release for 32-bit extensions and
	a graphical shell for a 16-bit patch to an 8-bit operating system
	originally coded for a 4-bit microprocessor, written by a 2-bit 
	company that can't stand for 1 bit of competition.
-
(c) 1999 Stan Brown.  Redistribution via the Microsoft Network is prohibited.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul  5 16: 8:21 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66])
	by hub.freebsd.org (Postfix) with ESMTP
	id E188A15376; Mon,  5 Jul 1999 16:08:12 -0700 (PDT)
	(envelope-from nik@nothing-going-on.demon.co.uk)
Received: (from nik@localhost)
	by nothing-going-on.demon.co.uk (8.9.3/8.9.2) id XAA83221;
	Mon, 5 Jul 1999 23:54:27 +0100 (BST)
	(envelope-from nik)
Date: Mon, 5 Jul 1999 23:54:26 +0100
From: Nik Clayton <nik@nothing-going-on.demon.co.uk>
To: Spiderman <billy@isyndicate.com>
Cc: freebsd-doc@freebsd.org, freebsd-stable@freebsd.org
Subject: Re: sup(1) in FreeBSD 3.2-STABLE
Message-ID: <19990705235425.S71138@catkin.nothing-going-on.org>
References: <19990618143616D.billy@isyndicate.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <19990618143616D.billy@isyndicate.com>; from Spiderman on Fri, Jun 18, 1999 at 02:36:16PM -0700
Organization: Nik at home, where there's nothing going on
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Fri, Jun 18, 1999 at 02:36:16PM -0700, Spiderman wrote:
> In cvsup(1) there is a refrence to sup(1) which doesn't exist.
> Should it exist?

No it shouldn't.  However, CVSup is a port, rather than a part of the
FreeBSD base system, so this should ideally have gone to 
cvsup-bugs@polstra.com.  Thanks for the report though.

I've forwarded your message on to John Polstra, who has said that the
next release will have that note removed from the documentation.

Once again, thanks for letting us know.

N
-- 
 [intentional self-reference] can be easily accommodated using a blessed,
 non-self-referential dummy head-node whose own object destructor severs
 the links.
    -- Tom Christiansen in <375143b5@cs.colorado.edu>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul  5 16:25: 4 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from lazlo.internal.steam.com (lazlo.steam.com [199.108.84.37])
	by hub.freebsd.org (Postfix) with ESMTP
	id EA2B614C40; Mon,  5 Jul 1999 16:24:46 -0700 (PDT)
	(envelope-from cliff@steam.com)
Received: from lazlo.internal.steam.com (cliff@lazlo.internal.steam.com [192.168.32.2])
	by lazlo.internal.steam.com (8.9.3/8.9.3) with ESMTP id QAA69104;
	Mon, 5 Jul 1999 16:26:14 -0700 (PDT)
Date: Mon, 5 Jul 1999 16:26:13 -0700 (PDT)
From: Cliff Skolnick <cliff@steam.com>
X-Sender: cliff@lazlo.internal.steam.com
To: Gary Palmer <gpalmer@FreeBSD.ORG>
Cc: JMS Internet <webmaster@jmsinternet.com>,
	Alfred Perlstein <bright@rush.net>, freebsd-stable@FreeBSD.ORG
Subject: Re: Server Slowdown 
In-Reply-To: <68110.931191733@noop.colo.erols.net>
Message-ID: <Pine.BSF.4.10.9907051618510.31545-100000@lazlo.internal.steam.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 5 Jul 1999, Gary Palmer wrote:
> Although you say you bumped up your apache limits, I bet you're
> running across the hardcoded process limit. I think in apache.h there
> is a #define which hard-limits the number of processes in the code.
> That certainly seems to be your problem ... a fast connect and
> sleeping for a few seconds before returning the page.

Be very carefull about bumping maxclients too high as you will loose
performance rapidly if your machine starts paging it's brains out.  In high
load situtuation it's usually better to serialize the requests than to start
paging.  I regularly do consulting for apache servers having performance
problems, and over half the time it is a maxclients set to some outrageous
number like 1800!  Sure if you have more than 2GB of physical memory you may
get away with this but most of these machines had 256MB or 512MB.

I've already exchanged mail with the original poster, in this case it looks
like he was disk bound by the looks of the "vmstat 5" output he sent.  He
had two IDE drives in the system but one was used as a backup.  My advice
was to moved the logs to the second disk and see what that does to
performance.

Cliff

--
Cliff Skolnick          | "They that can give up essential liberty to obtain
Steam Tunnel Operations |  a little temporary safety deserve neither liberty
cliff@steam.com         |  nor safety."
http://www.steam.com/   |                   -- Benjamin Franklin, 1759



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul  5 18:45:23 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from grizzly.fas.com (cc69528-a.mtpls1.sc.home.com [24.6.61.166])
	by hub.freebsd.org (Postfix) with ESMTP id C389314FF0
	for <freebsd-stable@FreeBSD.ORG>; Mon,  5 Jul 1999 18:45:15 -0700 (PDT)
	(envelope-from stanb@awod.com)
Received: by grizzly.fas.com
	($Revision: 1.37.109.23 $/16.2) id AA153085512; Mon, 5 Jul 1999 21:45:13 -0400
Subject: Default gnome configuration
To: freebsd-stable@FreeBSD.ORG (FreeBSD Stable Mailing List)
Date: Mon, 5 Jul 1999 21:45:12 -0400 (EDT)
From: "Stan Brown" <stanb@awod.com>
X-Mailer: ELM [version 2.4 PL24]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 1519      
Message-Id: <19990706014516.C389314FF0@hub.freebsd.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

 	I just this weekend put together 2 boxes for work. One was a FreeBSD
	3.2-STABLE machine, and one was a RedHat 6.0 machine. Why 2 you ask?
	Let's just say that the windozze support people at work have discovered
	that there _might_ be something else ut there, and i wnated them to see
	both Linux, _and_ FreeBSD.

	But I digress. Here is what I find stange the RedHat box by default has
	a very nice gnome environemnt (assuming you like GUI tools). The
	FreeBSD machine had a pretty strange default gnome seup, even using
	afterstep, instead of Enlightenment as the default window manager. I
	was particulary suprised at this, given that the new 3.2 install
	program even offers you the choice of gnom as a default destop. Now I
	grant you if you _don't_ choose this you get a different window
	manager. Still it seems we may be missing the boat here for
	desktop/client machines. I believe that the gnome (or KDE) environment
	will be an important part of wining the desktop back.

	So, could we perahps build a little nicer set of defaults for gnome?


-- 
Stan Brown     stanb@netcom.com                                    843-745-3154
Westvaco
Charleston SC.
-- 
Windows 98: n.
	useless extension to a minor patch release for 32-bit extensions and
	a graphical shell for a 16-bit patch to an 8-bit operating system
	originally coded for a 4-bit microprocessor, written by a 2-bit 
	company that can't stand for 1 bit of competition.
-
(c) 1999 Stan Brown.  Redistribution via the Microsoft Network is prohibited.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul  5 19:35:11 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from web1003.mail.yahoo.com (web1003.mail.yahoo.com [128.11.23.93])
	by hub.freebsd.org (Postfix) with SMTP id 6D7AA14DF1
	for <freebsd-stable@freebsd.org>; Mon,  5 Jul 1999 19:35:08 -0700 (PDT)
	(envelope-from bvmcg@yahoo.com)
Message-ID: <19990706023507.22760.rocketmail@web1003.mail.yahoo.com>
Received: from [24.29.199.198] by web1003.mail.yahoo.com; Mon, 05 Jul 1999 19:35:07 PDT
Date: Mon, 5 Jul 1999 19:35:07 -0700 (PDT)
From: Brian McGroarty <bvmcg@yahoo.com>
Reply-To: brian@pobox.com
Subject: Re: Default gnome configuration
To: freebsd-stable@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

The package description of Enlightenment is a bit condescending:

	A very artistic X window manager. Among other
	attributes, Enlightenment makes for qutie impressive
	screen shots.

This trivializes the marked advances it offers, and the
combination of the terrible default installation and the above
has doubtless put many off of Gnome/Englightenment

As in so many other areas, RedHat wins hands down over FreeBSD
in an area where it really makes little sense to do so.


--- Stan Brown <stanb@awod.com> wrote:
>  	I just this weekend put together 2 boxes for work. One was a
> FreeBSD
> 	3.2-STABLE machine, and one was a RedHat 6.0 machine. Why 2
> you ask?
> 	Let's just say that the windozze support people at work have
> discovered
> 	that there _might_ be something else ut there, and i wnated
> them to see
> 	both Linux, _and_ FreeBSD.
> 
> 	But I digress. Here is what I find stange the RedHat box by
> default has
> 	a very nice gnome environemnt (assuming you like GUI tools).
> The
> 	FreeBSD machine had a pretty strange default gnome seup, even
> using
> 	afterstep, instead of Enlightenment as the default window
> manager. I
> 	was particulary suprised at this, given that the new 3.2
> install
> 	program even offers you the choice of gnom as a default
> destop. Now I
> 	grant you if you _don't_ choose this you get a different
> window
> 	manager. Still it seems we may be missing the boat here for
> 	desktop/client machines. I believe that the gnome (or KDE)
> environment
> 	will be an important part of wining the desktop back.
> 
> 	So, could we perahps build a little nicer set of defaults for
> gnome?

===
_________________________________________________________

"Men who are orthodox  when they are young  are in danger
of being middle-aged all their lives." -- Walter Lippmann
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul  5 20:40:20 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from dingo.cdrom.com (castles501.castles.com [208.214.165.65])
	by hub.freebsd.org (Postfix) with ESMTP id 85C441506F
	for <freebsd-stable@freebsd.org>; Mon,  5 Jul 1999 20:40:16 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1])
	by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id UAA15851;
	Mon, 5 Jul 1999 20:36:39 -0700 (PDT)
	(envelope-from mike@dingo.cdrom.com)
Message-Id: <199907060336.UAA15851@dingo.cdrom.com>
X-Mailer: exmh version 2.0.2 2/24/98
To: brian@pobox.com
Cc: freebsd-stable@freebsd.org
Subject: Re: Default gnome configuration 
In-reply-to: Your message of "Mon, 05 Jul 1999 19:35:07 PDT."
             <19990706023507.22760.rocketmail@web1003.mail.yahoo.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 05 Jul 1999 20:36:39 -0700
From: Mike Smith <mike@smith.net.au>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> The package description of Enlightenment is a bit condescending:
> 
> 	A very artistic X window manager. Among other
> 	attributes, Enlightenment makes for qutie impressive
> 	screen shots.
> 
> This trivializes the marked advances it offers, and the
> combination of the terrible default installation and the above
> has doubtless put many off of Gnome/Englightenment
> 
> As in so many other areas, RedHat wins hands down over FreeBSD
> in an area where it really makes little sense to do so.

I'm sure your contributions in this area would be most appreciated.  
Now, where did you submit them again?

-- 
\\  The mind's the standard       \\  Mike Smith
\\  of the man.                   \\  msmith@freebsd.org
\\    -- Joseph Merrick           \\  msmith@cdrom.com




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul  5 21:44:53 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from web1006.mail.yahoo.com (web1006.mail.yahoo.com [128.11.23.96])
	by hub.freebsd.org (Postfix) with SMTP id B95AC14FF5
	for <freebsd-stable@freebsd.org>; Mon,  5 Jul 1999 21:44:03 -0700 (PDT)
	(envelope-from bvmcg@yahoo.com)
Message-ID: <19990706044402.15783.rocketmail@web1006.mail.yahoo.com>
Received: from [24.29.199.198] by web1006.mail.yahoo.com; Mon, 05 Jul 1999 21:44:02 PDT
Date: Mon, 5 Jul 1999 21:44:02 -0700 (PDT)
From: Brian McGroarty <bvmcg@yahoo.com>
Reply-To: brian@pobox.com
Subject: Re: Default gnome configuration 
To: freebsd-stable@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I've been paying for the FreeBSD discs for a few years now
despite having fast enough net access to get the thing for free
merely because it kicks money back to the development team.
There, you've got my contributions.

Last time I tried submitting anything it was dismissed without
even a test because D. Greenman didn't seem to want anyone else
touching his NE2000 driver. Thus the full duplex operation
memory size bug remains in place. Additionally, earlier offers
at assisting ISA PNP weren't met with any kind of welcoming
support, so I'm content to remain a user, and to continue
developing other platforms.

Your sarcasm isn't well received, Mr. Smith.



--- Mike Smith <mike@smith.net.au> wrote:
> > The package description of Enlightenment is a bit
> condescending:
> > 
> > 	A very artistic X window manager. Among other
> > 	attributes, Enlightenment makes for qutie impressive
> > 	screen shots.
> > 
> > This trivializes the marked advances it offers, and the
> > combination of the terrible default installation and the
> above
> > has doubtless put many off of Gnome/Englightenment
> > 
> > As in so many other areas, RedHat wins hands down over
> FreeBSD
> > in an area where it really makes little sense to do so.
> 
> I'm sure your contributions in this area would be most
> appreciated.  
> Now, where did you submit them again?

===
_________________________________________________________

"Men who are orthodox  when they are young  are in danger
of being middle-aged all their lives." -- Walter Lippmann
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul  5 21:50:10 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228])
	by hub.freebsd.org (Postfix) with ESMTP id 78ADC14EB2
	for <freebsd-stable@FreeBSD.ORG>; Mon,  5 Jul 1999 21:49:41 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1])
	by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA77903;
	Mon, 5 Jul 1999 21:48:08 -0700 (PDT)
	(envelope-from jkh@zippy.cdrom.com)
To: "Stan Brown" <stanb@awod.com>
Cc: freebsd-stable@FreeBSD.ORG (FreeBSD Stable Mailing List)
Subject: Re: Default gnome configuration 
In-reply-to: Your message of "Mon, 05 Jul 1999 21:45:12 EDT."
             <19990706014516.C389314FF0@hub.freebsd.org> 
Date: Mon, 05 Jul 1999 21:48:06 -0700
Message-ID: <77899.931236486@zippy.cdrom.com>
From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 	But I digress. Here is what I find stange the RedHat box by default has
> 	a very nice gnome environemnt (assuming you like GUI tools). The
> 	FreeBSD machine had a pretty strange default gnome seup, even using
> 	afterstep, instead of Enlightenment as the default window manager. I

I picked afterstep because it seemed more functional out of the box
than Enlightenment and Gnome doesn't really standardize on a specific
window manager the way KDE does, leaving the question of which WM to
use with it somewhat vague.  I have no particular axe to grind on this
choice either way, my choice of "nifty dotfiles" that configure Gnome
in lots of nice default environment kind aways simply being rather
limited.  I don't use Gnome so I couldn't simply borrow my own for
this - do you have some Gnome configuration data/tips for how we
can make the Gnome desktop more "nice" in the Red Hat fashion?

- Jordan


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul  5 22: 0:15 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from implode.root.com (root.com [209.102.106.178])
	by hub.freebsd.org (Postfix) with ESMTP id 5529215076
	for <freebsd-stable@FreeBSD.ORG>; Mon,  5 Jul 1999 22:00:12 -0700 (PDT)
	(envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.8/8.8.5) with ESMTP id VAA09263;
	Mon, 5 Jul 1999 21:59:46 -0700 (PDT)
Message-Id: <199907060459.VAA09263@implode.root.com>
To: brian@pobox.com
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Default gnome configuration 
In-reply-to: Your message of "Mon, 05 Jul 1999 21:44:02 PDT."
             <19990706044402.15783.rocketmail@web1006.mail.yahoo.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Mon, 05 Jul 1999 21:59:46 -0700
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>I've been paying for the FreeBSD discs for a few years now
>despite having fast enough net access to get the thing for free
>merely because it kicks money back to the development team.
>There, you've got my contributions.
>
>Last time I tried submitting anything it was dismissed without
>even a test because D. Greenman didn't seem to want anyone else
>touching his NE2000 driver. Thus the full duplex operation
>memory size bug remains in place.

   Huh? Whatever gave you that idea?

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org
Creator of high-performance Internet servers - http://www.terasolutions.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Mon Jul  5 22:48: 9 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from web1002.mail.yahoo.com (web1002.mail.yahoo.com [128.11.23.92])
	by hub.freebsd.org (Postfix) with SMTP id AE23715396
	for <freebsd-stable@freebsd.org>; Mon,  5 Jul 1999 22:48:07 -0700 (PDT)
	(envelope-from bvmcg@yahoo.com)
Message-ID: <19990706054807.19419.rocketmail@web1002.mail.yahoo.com>
Received: from [24.29.199.198] by web1002.mail.yahoo.com; Mon, 05 Jul 1999 22:48:07 PDT
Date: Mon, 5 Jul 1999 22:48:07 -0700 (PDT)
From: Brian McGroarty <bvmcg@yahoo.com>
Reply-To: brian@pobox.com
Subject: Re: Default gnome configuration 
To: freebsd-stable@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I wrote you directly following discussions in the mailing lists
regarding slow transmissions. The problem had turned out to be
non-detection and non-support of NE2000 cards with full-duplex
mode transceivers. I first sent a patch that prevented the rx
buffer spilling into the tx buffer and kept seperate pointers
for both, properly reflecting the effective half memory sizes. I
later wrote with specifications I argued out of D-Link which
clarified duplex card detection as well as information on better
supporting JITI (adjustable buffer fill interrupt triggers)
transfers.

Last I looked no changes had been made to if_ed.c. I since moved
to a 3c905 based card, so I dropped it.


--- David Greenman <dg@root.com> wrote:
> >I've been paying for the FreeBSD discs for a few years now
> >despite having fast enough net access to get the thing for
> free
> >merely because it kicks money back to the development team.
> >There, you've got my contributions.
> >
> >Last time I tried submitting anything it was dismissed
> without
> >even a test because D. Greenman didn't seem to want anyone
> else
> >touching his NE2000 driver. Thus the full duplex operation
> >memory size bug remains in place.
> 
>    Huh? Whatever gave you that idea?

===
_________________________________________________________

"Men who are orthodox  when they are young  are in danger
of being middle-aged all their lives." -- Walter Lippmann
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul  6  0:40:47 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from gipsy.zurich.gr (vdp112.ath02.cas.hol.gr [195.97.2.112])
	by hub.freebsd.org (Postfix) with ESMTP id 54D8814BCC
	for <freebsd-stable@FreeBSD.ORG>; Tue,  6 Jul 1999 00:40:14 -0700 (PDT)
	(envelope-from ocean@compulink.gr)
Received: from grzema-notebook (grzema-notebook.zurich.gr [192.168.185.62])
	by gipsy.zurich.gr (8.9.3/8.9.2) with SMTP id KAA03844;
	Tue, 6 Jul 1999 10:39:07 +0300 (EEST)
	(envelope-from ocean@compulink.gr)
From: "Elias Mandouvalos" <ocean@compulink.gr>
To: "'Stephen Montgomery-Smith'" <stephen@math.missouri.edu>,
	<freebsd-stable@FreeBSD.ORG>
Subject: RE: ttyv4 problems
Date: Tue, 6 Jul 1999 10:39:05 -0000
Message-ID: <000001bec79b$c59531a0$3eb9a8c0@grzema-notebook.zurich.gr>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
In-reply-to: <3780DF0D.E0C6CA82@math.missouri.edu>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

try cd /dev
./MAKEDEV vty12


-----Original Message-----
From: owner-freebsd-stable@FreeBSD.ORG
[mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Stephen
Montgomery-Smith
Sent: Monday, July 05, 1999 4:36 PM
To: freebsd-stable@FreeBSD.ORG
Subject: ttyv4 problems


I did a make world today.

Upon rebooting, I got error messages about getty not being able to find
/dev/ttyv4
through /dev/ttyv7.  Also startx would not work, reporting that /dev/ttyv4
was
missing.

I traced it down to /etc/ttys, which was updated.  Upon replacing this with
the
old /etc/ttys, all these bad problems disappeared.

> diff /etc-new/ttys /etc/ttys
2c2
< #     $Id: ttys,v 1.2.2.2 1999/07/04 17:18:50 des Exp $
---
> #     $Id: ttys,v 1.2.2.1 1999/02/12 04:03:39 wes Exp $
37,42c37
< ttyv3 "/usr/libexec/getty Pc"         cons25  on  secure
< ttyv4 "/usr/libexec/getty Pc"         cons25  on  secure
< ttyv5 "/usr/libexec/getty Pc"         cons25  on  secure
< ttyv6 "/usr/libexec/getty Pc"         cons25  on  secure
< ttyv7 "/usr/libexec/getty Pc"         cons25  on  secure
< ttyv8 "/usr/X11R6/bin/xdm -nodaemon"  xterm   off secure
---
> ttyv3 "/usr/X11R6/bin/xdm -nodaemon"  xterm   off secure
>

--

Stephen Montgomery-Smith              stephen@math.missouri.edu
307 Math Science Building             stephen@showme.missouri.edu
Department of Mathematics             stephen@missouri.edu
University of Missouri-Columbia
Columbia, MO 65211
USA

Phone (573) 882 4540
Fax   (573) 882 1869

http://math.missouri.edu/~stephen


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul  6  3:29:37 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from implode.root.com (root.com [209.102.106.178])
	by hub.freebsd.org (Postfix) with ESMTP id AAECD14BC9
	for <freebsd-stable@FreeBSD.ORG>; Tue,  6 Jul 1999 03:29:34 -0700 (PDT)
	(envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.8/8.8.5) with ESMTP id DAA10851;
	Tue, 6 Jul 1999 03:27:56 -0700 (PDT)
Message-Id: <199907061027.DAA10851@implode.root.com>
To: brian@pobox.com
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Default gnome configuration 
In-reply-to: Your message of "Mon, 05 Jul 1999 22:48:07 PDT."
             <19990706054807.19419.rocketmail@web1002.mail.yahoo.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Tue, 06 Jul 1999 03:27:56 -0700
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> >Last time I tried submitting anything it was dismissed
> without
> >even a test because D. Greenman didn't seem to want anyone
> else
> >touching his NE2000 driver. Thus the full duplex operation
> >memory size bug remains in place.
> 
>    Huh? Whatever gave you that idea?
>
>I wrote you directly following discussions in the mailing lists
>regarding slow transmissions. The problem had turned out to be
>non-detection and non-support of NE2000 cards with full-duplex
>mode transceivers. I first sent a patch that prevented the rx
>buffer spilling into the tx buffer and kept seperate pointers
>for both, properly reflecting the effective half memory sizes. I
>later wrote with specifications I argued out of D-Link which
>clarified duplex card detection as well as information on better
>supporting JITI (adjustable buffer fill interrupt triggers)
>transfers.
>
>Last I looked no changes had been made to if_ed.c. I since moved
>to a 3c905 based card, so I dropped it.

   I've apparantly completely spaced it since I don't even remember seeing
those patches. I don't appear to have anything saved in my mailbox about it,
either. Did I reply with something that indicated that I saw them?? The last
thing I recall seeing which was NE2000 related were some patches from Jonathan
Bresler that added support for a Linksys PCMCIA card, to which I replied that
the detection test was weak and may false-identify non-Linksys cards. In any
case, I've been out of town a lot recently and have been too busy to deal
with a lot of things like this.
   I really don't think it is fair to me for you to make baseless accusations
of me 'dismissing' a submission due to some sort of pride/territory problem.
That simply isn't the way that I operate and I'm truely sorry that you've
gotten that impression.

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org
Creator of high-performance Internet servers - http://www.terasolutions.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul  6  8:46: 5 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from nic.bse.bg (nic.bse.bg [195.138.140.5])
	by hub.freebsd.org (Postfix) with ESMTP id E581F1542F
	for <freebsd-stable@freebsd.org>; Tue,  6 Jul 1999 08:45:50 -0700 (PDT)
	(envelope-from hristo@bg.freebsd.org)
Received: from localhost (hristo@localhost)
	by nic.bse.bg (8.9.3/8.9.3) with ESMTP id SAA21808
	for <freebsd-stable@freebsd.org>; Tue, 6 Jul 1999 18:45:47 +0300 (EEST)
Date: Tue, 6 Jul 1999 18:45:45 +0300 (EEST)
From: Hristo Grigorov <hristo@bg.freebsd.org>
X-Sender: hristo@nic.bse.bg
To: freebsd-stable@freebsd.org
Subject: ipfw
Message-ID: <Pine.BSF.4.10.9907061836300.21791-100000@nic.bse.bg>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Greetings,

I set 'ipfw pipe 11 config bw 3Mbit/sec'
Sample output from 'ipfw pipe show 11':

00011:   3.000 Mbit/s   0 ms ...

Well, I didn't set default delay but actually there
is a delay ? It just can't be 0 ms !
At least CISCO routers auto-calculate what the delay is.

So, could you please tell me how to calculate the delay for
each pipe and I'll try to hack ipfw.c myself...

Thank you in advance!





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul  6 11:20:29 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from logatome.micronet.fr (logatome-2.francenet.fr [193.149.96.2])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0C3271528B; Tue,  6 Jul 1999 11:20:21 -0700 (PDT)
	(envelope-from Sebastien.Gioria@FranceNet.fr)
Received: from gioria.dialup.FranceNet.fr (eku28.dialup.francenet.fr [193.149.106.173] (may be forged))
	by logatome.micronet.fr (8.8.8/8.8.8) with ESMTP id UAA23771;
	Tue, 6 Jul 1999 20:18:33 +0200 (CEST)
Received: by gioria.dialup.FranceNet.fr (Postfix, from userid 42)
	id 67A572001A; Tue,  6 Jul 1999 20:20:07 +0200 (CEST)
Message-ID: <19990706202007.K780@FranceNet.fr>
Date: Tue, 6 Jul 1999 20:20:07 +0200
From: Sebastien GIORIA <gioria@FranceNet.fr>
To: freebsd-mobile@freebsd.org
Cc: freebsd-stable@freebsd.org
Subject: APA 1460 ?
Reply-To: Sebastien GIORIA <Sebastien.Gioria@FranceNet.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
Operating-System: Definitely FreeBSD
Function: Unix and Security Administrator
Organization: FranceNet
Postal-Address: 28 Rue Desaix , 75015 PARIS, FRANCE
Phone: +33 1 43 92 12 34
Fax: +33 1 43 92 14 45
X-Operating-System: FreeBSD-2.2.8-RELEASE (PAO enabled) on Dell Inspiron 3200
X-URL: http://www.FranceNet.fr -- http://www.freebsd-fr.org
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Anyone working on a camified version ? If no one working on it, 
where can I found a documentation to camifiy the driver ?

Thanks

	S.

-- 
-->  Sales staff sold a product we don't offer.  <--
Sebastien Gioria - FranceNet                     gioria@francenet.fr
Unix && Security Administrator                 security@francenet.fr
Tout FreeBSD en Francais =========>	  http://www.freebsd-fr.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul  6 11:31:49 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from mercury.webnology.com (mercury.webnology.com [209.155.51.2])
	by hub.freebsd.org (Postfix) with ESMTP id 7064914FE3
	for <freebsd-stable@FreeBSD.ORG>; Tue,  6 Jul 1999 11:31:47 -0700 (PDT)
	(envelope-from jooji@webnology.com)
Received: from localhost (jooji@localhost)
	by mercury.webnology.com (8.9.2/8.9.2) with SMTP id MAA00769
	for <freebsd-stable@FreeBSD.ORG>; Tue, 6 Jul 1999 12:34:32 -0500 (CDT)
Date: Tue, 6 Jul 1999 12:34:32 -0500 (CDT)
From: "Jasper O'Malley" <jooji@webnology.com>
To: freebsd-stable@FreeBSD.ORG
Subject: Re: ARP Problem? Need confirmation...
In-Reply-To: <Pine.LNX.4.02.9907051329260.17326-100000@mercury.webnology.com>
Message-ID: <Pine.LNX.4.02.9907061222320.455-100000@mercury.webnology.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Couple of questions that might go better in -questions, but they have
something to do with my understanding of the proxy ARP bug discussed in
this thread:

1) Can anyone explain what the difference between "permanent published"
   ARP table entries, and "permanent published (proxy only)" ARP table
   entries?

2) What purpose does the RTF_ANNOUNCE (aka RTF_PROTO2) routing message
   flag serve? How about the sin_other parameter of the sockaddr_inarp
   structure (defined in /usr/include/netinet/if_ether.h)?

3) How about the significance of the RTF_HOST routing message flag (i.e.
   how does an IP "host" route functionally differ from a "net" route with
   a /32 netmask)? 

4) What's the purpose of this snippet of code from rtmsg() in
   usr.sbin/arp/arp.c?

                if (doing_proxy) {
                        if (export_only)
                                sin_m.sin_other = SIN_PROXY;
                        else {
                                rtm->rtm_addrs |= RTA_NETMASK;
                                rtm->rtm_flags &= ~RTF_HOST;
                        }
                }

Cheers,
Mick

The Reverend Jasper P. O'Malley          dotdot:jooji@webnology.com
    Systems Administrator                  ringring:asktheadmiral
	Webnology, LLC               woowoo:http://www.webnology.com/~jooji



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul  6 11:57: 0 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from grom.mw.mil.pl (grom.mw.mil.pl [153.19.192.1])
	by hub.freebsd.org (Postfix) with ESMTP id 3204E15003
	for <freebsd-stable@FreeBSD.ORG>; Tue,  6 Jul 1999 11:56:54 -0700 (PDT)
	(envelope-from pawel@grom.mw.mil.pl)
Received: (from pawel@localhost)
	by grom.mw.mil.pl (8.8.8/8.8.7) id VAA07298
	for freebsd-stable@FreeBSD.ORG; Tue, 6 Jul 1999 21:05:59 +0200 (CEST)
	(envelope-from pawel)
Date: Tue, 6 Jul 1999 21:05:59 +0200 (CEST)
From: Pawel Jaskorzynski <pawel@grom.mw.mil.pl>
Message-Id: <199907061905.VAA07298@grom.mw.mil.pl>
To: freebsd-stable@FreeBSD.ORG
Subject: Re: ttyv4 problems 
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Just MAKEDEV appropriate devices. See ls -l /dev/ttyv*

Pawel


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul  6 13:44:12 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from relay1.ntu-kpi.kiev.ua (oberon.ntu-kpi.kiev.ua [195.178.136.20])
	by hub.freebsd.org (Postfix) with ESMTP id 628C514EE3
	for <freebsd-stable@freebsd.org>; Tue,  6 Jul 1999 13:44:06 -0700 (PDT)
	(envelope-from jar@ptf.ntu-kpi.kiev.ua)
Received: from ally.ptf.ntu-kpi.kiev.ua (jar@eth0.ptf.ntu-kpi.kiev.ua [10.0.1.12])
          by relay1.ntu-kpi.kiev.ua (8.NYB/8.NYB) with ESMTP id XAA15903
          for <freebsd-stable@freebsd.org>; Tue, 6 Jul 1999 23:42:33 +0300 (EEST)
          (envelope-from jar@ptf.ntu-kpi.kiev.ua)
Received: (from jar@localhost)
	by ally.ptf.ntu-kpi.kiev.ua (8.9.3/PTF-1.0exp) id XAA83619;
	Tue, 6 Jul 1999 23:42:20 +0300 (EEST)
	(envelope-from jar)
Date: Tue, 6 Jul 1999 23:42:20 +0300 (EEST)
From: Yaroslav Halchinsky <jar@ptf.ntu-kpi.kiev.ua>
Message-Id: <199907062042.XAA83619@ally.ptf.ntu-kpi.kiev.ua>
To: freebsd-stable@freebsd.org
Subject: Re: ipfw
In-Reply-To: <Pine.BSF.4.10.9907061836300.21791-100000@nic.bse.bg>
Organization: Kiev Institute of Physics & Technologies
User-Agent: tin/pre-1.4-19990624 ("Dawnrazor") (UNIX) (FreeBSD/3.2-STABLE (i386))
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hristo Grigorov <hristo@bg.freebsd.org> wrote:

> Greetings,

> I set 'ipfw pipe 11 config bw 3Mbit/sec'
> Sample output from 'ipfw pipe show 11':

> 00011:   3.000 Mbit/s   0 ms ...

> Well, I didn't set default delay but actually there
> is a delay ? It just can't be 0 ms !
> At least CISCO routers auto-calculate what the delay is.

> So, could you please tell me how to calculate the delay for
> each pipe and I'll try to hack ipfw.c myself...

ip_dummynet.c in fact. And take a look at struct dn_pkt in ip_dummynet.h

-- 
Regards,
Yaroslav Halchinsky


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul  6 14:51:17 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134])
	by hub.freebsd.org (Postfix) with ESMTP id 55AAC14E0F
	for <freebsd-stable@FreeBSD.ORG>; Tue,  6 Jul 1999 14:51:14 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Received: from localhost (doug@localhost)
	by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id OAA08285;
	Tue, 6 Jul 1999 14:50:59 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Date: Tue, 6 Jul 1999 14:50:59 -0700 (PDT)
From: Doug <Doug@gorean.org>
X-Sender: doug@dt054n86.san.rr.com
To: Stan Brown <stanb@awod.com>
Cc: FreeBSD Stable Mailing List <freebsd-stable@FreeBSD.ORG>
Subject: Re: ATAPI_STATIC ?
In-Reply-To: <19990705222138.AF3B614EEB@hub.freebsd.org>
Message-ID: <Pine.BSF.4.05.9907061449540.8187-100000@dt054n86.san.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 5 Jul 1999, Stan Brown wrote:

> 	Putting  together a new -STABLE mahcine today. I was choping sown the
> 	kernel to the minimum, when I noticed that the ATAPI CDROM was no
> 	longer working. Well to make a long earch short, I found out that if I
> 	left the ATAPI_STATIC out of the kernel config, the CD was not found at
> 	boot up.
> 
> 	Is this the expected behavio? If so what use is makeint this a loadable
> 	module, if it won't be found at power up?

	Yes, it's known behavior. I'm not sure what -stable branch you're
using, but I thought that the notes had been updated for 3.2-Stable...
maybe not though. 

Doug
-- 
On account of being a democracy and run by the people, we are the only
nation in the world that has to keep a government four years, no matter
what it does.
                -- Will Rogers



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul  6 15:44:27 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from dt054n86.san.rr.com (dt054n86.san.rr.com [24.30.152.134])
	by hub.freebsd.org (Postfix) with ESMTP id A12D514C32
	for <freebsd-stable@freebsd.org>; Tue,  6 Jul 1999 15:44:24 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Received: from localhost (doug@localhost)
	by dt054n86.san.rr.com (8.8.8/8.8.8) with ESMTP id PAA08570;
	Tue, 6 Jul 1999 15:44:19 -0700 (PDT)
	(envelope-from Doug@gorean.org)
Date: Tue, 6 Jul 1999 15:44:19 -0700 (PDT)
From: Doug <Doug@gorean.org>
X-Sender: doug@dt054n86.san.rr.com
To: brian@pobox.com
Cc: freebsd-stable@freebsd.org
Subject: Contributing to the project (Was: Re: Default gnome configuration)
In-Reply-To: <19990706044402.15783.rocketmail@web1006.mail.yahoo.com>
Message-ID: <Pine.BSF.4.05.9907061539110.8187-100000@dt054n86.san.rr.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Mon, 5 Jul 1999, Brian McGroarty wrote:

> Last time I tried submitting anything it was dismissed without
> even a test because D. Greenman didn't seem to want anyone else
> touching his NE2000 driver. Thus the full duplex operation
> memory size bug remains in place. Additionally, earlier offers
> at assisting ISA PNP weren't met with any kind of welcoming
> support, so I'm content to remain a user, and to continue
> developing other platforms.

	I can't speak to your previous experiences, but as someone who has
banged his head against the same brick walls I can offer you some advice.
I have found that the best way to get something noticed is to:

1. Write the code
2. Submit a PR
3. Wait a few days, then draw attention to the PR on -hackers, -current or
-stable; as appropriate. 

	This doesn't always get my stuff contributed, but it does usually
get it noticed and/or commented on. While it's true that a lot of the
developers are not open to input from very many people, in general good
ideas get noticed by someone, and the PR system leaves it in the queue so
that at some point in the future things often get done.

Hope this helps,

Doug
-- 
On account of being a democracy and run by the people, we are the only
nation in the world that has to keep a government four years, no matter
what it does.
                -- Will Rogers



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul  6 17:25:39 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157])
	by hub.freebsd.org (Postfix) with ESMTP id 8BC8C14F55
	for <stable@FreeBSD.org>; Tue,  6 Jul 1999 17:25:34 -0700 (PDT)
	(envelope-from chad@freeway.dcfinc.com)
Received: (from chad@localhost)
	by freeway.dcfinc.com (8.8.8/8.8.8) id RAA24812
	for stable@FreeBSD.org; Tue, 6 Jul 1999 17:25:32 -0700 (MST)
	(envelope-from chad)
From: "Chad R. Larson" <chad@DCFinc.com>
Message-Id: <199907070025.RAA24812@freeway.dcfinc.com>
Subject: PPP
To: stable@FreeBSD.org
Date: Tue, 6 Jul 1999 17:25:32 -0700 (MST)
Reply-To: chad@DCFinc.com
X-Mailer: ELM [version 2.4ME+ PL40 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

A friend has asked me to help him set up a box that will be:

1)  A demand dial router to his ISP
B)  A Network Address Translator for machines on his LAN

This has probably been discussed before, but would anyone with
some experience doing PPP like to pipe up with the pros and cons
of:

A)  user level PPP with the tunnel device
2)  the Kernel PPP link, with PPPD and NATD

It looks to me, at first blush, that the user space PPP program
would be easier to configure, and rolls the NAT function into
the same place.  Plus, it demand dials without external chat or
kermit scripts.  Is the performance similar?  Any other things
to look out for?

	-crl
--
Chad R. Larson (CRL15)   602-953-1392   Brother, can you paradigm?
chad@dcfinc.com         chad@larsons.org          larson1@home.net   
DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul  6 17:32: 8 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157])
	by hub.freebsd.org (Postfix) with ESMTP id EF0E7152E0
	for <stable@FreeBSD.org>; Tue,  6 Jul 1999 17:32:04 -0700 (PDT)
	(envelope-from chad@freeway.dcfinc.com)
Received: (from chad@localhost)
	by freeway.dcfinc.com (8.8.8/8.8.8) id RAA24835
	for stable@FreeBSD.org; Tue, 6 Jul 1999 17:32:03 -0700 (MST)
	(envelope-from chad)
From: "Chad R. Larson" <chad@DCFinc.com>
Message-Id: <199907070032.RAA24835@freeway.dcfinc.com>
Subject: FreeBSD toolkit breakage
To: stable@FreeBSD.org
Date: Tue, 6 Jul 1999 17:32:03 -0700 (MST)
Reply-To: chad@DCFinc.com
X-Mailer: ELM [version 2.4ME+ PL40 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I tried to install 2.2.8-1990328-STABLE on a new machine from the
release snapshot on the Toolkit CD set.

Two problems came up.  The first is that the makeflp.bat program
didn't understand it was now running in a subdirectory, and tried
to invoke things in the \tools director that wasn't there any more.
No biggie.

But biggie:  The install floppy, when told this was a CD-ROM
install, failed to find the "releases" directory (and the correct
release within it).  It instead insisted that the CD was for the
wrong release (3.1-something), and we died there.  

Lucky workaround--we stuck the CD into a handy nearby Linux machine,
and did an NFS export of /cdrom.  We then did an over-the-LAN
install via the NFS mount, which allowed us to specify the path to
the correct release.

Just a heads-up for y'all if you want to try the same thing.

	-crl
--
Chad R. Larson (CRL15)   602-953-1392   Brother, can you paradigm?
chad@dcfinc.com         chad@larsons.org          larson1@home.net   
DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul  6 18:45:23 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from mail001.mediacity.com (mail001.mediacity.com [205.216.172.9])
	by hub.freebsd.org (Postfix) with SMTP id 2EECC150E5
	for <stable@FreeBSD.ORG>; Tue,  6 Jul 1999 18:45:17 -0700 (PDT)
	(envelope-from idream@pop3.ispchannel.com)
Received: (qmail 11950 invoked from network); 7 Jul 1999 01:45:16 -0000
Received: from cm-24-142-56-197.cableco-op.ispchannel.com (HELO ?24.142.56.197?) (24.142.56.197)
  by mail001.mediacity.com with SMTP; 7 Jul 1999 01:45:16 -0000
Subject: FreeBSD toolkit breakage
Date: Tue, 6 Jul 1999 17:32:03 -0700
x-sender: idream@pop3.ispchannel.com
x-mailer: Claris Emailer 2.0v3, January 22, 1998
From: Chad R.Larson <chad@DCFinc.com>(by way of idream.com, <iDreamInColor@idream.com>)
Reply-To: "" <chad@DCFinc.com>
To: <stable@FreeBSD.ORG>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I tried to install 2.2.8-1990328-STABLE on a new machine from the
release snapshot on the Toolkit CD set.

Two problems came up.  The first is that the makeflp.bat program
didn't understand it was now running in a subdirectory, and tried
to invoke things in the \tools director that wasn't there any more.
No biggie.

But biggie:  The install floppy, when told this was a CD-ROM
install, failed to find the "releases" directory (and the correct
release within it).  It instead insisted that the CD was for the
wrong release (3.1-something), and we died there.  

Lucky workaround--we stuck the CD into a handy nearby Linux machine,
and did an NFS export of /cdrom.  We then did an over-the-LAN
install via the NFS mount, which allowed us to specify the path to
the correct release.

Just a heads-up for y'all if you want to try the same thing.

	-crl
--
Chad R. Larson (CRL15)   602-953-1392   Brother, can you paradigm?
chad@dcfinc.com         chad@larsons.org          larson1@home.net   
DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul  6 18:46: 1 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from mail001.mediacity.com (mail001.mediacity.com [205.216.172.9])
	by hub.freebsd.org (Postfix) with SMTP id 6120015440
	for <stable@FreeBSD.ORG>; Tue,  6 Jul 1999 18:45:52 -0700 (PDT)
	(envelope-from idream@pop3.ispchannel.com)
Received: (qmail 13803 invoked from network); 7 Jul 1999 01:45:51 -0000
Received: from cm-24-142-56-197.cableco-op.ispchannel.com (HELO ?24.142.56.197?) (24.142.56.197)
  by mail001.mediacity.com with SMTP; 7 Jul 1999 01:45:51 -0000
Subject: PPP
Date: Tue, 6 Jul 1999 17:25:32 -0700
x-sender: idream@pop3.ispchannel.com
x-mailer: Claris Emailer 2.0v3, January 22, 1998
From: Chad R.Larson <chad@DCFinc.com>(by way of idream.com, <iDreamInColor@idream.com>)
Reply-To: "Chad R. Larson" <chad@DCFinc.com>
To: <stable@FreeBSD.ORG>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

A friend has asked me to help him set up a box that will be:

1)  A demand dial router to his ISP
B)  A Network Address Translator for machines on his LAN

This has probably been discussed before, but would anyone with
some experience doing PPP like to pipe up with the pros and cons
of:

A)  user level PPP with the tunnel device
2)  the Kernel PPP link, with PPPD and NATD

It looks to me, at first blush, that the user space PPP program
would be easier to configure, and rolls the NAT function into
the same place.  Plus, it demand dials without external chat or
kermit scripts.  Is the performance similar?  Any other things
to look out for?

	-crl
--
Chad R. Larson (CRL15)   602-953-1392   Brother, can you paradigm?
chad@dcfinc.com         chad@larsons.org          larson1@home.net   
DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul  6 21: 2:32 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from tsolab.org (dnl.rockefeller.edu [129.85.17.127])
	by hub.freebsd.org (Postfix) with ESMTP id 5857D14F14
	for <stable@FreeBSD.ORG>; Tue,  6 Jul 1999 21:02:23 -0700 (PDT)
	(envelope-from dan@tsolab.org)
Received: from tsolab.org (ts018d21.hil-ny.concentric.net [206.173.18.129])
	by tsolab.org (8.8.8/8.8.8) with SMTP id AAA09206;
	Wed, 7 Jul 1999 00:06:18 -0400 (EDT)
	(envelope-from dan@tsolab.org)
Message-ID: <3782D0C8.B26A8A1B@tsolab.org>
Date: Wed, 07 Jul 1999 00:00:08 -0400
From: Daniel Tso <dan@tsolab.org>
X-Mailer: Mozilla 4.05 [en] (Win95; U)
MIME-Version: 1.0
To: "Chad R. Larson" <chad@DCFinc.com>
Cc: stable@FreeBSD.ORG
Subject: Re: PPP
References: <bulk.84459.19990706184601@hub.freebsd.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> A friend has asked me to help him set up a box that will be:
> 
> 1)  A demand dial router to his ISP
> B)  A Network Address Translator for machines on his LAN
> 
> This has probably been discussed before, but would anyone with
> some experience doing PPP like to pipe up with the pros and cons
> of:
> 
> A)  user level PPP with the tunnel device
> 2)  the Kernel PPP link, with PPPD and NATD
> 
> It looks to me, at first blush, that the user space PPP program
> would be easier to configure, and rolls the NAT function into
> the same place.  Plus, it demand dials without external chat or
> kermit scripts.  Is the performance similar?  Any other things
> to look out for?

I have been doing this with method A: user PPP with builtin aliasing.

With a 33.3K modem (28K connects) or 56K modem (50.3K connects). user
PPP on a 486/66 easily saturates the line, with about 30% CPU usage.

Pretty easy to set up...


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul  6 22:22:45 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from one.orenda.com.my (one.orenda.com.my [202.185.206.8])
	by hub.freebsd.org (Postfix) with ESMTP id A890614D5A
	for <stable@FreeBSD.ORG>; Tue,  6 Jul 1999 22:22:35 -0700 (PDT)
	(envelope-from azmansl@xkt.org)
Received: from a (az486pc [10.1.1.6])
	by one.orenda.com.my (8.8.8/8.8.8) with SMTP id NAA07998
	for <stable@FreeBSD.ORG>; Wed, 7 Jul 1999 13:22:34 +0800 (MYT)
	(envelope-from azmansl@orenda.com.my)
Message-ID: <001801bec838$b855b120$0601010a@a>
From: "azmansl" <azmansl@xkt.org>
To: <stable@FreeBSD.ORG>
Subject: Wrong SCSI disk size.
Date: Wed, 7 Jul 1999 13:21:18 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2014.203
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.203
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I cvsup 3.2-stable yesterday. Now the boot time messages gave a
wrong size for my SCSI disk, although the drive parameters remain
the same. Where to start looking? Is this something to do with
the new code?


---new dmesg-----
da0 at ahc0 bus 0 target 1 lun 0
da0: <SEAGATE ST34573LC 6246> Fixed Direct Access SCSI-2 device
da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged
Queueing Enabled
da0: 244MB (8888924 512 byte sectors: 255H 63S/T 553C)
^^^^^^^^^^^^^^^^
da1 at ahc0 bus 0 target 2 lun 0
da1: <SEAGATE ST34573LC 6246> Fixed Direct Access SCSI-2 device
da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged
Queueing Enabled
da1: 244MB (8888924 512 byte sectors: 255H 63S/T 553C)

---old dmesg------
da0 at ahc0 bus 0 target 1 lun 0
da0: <SEAGATE ST34573LC 6246> Fixed Direct Access SCSI-2 device
da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged
Queueing Enabled
da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C)
da1 at ahc0 bus 0 target 2 lun 0
da1: <SEAGATE ST34573LC 6246> Fixed Direct Access SCSI-2 device
da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged
Queueing Enabled
da1: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C)





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Tue Jul  6 22:54:42 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.cpip.net.cn (unknown [210.73.64.200])
	by hub.freebsd.org (Postfix) with ESMTP id 10D6814BD2
	for <freebsd-stable@FreeBSD.ORG>; Tue,  6 Jul 1999 22:54:33 -0700 (PDT)
	(envelope-from cqq@capinfo.com.cn)
Received: from capinfo.com.cn ([210.73.64.229]) by mail.cpip.net.cn
          (Netscape Messaging Server 3.01)  with ESMTP id AAA29127
          for <freebsd-stable@FreeBSD.ORG>; Wed, 7 Jul 1999 13:53:20 +0900
Message-ID: <3782EB92.493FB9F7@capinfo.com.cn>
Date: Wed, 07 Jul 1999 13:54:26 +0800
From: cqq@capinfo.com.cn
Reply-To: cqq@capinfo.com.cn
Organization: =?iso-8859-1?Q?=CA=D7=B6=BC=D0=C5=CF=A2=B7=A2=D5=B9=D3=D0=CF=DE=B9=AB=CB=BE?=
X-Mailer: Mozilla 4.61 [en] (Win95; I)
X-Accept-Language: zh-CN,en
MIME-Version: 1.0
To: freebsd-stable@FreeBSD.ORG
Subject: (no subject)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

auth f8b8dd4d subscribe freebsd-stable cqq@capinfo.com.cn



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7  1:14:22 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from expnet.net (c879583-a.ptbrg1.sfba.home.com [24.1.122.24])
	by hub.freebsd.org (Postfix) with ESMTP id D219A15003
	for <freebsd-stable@FreeBSD.ORG>; Wed,  7 Jul 1999 01:14:14 -0700 (PDT)
	(envelope-from noc@expnet.net)
Received: from briang [10.28.245.83] by expnet.net
  (SMTPD32-5.01) id AD4521A016A; Wed, 07 Jul 1999 01:18:13 PDT
Message-ID: <002e01bec850$078d6b40$53f51c0a@expnet.net>
From: "Brian Gallucci" <noc@expnet.net>
To: <freebsd-stable@FreeBSD.ORG>
Subject: Load Balancing !!
Date: Wed, 7 Jul 1999 01:09:25 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_002B_01BEC815.5AE24800"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This is a multi-part message in MIME format.

------=_NextPart_000_002B_01BEC815.5AE24800
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I trying to figure out if I can do load balancing with FreeBSD 2.2.7 =
this is what I'm trying to do >

|-------------------|
| Corp Office  |
|-------------------|
  |1.1Mbps     | 1.1Mbps
  |SDSL        | SDSL
  |                 |
  |                 |
  |                 |
  |                 |
  | 209.x.x.x  | 209.xx.xx.xx
 |-----------------------------|
 | Branch Office         |
 | 25 Users                |
 | Running FreeBSD 2.2.7 w/NATD
 |------------------------------|
      |
      |
      |=20
      |
      | 10.xx.xx.xx
|-------------------|
|   Users       |
|-------------------|
=20
So my question is if I have three network cards in the BSD box running =
NATD
fxp0 =3D 209.x.x.x / 19
fxp1 =3D 209.x.x.x / 19
tl0 =3D 10.x.x.x / 24
can it do load balancing on nic 1 & 2 ?

And if so where can I get some information on it ?
=20
Thanks
-Brian

------=_NextPart_000_002B_01BEC815.5AE24800
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>
<DIV><FONT size=3D2>I trying to figure out if I can do load balancing =
with FreeBSD=20
2.2.7 this is what I'm trying to do &gt;</FONT></DIV>
<DIV><FONT size=3D2>
<DIV><FONT size=3D2><BR>|-------------------|<BR>| Corp=20
Office&nbsp;&nbsp;|<BR>|-------------------|<BR>&nbsp;=20
|1.1Mbps&nbsp;&nbsp;&nbsp;&nbsp; | 1.1Mbps<BR>&nbsp;=20
|SDSL&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | SDSL<BR>&nbsp;=20
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;=20
|<BR>&nbsp;=20
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;=20
|<BR>&nbsp;=20
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;=20
|<BR>&nbsp;=20
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;=20
|<BR>&nbsp; | 209.x.x.x&nbsp; |=20
209.xx.xx.xx<BR>&nbsp;|-----------------------------|<BR>&nbsp;| Branch=20
Office&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>&nbsp;| 25=20
Users&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;=20
|<BR>&nbsp;| Running FreeBSD 2.2.7=20
w/NATD<BR>&nbsp;|------------------------------|<BR>&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;=20
|<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
|=20
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | =

10.xx.xx.xx<BR>|-------------------|<BR>|&nbsp;&nbsp;=20
Users&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=20
|<BR>|-------------------|</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>So my question is if I have three network cards in =
the BSD box=20
running NATD</FONT></DIV>
<DIV><FONT size=3D2>fxp0 =3D 209.x.x.x / 19<BR>fxp1 =3D 209.x.x.x / =
19</FONT></DIV>
<DIV><FONT size=3D2>tl0 =3D 10.x.x.x / 24</FONT></DIV>
<DIV><FONT size=3D2>can it do load balancing on nic 1 &amp; 2 =
?</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>And if so where can I get some information on it ?</DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Thanks</FONT></DIV>
<DIV><FONT =
size=3D2>-Brian</DIV></FONT></FONT></DIV></FONT></DIV></BODY></HTML>

------=_NextPart_000_002B_01BEC815.5AE24800--



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7  1:25:10 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from staff.cs.usyd.edu.au (staff.cs.usyd.edu.au [129.78.8.1])
	by hub.freebsd.org (Postfix) with SMTP id 26ACF150A4
	for <freebsd-stable@freebsd.org>; Wed,  7 Jul 1999 01:25:00 -0700 (PDT)
	(envelope-from mhenry@hons.cs.usyd.edu.au)
Subject: Re: Load Balancing !!
To: freebsd-stable@freebsd.org
Date: Wed, 7 Jul 1999 18:24:58 +1000 (EST)
From: "Michael Henry" <mhenry@hons.cs.usyd.edu.au>
In-Reply-To: <002e01bec850$078d6b40$53f51c0a@expnet.net> from "Brian Gallucci" at Jul 7, 99 01:09:25 am
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 989       
Message-Id: <19990707082503.26ACF150A4@hub.freebsd.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Take a look at http://www.coyotepoint.com/


> 
> I trying to figure out if I can do load balancing with FreeBSD 2.2.7 =
> this is what I'm trying to do >
> 
> |-------------------|
> | Corp Office  |
> |-------------------|
>   |1.1Mbps     | 1.1Mbps
>   |SDSL        | SDSL
>   |                 |
>   |                 |
>   |                 |
>   |                 |
>   | 209.x.x.x  | 209.xx.xx.xx
>  |-----------------------------|
>  | Branch Office         |
>  | 25 Users                |
>  | Running FreeBSD 2.2.7 w/NATD
>  |------------------------------|
>       |
>       |
>       |=20
>       |
>       | 10.xx.xx.xx
> |-------------------|
> |   Users       |
> |-------------------|
> =20
> So my question is if I have three network cards in the BSD box running =
> NATD
> fxp0 =3D 209.x.x.x / 19
> fxp1 =3D 209.x.x.x / 19
> tl0 =3D 10.x.x.x / 24
> can it do load balancing on nic 1 & 2 ?
> 
> And if so where can I get some information on it ?
> =20
> Thanks
> -Brian




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7  1:25:54 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73])
	by hub.freebsd.org (Postfix) with ESMTP id BF0D215386
	for <stable@freebsd.org>; Wed,  7 Jul 1999 01:25:51 -0700 (PDT)
	(envelope-from davids@webmaster.com)
Received: from whenever ([209.133.29.2]) by shell.webmaster.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35)
          with SMTP id com for <stable@freebsd.org>;
          Wed, 7 Jul 1999 01:25:50 -0700
From: "David Schwartz" <davids@webmaster.com>
To: <stable@freebsd.org>
Subject: PPS API change assert/clear
Date: Wed, 7 Jul 1999 01:25:50 -0700
Message-ID: <000201bec852$521b8000$021d85d1@youwant.to>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


	It seems that the logic of assert and clear have changed. Now an assertion
of DCD is considered a clear, and vice-versa. Why was the logic broken?

	DS



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7  3: 2:36 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58])
	by hub.freebsd.org (Postfix) with ESMTP id 236CF14C8D
	for <stable@FreeBSD.ORG>; Wed,  7 Jul 1999 03:02:24 -0700 (PDT)
	(envelope-from jhay@zibbi.mikom.csir.co.za)
Received: (from jhay@localhost)
	by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id MAA97699;
	Wed, 7 Jul 1999 12:02:09 +0200 (SAT)
	(envelope-from jhay)
From: John Hay <jhay@mikom.csir.co.za>
Message-Id: <199907071002.MAA97699@zibbi.mikom.csir.co.za>
Subject: Re: PPS API change assert/clear
In-Reply-To: <000201bec852$521b8000$021d85d1@youwant.to> from David Schwartz at "Jul 7, 1999 01:25:50 am"
To: davids@webmaster.com (David Schwartz)
Date: Wed, 7 Jul 1999 12:02:09 +0200 (SAT)
Cc: stable@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> 
> 	It seems that the logic of assert and clear have changed. Now an assertion
> of DCD is considered a clear, and vice-versa. Why was the logic broken?
> 

The PPSAPI draft was clarified and we were the odd ones out, so we changed
to be compatable to the rest.

If you are using the Oncore driver, you can just add a line "CLEAR" to
your /etc/ntp.oncore config file and all would be well again. It you
are using one of the other drivers that use the PPSAPI through
refclock_gtlin(), I have a patch to make it configurable from ntp.conf.
Email me and I'll send it to you. With a bit of luck it should make it
into the next version of ntp.

John
-- 
John Hay -- John.Hay@mikom.csir.co.za


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7  7: 2:14 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from freebsd.hagens.ab.ca (ppp4.heartland.ab.ca [207.107.228.132])
	by hub.freebsd.org (Postfix) with ESMTP
	id 81A0614C01; Wed,  7 Jul 1999 07:02:08 -0700 (PDT)
	(envelope-from darren@telusplanet.net)
Received: from darren.hagens.ab.ca ([10.0.1.3])
	by freebsd.hagens.ab.ca (8.9.2/8.9.2) with ESMTP id HAA05906;
	Wed, 7 Jul 1999 07:11:23 -0600 (MDT)
	(envelope-from darren@telusplanet.net)
Date: Wed, 7 Jul 1999 08:03:16 +0000 (GMT)
From: dkwiebe <darren@telusplanet.net>
X-Sender: darren@darren.hagens.ab.ca
To: owner-freebsd-stable@FreeBSD.ORG
Cc: stable@FreeBSD.ORG
Subject: Re: PPP
In-Reply-To: <bulk.84459.19990706184601@hub.freebsd.org>
Message-ID: <Pine.BSF.4.05.9907070800230.41889-100000@darren.hagens.ab.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



On Tue, 6 Jul 1999 owner-freebsd-stable@FreeBSD.ORG wrote:

> It looks to me, at first blush, that the user space PPP program
> would be easier to configure, and rolls the NAT function into
> the same place.  Plus, it demand dials without external chat or
> kermit scripts.  Is the performance similar?  Any other things
> to look out for?
> 
I found the ppp program very easy to setup.  I am using a 56k modem
running on a P100.  The computer also acts as a print server.  I have been
very satisfied with how easy it was to setup.

Darren Wiebe
dkwiebe@hagenhomes.com



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7  9:21:31 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from out0.mx.skynet.be (out0.mx.skynet.be [195.238.2.35])
	by hub.freebsd.org (Postfix) with ESMTP id 616B014F0B
	for <freebsd-stable@freebsd.org>; Wed,  7 Jul 1999 09:21:18 -0700 (PDT)
	(envelope-from brad@shub-internet.org)
Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121])
	by out0.mx.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id SAA10546;
	Wed, 7 Jul 1999 18:20:53 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: brad@mail.his.com
Message-Id: <v04205512b3a92c813715@[195.238.1.121]>
Date: Wed, 7 Jul 1999 18:20:32 +0200
To: freebsd-stable@freebsd.org
From: Brad Knowles <brad@shub-internet.org>
Subject: Does vinum actually currently build under 3.2-STABLE?
Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>,
	Greg Lehey <grog@lemis.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Folks,

	I know a little while back that Poul-Henning Kamp had suggested 
some changes to vinum that would get it to compile (in 3.2-STABLE?), 
and I've seen some recent traffic on -current to indicate that there 
were some other minor problems keeping vinum from building with 
FreeBSD 4.0-CURRENT.

	The problems with FreeBSD 4.0-CURRENT appear to have been cleared 
up by Greg committing one additional file to CVS.  However, I am not 
exactly clear on whether vinum is currently supposed to build 
out-of-the-box with 3.2-STABLE, either with the provided code 
(apparently dated 5 May) or with the tarball at 
<ftp://ftp.lemis.com/pub/vinum/vinum-4.0-CURRENT.tar.gz> (dated 11 
May).


	The reason that I ask is that I've got a new server that I'm 
setting up (pretty honkin' w/ a PIII@450Mhz and 1GB RAM), and I've 
just benchmarked it with Greg's "rawio" program.

	However, that was with the four IBM Ultrastar 9LZX 10kRPM drives 
connected through a DPT SmartRAID IV controller (the drivers still 
aren't out yet for the SmartRAID V) with 64MB cache and 128KB stripe 
size (automatically selected when the card was configured for maximum 
performance).  I'd now like to see how this system performs with an 
Adaptec 3950U2 and vinum, attached to the same drives.


	Anyway, any answers you can provide would be appreciated.  In 
particular, since I am not subscribed to the -stable mailing list, I 
would appreciate at least being cc'ed on any response you may have 
that goes back to the list.\


	TIA!

-- 
Brad Knowles <brad@shub-internet.org> <http://www.shub-internet.org/brad/>
     <http://wwwkeys.pgp.net:11371/pks/lookup?op=get&search=0xE38CCEF1>

Your mouse has moved.   Windows NT must be restarted for the change to
take effect.   Reboot now?  [ OK ]


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7  9:52:32 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132])
	by hub.freebsd.org (Postfix) with ESMTP id CBEDC15473
	for <freebsd-stable@FreeBSD.ORG>; Wed,  7 Jul 1999 09:52:26 -0700 (PDT)
	(envelope-from Thierry.Herbelot@alcatel.fr)
Received: from aifhs2.alcatel.fr (mailhub.alcatel.fr [155.132.180.80])
        by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id RAA07998;
        Wed, 7 Jul 1999 17:48:48 +0200
Received: from lune.telspace.alcatel.fr (lune.telspace.alcatel.fr [155.132.144.65])
        by aifhs2.alcatel.fr (ALCANET/SMTP2) with ESMTP id SAA03398;
        Wed, 7 Jul 1999 18:46:21 +0200 (MET DST)
Received: from telss1 (telss1.telspace.alcatel.fr [155.132.51.4])
	by lune.telspace.alcatel.fr (8.9.1a/8.9.1) with ESMTP id SAA24206;
	Wed, 7 Jul 1999 18:30:40 +0200 (MEST)
Received: from telspace.alcatel.fr by telss1 (8.8.8+Sun/SMI-SVR4)
	id SAA23038; Wed, 7 Jul 1999 18:37:32 +0200 (MET DST)
Message-ID: <378382DB.5459E1AC@telspace.alcatel.fr>
Date: Wed, 07 Jul 1999 18:39:55 +0200
From: Thierry Herbelot <Thierry.Herbelot@alcatel.fr>
Organization: ALCATEL CIT Nanterre
X-Mailer: Mozilla 4.5 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Brad Knowles <brad@shub-internet.org>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Does vinum actually currently build under 3.2-STABLE?
References: <v04205512b3a92c813715@[195.238.1.121]>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

YES, vinum builds and works fine under 3.2-S (I'm using it with two IDE
drives)

	TfH

Brad Knowles wrote:
> 
> Folks,
> 
>         I know a little while back that Poul-Henning Kamp had suggested
> some changes to vinum that would get it to compile (in 3.2-STABLE?),
> and I've seen some recent traffic on -current to indicate that there
> were some other minor problems keeping vinum from building with
> FreeBSD 4.0-CURRENT.
> 
>         The problems with FreeBSD 4.0-CURRENT appear to have been cleared
> up by Greg committing one additional file to CVS.  However, I am not
> exactly clear on whether vinum is currently supposed to build
> out-of-the-box with 3.2-STABLE, either with the provided code
> (apparently dated 5 May) or with the tarball at
> <ftp://ftp.lemis.com/pub/vinum/vinum-4.0-CURRENT.tar.gz> (dated 11
> May).
> 
>         The reason that I ask is that I've got a new server that I'm
> setting up (pretty honkin' w/ a PIII@450Mhz and 1GB RAM), and I've
> just benchmarked it with Greg's "rawio" program.
> 
>         However, that was with the four IBM Ultrastar 9LZX 10kRPM drives
> connected through a DPT SmartRAID IV controller (the drivers still
> aren't out yet for the SmartRAID V) with 64MB cache and 128KB stripe
> size (automatically selected when the card was configured for maximum
> performance).  I'd now like to see how this system performs with an
> Adaptec 3950U2 and vinum, attached to the same drives.
> 
>         Anyway, any answers you can provide would be appreciated.  In
> particular, since I am not subscribed to the -stable mailing list, I
> would appreciate at least being cc'ed on any response you may have
> that goes back to the list.\
> 
>         TIA!
> 
> --
> Brad Knowles <brad@shub-internet.org> <http://www.shub-internet.org/brad/>
>      <http://wwwkeys.pgp.net:11371/pks/lookup?op=get&search=0xE38CCEF1>
> 
> Your mouse has moved.   Windows NT must be restarted for the change to
> take effect.   Reboot now?  [ OK ]
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7 11:42:43 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145])
	by hub.freebsd.org (Postfix) with ESMTP id B13FC14D7D
	for <freebsd-stable@freebsd.org>; Wed,  7 Jul 1999 11:42:40 -0700 (PDT)
	(envelope-from daeron@Wit401305.student.utwente.nl)
Received: from localhost (daeron@localhost)
	by shadowmere.student.utwente.nl (8.9.3/8.9.3) with ESMTP id UAA01380
	for <freebsd-stable@freebsd.org>; Wed, 7 Jul 1999 20:42:39 +0200 (CEST)
	(envelope-from daeron@Wit401305.student.utwente.nl)
Date: Wed, 7 Jul 1999 20:42:39 +0200 (CEST)
From: Pascal Hofstee <daeron@Wit401305.student.utwente.nl>
To: freebsd-stable@freebsd.org
Subject: Macronix driver bugs ?
Message-ID: <Pine.BSF.4.10.9907072042110.1367-100000@shadowmere.student.utwente.nl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Hi,

I today tried to upgrade my SMC-8216 Elita Ultra ethernet card to a nice
Macronix 98713 card a friend of mine had lying around.

It's a FreeBSD-3.2-STABLE system cvsupped and buildworld today (July 7th)

I checked the LINT file for support and found the following:
device mx0

After rebuilding my kernel and ensuring etc/rc.conf contained the proper
settings for the network card ... (changing all the ed0 references to mx0)
I found that my system would always lock up somewhere during the
boot-phase or when it even passed that it would lock up during starting
xdm.

I had it lock up my system completely during PCI-probing once (before
detecting vga0), during network configuration ... hostname, ifconfig or
starting of network services like samba e.g.

--------------------
  Pascal Hofstee - daeron@shadowmere.student.utwente.nl

-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP--
t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+
------END GEEK CODE BLOCK------




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7 11:50: 2 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73])
	by hub.freebsd.org (Postfix) with ESMTP id 3937014D7D
	for <stable@FreeBSD.ORG>; Wed,  7 Jul 1999 11:49:58 -0700 (PDT)
	(envelope-from davids@webmaster.com)
Received: from whenever ([209.133.29.2]) by shell.webmaster.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35)
          with SMTP id com; Wed, 7 Jul 1999 11:49:57 -0700
From: "David Schwartz" <davids@webmaster.com>
To: "John Hay" <jhay@mikom.csir.co.za>
Cc: <stable@FreeBSD.ORG>
Subject: RE: PPS API change assert/clear
Date: Wed, 7 Jul 1999 11:49:57 -0700
Message-ID: <000a01bec8a9$8237dd40$021d85d1@youwant.to>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
In-Reply-To: <199907071002.MAA97699@zibbi.mikom.csir.co.za>
Importance: Normal
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> >
> > 	It seems that the logic of assert and clear have changed.
> Now an assertion
> > of DCD is considered a clear, and vice-versa. Why was the logic broken?
> >
>
> The PPSAPI draft was clarified and we were the odd ones out, so we changed
> to be compatable to the rest.

	That makes no sense. I know Linux is currently the same way FreeBSD was.
Can you send me a copy of this 'clarification'?

	I can't understand how this can possibly make sense. I now get a 'CLEAR'
event whenever I assert DCD and an 'ASSERT' event whenever I clear DCD.

	DS



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7 11:54:18 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73])
	by hub.freebsd.org (Postfix) with ESMTP id 861C815457
	for <freebsd-stable@freebsd.org>; Wed,  7 Jul 1999 11:54:15 -0700 (PDT)
	(envelope-from davids@webmaster.com)
Received: from whenever ([209.133.29.2]) by shell.webmaster.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35)
          with SMTP id com; Wed, 7 Jul 1999 11:54:14 -0700
From: "David Schwartz" <davids@webmaster.com>
To: "Pascal Hofstee" <daeron@Wit401305.student.utwente.nl>,
	<freebsd-stable@freebsd.org>
Subject: RE: Macronix driver bugs ?
Date: Wed, 7 Jul 1999 11:54:14 -0700
Message-ID: <000e01bec8aa$1b938200$021d85d1@youwant.to>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
In-Reply-To: <Pine.BSF.4.10.9907072042110.1367-100000@shadowmere.student.utwente.nl>
Importance: Normal
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


	I've had a lot of problems with MX98713 cards and FreeBSD-stable. None were
as bad as what you report. But I finally decided to either run the cards at
10Mbps (which seems to work fine for me) or replace the cards with others
and put the 98713 cards in the NT machines.

	For what it's worth, I've had very similar problems with 98713 cards under
Linux too -- about 6 months before I had them with FreeBSD. And one Windows
98 machine caused my hub's collision rate to go through the roof with a
98713 card.

	The most common problem I have is incredibly lousy network performance. The
second most common problem is the transmitter simply 'stopping', recovering
only if I do an 'ifconfig down' folloed by an 'ifconfig up'.

	One odd sympton is that if you log into the machine and ping to any other
machine on the LAN, after about 8 packets, you'll start seeing duplicates of
old packets. It seems that, among other things, it's receiving some packets
twice.

	The 98713 is just bad, in my experience. Throw them out and buy new ones
(or give them to your 'friends'). The money you spend will be made up for by
the time you save.

	DS

> Hi,
>
> I today tried to upgrade my SMC-8216 Elita Ultra ethernet card to a nice
> Macronix 98713 card a friend of mine had lying around.
>
> It's a FreeBSD-3.2-STABLE system cvsupped and buildworld today (July 7th)
>
> I checked the LINT file for support and found the following:
> device mx0
>
> After rebuilding my kernel and ensuring etc/rc.conf contained the proper
> settings for the network card ... (changing all the ed0 references to mx0)
> I found that my system would always lock up somewhere during the
> boot-phase or when it even passed that it would lock up during starting
> xdm.
>
> I had it lock up my system completely during PCI-probing once (before
> detecting vga0), during network configuration ... hostname, ifconfig or
> starting of network services like samba e.g.
>
> --------------------
>   Pascal Hofstee - daeron@shadowmere.student.utwente.nl
>
> -----BEGIN GEEK CODE BLOCK-----
> Version: 3.1
> GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+
> PE Y-- PGP--
> t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+
> ------END GEEK CODE BLOCK------
>
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
>



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7 11:58:50 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73])
	by hub.freebsd.org (Postfix) with ESMTP id A3D3815473
	for <stable@FreeBSD.ORG>; Wed,  7 Jul 1999 11:58:46 -0700 (PDT)
	(envelope-from davids@webmaster.com)
Received: from whenever ([209.133.29.2]) by shell.webmaster.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35)
          with SMTP id com; Wed, 7 Jul 1999 11:58:44 -0700
From: "David Schwartz" <davids@webmaster.com>
To: "John Hay" <jhay@mikom.csir.co.za>
Cc: <stable@FreeBSD.ORG>
Subject: RE: PPS API change assert/clear
Date: Wed, 7 Jul 1999 11:58:44 -0700
Message-ID: <000f01bec8aa$bc9bb870$021d85d1@youwant.to>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
In-Reply-To: <000a01bec8a9$8237dd40$021d85d1@youwant.to>
Importance: Normal
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


	Wow. It seems you're right. This still makes no sense to me, but it does
seem to be the standard!

	When DCD is asserted, you will get a clear event. When DCD is cleared, you
will get an assert event. Go figure:

   A PPS signal consists of a series of pulses, each with an
   ``asserted'' (logical true) phase, and a ``clear'' (logical false)
   phase.  The two phases may be of different lengths.  The API may
   capture an ``assert timestamp'' at the moment of the transition into
   the asserted phase, and a ``clear timestamp'' at the moment of the
   transition into the clear phase.

   The specific assignment of the logical values ``true'' and ``false''
   with specific voltages of a PPS signal, if applicable, is outside the
   scope of this specification.  However, these assignments SHOULD be
   consistent with applicable standards.  Implementors of PPS sources
   SHOULD document these assignments.

      ---------
      Reminder to implementors of DCD-based PPS support:  TTL and
      RS-232C (V.24/V.28) interfaces both define the "true" state as
      the one having the highest positive voltage. TTL defines a
      nominal absence of voltage as the "false" state, but RS-232C
      (V.24/V.28) defines the "false" state by the presence of a
      negative voltage.
      ---------

	DS

> > >
> > > 	It seems that the logic of assert and clear have changed.
> > Now an assertion
> > > of DCD is considered a clear, and vice-versa. Why was the
> logic broken?
> > >
> >
> > The PPSAPI draft was clarified and we were the odd ones out, so
> we changed
> > to be compatable to the rest.
>
> 	That makes no sense. I know Linux is currently the same way
> FreeBSD was.
> Can you send me a copy of this 'clarification'?
>
> 	I can't understand how this can possibly make sense. I now
> get a 'CLEAR'
> event whenever I assert DCD and an 'ASSERT' event whenever I clear DCD.
>
> 	DS



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7 12: 1:51 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from alice.gba.oz.au (gba-254.tmx.com.au [203.9.155.254])
	by hub.freebsd.org (Postfix) with SMTP id 3C3A414C99
	for <stable@FreeBSD.ORG>; Wed,  7 Jul 1999 12:01:40 -0700 (PDT)
	(envelope-from gjb-freebsd@gba.oz.au)
Received: (qmail 12178 invoked by uid 1001); 7 Jul 1999 19:06:04 +1000
Message-ID: <19990707090604.12177.qmail@alice.gba.oz.au>
X-Posted-By: GBA-Post 1.03 20-Sep-1998
X-PGP-Fingerprint: 5A91 6942 8CEA 9DAB B95B  C249 1CE1 493B 2B5A CE30
Date: Wed, 07 Jul 1999 19:06:03 +1000
From: Greg Black <gjb-freebsd@gba.oz.au>
To: "Chad R. Larson" <chad@DCFinc.com>
Cc: stable@FreeBSD.ORG
Subject: Re: PPP 
References: <bulk.84459.19990706184601@hub.freebsd.org> 
In-reply-to: <bulk.84459.19990706184601@hub.freebsd.org> 
    of Tue, 06 Jul 1999 17:25:32 MST
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> A)  user level PPP with the tunnel device
> 2)  the Kernel PPP link, with PPPD and NATD
> 
> It looks to me, at first blush, that the user space PPP program
> would be easier to configure, and rolls the NAT function into
> the same place.  Plus, it demand dials without external chat or
> kermit scripts.  Is the performance similar?  Any other things
> to look out for?

The kernel ppp implementation is broken in a few ways and seems
not to be receiving the same development attention as the user
ppp.  I have found that user ppp seems to work just as you'd
expect without any dramas.

-- 
Greg Black -- <gjb@acm.org> or <gjb@computer.org>
Fight censorship in Australia: <http://www.efa.org.au>



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7 12: 2:53 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from shadowmere.student.utwente.nl (wit401305.student.utwente.nl [130.89.236.145])
	by hub.freebsd.org (Postfix) with ESMTP id B7FA714C99
	for <freebsd-stable@FreeBSD.ORG>; Wed,  7 Jul 1999 12:02:50 -0700 (PDT)
	(envelope-from daeron@Wit401305.student.utwente.nl)
Received: from localhost (daeron@localhost)
	by shadowmere.student.utwente.nl (8.9.3/8.9.3) with ESMTP id VAA16753;
	Wed, 7 Jul 1999 21:02:45 +0200 (CEST)
	(envelope-from daeron@Wit401305.student.utwente.nl)
Date: Wed, 7 Jul 1999 21:02:45 +0200 (CEST)
From: Pascal Hofstee <daeron@Wit401305.student.utwente.nl>
To: David Schwartz <davids@webmaster.com>
Cc: Pascal Hofstee <daeron@Wit401305.student.utwente.nl>,
	freebsd-stable@FreeBSD.ORG
Subject: RE: Macronix driver bugs ?
In-Reply-To: <000e01bec8aa$1b938200$021d85d1@youwant.to>
Message-ID: <Pine.BSF.4.10.9907072101330.16028-100000@shadowmere.student.utwente.nl>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 7 Jul 1999, David Schwartz wrote:

> 	I've had a lot of problems with MX98713 cards and FreeBSD-stable. None were
> as bad as what you report. But I finally decided to either run the cards at
> 10Mbps (which seems to work fine for me) or replace the cards with others
> and put the 98713 cards in the NT machines.

I DO run it at 10 Mbps (half-duplex) ... but our network here gets
upgarded soon to 100 Mbps (full-duplex) .... that's why I was "hoping to
ditch the SMC"

--------------------
  Pascal Hofstee - daeron@shadowmere.student.utwente.nl

-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS d- s+: a-- C++ UB++++ P+ L- E--- W- N+ o? K- w--- O? M V? PS+ PE Y-- PGP--
t+ 5 X-- R tv+ b+ DI D- G e* h+ r- y+
------END GEEK CODE BLOCK------



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7 12:37:15 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58])
	by hub.freebsd.org (Postfix) with ESMTP id 8B14914F79
	for <stable@FreeBSD.ORG>; Wed,  7 Jul 1999 12:37:07 -0700 (PDT)
	(envelope-from jhay@zibbi.mikom.csir.co.za)
Received: (from jhay@localhost)
	by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id VAA06015;
	Wed, 7 Jul 1999 21:36:50 +0200 (SAT)
	(envelope-from jhay)
From: John Hay <jhay@mikom.csir.co.za>
Message-Id: <199907071936.VAA06015@zibbi.mikom.csir.co.za>
Subject: Re: PPS API change assert/clear
In-Reply-To: <000f01bec8aa$bc9bb870$021d85d1@youwant.to> from David Schwartz at "Jul 7, 1999 11:58:44 am"
To: davids@webmaster.com (David Schwartz)
Date: Wed, 7 Jul 1999 21:36:50 +0200 (SAT)
Cc: stable@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Do you mean that if you measure the voltage on the DCD pin and it go from
negative to positive (ASSERT) you get a CLEAR from the software? That is
wrong and not what I see here. Do you have version 1.224.2.6 of sio.c?
I know it has been broken in versions before that in stable and versions
before 1.246 in current.

John
-- 
John Hay -- John.Hay@mikom.csir.co.za

> 
> 	Wow. It seems you're right. This still makes no sense to me, but it does
> seem to be the standard!
> 
> 	When DCD is asserted, you will get a clear event. When DCD is cleared, you
> will get an assert event. Go figure:
> 
>    A PPS signal consists of a series of pulses, each with an
>    ``asserted'' (logical true) phase, and a ``clear'' (logical false)
>    phase.  The two phases may be of different lengths.  The API may
>    capture an ``assert timestamp'' at the moment of the transition into
>    the asserted phase, and a ``clear timestamp'' at the moment of the
>    transition into the clear phase.
> 
>    The specific assignment of the logical values ``true'' and ``false''
>    with specific voltages of a PPS signal, if applicable, is outside the
>    scope of this specification.  However, these assignments SHOULD be
>    consistent with applicable standards.  Implementors of PPS sources
>    SHOULD document these assignments.
> 
>       ---------
>       Reminder to implementors of DCD-based PPS support:  TTL and
>       RS-232C (V.24/V.28) interfaces both define the "true" state as
>       the one having the highest positive voltage. TTL defines a
>       nominal absence of voltage as the "false" state, but RS-232C
>       (V.24/V.28) defines the "false" state by the presence of a
>       negative voltage.
>       ---------
> 
> 	DS
> 
> > > >
> > > > 	It seems that the logic of assert and clear have changed.
> > > Now an assertion
> > > > of DCD is considered a clear, and vice-versa. Why was the
> > logic broken?
> > > >
> > >
> > > The PPSAPI draft was clarified and we were the odd ones out, so
> > we changed
> > > to be compatable to the rest.
> >
> > 	That makes no sense. I know Linux is currently the same way
> > FreeBSD was.
> > Can you send me a copy of this 'clarification'?
> >
> > 	I can't understand how this can possibly make sense. I now
> > get a 'CLEAR'
> > event whenever I assert DCD and an 'ASSERT' event whenever I clear DCD.
> >
> > 	DS


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7 12:44:10 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73])
	by hub.freebsd.org (Postfix) with ESMTP id 3FE2E14F4E
	for <stable@FreeBSD.ORG>; Wed,  7 Jul 1999 12:44:07 -0700 (PDT)
	(envelope-from davids@webmaster.com)
Received: from whenever ([209.133.29.2]) by shell.webmaster.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35)
          with SMTP id com; Wed, 7 Jul 1999 12:44:06 -0700
From: "David Schwartz" <davids@webmaster.com>
To: "John Hay" <jhay@mikom.csir.co.za>
Cc: <stable@FreeBSD.ORG>
Subject: RE: PPS API change assert/clear
Date: Wed, 7 Jul 1999 12:44:06 -0700
Message-ID: <000401bec8b1$12fba1c0$021d85d1@youwant.to>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
Importance: Normal
In-Reply-To: <199907071936.VAA06015@zibbi.mikom.csir.co.za>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> Do you mean that if you measure the voltage on the DCD pin and it go from
> negative to positive (ASSERT) you get a CLEAR from the software?

	Negative to positive is not an assertion of DCD. DCD is active low. It has
been logically asserted when the voltage goes negative.

> That is
> wrong and not what I see here. Do you have version 1.224.2.6 of sio.c?
> I know it has been broken in versions before that in stable and versions
> before 1.246 in current.

	Why is that wrong? (I know, the standard says so, but it seems to me that
the standard makes no sense.)

	When I asked Ulrich Windl, one of the authors of the standard, (but this
may be before the clarification), he said:

Me: Since DCD is active-low, is an 'ASSERT' a high-to-low transition on the
DCD pin?

Ulrich: This problem has been discussed a lot. ASSERT is from the
perspective
of the UART's register. ASSERT means the CD bit in the modem status
register has been set. Depending what your line drivers and level
converters do, the level may change.

	Ulrich gave me the answer that I expected. The one that I thought made
sense. And the Linux PPSkit that Ulrich Windl wrote works as he stated.

	It's hard for me to keep my software working when the definition keeps
changing. :/

	David Schwartz
	http://www.gpsclock.com/



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7 12:54:24 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169])
	by hub.freebsd.org (Postfix) with ESMTP id B36B615537
	for <stable@FreeBSD.ORG>; Wed,  7 Jul 1999 12:54:19 -0700 (PDT)
	(envelope-from ken@panzer.kdm.org)
Received: (from ken@localhost)
	by panzer.kdm.org (8.9.3/8.9.1) id NAA93349;
	Wed, 7 Jul 1999 13:53:52 -0600 (MDT)
	(envelope-from ken)
Message-Id: <199907071953.NAA93349@panzer.kdm.org>
Subject: Re: Wrong SCSI disk size.
In-Reply-To: <001801bec838$b855b120$0601010a@a> from azmansl at "Jul 7, 1999 01:21:18 pm"
To: azmansl@xkt.org (azmansl)
Date: Wed, 7 Jul 1999 13:53:52 -0600 (MDT)
Cc: stable@FreeBSD.ORG
From: "Kenneth D. Merry" <ken@plutotech.com>
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

azmansl wrote...
> I cvsup 3.2-stable yesterday. Now the boot time messages gave a
> wrong size for my SCSI disk, although the drive parameters remain
> the same. Where to start looking? Is this something to do with
> the new code?
> 
> 
> ---new dmesg-----
> da0 at ahc0 bus 0 target 1 lun 0
> da0: <SEAGATE ST34573LC 6246> Fixed Direct Access SCSI-2 device
> da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged
> Queueing Enabled
> da0: 244MB (8888924 512 byte sectors: 255H 63S/T 553C)
> ^^^^^^^^^^^^^^^^
> da1 at ahc0 bus 0 target 2 lun 0
> da1: <SEAGATE ST34573LC 6246> Fixed Direct Access SCSI-2 device
> da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged
> Queueing Enabled
> da1: 244MB (8888924 512 byte sectors: 255H 63S/T 553C)
> 
> ---old dmesg------
> da0 at ahc0 bus 0 target 1 lun 0
> da0: <SEAGATE ST34573LC 6246> Fixed Direct Access SCSI-2 device
> da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged
> Queueing Enabled
> da0: 4340MB (8888924 512 byte sectors: 255H 63S/T 553C)
[ ... ]

A fix was checked in today.  cvsup again and the problem should be fixed.
The problem is only cosmetic, though, and shouldn't affect the operation of
your system.

Ken
-- 
Kenneth Merry
ken@plutotech.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7 13:10:24 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52])
	by hub.freebsd.org (Postfix) with ESMTP id 69C66154BA
	for <freebsd-stable@freebsd.org>; Wed,  7 Jul 1999 13:10:16 -0700 (PDT)
	(envelope-from dbushong@CSUA.Berkeley.EDU)
Received: (from dbushong@localhost) 
	by soda.CSUA.Berkeley.EDU (8.8.8/) id NAA20074
        for freebsd-stable@freebsd.org; Wed, 7 Jul 1999 13:08:36 -0700 (PDT)
        env-from (dbushong)
From: dbushong@CSUA.Berkeley.EDU (David Bushong)
Message-Id: <199907072008.NAA20074@soda.CSUA.Berkeley.EDU>
Subject: /usr/share/misc/magic updates?
To: freebsd-stable@freebsd.org
Date: Wed, 7 Jul 1999 13:08:36 -0700 (PDT)
X-Mailer: ELM [version 2.4ME+ PL38 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I have an update to /usr/share/misc/magic I'd like to submit, but have no
clue where to send it.  Pointers?

--David Bushong


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7 13:19:45 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from easeway.com (ns1.easeway.com [209.69.39.1])
	by hub.freebsd.org (Postfix) with ESMTP id AE689154D2
	for <stable@freebsd.org>; Wed,  7 Jul 1999 13:19:36 -0700 (PDT)
	(envelope-from mwlucas@easeway.com)
Received: (from mwlucas@localhost)
	by easeway.com (8.8.8/8.8.5) id QAA02936
	for stable@freebsd.org; Wed, 7 Jul 1999 16:09:20 -0400 (EDT)
Message-Id: <199907072009.QAA02936@easeway.com>
Subject: Net_SSLeay.pm-1.03
To: stable@freebsd.org
Date: Wed, 7 Jul 1999 16:09:20 -0400 (EDT)
From: mwlucas@exceptionet.com
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello,

I'm trying to compile Net_SSLeay.pm-1.03 on a 3.2-stable system.  After
mucking with the various include files, I can get it to this point, where
it chokes & dies:

prompt#make
cc -c -I/usr/local/include/       -DVERSION=\"1.03\"
-DXS_VERSION=\"1.03\" -DPIC -fpic -I/usr/libdata/perl/5.00503/mach/CORE
SSLeay.c
In file included from /usr/local/include/openssl/evp.h:79,
                 from /usr/local/include/openssl/pem.h:66,
                 from /usr/local/include/ssl.h:151,
                 from SSLeay.xs:29:
/usr/local/include/openssl/des.h:96: #error "_ is defined, but some
strange definition the DES library cannot handle that."
/usr/local/include/openssl/des.h:98: warning: `_' redefined
/usr/libdata/perl/5.00503/mach/CORE/config.h:1149: warning: this is the
location of the previous definition
*** Error code 1

Stop.
prompt#

Any advice?

Thanks,
==ml

-- 
Michael Lucas			|
Exceptionet, Inc.		|	www.exceptionet.com
"Exceptional Networking"	|


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7 13:20:44 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58])
	by hub.freebsd.org (Postfix) with ESMTP id 95803152ED
	for <stable@FreeBSD.ORG>; Wed,  7 Jul 1999 13:20:30 -0700 (PDT)
	(envelope-from jhay@zibbi.mikom.csir.co.za)
Received: (from jhay@localhost)
	by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id WAA06678;
	Wed, 7 Jul 1999 22:20:11 +0200 (SAT)
	(envelope-from jhay)
From: John Hay <jhay@mikom.csir.co.za>
Message-Id: <199907072020.WAA06678@zibbi.mikom.csir.co.za>
Subject: Re: PPS API change assert/clear
In-Reply-To: <000401bec8b1$12fba1c0$021d85d1@youwant.to> from David Schwartz at "Jul 7, 1999 12:44:06 pm"
To: davids@webmaster.com (David Schwartz)
Date: Wed, 7 Jul 1999 22:20:11 +0200 (SAT)
Cc: jhay@mikom.csir.co.za (John Hay), stable@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Uhm, did you measure it? I just connected a modem through a breakout box
so that I can easily measure the voltages. At the start the DCD voltage
is -12V and after it has connected with carrier I have 7.5V. That seems
like a negative to positive transition for assert?

I was actually the one that started the discussion on the PPSAPI mail list
because I was also under the impression that RS232 signals are active low.
But after a lot of talking and some measurements we found that it isn't
true. Maybe you can think of it as active low if you measure between the
serial chip and the RS232 driver chip, but that is the only place where
it is active low according to my measurements.

John
-- 
John Hay -- John.Hay@mikom.csir.co.za

> 
> > Do you mean that if you measure the voltage on the DCD pin and it go from
> > negative to positive (ASSERT) you get a CLEAR from the software?
> 
> 	Negative to positive is not an assertion of DCD. DCD is active low. It has
> been logically asserted when the voltage goes negative.
> 
> > That is
> > wrong and not what I see here. Do you have version 1.224.2.6 of sio.c?
> > I know it has been broken in versions before that in stable and versions
> > before 1.246 in current.
> 
> 	Why is that wrong? (I know, the standard says so, but it seems to me that
> the standard makes no sense.)
> 
> 	When I asked Ulrich Windl, one of the authors of the standard, (but this
> may be before the clarification), he said:
> 
> Me: Since DCD is active-low, is an 'ASSERT' a high-to-low transition on the
> DCD pin?
> 
> Ulrich: This problem has been discussed a lot. ASSERT is from the
> perspective
> of the UART's register. ASSERT means the CD bit in the modem status
> register has been set. Depending what your line drivers and level
> converters do, the level may change.
> 
> 	Ulrich gave me the answer that I expected. The one that I thought made
> sense. And the Linux PPSkit that Ulrich Windl wrote works as he stated.
> 
> 	It's hard for me to keep my software working when the definition keeps
> changing. :/
> 
> 	David Schwartz
> 	http://www.gpsclock.com/
> 


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7 13:53:41 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73])
	by hub.freebsd.org (Postfix) with ESMTP id BBFF214C0A
	for <stable@FreeBSD.ORG>; Wed,  7 Jul 1999 13:53:39 -0700 (PDT)
	(envelope-from davids@webmaster.com)
Received: from whenever ([209.133.29.2]) by shell.webmaster.com
          (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35)
          with SMTP id com; Wed, 7 Jul 1999 13:53:33 -0700
From: "David Schwartz" <davids@webmaster.com>
To: "John Hay" <jhay@mikom.csir.co.za>
Cc: <stable@FreeBSD.ORG>
Subject: RE: PPS API change assert/clear
Date: Wed, 7 Jul 1999 13:53:32 -0700
Message-ID: <000001bec8ba$c65564f0$021d85d1@youwant.to>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0
In-Reply-To: <199907072020.WAA06678@zibbi.mikom.csir.co.za>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


	You are right. I just wasn't thinking clearly. Thanks.

	/me dons his pointy hat

	This one is getting worn out, I need a new one.

	David Schwartz



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7 15:28:49 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from mail1.sirius.com (mail1.sirius.com [205.134.253.131])
	by hub.freebsd.org (Postfix) with ESMTP id 714B61504D
	for <freebsd-stable@FreeBSD.ORG>; Wed,  7 Jul 1999 15:28:46 -0700 (PDT)
	(envelope-from freepix@sirius.com)
Received: from webmail.sirius.com (webmail.sirius.com [207.44.134.1])
	by mail1.sirius.com (8.9.2/8.9.1) with SMTP id PAA50348
	for <freebsd-stable@FreeBSD.ORG>; Wed, 7 Jul 1999 15:28:42 -0700 (PDT)
Message-Id: <199907072228.PAA50348@mail1.sirius.com>
To: freebsd-stable@FreeBSD.ORG
From: freepix@sirius.com
Subject: IDE Channel??
Date: Wed, 7 Jul 99 22:28:42 +0000
X-Mailer: Sirius WebMail v2.0
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I'm attempting to balance the load between my two hard drives in my server, but 
I'm not sure if they are on their own IDE channels...  The server isn't located 
in my city so I can't physically look into the case to see if they are on the 
same chain, but I thought there would be a way to identify it via FreeBSD.  One 
is named WD0 and the other is WD1 if that helps anyone...  If I left anything 
out, please e-mail me back...

Thanks
everyone..



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7 15:51:26 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from uniqsite.uniqsite.com (209-249-66-9.snj0.flashcom.net [209.249.66.9])
	by hub.freebsd.org (Postfix) with ESMTP id E09F4154DD
	for <stable@freebsd.org>; Wed,  7 Jul 1999 15:51:24 -0700 (PDT)
	(envelope-from gfish@uniqsite.com)
Received: from localhost (gfish@localhost)
	by uniqsite.uniqsite.com (8.9.2/8.8.8) with ESMTP id PAA54038
	for <stable@freebsd.org>; Wed, 7 Jul 1999 15:51:17 -0700 (PDT)
	(envelope-from gfish@uniqsite.com)
Date: Wed, 7 Jul 1999 15:51:17 -0700 (PDT)
From: Golden Fischer <gfish@uniqsite.com>
To: stable@freebsd.org
Subject: unsubscribe
Message-ID: <Pine.BSF.4.05.9907071550360.54018-100000@uniqsite.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

unsubscribe gfish@uniqsite.com




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7 16: 4: 2 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28])
	by hub.freebsd.org (Postfix) with ESMTP id E1EBF154B9
	for <freebsd-stable@FreeBSD.ORG>; Wed,  7 Jul 1999 16:03:54 -0700 (PDT)
	(envelope-from fullermd@futuresouth.com)
Received: (from fullermd@localhost)
	by shell.futuresouth.com (8.9.3/8.9.3) id SAA03827;
	Wed, 7 Jul 1999 18:03:40 -0500 (CDT)
Date: Wed, 7 Jul 1999 18:03:40 -0500
From: "Matthew D. Fuller" <fullermd@futuresouth.com>
To: freepix@sirius.com
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: IDE Channel??
Message-ID: <19990707180340.A28335@futuresouth.com>
References: <199907072228.PAA50348@mail1.sirius.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <199907072228.PAA50348@mail1.sirius.com>; from freepix@sirius.com on Wed, Jul 07, 1999 at 10:28:42PM +0000
X-OS: FreeBSD <http://www.freebsd.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Jul 07, 1999 at 10:28:42PM +0000, a little birdie told me
that freepix@sirius.com remarked
> I'm attempting to balance the load between my two hard drives in my server, but 
> I'm not sure if they are on their own IDE channels...  The server isn't located 
> in my city so I can't physically look into the case to see if they are on the 
> same chain, but I thought there would be a way to identify it via FreeBSD.  One 
> is named WD0 and the other is WD1 if that helps anyone...  If I left anything 
> out, please e-mail me back...

They're on the same channel.
wd0 is channel 0 master
wd1 is channel 0 slave
wd2 is channel 1 master
wd3 is channel 1 slave




-- 
Matthew Fuller     (MF4839)     |    fullermd@over-yonder.net
Unix Systems Administrator      |    fullermd@futuresouth.com
Specializing in FreeBSD         |    http://www.over-yonder.net/
FutureSouth Communications      |    ISPHelp ISP Consulting

"The only reason I'm burning my candle at both ends, is because I
      haven't figured out how to light the middle yet"


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7 16: 9: 9 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
	by hub.freebsd.org (Postfix) with ESMTP id 0B61A154BC
	for <freebsd-stable@freebsd.org>; Wed,  7 Jul 1999 16:09:03 -0700 (PDT)
	(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id IAA10573;
	Thu, 8 Jul 1999 08:38:53 +0930 (CST)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.3/8.9.0) id IAA03744;
	Thu, 8 Jul 1999 08:38:53 +0930 (CST)
Date: Thu, 8 Jul 1999 08:38:53 +0930
From: Greg Lehey <grog@lemis.com>
To: Brad Knowles <brad@shub-internet.org>
Cc: freebsd-stable@freebsd.org,
	Poul-Henning Kamp <phk@critter.freebsd.dk>
Subject: Re: Does vinum actually currently build under 3.2-STABLE?
Message-ID: <19990708083853.F2340@freebie.lemis.com>
References: <v04205512b3a92c813715@[195.238.1.121]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <v04205512b3a92c813715@[195.238.1.121]>; from Brad Knowles on Wed, Jul 07, 1999 at 06:20:32PM +0200
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wednesday,  7 July 1999 at 18:20:32 +0200, Brad Knowles wrote:
> Folks,
>
> 	I know a little while back that Poul-Henning Kamp had suggested
> some changes to vinum that would get it to compile (in 3.2-STABLE?),

That was a while back.  I fixed those problems about 3 weeks ago.

> and I've seen some recent traffic on -current to indicate that there
> were some other minor problems keeping vinum from building with
> FreeBSD 4.0-CURRENT.

Vinum builds under 3.2-STABLE.  I don't know why you're trying to use
the wrong version.  Yes, I once said that, at that moment, the
-CURRENT version would build under -STABLE.  That was quite some time
ago, and it no longer applies.

> 	The problems with FreeBSD 4.0-CURRENT appear to have been
> cleared up by Greg committing one additional file to CVS.

I did?  Which one?

> However, I am not exactly clear on whether vinum is currently
> supposed to build out-of-the-box with 3.2-STABLE, either with the
> provided code (apparently dated 5 May) or with the tarball at
> <ftp://ftp.lemis.com/pub/vinum/vinum-4.0-CURRENT.tar.gz> (dated 11
> May).

It's supposed to build out of the box.  Vinum is included in -STABLE.
The last modification was 11 May (sys/dev/vinum/vinumparser.c).

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7 16:35:54 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66])
	by hub.freebsd.org (Postfix) with ESMTP id F10AB15525
	for <freebsd-stable@freebsd.org>; Wed,  7 Jul 1999 16:35:17 -0700 (PDT)
	(envelope-from nik@nothing-going-on.demon.co.uk)
Received: (from nik@localhost)
	by nothing-going-on.demon.co.uk (8.9.3/8.9.2) id XAA37348;
	Wed, 7 Jul 1999 23:58:53 +0100 (BST)
	(envelope-from nik)
Date: Wed, 7 Jul 1999 23:58:52 +0100
From: Nik Clayton <nik@nothing-going-on.demon.co.uk>
To: David Bushong <dbushong@CSUA.Berkeley.EDU>
Cc: freebsd-stable@freebsd.org
Subject: Re: /usr/share/misc/magic updates?
Message-ID: <19990707235852.A36792@catkin.nothing-going-on.org>
References: <199907072008.NAA20074@soda.CSUA.Berkeley.EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <199907072008.NAA20074@soda.CSUA.Berkeley.EDU>; from David Bushong on Wed, Jul 07, 1999 at 01:08:36PM -0700
Organization: Nik at home, where there's nothing going on
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, Jul 07, 1999 at 01:08:36PM -0700, David Bushong wrote:
> I have an update to /usr/share/misc/magic I'd like to submit, but have no
> clue where to send it.  Pointers?

Use send-pr(1).  See the "How to Contribute" section in chapter 19 of 
the FreeBSD Handbook.

N
-- 
 [intentional self-reference] can be easily accommodated using a blessed,
 non-self-referential dummy head-node whose own object destructor severs
 the links.
    -- Tom Christiansen in <375143b5@cs.colorado.edu>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Wed Jul  7 22: 4:22 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from posgate.acis.com.au (posgate.acis.com.au [203.14.230.14])
	by hub.freebsd.org (Postfix) with ESMTP id 0185F15214
	for <freebsd-stable@FreeBSD.ORG>; Wed,  7 Jul 1999 22:04:11 -0700 (PDT)
	(envelope-from andymac@bullseye.apana.org.au)
Received: from bullseye.apana.org.au (uucp@localhost)
	by posgate.acis.com.au (8.9.2/8.9.2/Debian/GNU) with UUCP id OAA13710;
	Thu, 8 Jul 1999 14:55:29 +1000 (EST)
Received: from bullseye.apana.org.au (central.apana.org.au [203.9.107.245])
	by bullseye.apana.org.au (8.8.8/8.8.8) with SMTP id LAA00812;
	Thu, 8 Jul 1999 11:04:43 +1000 (EST)
	(envelope-from andymac@bullseye.apana.org.au)
Date: Thu, 8 Jul 1999 10:56:37 +1000 (EST)
From: Andrew MacIntyre <andymac@bullseye.apana.org.au>
To: Pascal Hofstee <daeron@Wit401305.student.utwente.nl>
Cc: David Schwartz <davids@webmaster.com>, freebsd-stable@FreeBSD.ORG
Subject: RE: Macronix driver bugs ?
In-Reply-To: <Pine.BSF.4.10.9907072101330.16028-100000@shadowmere.student.utwente.nl>
Message-ID: <Pine.OS2.3.95.990708105329.263C-100000@CENTRAL>
X-X-Sender: andymac@bullseye.apana.org.au
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Wed, 7 Jul 1999, Pascal Hofstee wrote:

> On Wed, 7 Jul 1999, David Schwartz wrote:
> 
> > 	I've had a lot of problems with MX98713 cards and FreeBSD-stable. None were
> > as bad as what you report. But I finally decided to either run the cards at
> > 10Mbps (which seems to work fine for me) or replace the cards with others
> > and put the 98713 cards in the NT machines.
> 
> I DO run it at 10 Mbps (half-duplex) ... but our network here gets
> upgarded soon to 100 Mbps (full-duplex) .... that's why I was "hoping to
> ditch the SMC"

Problems with drivers for these cards should be directed to the author,
Bill Paul <wpaul@skynet.ctr.columbia.edu>.  Please provide as much detail
as you can.

--
Andrew I MacIntyre                     "These thoughts are mine alone..."
E-mail: andrew.macintyre@aba.gov.au    (work) | Snail: PO Box 370
        andymac@bullseye.apana.org.au  (play) |        Belconnen  ACT  2616
Fido:   Andrew MacIntyre, 3:620/243.18        |        Australia



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8  0:10:43 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from beatrice.rutgers.edu (beatrice.rutgers.edu [165.230.209.226])
	by hub.freebsd.org (Postfix) with SMTP id E58A915273
	for <stable@FreeBSD.ORG>; Thu,  8 Jul 1999 00:10:39 -0700 (PDT)
	(envelope-from easmith@beatrice.rutgers.edu)
Received: (from easmith@localhost) by beatrice.rutgers.edu (950413.SGI.8.6.12/950213.SGI.AUTOCF) id DAA05487; Thu, 8 Jul 1999 03:11:47 -0400
From: "Allen Smith" <easmith@beatrice.rutgers.edu>
Message-Id: <9907080311.ZM5485@beatrice.rutgers.edu>
Date: Thu, 8 Jul 1999 03:11:46 -0400
In-Reply-To: "Ilya Balashov" <tsw@inec.ru>   "ipfilter broken in 3.2-stable" (Jun  3,  3:57am)
References: <NDBBKDAEHKFDJNIGJNPJMENLCCAA.tsw@inec.ru>
X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail)
To: "Ilya Balashov" <tsw@inec.ru>, <stable@FreeBSD.ORG>
Subject: Re: ipfilter broken in 3.2-stable
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Jun 3,  3:57am, Ilya Balashov (possibly) wrote:
> i using freebsd 3.2-stable with ipfw... for some reasons, i try to change
> ipfw (options IPFIREWALL) and ipf (options IPFILTER)...
> 
> but after reconfigure my system with ipfilter (NAT+accounting+some blocking
> rules), i have critical problems with IPfilter internal ftp proxy (using it
> cause kernel panic)

Hmm... any further data available?

> atfer some exploration, i found ipfilter 3.2.10 is latest, but in 3.2-stable
> has 3.2.7
> 
> i wrote to Darren Reed, and ask him:
> "can you update IP Filter in 3.2-stable branch???"
> and he answer: "when I get 3.2 cd-rom's, yes"

We're working on an updated version... if you're willing to work with
a beta (testing by more people is definitely desirable), see
http://false.net/ipfilter/1999_07/0041.html for more
information. Signing onto the ipfilter mailing list is also advised;
you probably want to check through the mailing list archives for July.

	-Allen

-- 
Allen Smith				easmith@beatrice.rutgers.edu
	


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8  3:29:37 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from smtp4.erols.com (smtp4.erols.com [207.172.3.237])
	by hub.freebsd.org (Postfix) with ESMTP id 2635714C81
	for <freebsd-stable@freebsd.org>; Thu,  8 Jul 1999 03:29:34 -0700 (PDT)
	(envelope-from jobaldwi@vt.edu)
Received: from john.baldwin.cx (207-172-143-79.s16.as1.hgt.md.dialup.rcn.com [207.172.143.79])
	by smtp4.erols.com (8.8.8/smtp-v1) with ESMTP id GAA15478;
	Thu, 8 Jul 1999 06:29:31 -0400 (EDT)
Message-Id: <199907081029.GAA15478@smtp4.erols.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <m110qpX-0008G4C@rip.psg.com>
Date: Thu, 08 Jul 1999 06:29:39 -0400 (EDT)
From: John Baldwin <jobaldwi@vt.edu>
To: Randy Bush <randy@psg.com>
Subject: Re: Splash Screens (was Re: 3.2-RELEASE Feedback)
Cc: FreeBSD Stable <freebsd-stable@freebsd.org>
Cc: FreeBSD Stable <freebsd-stable@freebsd.org>,
	Randall Hopper <aa8vb@ipass.net>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 04-Jul-99 Randy Bush wrote:
> so, i hacked my /boot/loader.conf.local to be
> 
>     splash_bmp_load="YES"
>     vesa_load="YES"
>     bitmap_load="YES"
>     bitmap_name="/boot/splash.bmp"
>     bitmap_type="splash_image_data"
> 
> install a 1024x768 /boot/spalsh.bmp
> 
> but i get
> 
>     Preloaded elf kernel "kernel" at 0xc04df000.
>     Preloaded elf module "splash_bmp.ko" at 0xc04df09c.
>     Preloaded elf module "vesa.ko" at 0xc04df140.
>     link_elf: symbol vm86_intcall undefined
>     Preloaded splash_image_data "/boot/splash.bmp" at 0xc04df1dc.
>     module_register_init: module_register(splash_bmp, c0295624, 0) error 19
>     Probing for devices on PCI bus 0:
> 
> and no spash, of course.
> 
> 3.2-stable+pao
> vaio 505tx

Run vidcontrol -i mode to see what modes your VGA BIOS supports.  Some BIOS's
are cheap and require a TSR to support VESA, e.g. ATI Rage PRO 3D, and with
these you are stuck with 320x200.

> randy

---

John Baldwin <jobaldwi@vt.edu> -- http://members.freedomnet.com/~jbaldwin/
PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.freebsd.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8  3:29:41 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from smtp3.erols.com (smtp3.erols.com [207.172.3.236])
	by hub.freebsd.org (Postfix) with ESMTP id 02E3314D14
	for <stable@FreeBSD.ORG>; Thu,  8 Jul 1999 03:29:37 -0700 (PDT)
	(envelope-from jobaldwi@vt.edu)
Received: from john.baldwin.cx (207-172-143-79.s16.as1.hgt.md.dialup.rcn.com [207.172.143.79])
	by smtp3.erols.com (8.8.8/8.8.5) with ESMTP id GAA01764;
	Thu, 8 Jul 1999 06:29:28 -0400 (EDT)
Message-Id: <199907081029.GAA01764@smtp3.erols.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <xzp908xwr6w.fsf@flood.ping.uio.no>
Date: Thu, 08 Jul 1999 06:29:36 -0400 (EDT)
From: John Baldwin <jobaldwi@vt.edu>
To: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Subject: Re: Splash Screens (was Re: 3.2-RELEASE Feedback)
Cc: stable@FreeBSD.ORG, Jim Mock <jim@advocacy.FreeBSD.org>,
	Randall Hopper <aa8vb@ipass.net>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 03-Jul-99 Dag-Erling Smorgrav wrote:
> Randall Hopper <aa8vb@ipass.net> writes:
>> Ok, I didn't know what to do with:
>> 
>>      include /boot/loader.4th
>>      start
>> 
>> which were already in this file, so I commented them out.  I was lucky.
> 
> They're not much use unless you want to use loader.conf (loader.4th
> reads loader.conf and does magic stuff as directed by variables
> defined there, much like /etc/rc does magic stuff as directed by
> /etc/rc.conf)
> 
>> So I went splash shopping.
> 
> I use the Saturn pics myself, though for some mysterious reason
> they're not on the advocacy site. They're by far the best splash
> screens I've seen, as they were designed specifically for that purpose
> (rather than just being *adapted* to that purpose). I think they're on
> John Baldwin's site (there's a link from the advocacy page), but I
> can't get through to it right now so I can't check.

My site is down for the summer (can't afford a static IP), but the new screens
are are going to be up on advocacy as soon as Jim and Rob give me the go ahead
<hint, hint, nudge, nudge>.

---

John Baldwin <jobaldwi@vt.edu> -- http://members.freedomnet.com/~jbaldwin/
PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.freebsd.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8  3:42:44 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from out0.mx.skynet.be (out0.mx.skynet.be [195.238.2.35])
	by hub.freebsd.org (Postfix) with ESMTP id 95D7B14CED
	for <freebsd-stable@freebsd.org>; Thu,  8 Jul 1999 03:42:41 -0700 (PDT)
	(envelope-from brad@shub-internet.org)
Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121])
	by out0.mx.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id MAA28038;
	Thu, 8 Jul 1999 12:42:10 +0200 (MET DST)
Mime-Version: 1.0
X-Sender: brad@mail.his.com
Message-Id: <v04205506b3aa2d288710@[195.238.1.121]>
In-Reply-To: <19990708083853.F2340@freebie.lemis.com>
References: <v04205512b3a92c813715@[195.238.1.121]>
 <19990708083853.F2340@freebie.lemis.com>
Date: Thu, 8 Jul 1999 12:42:02 +0200
To: Greg Lehey <grog@lemis.com>
From: Brad Knowles <brad@shub-internet.org>
Subject: Re: Does vinum actually currently build under 3.2-STABLE?
Cc: freebsd-stable@freebsd.org,
	Poul-Henning Kamp <phk@critter.freebsd.dk>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

At 8:38 AM +0930 1999/7/8, Greg Lehey wrote:

> Vinum builds under 3.2-STABLE.  I don't know why you're trying to use
> the wrong version.  Yes, I once said that, at that moment, the
> -CURRENT version would build under -STABLE.  That was quite some time
> ago, and it no longer applies.

	I apologize if I have offended you.  I had not heard that vinum 
4.0-CURRENT was no longer the version that I should be attempting to 
apply to FreeBSD 3.2-STABLE.


	The last time I had tried to do anything with vinum, you had 
recommended that I grab your -CURRENT and start over from there, and 
when I started working with vinum again, I tried to largely pick up 
where I left off before.

	I did carefully check the source trees to ensure that what you 
had did actually appear to be later code before I manually installed 
it (mv'ing each original affected file or directory to <name>.orig, 
before copying your "new" code into place).


	It would help me (if no one else) if the documentation you had on 
your web site would be kept a bit more up-to-date as to which 
versions are suitable for use with which versions of FreeBSD, and if 
we're supposed to be using the version that ships with the package, 
says that too.

	Speaking only for myself, I'm not subscribed to all of the 
freebsd- mailing lists (heck, I'm not subscribed to any of them), and 
although I do active searching of the archives of the mailing lists 
before I post any questions, my searches might not be fully 
sufficient to dig up all the relevant information, or the archives 
might not yet have caught up to the absolute last-second state of the 
moment.

> I did?  Which one?

	I have not yet been able to locate the exact name of the file, 
but the most relevant messages of yours that I've found so far in the 
archives of the -current mailing list are at 
<http://docs.freebsd.org/cgi/getmsg.cgi?fetch=431564+0+archive/1999/fr 
eebsd-current/19990704.freebsd-current> and 
<http://docs.freebsd.org/cgi/getmsg.cgi?fetch=532152+0+archive/1999/fr 
eebsd-current/19990704.freebsd-current>.  Note that they are dated 
only five days ago.

> It's supposed to build out of the box.  Vinum is included in -STABLE.
> The last modification was 11 May (sys/dev/vinum/vinumparser.c).

	The problem turned out to be that I had not managed to fully 
restore all the .orig files and directories I had manually mv'ed. 
Once I restored the one problem directory that had remained 
(/usr/src/sys/dev/vinum, as I recall), the build went cleanly.


	I'm now doing further benchmarks with rawio against a bare IBM 
UltraStar 9LZX 10KRPM drive connected through an Adaptec 3950U2, to 
add to the previous benchmarks I had done (and reported to you) on 
the DPT SmartRAID IV w/ 64MB cache and 128KB stripe size across four 
9LZX drives.

	Once this test is complete, I'll do another test with a vinum one 
drive concat device on the same disk (to see what overhead vinum 
adds), then a two-way, three-way, and four-way stripe with identical 
disks.  Since this is a pretty honkin' machine (PIII@450Mhz w/ 1GB 
RAM), it will be interesting to compare the performance of the older 
DPT SmartRAID IV card against vinum.

	I'll then go in and throw bonnie and perhaps some other tools at 
the 4-way striped disk arrays (both vinum and SmartRAID IV) and see 
what kind of difference 1GB of buffer cache can make.  ;-)

-- 
Brad Knowles <brad@shub-internet.org> <http://www.shub-internet.org/brad/>
     <http://wwwkeys.pgp.net:11371/pks/lookup?op=get&search=0xE38CCEF1>

Your mouse has moved.   Windows NT must be restarted for the change to
take effect.   Reboot now?  [ OK ]


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8  4:20:34 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from thelab.hub.org (nat195.34.mpoweredpc.net [142.177.195.34])
	by hub.freebsd.org (Postfix) with ESMTP
	id 623AE154F5; Thu,  8 Jul 1999 04:20:22 -0700 (PDT)
	(envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
	by thelab.hub.org (8.9.3/8.9.1) with ESMTP id IAA28701;
	Thu, 8 Jul 1999 08:20:37 -0300 (ADT)
	(envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Thu, 8 Jul 1999 08:20:37 -0300 (ADT)
From: The Hermit Hacker <scrappy@hub.org>
To: freebsd-current@freebsd.org
Cc: freebsd-stable@freebsd.org
Subject: Known MMAP() race conditions ... ?
Message-ID: <Pine.BSF.4.05.9907080812570.4088-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Three weeks ago, I, and a few other INN administrators, posted about
FreeBSD -STABLE's inability to run the newest INN code, due to MMAP() race
conditions...essentially, after X hours of run time, on a heavily loaded
INN server, the whole thing locks up solid.

At that time, Matt pop'd up and stated that he knew of *at least* 6 MMAP()
related race conditions that he was hoping to be able to get fixed "within
a week"...that would have been two weeks ago.

I've been watching the -commit messages closely, and CVSup'ng a new kernel
almost daily, in the hopes of seeing some MMAP() related activity from
someone, and haven't seen anything so far, so I'm curious as to whether or
not anyone *but* Matt is aware of these race conditions, and/or is working
on this?

I'm trying to push moving some Solaris boxes at work over to FreeBSD,
with our INN server being the 'safest' example to move over first, but
there is no way I can do that with the current INN/FreeBSD interaction :(

Thanks...

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8  5:55: 6 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from enst.enst.fr (enst.enst.fr [137.194.2.16])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5B47A15116; Thu,  8 Jul 1999 05:55:00 -0700 (PDT)
	(envelope-from beyssac@enst.fr)
Received: from bofh.enst.fr (bofh-2.enst.fr [137.194.2.37])
	by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id OAA16476;
	Thu, 8 Jul 1999 14:54:58 +0200 (MET DST)
Received: by bofh.enst.fr (Postfix, from userid 12426)
	id 3DEB3D226; Thu,  8 Jul 1999 14:54:58 +0200 (CEST)
Message-ID: <19990708145458.A10059@enst.fr>
Date: Thu, 8 Jul 1999 14:54:58 +0200
From: Pierre Beyssac <beyssac@enst.fr>
To: The Hermit Hacker <scrappy@hub.org>, freebsd-current@FreeBSD.ORG
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: Known MMAP() race conditions ... ?
References: <Pine.BSF.4.05.9907080812570.4088-100000@thelab.hub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <Pine.BSF.4.05.9907080812570.4088-100000@thelab.hub.org>; from The Hermit Hacker on Thu, Jul 08, 1999 at 08:20:37AM -0300
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Jul 08, 1999 at 08:20:37AM -0300, The Hermit Hacker wrote:
> I'm trying to push moving some Solaris boxes at work over to FreeBSD,
> with our INN server being the 'safest' example to move over first, but

You'd better try to configure INN without mmap(); this doesn't
induce much performance penalty and you avoid any problems with
FreeBSD's mmap.

Now there are other (and IMHO, better) ways to demonstrate FreeBSD
stability on a production server: HTTP, POP/SMTP, DNS,...
-- 
Pierre Beyssac		pb@enst.fr


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8  6:17:45 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from ideaglobal.com (ultra2.ideaglobal.com [194.36.20.11])
	by hub.freebsd.org (Postfix) with ESMTP id 12C1614EB6
	for <freebsd-stable@freebsd.org>; Thu,  8 Jul 1999 06:17:42 -0700 (PDT)
	(envelope-from kiril@ideaglobal.com)
Received: (from kiril@localhost)
	by ideaglobal.com (8.9.2/8.9.2) id OAA05851
	for freebsd-stable@freebsd.org; Thu, 8 Jul 1999 14:11:52 +0100 (BST)
From: Kiril Mitev <kiril@ideaglobal.com>
Message-Id: <199907081311.OAA05851@ideaglobal.com>
Subject: libcrypt links changed, cannot login anymore...
To: freebsd-stable@freebsd.org
Date: Thu, 8 Jul 1999 14:11:52 +0100 (BST)
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Dear List

I've changed the libcrypt* links from libdescrypt to libscrypt, and 
thereby killed completely everybody's logins (read: cannot login 
anymore).

I do recall that it was supposed to be OK to do this, or was my recollection
erm, wrong ?



Kiril



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8  6:18:33 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from thelab.hub.org (nat195.34.mpoweredpc.net [142.177.195.34])
	by hub.freebsd.org (Postfix) with ESMTP
	id 437C2151E7; Thu,  8 Jul 1999 06:18:29 -0700 (PDT)
	(envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
	by thelab.hub.org (8.9.3/8.9.1) with ESMTP id KAA29806;
	Thu, 8 Jul 1999 10:18:36 -0300 (ADT)
	(envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Thu, 8 Jul 1999 10:18:35 -0300 (ADT)
From: The Hermit Hacker <scrappy@hub.org>
To: Pierre Beyssac <beyssac@enst.fr>
Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Known MMAP() race conditions ... ?
In-Reply-To: <19990708145458.A10059@enst.fr>
Message-ID: <Pine.BSF.4.05.9907081009190.4088-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 8 Jul 1999, Pierre Beyssac wrote:

> On Thu, Jul 08, 1999 at 08:20:37AM -0300, The Hermit Hacker wrote:
> > I'm trying to push moving some Solaris boxes at work over to FreeBSD,
> > with our INN server being the 'safest' example to move over first, but
> 
> You'd better try to configure INN without mmap(); this doesn't
> induce much performance penalty and you avoid any problems with
> FreeBSD's mmap.

The newest INN does not have this option, MMAP() is a requirement for
it...

> Now there are other (and IMHO, better) ways to demonstrate FreeBSD
> stability on a production server: HTTP, POP/SMTP, DNS,...

ah, okay, so you are saying that FreeBSD shouldn't be demonstrated using
software that taxes/tweaks bugs in it?  Boy, does that sound like a quick
road to problems... Management: but, when you sold us on this operating
system, it was perfectly stable.  Me: ya, well, I picked and choose the
software I ran for the demo, sorry...

personal, sounds like something Microsoft would do, not something that
*I'd* want to base a decision on.  

right now, at work, I'm enjoying a 4 way battle.  Me, fighting to bring in
FreeBSD to replace some of our Solaris boxes.  A friend of mine, fighting
to bring in Linux to replace some of our Solaris boxes.  My boss fighting
against both of us to keep Solaris "because its what we've always used".
And another department fighting for NT/Novell solutions.

Right now, my 'fight' is weak, since all my friend has to do is point out
that 'the MMAP() issue isn't an issue under Linux'...and, as far as I'm
concerned, the MMAP() issue is about the *only* issue that prevents me
from being able to move forward. 

My opinion on the Linux vs *BSD issue is, and always has been, that *BSD
makes the better *server*...we have very strong networking code, a very
stable kernel and a sane development model...but this MMAP() issue really
hurts :(  IMHO, *BSD was designed around *loaded* machines, yet it can't
handle a fully configured, loaded INN server without hanging :(

If someone is working on this, and its just a matter of patience because
the bugs, altho known, are obscure, great.  If ppl think that the problem
isn't serious enough, expect that once INN 2.3 is released, there is going
to be a major outcry, since INN 2.3 *requires* MMAP() to be used, it isn't
an option anymore :(

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8  6:37:10 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from fed-ef1.frb.gov (fed.frb.gov [132.200.32.32])
	by hub.freebsd.org (Postfix) with ESMTP
	id C871714BF5; Thu,  8 Jul 1999 06:37:01 -0700 (PDT)
	(envelope-from seth@freebie.dp.ny.frb.org)
Received: by fed-ef1.frb.gov; id JAA26763; Thu, 8 Jul 1999 09:36:52 -0400 (EDT)
Received: from m1pmdf.frb.gov(192.168.3.38) by fed.frb.gov via smap (V4.2)
	id xma026487; Thu, 8 Jul 99 09:36:34 -0400
Date: Thu, 08 Jul 1999 09:36:25 -0400 (EDT)
From: Seth <seth@freebie.dp.ny.frb.org>
Subject: Re: Known MMAP() race conditions ... ?
In-reply-to: <19990708145458.A10059@enst.fr>
To: Pierre Beyssac <beyssac@enst.fr>
Cc: The Hermit Hacker <scrappy@hub.org>, freebsd-current@FreeBSD.ORG,
	freebsd-stable@FreeBSD.ORG
Message-id: <Pine.BSF.4.10.9907080934170.97212-100000@freebie.dp.ny.frb.org>
MIME-version: 1.0
Content-type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Is this the same problem that locks the machine up when two find's are
performed (even by a user)?  That problem was discussed a couple months
ago in this group, but I haven't heard whether that's been resolved yet.

SB




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8  7:45:54 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from enst.enst.fr (enst.enst.fr [137.194.2.16])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3613C14CED; Thu,  8 Jul 1999 07:45:45 -0700 (PDT)
	(envelope-from beyssac@enst.fr)
Received: from bofh.enst.fr (bofh-2.enst.fr [137.194.2.37])
	by enst.enst.fr (8.9.1a/8.9.1) with ESMTP id QAA21830;
	Thu, 8 Jul 1999 16:45:43 +0200 (MET DST)
Received: by bofh.enst.fr (Postfix, from userid 12426)
	id BD9D5D226; Thu,  8 Jul 1999 15:50:02 +0200 (CEST)
Message-ID: <19990708155002.H90983@enst.fr>
Date: Thu, 8 Jul 1999 15:50:02 +0200
From: Pierre Beyssac <beyssac@enst.fr>
To: The Hermit Hacker <scrappy@hub.org>
Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Known MMAP() race conditions ... ?
References: <19990708145458.A10059@enst.fr> <Pine.BSF.4.05.9907081009190.4088-100000@thelab.hub.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.93.2i
In-Reply-To: <Pine.BSF.4.05.9907081009190.4088-100000@thelab.hub.org>; from The Hermit Hacker on Thu, Jul 08, 1999 at 10:18:35AM -0300
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, Jul 08, 1999 at 10:18:35AM -0300, The Hermit Hacker wrote:
> The newest INN does not have this option, MMAP() is a requirement for
> it...

Sorry, I didn't know that. Too bad, then.

> ah, okay, so you are saying that FreeBSD shouldn't be demonstrated using
> software that taxes/tweaks bugs in it?

Exactly. If you want to show the strengths of a system, it just
doesn't make sense to rely on its weaker parts.

> Boy, does that sound like a quick
> road to problems... Management: but, when you sold us on this operating
> system, it was perfectly stable.  Me: ya, well, I picked and choose the
> software I ran for the demo, sorry...

I didn't say you have to lie about your choice.

> Right now, my 'fight' is weak, since all my friend has to do is point out
> that 'the MMAP() issue isn't an issue under Linux'...and, as far as I'm

Linux has other -- IMHO more annoying -- issues, so I think your
friend had better stop bragging.

> My opinion on the Linux vs *BSD issue is, and always has been, that *BSD
> makes the better *server*...we have very strong networking code, a very
> stable kernel and a sane development model...but this MMAP() issue really
> hurts :(

I think everyone agrees. Now, the problem is that it's not an easy
thing to fix, or it would already be fixed.
-- 
Pierre Beyssac		pb@enst.fr


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8  7:58:59 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
	by hub.freebsd.org (Postfix) with ESMTP
	id 836CE1530B; Thu,  8 Jul 1999 07:58:52 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id HAA40125;
	Thu, 8 Jul 1999 07:58:49 -0700 (PDT)
	(envelope-from dillon)
Date: Thu, 8 Jul 1999 07:58:49 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199907081458.HAA40125@apollo.backplane.com>
To: The Hermit Hacker <scrappy@hub.org>
Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Known MMAP() race conditions ... ?
References:  <Pine.BSF.4.05.9907080812570.4088-100000@thelab.hub.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

:At that time, Matt pop'd up and stated that he knew of *at least* 6 MMAP()
:related race conditions that he was hoping to be able to get fixed "within
:a week"...that would have been two weeks ago.

    I think I was talking about mmap w/ NFS.

    Under FreeBSD-current I know of two problems ( though I could be
    forgetting some ) - there is a problem when a lot of pages get dirtied
    that can cause a low-memory deadlock to occur, and I believe there is a
    problem when mlock() or madvise() is used though I haven't reproduced
    it yet.

    Under FreeBSD-stable there are a number of additional, but minor problems
    related to visibility of non-zero garbage after file EOF in an mmap(),
    but these would have no effect on INN.

    What we need to know is why the machines are locking up.  The usual
    way to figure this out is to compile the kernel up with DDB and then
    when it locks up ctl-alt-esc on the console to get the DDB prompt,
    and do a 'ps' to see what the procsses are blocked in.

    If the problem is the dirty-page problem, there are ways around it
    (basically by syncing more often).

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>

:Thanks...
:
:Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
:Systems Administrator @ hub.org 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8  9:34:35 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from grizzly.fas.com (cc69528-a.mtpls1.sc.home.com [24.6.61.166])
	by hub.freebsd.org (Postfix) with ESMTP id CD840154E7
	for <freebsd-stable@FreeBSD.ORG>; Thu,  8 Jul 1999 09:34:29 -0700 (PDT)
	(envelope-from stanb@awod.com)
Received: by grizzly.fas.com
	($Revision: 1.37.109.23 $/16.2) id AA274641667; Thu, 8 Jul 1999 12:34:27 -0400
Subject: Difference between wdc, and acd devices?
To: freebsd-stable@FreeBSD.ORG (FreeBSD Stable Mailing List)
Date: Thu, 8 Jul 1999 12:34:26 -0400 (EDT)
From: "Stan Brown" <stanb@awod.com>
X-Mailer: ELM [version 2.4 PL24]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 762       
Message-Id: <19990708163430.CD840154E7@hub.freebsd.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

	In playing around with the kernel configuration for my ATAPI CDROM, I
	find myself confused over whether I need the acd, or wdc devices, or
	both.

	Couls someone plaes point me to som documentation on this issue?

	Also is the acd entry new, or have I just been overlooking it, all
	these years?


-- 
Stan Brown     stanb@netcom.com                                    843-745-3154
Westvaco
Charleston SC.
-- 
Windows 98: n.
	useless extension to a minor patch release for 32-bit extensions and
	a graphical shell for a 16-bit patch to an 8-bit operating system
	originally coded for a 4-bit microprocessor, written by a 2-bit 
	company that can't stand for 1 bit of competition.
-
(c) 1999 Stan Brown.  Redistribution via the Microsoft Network is prohibited.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8 10: 1:59 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235])
	by hub.freebsd.org (Postfix) with ESMTP id 3A04714C31
	for <freebsd-stable@FreeBSD.ORG>; Thu,  8 Jul 1999 10:01:25 -0700 (PDT)
	(envelope-from jedgar@fxp.org)
Received: by pawn.primelocation.net (Postfix, from userid 1003)
	id 6615FF818; Thu,  8 Jul 1999 13:01:24 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by pawn.primelocation.net (Postfix) with ESMTP
	id 574029B15; Thu,  8 Jul 1999 13:01:24 -0400 (EDT)
Date: Thu, 8 Jul 1999 13:01:24 -0400 (EDT)
From: "Chris D. Faulhaber" <jedgar@fxp.org>
X-Sender: jedgar@pawn.primelocation.net
To: Stan Brown <stanb@awod.com>
Cc: FreeBSD Stable Mailing List <freebsd-stable@FreeBSD.ORG>
Subject: Re: Difference between wdc, and acd devices?
In-Reply-To: <19990708163430.CD840154E7@hub.freebsd.org>
Message-ID: <Pine.BSF.4.10.9907081300300.46001-100000@pawn.primelocation.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 8 Jul 1999, Stan Brown wrote:

> 	In playing around with the kernel configuration for my ATAPI CDROM, I
> 	find myself confused over whether I need the acd, or wdc devices, or
> 	both.
> 
> 	Couls someone plaes point me to som documentation on this issue?
> 
> 	Also is the acd entry new, or have I just been overlooking it, all
> 	these years?
> 

See /usr/src/UPDATING wrt the 19981224 entry.


-----
Chris D. Faulhaber <jedgar@fxp.org>  |  All the true gurus I've met never
System/Network Administrator,        |  claimed they were one, and always
Reality Check Information, Inc.      |  pointed to someone better.




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8 11:32: 9 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from thelab.hub.org (nat195.34.mpoweredpc.net [142.177.195.34])
	by hub.freebsd.org (Postfix) with ESMTP
	id F03D115517; Thu,  8 Jul 1999 11:31:59 -0700 (PDT)
	(envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
	by thelab.hub.org (8.9.3/8.9.1) with ESMTP id PAA36579;
	Thu, 8 Jul 1999 15:32:04 -0300 (ADT)
	(envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Thu, 8 Jul 1999 15:32:04 -0300 (ADT)
From: The Hermit Hacker <scrappy@hub.org>
To: Pierre Beyssac <beyssac@enst.fr>
Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Known MMAP() race conditions ... ?
In-Reply-To: <19990708155002.H90983@enst.fr>
Message-ID: <Pine.BSF.4.05.9907081531250.4088-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 8 Jul 1999, Pierre Beyssac wrote:

> > Right now, my 'fight' is weak, since all my friend has to do is point out
> > that 'the MMAP() issue isn't an issue under Linux'...and, as far as I'm
> 
> Linux has other -- IMHO more annoying -- issues, so I think your
> friend had better stop bragging.

Linux has strenghts over *BSD, and vice versa...

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8 11:34:49 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from thelab.hub.org (nat195.34.mpoweredpc.net [142.177.195.34])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8748615571; Thu,  8 Jul 1999 11:34:39 -0700 (PDT)
	(envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
	by thelab.hub.org (8.9.3/8.9.1) with ESMTP id PAA36583;
	Thu, 8 Jul 1999 15:34:25 -0300 (ADT)
	(envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Thu, 8 Jul 1999 15:34:25 -0300 (ADT)
From: The Hermit Hacker <scrappy@hub.org>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Known MMAP() race conditions ... ?
In-Reply-To: <199907081458.HAA40125@apollo.backplane.com>
Message-ID: <Pine.BSF.4.05.9907081532530.4088-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 8 Jul 1999, Matthew Dillon wrote:

> :At that time, Matt pop'd up and stated that he knew of *at least* 6 MMAP()
> :related race conditions that he was hoping to be able to get fixed "within
> :a week"...that would have been two weeks ago.
> 
>     I think I was talking about mmap w/ NFS.
> 
>     Under FreeBSD-current I know of two problems ( though I could be
>     forgetting some ) - there is a problem when a lot of pages get dirtied
>     that can cause a low-memory deadlock to occur, and I believe there is a
>     problem when mlock() or madvise() is used though I haven't reproduced
>     it yet.
> 
>     Under FreeBSD-stable there are a number of additional, but minor problems
>     related to visibility of non-zero garbage after file EOF in an mmap(),
>     but these would have no effect on INN.
> 
>     What we need to know is why the machines are locking up.  The usual
>     way to figure this out is to compile the kernel up with DDB and then
>     when it locks up ctl-alt-esc on the console to get the DDB prompt,
>     and do a 'ps' to see what the procsses are blocked in.

No matter how much I want to get this fixed, I don't haven't yet been able
to get DDB to dump properly :(  I've tried various things wiht the
portmaster that the serial console is attached to, but its either an old
ComOS on that machine, or they've "secured" it up against the various work
arounds :(

and...my server does this once a day, so would be a perfect candidate for
debugging :(

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8 11:43:10 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2389E155E3; Thu,  8 Jul 1999 11:43:06 -0700 (PDT)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.9.3/8.9.1) id LAA41965;
	Thu, 8 Jul 1999 11:43:04 -0700 (PDT)
	(envelope-from dillon)
Date: Thu, 8 Jul 1999 11:43:04 -0700 (PDT)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <199907081843.LAA41965@apollo.backplane.com>
To: The Hermit Hacker <scrappy@hub.org>
Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Known MMAP() race conditions ... ?
References:  <Pine.BSF.4.05.9907081532530.4088-100000@thelab.hub.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

:No matter how much I want to get this fixed, I don't haven't yet been able
:to get DDB to dump properly :(  I've tried various things wiht the
:portmaster that the serial console is attached to, but its either an old
:ComOS on that machine, or they've "secured" it up against the various work
:arounds :(
:
:and...my server does this once a day, so would be a perfect candidate for
:debugging :(
:
:Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy

    You *might* be able to leave a 'top -S' running in a tall window.  It 
    is possible that it will still operate even when the rest of the system
    locks up.

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8 11:59: 8 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from thelab.hub.org (nat195.34.mpoweredpc.net [142.177.195.34])
	by hub.freebsd.org (Postfix) with ESMTP
	id 14C5E15091; Thu,  8 Jul 1999 11:59:01 -0700 (PDT)
	(envelope-from scrappy@hub.org)
Received: from localhost (scrappy@localhost)
	by thelab.hub.org (8.9.3/8.9.1) with ESMTP id PAA36990;
	Thu, 8 Jul 1999 15:59:04 -0300 (ADT)
	(envelope-from scrappy@hub.org)
X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs
Date: Thu, 8 Jul 1999 15:59:03 -0300 (ADT)
From: The Hermit Hacker <scrappy@hub.org>
To: Matthew Dillon <dillon@apollo.backplane.com>
Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG
Subject: Re: Known MMAP() race conditions ... ?
In-Reply-To: <199907081843.LAA41965@apollo.backplane.com>
Message-ID: <Pine.BSF.4.05.9907081558470.4088-100000@thelab.hub.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Running now, will send you the output tomorrow when I get back to the
office :)

On Thu, 8 Jul 1999, Matthew Dillon wrote:

> :No matter how much I want to get this fixed, I don't haven't yet been able
> :to get DDB to dump properly :(  I've tried various things wiht the
> :portmaster that the serial console is attached to, but its either an old
> :ComOS on that machine, or they've "secured" it up against the various work
> :arounds :(
> :
> :and...my server does this once a day, so would be a perfect candidate for
> :debugging :(
> :
> :Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
> 
>     You *might* be able to leave a 'top -S' running in a tall window.  It 
>     is possible that it will still operate even when the rest of the system
>     locks up.
> 
> 					-Matt
> 					Matthew Dillon 
> 					<dillon@backplane.com>
> 

Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8 12:44:41 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from shuttle.netronix.com (shuttle.netronix.com [205.149.170.14])
	by hub.freebsd.org (Postfix) with ESMTP id A9D4B15101
	for <freebsd-stable@freebsd.org>; Thu,  8 Jul 1999 12:44:37 -0700 (PDT)
	(envelope-from mike@netronix.com)
Received: from enterprise (enterprise [205.149.190.34]) by shuttle.netronix.com (8.9.3/8.6.5) with SMTP id NAA23746 for <freebsd-stable@freebsd.org>; Thu, 8 Jul 1999 13:00:07 -0700 (PDT)
Message-Id: <4.1.19990708123747.018dfcb0@shuttle.netronix.com>
X-Sender: mike@shuttle.netronix.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Thu, 08 Jul 1999 12:51:37 -0700
To: freebsd-stable@freebsd.org
From: Mike Tisdell <mike@netronix.com>
Subject: VPN question (using ppp and ssh)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

	

I have setup a VPN using ppp and ssh, using the device !/etc/ppp/secure
in the ppp.conf. Amost the same as that provided in the ppp.conf.sample in
2.2.8. I want to use the VPN in the -auto mode because the vpn session is
routed over a standard on demand ppp connection to an ISP. The problem that
I am having is that when anything (including the idle timer) causes the
link to come down and ssh terminates, ppp also terminates with a discripter
0 error.

I have tried listing multiple instances of !/etc/ppp/secure in the device
statement in ppp.conf hoping that when ppp sees the failed device it would
try the next, but it doesn't. It appears that when ssh terminates and
closes stdin/stdout it causes a fatal error that ppp cannot recover from.
Does anyone have any ideas on how to get around this?


				mike@netronix.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8 17:17: 0 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from awfulhak.org (dynamic-98.max1-du-ws.dialnetwork.pavilion.co.uk [212.74.8.98])
	by hub.freebsd.org (Postfix) with ESMTP id D9A06155E7
	for <freebsd-stable@FreeBSD.ORG>; Thu,  8 Jul 1999 17:16:50 -0700 (PDT)
	(envelope-from brian@Awfulhak.org)
Received: from dev.lan.awfulhak.org (dev.lan.awfulhak.org [172.16.0.5])
	by awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA09793;
	Fri, 9 Jul 1999 00:59:13 +0100 (BST)
	(envelope-from brian@lan.awfulhak.org)
Received: from dev.lan.awfulhak.org (localhost [127.0.0.1])
	by dev.lan.awfulhak.org (8.9.3/8.9.3) with ESMTP id AAA64867;
	Fri, 9 Jul 1999 00:59:12 +0100 (BST)
	(envelope-from brian@dev.lan.awfulhak.org)
Message-Id: <199907082359.AAA64867@dev.lan.awfulhak.org>
X-Mailer: exmh version 2.0.2 2/24/98
To: Mike Tisdell <mike@netronix.com>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: VPN question (using ppp and ssh) 
In-reply-to: Your message of "Thu, 08 Jul 1999 12:51:37 PDT."
             <4.1.19990708123747.018dfcb0@shuttle.netronix.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 09 Jul 1999 00:59:12 +0100
From: Brian Somers <brian@Awfulhak.org>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> I have setup a VPN using ppp and ssh, using the device !/etc/ppp/secure
> in the ppp.conf. Amost the same as that provided in the ppp.conf.sample in
> 2.2.8. I want to use the VPN in the -auto mode because the vpn session is
> routed over a standard on demand ppp connection to an ISP. The problem that
> I am having is that when anything (including the idle timer) causes the
> link to come down and ssh terminates, ppp also terminates with a discripter
> 0 error.
> 
> I have tried listing multiple instances of !/etc/ppp/secure in the device
> statement in ppp.conf hoping that when ppp sees the failed device it would
> try the next, but it doesn't. It appears that when ssh terminates and
> closes stdin/stdout it causes a fatal error that ppp cannot recover from.
> Does anyone have any ideas on how to get around this?

The latest version of ppp handles this sort of error like carrier 
loss on a tty :-)

> 				mike@netronix.com

-- 
Brian <brian@Awfulhak.org>                        <brian@FreeBSD.org>
      <http://www.Awfulhak.org>                   <brian@OpenBSD.org>
Don't _EVER_ lose your sense of humour !          <brian@FreeBSD.org.uk>




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8 18:41: 8 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5])
	by hub.freebsd.org (Postfix) with ESMTP id E83901511F
	for <stable@freebsd.org>; Thu,  8 Jul 1999 18:41:06 -0700 (PDT)
	(envelope-from rhh@ipass.net)
Received: from stealth.ipass.net. (ppp-3-42.dialup.rdu.ipass.net [209.170.134.42])
	by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id VAA28473;
	Thu, 8 Jul 1999 21:41:01 -0400 (EDT)
Received: (from rhh@localhost)
	by stealth.ipass.net. (8.9.3/8.8.8) id VAA01821;
	Thu, 8 Jul 1999 21:43:04 -0400 (EDT)
	(envelope-from rhh)
Date: Thu, 8 Jul 1999 21:43:04 -0400
From: Randall Hopper <aa8vb@ipass.net>
To: stable@freebsd.org
Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>
Subject: Splash Background Color
Message-ID: <19990708214304.A1736@ipass.net>
References: <199907082225.SAA06505@smtp3.erols.com> <19990708193133.A6924@ipass.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <19990708193133.A6924@ipass.net>; from Randall Hopper on Thu, Jul 08, 1999 at 07:31:33PM -0400
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

John Baldwin:
 |I'm happy to report that the splash screen gallery is available again at
 |http://www.cslab.vt.edu/~jobaldwi/splash/

Is there a way to change the background (overscan) color used to display
VESA splash pics?

Those saturn splash screens look nice, but the overscan is fire engine read -- most annoying.

Thanks,

Randall




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8 19:20:24 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.westbend.net (ns1.westbend.net [209.224.254.131])
	by hub.freebsd.org (Postfix) with ESMTP id 5C31814E67
	for <freebsd-stable@FreeBSD.ORG>; Thu,  8 Jul 1999 19:20:18 -0700 (PDT)
	(envelope-from hetzels@westbend.net)
Received: from admin (admin.westbend.net [209.224.254.141])
	by mail.westbend.net (8.8.8/8.8.8) with SMTP id VAA03238;
	Thu, 8 Jul 1999 21:20:13 -0500 (CDT)
	(envelope-from hetzels@westbend.net)
Message-ID: <00a701bec9b1$93f73a40$8dfee0d1@westbend.net>
From: "Scot W. Hetzel" <hetzels@westbend.net>
To: "Kiril Mitev" <kiril@ideaglobal.com>
Cc: <freebsd-stable@FreeBSD.ORG>
References: <199907081311.OAA05851@ideaglobal.com>
Subject: Re: libcrypt links changed, cannot login anymore...
Date: Thu, 8 Jul 1999 21:20:13 -0500
Organization: West Bend Internet
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

From: Kiril Mitev <kiril@ideaglobal.com>
> I've changed the libcrypt* links from libdescrypt to libscrypt, and
> thereby killed completely everybody's logins (read: cannot login
> anymore).
>
> I do recall that it was supposed to be OK to do this, or was my
recollection
> erm, wrong ?
>
your recollection is wrong.

It's okay to change the links from libscrypt to libdescrypt for libcrypt*,
as the libdescrypt library can encode/decode DES and pass MD5 passwords to
libscrypt.

Where as the libscrypt can only encode/decode MD5 passwords.

Since, you originally used the libdescrypt, all the passwords were encrypted
with DES encryption.

Scot



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8 20:32:37 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134])
	by hub.freebsd.org (Postfix) with ESMTP id 7DB7514EBA
	for <freebsd-stable@freebsd.org>; Thu,  8 Jul 1999 20:32:30 -0700 (PDT)
	(envelope-from grog@freebie.lemis.com)
Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137])
	by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA18090;
	Fri, 9 Jul 1999 13:02:21 +0930 (CST)
Received: (from grog@localhost)
	by freebie.lemis.com (8.9.3/8.9.0) id NAA12022;
	Fri, 9 Jul 1999 13:02:19 +0930 (CST)
Date: Fri, 9 Jul 1999 13:02:19 +0930
From: Greg Lehey <grog@lemis.com>
To: Brad Knowles <brad@shub-internet.org>
Cc: freebsd-stable@freebsd.org,
	Poul-Henning Kamp <phk@critter.freebsd.dk>
Subject: Re: Does vinum actually currently build under 3.2-STABLE?
Message-ID: <19990709130219.W6035@freebie.lemis.com>
References: <v04205512b3a92c813715@[195.238.1.121]> <19990708083853.F2340@freebie.lemis.com> <v04205506b3aa2d288710@[195.238.1.121]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.4i
In-Reply-To: <v04205506b3aa2d288710@[195.238.1.121]>; from Brad Knowles on Thu, Jul 08, 1999 at 12:42:02PM +0200
WWW-Home-Page: http://www.lemis.com/~grog
X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF  13 24 52 F8 6D A4 95 EF
Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia
Phone: +61-8-8388-8286
Fax: +61-8-8388-8725
Mobile: +61-41-739-7062
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thursday,  8 July 1999 at 12:42:02 +0200, Brad Knowles wrote:
> At 8:38 AM +0930 1999/7/8, Greg Lehey wrote:
>
>> Vinum builds under 3.2-STABLE.  I don't know why you're trying to use
>> the wrong version.  Yes, I once said that, at that moment, the
>> -CURRENT version would build under -STABLE.  That was quite some time
>> ago, and it no longer applies.
>
> 	I apologize if I have offended you.  I had not heard that vinum
> 4.0-CURRENT was no longer the version that I should be attempting to
> apply to FreeBSD 3.2-STABLE.

No, you haven't offended me, but you've caused yourself unnecessary
work--see the private mail message I just sent.

> 	The last time I had tried to do anything with vinum, you had
> recommended that I grab your -CURRENT and start over from there, and
> when I started working with vinum again, I tried to largely pick up
> where I left off before.

Right.  As I explained in the other message, you were testing some
stuff then.

> 	It would help me (if no one else) if the documentation you had on
> your web site would be kept a bit more up-to-date as to which
> versions are suitable for use with which versions of FreeBSD, and if
> we're supposed to be using the version that ships with the package,
> says that too.

Right.  I've updated the web page.

> 	I'll then go in and throw bonnie and perhaps some other tools at
> the 4-way striped disk arrays (both vinum and SmartRAID IV) and see
> what kind of difference 1GB of buffer cache can make.  ;-)

It will certainly add to the confusion factor, anyway.

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8 21: 1:29 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from smtp1.erols.com (smtp1.erols.com [207.172.3.234])
	by hub.freebsd.org (Postfix) with ESMTP id 0A5A014D24
	for <stable@freebsd.org>; Thu,  8 Jul 1999 21:01:17 -0700 (PDT)
	(envelope-from jobaldwi@vt.edu)
Received: from john.baldwin.cx (207-172-143-66.s3.as1.hgt.md.dialup.rcn.com [207.172.143.66])
	by smtp1.erols.com (8.8.8/8.8.5) with ESMTP id AAA26712;
	Fri, 9 Jul 1999 00:01:12 -0400 (EDT)
Message-Id: <199907090401.AAA26712@smtp1.erols.com>
X-Mailer: XFMail 1.3 [p0] on FreeBSD
X-Priority: 3 (Normal)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0
In-Reply-To: <19990708214304.A1736@ipass.net>
Date: Fri, 09 Jul 1999 00:01:20 -0400 (EDT)
From: John Baldwin <jobaldwi@vt.edu>
To: Randall Hopper <aa8vb@ipass.net>
Subject: RE: Splash Background Color
Cc: Dag-Erling Smorgrav <des@flood.ping.uio.no>, stable@freebsd.org
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


On 09-Jul-99 Randall Hopper wrote:
> John Baldwin:
>  |I'm happy to report that the splash screen gallery is available again at
>  |http://www.cslab.vt.edu/~jobaldwi/splash/
> 
> Is there a way to change the background (overscan) color used to display
> VESA splash pics?
> 
> Those saturn splash screens look nice, but the overscan is fire engine read
> -- most annoying.

In my experience it seems to be specific to the video cards.  I've seen it on a
S3-based Diamond card and ATI Rage PRO's, while my Matrox G200 and a Cirrus
Logic at work have black overscans.  Go figure.  It should be a couple of
simple out's to the appropriate ports to set the overscan color, but I don't
have my VGA book handy. :(

> Thanks,
> 
> Randall

---

John Baldwin <jobaldwi@vt.edu> -- http://members.freedomnet.com/~jbaldwin/
PGP Key: http://members.freedomnet.com/~jbaldwin/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.freebsd.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8 21: 7: 2 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3])
	by hub.freebsd.org (Postfix) with ESMTP id AAFDF14D64
	for <stable@freebsd.org>; Thu,  8 Jul 1999 21:06:51 -0700 (PDT)
	(envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp)
Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:vd6SwAEaSCXKsaGche8LI/wDktheIrir@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1])
	by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id NAA31889;
	Fri, 9 Jul 1999 13:06:31 +0900 (JST)
Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP
	id NAA25966; Fri, 9 Jul 1999 13:10:46 +0900 (JST)
Message-Id: <199907090410.NAA25966@zodiac.mech.utsunomiya-u.ac.jp>
To: Randall Hopper <aa8vb@ipass.net>
Cc: stable@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: Re: Splash Background Color 
In-reply-to: Your message of "Thu, 08 Jul 1999 21:43:04 -0400."
             <19990708214304.A1736@ipass.net> 
References: <199907082225.SAA06505@smtp3.erols.com> <19990708193133.A6924@ipass.net>
	  <19990708214304.A1736@ipass.net> 
Date: Fri, 09 Jul 1999 13:10:45 +0900
From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>Is there a way to change the background (overscan) color used to display
>VESA splash pics?
>
>Those saturn splash screens look nice, but the overscan is fire engine read --
> most annoying.

Both the BMP file decoder (splash_bmp) and the PCX decoder
(splash_pcx) use the color palette 0 to clear the screen before
drawing the bitmap.  What you see as the background and border color is
whichever color happen to be set in the color palette 0 in the bitmap
file.

The problem comes from the fact that the W*ndows BMP file format and
the PCX format do not specify which color palette should be used as
the background color.  There is no way for the splash decoders to know
which background color would look great with the given bitmap.

Why palette 0? you may ask.  It's partly because of lazy programming :-)
and partly because of assumption that bitmap files tend to store
frequently used colors at the beginning of the color palette table
(this is even recommended for the BMP format by M*crosoft),
thus, it is likely that the palette 0 contains very, if not most,
frequently used color in the bitmap.  This frequently used color may
not be the best color for the background and border color, but won't
look very strange because it is, after all, very much used in the
bitmap.

Alternative approach would be that we search for "black" palette and use
that palette index number to fill the background.

As for options to specify the background color, you cannot specify the
background color by some options to the splash decoders.  AFAIK, there
is no way to pass option strings to the KLD module...

(Even if there is a way to pass options to the splash decoders, we
have to modify them further so that they search for an empty, unused
color palette entry to use...)

Kazu




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8 22:41:53 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from ibm1.exotrope.net (ibm1.exotrope.net [199.105.232.82])
	by hub.freebsd.org (Postfix) with ESMTP id D5C0E14CEC
	for <FreeBSD-stable@FreeBSD.ORG>; Thu,  8 Jul 1999 22:41:45 -0700 (PDT)
	(envelope-from reason@exotrope.net)
Received: from rgreen (bgm-44-34.stny.rr.com [24.94.44.34])
	by ibm1.exotrope.net (8.8.5/8.8.5) with SMTP id BAA21608
	for <FreeBSD-stable@FreeBSD.ORG>; Fri, 9 Jul 1999 01:39:54 -0400 (EDT)
Message-ID: <001401bec9cd$7a5dd140$222c5e18@stny.rr.com>
From: "R Green" <reason@exotrope.net>
To: <FreeBSD-stable@FreeBSD.ORG>
Subject: subscribe
Date: Fri, 9 Jul 1999 01:39:56 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0011_01BEC9AB.F2B6A800"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

This is a multi-part message in MIME format.

------=_NextPart_000_0011_01BEC9AB.F2B6A800
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

subscribe

------=_NextPart_000_0011_01BEC9AB.F2B6A800
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3401" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>subscribe</FONT></DIV></BODY></HTML>

------=_NextPart_000_0011_01BEC9AB.F2B6A800--



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Thu Jul  8 23: 2:44 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87])
	by hub.freebsd.org (Postfix) with ESMTP id 64AE814D0C
	for <stable@FreeBSD.ORG>; Thu,  8 Jul 1999 23:02:41 -0700 (PDT)
	(envelope-from dcs@newsguy.com)
Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id PAA12771; Fri, 9 Jul 1999 15:02:30 +0900 (JST)
Message-ID: <37858F99.84ADB6C0@newsguy.com>
Date: Fri, 09 Jul 1999 14:58:49 +0900
From: "Daniel C. Sobral" <dcs@newsguy.com>
X-Mailer: Mozilla 4.6 [en] (Win98; I)
X-Accept-Language: pt-BR,ja
MIME-Version: 1.0
To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Cc: Randall Hopper <aa8vb@ipass.net>, stable@FreeBSD.ORG
Subject: Re: Splash Background Color
References: <199907082225.SAA06505@smtp3.erols.com> <19990708193133.A6924@ipass.net>
		  <19990708214304.A1736@ipass.net> <199907090410.NAA25966@zodiac.mech.utsunomiya-u.ac.jp>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Kazutaka YOKOTA wrote:
> 
> As for options to specify the background color, you cannot specify the
> background color by some options to the splash decoders.  AFAIK, there
> is no way to pass option strings to the KLD module...

Actually, there is. Loader saves any parameters passed to the module
as MODINFO_ARGS, which I suppose can be found with
preload_search_info().

> (Even if there is a way to pass options to the splash decoders, we
> have to modify them further so that they search for an empty, unused
> color palette entry to use...)

If it was easy, it wouldn't be fun. ;-)

--
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org

	Given infinite time, 100 monkeys could type out the complete works
of Shakespeare.
	Win 98 source code? Eight monkeys, five minutes.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul  9  1:20:21 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from mailgrd.orion.no (postkontor.orion.no [194.143.1.101])
	by hub.freebsd.org (Postfix) with ESMTP id 7919A15533
	for <freebsd-stable@freebsd.org>; Fri,  9 Jul 1999 01:20:15 -0700 (PDT)
	(envelope-from raymond@orion.no)
Received: from postkontor.orion.no (unverified [62.92.20.132]) by mailgrd.orion.no
 (Integralis SMTPRS 2.04) with ESMTP id <B0000156303@mailgrd.orion.no>;
 Fri, 09 Jul 1999 10:21:02 +0200
Received: from foobar.orion.no by postkontor.orion.no with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1460.8)
	id NJJ1ZMHH; Fri, 9 Jul 1999 10:20:38 +0200
X-Mailer: 21.2 "Clio" XEmacs Lucid (beta12) (via feedmail 8 I);
	VM 6.71 under 21.2 "Clio" XEmacs Lucid (beta12)
From: "Raymond Wiker" <raymond@orion.no>
MIME-Version: 1.0
Message-Id: <14213.45263.666074.885801@foobar.orion.no>
Date: Fri, 9 Jul 1999 10:20:31 +0200 (CEST)
To: Mike Tisdell <mike@netronix.com>
Cc: freebsd-stable@freebsd.org
Subject: Re: VPN question (using ppp and ssh)
In-Reply-To: <4.1.19990708123747.018dfcb0@shuttle.netronix.com>
References: <4.1.19990708123747.018dfcb0@shuttle.netronix.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Mike Tisdell writes:
 > 	
 > 
 > I have setup a VPN using ppp and ssh, using the device !/etc/ppp/secure
 > in the ppp.conf. Amost the same as that provided in the ppp.conf.sample in
 > 2.2.8. I want to use the VPN in the -auto mode because the vpn session is
 > routed over a standard on demand ppp connection to an ISP. The problem that
 > I am having is that when anything (including the idle timer) causes the
 > link to come down and ssh terminates, ppp also terminates with a discripter
 > 0 error.
 > 
 > I have tried listing multiple instances of !/etc/ppp/secure in the device
 > statement in ppp.conf hoping that when ppp sees the failed device it would
 > try the next, but it doesn't. It appears that when ssh terminates and
 > closes stdin/stdout it causes a fatal error that ppp cannot recover from.
 > Does anyone have any ideas on how to get around this?

	It might be possible to get around this by using the port
forwarding mechanism in ssh, instead of using the ssh connection
directly.

	Try putting the following in /etc/services:

ppp-out         6668/tcp   # Outgoing ppp connections

and in /etc/inetd.conf:

ppp-out stream tcp ssh -a -x vpn /usr/sbin/ppp -direct vpn-in

	With a bit of luck(!), this would work as follows:

	- use localhost:6668 as the "device" for ppp

	- a connection to port 6668 (ppp-out) on the local machine
results in an ssh connection to the remote machine

	- this connection, in turn, is terminated by ppp

	Note: vpn is the name of an ssh configuration, while vpn-in is 
the name of a ppp configuration.

	Note 2: you may also need some sort of delay before trying to
bring up the connection again (unless you have more than one tunnel
device...) 

	//Raymond.

-- 
Raymond Wiker, Orion Systems AS
+47 370 61150



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul  9  6:13:41 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from livid.globalserve.net (livid.globalserve.net [209.90.144.71])
	by hub.freebsd.org (Postfix) with ESMTP id 5CC56155B3
	for <freebsd-stable@FreeBSD.ORG>; Fri,  9 Jul 1999 06:13:29 -0700 (PDT)
	(envelope-from nick@globalserve.net)
Received: from localhost (nick@localhost [127.0.0.1])
	by livid.globalserve.net (8.9.3/8.9.3) with ESMTP id JAA22677;
	Fri, 9 Jul 1999 09:15:55 -0400 (EDT)
Date: Fri, 9 Jul 1999 09:15:55 -0400 (EDT)
From: Nicolas Perreten <nick@globalserve.net>
To: Kiril Mitev <kiril@ideaglobal.com>
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: libcrypt links changed, cannot login anymore...
In-Reply-To: <199907081311.OAA05851@ideaglobal.com>
Message-ID: <Pine.BSF.4.05.9907090915250.22403-100000@livid.globalserve.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Redownload all the files in /pub/FreeBSD/src, run "install.sh all", and
do a "make depend; make ; make install. That'll rebuild everything with
the new libraries."

Nicolas Perreten
Systems Administrator
Globalserve Communications Inc., a Primus Canada Company
We learned. We laughed. The best is yet to come.

On Thu, 8 Jul 1999, Kiril Mitev wrote:

> Dear List
> 
> I've changed the libcrypt* links from libdescrypt to libscrypt, and 
> thereby killed completely everybody's logins (read: cannot login 
> anymore).
> 
> I do recall that it was supposed to be OK to do this, or was my recollection
> erm, wrong ?
> 
> 
> 
> Kiril
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
> 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul  9  8:50:20 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from david.siemens.de (david.siemens.de [192.35.17.14])
	by hub.freebsd.org (Postfix) with ESMTP
	id 98A8B14EA4; Fri,  9 Jul 1999 08:50:15 -0700 (PDT)
	(envelope-from ust@cert.siemens.de)
X-Envelope-Sender-Is: ust@cert.siemens.de (at relayer david.siemens.de)
Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14])
	by david.siemens.de (8.9.3/8.9.3) with ESMTP id RAA09109;
	Fri, 9 Jul 1999 17:50:14 +0200 (MET DST)
Received: from mars.cert.siemens.de (ust.mchp.siemens.de [139.23.201.17])
	by mail1.siemens.de (8.9.3/8.9.3) with ESMTP id RAA20311;
	Fri, 9 Jul 1999 17:50:14 +0200 (MET DST)
Received: from alaska.cert.siemens.de (alaska.cert.siemens.de [139.23.202.134])
	by mars.cert.siemens.de (8.9.3/8.9.3/Siemens CERT [ $Revision: 1.9 ]) with ESMTP id RAA05469;
	Fri, 9 Jul 1999 17:51:56 +0200 (CEST)
Received: (from ust@localhost)
	by alaska.cert.siemens.de (8.9.3/8.9.3/alaska [ $Revision: 1.2 ]) id PAA28634;
	Fri, 9 Jul 1999 15:51:56 GMT
	(envelope-from ust)
Date: Fri, 9 Jul 1999 17:51:56 +0200
From: Udo Schweigert <ust@cert.siemens.de>
To: freebsd-stable@freebsd.org, cvs-all@freebsd.org
Subject: dhclient.conf missing when making world
Message-ID: <19990709175156.A28493@alaska.cert.siemens.de>
Mail-Followup-To: freebsd-stable@freebsd.org, cvs-all@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
X-Operating-System: FreeBSD 3.2-STABLE
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello,

today I got the following after a make world.

/usr/obj/home/src/RELENG_3/tmp/usr/bin/make etc-examples)
(cd /home/src/RELENG_3/etc;  install -C -c -o root -g wheel -m 444 aliases amd.map auth.conf crontab csh.cshrc csh.login csh.logout  dhclient.conf dm.conf fbtab ftpusers gettytab group hosts hosts.allow  host.conf hosts.equiv hosts.lpd inetd.conf login.access login.conf  motd modems networks newsyslog.conf pam.conf pccard.conf.sample  phones printcap profile protocols rc rc.atm rc.devfs rc.diskless1  rc.diskless2 rc.firewall rc.isdn rc.network rc.pccard rc.serial  rc.shutdown etc.i386/rc.i386 remote security  services shells syslog.conf etc.i386/ttys  etc.i386/disktab rpc make.conf /home/src/RELENG_3/etc/../gnu/usr.bin/man/manpath/manpath.config /home/src/RELENG_3/etc/../usr.bin/mail/misc/mail.rc /home/src/RELENG_3/etc/../usr.bin/locate/locate/locate.rc netstart pccard_ether /usr/share/examples/etc;  install -C -c -o root -g wheel -m 444 defaults/rc.conf /usr/share/examples/etc/defaults)                            
install: dhclient.conf: No such file or directory                               
*** Error code 71 (continuing)                            

Regards
-------------------------------------------------------------------------------
Udo Schweigert              || Voice      : +49 89 636 42170
Siemens AG, Siemens CERT    || Fax        : +49 89 636 48000
ZT IK 3                     || email      : Udo.Schweigert@mchp.siemens.de
D-81730 Muenchen / Germany  ||            : ust@cert.siemens.de
PGP fingerprint             || 2A 53 F6 A6 30 59 64 02  6B C4 E0 73 B2 C9 6C E7
-------------------------------------------------------------------------------


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul  9 15:43:35 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5])
	by hub.freebsd.org (Postfix) with ESMTP id 6556A14E10
	for <stable@freebsd.org>; Fri,  9 Jul 1999 15:43:29 -0700 (PDT)
	(envelope-from rhh@ipass.net)
Received: from stealth.ipass.net. (ppp-3-8.dialup.rdu.ipass.net [209.170.134.8])
	by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id SAA04094;
	Fri, 9 Jul 1999 18:43:23 -0400 (EDT)
Received: (from rhh@localhost)
	by stealth.ipass.net. (8.9.3/8.8.8) id SAA03384;
	Fri, 9 Jul 1999 18:45:27 -0400 (EDT)
	(envelope-from rhh)
Date: Fri, 9 Jul 1999 18:45:27 -0400
From: Randall Hopper <aa8vb@ipass.net>
To: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Cc: stable@freebsd.org
Subject: Re: Splash Background Color
Message-ID: <19990709184527.A1225@ipass.net>
References: <199907082225.SAA06505@smtp3.erols.com> <19990708193133.A6924@ipass.net> <19990708214304.A1736@ipass.net> <199907090410.NAA25966@zodiac.mech.utsunomiya-u.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.1i
In-Reply-To: <199907090410.NAA25966@zodiac.mech.utsunomiya-u.ac.jp>; from Kazutaka YOKOTA on Fri, Jul 09, 1999 at 01:10:45PM +0900
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Kazutaka YOKOTA:
 |>Is there a way to change the background (overscan) color used to display
 |>VESA splash pics?
 |>
 |>Those saturn splash screens look nice, but the overscan is fire engine
 |>read -- most annoying.
...
 |What you see as the background and border color is whichever color happen
 |to be set in the color palette 0 in the bitmap file.
...
1)
 |assumption that bitmap files tend to store frequently used colors at the
 |beginning of the color palette table
...
2)
 |Alternative approach would be that we search for "black" palette and use
 |that palette index number to fill the background.

If there's some cool tool that we can point people to, which will let them
easily put the preferred background color in slot 0 in the bitmap file's
color table and rewrite the file, then Option #1 sounds like a good way to
go.

If there isn't, I'd be interested in a way to do Option #2.

 |As for options to specify the background color, you cannot specify the
 |background color by some options to the splash decoders.  AFAIK, there
 |is no way to pass option strings to the KLD module...

Ok.

Thanks,

Randall


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul  9 18:17:32 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from server1.siscom.net (server1.siscom.net [209.251.2.89])
	by hub.freebsd.org (Postfix) with SMTP id 8567814DD6
	for <stable@freebsd.org>; Fri,  9 Jul 1999 18:17:23 -0700 (PDT)
	(envelope-from radams@siscom.net)
Received: (qmail 59531 invoked from network); 10 Jul 1999 01:17:22 -0000
Received: from mp.siscom.net (HELO jason) ([209.251.2.49]) (envelope-sender <radams@siscom.net>)
          by server1.siscom.net (qmail-ldap-1.03) with SMTP
          for <hardware@freebsd.org>; 10 Jul 1999 01:17:22 -0000
Message-ID: <04a901beca73$93a70940$3102fbd1@siscom.net>
From: "Robert J. Adams" <radams@siscom.net>
To: <hardware@freebsd.org>
Cc: <stable@freebsd.org>
Subject: Fibre Channel Controller
Date: Fri, 9 Jul 1999 21:28:53 -0400
Organization: SISCOM, Inc.
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hello all,

Anyone know of a Fibre Channel Controller that is compatible with FBSD?

-j

---
Robert J. Adams radams@siscom.net http://www.siscom.net
Looking to outsource news? http://www.newshosting.com
SISCOM Network Administration - President, SISCOM Inc.
Phone: 937-222-8150 FAX: 937-222-8153 



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul  9 18:20:31 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id D7A6914DD6; Fri,  9 Jul 1999 18:20:24 -0700 (PDT)
	(envelope-from mjacob@feral.com)
Received: from semuta.feral.com (semuta [192.67.166.70])
	by feral.com (8.8.7/8.8.7) with ESMTP id SAA27421;
	Fri, 9 Jul 1999 18:20:11 -0700
Date: Fri, 9 Jul 1999 18:20:11 -0700 (PDT)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: "Robert J. Adams" <radams@siscom.net>
Cc: hardware@FreeBSD.ORG, stable@FreeBSD.ORG
Subject: Re: Fibre Channel Controller
In-Reply-To: <04a901beca73$93a70940$3102fbd1@siscom.net>
Message-ID: <Pine.BSF.4.05.9907091819510.385-100000@semuta.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



> Hello all,
> 
> Anyone know of a Fibre Channel Controller that is compatible with FBSD?

Qlogic 2100/2200. It's part of 3.0 and later, but has been backported into
2.2.X.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Fri Jul  9 20:56:14 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from netrinsics.com (unknown [210.74.177.14])
	by hub.freebsd.org (Postfix) with ESMTP id 6ECFD14D07
	for <freebsd-stable@freebsd.org>; Fri,  9 Jul 1999 20:56:06 -0700 (PDT)
	(envelope-from robinson@netrinsics.com)
Received: (from robinson@localhost)
	by netrinsics.com (8.9.3/8.8.7) id LAA24952
	for freebsd-stable@freebsd.org; Sat, 10 Jul 1999 11:55:21 +0800 (CST)
	(envelope-from robinson)
Date: Sat, 10 Jul 1999 11:55:21 +0800 (CST)
From: Michael Robinson <robinson@netrinsics.com>
Message-Id: <199907100355.LAA24952@netrinsics.com>
To: freebsd-stable@freebsd.org
Subject: Persistent IPC locks in FreeBSD?
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Under Solaris, you can initialize a pthread_mutex_t in mmapped memory that
can be shared by any process that mmaps the same object, even after the first
process exits.  This has the advantage that the mutex is tightly and
unambiguously bound to the data in the mmapped file, even through reboots
(or even kernel upgrades), and is automatically removed when the mmapped 
file is deleted or reinitialized.

From what I can tell from the documentation, this sort of persistent IPC
behavior is unavailable for a FreeBSD pthread_mutex.  Furthermore, the
alternative--SysV semaphores--have problematic creation, persistence, and
destruction semantics.

Is this basically the way it is, and I just have to live with it, or have
I overlooked something?

	-Michael Robinson



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message


From owner-freebsd-stable  Sat Jul 10 12:50:10 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from mail.cybcon.com (mail.cybcon.com [205.147.76.5])
	by hub.freebsd.org (Postfix) with ESMTP
	id 249F214C05; Sat, 10 Jul 1999 12:50:04 -0700 (PDT)
	(envelope-from wwoods@cybcon.com)
Received: from ns1.cybcon.com (wwoods@ns1.cybcon.com [205.147.76.1])
	by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id MAA06524;
	Sat, 10 Jul 1999 12:50:04 -0700 (PDT)
Date: Sat, 10 Jul 1999 12:50:03 -0700 (PDT)
From: Bill Woods <wwoods@cybcon.com>
To: freebsd-stable@freebsd.org
Cc: freebsd-ports@freebsd.org
Subject: linux-base port....help please
Message-ID: <Pine.BSI.4.05L.9907101246150.2179-100000@pdx.cybcon.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I was installing the linux-base port and doing a make install produces:

execution of script failed
error: /usr/ports/distfiles/rpm/libc-5.3.12-27.i386.rpm cannot be
installed
libg++-2.7.2.8-9.i386.rpm
libstdc++-2.8.0-14.i386.rpm
sh-utils-1.16-14.i386.rpm
ELF interpreter /compat/linux/lib/ld-linux.so.2 not found
execution of script failed
error: /usr/ports/distfiles/rpm/sh-utils-1.16-14.i386.rpm cannot be
installed
readline-2.2.1-1.i386.rpm
ELF interpreter /compat/linux/lib/ld-linux.so.2 not found
execution of script failed
error: /usr/ports/distfiles/rpm/readline-2.2.1-1.i386.rpm cannot be
installed
redhat-release-5.2-1.noarch.rpm
rpm-2.5.5-5.2.i386.rpm
ELF interpreter /compat/linux/lib/ld-linux.so.2 not found
execution of script failed
error: /usr/ports/distfiles/rpm/rpm-2.5.5-5.2.i386.rpm cannot be installed
brandelf -t Linux /compat/linux/bin/rpm
setserial-2.14-4.i386.rpm
slang-0.99.38-8.i386.rpm
stat-1.5-8.i386.rpm
tcsh-6.07.09-1.i386.rpm
ELF interpreter /compat/linux/lib/ld-linux.so.2 not found
execution of script failed
error: /usr/ports/distfiles/rpm/tcsh-6.07.09-1.i386.rpm cannot be
installed
*** Error code 1

Stop.
*** Error code 1

Stop.
*** Error code 1

Stop.

I have linux_libs installed, but I got the same error without them
installed.....
any ideas?

William





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message