Re: dot-0 releases

[Brad Knowles]

At 3:40 PM -0800 2000/3/21, Jordan K. Hubbard wrote:

>  Actually, those our outdated statements and I'm going to ask the
>  Walnut Creek CDROM postmaster to remove them.  They only send a
>  confusing message.  Thanks for the reminder. :)

So, you're saying that it's perfectly safe for me to replace the 
one and only news peering server that we have (currently running 3.x) 
with one running 4.0-RELEASE, and if we have any problems then you'll 
personally fly out here to fix it?  ;-)

I hope you'll forgive me if I tend to be slightly more 
conservative than this, and if I recommend that others do the same. 
We're not all clones of David Greenman, Jordan K. Hubbard, or Mike 
O'Dell.  ;-)

--
   These are my opinions -- not to be taken as official Skynet policy
==
Brad Knowles, <[EMAIL PROTECTED]>|| Belgacom Skynet SA/NV
Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124
Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels
http://www.skynet.be || Belgium


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

Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?)

[Warner Losh]

In message  Brad Knowles writes:
:   However, that's precisely the kind of additional work that needs 
: to get folded into 4.0, so that 4.1 or 4.2 *is* ready for general use 
: in a production environment.

What, specifically, is broken in 4.0 that would preclude its use in
production systems?

Warner


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

dot-0 releases

[Brandon D. Valentine]

About time this thread got its own subject line.

On Tue, 21 Mar 2000, David Murphy wrote:

>Then we're in agreement on what an X.0 release should be. I'm
>genuinely glad we understand each other, and would suggest that a note
>similar to the above in the release notes/announcement would greatly
>improve the new user's understanding of what X.0-RELEASE is and is not
>suited for/aimed at.

>From http://www.cdrom.com/titles/freebsd/bsd40offer.phtml:

"FreeBSD 4.0 will probably be released in March 2000 as a
fully-operational release, rather than a Snapshot. However, we don't
expect all FreeBSD customers are quite ready for a major "dot-0" release
so we're only offering it to those of you brave souls who REALLY want
it."

>From http://www.freebsdmall.com/software/:

"FreeBSD 4.0 - A full, professional quality, UNIX-compatible operating
system. Prerelease for developers and early-adopters. Not appropriate
for production-level environment yet."

If you're a new user the above certainly warns you.  If you're getting 4.0
via cvsup, installing over the internet or are downloading the
setup files from an ftp site, chances are you also are bright enough to do a
little bit of research before installing.  Generalizations aside, there
will always be brutes who would rather learn to wear safety goggles
after something in their blue collar environment decides to go
careening into their cornea.

-
| -Brandon D. Valentinebandix at looksharp.net
|  bandix on EFnet IRC BVRiker on AIM
-
| "...and as for hackers, we note that all of those known to
| The Register are so strapped financially that seizing their
| property would be tantamount to squeezing blood from a
| stone." -- The Register, 02/17/2000
-



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

Re: Voxware is toast. Get used to it. (Re: Suggestions for improving newpcm performance?)

[Jeffrey J. Mountin]

At 10:07 AM 3/21/00 -0700, John Reynolds~ wrote:
>I would have to agree with Jordan here. Of course with the plethora of PC
>hardware combinations out there (with some of the marginally designed
>components people pick up) it is impossible for the developers to make sure
>100% of everything "works as expected (TM)."
>
>I went through the 2.2.8->3.0 transition and now I've installed 4.0-RC, RC2,
>and RC3 on the same hardware that I did the 2.2.8->3.0 transition on and I can
>say without a doubt that 4.0 is a *much* better ".0" release than 3.0 was.

And I will second this a few times over.

>This "crypto" thing is tripping people up, but it's just a matter of RTFM, not
>instability of the software.

There is more tripping involved with doing a 3.x -> 4.0 source 
upgrade.  Seems to be an endless discussion about upgrading from source and 
AFAICR is much more toublesome than the 2.x - 3.0 with aout -> elf.  Can't 
see it for a production environment.  Rather swap a disk or server.  Less 
pain, problems, and much easier to keep downtime at a minimum in the event 
something doesn't work out right.


