FreebSD 3.5S to FreeBSD 4.x-STABLE problem

Hi! I'm trying to upgrade my system to 4.x-STABLE. The system runs a fresh 3.5-stable and I've cvsup'ed the source to RELENG_4. I've tried removing /usr/src and cvsuping, I've tried updating my existant /usr/src to RELENG_4. When I follow /usr/src/UPDATING I always get the same error: Extractin

Re: passwd (still) broken in NIS environments

Do you have the same crypting algorithm on both ends ? (FreeBSD recently went to MD5 as a standard - Solaris most likely is still using DES) TfH Gerald Pfeifer <[EMAIL PROTECTED]> on 23/01/2001 11:40:07

Running with very high HZ ?

Hello, is there any limitations to the frequency of the clock ? more precisely : is it ok to run a recent PC (P-III + BX chipset) with HZ=5000 ? (I remember a comment in ipfw or dummynet advising the use of HZ=1000, is-it ok to go higher ?) TfH To Unsubscribe: send mail to [EMAIL PRO

make buildworld fails

Hi, "make buildworld" constantly fails on my 4.2-STABLE machine. I cvsup'ed freshly, but the problem persists. Here is the error log: -- >>> stage 4: make dependencies -- cd /u

Re: make buildworld fails

Lukas Ertl wrote: > > Hi, > > "make buildworld" constantly fails on my 4.2-STABLE machine. I cvsup'ed > freshly, but the problem persists. Here is the error log: > > -I/usr/obj/usr/src/i386/usr/include /usr/src/bin/chio/chio.c > cpp: Memory exhausted. How much memory is in this box ? and wh

Re: make buildworld fails

On Tue, 23 Jan 2001, Simon Loader wrote: > Lukas Ertl wrote: > > > > Hi, > > > > "make buildworld" constantly fails on my 4.2-STABLE machine. I cvsup'ed > > freshly, but the problem persists. Here is the error log: > > > > > -I/usr/obj/usr/src/i386/usr/include /usr/src/bin/chio/chio.c > > cpp: M

Re: passwd (still) broken in NIS environments

On Tue, 23 Jan 2001 [EMAIL PROTECTED] wrote: > Do you have the same crypting algorithm on both ends ? > (FreeBSD recently went to MD5 as a standard - Solaris most > likely is still using DES) Yes, the Solaris NIS Server is using DES. However, as we don't have problems logging in, just changing pa

softupdates/NFS/vinum(?) panics

I have been getting frequent panics: softdep_lock: locking against myself These have been occurring since an incident on 16th January, where the SCSI cable was accidentally unplugged on a running system, and vinum had trouble recovering. That incident almost certainly caused some arbitrary

Re: Dell PERC 3 support?

Alfred Perlstein stated: : A friend just asked me if we support the PERC 3 cards shipped in : Dell servers. If not, anyone have a recommendation for a controller : in the same price performance category that is supported? Alfred- The PERC 3 cards use the aac driver which was only very recently

Re: passwd (still) broken in NIS environments

Gerald Pfeifer wrote: > > On Tue, 23 Jan 2001 [EMAIL PROTECTED] wrote: > > Do you have the same crypting algorithm on both ends ? > > (FreeBSD recently went to MD5 as a standard - Solaris most > > likely is still using DES) > > Yes, the Solaris NIS Server is using DES. However, as we don't have

Re: Dell PERC 3 support?

- Original Message - From: "Sean O'Connell" <[EMAIL PROTECTED]> > The PERC 3 cards use the aac driver which was only very recently > MFC'd (it should work with a recent snapshot). The card should > work and you can download from Dell a Linux command line tool to > do some work with the

Re: libgcc_pic is gone (affects Wine port)

Quoting Gerald Pfeifer <[EMAIL PROTECTED]>: > Due to a serious bug in the port of GCC used in the base system > (see ) I and > probably others had to explicitly link against libgcc_pic. > > This bug has been fixed (around 4.2-RELEASE), but also l

Re: Dell PERC 3 support?

Shawn Barnhart stated: : Have you gotten an aac card to work under STABLE? I tried with the : following procedure within a week of the MFC of the aac driver. Card make : was a HP Netraid 4M connected to a HP rackstorage/12 (6 disks, raid 5): : : 1) build STABLE kernel on updated STABLE machine

Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export (was: Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, ReiserFS)

Note: when replying, please remove the (was: ) part of the Subject and the reiserfs-list from the recipients. On Tue, 23 Jan 2001, Guy Harris wrote: > Perhaps the Linux server should, in "nfsd_access()", treat "nfserr_rofs" > the same way it treats "nfserr_perm" and "nfserr_acces", and just say