Re: Sil680 RAID Support while installing 5.1-Release

[Gabriel Ambuehl]

Hi Travis Troyer,
you wrote.

TT> I just purchased a Sil680 IDE RAID controller, and have setup
TT> a striped RAID array.  When I boot from the 5.1 installation
TT> CD-ROM, FreeBSD does not recognize them as one disk.  I
TT> checked the hardware notes, and "Sil680 UDMA6" is listed. 
TT> Seeing Sil680 listed, I assumed that the RAID capabilities
TT> would also be supported.  I read something posted awhile back
TT> referring to the Sil680 controller, saying it was supported,
TT> but dangerous unless using 5.1-Current.  Does anybody know
TT> anything about the current status of this?  Is there anyway to
TT> get the FreeBSD installation to recognize my RAID array, or
TT> should I just buy another controller?

I was wondering about the online Sil 3112 SATA RAID controller on my
Gigabyte 7VAXP board. The 5.1 RELEASE boot CD crashes saying it
couldn't write to root (which is weird, considering it usually should
be able to write to memfs??).




Regards,
Gabriel

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re[2]: Sil680 RAID Support while installing 5.1-Release

[Gabriel Ambuehl]

Hello Derek,

Saturday, September 27, 2003, 8:50:21 PM, you wrote:

> Gabriel,

> I experienced the same problem using 5.1 release with an Adaptec SATA
> Raid card that uses the SATA Sil3112A chip.

> With 5.1-CURRENT I can get FreeBSD to install, but the server locks-up
> because the disk subsystem gets a DMA write error that it either never
> recovers from or falls into the debugger (most times it does NOT go to
> the debugger.)

> There are a few of us using SATA Sil3112A chips and experiencing these
> problems.


It seems to boot ok with the latest snapshot boot cd from
current.freebsd.org HOWEVER whatever I do, the disks will show up
individually in the setup and not as array.


Best regards,
 Gabriel

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

SiL3112 SATA (RAID) Controller drives aren't working at all.

[Gabriel Ambuehl]

The drivers in 28.9.JPSNAP of current will allow you to install
FreeBSD on a SATA disk connected to a Silicon Image 3112 SATA RAID
controller but not much more. Shortly after booting, the system will
start getting UDMA timeouts and basically just freezes. Furthermore,
the disks connected to the controller will ALWAYS show up as
individual disks in the setup, no matter if they are alone, in a
stripe set or a real RAID 1 array.

Seeing that this probably belongs in Soren's domain, is there any
possibility to add some function to atacontrol to allow rebuilding
without having hotswap on HPT/Promise chipsets? (I know the Windows
drivers of both can do so, so imagine the feature has to be
somewhere).

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re[2]: SiL3112 SATA (RAID) Controller drives aren't working at all.

[Gabriel Ambuehl]

Hi Derek Ragona,
you wrote.

DR> My troublesome system uses an Adaptec Serial ATA RAID 1210SA which has the
DR> SiI3112 RAID chip.  I have only one drive connected, so no RAID functionality.

DR> Here is my verbose dmesg using the 9/28/03 snapshot:
DR> http://www.computinginnovations.com/dmesg.html

My 28.8.03 JPSNAP (i.e. current.freebsd.org) box with two Maxtor 120
GB SATA drives connected to the Sil3112 chip will probe both disks ok,
comes up normally but shortly thereafter goes under in a bunch of UDMA
timeouts. I can provide dmesg later today if that is of any worth.



Regards,
Gabriel

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re[2]: SiI3112 SATA controller problems - status

[Gabriel Ambuehl]

Hi Soren Schmidt,
you wrote.

SS> It seems Will Andrews wrote:
>> On Tue, Sep 30, 2003 at 10:22:33PM +0200, Soren Schmidt wrote:
>> > No what I mean is that the Raptor is a PATA device fitted with a
>> > marvell PATA->SATA converter "on board", its not a "pure" SATA
>> > design, but just the old stuff they used to make with the marvell
>> > chip kludged on the back :)
>> > 
>> > The power connector is uninteresting in this context.
>> 
>> Interesting, since no one's made any PATA drives that spin at
>> 10,000 RPM as far as I know.  For some reason I thought the
>> interface change allowed for this (but couldn't come up with a
>> good reason why it would make a difference).  :)

