Date: Fri, 06 Mar 1998 01:01:00 -0600 From: POSTMASTER@MSPO2.MED.UTMB.EDU To: stable@FreeBSD.ORG Subject: Mail failure Message-ID: <01IUC3IACH0Y0004D3@BEACH.UTMB.EDU>
next in thread | raw e-mail | index | archive | help
FROM: UTMB/MSPO2/POSTMASTER
TO: stable@FreeBSD.ORG DATE: 03-06-98
TIME: 01:02
SUBJECT: Mail failure
------------------------------------------------------------------------------
[002] Mail was received that was addressed to unknown addresses.
Mail item was not delivered to:
UTMB/MSPO2/ehymel
------------------------------------------------------------------------------
stable-digest Thursday, March 5 1998 Volume 04 : Number 026
In this issue:
When: 2.2.5-stable branch freeze and beginning of 2.2.6-BETA
Re: When: 2.2.5-stable branch freeze and beginning of 2.2.6-BETA
Re: When: 2.2.5-stable branch freeze and beginning of 2.2.6-BETA
Re: When: 2.2.5-stable branch freeze and beginning of 2.2.6-BETA
problems with de driver for quad card
Re: When: 2.2.5-stable branch freeze and beginning of 2.2.6-BETA
Re: When: 2.2.5-stable branch freeze and beginning of 2.2.6-BETA
Re: When: 2.2.5-stable branch freeze and beginning of 2.2.6-BETA
Re: When: 2.2.5-stable branch freeze and beginning of 2.2.6-BETA
Re: problems with de driver for quad card
Re: When: 2.2.5-stable branch freeze and beginning of 2.2.6-BETA
Re: 'make world': /bin/sh not found
Compile failure on gctags
Request for next release
Re: Compile failure on gctags
Re: Request for next release
Re: Compile failure on gctags
Re: Request for next release
Re: Compile failure on gctags
Re: Request for next release
Re: Request for next release
Re: Request for next release
Re: Request for next release
RAID Controllers
-stable suitable for small-enterprise NFS server?
problem compiling stable yesterday.....
Re: problem compiling stable yesterday.....
Re: RAID Controllers
Re: problem compiling stable yesterday.....
Re: problem compiling stable yesterday.....
Re: problem compiling stable yesterday.....
RE: is xntpd working in -STABLE?
[none]
Re: Request for next release
PCI LKM support: Need test results under 2.2.5 [se@FreeBSD.ORG: Re: PCI
LKM's?]
Re: Request for next release
UUCP request for next release
Re: UUCP request for next release
Re: UUCP request for next release
Re: mgetty and iij-ppp
Re: mgetty and iij-ppp
bind
Re: bind
Re: bmake
panic in vfs_bio.c getnewbuf+0x21f
----------------------------------------------------------------------
Date: Wed, 04 Mar 1998 21:22:48 -0800
From: "Jordan K. Hubbard" <jkh@FreeBSD.ORG>
Subject: When: 2.2.5-stable branch freeze and beginning of 2.2.6-BETA
.. will be Monday, March 9th. That means all general merge work and
general sysinstall hackery must be done by 1:00PM PST on that day so
that we may enter the BETA test cycle and start regression testing.
Daily snapshots of the BETA bits will be made available as usual in
ftp://releng22.freebsd.org/pub/FreeBSD.
The BETA period for 2.2.6 will end on the 24th of March at 1:00AM PST,
e.g. just a little after the 23rd of March has ended. :) I will be
tagging the tree in preparation for 2.2.6 release at that time.
Actually meeting a planned-in-advance deadline would also be a new
thing around here and I'm going to do my darndest to see that it
happens for once. :-)
Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Wed, 04 Mar 1998 22:21:36 -0800
From: Studded <Studded@dal.net>
Subject: Re: When: 2.2.5-stable branch freeze and beginning of 2.2.6-BETA
Jordan K. Hubbard wrote:
>
> ... will be Monday, March 9th.
So I take it we're not going to wait for XFree86 R6.4? According to
the ftp site they're planning wide release by the end of march. Or
perhaps we're part of the inner circle they mention? :)
Doug
- --
*** Chief Operations Officer, DALnet IRC network ***
*** Proud operator, designer and maintainer of the world's largest
*** Internet Relay Chat server. 5,328 clients and still growing.
*** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 05 Mar 1998 15:47:52 +0900
From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Subject: Re: When: 2.2.5-stable branch freeze and beginning of 2.2.6-BETA
>> ... will be Monday, March 9th.
>
> So I take it we're not going to wait for XFree86 R6.4? According to
>the ftp site they're planning wide release by the end of march. Or
>perhaps we're part of the inner circle they mention? :)
I believe the next XFree86 release will still be based on X11R6.3.
Kazu
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Wed, 04 Mar 1998 23:20:47 -0800
From: Studded <Studded@dal.net>
Subject: Re: When: 2.2.5-stable branch freeze and beginning of 2.2.6-BETA
Kazutaka YOKOTA wrote:
>
> >> ... will be Monday, March 9th.
> >
> > So I take it we're not going to wait for XFree86 R6.4? According to
> >the ftp site they're planning wide release by the end of march. Or
> >perhaps we're part of the inner circle they mention? :)
>
> I believe the next XFree86 release will still be based on X11R6.3.
Nothing personal because I don't know you, but one of the worst things
you can do on a technical list is guess. Please confirm your facts
before you state your opinions. Check out
http://www.camb.opengroup.org/tech/desktop/x/.
Doug
- --
*** Chief Operations Officer, DALnet IRC network ***
*** Proud operator, designer and maintainer of the world's largest
*** Internet Relay Chat server. 5,328 clients and still growing.
*** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 05 Mar 1998 02:38:03 -0500
From: "Prashant R. Chandra" <prashant+@cs.cmu.edu>
Subject: problems with de driver for quad card
Hi! All,
Please forgive me if this question has been asked before on the
mailing
list. I want to report a problem we are facing with the driver for the
Zynx ZX346 Quad PCI ethernet card. When two of these cards are
connected
back-to-back (in two Pentium II PCs) the configuration seems to go
haywire.
The cards come up complaining that autosense failed and if I use
ifconfig
to set the media type to 100baseTX on both ends, I get connectivity but
I have problem with bidirectional traffic. Ping seems to work fine, but
doing a TCP bandwidth test using ttcp fails because packets are being
dropped on the point-to-point link between the two cards. (Fails means
the TCP bandwidth is only about 0.8 Mbps or so). Another problem is
that
I cannot get the link to operate at 10 Mbps. If I set the media to
10baseT/UTP,
the interface reports that it has 'no carrier'.
I have repeated the exact same tests with Windows NT 4.0 and everything
seems to be fine (TCP bandwidth of 93 Mbps).
Everything is also fine when one end of the link is a
Dec Alpha workstation with a 100 Mbps ethernet interface (not the same
quad board). The problem only happens when two quad cards are connected
back to back in FreeBSD PCs.
The problem seems to be due to misconfiguration of
full-duplex/half-duplex
operation. The list of supported media types for the de driver does not
include 100baseTX <full-duplex> and 10baseT/UTP <full-duplex>. What is
the
reason? (the hardware supports full-duplex operation)
The version of FreeBSD we are using is FreeBSD 2.2.5. We also see this
problem with NetBSD 1.3. It is not suprising since the driver is the
same.
I had posted this message on the NetBSD mailing list a month ago and got
no
reply. Hopefully I will have better luck this time :-). If anyone out
there
has tried the quad cards in a back-to-configuration (using a null-cable)
and
has encountered similar problems please let me know. Any suggestions on
how
to tackle this will be greatly appreciated. Please reply directly to
prashant@cs.cmu.edu.
Thank you.
-prashant
PS: The exact ifconfig command we use to bring up the interfaces as
100Mbps
is:
ifconfig de0 192.200.51.1 255.255.255.0 192.200.51.255 media 100baseTX
up
- --
____________________________________________________
R. Prashant Chandra
e-mail: prashant@cs.cmu.edu
Web: http://www.cs.cmu.edu/~prashant
Phone: 412-268-2580 (Office)
412-268-7560 (Lab)
412-681-3829 (Home)
____________________________________________________
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Wed, 04 Mar 1998 23:40:54 -0800
From: "Jordan K. Hubbard" <jkh@FreeBSD.ORG>
Subject: Re: When: 2.2.5-stable branch freeze and beginning of 2.2.6-BETA
> So I take it we're not going to wait for XFree86 R6.4? According to
> the ftp site they're planning wide release by the end of march. Or
> perhaps we're part of the inner circle they mention? :)
I don't know the answer to this yet. We'll have to see.
Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Wed, 04 Mar 1998 23:48:58 -0800
From: "Jordan K. Hubbard" <jkh@FreeBSD.ORG>
Subject: Re: When: 2.2.5-stable branch freeze and beginning of 2.2.6-BETA
> > I believe the next XFree86 release will still be based on X11R6.3.
>
> Nothing personal because I don't know you, but one of the worst things
> you can do on a technical list is guess. Please confirm your facts
> before you state your opinions. Check out
> http://www.camb.opengroup.org/tech/desktop/x/.
I agree, uninformed guessing can be a bad thing. What guess lies
behind your claim that XFree86 3.3.2 will be based on X11R6.4? Just
because it's available internally to consortium members is by no means
a declaration that the XFree86 project intends to track it in their
upcoming point release of 3.3.2 and, in fact, I'd say that it'd be a
very bad guess indeed to assume such a thing. :-)
Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 05 Mar 1998 00:10:09 -0800
From: Michael Oski <oski@pacbell.net>
Subject: Re: When: 2.2.5-stable branch freeze and beginning of 2.2.6-BETA
Jordan K. Hubbard wrote:
> > > I believe the next XFree86 release will still be based on X11R63.
> >
> > Nothing personal because I don't know you, but one of the worst
things
> > you can do on a technical list is guess. Please confirm your facts
> > before you state your opinions. Check out
> > http://www.camb.opengroup.org/tech/desktop/x/.
>
> I agree, uninformed guessing can be a bad thing. What guess lies
> behind your claim that XFree86 3.3.2 will be based on X11R6.4? Just
> because it's available internally to consortium members is by no means
> a declaration that the XFree86 project intends to track it in their
> upcoming point release of 3.3.2 and, in fact, I'd say that it'd be a
> very bad guess indeed to assume such a thing. :-)
>
> Jordan
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
Ah, the joy of rash assumptions....
FYI - XFree86 v3.3.2 is still based on X11R6.3, you can verify by
checking the release notes included in the .tgz's.
Also, www.XFree86.org claims they have no scheduled release date for
version 4.0.
Now here's my assumption: this is most likely the first based on X11R6.4
;-)
Michael!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 05 Mar 1998 17:20:31 +0900
From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Subject: Re: When: 2.2.5-stable branch freeze and beginning of 2.2.6-BETA
>> > So I take it we're not going to wait for XFree86 R6.4? According
to
~~~~~~~
>> >the ftp site they're planning wide release by the end of march. Or
>> >perhaps we're part of the inner circle they mention? :)
>>
>> I believe the next XFree86 release will still be based on X11R6.3.
>
> Nothing personal because I don't know you, but one of the worst things
>you can do on a technical list is guess. Please confirm your facts
>before you state your opinions. Check out
>http://www.camb.opengroup.org/tech/desktop/x/.
Nothing personal, but aren't you rather confusing the Open Group and
the XFree86 Project Inc?
XFree86 is primarily developed and distributed by the XFree86 Project
Inc. The code is, of course, derived from that of the Open Group.
But, it does not necessarily mean that the latest release from the
XFree86 always matches the latest release of X11.
In fact
http://www.camb.opengroup.org/tech/desktop/x/r6.4doc/relnotes/relnotes.htm
mentions XFree86 3.3.1 which was released in Aug. 97 and is based on
X11R6.3pl2.
You had better check out the XFree86 web site:
http://www.xfree86.org/
rather than the Open Group's, for the latest information and status
of XFree86.
Kazu
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 5 Mar 1998 10:30:21 +0100 (CET)
From: Andre Albsmeier <andre.albsmeier@mchp.siemens.de>
Subject: Re: problems with de driver for quad card
> Hi! All,
> Please forgive me if this question has been asked before on the
> mailing
> list. I want to report a problem we are facing with the driver for the
> Zynx ZX346 Quad PCI ethernet card. When two of these cards are
> connected
> back-to-back (in two Pentium II PCs) the configuration seems to go
> haywire.
> The cards come up complaining that autosense failed and if I use
> ifconfig
> to set the media type to 100baseTX on both ends, I get connectivity but
> I have problem with bidirectional traffic. Ping seems to work fine, but
> doing a TCP bandwidth test using ttcp fails because packets are being
> dropped on the point-to-point link between the two cards. (Fails means
> the TCP bandwidth is only about 0.8 Mbps or so). Another problem is
> that
> I cannot get the link to operate at 10 Mbps. If I set the media to
> 10baseT/UTP,
> the interface reports that it has 'no carrier'.
The de driver is broken regarding the media selection. (PR 4841).
I had some email exchange with Matt Thomas concerning this but
haven't heard from him for approx. 2 month. I gave it up now and
will keep on using the old version 1.54.2.6 which works for
my SMC 8434BT.
-Andre
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 05 Mar 1998 00:57:57 -0800
From: Studded <Studded@san.rr.com>
Subject: Re: When: 2.2.5-stable branch freeze and beginning of 2.2.6-BETA
Kazutaka YOKOTA wrote:
>
> >> > So I take it we're not going to wait for XFree86 R6.4?
According to
> ~~~~~~~
Please don't assume I don't know what I mean. I asked the question I
wanted to ask. What I should have made more clear is that the open
group's ftp site was the one I was referring to.
> Nothing personal, but aren't you rather confusing the Open Group and
> the XFree86 Project Inc?
Nope, sorry I wasn't more clear.
> XFree86 is primarily developed and distributed by the XFree86 Project
> Inc. The code is, of course, derived from that of the Open Group.
> But, it does not necessarily mean that the latest release from the
> XFree86 always matches the latest release of X11.
> You had better check out the XFree86 web site:
> http://www.xfree86.org/
> rather than the Open Group's, for the latest information and status
> of XFree86.
I did, and there was no mention of anything beyond 3.3.1. Anyway, I've
spent all day arguing with a pita solaris machine, and I am too tired to
really give a rip. My apologies for any offense.
Doug
- --
*** Chief Operations Officer, DALnet IRC network ***
*** Proud operator, designer and maintainer of the world's largest
*** Internet Relay Chat server. 5,328 clients and still growing.
*** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 5 Mar 1998 10:01:44 +0000
From: nik@iii.co.uk
Subject: Re: 'make world': /bin/sh not found
On Wed, Mar 04, 1998 at 01:49:36AM -0800, Jordan K. Hubbard wrote:
> > This is an odd one. I'm trying to update my 2.2.5-stable system to the
> > latest -stable. My last successful 'make world' was on Jan 31 this
> > year.
>
> Just a suggestion: cp /usr/src/share/mk/* /usr/share/mk
> I suspect that your bsd.info.mk file may be spooged.
No joy. Something I neglected to mention was that I can go into the
appropriate directory and run the 'make clean' by hand it works with no
problems. It looks as though I'm hitting some sort of resource limit,
but I can't find where.
Very odd.
N
- --
Work: nik@iii.co.uk | FreeBSD + Perl + Apache
Rest: nik@nothing-going-on.demon.co.uk | Remind me again why we need
Play: nik@freebsd.org | Microsoft?
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: 05 Mar 1998 13:10:31 +0100
From: sperber@informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor])
Subject: Compile failure on gctags
In yesterday's STABLE (fetched from ftp.de.freebsd.org), the build
fails like this:
/usr/src/usr.bin/global/gctags/C.c: In function `c_entries':
/usr/src/usr.bin/global/gctags/C.c:280: `rflag' undeclared (first use this
function)
/usr/src/usr.bin/global/gctags/C.c:280: (Each undeclared identifier is
reported only once
/usr/src/usr.bin/global/gctags/C.c:280: for each function it appears in.)
I think that one occurrence of rtag needs to be protected by an
#ifdef GTAGS
- --
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 05 Mar 1998 08:35:50 -0500
From: Robert Withrow <witr@rwwa.com>
Subject: Request for next release
If the next CDROM release of -stable is intended to be a 4 CD monster,
would it be possible for the insert to give detailed instructions
and information to dummies like me about what exactly each of the
CD's are used for?
I mean, I got to understand the "live file system" CD back in the
good old 2 CD days. And I always enjoy the challenge of finding
(or not finding) the unpacked source distribution. But when the
2.2.5 release came out I did't have a clue about what to do with
my 4 CD riches...
;-)
- ---------------------------------------------------------------------
Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.COM
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 5 Mar 1998 05:36:03 -0800 (PST)
From: Chris Timmons <skynyrd@opus.cts.cwu.edu>
Subject: Re: Compile failure on gctags
What, without even my mangling hands stirring things up? I'll take a look
momentarily.
- -Chris
On 5 Mar 1998, Michael Sperber [Mr. Preprocessor] wrote:
>
> In yesterday's STABLE (fetched from ftp.de.freebsd.org), the build
> fails like this:
>
> /usr/src/usr.bin/global/gctags/C.c: In function `c_entries':
> /usr/src/usr.bin/global/gctags/C.c:280: `rflag' undeclared (first use this
function)
> /usr/src/usr.bin/global/gctags/C.c:280: (Each undeclared identifier is
reported only once
> /usr/src/usr.bin/global/gctags/C.c:280: for each function it appears in)
>
> I think that one occurrence of rtag needs to be protected by an
>
> #ifdef GTAGS
>
> --
> Cheers =8-} Mike
> Friede, Völkerverständigung und überhaupt blabla
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 05 Mar 1998 05:45:53 -0800
From: "Jordan K. Hubbard" <jkh@FreeBSD.ORG>
Subject: Re: Request for next release
> If the next CDROM release of -stable is intended to be a 4 CD monster,
> would it be possible for the insert to give detailed instructions
> and information to dummies like me about what exactly each of the
> CD's are used for?
Yes, that's already planned along with updated installation
instructions. The next booklet will be a total rewrite, essentially.
Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 5 Mar 1998 06:20:54 -0800 (PST)
From: Chris Timmons <skynyrd@opus.cts.cwu.edu>
Subject: Re: Compile failure on gctags
Michael,
I didn't see it at first, but now I do: global is contribified in -stable,
so there shouldn't be ANY program source files under src/usr.bin/global.
I just built it here without any problem. The question is, what's up with
your sources?
I'm not sure how you are updating your sources, but you should use CVSup.
See the FreeBSD Handbook at http://www.freebsd.org for instructions on how
to do that. If you are ftp'ing the CVS repository, that is a sure way to
run amok - retrieve that with CVSup as well. If you are updating your
tree with CVS, you must say 'cvs update -Pd -rRELENG_2_2' in /usr/src.
Regards,
- -Chris
On 5 Mar 1998, Michael Sperber [Mr. Preprocessor] wrote:
>
> In yesterday's STABLE (fetched from ftp.de.freebsd.org), the build
> fails like this:
>
> /usr/src/usr.bin/global/gctags/C.c: In function `c_entries':
> /usr/src/usr.bin/global/gctags/C.c:280: `rflag' undeclared (first use this
function)
> /usr/src/usr.bin/global/gctags/C.c:280: (Each undeclared identifier is
reported only once
> /usr/src/usr.bin/global/gctags/C.c:280: for each function it appears in)
>
> I think that one occurrence of rtag needs to be protected by an
>
> #ifdef GTAGS
>
> --
> Cheers =8-} Mike
> Friede, Völkerverständigung und überhaupt blabla
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 5 Mar 1998 17:20:26 +0300
From: "Igor Sysoev" <igor@nitek.ru>
Subject: Re: Request for next release
> > If the next CDROM release of -stable is intended to be a 4 CD monster,
> > would it be possible for the insert to give detailed instructions
> > and information to dummies like me about what exactly each of the
> > CD's are used for?
>
> Yes, that's already planned along with updated installation
> instructions. The next booklet will be a total rewrite, essentially.
What' s about FAQ and Handbook ? Will be they included in HTML format ?
with best regards,
Igor Sysoev
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: 05 Mar 1998 17:03:00 +0100
From: sperber@informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor])
Subject: Re: Compile failure on gctags
>>>>> "Chris" == Chris Timmons <skynyrd@opus.cts.cwu.edu> writes:
Chris> Michael,
Chris> I didn't see it at first, but now I do: global is contribified
Chris> in -stable,
I'm new to -STABLE, so I don't know what that means or how to fix it.
Chris> so there shouldn't be ANY program source files under
Chris> src/usr.bin/global.
Can I just rm -rf that directory?
Chris> I just built it here without any problem. The question is, what's up
with
Chris> your sources?
Nothing. I pulled src.tar off
/ftp.de.freebsd.org:/pub/FreeBSD/FreeBSD-stable as per the Handbook
instructions. Anything wrong with that?
Chris> I'm not sure how you are updating your sources, but you should
Chris> use CVSup.
I can't because there's a networking bug in FreeBSD 2.2.5 that
makes network writes fail (duly reported). That's actually the
*reason* I want to compile stable at all---I have a faint hope it's
fixed there. Catch-22 dadadadadaaaaaaaaaaaa
- --
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 5 Mar 1998 17:46:38 +0100
From: Eivind Eklund <eivind@yes.no>
Subject: Re: Request for next release
On Thu, Mar 05, 1998 at 05:20:26PM +0300, Igor Sysoev wrote:
> > > If the next CDROM release of -stable is intended to be a 4 CD monster,
> > > would it be possible for the insert to give detailed instructions
> > > and information to dummies like me about what exactly each of the
> > > CD's are used for?
> >
> > Yes, that's already planned along with updated installation
> > instructions. The next booklet will be a total rewrite, essentially.
>
> What' s about FAQ and Handbook ? Will be they included in HTML format ?
I'm fairly certain the FAQ and handbook are automatically built for the
distribution now. There was a flurry of commits (by Jordan) some time back
to make this possible.
Eivind.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 05 Mar 1998 09:19:33 -0800
From: "Jordan K. Hubbard" <jkh@FreeBSD.ORG>
Subject: Re: Request for next release
> What' s about FAQ and Handbook ? Will be they included in HTML format ?
Yes, that's been fixed for awhile (see one of the SNAPs).
Jordan
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 5 Mar 1998 09:32:11 -0800 (PST)
From: Gary Kline <kline@tera.tera.com>
Subject: Re: Request for next release
According to Robert Withrow:
> If the next CDROM release of -stable is intended to be a 4 CD monster,
> would it be possible for the insert to give detailed instructions
> and information to dummies like me about what exactly each of the
> CD's are used for?
>
> I mean, I got to understand the "live file system" CD back in the
> good old 2 CD days. And I always enjoy the challenge of finding
> (or not finding) the unpacked source distribution. But when the
> 2.2.5 release came out I did't have a clue about what to do with
> my 4 CD riches...
>
> ;-)
>
I'll second this. I installed 2.1.5 to my new 6x86 box
no problem. Except for X. With my new 2.2.5 (very stable)
after perhaps 6 hours and as many retries, zip.
X fails. I can't find the VGA-16 driver. The release
fails to boot in any fashion, although this may be a BIOS
config problem.
Debian was almost pushbutton on my 0th and 2nd SCSI; so
X does work with my Matrox vcard.
This is my 3rd CD set. Should be the simplest, but isn't.
If there are any FBSD gurus in the Seattle area willing
to help out, I'll buy ya a beer. In fact an entire case!
gary kline
kline@tera.com
kline@thought.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 5 Mar 1998 18:01:24 +0000 (GMT)
From: Scot Elliott <scot@poptart.org>
Subject: Re: Request for next release
On Thu, 5 Mar 1998, Robert Withrow wrote:
> I mean, I got to understand the "live file system" CD back in the
> good old 2 CD days. And I always enjoy the challenge of finding
> (or not finding) the unpacked source distribution. But when the
> 2.2.5 release came out I did't have a clue about what to do with
> my 4 CD riches...
>
True - the descriptions on the last CD sets weren't entirely accurate ;-)
I only just discovered the 'missing' packages on the fourth CD. Is there
really not enough room on any of the CDs for the whole packages
collection? And what colour is the cutesy little daemon fellow going to
be this time?
-
-----------------------------------------------------------------------------
Scot Elliott (scot@poptart.org) | Work: +44 (0)1344 899401
PGP fingerprint: FCAE9ED3A234FEB59F8C7F9DDD112D | Home: +44 (0)181 8961019
-
-----------------------------------------------------------------------------
Public key available by finger at: finger scot@poptart.org
or at: http://www.poptart.org/pgpkey.html
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 5 Mar 1998 13:48:25 -0500 (EST)
From: lrios <lrios@ziplink.net>
Subject: RAID Controllers
Does Free BSD 2-2-5 have support for RAID controllers?? If so what brand
of controllers will it support??
If any would be appreciated..
______ __
/___ / / / __
/ /(@)__ / (@)__ / /__ lrios@ziplink.net
/ // / _ \/ / / _ \/ '_/
/ //_/ .__/_/_/_//_/_/\_\ NASA TEAM
/ /__/_/___________________ `He who dies with the most toys win!`
/___________________________
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 5 Mar 1998 14:04:00 -0500 (EST)
From: Snob Art Genre <benedict@echonyc.com>
Subject: -stable suitable for small-enterprise NFS server?
I can't imagine that this would be the case . . . but are there any NFS
issues I should know about before building a ~12-user -stable NFS box?
Ben
"You have your mind on computers, it seems."
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 5 Mar 1998 14:29:55 -0500 (EST)
From: zoonie <zoonie@myhouse.com>
Subject: problem compiling stable yesterday.....
i have been having some trouble compiling 2.2.5-stable on this machine for
the last couple of days. originally i was getting signal 11s when a "make
buildworld" was run. so, instead of trying to figure out exactly what the
problem was i just deleted everything in /usr/src and used cvsup to put it
all back. then i did a "make world" and everything was going along just
fine so i went to bed. this morning i checked and i saw that the machine
rebooted itself. the machine is running stable from around jan.29th and
it has always compiled stable without any problems and i have never had
any problems with it. does anybody have any ideas or do i need to RTFM?
thanks.......
> t found at 0x360
> pid 20789 (make), uid 0: exited on signal 11 (core dumped)
>
>
> Fatal trap 12: page fault while in kernel mode
> fault virtual address = 0xefc004b8
> fault code = supervisor read, page not present
> instruction pointer = 0x8:0xf017484b
> stack pointer = 0x10:0xefbfff14
> frame pointer = 0x10:0xefbfff24
> code segment = base 0x0, limit 0xfffff, type 0x1b
> = DPL 0, pres 1, def32 1, gran 1
> processor eflags = interrupt enabled, resume, IOPL = 0
> current process = 14017 (as)
> interrupt mask = net tty bio
> panic: page fault
>
> syncing disks... 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32 32
32 giving up
> Automatic reboot in 15 seconds - press a key on the console to abort
> Rebooting...
> Copyright (c) 1992-1998 FreeBSD Inc.
> Copyright (c) 1982, 1986, 1989, 1991, 1993
> The Regents of the University of California. All rights reserved.
>
> FreeBSD 2.2.5-STABLE #0: Sat Jan 31 08:44:48 EST 1998
> root@zero.myhouse.com:/usr/src/sys/compile/ZERO
> CPU: i486DX (486-class CPU)
> real memory = 33554432 (32768K bytes)
> avail memory = 30826496 (30104K bytes)
> Probing for devices on the ISA bus:
> sc0 at 0x60-0x6f irq 1 on motherboard
> sc0: VGA color <16 virtual consoles, flags=0x0>
> sio0 at 0x3f8-0x3ff irq 4 on isa
> sio0: type 16450
> sio1 at 0x2f8-0x2ff irq 3 on isa
> sio1: type 16450
> lpt0 at 0x378-0x37f irq 7 on isa
> lpt0: Interrupt-driven port
> lp0: TCP/IP capable interface
> fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
> fd0: 1.44MB 3.5in
> wdc0 at 0x1f0-0x1f7 irq 14 on isa
> wdc0: unit 0 (wd0): <WDC AC22100H>
> wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S
> 1 3C5x9 board(s) on ISA found at 0x300
> ep0 at 0x300-0x30f irq 10 on isa
> ep0: aui/utp[*UTP*] address 00:a0:24:04:17:c9
> npx0 flags 0x1 on motherboard
> npx0: INT 16 interface
> WARNING: / was not properly dismounted.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 5 Mar 1998 11:33:27 -0800 (PST)
From: Tom <tom@uniserve.com>
Subject: Re: problem compiling stable yesterday.....
On Thu, 5 Mar 1998, zoonie wrote:
> the last couple of days. originally i was getting signal 11s when a "make
Your hardware is bad.
Tom
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 5 Mar 1998 11:09:47 -0800 (PST)
From: Tom <tom@uniserve.com>
Subject: Re: RAID Controllers
On Thu, 5 Mar 1998, lrios wrote:
> Does Free BSD 2-2-5 have support for RAID controllers?? If so what brand
> of controllers will it support??
> If any would be appreciated..
- Any kind of SCSI-SCSI RAID box
- DPT (you need to install driver yourself from ftp.simon-shapiro.org)
Tom
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 5 Mar 1998 14:37:01 -0500 (EST)
From: zoonie <zoonie@myhouse.com>
Subject: Re: problem compiling stable yesterday.....
ok, i'll look into that. i was wondering about that as i composed the
message.....thanks....
BTW, somebody had mentioned a signal 11 FAQ a couple of months ago on this
list and i looked around but didn't find it. does anybody know where it
is located?
On Thu, 5 Mar 1998, Tom wrote:
>
> On Thu, 5 Mar 1998, zoonie wrote:
>
> > the last couple of days. originally i was getting signal 11s when a "make
>
> Your hardware is bad.
>
> Tom
>
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 5 Mar 1998 14:16:34 -0600
From: Paul Saab <paul@mu.org>
Subject: Re: problem compiling stable yesterday.....
http://www.freebsd.org/FAQ/FAQ71.html#71
Paul
zoonie (zoonie@myhouse.com) wrote:
> ok, i'll look into that. i was wondering about that as i composed the
> message.....thanks....
>
> BTW, somebody had mentioned a signal 11 FAQ a couple of months ago on this
> list and i looked around but didn't find it. does anybody know where it
> is located?
>
> On Thu, 5 Mar 1998, Tom wrote:
>
> >
> > On Thu, 5 Mar 1998, zoonie wrote:
> >
> > > the last couple of days. originally i was getting signal 11s when a
"make
> >
> > Your hardware is bad.
> >
> > Tom
> >
> >
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 5 Mar 1998 15:37:15 -0500 (EST)
From: zoonie <zoonie@myhouse.com>
Subject: Re: problem compiling stable yesterday.....
thanks for the pointer, i should probably look at the freebsd FAQ more
often and instead of the handbook now i know where the signal 11 FAQ
is....
thanks again to everybody else that responded also....
On Thu, 5 Mar 1998, Paul Saab wrote:
>
> http://www.freebsd.org/FAQ/FAQ71.html#71
>
> Paul
>
> zoonie (zoonie@myhouse.com) wrote:
> > ok, i'll look into that. i was wondering about that as i composed the
> > message.....thanks....
> >
> > BTW, somebody had mentioned a signal 11 FAQ a couple of months ago on this
> > list and i looked around but didn't find it. does anybody know where it
> > is located?
> >
> > On Thu, 5 Mar 1998, Tom wrote:
> >
> > >
> > > On Thu, 5 Mar 1998, zoonie wrote:
> > >
> > > > the last couple of days. originally i was getting signal 11s when a
"make
> > >
> > > Your hardware is bad.
> > >
> > > Tom
> > >
> > >
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-stable" in the body of the message
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 5 Mar 1998 15:55:27 -0500
From: Max Euston <meuston@jmrodgers.com>
Subject: RE: is xntpd working in -STABLE?
[ David: Sorry for the blank reply, my mouse got hyper for a moment :-) ]
David,
Funny, I just started working on this yesterday. I don't have a complete
answer for you, but here are some data points:
1) Yes, xntpd DOES run on -stable (cvsup'ed and "make buildworld
installworld" within about the last week).
2) I had the same symptom - the '-d' did no good either.
3) With all the variables I was trying, I'm not sure exactly how I got it
working.
4) I had to make sure to open my firewall (I was also setting up ipfw for
the first time) for udp port 123 (I know this is obvious, but it may or may
not be the cause for the lack of output even w/ '-d').
5) I used 'ntpdate -d' to get some more information when it was failing
(and am running it now at bootup).
6) My drift file is empty, but I manually created
/etc/ntp.{conf|drift|keys}. (I am still working on this).
7) From /etc/rc.conf:
ntpdate_enable="YES" # Run the ntpdate to sync time (or NO).
ntpdate_flags="-bs ntp.ctr.columbia.edu" # Flags to ntpdate (if
enabled).
xntpd_enable="YES" # Run xntpd Network Time Protocol (or NO).
xntpd_flags="" # Flags to xntpd (if enabled).
8) From /etc/ntp.conf (minimal):
server ntp.ctr.columbia.edu
peer ns1
I didn't get to read my mail early today, so you may have already got this
working. If not, let me know if I can give any further information.
Max
- -----
Max Euston <meuston@jmrodgers.com>
Sysadm, Programmer, etc...
On Wednesday, March 04, 1998 5:26 PM, David O'Brien [SMTP:obrien@NUXI.com]
wrote:
> I've got no problems with xntpd on a 2.2.5-R box with -CURRENT kernel
> from last week.
>
> BUT, on my two machines I've done a `make world' on it doesn't.
> I can't get it to create a `/var/run/ntp.drift' file. I've taken the
> /etc/ntp.conf file from the 2.2.5-R box and put it on the other two. No
> help. Tried ``xntpd -d'' to get some debuging output. It just exits.
> No explaintion, no output to the screen at all. /var/log/messages says:
>
> Mar 4 14:24:50 kongur xntpd[2261]: xntpd version=3.4e (beta
multicast);
> Sat Oct 4 12:04:05 GMT 1997 (1)
> Mar 4 14:24:50 kongur xntpd[2261]: tickadj = 5, tick = 10000,
> tvu_maxslew = 495
>
> but xntpd wont deamonize.
>
> --
> -- David (obrien@NUXI.com -or- obrien@FreeBSD.org)
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Thu, 5 Mar 1998 17:14:59 -0500
From: "Lawrence Katz" <lkatz@mastermind-tech.com>
Subject: [none]
subscribe freebsd-stable
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Fri, 06 Mar 1998 10:38:34 +1100
From: John Saunders <john.saunders@scitec.com.au>
Subject: Re: Request for next release
Robert Withrow wrote:
> I mean, I got to understand the "live file system" CD back in the
> good old 2 CD days. And I always enjoy the challenge of finding
> (or not finding) the unpacked source distribution.
Err, exactly what _is_ the live filesystem used for? I guess it could
be mounted to give all the binaries if I ever have to boot from a
rescue disk. But I've been lucky so far.
What exactly do you use the unpacked source distribution for? I tried
using the union filesystem to mount it so I could build directly off
the CD. But union is broken so I ended up having to copy the source
onto a harddisk anyway. Same with the CVS repository, you can't use
it on the CD and have to copy to harddisk. Also it seems faster to
extract the compressed tar files from the CD than to copy the unpacked
version.
So I never got the point of wasting all those CDs. :)
Cheers.
- -- +------------------------------------------------------------+
. | John Saunders mailto:John.Saunders@scitec.com.au (Work) |
,--_|\ | mailto:john@nlc.net.au (Home) |
/ Oz \ | http://www.nlc.net.au/~john/ |
\_,--\_/ | SCITEC LIMITED Phone +61 2 9428 9563 Fax +61 2 9428 9933 |
v | "By the time you make ends meet, they move the ends." |
+------------------------------------------------------------+
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
------------------------------
Date: Fri, 6 Mar 1998 00:47:05 +0100
From: Stefan Esser <se@FreeBSD.ORG>
Subject: PCI LKM support: Need test results under 2.2.5 [se@FreeBSD.ORG: Re:
PCI LKM's?]
***********************************************************
I'd ***really*** love to see PCI LKM support make it
into 2.2.6, but there is a problem, and I need help
from users of FreeBSD-2.2.x.
If you are intererested in this feature, then please
build a patched kernel, and let me know what you find!
***********************************************************
I had sent the message below to Danil O'Conner a few weeks
ago, and he reported a problem with the *first* PCI device
not being attached by a kernel compiled with this patch.
The LKM code itself worked at a time (nearly one year ago),
but there might be some unexpected side effect of the diffs.
Since I do not have a 2.2.5 system to test this on myself
(and since I'm short fo spare time), I'd appreciate more
feedback about this set of patches. I did not touch the
interrupt registration code, at least not knowingly :)
Please let me know, whether a kernel compiled with this
patch attaches all PCI devices. It will either work, or
fail when probing for devices (best if you try booting
with -s and just check for diagnostics at the start of
the PCI probes).
- --liOOAslEiF7prFVr
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=mutthy1553
On 1998-02-17 10:50 +1030, Daniel O'Connor <doconnor@gsoft.com.au> wrote:
> > I added PCI LKM support to the PCI code more than one year
> > ago, but never put it into the "official" 2.2.x repository.
> > If you want patches, I can provide you with them, but if
> > there is sufficient interest, I can also commit that code
> > to -stable.
> I would like that very much :)
Ok, since you offered to test the code, I've appended
the diffs to /sys/pci/{pci.c,pcibus.h,pci_ioctl.h} and
to /usr/src/usr.sbin/pciconf/pciconf.{c,8} as separate
attachments. Please apply and test them ...
(As I explained before, I don't have any 2.2.x system
to test them on. I compiled pci.c with those patches,
and found that one chunk had gone to the wrong lines,
causing a syntax error. This is fixed in the patches
I'm sending, but I'm a little worried, that it might
have happened in other less obvious places as well ...)
> > The interface is very simple:
> >
> > int pci_register_lkm (struct pci_device *dvp, int if_revision)
> What about unloading LKM's? Perhaps pci_unregister_lkm, which unlinks it
from
> the list and removes the lkm..?
Well, unloading LKMs should be possible, and I could
add support for that, but I didn't at the time, since
I felt that the rest of the kernel wasn't yet up to it.
AFAIK, there is no locking in place currently, which
would prevent unloading a busy driver.
If you have support for a shutdown function in your
driver, then I could call that, and thereafter remove
the driver from the list of known PCI devices in order
to prepare the unload.
> > I added a support function to pciconf (or rather the underlying
> > ioctl()), which reported whether a driver had been attached to
> > a device. This allowed the loading of PCI LKMs from a script
> > called from /etc/rc, controlled by the PCI vendor and device
> > IDs.
> Thats neat, and IMHO is a good idea for making the system more flexible (ie
> requiring less reboots :)
Only, if unloading of PCI LKMs is supported, I'm afraid.
If you need it, I can see what I can do within a few days,
though I'm very busy and can't promise anything, currently.
Regards, STefan
- --liOOAslEiF7prFVr
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="PCICONF-LKM.patch"
Index: pciconf.c
===================================================================
RCS file: /usr/cvs/src/usr.sbin/pciconf/pciconf.c,v
retrieving revision 1.1.1.1.2.3
diff -u -2 -r1.1.1.1.2.3 pciconf.c
- --- pciconf.c 1997/10/08 07:36:44 1.1.1.1.2.3
+++ pciconf.c 1998/02/17 21:22:55
@@ -50,13 +50,16 @@
static void readit(const char *, const char *, int);
static void writeit(const char *, const char *, const char *, int);
+static void chkattached(const char *, int);
+static exitstatus = 0;
static void
usage()
{
- - fprintf(stderr, "%s\n%s\n%s\n",
- - "usage: pciconf -l",
- - " pciconf -r [-b | -h] sel addr",
- - " pciconf -w [-b | -h] sel addr [value]");
+ fprintf(stderr, "%s\n%s\n%s\n%s\n",
+ "usage: pciconf -l",
+ " pciconf -a sel",
+ " pciconf -r [-b | -h] sel addr",
+ " pciconf -w [-b | -h] sel addr [value]");
exit (1);
}
@@ -66,11 +69,15 @@
{
int c;
- - int listmode, readmode, writemode;
+ int listmode, readmode, writemode, attachedmode;
int byte, isshort;
- - listmode = readmode = writemode = byte = isshort = 0;
+ listmode = readmode = writemode = attachedmode = byte = isshort = 0;
- - while ((c = getopt(argc, argv, "lrwbh")) != -1) {
+ while ((c = getopt(argc, argv, "alrwbh")) != -1) {
switch(c) {
+ case 'a':
+ attachedmode = 1;
+ break;
+
case 'l':
listmode = 1;
@@ -100,9 +107,13 @@
if ((listmode && optind != argc)
|| (writemode && optind + 3 != argc)
- - || (readmode && optind + 2 != argc))
+ || (readmode && optind + 2 != argc)
+ || (attachedmode && optind + 1 != argc))
usage();
if (listmode) {
list_devs();
+ } else if(attachedmode) {
+ chkattached(argv[optind],
+ byte ? 1 : isshort ? 2 : 4);
} else if(readmode) {
readit(argv[optind], argv[optind + 1],
@@ -115,5 +126,5 @@
}
- - return 0;
+ return exitstatus;
}
@@ -208,3 +219,25 @@
if (ioctl(fd, PCIOCWRITE, &pi) < 0)
err(1, "ioctl(PCIOCWRITE)");
+}
+
+static void
+chkattached (const char *name, int width)
+{
+ int fd;
+ struct pci_io pi;
+
+ pi.pi_sel = getsel(name);
+ pi.pi_reg = 0;
+ pi.pi_width = width;
+ pi.pi_data = 0;
+
+ fd = open(_PATH_DEVPCI, O_RDWR, 0);
+ if (fd < 0)
+ err(1, "%s", _PATH_DEVPCI);
+
+ if (ioctl(fd, PCIOCATTACHED, &pi) < 0)
+ err(1, "ioctl(PCIOCATTACHED)");
+
+ exitstatus = pi.pi_data ? 0 : 2; /* exit(2), if NOT attached */
+ printf("%s: %s%s\n", name, pi.pi_data == 0 ? "not " : "", "attached");
}
Index: pciconf.8
===================================================================
RCS file: /usr/cvs/src/usr.sbin/pciconf/pciconf.8,v
retrieving revision 1.3.2.1
diff -u -2 -r1.3.2.1 pciconf.8
- --- pciconf.8 1997/10/08 10:33:10 1.3.2.1
+++ pciconf.8 1998/02/17 21:28:24
@@ -33,4 +33,5 @@
.Sh SYNOPSIS
.Nm pciconf Fl l
+.Nm pciconf Fl a Ar selector
.Nm pciconf Fl r Ar selector
.Op Fl b | Fl h
@@ -105,4 +106,14 @@
.Fl l
can be used without modification. All numbers are base 10.
+.Pp
+With the
+.Fl a
+flag,
+.Nm
+determines whether any driver has been assigned to the device
+identified by
+.Ar selector .
+An exit status of zero indicates that the device has a driver;
+non-zero indicates that it does not.
.Pp
The
- --liOOAslEiF7prFVr
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename=loadlkm
#!/bin/sh
#
# Put this script into a new directory /etc/pci under the name "loadlkm" and
# make /etc/rc call it early (may have to load network interface drivers)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01IUC3IACH0Y0004D3>