Hi.
I updated 'snc' driver for -current.
This driver is only for NEC pc98 machines.
http://triaez.kaisei.org/~mzaki/sonic/
This is very stable for usual operation.
I hope this will be merged into the tree.
--
Motomichi Matsuzaki <[EMAIL PROTECTED]>
Dept. of Biological Sciences, Grad. Sch
On Sat, Sep 23, 2000 at 09:44:21PM -0400, Garrett Wollman wrote:
> < said:
>
> > Is their any harm in just keeping the -P flag as a no-op and optionally
> > remove it at some later time (for backward compatibility)?
>
> We should try to be consistent with POSIX.1-200x as much as possible.
What
On Sun, Sep 24, 2000 at 00:04:38 +0200, German Tischler wrote:
[ problems with SMP, but not UP kernels, I don't know anything about that ]
> Is anyone else seeing this ?
>
> Another strange thing is that cdrecord -scanbus tells me
>
> scsibus0:
> 0,0,0 0) *
> 0,1,0 1) *
< said:
> Is their any harm in just keeping the -P flag as a no-op and optionally
> remove it at some later time (for backward compatibility)?
We should try to be consistent with POSIX.1-200x as much as possible.
-GAWollman
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fre
On 24-Sep-00 Justin Thomas wrote:
> I am trying to compile (make buildworld) the latest CURRENT version of
> FreeBSD (5). I keep getting an error when it trys to build "libdisk"
> about something being redefined or something. This is quite a ways into
> the build process. Is anyone familiar wi
Attached is the end of the .out file where my error occurs. Thanks for
any help.
~Justin
===> libdevstat
cc -O -pipe -I/usr/src/lib/libdevstat -I/usr/src/lib/libdevstat/../../sys
-I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libdevstat/devstat.c -o devstat.o
building standard devstat l
I am trying to compile (make buildworld) the latest CURRENT version of
FreeBSD (5). I keep getting an error when it trys to build "libdisk"
about something being redefined or something. This is quite a ways into
the build process. Is anyone familiar with this error?
Thanks,
Justin
To Unsub
In message <[EMAIL PROTECTED]> Marcel Moolenaar writes:
: Is their any harm in just keeping the -P flag as a no-op and optionally
: remove it at some later time (for backward compatibility)?
-P is non-standard, was introduced only in July and therefore we don't
need to keep it around for any rea
"Andrey A. Chernov" wrote:
>
> --- usr.sbin/mtree/mtree.c.orig Thu Jul 27 07:36:02 2000
> +++ usr.sbin/mtree/mtree.c Fri Sep 15 04:00:46 2000
[snip]
> @@ -115,10 +119,6 @@
> case 'q':
> qflag = 1;
> break;
> - case
David Siebörger wrote:
> I've experienced the (apparently common) problem of switching from X
> to console and back to X and getting an unresponsive mouse pointer in
> X. This occurs when I use protocol "Auto", or don't specify a
> protocol.
Someone was kind enough to send me the attach
Hi.
On my machine the ahc (aic) driver times out while probing for devices
on SMP, while it is working on UP.
dmesg says
ahc0: port 0xd000-0xd0ff mem 0xe100
-0xe1000fff irq 15 at device 6.0 on pci0
aic7890/91: Wide Channel A, SCSI Id=7, 32/255 SCBs
while booting the SMP kernel it says
(p
[EMAIL PROTECTED] (Christian Weisgerber) wrote:
>
> Doug Barton <[EMAIL PROTECTED]> wrote:
>
>> Previously I had X + moused working just fine, so I had the best
>> of both worlds. With X 4.0.1 if I use moused I get no response from the
>> mouse in X at all.
>
> Make sure you use
>
>
On Fri, Sep 22, 2000 at 23:43 +0200, Leif Neland wrote:
>
> On Sat, 12 Aug 2000, Brian Somers wrote:
>
> > > Is ppp.linkdown executed before or after the link is down?
> > >
> > > I'd like to change a dyndns, but will link activity done in
> > > linkdown defeat the timeout, or start a new call?
Doug Barton <[EMAIL PROTECTED]> wrote:
> Previously I had X + moused working just fine, so I had the best
> of both worlds. With X 4.0.1 if I use moused I get no response from the
> mouse in X at all.
Make sure you use
Option "Protocol" "MouseSystems"
Protocol "Auto" is not
On Sat, 23 Sep 2000, Mark Huizer wrote:
> I thought I had read the interesting stuff on ssh recently in -current,
> but I can't get ssh to work again on the machine I switched to
> yesterday's current :-(
device random in your kernel.
Kris
--
In God we Trust -- all others must submit an X.509
Hello!
On Sat, Sep 23, 2000 at 02:01:21PM +0200, Mark Huizer wrote:
> tiggr 1:31pm [~/.ssh] ssh eeyore
> ssh: no RSA support in libssl and libcrypto. See ssl(8).
> Disabling protocol version 1
> DH_generate_key
>
> That's with USA_RESIDENT=NO, and with rsaref port installed.
?? Can you give m
Hmm...
I thought I had read the interesting stuff on ssh recently in -current,
but I can't get ssh to work again on the machine I switched to
yesterday's current :-(
tiggr 1:31pm [~/.ssh] ssh eeyore
ssh: no RSA support in libssl and libcrypto. See ssl(8).
Disabling protocol version 1
DH_generat
It seems Donn Miller wrote:
> In article <[EMAIL PROTECTED]> you wrote:
>
>
> > I am also seeing the fdc0 problem "fdc0: cannot reserve I/O port range".
>
> What's up with the fdc driver? I'm seeing the exact same thing. There was
> never any heads-up about this. Surely, the person who broke
In article <[EMAIL PROTECTED]> you wrote:
> I am also seeing the fdc0 problem "fdc0: cannot reserve I/O port range".
What's up with the fdc driver? I'm seeing the exact same thing. There was
never any heads-up about this. Surely, the person who broke it knows about
it. :-( It's nice to have
On Fri, 22 Sep 2000, Kenneth Wayne Culver wrote:
...
> Alright, I think I may just do that too... I was going to try to tough it
> out... but it looks like that just won't work I wish there was some
Thats not correct.
You have to upper kern.vm.kmem.size as a workaround.
Please read the thread
Compiling a kernel with gdt:
/home/src/sys/i386/i386/machdep.c:1183: `MAXCPU' undeclared here (not in a funct
ion)
/home/src/sys/i386/i386/machdep.c:1183: size of array `gdt' has non-integer type
BK said MAXCPU is defined on machine/smp.h. Well, machdep.c includes smp.h
only if SMP is defined.
On Sat, Sep 23, 2000, Bruce Evans wrote:
> On Sat, 23 Dec 2000, Adrian Chadd wrote:
>
> > Here's the patch:
> >
> > --- fsck.c.orig Sat Dec 23 11:13:30 2000
> > +++ fsck.c Sat Dec 23 11:13:34 2000
> > @@ -501,7 +501,7 @@
> > errx(1, "partition `%s' is not of a legal vfstype"
hi, there!
On Sat, 23 Sep 2000, Leif Neland wrote:
> Pine 4.21 complains that /var/mail is vulnerable, that the perms should be
> 1777
>
> Would this be less vulnerable than 775 which make world restores it to?
this happens because ports/mail/pine4/patches/patch-aw was not merged when
libc-cli
23 matches
Mail list logo
