-current of June 01:
For me it was in stage 4 at:
ln -sf libm.so.2 /usr/obj/usr/src/i386/usr/lib/libm.so
cd /usr/src/lib/libncurses; make depend; make all; make install
./make_keys /usr/src/lib/libncurses/../../contrib/ncurses/ncurses/tinfo/keys.lis
t > init_keytry.h
sh /usr/src/lib/libncurses
I've just discovered (and fixed) a serious data corruption bug in
Vinum. Under certain circumstances, serious data corruption can
result:
1. You are using RAID-4 or RAID-5 plexes.
2. One of these plexes (not the first plex in the system, whether a
RAID-[45] plex or not) develops parity pro
In message <[EMAIL PROTECTED]> Michael Lucas writes:
: Short answer: Warner Losh & others are beavering away on it.
I'm meeting in Japan next week with many of the nomads and other
communities there working in this area... If you can make it to
tokyo or osaka, then you might want to attend...
W
In message <[EMAIL PROTECTED]> Sleepless in Brisbane
writes:
: Is there cardbus support under FreeBSD-Current and if so what can it currently
: support? If there is not cardbus support then are there any other users
: interested in working on it?
No. Yes. Wanna join us?
Warner
To Unsubscri
Cardbus is a work-in-progress.
Check the archives of freebsd-mobile for the gory details.
Short answer: Warner Losh & others are beavering away on it.
> I have seen so far a few people ask this question and all they have been told
> is to look at the supported hardware section on the handbook a
Christian Weisgerber <[EMAIL PROTECTED]> wrote:
> The following, completely innocuous command line
> $ fetch -o - http://sites.inka.de/mips/unix/freebsd/xterm.shar | sh
> executed as a non-priviledged user, reproducibly panics the machine.
It's caused by fdesc mounted on /dev/fd.
I sent in a PR,
> > - There's one interface involved here
>
> Correct.
>
> > - It has a 21143 chip
>
> Well, the de driver says 21142. The dc driver says 21143.
It's just a difference in chip revision, really.
> This one does not have AUI so that is not going to be a problem. What I do
> wonder, though, is
I have seen so far a few people ask this question and all they have been told
is to look at the supported hardware section on the handbook at the freebsd
home website (which is useless as there is nothing listed under PCMCIA on the
site at the moment). Perhaps then someone working with PCMCIA co
On Thu, Jun 01, 2000 at 12:51:25PM -0700, Bill Paul wrote:
> > Hi Bill,
> >
> > I applied your patches to -current without incidents.
> >
> > I have a testbox (Digital dual P6) that gives:
> >
> > May 31 10:56:38 p6 /kernel: dc0: port
> [...]
> > May 31 11:03:27 p6 /kernel: dc0: watchdog tim
> Hi Bill,
>
> I applied your patches to -current without incidents.
>
> I have a testbox (Digital dual P6) that gives:
>
> May 31 10:56:38 p6 /kernel: dc0: port
[...]
> May 31 11:03:27 p6 /kernel: dc0: watchdog timeout
>
> This box can also house an Alpha Miata MX5 mainboard, the Intel & A
> On Tue, 30 May 2000 12:30:41 -0700 (PDT)
> Kris Kennaway <[EMAIL PROTECTED]> said:
kris> On Tue, 30 May 2000, Alexander Leidinger wrote:
> > I've just committed the version from ports to the source tree - could you
> > verify it works?
>
> I have to wait until internat catches up, but
On Wed, May 31, 2000 at 12:30:51PM +0200, Wilko Bulte wrote:
> On Tue, May 30, 2000 at 09:29:46AM -0700, Bill Paul wrote:
> > > On Tue, May 30, 2000 at 12:28:25AM -0700, Bill Paul wrote:
> > > > Several people have reported problems with if_dc botching autonegotiation
> > > > on 21143 NICs with no
12 matches
Mail list logo