Jeff Mountin - [EMAIL PROTECTED]
Systems/Network Administrator
FreeBSD - the power to serve



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

Re: make world fails

[Brandon D. Valentine]

On Tue, 21 Mar 2000, Carl Johan Madestrand wrote:

>rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/spray.x -o spray.h
>unsigned hnt usec;

Last time I checked there was no type unsigned hnt in the standard
library.  ;-)  It should read unsigned int.  Not sure who's fault that is.

-
| -Brandon D. Valentinebandix at looksharp.net
|  bandix on EFnet IRC BVRiker on AIM
-
| "...and as for hackers, we note that all of those known to
| The Register are so strapped financially that seizing their
| property would be tantamount to squeezing blood from a
| stone." -- The Register, 02/17/2000
-



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

Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions

[Warner Losh]

In message <[EMAIL PROTECTED]> "Jeffrey J. Mountin" writes:
: Are you saying that da0a is (almost) functionally equivalent to da0s3a if 
: slice 3 is the first FBSD slice.  Thought they were for "dangerously 
: dedicated" partitions.

No.  That's not correct.  While they are used in dangerously (and
stupidly) dedicated mode, they can be used at any time.  I still have
some mount points on my -current machine that refer to sd1c because
I've been too lazy to update them.

: Sounds similar to da0 being the same as da0s1 for disklabel.  Hmmm...

Not quite.  Those aren't really the same.

: >It is a shame that you can't use them to mount / on / in an
: >emergency.  The consistancy checks won't let you.
: 
: Agreed.  The few times I've needed to use a fixit floppy or CD...
: Let's just say it isn't fun. 8-/

But if you can mount it as /mnt, then you can usually fix it.  :-)

Warner


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

make world fails

[Carl Johan Madestrand]

cvsupped today, 4.0-STABLE, make buildworld.
The compilation fails after a while. 

===> rpcsvc
rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/key_prot.x -o key_prot.h
rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/klm_prot.x -o klm_prot.h
rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/mount.x -o mount.h
rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/nfs_prot.x -o nfs_prot.h
rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/nlm_prot.x -o nlm_prot.h
rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/rex.x -o rex.h
rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/rnusers.x -o rnusers.h
rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/rquota.x -o rquota.h
rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/rstat.x -o rstat.h
rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/rwall.x -o rwall.h
rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/sm_inter.x -o sm_inter.h
rpcgen -C -h -DWANT_NFS3 /usr/src/include/rpcsvc/spray.x -o spray.h
unsigned hnt usec;
^
rpcgen: /usr/src/include/rpcsvc/spray.x, line 51: expected ';'
*** Error code 1

Any Ideas?

-- 
- Carl Johan Madestrand <[EMAIL PROTECTED]>
- IRC: Lord_CJ 
- ICQ: 46955545


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

Re: unusual cvsup message

[Jeffrey J. Mountin]

At 04:28 PM 3/19/00 -0800, Sameer R. Manek wrote:
>I got this message on a cvsup performed today, at about Sun Mar 19 15:07:18
>PST 2000, anyone else get a similar message? and should i be concerned about
>it?

Not quite the same here:  Should not be a problem, since the entire file is 
fetched.

>  Edit src/sys/contrib/dev/oltr/trlld.h
>src/sys/contrib/dev/oltr/trlld.h: Cannot get edited text: "d" edit command
>specifies line past end of base delta -- will transfer entire file

  Edit src/sys/contrib/dev/oltr/trlld.h
   Add delta 1.3.2.1 2000.03.19.00.32.34 lile
src/sys/contrib/dev/oltr/trlld.h: Checksum mismatch -- will transfer entire 
file

As of about an hour ago with virgin 4.0R (first rollese) sources.


Jeff Mountin - [EMAIL PROTECTED]
Systems/Network Administrator
FreeBSD - the power to serve



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

Re: 3.4S->4.0S upgrade: make buildworld failing

[Christopher J . Gibbons]

I ran into the exact same situation when I upgraded from 3.4,
commenting out the KERBEROS line in make.conf does indeed cause the
build to complete and you can perform the upgrade as provided in
/usr/src/UPDATING.