SS> Hmm, PR? pricing? I guess its easier to make people shell out $$
SS> for a pretty expensive 36G drive if you add SATA to the mix of features :)

Actually, that drive is more like a SCSI drive with SATA connectors.
FWIW, it's still cheaper than a SCSI drive with the same specs and it
got 5 years warranty so I hope it is actually built better than the
desktop crap we see dying like the flies here (hint: massive airstream
over the disks helps a lot, cooler disks live much longer, so if you
can accept the noise, get some badass 12CM fan to cool them ;-).

Regards,
Gabriel

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: New SATA Hardware

[Gabriel Ambuehl]

Hi Steve Ames,
you wrote.

SA> G'day.

SA> My company is putting together a system with lots of file
SA> system on it to do disk based backup.

SA> Under 5.1-CURRENT what's the best supported (and performing
SA> optimally) SATA RAID controller (RAID 0, maybe 5)? What
SA> manufacturer/model of SATA disks do you recommend for that
SA> controller?

SA> This is our first forray into the world of SATA and we want
SA> to make it painless. I realize I've probably not supplied enough
SA> info for a solid answer but perhaps for a starting place?

3Ware Escalade 8XXX (I think 8K series is SATA, you'll easily figure
it out on their site) should be a safe bet from all I know. Also one of the
most expensive ones, though. But seeing that RAID5 can save you a lot
of money on big disk clusters, it might even end up being cheaper than
el cheapo RAID1 stuff.



Regards,
Gabriel

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

ATA broken as of yesterday?

[Gabriel Ambuehl]

A machine I had recompiled with a CVSUP as of yesterday (and again
today, to no avail) can't mount root from a HPT370 (/dev/ar0s1a)
RAID 1 array anymore, with the saved old kernel (two weeks or so I think)
it boots without any trouble.


Regards,
Gabriel

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re[2]: ATA broken as of yesterday?

[Gabriel Ambuehl]

Hi Bruno Van Den Bossche,
you wrote.

BVDB> On Thu, 9 Oct 2003 14:36:12 +0200
BVDB> Gabriel Ambuehl <[EMAIL PROTECTED]> wrote:

>> A machine I had recompiled with a CVSUP as of yesterday (and again
>> today, to no avail) can't mount root from a HPT370 (/dev/ar0s1a)
>> RAID 1 array anymore, with the saved old kernel (two weeks or so I
>> think) it boots without any trouble.

BVDB> I've got the same controller onboard and just cvsupped and rebuild world
BVDB> and kernel and everyting seems to be working fine.  I don't have my
BVDB> root-partition on it and it's configured for striping instead of RAID 1.

BVDB> atapci1:  port
BVDB> 0xcc00-0xccff,0xc800-0xc803,0xc400-0xc407,0xc000-0xc003,0xbc00-0xbc07
BVDB> irq 9 at device 14.0 on pci0


I think my machine didn't even show up atapci1 with the new kernel.
But since I'm not currently onsite, it's hard to verify this. I'll see
whether I can get another box with the controller together.
Regards,
Gabriel

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re[2]: Kernel maybe borked...

[Gabriel Ambuehl]

Hi John Hay,
you wrote.

