You are probably using a -CURRENT with a broken randomness
device. For more information you can try and search the
mailing list archives.
No - he has _no_ randomness device.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
My current box (make world'ed this morning) fails on fetch(1) for some
CGI scripts.
% fetch -v -v http://www.FreeBSD.org/cgi/search.cgi/
looking up www.FreeBSD.org
connecting to www.FreeBSD.org:80
requesting http://www.FreeBSD.org:80/cgi/search.cgi/
looking up www.FreeBSD.org
connecting to
Jun Kuriyama [EMAIL PROTECTED] writes:
My current box (make world'ed this morning) fails on fetch(1) for some
CGI scripts.
The bug is only in the status report, check the acutal size of
fetch.out. I fixed this in a commit half an hour ago.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To
Cyrille Lefevre wrote:
Non-centralized configuration is frowned upon. Having to find which file
has something, or having to read through multiple files to understand
how the system is configured is a disadvantage wrt to the present
system.
not so difficult if a command do that for
I haven't looked into it too deeply yet because of other source tree
problems, but if you used to get your crypto ,v files from internat,
you will suffer some funny problems unless you nuke the old checked-out
files.
My apologies if this is old news, but I see nothing in UPDATING.
The
I'd like to disclaim all responsibility :-I
I'd normally try to figure out what the problem is or ask for more
info, but seen as ppp caused a kernel panic on me this morning on the
train, and since then cvsup has caused a similar panic, htc panics
and just about anything else interesting I do
Udo Erdelhoff schrieb:
Hi,
ppp -auto stopped working fater I've updated my box from 06/17-Sources
to yesterday's version (07/06, approx. 1500 GMT). tcpdump -ni tun0
shows the traffic but that's it. ppp.log doesn't show any obvious
problems. -ddial works, sending a manual dial
My apologies if this is old news, but I see nothing in UPDATING.
I sent it to ctm-announce...
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
suggestion
/dev/random now has good entropy collection (from the keyboard and
sysmouse drivers). Please ensure that either `options RANDOMDEV' is
present in your kernel config file or that `randomdev_load="YES"'
is in your /boot/loader.conf. If you do not have the /dev/random
driver,
What optimizations did you use when compiling your kernel?
(COPTFLAGS)
If it's anything more than -O -pipe, then that may very well
be your problem.
-Dan
On Tue, Jul 11, 2000 at 09:28:44PM -0400, Patrick Gardella wrote:
I've somehow been burned by the config changes when I build world
Hi,
We, PAO folks in Japan, have prepared the patch for
etc/defaults/pccard.conf CURRENT (rev. 1.121) merging more that one
hundred of PCCard entries from PAO3. We'd be happy if we could use
various cards on the installation.
http://people.freebsd.org/~iwasaki/pccard/pccard.conf-MFPAO
We'd
John Galt wrote:
On Wed, 12 Jul 2000, Mark Murray wrote:
You are probably using a -CURRENT with a broken randomness
device. For more information you can try and search the
mailing list archives.
No - he has _no_ randomness device.
Isn't there an add-on daemon for that, ESD or
On Wed, Jul 12, 2000 at 02:50:45PM +0100, Brian Somers wrote:
I'd like to disclaim all responsibility :-I
I'm almost convinced you're innocent. I've managed to restabilize my system
by replacing "set device PPPoE:ed1" with "set device /dev/cuaa2". I've been
pumping data through ppp for about 10
I'm afraid I don't quite understand how that desribes the fix to my
problem (Freezing on boot after having probed a non-existant vga1 and
sc1). What I did do, I went into sys/dev/fb/vga.c and commented out
the second vga head detection. Works beautifully now, though it
would be better to
In message [EMAIL PROTECTED] Mitsuru IWASAKI writes:
: Xircom CompactCard Ethernet 10 (CFE-10)
The entry for this that I just committed works great for me :-)
: - We are sure that some kind of cards wouldn't be supported and marked as
:# XXX NOT SUPPORTED YET
:and disabled because of
Isn't there an add-on daemon for that, ESD or somesuch? The OpenSSL docs
mention it.
On Wed, 12 Jul 2000, Mark Murray wrote:
You are probably using a -CURRENT with a broken randomness
device. For more information you can try and search the
mailing list archives.
No - he has _no_
In article [EMAIL PROTECTED],
Brian Somers [EMAIL PROTECTED] wrote:
I haven't looked into it too deeply yet because of other source tree
problems, but if you used to get your crypto ,v files from internat,
you will suffer some funny problems unless you nuke the old checked-out
files.
Using a freshly supped -current source tree (2 hours ago) I'm getting a panic on
boot:
trap entry = 0x4 (unaligned access fault)
a0 = 0xfc590a33
a1 = 0x2c
a2 = 0x2
pc = 0xfc3a970c
ra = 0xfc3a96b8
curproc = 0
This is
After cvsupping around 1:00 GMT and making world, I got this when doing
cvsup again:
Parsing supfile "/root/standard-supfile"
Connecting to cvsup.dk.FreeBSD.org
***
idThread.T closure rootA* waiting for
2
19 matches
Mail list logo