Once upgraded, I believe you can rebuild the system yet again
under 4.0 and enable KERBEROS in make.conf, although I haven't tried 
it I think I saw it posted here before...might be an exercise for myself 
later tonight. ;-)

Hope this helps,

+---
| Christopher J. Gibbons   UNIX Systems Admin.   [EMAIL PROTECTED]
+---

From: Scott Allendorf <[EMAIL PROTECTED]>
Subject: 3.4S->4.0S upgrade: make buildworld failing
Date: Tue, 21 Mar 2000 15:25:29 -0600 (CST)

> I am attempting to upgrade from 3.4-STABLE (cvsupped/built late last
> week) to 4.0-STABLE cvsupped this morning into a clean /usr/src.  The
> supfile was /usr/src/share/examples/cvsup/stable-supfile with cvs-crypto
> uncommented and RELENG_3 changed to RELENG_4.  Whenever MAKE_KERBEROS4 is
> uncommented in /etc/make.conf, "make buildworld" fails with the error
> shown below.  Adding "RSAREF= YES" to /etc/make.conf does not change
> anything.  Commenting out the MAKE_KERBEROS4 definition allows the build
> to complete.  Is anyone else seeing this?  Is it pilot error or have I
> stumbled onto a problem or an omission in the instructions in
> /usr/src/UPDATING?
> 
> Cheers,
> 
> Scott
> 
> Script started on Tue Mar 21 13:03:32 2000
> 
> host# grep -v ^\# /etc/make.conf
> CFLAGS= -O -pipe
> COPTFLAGS= -O -pipe
> COMPAT1X= yes
> COMPAT20= yes
> COMPAT21= yes
> COMPAT22= yes
> HAVE_MOTIF=   yes
> USA_RESIDENT= YES
> MAKE_KERBEROS4=   yes
> SUP_UPDATE= yes
> SUP=/usr/local/bin/cvsup
> SUPFLAGS=   -g -L 2
> SUPFILE=/usr/local/etc/cvsup/stable-supfile
> SUPFILE2=   /usr/local/etc/cvsup/ports-supfile
> TOP_TABLE_SIZE= 101
> 
> host# cd /usr/src
> host# ls /usr/obj
> host# make buildworld
> 
> --
> >>> Rebuilding the temporary build tree
> --
> 
> ... All was well until ...
> 
> ===> libkadm
> ln -sf /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/include/protos.H 
>protos.h
> rm -f .depend
> mkdep -f .depend -a
>-I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/include 
>-I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../include 
>-I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/krb 
>-I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kdb 
>-I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm 
>-I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/roken 
>-I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb 
>-I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm 
>-I/usr/obj/usr/src/kerberosIV/lib/libkadm 
>-I/usr/src/kerberosIV/lib/libkadm/../../include -DHAVE_CONFIG_H 
>-I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../include -DBINDIR=\"/usr/bin\" 
>-DSBINDIR=\"/usr/sbin\" -I/usr/obj/usr/src/i386/usr/include  
>/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_cli_wrap.c 
>/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_stream.c 
>/usr/src/kerberosIV/lib/libkadm/..!
> !
> /../../crypto/kerberosIV/lib/kadm/kadm_supp.c 
>/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.c 
>/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/check_password.c
> In file included from 
>/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:75,
>  from 
>/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_cli_wrap.c:30:
> /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: invalid macro 
>name
> In file included from 
>/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:78,
>  from 
>/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_cli_wrap.c:30:
> /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: warning: 
>`ERROR_TABLE_BASE_' redefined
> /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: warning: this 
>is the location of the previous definition
> /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: invalid 
>macro name
> In file included from 
>/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:75,
>  from 
>/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_stream.c:38:
> /usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: invalid macro 
>name
> In file included from 
>/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:78,
>  from 
>/usr/src/kerber

Re: HEADS UP: 3.x -> 4.0-STABLE upgrade instructions

[Jeffrey J. Mountin]

At 11:20 AM 3/19/00 -0700, Warner Losh wrote:
>In message <[EMAIL PROTECTED]> Brandon Fosdick writes:
>: I thought of that, but I didn't know what the devices w/o slice numbers
>: did. Guess I should have just tried it.
>
>Devices w/o slice numbers are the "compatibility" devices.  These map
>to the first BSD partition on the disk.  For most people, this is the
>only partition on the disk.

Are you saying that da0a is (almost) functionally equivalent to da0s3a if 
slice 3 is the first FBSD slice.  Thought they were for "dangerously 
dedicated" partitions.

Sounds similar to da0 being the same as da0s1 for disklabel.  Hmmm...

Changed an fstab entry from ad1s1e to ad1e and it works.

>It is a shame that you can't use them to mount / on / in an
>emergency.  The consistancy checks won't let you.

Agreed.  The few times I've needed to use a fixit floppy or CD...
Let's just say it isn't fun. 8-/

--snip--


Jeff Mountin - [EMAIL PROTECTED]
Systems/Network Administrator
FreeBSD - the power to serve



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

bru2000 15.1 elf

[Rodney Whipple]

Hi

I am currently trying to get Bru2000 15.1 which is the elf version.  I
keep getting an error upon ./install
that tells me

try bru -h ...elf binary type not known   use brandelf
try  bru.static -h ...elf binary type not know

I have tried the brandelf to the file bru still the same error.

Has any ran into the same thing and how do I get around it.  I have
tried installing the port
elftoaout and still the same error.  Bru still has an a.out 15.1
solution but am trying to
go with the elf version since it seems the right direction.

--
Thank You

Rodney Whipple
ATCjet.net
Internet Services
[EMAIL PROTECTED]
1-888-565-5422




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

3.4S->4.0S upgrade: make buildworld failing

[Scott Allendorf]

I am attempting to upgrade from 3.4-STABLE (cvsupped/built late last
week) to 4.0-STABLE cvsupped this morning into a clean /usr/src.  The
supfile was /usr/src/share/examples/cvsup/stable-supfile with cvs-crypto
uncommented and RELENG_3 changed to RELENG_4.  Whenever MAKE_KERBEROS4 is
uncommented in /etc/make.conf, "make buildworld" fails with the error
shown below.  Adding "RSAREF= YES" to /etc/make.conf does not change
anything.  Commenting out the MAKE_KERBEROS4 definition allows the build
to complete.  Is anyone else seeing this?  Is it pilot error or have I
stumbled onto a problem or an omission in the instructions in
/usr/src/UPDATING?

Cheers,

Scott

Script started on Tue Mar 21 13:03:32 2000

host# grep -v ^\# /etc/make.conf
CFLAGS= -O -pipe
COPTFLAGS= -O -pipe
COMPAT1X=   yes
COMPAT20=   yes
COMPAT21=   yes
COMPAT22=   yes
HAVE_MOTIF= yes
USA_RESIDENT=   YES
MAKE_KERBEROS4= yes
SUP_UPDATE= yes
SUP=/usr/local/bin/cvsup
SUPFLAGS=   -g -L 2
SUPFILE=/usr/local/etc/cvsup/stable-supfile
SUPFILE2=   /usr/local/etc/cvsup/ports-supfile
TOP_TABLE_SIZE= 101

host# cd /usr/src
host# ls /usr/obj
host# make buildworld

--
>>> Rebuilding the temporary build tree
--

... All was well until ...

===> libkadm
ln -sf /usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/include/protos.H 
protos.h
rm -f .depend
mkdep -f .depend -a
-I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/include 
-I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../include 
-I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/krb 
-I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kdb 
-I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm 
-I/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/roken 
-I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb 
-I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm 
-I/usr/obj/usr/src/kerberosIV/lib/libkadm 
-I/usr/src/kerberosIV/lib/libkadm/../../include -DHAVE_CONFIG_H 
-I/usr/obj/usr/src/kerberosIV/lib/libkadm/../../include -DBINDIR=\"/usr/bin\" 
-DSBINDIR=\"/usr/sbin\" -I/usr/obj/usr/src/i386/usr/include  
/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_cli_wrap.c 
/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_stream.c 
/usr/src/kerberosIV/lib/libkadm/..!
/../../crypto/kerberosIV/lib/kadm/kadm_supp.c 
/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.c 
/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/check_password.c
In file included from 
/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:75,
 from 
/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_cli_wrap.c:30:
/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: invalid macro 
name
In file included from 
/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:78,
 from 
/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_cli_wrap.c:30:
/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: warning: 
`ERROR_TABLE_BASE_' redefined
/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: warning: this 
is the location of the previous definition
/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: invalid macro 
name
In file included from 
/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:75,
 from 
