th , 01 ÁÐÒ 1999, Daniel C. Sobral wrote:
> > Granted, we don't have a driver for that controller either, but the
> > programming manual is readily available from LSI Logic. Seems to me that
> > NetBSD has a driver for it, based on a Linux driver. (Been a while since
> > I looked into it, so I m
n file included from ../../ntfs/ntfs_vnops.c:66:
../../ntfs/ntfs.h:29: warning: `DIAGNOSTIC' redefined
opt_global.h:13: warning: this is the location of the previous definition
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wc
> n file included from ../../ntfs/ntfs_vnops.c:66:
> ../../ntfs/ntfs.h:29: warning: `DIAGNOSTIC' redefined
> opt_global.h:13: warning: this is the location of the previous definition
> cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
> -Wmissing-prototypes -Wpointer-arith -Wi
[replies redirected to hopefullly the right place]
> Please check these before potentially starting rumours.
> TCP_WRAPPERS is NOT in STABLE.
I can't really say it's in -CURRENT, either; it installs
/usr/lib/libwrap.so.3 and /usr/include/tcpd.h, but no /usr/libexec/tcpd as
far as I can see. The
N wrote:
> What is the reason behind not installing /usr/libexec/tcpd? I can see not
> mucking with /etc/inetd.conf by default, but having the binary around
> would definitely save a lot of people some work.
RTFM inetd(8).
RTFCM.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.or
>> What is the reason behind not installing /usr/libexec/tcpd? I can see not
>> mucking with /etc/inetd.conf by default, but having the binary around
>> would definitely save a lot of people some work.
> RTFCM.
Cool. Excellent. Thanks for the pointer. [sounds of foot in mouth insertion]
(shoul
N wrote:
> >> What is the reason behind not installing /usr/libexec/tcpd? I can see not
> >> mucking with /etc/inetd.conf by default, but having the binary around
> >> would definitely save a lot of people some work.
> > RTFCM.
>
> Cool. Excellent. Thanks for the pointer. [sounds of foot in mou
Hello,
I recently tried to update the egcs-1.1.2 and got this error. My system is
upto the current ctm src-cur.3811. The compiler is egcs-1.1.2. Any idea ?
Thanks.
Clarence
=== Error ===
===> Building for egcs-1.1.2
gmake[1]: Entering directory `/usr/ports/lang/egcs/work/egcs-1.1.2/l
In article <99040212091200.24...@camel.avias.com>,
Ilya Naumov wrote:
> how ironic - older 2.2.x do support it, but newer 3.1/4.0 does not.
What is ironic about that? Old OS versions support old hardware,
and new OS versions support new hardware. It makes perfect sense to
me.
John "My Sun 3/
> I recently tried to update the egcs-1.1.2 and got this error.
Fixed. Please fetch the latest Port version.
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
> Is there a simple knob to turn to get the egcs compiler by
> default?
Not really. You would have to CVSup my src/gnu/ bits and spam them over
the /usr/src/ tree.
> And, at the risk of being flamed, I noticed (after all these years)
> that we build some for Objective C stuff. Is this actual
Something that I have never experienced before this point and am not
sure whether to apply the concern to softupdates or the ATA - drivers.
After a power outage, restarting the computer in single user, running
fsck on all the entries in /etc/fstab, and typing exit it would tell me
that it could n
In article ,
Kevin G. Eliuk wrote:
>
> Something that I have never experienced before this point and am not
> sure whether to apply the concern to softupdates or the ATA - drivers.
>
> After a power outage, restarting the computer in single user, running
> fsck on all the entries in /etc/fstab,
I've committed the basic infrastructure to improve TLB management
on SMPs. Translation: this will lead to the elimination of a LOT
of interprocessor interrupts to invalidate TLB entries. I'll be
"turning on" the new mechanisms slowly so we can carefully debug
each step and (hopefully) avoid any p
>> (shouldn't auth.info be sent somewhere? Currently successful connections
>> don't seem to be logged at all.)
> You didn't include the patch for this :-)
--- /usr/src/etc/syslog.confWed Oct 14 23:59:55 1998
+++ /etc/syslog.confThu Feb 4 02:23:07 1999
@@ -11,6 +11,7 @@
*.notice;news.
> > Is there a simple knob to turn to get the egcs compiler by
> > default?
>
> Not really. You would have to CVSup my src/gnu/ bits and spam them over
> the /usr/src/ tree.
When do you intend to "throw the switch" in bringing egcs in by
default? A lot of people are asking and perhaps a bit o
> Also, I seem to recall that we already have another copy of libiberty
> (under gdb). Do we really need to have both of them?
The EGCS copy is newer. We are considering building a libiberty.* for
/usr/lib/. Once we know which sources to use, the duplicate can be
deleted.
--
-- David(obr.
Here is the explanation for the problem from the NcFTP author:
- Forwarded message from Mike Gleason -
Date: Fri, 02 Apr 1999 12:39:07 -0600
Subject: Re: (FWD) Re: Dates off by 1 year (was: Fools Day Joke ?)
The problem is that NcFTP 3 tries to parse the output of the listing and
stores
On Fri, 2 Apr 1999, David O'Brien wrote:
> > Also, I seem to recall that we already have another copy of libiberty
> > (under gdb). Do we really need to have both of them?
>
> The EGCS copy is newer. We are considering building a libiberty.* for
> /usr/lib/. Once we know which sources to use, t
On 2 April 1999 at 22:25, Doug Rabson wrote:
> We should also consider installing libbfd. If and when we bring in a newer
> version of gdb, it would be a good idea to avoid importing yet another
> version of libiberty and libbfd.
... and GNU regex.
Jacques Vidrine / n...@nectar.com / nec...@free
Hi all,
Baring unforeseen problems, I plan to pull the switch on Sunday that will
make EGCS the base compiler in 4.0-CURRENT.
A CVSup and a `build world' after I pull the switch should be all that is
necessary to give you the new compiler.
I have tested kernel builds and `make world' and believe
On Fri, 2 Apr 1999, David O'Brien wrote:
# Hi all,
#
# Baring unforeseen problems, I plan to pull the switch on Sunday that will
# make EGCS the base compiler in 4.0-CURRENT.
#
# A CVSup and a `build world' after I pull the switch should be all that is
# necessary to give you the new compiler.
#
On Fri, 2 Apr 1999, Alan Cox wrote:
>
> Now, if you're not using Luoqi's patches to enable multithreaded
> address spaces, you can stop reading here. If you are, you'll
> need to patch i386/i386/swtch.s as follows:
My suggestion is that we apply Luoqi's %fs patch to -current rather than
have t
Hi!
A fresh cvsup plus make buildworld did not complete on
my 3.0-RELEASE system.
--
r...@oranje# date
Fri Apr 2 22:37:32 CEST 1999
r...@oranje# make buildworld; date
-
> % netscape
> no recognized font charsets!
>
> 3.1-stable as of today
> navigator 4.5 freshly installed
I had similiar font problems when installing Navigator 4.5 under
Solaris 2.6.
They went away after I nuked all prior traces of Navigator, including
my .netscape directory (you should rename
> The name of the directory where it resides doesn't matter. It's not a
As long as that directory is not /var/db/pkg, where I put my package
information, I agree that it doesn't matter either. :-)
> The same situation arises whether the version info is in /var/db/pkg
> or /some/other/place. It
In article ,
Doug Rabson wrote:
> We should also consider installing libbfd.
We can do that any time (ELF only), as far as I'm concerned.
John
--
John Polstra j...@polstra.com
John D. Polstra & Co., Inc.Seattle, Washing
On Fri, 2 Apr 1999, John Polstra wrote:
> In article ,
> Kevin G. Eliuk wrote:
> >
> > WARNING: R/W mount of / denied. Filesystem is not clean - run fsck
>
> One possibility: Make sure your /etc/fstab lists the root device
> including the slice. For example, "/dev/wd0s1a" and _not_ "/dev/wd0
> Can you tell where the switch is so I can pull the switch early
The "switch" is me checking out src/gnu/usr.bin/cc, overlaying the bits
I've been working on and then committing them.
You can get the bits using the sup file I've posted to current last
month.
> and start fixing some of the ports
I didn't see anything along these lines the the archive, so
here goes... (something different to the other threads running
these days.)
In 3.3.1 and 4.0-current, if one puts the following in /etc/passwd
to enable NIS logins:
+:*:
then logins (console or ssh) of ordinary users don't w
Umm- it's never supposed to have been with a '*' in it for this YP
implementation, I believe. Fixing the security check would be a good
thing. Going to pam/nsswitch.conf would be even better.
On Fri, 2 Apr 1999, Scott Michel wrote:
> I didn't see anything along these lines the the archive, so
> Umm- it's never supposed to have been with a '*' in it for this YP
> implementation, I believe. Fixing the security check would be a good
> thing. Going to pam/nsswitch.conf would be even better.
Been that way for years, ever since I started supporting a SCO box
oh these many years ago with a U
On Fri, 2 Apr 1999, Scott Michel wrote:
> > Umm- it's never supposed to have been with a '*' in it for this YP
> > implementation, I believe. Fixing the security check would be a good
> > thing. Going to pam/nsswitch.conf would be even better.
>
> Been that way for years, ever since I started
In the last episode (Apr 02), David O'Brien said:
> Here is the explanation for the problem from the NcFTP author:
Oh yeah. go and ask the author. That's cheating.
-Dan
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
34 matches
Mail list logo