JH> Return-Path: <[EMAIL PROTECTED]>
JH> Delivered-To: [EMAIL PROTECTED]
JH> Received: (qmail 61696 invoked from network); 18 Oct 2003 16:55:08 -
JH> Received: from mx2.freebsd.org (216.136.204.119)
JH>   by 0 with SMTP; 18 Oct 2003 16:55:08 -
JH> Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18])
JH> by mx2.freebsd.org (Postfix) with ESMTP
JH> id 1B77655508; Sat, 18 Oct 2003 09:54:51 -0700 (PDT)
JH> (envelope-from [EMAIL PROTECTED])
JH> Received: from hub.freebsd.org (localhost [127.0.0.1])
JH> by hub.freebsd.org (Postfix) with ESMTP
JH> id 914FE16A50B; Sat, 18 Oct 2003 09:54:48 -0700 (PDT)
JH> Delivered-To: [EMAIL PROTECTED]
JH> Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
JH> by hub.freebsd.org (Postfix) with ESMTP id 3910116A4BF
JH> for <[EMAIL PROTECTED]>; Sat, 18 Oct 2003 09:53:23 -0700 (PDT)
JH> Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za
JH> [146.64.24.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DCA943F93
JH> for <[EMAIL PROTECTED]>; Sat, 18 Oct 2003 09:53:20 -0700 (PDT)
JH> (envelope-from [EMAIL PROTECTED])
JH> Received: from zibbi.icomtek.csir.co.za (localhost [IPv6:::1])
JH> h9IGrHqs021649; Sat, 18 Oct 2003 18:53:17 +0200 (SAST)
JH> (envelope-from [EMAIL PROTECTED])
JH> Received: (from [EMAIL PROTECTED])
JH> by zibbi.icomtek.csir.co.za (8.12.9/8.12.9/Submit) id h9IGrEqA021648;
JH> Sat, 18 Oct 2003 18:53:14 +0200 (SAST)
JH> (envelope-from jhay)
JH> Date: Sat, 18 Oct 2003 18:53:13 +0200
JH> From: John Hay <[EMAIL PROTECTED]>
JH> To: Poul-Henning Kamp <[EMAIL PROTECTED]>
JH> Message-ID: <[EMAIL PROTECTED]>
JH> References: <[EMAIL PROTECTED]>
JH> Mime-Version: 1.0
JH> Content-Type: text/plain; charset=us-ascii
JH> Content-Disposition: inline
JH> In-Reply-To: <[EMAIL PROTECTED]>
JH> User-Agent: Mutt/1.4i
JH> Cc: [EMAIL PROTECTED]
JH> Subject: Re: Kernel maybe borked...
JH> X-BeenThere: [EMAIL PROTECTED]
JH> X-Mailman-Version: 2.1.1
JH> Precedence: list
JH> List-Id: Discussions about the use of FreeBSD-current
JH> 
JH> List-Unsubscribe:
JH> ,
JH>
JH> 
JH> List-Archive: 
JH> List-Post: 
JH> List-Help:
JH> 
JH> List-Subscribe:
JH> ,
JH>
JH> 
JH> Sender: [EMAIL PROTECTED]
JH> Errors-To: [EMAIL PROTECTED]

JH> On Sat, Oct 18, 2003 at 03:48:49PM +0200, Poul-Henning Kamp wrote:
>> 
>> I'm chasing a problem which indicates that I may have borked the
>> kernel with one of my last commits.  I'm hunting it right now.

JH> So you don't mean just compile errors like this, but real things like
JH> turning over the fish bowl when booting?

JH> 
JH> cc -O -pipe -march=pentium  -D_KERNEL -Wall -Wredundant-decls
JH> -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes
JH> -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions -std=c99
JH> -DKLD_MODULE -nostdinc -I-   -I. -I@ -I@/../include
JH> -finline-limit=15000 -fno-common -g -mno-align-long-strings
JH> -mpreferred-stack-boundary=2 -ffreestanding -Wall
JH> -Wredundant-decls -Wnested-externs -Wstrict-prototypes 
JH> -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual 
JH> -fformat-extensions -std=c99 -c
JH> /usr/src/sys/dev/raidframe/rf_freebsdkintf.c
JH> /usr/src/sys/dev/raidframe/rf_freebsdkintf.c: In function `rf_DispatchKernelIO':
JH> /usr/src/sys/dev/raidframe/rf_freebsdkintf.c:1547: error:
JH> structure has no member named `b_io'
JH> /usr/src/sys/dev/raidframe/rf_freebsdkintf.c:1547: error:
JH> structure has no member named `b_io'
JH> *** Error code 1

JH> Stop in /usr/src/sys/modules/raidframe.
JH> *** Error code 1

JH> Stop in /usr/src/sys/modules.
JH> ##

Now it's
#
cc -c -O -pipe -mcpu=pentiumpro -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  
-fformat-extensions -std=c99 -g -nostdinc -I-  -I. -I/usr/src/sys 
-I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter 
-I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -D_KERNEL 
-include opt_global.h -fno-common -finline-limit=15000 -fno-strict-aliasing  
-mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror  
/usr/src/sys/dev/ep/if_ep_eisa.c
/usr/src/sys/dev/ep/if_ep_eisa.c: In function `ep_eisa_attach':
/usr/src/sys/dev/ep/if_ep_eisa.c:218: error: `BASE' undeclared (first use in this 
function)
/usr/src/sys/dev/ep/if_ep_eisa.c:218: error: (Each undeclared identifier is reported 
only once
/usr/src/sys/dev/ep/if_ep_eisa.c:218: error: for each function it appears in.)
*** Error code 1

Stop in /usr/obj/usr/src/sys/GENE

ATAng: completely broken? Trouble with HPT370 on 4.9RC3

[Gabriel Ambuehl]

ATAng seems to cause nothing but trouble for me. It won't recognize
HPT370 arrays at all (whereas older 5.1 Kernels work perfectly) and
just goes on complaining it can't mount root from it. Promise RAID is
somewhat better (can mount root from it but goes on telling me one of
the subdisks is down when it clearly isn't) and finally it doesn't seem
to even recognize disks connected to a VIA VT8325 southbridge at all.
Silicon Image SATA seems to work at times (no RAID at all though) but
then starts throwing timeouts under make buildworld loads whereas CVSUP
works nicely as far as I can tell.

Further, 4.9RC3 also gives me headaches with HPT370 but seems to work ok with
Promise RAID, didn't try SATA or VT8325 so far. I'd definitely vote
for delaying 4.9 until some more people have beaten on the ATA drivers
in there (I don't have any Intel machines so I can't check those chipsets).

I'll try the same system with 4.8 later today and report if its the
hardware or the software (I'd guess the latter as older 5.1 builds
worked nicely).

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re[2]: ATAng: completely broken? Trouble with HPT370 on 4.9RC3

[Gabriel Ambuehl]

Hello Janet,

Sunday, October 26, 2003, 1:52:52 PM, you wrote:

> Gabriel Ambuehl wrote:

>> Further, 4.9RC3 also gives me headaches with HPT370 but seems to work ok with
>> Promise RAID, didn't try SATA or VT8325 so far. I'd definitely vote
>> for delaying 4.9 until some more people have beaten on the ATA drivers
>> in there (I don't have any Intel machines so I can't check those chipsets).

> What kind of problems are you seeing with 4.9RC?

Setup says there are no disks in the system!

> I am running a  rocketraid100 (HPT370) card fine on it in RAID1
> mode.  What kind of system are you running the HPT370 on?

Gigabyte VAXP KT400, Realtek LAN, Promise FT133 Lite (that one works
with 4.9 RC and RAID1), Sil 3*** SATA RAID,
Athlon XP 2400+
2x Seagate Barracuda 7200.8 80G ATA100 drives
Adaptac ATA1200A HPT370 PCI card
Not much luck on Asus KM400 chipset based board, either.





Best regards,
 Gabriel

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

microuptime went backwards

[Gabriel Ambuehl]

-BEGIN PGP SIGNED MESSAGE-

Hello,
I just installed 5 CURRENT (20.1. snapshot) on a K6-2 500 whic was
previously running 4.4 STABLE without any problems but since CURRENT
is running, it keeps printing error messages about microuptime went
backwards which doesn't seem to hurt the system itself but is very
annoying to work with as it jams the whole screen in a matter of
seconds with error messages, thus making it impossible to really work
with the system. Now in some mailinglist archive it was suggested to
turn of the APM of the board (some Elitegroup Super Socket 7 board
based on a SiS chipset, can dig out the specs if that helps) but
that didn't help at all...

Oh and please reply to me privately as well as I'm not reading this
list (too much traffic)!


Best regards,
 Gabriel

-BEGIN PGP SIGNATURE-
Version: PGP 6.5i

iQEVAwUBPFK9G8Za2WpymlDxAQFhlQgAtHfA5JbWxM9fZ/UFAq2zoLC6QLCBufXX
PmC4eisjnjGCyWmx2ukmRAZEjDa38b05tRON13Tax8U1kz1dUaFC4HLAhppUlkkO
ZsantX/MMJRAjYa6zS2Ez4lDsKr9GVmuLZxIdBGJ4Mfg+LmI+/owzQHn+m4EEeLe
TC31lNxf4Q8IJDkE4AAiuU/V3iQOPwmeia49jk6J5nqsw4ZZ0PKXEcUs53JkVDMy
jSSUBtm2lJCZnkMi27IdyzXkfwmDNJJDNj10U1qbwt/v1j6lcT8T2NW1rNJLPsQ9
3EKcTXx37RnYk8l7SJa6N69reMjgWlKi1q8f9q7ZGf6ALsqgyhmYGQ==
=bVJy
-END PGP SIGNATURE-


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

Can't build current...

[Gabriel Ambuehl]

-BEGIN PGP SIGNED MESSAGE-

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

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

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

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

Stop in /usr/src.


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




Best regards,
 Gabriel

-BEGIN PGP SIGNATURE-
Version: PGP 6.0.2i

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



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

Can't build current...

[Gabriel Ambuehl]

-BEGIN PGP SIGNED MESSAGE-

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

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

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

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

Stop in /usr/src.


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




Best regards,
 Gabriel

-BEGIN PGP SIGNATURE-
Version: PGP 6.0.2i

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



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

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

[Gabriel Ambuehl]

-BEGIN PGP SIGNED MESSAGE-

Hello Makoto,

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


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

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

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


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


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


Best regards,
 Gabriel

-BEGIN PGP SIGNATURE-
Version: PGP 6.0.2i

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



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

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

[Gabriel Ambuehl]

-BEGIN PGP SIGNED MESSAGE-

Hello Robert,

Tuesday, March 27, 2001, 8:19:42 PM, you wrote:

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

Actually, it doesn't even ask the user what to do with crypto if 5
CURRENT is selected (can't remember for sure what it did when one
selected 4 STABLE). So even if the user selects everything that is
presented to him, src-crypto and src-secure won't be in the cvsup file
and thus a normal attempt to build the system will break. Guess it is
time to formulate a PR on this...

Oh and while I'm on it: where is src/crypto/rijndael in the CVS?
CVSWEB doesn't find it, neither does it get downloaded (this time
using a complete supfile ;-)...

(although I managed to get the necessary files after searching with
google but obviously they are not on the FreeBSD site. Those seem to
be used only by the kernel as world will build without them.)


Best regards,
 Gabriel

-BEGIN PGP SIGNATURE-
Version: PGP 6.0.2i

iQEVAwUBOsIqW8Za2WpymlDxAQF9pwgAtVjLwwE561veqFCtW7MsZ/j/qBj5NDAx
UTaqNneKx4HRBrt5xfVS0LLwYyr3HubUzvnJy7rIa24h+/7YXwQQGzVphitF3meo
VaQYIB+hei6ZSCuywXpoVnYEikkMBuHRaM/BxtajTWBTeugsPQX+83L6/yVQfHSr
FF1ttkTcyCnLHQLTrz+zevtmBlRaZNyBJAMgKkDGAVqQQSFIF7mniJStlEnZsq9B
J1tBWHrBQjLG2Y7CkGn3WaDO5VBrCMn9fvQTQoBZUmTJ7+AGjkyWILyeMZ/iPL87
j7rcRpLyqgGlNva83pr2p3qQxeE662nbW9z/IdENdCqc4hyU8pzGzA==
=cAKe
-END PGP SIGNATURE-



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