/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_stream.c:38:
/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: invalid macro 
name
In file included from 
/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:78,
 from 
/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_stream.c:38:
/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:13: warning: 
`ERROR_TABLE_BASE_' redefined
/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:13: warning: this 
is the location of the previous definition
/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkadm/kadm_err.h:17: invalid macro 
name
In file included from 
/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:75,
 from 
/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_supp.c:36:
/usr/obj/usr/src/kerberosIV/lib/libkadm/../../lib/libkrb/krb_err.h:17: invalid macro 
name
In file included from 
/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_locl.h:78,
 from 
/usr/src/kerberosIV/lib/libkadm/../../../crypto/kerberosIV/lib/kadm/kadm_supp.c:36:
/usr/obj/usr/src/kerberosIV/lib/libkadm/.

Re: 3.4->4.0 ld-elf.so.1 error?

[Mark Ovens]

On Tue, Mar 21, 2000 at 12:46:38PM -0800, Kris Kennaway wrote:
> On Mon, 20 Mar 2000, Mark Ovens wrote:
> 
> > # ldconfig -R /usr/obj/usr/src/lib/libc
> 
> or something like setenv LD_LIBRARY_PATH /usr/obj/usr/src/lib/libc
> 

Why would you set LD_LIBRARY_PATH? ``ldconfig -R '' worked fine
for me, I only needed it to build the kernel. After installworld
libc.so.4 wasn't a problem.

> > # config YOUR-KERNEL-HERE
> 
> Kris
> 
> 
> In God we Trust -- all others must submit an X.509 certificate.
> -- Charles Forsythe <[EMAIL PROTECTED]>
> 
> 
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-stable" in the body of the message

-- 
Seminars, n.:
   From "semi" and "arse", hence, any half-assed discussion.

  FreeBSD - The Power To Serve http://www.freebsd.org
  My Webpage http://ukug.uk.freebsd.org/~mark/
mailto:[EMAIL PROTECTED] http://www.radan.com



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

Re: Voxware is toast. Get used to it. (Re: Suggestions forimproving newpcm performance?)

[Brad Knowles]

At 11:25 AM -0800 2000/3/21, Jordan K. Hubbard wrote:

>  Which areas are these?  Again, please be specific so that I can
>  actually respond to this rather than going "What the hell is this man
>  even talking about?" :-)

Alright, as I get first-hand details of problems that I am 
personally experiencing with 4.0-STABLE, I will post them here or in 
-current, as I feel more appropriate.


In fact, you may want to look at a message I just posted on 
-current with regards to vinum and rawio, although at this stage I'm 
at the "what the hell did I do wrong?" stage, and can't do much more 
than identify that there is some sort of problem.

--
   These are my opinions -- not to be taken as official Skynet policy
==
Brad Knowles, <[EMAIL PROTECTED]>|| Belgacom Skynet SA/NV
Systems Architect, Mail/News/FTP/Proxy Admin || Rue Colonel Bourg, 124
Phone/Fax: +32-2-706.13.11/12.49 || B-1140 Brussels
http://www.skynet.be || Belgium


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

Re: 3.4->4.0 ld-elf.so.1 error?

[Kris Kennaway]

On Mon, 20 Mar 2000, Mark Ovens wrote:

>   # ldconfig -R /usr/obj/usr/src/lib/libc

or something like setenv LD_LIBRARY_PATH /usr/obj/usr/src/lib/libc

>   # config YOUR-KERNEL-HERE

Kris


In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <[EMAIL PROTECTED]>



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