I CVSup'd this morning around 05:00 BST, then make -DCLOBBER world /
mergemaster / sh MAKEDEV all / buildkernel / installkernel. My Adaptec
2940UW is no longer probed at boot time.
/boot/device.hints contains the proper entries and a pnpscan -v detects
a SCSI controller.
Attached are my current
In -CURRENT cvsupped as of today, the mixer no longer works. anything that
tries to access the mixer just says "Operation not permitted"
=
| Kenneth Culver | FreeBSD: The best NT upgrade|
| Unix Systems Administra
thomas r stromberg wrote:
>
>BTW, anyone ever notice that ftp.openbsd.org is (more then likely it
>just claims to be) SunOS 4.1?
No, it's a SPARC server they're given free use of. It is barely SunOS any
more, most of the userland has been "upgraded" to more current stuff.
Replies direc
Stephen Hocking wrote:
>
> I just updated my sources after a few days and reconfiged, recompiled & booted
> a machine with with a NCR810a card. It panicked partway through the boot
> messages (prior to mounting filesystems) saying that it couldn't allocate
> space for sym1's data. The previous ke
Can everyone please review the following code:
http://www.freebsd.org/~kris/openssh-2.2.0.tgz
which is my first pass at integrating the latest 0-day OpenSSH release.
OpenBSD have integrated some of our patches and subtly changed others, and
moved several chunks around, so I'd like some eyes-on
> > I posted code and results a while back to freebsd-arch which sampled the
> > sound card from userland and analysed the shannon entropy of the noise
> > (for the record, all but one card I tried gave about 6 bits of entropy or
> > more per 16 bit sample with no recording device plugged in, and
Looks like conf/files.i386 and conf/files.pc98 need to be updated.
-- Danny J. Zerkel
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
You could just as easily use a CRC function, which has the nice
property of having a collision rate of 2^l, where l is the length
of the CRC. CRCs are also pretty low-cost to compute relative to
other methods.
-scooter
At 09:47 PM 8/25/00 -0400, you wrote:
>[I see my post made it]
>
>To expand
> > Maybe. It's also not clear to me whether &my& current breakage is PCI related
> > or device.hints related (it appears that the read of my /boot/devices.hints
> > file gets things garbled):
>
> If you want a working vidconsole on the alpha, compile your hints statically
> into the kernel. :)
Matthew Jacob wrote:
>
> Maybe. It's also not clear to me whether &my& current breakage is PCI related
> or device.hints related (it appears that the read of my /boot/devices.hints
> file gets things garbled):
If you want a working vidconsole on the alpha, compile your hints statically
into the
Poul-Henning Kamp wrote:
>
> If I boot this machine on a -current kernel, it doesn't find the
> fxp#'s at all:
Do you have Peter's latest commits to pci/pci.c pci/pcisupport.c and
i386/isa/pcibus.c? Without that, mulitple PCI busses is b0rked on i386.
--
John Baldwin <[EMAIL PROTECTED]> -- h
> mcclock isn't at 112 on the alpha.
Oops (*blush*).. these are decimal...
>
> > >
> > > Maybe. It's also not clear to me whether &my& current breakage is PCI related
> > > or device.hints related (it appears that the read of my /boot/devices.hints
> > > file gets things garbled):
> >
> >
mcclock isn't at 112 on the alpha.
> >
> > Maybe. It's also not clear to me whether &my& current breakage is PCI related
> > or device.hints related (it appears that the read of my /boot/devices.hints
> > file gets things garbled):
>
> What makes you say that? This all looks fine to me. (The
>
> Maybe. It's also not clear to me whether &my& current breakage is PCI related
> or device.hints related (it appears that the read of my /boot/devices.hints
> file gets things garbled):
What makes you say that? This all looks fine to me. (The hang is not so
good though...)
> Hit [Enter] t
Maybe. It's also not clear to me whether &my& current breakage is PCI related
or device.hints related (it appears that the read of my /boot/devices.hints
file gets things garbled):
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [kernel]...
Entering k
If I boot this machine on a -current kernel, it doesn't find the
fxp#'s at all:
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD CC28 #0: Mon Aug 28 16:30:18 GMT 2000
[EMAIL PROTECTE
In message <[EMAIL PROTECTED]> Andrzej Bialecki
writes:
: On Fri, 1 Sep 2000, Warner Losh wrote:
:
: > In message <[EMAIL PROTECTED]> Stanislav Grozev writes:
: > : the card stopped working - the pccardd daemon correctly identifies
: > : it as a DFE-650 but fails to attach a driver to it.
: > :
> I posted code and results a while back to freebsd-arch which sampled the
> sound card from userland and analysed the shannon entropy of the noise
> (for the record, all but one card I tried gave about 6 bits of entropy or
> more per 16 bit sample with no recording device plugged in, and maximum
Hi, merging the code from ACPI For FreeBSD project into CURRENT finished!
We would very much appreciate for all people who encouraged and helped
and supported us.
1. Using ACPI
If you have machines with ACPI BIOS, you should be able to power off the
machine by shutdown -p (or acpiconf -s 5), or t
On Fri, 1 Sep 2000, Mark Murray wrote:
> > > PC's are pretty low-entropy devices; users who need lots of random
> > > bits (as opposed to a steady supply of random numbers) are arguably
> > > going to need to go to extraordinary lengths to get them; their
> > > own statistical analysis is almost
>From the keyboard of Justin Ovens [[EMAIL PROTECTED]]:
> What would cause freebsd -current to lock up when i telnet, ftp, or ssh to
> it? Somthing with inetd?
I had the same problem here for a day or two, i cvsuped a fresh tree
some hours ago, and made a fresh world which solved the problem.
In message <[EMAIL PROTECTED]> Stanislav Grozev writes:
: the card stopped working - the pccardd daemon correctly identifies
: it as a DFE-650 but fails to attach a driver to it.
: the 'ed' driver is in the kernel, the /boot/device.hints section for 'ed'
: is the default one.
Maybe that's the pro
On Fri, 1 Sep 2000, Justin Ovens [[EMAIL PROTECTED]] wrote:
> What would cause freebsd -current to lock up when i telnet, ftp, or ssh to
> it? Somthing with inetd?
>
chgsbsize breakage from a few days ago?
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Justin Ovens ([
N.M. it seems to be somthing with my kernel, i booted up off an older
kernel (4.1-STABLE) and i can telnet to it, so im going to try and make a
new config file and recompile my kernel..
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Justin Ovens ([EMAIL PROTECTED])
System/Net
Of course I should have done a "boot -v" (thanks neph!)
Doesn't work with tagged queueing:
ad0: ATA-4 disk at ata0-master
ad0: 17206MB (35239680 sectors), 34960 cyls, 16 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 0 depth queue, UDMA66
ad0: piomode=4 dmamode=2 udmamode=4 cblid=1
Works with tag
>
>I've put the latest patches for tagged queueing on ATA disks up
>for ftp on:
>
> ftp://freebsd.dk/pub/ATA/ATA-tagged-queueing-diff-0831.gz
On my testmachine:
atapci0: port 0xffa0-0xffaf at device 4.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
...
ad0: 17206MB
[EMAIL PROTECTED] wrote:
> I am interested in joining the mailing list for freebsdcurrent.
>
> This can be e-mailed to:
> [EMAIL PROTECTED]
> or
> [EMAIL PROTECTED]
Hi,
I'm a mail robot for this list. Unfortunately currently I'm on vacation, so
your request could not be fulfilled at this time.
What would cause freebsd -current to lock up when i telnet, ftp, or ssh to
it? Somthing with inetd?
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Justin Ovens ([EMAIL PROTECTED])
System/Network Administrator
http://www.lostworld.net
http://resume.lostworld.net -- Personal R
Date: Fri, 1 Sep 2000 03:06:28 -0700 (PDT)
From: Kris Kennaway <[EMAIL PROTECTED]>
I claim this to be untrue: my tests show an ordinary sound card (with no
recording source, at maximum input gain) will provide far more
(high-quality) entropy than Yarrow can make use of under even t
If memory serves me right, David Lebel wrote:
> I'm currently using the -STABLE branch of FreeBSD, and I'm wondering if there
> is a page somewhere that lists the feature set planned for 5.0 when it is
> released? How will it compare to the current 4.x branch ?
It's really hard to predict the f
Hello,
I'm currently using the -STABLE branch of FreeBSD, and I'm wondering if there
is a page somewhere that lists the feature set planned for 5.0 when it is
released? How will it compare to the current 4.x branch ?
Ciao,
...David
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "
On Thu, 31 Aug 2000 16:11:35 MST, Peter Wemm wrote:
> Modified files:
> sys/i386/isa pcibus.c
> sys/pci pcisupport.c
> Log:
> Take a shot at fixing multiple pci busses on i386.
Any chance that this is related to my new panic?
panic: pmap_enter: att
> > PC's are pretty low-entropy devices; users who need lots of random
> > bits (as opposed to a steady supply of random numbers) are arguably
> > going to need to go to extraordinary lengths to get them; their
> > own statistical analysis is almost certainly going to be required.
>
> I claim thi
Hi all,
i have a Fujitsu-Siemens Lifebook C Series notebook, which is equipped
with a D-Link DFE-650 NE-2000 Compatible PCCard Ethernet. on 4.1-RELEASE
it works like a charm - once you have an 'ed' driver in the kernel,
pccardd attaches it to the card and all is fine. Today I upgraded
the laptop
On Fri, 1 Sep 2000, Kris Kennaway wrote:
> On Fri, 1 Sep 2000, Sheldon Hearn wrote:
>
> > > > Has anyone else noticed that -CURRENT is a bit "jumpy"? I notice for
> > >
> > > It's probably the new /dev/random implementation. It's being worked on.
> >
> > What makes you say that? Are you seei
On Fri, 1 Sep 2000, Sheldon Hearn wrote:
> On Fri, 01 Sep 2000 03:07:33 MST, Kris Kennaway wrote:
>
> > On Fri, 1 Sep 2000, Paul Herman wrote:
> >
> > > Has anyone else noticed that -CURRENT is a bit "jumpy"? I notice for
> >
> > It's probably the new /dev/random implementation. It's being wo
On Fri, 01 Sep 2000 03:07:33 MST, Kris Kennaway wrote:
> On Fri, 1 Sep 2000, Paul Herman wrote:
>
> > Has anyone else noticed that -CURRENT is a bit "jumpy"? I notice for
>
> It's probably the new /dev/random implementation. It's being worked on.
What makes you say that? Are you seeing the
On Fri, 1 Sep 2000, Paul Herman wrote:
> Has anyone else noticed that -CURRENT is a bit "jumpy"? I notice for
It's probably the new /dev/random implementation. It's being worked on.
Kris
--
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <[EMAIL PROTECT
On Sat, 26 Aug 2000, Mark Murray wrote:
> My approach to this (and this is the first time I am stating this in
> such a wide forum) is to provide another device (say /dev/srandom) for
> folk who want to do their own randomness processing. This would provide
> a structure of data including the ent
On Thu, Aug 31, 2000 at 10:24:46PM -0700, George W. Dinolt wrote:
> If I read things correctly you relocated the svr4 pieces from sys to
> sys/compat in todays -CURRENT. It appears that the streams module
> depends on several include files which you moved. As a result, the
> streams module no long
Hi,
Has anyone else noticed that -CURRENT is a bit "jumpy"? I notice for
example when simply typing commands prompt that the process will
"stick" or "hang" only for about 100-200ms or so and then come back to
life. The system is otherwise idle (happens also in single-user.)
It's -CURRENT built
I've just committed a driver for the abovementioned RAID adapter families
provided by DPT/Adaptec and the long-suffering Mark Salyzyn. The driver
will be maintained by Adaptec, with a little help from yours truly if
really necessary.
With any luck, we should see the complete set of managemen
42 matches
Mail list logo
