On Tue, Nov 28, 2000 at 02:57:45PM -0700, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Kris Kennaway writes:
> : Please review. This syncs up our code with some NetBSD changes, as well
> : as attempting to sync rwall up with wall.
>
> You might also want to bruing i
wn ports down
the road, more power to ya! For doing something like embedded work or
a server this makes total
sense and I think it is a huge positive for FreeBSD, no reason to
trash that or break it in any way.
For the other 99.9% of society who want something "that j
EAD
https://pkg.trueos.org/iso/freebsd13-zol/
Please report issues on our GitHub tracker at:
https://github.com/zfsonfreebsd/ZoF
Thanks and happy testing!
--
Kris Moore
Vice President of Engineering
iXsystems, Inc
Ph: (408) 943-4100
Ph: (408) 943-4101
The Groundbreaking
se-docs/
Download Links
-
FreeBSD 12-STABLE:
https://pkg.trueos.org/iso/freebsd12-pkgbase/
FreeBSD 13-CURRENT:
https://pkg.trueos.org/iso/freebsd-pkgbase/
--
Kris Moore
Vice President of Engineering
iXsystems, Inc
Ph: (408) 943-4100
Ph: (408) 943-4101
The G
-* packages, for same reasons,
to keep image nice and small.
--
Kris Moore
Vice President of Engineering
iXsystems, Inc
Ph: (408) 943-4100
Ph: (408) 943-4101
The Groundbreaking TrueNAS M-Series -
Enterprise Storage & Servers Driven By Open Source
-Original Message-
From: Lev Serebryakov
Correct, this is ZFS only. And it's something we're using specific to FreeNAS /
TrueOS, which is why I didn't originally mention it as apart of our CFT.
For UFS, there will need to be additional care taken when doing updates.
--
Kris Moore
Vice President of Engineering
iX
e packages haven't pushed to the
mirrors yet, Jenkins is still chewing on a build of them here. I was using
the 12-stable packages yesterday which has these changes. They should be
synced up to the mirrors in the next 24-48 hours. Sorry about the confusion.
--
Kris Moore
Vice President of E
> -Original Message-
> From: Rodney W. Grimes
> Sent: Monday, April 29, 2019 10:41 AM
> To: Kris Moore
> Cc: Rodney W. Grimes ; Goran Mekić
> ; Emmanuel Vadot ; FreeBSD
> Stable ; FreeBSD Current curr...@freebsd.org>; freebsd-pkgb...@freebsd.org; freebsd-
>
> -Original Message-
> From: Matthias Apitz
> Sent: Monday, April 29, 2019 10:50 AM
> To: Emmanuel Vadot
> Cc: Kris Moore ; FreeBSD Stable sta...@freebsd.org>; freebsd-...@freebsd.org; freebsd-
> hack...@freebsd.org; FreeBSD Current ;
> freebsd-pkgb...
acker:
https://github.com/zfsonfreebsd/ZoF/issues
Thanks to everybody who's been helping us test so far!
--
Kris Moore
Vice President of Engineering
iXsystems, Inc
Ph: (408) 943-4100
Ph: (408) 943-4101
The Groundbreaking TrueNAS M-Series -
Enterprise Storage & Servers Driven
entium -fpcc-struct-return -ffast-math -fno-strength-reduce
> ...
You don't have CXXFLAGS set in your environment, do you? That will break
several of the things under gnu/
Kris
-
"Never criticize anybody until you have walked a mile in their shoes,
because by that time you will be
n that lags significantly behind -current or -stable, you
>will require a ports upgrade kit from http://www.freebsd.org/ports
Does someone plan to add this question and the other one about the dangers
of -current to the FAQ? I think they are both well-answered.
Kris
-
"Never criti
On Mon, 19 Jul 1999, Nik Clayton wrote:
> docs/7791 is of the opinion that ipf(1) should be moved to ipf(8), to
> (among other things) be consistent with ipfw(8).
>
> Anyone care to comment one way or the other?
Definitely.
Kris
To Unsubscribe: send mail to [EMAIL PRO
empting to paste the contents of a large
buffer from xemacs (v21.1 from ports) into the pico editor from pine4.
Any ideas before I recompile kvt with -g and try and track down what it's
doing?
Kris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
;ed the pine
process, at which point it changed to what it is now.
Kris
> Kevin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
pawned
> > from the KDE panel. The second one was running a copy of pine and was in
> > the same state as the other initially, until I kill -KILL'ed the pine
> > process, at which point it changed to what it is now.
> >
> > Kris
>
> Well, since the CPU tim
?? ()
#11 0x805dca2 in ?? ()
#12 0x804f020 in ?? ()
(this is from process 92724 which is still running).
I might try and compile kvt with debugging support and see what it's
doing; I think I can repeat the problem at will.
Kris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sun, 25 Jul 1999, Amancio Hasty wrote:
> while you are at it try to compile a kernel with symbols ...
I already have (this is my standard practice). What should I do with it
here?
Kris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in th
ces are
they have been answered (many times) before.
Thanks and good luck!
Kris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ich I'm not sure that you are,
yet.
It's not (just) about the danger to your own system, it's the hand-holding
load on the developers when a FreeBSD neophyte thinks he's ready to run
the developer's version :-(
Kris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
/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
[SNIP]
I saw these too when I was building with a fresh tree checked out from
internat. Mark? :)
Kris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Mon, 3 Jan 2000, Andrew Sherrod wrote:
> Do you know which version is shipping with FreeBSD 3.4?
http://www.freebsd.org/ports/mail.html
says elm-2.4ME+61
Kris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
/src/usr.bin/ )
We seem to have re-reverted to "make world before make kernel" :-/
Kris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ce that ad1
and ad2 are only detected as WDMA2, when it seems (from the udma=2) that
they can handle UDMA - is this a cabling issue or something (I'm not
familiar with IDE cabling requirements)?
Kris
Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
e that's the
reason?
Kris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
no real
advantage to using SHA1 passwords anyway, since they're an algorithmically
identical format to the default MD5 system, and there's nothing inherently
insecure about that one.
If anyone has been using SHA1 passwords, now's the time to regenerate them
:-)
Kris
To Unsubscribe:
aking use of the feature will have to update their passwords
back to MD5 before they reinstall the library.
Kris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Fri, 7 Jan 2000, Etienne De Bruin wrote:
> When compiling 3.4-RELEASE I find that whilst linking in src/bin/csh,
> the linker complains about not finding the following symbols:
And this has exactly what to do with FreeBSD 4.0-CURRENT?
Kris
To Unsubscribe: send mail to [EMAIL PRO
nal. If you need a fully functional IPv6 today, stick
with FreeBSD 3.4 + KAME.
Kris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sun, 9 Jan 2000, Leif Neland wrote:
> Kernel build stops with "Don't know how to make sha1.c".
> sha was removed a few days ago, a "heads up" said.
Different instance - that was just SHA1-format passwords.
Kris
To Unsubscribe: send mail to [EMAIL PROTE
llowed that one to build.
Kris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
In addition to my lost contact problems with the ATA driver and one of my
WDC drives, my CDROM no longer works properly under the new
drivers. Accessing the drive causes excessive pauses and seems to chew
lots of CPU in the kernel: the system becomes very sluggish with about 4
or 5 seconds to resp
ne of these is not up to date, or is out of sync. I had this
problem yesterday when my modules were out of date. Please double-check to
make sure..
Kris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
use cvs -R to do it read-only..
Kris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
mine unwedges after about 1 1/2 - 2 minutes (it just seems to
be spinning hard in the kernel).
Kris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sat, 15 Jan 2000, Kris Kennaway wrote:
> Support RSA via RSAref. This autodetects the RSAref package, and if it
> is not found, compiles without RSA.
Openssl should now be fully functional for both US and international users
- please report any problems you have in using it to m
Bruce tells me there were good reasons why patch won't be upgraded
("downgraded") from 2.1 to 2.5 - it was already tried once and reverted.
Should we blow away /usr/src/contrib/patch if it's never going to be used?
Kris
"How many roads must a man walk down?"
&
rely sure this is the best way to go about things (it's a
messy area) - any suggestions are welcome.
Kris
[*] I should make the matching more flexible.
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
&
h this -
I'm not sure exactly what the best way to do it is. For example, ports
like w3m-ssl pass the location of the openssl include directory, which
needs to be either /usr/include or ${LOCALBASE}/include. Perhaps the best
thing would be to bump OSVERSION (belatedly).
Kris
"How many
.
I figured this out late last night (I couldn't reproduce it for a long
time because my test boxes didn't have the openssl port installed) - I'm
looking at how to fix it.
Kris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
you using openssl-rsaref, or openssl with no RSA (the
latter will break many ports, the former has a restrictive license).
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!&qu
Unless anyone objects I'm going to bump OSVERSION tonight to provide a
cutoff for whether or not openssl is available in the base system. Ports
need to behave differently in either case..
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!&quo
t there may
be a better one. Anyone?
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Homer Simpson
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Mon, 17 Jan 2000, David O'Brien wrote:
> Due to the concequence involved, you really do need to check for 'NO',
> 'YES', and "other". Rather than combining 'YES' and "other".
You're suggesting not building openssl at all if t
On Mon, 17 Jan 2000, John Polstra wrote:
> You mean "__FreeBSD_version" (in src/sys/sys/param.h), right?
Right, sorry. OSVERSION is what bsd.port.mk calls it.
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That
could you :-)
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Homer Simpson
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
The simplest way to test whether OpenSSL can do RSA is to write a file at
install-time, like the following patch. Any objections?
Kris
Index: Makefile
===
RCS file: /home/ncvs/src/secure/lib/libcrypto/Makefile,v
retrieving revision
On Mon, 17 Jan 2000, Kris Kennaway wrote:
> + rm -f /etc/ssl/openssl_hasrsa
Doh, I meant /bin/rm
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Ho
On Tue, 18 Jan 2000, jack wrote:
> On Jan 17 Kris Kennaway wrote:
>
> > > + rm -f /etc/ssl/openssl_hasrsa
> >
> > Doh, I meant /bin/rm
>
> No, you meant ${RM}
I couldn't find this defined in /usr/share/mk/* - it's only in
bsd.port.mk, AFAICT.
Kris
gt; bsd.port.mk ... but I'm *sure* it's in there, it has been for ages!
Reread the above. I know it's in bsd.port.mk, but that doesn't help me
when I'm building in /usr/src/secure/lib/libcrypto ;-)
Kris
"How many roads must a man walk down, before you call him
On Tue, 18 Jan 2000, Sheldon Hearn wrote:
> On Mon, 17 Jan 2000 21:53:10 PST, Kris Kennaway wrote:
>
> > +.if defined(WITH_RSA) && ${WITH_RSA} == YES
> > + /usr/bin/touch /etc/ssl/openssl_hasrsa
>
> Um, are you sure you want that hard path, /etc/ssl ? Shou
On Tue, 18 Jan 2000, Sheldon Hearn wrote:
> Does sysinstall set this one? If not, it should. Then we can stop
> worrying about it. :-)
Not yet, but it should. If someone can help me out here it would be
greatly appreciated.
Kris
"How many roads must a man walk down, before y
f making an openssl-using port (at least, that's how many times
my debugging echos get run :)
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Homer Simpson
else we can
surely change them to suit, but I'd rather not complicate things even more
than they are already without a reason..
> The other thing that could be set based on the CRYPTO_COUNTRY code is where
> to get the FreeBSD crypto related source from.
Well, right now there is only
On Tue, 18 Jan 2000, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Satoshi - Ports Wraith - Asami
>writes:
> : Won't people get into legal trouble (technically) if they build the
> : wrong version?
>
> RESIDENT=
> CITIZEN=
What about us dual citizens?
idea I've wanted to
implement for a while, although I was thinking of doing it dynamically by
testing the available bandwidth to each of the hosts (and storing it in a
database) and using them in order of increasing bandwidth.
Kris
"How many roads must a man walk down, before you c
speed.o(.text+0x60a): undefined reference to `RSA_PKCS1_RSAref'
> /usr/local/lib/libcrypto.so: undefined reference to
> `ERR_load_RSAREF_strings'
it's a known problem which I hope to fix tonight - pkg_delete or move
aside your openssl installation (e.g. /usr/local/lib/lib{crypto,ssl}
O_RSA was unset.
I have no problem with this, but it means either we have to have people
who have an RSA license get their crypto from internat, or freefall has to
have the RSA code (possbibly in another cvsup collection).
Kris
"How many roads must a man walk down, before you call him a
at people who want RSA and have a license
would have to get their crypto from internat, or from freefall with a
special cvsup collection :-)
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
&q
a make world of both possible cases, but ppkg_delete or move aside
the openssl libraries in /usr/local/lib for now.
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!&
ailing lists so
I don't have to explain this n times. A fix is coming, but I have to test
it on 4 different cases, and the buildworlds take time.
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!
stale libcrypto.so in
/usr/local/lib due to the -L path.
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Homer Simpson
To Unsubscribe: send mail to [EMAIL PROTEC
oked at afterwards. The problem is the extra complexity it
adds..
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Homer Simpson
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Fri, 21 Jan 2000, Brian Hechinger wrote:
> rebooted, tried to log in and couldn't. not as root, not as my regular user.
Sounds like you clobbered your DES libcrypt libraries with non-DES ones,
and now you can't use your DES passwords.
Kris
"How many roads must a man
from security/mcrypt. Do
you have an old version of this installed which the configure script might
be locating?
BTW, please don't reply to an unrelated message when starting a new
topic. It screws up the message threading for people who use a MUA which
can do that.
Kris
"How m
0, end = 12594959, size 4207140 : OK
ad2s1: type 0xa5, start 63, end = 4193909, size 4193847 : OK
ad2s2: type 0xa5, start 4193910, end = 8387819, size 4193910 : OK
ad2s3: type 0xa5, start 8387820, end = 12594959, size 4207140 : OK
Kris
"How many roads must a man walk down, before you cal
nd options IPFILTER_LOG in the kernel
(because the kld wouldn't load for me). What am I doing wrong?
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Homer S
ryone's problems.
I think we should consider defaulting back to the wd drivers unless soren
can work miracles in the meantime, rather than risking a large subset of
the user base finding 4.0 doesn't work right on their machines :-(
Kris
"How many roads must a man walk down, b
On Mon, 24 Jan 2000, Soren Schmidt wrote:
> Huh, you have only told me about the missing CDROM (should be fixed
> with the commit I just did), what else seems to be a problem ??
My WDC drive falling back to PIO mode..see the dmesg in the previous
message.
Kris
"How many roads
Can people please review this for style and content, for inclusion in
the FAQ? I'll also need someone to mark it up once it's ready since SGML
is currently not among my abilities :-)
Thanks,
Kris
As of FreeBSD 4.0, the OpenSSL toolkit is a part of the base
system. Ope
n standards :-)
> I can't speak to the veracity of the content, but I can mark it up for
> the Handbook as necessary.
Thanks! :)
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"O
udp from any to any port = 31337 keep state
# Allow loopback
pass out quick on lo0
pass in quick on lo0
Note that I haven't been able to test this ruleset for legitimacy yet
because I can't interface with ipfstat :-)
Kris
"How many roads must a man walk down, before you
; src-share
> src-sys
src-tools
> src-usrbin
> src-usrsbin
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Homer Simpson
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
/home/kris/tmp/world/obj/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/alpha/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/gnu/usr.bin/cc/cpp/../cc_int/libcc_int.a(choose-temp.o):
In function `choose_temp_base':
choose-temp.c(.text+0x218): warning: mktemp() possibly used
uns
On Wed, 19 Jan 2000, Kris Kennaway wrote:
> Modified files:
> secure/usr.bin/openssl Makefile
> Log:
> Don't search for libraries in ${LOCALBASE}. This should fix the problems
> people were seeing with conflicts with the openssl port.
I tried to test all of the
I get this whenever I try and build a kernel (with or without IPFIREWALL):
linking kernel.debug
ip6_fw.o: In function `ip6_fw_init':
/sys/compile/MORDEN/../../netinet6/ip6_fw.c(.text+0x18a4): undefined reference to
`ip6_fw_chk_ptr'
/sys/compile/MORDEN/../../netinet6/ip6_fw.c(.text+0x18ae): undef
don't use a configure script. This has
only been necessary so far for pipsecd and seems to fix the problem there.
New patched ports (see http://www.freebsd.org/~kris/openssl):
w3m-ssl
pipsecd (updated)
Kris
Index: Mk/bsd.port.mk
=
Ack, this was meant for ports, although the additional testing would
certainly be welcome :) Sorry..
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Homer Simpso
onf/files to
>
> netinet6/ip6_fw.c optional ipv6firewall
>
> I believe this is the correct fix in any case.
Thanks, this fixes it, but I have INET6 anyway..
Kris
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
This commit causes my P5 to panic at boot:
kato2000/01/28 23:49:03 PST
Modified files:
sys/i386/i386identcpu.c
Log:
Simplify messages of Pentium II, Pentium II Xeon, Celeron, Pentium III
and Pentium III Xeon CPUs. If a CPU is one of Pentium II, Pentium II
Xeon and
anged).
If anything has changed in the verbose boot I can provide a copy of it,
otherwise all my relevant details are in the archives from previous
messages..
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetoric
Send me one, there are a few changed items, I'll see what can be done...
Will do tomorrow..
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Homer Simpson
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ng else) I can boot fine :-)
> - Please report the panic message you got.
I'll have to write this down by hand - it didn't look very interesting,
though.
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question
oted fine this
time, so it looks like you can ignore my previous report. My best guess is
that something in my kernel was out of sync with itself (I built multiple
times to try and get the ipfw6 error to go away, perhaps it didn't
recompile an object file when it should have).
Sorry for the
looks to be the case - thanks, Guido!
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Homer Simpson
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
multiuser mode at all
otherwise.
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Homer Simpson
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Tue, 1 Feb 1900, I am not any sort of Fluffy wrote:
Please fix your mailer. It is over 100 years old.
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Homer
On Wed, 2 Feb 2000, Maxim Sobolev wrote:
> What happed with much-advertised by Polstra cvsup8.freebsd.org cvsup mirror?
He advertised shortly thereafter that it had died :-)
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"Th
you should use for new passwords, but I
won't be able to get that committed until after 4.0.
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Homer Simpson
version
> I get the following:
Jim Bloom and I are in the process of preparing patches for all of the
openssl-using ports. See http://www.freebsd.org/~kris/openssl for some of
them, although I haven't added the latest ones Jim has sent me. I don't
think the apache13-php3 has been f
On Sat, 5 Feb 2000, Klaus Herrmann wrote:
> options ATA_ENABLE_ATAPI_DMA#Enable DMA on ATAPI devices
Try removing this. According to the warning in LINT, this breaks many
CDROMs.
Kris
"How many roads must a man walk down, before you call him a man?"
"E
able, because I haven't had the time to build
them, but I'll either be doing this tonight or over the weekend. You'll
have to rebuild from source as it explains there.
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"T
> The des distribution (des/des.??) of the 4.0 release candidate
> does not includes RSA headers nor RSA binaries, because they
> were built as USA_RESIDENT=YES.
Are you referring to the crypto distribution? Mark Murray
([EMAIL PROTECTED]) is the person you need to talk to about non-US cr
h
>
> Or is there something that I miss?
That looks right. I think the original person was getting their crypto
from the wrong place.
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..the
the handbook for an explanation of the openssl
situation. That's all thats really changed lately.
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Home
allow it to build
properly on all versions of FreeBSD. Since the ports freeze is on monday,
I'll commit it myself if I dont hear back from him before then.
> The real fix would be to really put openssl into the base system.
Thanks, alread
7;s just the nature of the new gcc. In the end,
> it will be worth it.
# gcc -v
Using builtin specs.
gcc version 2.95.2 19991024 (release)
# which gcc
/usr/bin/gcc
-current has been using 2.95.2 for some time, and yes, it caused new
compile errors that were not seen before (especially in ports) :
y default,
actually, but if you add OpenSSL-rsaref and then remove it you'll have to
add this one back again).
These will shortly be moving somewhere on ftp.freebsd.org (Hi jkh :) but
in the meantime you can get them from http://www.freebsd.org/~kris/openssl
Hopefully international versions of the p
d the rest of this
monster thread yet, but the portcheckout port does exactly this.
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetorical question!"
"Oh..then, seven!" -- Homer Simpson
To Unsubscribe
hat means "let the bug reports
begin"! Please check that your bug hasn't already been reported before
mailing, though, eh? Making Mark pass out again in fright due to 3000 new
messages in -current when he wakes up won't help anyone, least of all him
:-)
Kris
"How many
1 - 100 of 1614 matches
Mail list logo
