Re: Upgrading 5.3 6.0 buildworld failure now in libmagic
From: Vizion [EMAIL PROTECTED] To: freebsd-stable@freebsd.org, [EMAIL PROTECTED] Date: Tue, 6 Dec 2005 19:41:30 -0800 Cc: Doug Barton [EMAIL PROTECTED], Kris Kennaway [EMAIL PROTECTED] Subject: Re: Upgrading 5.3 6.0 buildworld failure now in libmagic On Tuesday 06 December 2005 16:50, the author Allen contributed to the dialogue on- Re: Upgrading 5.3 6.0 buildworld failure now in libmagic: On Tue, December 6, 2005 19:44, Doug Barton wrote: On Tue, 6 Dec 2005, secmgr wrote: Not to belabour this, but the 6.0 release notes do specificly say 5.3 RELEASE and newer. 5.4-STABLE is newer. :) Source upgrades to FreeBSD 6.0-RELEASE are only supported from FreeBSD 5.3-RELEASE or later. Users of older systems wanting to upgrade 6.0-RELEASE will need to update to FreeBSD 5.3 or newer first, then to FreeBSD 6.0-RELEASE. How does this change to UPDATING in RELENG_6 look to you: Index: UPDATING === RCS file: /home/ncvs/src/UPDATING,v retrieving revision 1.416.2.7 diff -u -r1.416.2.7 UPDATING --- UPDATING1 Nov 2005 23:44:40 - 1.416.2.7 +++ UPDATING7 Dec 2005 00:42:04 - @@ -229,7 +229,13 @@ page for more details. Due to several updates to the build infrastructure, source - upgrades from versions prior to 5.3 no longer supported. + upgrades from versions prior to 5.4-STABLE are not likely + to succeed. Sorry to butt in but.. Doesn't the definition of -STABLE change, for all intents and purposes, by the minute? What next, versions prior to 5.4-STABLE as of MMDD ? I believe I've seen exactly this type of notation in UPDATING over the years, in both 4.x 5.x. + + When upgrading from one major version to another, it is + generally best to upgrade to the latest code in the branch + currently installed first, then do another upgrade to the + new branch. This is getting closer to the truth. Why don't you just say update to the most recent RELENG_5 before attempting. Future proof, no room for confusion. [...snip...] There is however a perennial problem that freebsd documentation has always been seen as behind and seperate from the development process rather than an Maybe (hmm, even probably :) but I've found documentation, announcements, errata, etc. (*manpages*) for FreeBSD to be *much* better, more relevant up to date than, umm, other opensource systems. Compared to FreeBSD, other systems' documentation/manpages seem haphazard in some cases even nonexistent. integral part of that process. [...snip...] Certainly better documentation for the upgrade path between 5.3 and 6.0 would have saved me a h*** of a lot of time.. but there it is.. live does not hand out many A++s I would guess that it says 5.3 instead of 5.4 due to oversight, e.g. it was written/documented/recommended before 5.4 was out. Maybe that's (part of) the basis for the Handbook's recommendation of reading the -stable list if you indeed want to track past -RELEASE. :) Thank you top everyone who helped. I have now successfully upgarded to 5.4 and am about to begin the last leg of this journey towards 6.0. my two pennorth david -- Mine too I guess :) -kc ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
UFS2 vs UFS1 determination
Hello -stable: How can I determine a filesystem's type in FreeBSD? More specifically, how can I determine whether a filesystem is UFS1 or UFS2 (assuming, of course, that UFS2 is supported by the OS)? FAQ/doc/RTFM pointers are welcome. :) Thanks, -kc ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-stable doesn't ifconfig at startup
Date: Fri, 11 Feb 2005 09:27:01 +0200
From: Ion-Mihai Tetcu [EMAIL PROTECTED]
To: Kenneth W Cochran [EMAIL PROTECTED]
Cc: freebsd-stable@freebsd.org
Subject: Re: 5.3-stable doesn't ifconfig at startup
On Fri, 11 Feb 2005 02:00:39 -0500 (EST)
Kenneth W Cochran [EMAIL PROTECTED] wrote:
Hello -stable:
Any idea(s) why (my) 5.3-stable (as of 9 February) isn't
configuring the network interface or setting up the default route?
I installed 5.3-release from CD and things worked fine.
Then I updated the system sources (via cvsup) to RELENG_5 and
went through {build,install}world/mergemaster/reboot as outlined
^^^
in /usr/src/UPDATING and now I get no network interfaces
^
configured no default route set. I've tracked RELENG_4 for
years with nothing like this ever happening. Kernel has not been
reconfigured (yet), it's still GENERIC, albeit RELENG_5 now.
In looking through the rc scripts, it appears that network
interface(s) are being renamed but I see no references to this
in, say, UPDATING or errara or other documentation. Any ideas?
mergemaster pilot error ?
If you didn't changed something in them I'd suggest wiping /etc/rc.d/*
and /etc/defaults/* and do a mergermaster -i
--
IOnut
Unregistered ;) FreeBSD user
First thing I thought of; both mergemaster -p and
mergemaster without arguments are fine; all its targets
updated accordingly.
-kc
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3-stable doesn't ifconfig at startup
Date: Fri, 11 Feb 2005 15:32:44 +0200
From: Ion-Mihai Tetcu [EMAIL PROTECTED]
To: Kenneth W Cochran [EMAIL PROTECTED]
Cc: freebsd-stable@freebsd.org
Subject: Re: 5.3-stable doesn't ifconfig at startup
On Fri, 11 Feb 2005 07:48:27 -0500 (EST)
Kenneth W Cochran [EMAIL PROTECTED] wrote:
Date: Fri, 11 Feb 2005 09:27:01 +0200
From: Ion-Mihai Tetcu [EMAIL PROTECTED]
To: Kenneth W Cochran [EMAIL PROTECTED]
Cc: freebsd-stable@freebsd.org
Subject: Re: 5.3-stable doesn't ifconfig at startup
On Fri, 11 Feb 2005 02:00:39 -0500 (EST)
Kenneth W Cochran [EMAIL PROTECTED] wrote:
Hello -stable:
Any idea(s) why (my) 5.3-stable (as of 9 February) isn't
configuring the network interface or setting up the default route?
I installed 5.3-release from CD and things worked fine.
Then I updated the system sources (via cvsup) to RELENG_5 and
went through {build,install}world/mergemaster/reboot as outlined
[ .. ]
mergemaster pilot error ?
If you didn't changed something in them I'd suggest wiping /etc/rc.d/*
and /etc/defaults/* and do a mergermaster -i
First thing I thought of; both mergemaster -p and
mergemaster without arguments are fine; all its targets
updated accordingly.
But set by hand it works ?
I've did the same thing 3 weeks ago and rebuild the machine 3 times w/o
problems
--
IOnut
Unregistered ;) FreeBSD user
Yes, setting by hand works, e.g. ifconfig route add default ...
Netcard is Intel fxp type. So far, UTSL is rather, umm, vague...
-kc
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
fixed: 5.3-stable doesn't ifconfig at startup
Date: Fri, 11 Feb 2005 09:51:00 -0600
From: Scot Hetzel [EMAIL PROTECTED]
To: Kenneth W Cochran [EMAIL PROTECTED]
Subject: Re: 5.3-stable doesn't ifconfig at startup
Cc: freebsd-stable@freebsd.org
On Fri, 11 Feb 2005 08:58:02 -0500 (EST), Kenneth W Cochran
Hello -stable:
Any idea(s) why (my) 5.3-stable (as of 9 February) isn't
configuring the network interface or setting up the default route?
I installed 5.3-release from CD and things worked fine.
Then I updated the system sources (via cvsup) to RELENG_5 and
went through {build,install}world/mergemaster/reboot as outlined
what does your /etc/rc.conf look like?
/etc/rc.conf did not change between OS versions.
See below... Thanks :)
-kc
Original message:
Date: Fri, 11 Feb 2005 02:00:39 -0500 (EST)
From: Kenneth W Cochran [EMAIL PROTECTED]
To: freebsd-stable@freebsd.org
Subject: 5.3-stable doesn't ifconfig at startup
Hello -stable:
Any idea(s) why (my) 5.3-stable (as of 9 February) isn't
configuring the network interface or setting up the default route?
I installed 5.3-release from CD and things worked fine.
Then I updated the system sources (via cvsup) to RELENG_5 and
went through {build,install}world/mergemaster/reboot as outlined
in /usr/src/UPDATING and now I get no network interfaces
configured no default route set. I've tracked RELENG_4 for
years with nothing like this ever happening. Kernel has not been
reconfigured (yet), it's still GENERIC, albeit RELENG_5 now.
In looking through the rc scripts, it appears that network
interface(s) are being renamed but I see no references to this
in, say, UPDATING or errara or other documentation. Any ideas?
Pointers to documentation are welcome. :)
Ok, found the problem - turned out to be the *filemode(s)* of the
updated bits in /etc/rc.d/*. The netif script was filemode
644, rendering it not executable. Changing its filemode to
555 (and that of other updated scripts as well), as per
installation, fixed it.
Background: Upon installation, with only a couple of exceptions
(oversights?) all the files in /etc/rc.d are root:wheel and mode
555 (-r-xr-xr-x). Rather than using mergemaster to replace the
updated files/scripts (reason: I want to preserve cvsup dates and
previous versions of /etc-pieces and mergemaster timestamps the
files as of mergemaster-time), I merely copied (-p) the updated
files from /usr/src/rc.d/*. It appears that mergemaster does,
however, fix the owner:group:filemode of whatever it installs.
This points up another question or two:
How can I make sure that I have correct/proper owner:group:mode
within the system? It looks to me like install{world,kernel}
fix them but what of /etc? In other words, how can I audit the
permissions in the system in general and /etc in particular?
Can mergemaster preserve the file modification time(s) of what it
installs (from /usr/src/*)?
Documentation pointers welcome. :)
Thanks to all,
-kc
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
5.3-stable doesn't ifconfig at startup
Hello -stable:
Any idea(s) why (my) 5.3-stable (as of 9 February) isn't
configuring the network interface or setting up the default route?
I installed 5.3-release from CD and things worked fine.
Then I updated the system sources (via cvsup) to RELENG_5 and
went through {build,install}world/mergemaster/reboot as outlined
in /usr/src/UPDATING and now I get no network interfaces
configured no default route set. I've tracked RELENG_4 for
years with nothing like this ever happening. Kernel has not been
reconfigured (yet), it's still GENERIC, albeit RELENG_5 now.
In looking through the rc scripts, it appears that network
interface(s) are being renamed but I see no references to this
in, say, UPDATING or errara or other documentation. Any ideas?
Pointers to documentation are welcome. :)
Thanks,
-kc
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
4.10-BETA named (not) starting
Hello -stable: I just updated to -stable as of 2004/04/14 and named is not starting at bootup. From /var/log/messages: Apr 15 07:38:14 console.info localhost /kernel: can't open '/etc/namedb/named.conf' But, if I become root type ndc start, named starts seems to run as before. Any idea(s) what's happening here and/or how to fix? Thanks, -kc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DNS problem
Date: Sun, 1 Feb 2004 12:36:27 -0800 (PST) From: Don Lewis [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: DNS problem On 1 Feb, Kovács Péter wrote: Hello, Which server in your organization is acting as a DNS server? The Windows... If you only have one network card in your FreeBSD box... Yes, I only have one. This could be why you only see this kind of traffic with one IP address. Is there a way to fix this? Something on your FreeBSD box is sending DNS queries to your Windows box and is timing out its query and closing the socket it used to send the query before the Windows box returns its response. Because you have net.inet.udp.log_in_vain enabled, your FreeBSD box logs the arrival of the DNS response packet because there is not a UDP socket listening on the port that the response is being returned to. About all you can do to turn off these messages is to turn off udp.log_in_vain. As a substitute you could log unexpected packets using one of the firewall packages on FreeBSD, which would allow you to ignore packets coming from port 53 on your DNS server. I get similar messages, viz: Feb 2 09:16:59 kern.info localhost /kernel: Connection attempt to UDP 192.168.0.1:3826 from 192.168.0.1:53 Feb 2 09:17:39 kern.info localhost /kernel: Connection attempt to UDP 192.168.0.1:3827 from 192.168.0.1:53 Feb 2 09:20:28 kern.info localhost /kernel: Connection attempt to UDP 192.168.0.1:3853 from 192.168.0.1:53 Feb 2 09:20:33 kern.info localhost /kernel: Connection attempt to UDP 192.168.0.1:3854 from 192.168.0.1:53 Feb 2 09:20:43 kern.info localhost /kernel: Connection attempt to UDP 192.168.0.1:3855 from 192.168.0.1:53 Feb 2 09:21:01 kern.info localhost /kernel: Connection attempt to UDP 192.168.0.1:3856 from 192.168.0.1:53 Sysctl log_in_vain is is set for both tcp udp. It has been like this for ages and so far I can find neither an explanation as to why, no a way to fix it (assuming it is some kind of breakage/misconfiguration). OS is 4.9-stable as of 15 January, 2004. There is indeed a Windows box at 192.168.0.2, but DNS is on the FreeBSD machine, configured as cache-only (supposedly; could be something not quite correct in that config...) There are 2 network interfaces and the syslog indicates (I think correctly) named listening on both of them when it starts. 192.168.0/24 is on an internal interface/network; the external interface gets its ip-address from the ISP via DHCP. What I'd like to do is 1. fix any errors/misconfigurations that might be causing those messages and 2. keep the cache-only nameserver, and have it run/query efficiently. Any ideas/suggestions/suggested reading? Thanks, -kc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DNS problem
To: Kenneth W Cochran [EMAIL PROTECTED] Cc: Don Lewis [EMAIL PROTECTED], [EMAIL PROTECTED] From: [EMAIL PROTECTED] Subject: Re: DNS problem Date: Tue, 03 Feb 2004 07:28:29 +1100 Date: Sun, 1 Feb 2004 12:36:27 -0800 (PST) From: Don Lewis [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: DNS problem On 1 Feb, Kovács Péter wrote: Hello, Which server in your organization is acting as a DNS server? The Windows... If you only have one network card in your FreeBSD box... Yes, I only have one. This could be why you only see this kind of traffic with one IP address. Is there a way to fix this? Something on your FreeBSD box is sending DNS queries to your Windows box and is timing out its query and closing the socket it used to send the query before the Windows box returns its response. Because you have net.inet.udp.log_in_vain enabled, your FreeBSD box logs the arrival of the DNS response packet because there is not a UDP socket listening on the port that the response is being returned to. About all you can do to turn off these messages is to turn off udp.log_in_vain. As a substitute you could log unexpected packets using one of the firewall packages on FreeBSD, which would allow you to ignore packets coming from port 53 on your DNS server. I get similar messages, viz: Feb 2 09:16:59 kern.info localhost /kernel: Connection attempt to UDP 192. 168.0.1:3826 from 192.168.0.1:53 Feb 2 09:17:39 kern.info localhost /kernel: Connection attempt to UDP 192. 168.0.1:3827 from 192.168.0.1:53 Feb 2 09:20:28 kern.info localhost /kernel: Connection attempt to UDP 192. 168.0.1:3853 from 192.168.0.1:53 Feb 2 09:20:33 kern.info localhost /kernel: Connection attempt to UDP 192. 168.0.1:3854 from 192.168.0.1:53 Feb 2 09:20:43 kern.info localhost /kernel: Connection attempt to UDP 192. 168.0.1:3855 from 192.168.0.1:53 Feb 2 09:21:01 kern.info localhost /kernel: Connection attempt to UDP 192. 168.0.1:3856 from 192.168.0.1:53 Sysctl log_in_vain is is set for both tcp udp. It has been like this for ages and so far I can find neither an explanation as to why, no a way to fix it (assuming it is some kind of breakage/misconfiguration). OS is 4.9-stable as of 15 January, 2004. So let me try to restate/rephrase what is going on... Your resolver asks the same question multiple times to multiple servers. It closes the socket after it gets the first answers. It is *normal* to receive answers from the other server after the first answer. My resolver makes some queries from some high port to port 53 of whatever nameserver(s) it is configured (explicitly or by default) to query. The answers come back from port 53 of that/those servers to that originating (high) port. As soon as it gets an answer, it closes that high port from which it was asking. This all happens via UDP? It is also *normal* to receive answers late if the nameserver cannot resolve the answer. In this case it sends SERVFAIL to say that it is giving up. Usually the client has timed-out and closed the socket before that has happened. So the logged messages I'm seeing are resulting from ports that were closed (well, actually no longer listening) following an answer to the original query. (?) In other words - originating query-port (high) got closed b/c the resolver got some answer, therefore there's no longer a listener on it, therefore the logged message(s). Correct? Is this configurable somehow? Sounds like it might not be, as it appears to be a *resolver* behavior rather than that of the nameserver. Where might I find this documented? Many thanks, -kc There is indeed a Windows box at 192.168.0.2, but DNS is on the FreeBSD machine, configured as cache-only (supposedly; could be something not quite correct in that config...) There are 2 network interfaces and the syslog indicates (I think correctly) named listening on both of them when it starts. 192.168.0/24 is on an internal interface/network; the external interface gets its ip-address from the ISP via DHCP. What I'd like to do is 1. fix any errors/misconfigurations that might be causing those messages and 2. keep the cache-only nameserver, and have it run/query efficiently. Any ideas/suggestions/suggested reading? -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
problem with cvs-all@freebsd.org?
Just wondering; haven't seen any updates on the html version of the cvs-all list and the date-order seems, umm, strange. Well, I guess heads-up if nothing else... -kc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: XFree 4.3.0 / Xft font problems
Date: Tue, 18 Mar 2003 10:27:44 -0500 From: Jason Andresen [EMAIL PROTECTED] To: Kenneth W Cochran [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: XFree 4.3.0 / Xft font problems Kenneth W Cochran wrote: Regular xchat 1.8.11 and gaim 0.59.9 look fine. Mozilla built without Xft (-DWITHOUT_XFT) looks ok (menu bar looks good, as with other apps) but not great (displayed text looks ok but not very good). Mozilla uses whatever you have configured in the preferences panel as the font for the menubar IIRC. Try changing your font from serif to sans-serif. Additionally, you're probably having trouble with the antialiased small text. You might want to try creating a /usr/X11R6/etc/fonts/local.conf file with the following lines: !-- Fontconfig local overrides -- match target=pattern test qual=any name=size compare=less_eq double12/double /test edit name=antialias mode=assign boolfalse/bool /edit /match And see if that's any easier on your eyes. Where is that kind of thing documented? And how can I isolate these changes across OS/system maintenance/upgrades? Why does the default install look so bad? (Hmm, maybe don't answer that... ;) As installed, Mozilla-1.3b,1 fonts: (WITHOUT_XFT) Proportional: Serif 12 pixels Serif: adobe-avantgarde-iso8859-1 Sans-serif: (same) Cursive: (same) Fantasy: (same) Monospace: (same) 16 pixels As installed, Mozilla-1.3b,1 fonts: (default build, with Xft) Proportional: Serif 12 pixels Serif: Bitstream Charter Sans-serif: (same) Cursive: (same) Fantasy: (same) Monospace: (same) 16 pixels So where are the various font classes (for want of a better term) used? And how do I fix this stuff for (for examples) the Xft-enabled versions of other clients? Excerpts from XF86Config: (vidcard is Matrox G400 32mb) # This loads the Type1 and FreeType font modules Loadtype1 Loadspeedo Loadfreetype #Loadxtt # This loads the GLX module Load glx # This loads the DRI module Load dri # From XFree86 -configure #Load extmod Load record Load xtrap ... FontPath /usr/X11R6/lib/X11/fonts/local/ FontPath /usr/X11R6/lib/X11/fonts/misc/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath /usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath /usr/X11R6/lib/X11/fonts/Speedo/ FontPath /usr/X11R6/lib/X11/fonts/Type1/ #FontPath /usr/X11R6/lib/X11/fonts/TrueType/ #FontPath /usr/X11R6/lib/X11/fonts/freefont/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/ FontPath /usr/X11R6/lib/X11/fonts/100dpi/ FontPath /usr/X11R6/lib/X11/fonts/cyrillic/ FontPath /usr/X11R6/lib/X11/fonts/URW/ Is this of any help? Any config changes appropriate? X was configured thusly: 1. As root, XFree86 -configure 2. As root, xf86config - answer the questions write out XF86Config 3. Customize XF86Config: a. Carefully merge the XF86Config.new into XF86Config. b. Add URW fonts per requirements for some ports. c. other stuff as appropriate Is there a Better Way To Do This(tm)? ;) Would welcome faq/documentation pointers, both online printed. semi-rant Complexities/oddities such as this are, I think, part of what hinders public/PHB acceptance of Unix/Linux/*BSD/opensource and keeps in place certain monopolies. As a friend of mine says, you have to have a Decoder Ring to run this stuff. /semi-rant Please pardon my, umm, venting, I'm sure stuff like this will be fixed before long. ;) -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Opera 6.11 coredumping on exit
Hello -stable: Anyone else experiencing Opera 6.11.20021129 (from ports) coredumping on exit? 6.10 did it too, but IIRC it didn't start doing that until a cvsup/build/installworld in early November. My guess is that Opera is developed/released on a -release system(?) I guess I'm wondering whether it is an Opera bug, perhaps exposed by something in FreeBSD since 4.7-release, or something in FreeBSD itself. On exiting Opera, I get the following message: $ opera opera in free(): warning: junk pointer, too high to make sense Segmentation fault (core dumped) $ sh: turning off NDELAY mode Any ideas? (i.e. maybe a Better Idea to report it to Opera instead?) Thanks, -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Opera for FreeBSD
It coredumps on exit here. OS is 4.7-stable as of
today, 2002/11/01. Previous beta did the same thing,
but it seems that it didn't start coredumping until a
cvsup/{build,install}world a couple of weeks ago.
Other than the exit-coredump, it seems to run well.
Here's the exit-message:
opera in free(): warning: junk pointer, too high to make sense
Segmentation fault (core dumped)
$ sh: turning off NDELAY mode
Any ideas?
-kc
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
IPFW2 option in -stable kernel config
In reading the notes in the cvs-all stable lists regarding the IPFW2, it isn't clear (well to me :) how to properly specify the new code. As per the announcement(s), there is, of course, no explanation in LINT either. Are IPFIREWALL IPFW2 mutually exclusive? Does IPFW2 depend on specification of IPFIREWALL? Do options like IPDIVERT, IPFIREWALL_VERBOSE other knobs apply to IPFIREWALL as well? In looking over the kernel source(s), it appears that IPFW2 might trump IPFIREWALL therefore IPFIREWALL becomes a don't care if IPFW2 is specified. Is this correct? Thanks, -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
gtk12 glib12 port build failures in -stable
Hello -ports -stable:
I just cvsup'ed did a {build,install}world today (1 Aug).
I also updated ports-tree after having built newly updated
gettext, gtk12 glib12 refuse to build.
Here is the ending part of the gtk12 build: (glib12 is 1.2.10_7)
checking for glib-config... /usr/local/bin/glib12-config
checking for GLIB - version = 1.2.8... no
*** Could not run GLIB test program, checking why...
*** The test program failed to compile or link. See the file config.log for the
*** exact error that occured. This usually means GLIB was incorrectly installed
*** or that you have moved GLIB since it was installed. In the latter case, you
*** may want to edit the glib-config script: /usr/local/bin/glib12-config
configure: error:
*** GLIB 1.2.8 or better is required. The latest version of GLIB
*** is always available from ftp://ftp.gtk.org/.
=== Script configure failed unexpectedly.
Please report the problem to [EMAIL PROTECTED] [maintainer] and attach
the /usr/ports/x11-toolkits/gtk12/work/gtk+-1.2.10/config.log including
the output of the failure of your make command. Also, it might be a good
idea to provide an overview of all packages installed on your system
(e.g. an `ls /var/db/pkg`).
*** Error code 1
Stop in /usr/ports/x11-toolkits/gtk12.
--
Here is the end of the glib12 build:
checking for pthread.h... yes
checking for thread implementation... posix
checking for pthread_attr_init in -lpthread... no
checking for pthread_attr_init in -lpthreads... no
checking for pthread_attr_init in -lthread... no
checking for pthread_attr_init in -lc_r... no
checking for pthread_attr_init... no
checking for __d10_pthread_attr_init in -lthread... no
checking for __pthread_attr_init_system in -lpthread... no
configure: error: I can't find the libraries for the thread implementation
posix. Please choose another thread implementation or
provide information on your thread implementation.
You can also run 'configure --disable-threads'
to compile without thread support.
=== Script configure failed unexpectedly.
Please report the problem to [EMAIL PROTECTED] [maintainer] and attach
the /usr/ports/devel/glib12/work/glib-1.2.10/config.log including the
output of the failure of your make command. Also, it might be a good idea
to provide an overview of all packages installed on your system (e.g. an
`ls /var/db/pkg`).
*** Error code 1
Stop in /usr/ports/devel/glib12.
--
Ideas? Fixes? Workarounds?
Many thanks,
-kc
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
glib12 port build failure in -stable (update)
Could this be a side-effect of the 1.9.2.2 ver of uthread_dup2.c which was committed 1 August? (output from build-attempt of /usr/ports/devel/glib12): checking for pthread.h... yes checking for thread implementation... posix checking for pthread_attr_init in -lpthread... no checking for pthread_attr_init in -lpthreads... no checking for pthread_attr_init in -lthread... no checking for pthread_attr_init in -lc_r... no checking for pthread_attr_init... no checking for __d10_pthread_attr_init in -lthread... no checking for __pthread_attr_init_system in -lpthread... no configure: error: I can't find the libraries for the thread implementation posix. Please choose another thread implementation or provide information on your thread implementation. You can also run 'configure --disable-threads' to compile without thread support. === Script configure failed unexpectedly. Please report the problem to [EMAIL PROTECTED] [maintainer] and attach the /usr/ports/devel/glib12/work/glib-1.2.10/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 Stop in /usr/ports/devel/glib12. -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
4.6-RC, xchat 1.8.8_2 segfaulting
Hello -stable:
Is anyone here having xchat (v 1.8.8_2, from ports) segfaulting
in -stable? I'm getting a null pointer dereference.
I'm seeing this on a system since cvsup/{build,install}world
of 1 May. Previous to that everything was (well, seemed)
fine. It now runs 4.6-RC, as of afternoon local time
Friday, 17 May xchat still crashes; best I can tell,
everything else is working fine (at least not segfaulting).
xchat segfaults repeatably while connecting to servers running:
bahamut, with services
unreal ircd, with services
I can't determine versions; the connection doesn't make it that far.
It runs fine (so far, repeatably) connecting with servers running:
plain vanilla ircd v 2.9.5 (?) without services
(I think this ircd is from ports of yore...)
cyclone0.3.1.1 with services I think, b/c nickserv answers
Could anything have changed in -stable (or perhaps -ports,
i.e. dependencies) between 24 April 1 May that might be
causing this and/or exposing some other glitch?
Many thanks,
-kc
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
xchat-1.8.8 segfaulting on -stable
Hello: Xchat has started segfaulting coredumping here. Until the past few days, xchat has been trouble-free. OS: 4.5-stable as of 2002/05/01 just before the 4.6-prerelease commit Ports tree: updated 2002/05/05 all dependencies/versions up-to-date, except as noted below xchat is 1.8.8 XFree86 is still 4.1.0_10 Seems the segfaulting didn't start until after 2002/05/01 (when I updated the base OS), otherwise xchat has worked fine. The segfault appears to be happening when I try to connect to an IRC server. Any idea(s) as to what's happening how to repair? Thanks, -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Status, USB/Olympus E-10
(cc'ed to -scsi) Hello, A couple of committers I were working last July (2001) with support for the Olympus E-10 digital camera in FreeBSD. This is a USB device. I just saw some commits in cam/scsi_da for Nikon I'm wondering what the situation is wrt Olympus? The problem I was having was that even though FreeBSD (then 4.3-stable) would recognise the camera, if I tried to mount() it the os would reboot(!) :(( No panic, no nothing, just a hard freeze rebooting. Obviously, this is Very Very Bad. I've seen Linux (2.4-something) working with this just fine. Linux sees this camera as a SCSI device with a MS-DOS filesystem. I'm now running a 4.5-PRERELEASE wonder if, assuming this hasn't been fixed since 4.3, that this might be fixed in 4.5? At least if the camera isn't/can't be supported in time (for 4.5), is there some way we could at least protect the system from the rebooting? I can probably help test. I'm thinking of filing a PR, but seek advice before doing that. Many thanks, -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Default user directory (adduser) filemode
Hello -stable: I notice that when I add a user to FreeBSD, either from adduser or from /stand/sysinstall -- UserAdd(sp?), the default filemode of the user's home directory is 755. So far, I can't find (something like) a config-option for this (i.e., in /etc/adduser.conf). Is this a bug or a feature(tm)? :) OS is -stable (RELENG_4), as of 8 September 2001. Thanks, -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Default user directory (adduser) filemode
Sounds reasonable... But sysinstall -- UserAdd doesn't use the adduser Perl script, but the pw command. Just MHO, but I think the defaults are too loose, not well-documented, and not easily auditable. Should I file a PR, maybe? CC'ing to -security... -kc Date: Thu, 13 Sep 2001 09:56:22 -0400 From: Chip Norkus [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Default user directory (adduser) filemode On Thu Sep 13, 2001; 06:42AM -0700 Mike Harding used 1.4K bytes of bandwidth to send the following: 'adduser' is a perl script, search it for '755' and you will find where the permissions are set, it's trivial to change in the source, although logically this could be a configuration parameter. The script is in /usr/sbin/adduser. Additionally, if you change your umask, mkdir(2) (which is what is used by adduser) will be restricted. So, if you want files created to be completely restricted from group/other access, you might do: # (umask 077;adduser) A more useful value (especially if you are supporting something like 'public_html' in user directories) would be a umask of 066, or maybe even 026. For more info see `man 2 umask` and `man chmod`. - Mike H. Date: Thu, 13 Sep 2001 09:17:51 -0400 (EDT) From: Kenneth W Cochran [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] List-ID: freebsd-stable.FreeBSD.ORG List-Archive: http://docs.freebsd.org/mail/ (Web Archive) List-Help: mailto:[EMAIL PROTECTED]?subject=help (List Instructions) List-Subscribe: mailto:[EMAIL PROTECTED]?subject=subscribe%20freebsd-stable List-Unsubscribe: mailto:[EMAIL PROTECTED]?subject=unsubscribe%20freebsd-stable X-Loop: FreeBSD.ORG Precedence: bulk Hello -stable: I notice that when I add a user to FreeBSD, either from adduser or from /stand/sysinstall -- UserAdd(sp?), the default filemode of the user's home directory is 755. So far, I can't find (something like) a config-option for this (i.e., in /etc/adduser.conf). Is this a bug or a feature(tm)? :) OS is -stable (RELENG_4), as of 8 September 2001. Thanks, -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: NAT with 1 public interface still not working
Hey, thanks... ( for your previous message a couple of days ago, too, but I've been having email troubles.) But it still doesn't work, i.e. no change from previous behavior. As a test/example, traceroute from the private machine to anywhere outside stops at the gateway machine. This *has* to work somehow - I got this to work a few months ago for someone using Windows 98 its ICS (Internet Connection Sharing). This is obviously some kind of operator error ( truth-be-known, probably yet another shortcoming of Windows, security-wise), but I can't find the information I need to make this work. :( For example, which IP? What change(s) do I need to make to my ipfw fules and/or natd to fix this? Or maybe I should use ipnat? -kc From: fallous [EMAIL PROTECTED] To: Kenneth W Cochran [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: NAT with 1 public interface still not working Date: Thu, 6 Sep 2001 08:20:59 -0700 divert 8668 ip from any to any via IP instead of interface name should work assuming that incoming on fxp0 has the same destination IP as what your outgoing packets use as source. On Thursday 06 September 2001 07:42 am, Kenneth W Cochran wrote: Hello: How do I properly set up NAT on a (gateway) system that transmits and receives on different interfaces? Briefly - Machine A receives on fxp0 transmits on ppp0. I'd like to use a 2nd Ethernet on Machine A (fxp1) for the NATed/masqueraded network. Scenario: Machine A: - Running RELENG_4 as of 2001/09/01; tracking -stable roughly weekly (thus one reason I'm asking on -stable :). - Connected to a hybrid aka 1-way cable-modem, - Receives via cablemodem/Ethernet (fxp0, config'ed as 10.0.0.11/24) - Transmits/outgoing via analog dial-modem ppp(d). - Real ip-address is established by (kernel) pppd (ppp0, *not* tun0), and is officially dynamic, even though it always (at least right now) gets the same ip-address. - Runs cache-only nameserver. - Has been running in this manner for about 1.5 years. - (recently) Has 2nd NIC (fxp1), connected to hub for private network. Machine B: - Has private ip-address on its fxp0. - Connected via hub to 2nd NIC (fxp1) on Machine A. I've followed the instructions from the Handbook, Section 18.10, Network Address Translation with regard to kernel rc.conf configuration, etc. Here is the output from ipfw list on Machine A: 00050 divert 8668 ip from any to any via fxp0 00100 allow ip from any to any via lo0 00200 deny ip from any to 127.0.0.0/8 00300 deny ip from 127.0.0.0/8 to any 65000 allow ip from any to any 65535 allow ip from any to any Machines A B can talk to each other; I can ping ssh from/to either one, DNS works on both machines. However, while Machine A communicates outside (with the Internet) as usual, Machine B cannot. I'm beginning to wonder if FreeBSD can even *do* this, as I can't find anything in the natd manpage (or experimentation) that indicates natd can support 1 interface, and the manpages are silent about use of kernel ppp for this. (?) :-/ I'm thinking something needs to be tweaked in the ipfw and/or natd-config(s). Suggestions? Also, where would be the best place(s) to put these customizations (for example, so as to not be any more disruptive than necessary to the base-OS configs)? Does it matter whether the ppp(d)-link is up before/after ipfw/natd configuration? Of course, FAQ/-doc/readme pointers are quite welcome. :) Please cc replies to me. Many thanks, -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: New kernel option CPU_ENABLE_SSE
To: Kris Kennaway [EMAIL PROTECTED] cc: Kenneth W Cochran [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: New kernel option CPU_ENABLE_SSE --R+My9LyyhiUvIEro Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Aug 16, 2001 at 04:20:35PM -0400, Kenneth W Cochran wrote: Assuming CPU_ENABLE_SSE is a Good Thing, why not make it default with the cpu I686_CPU kernel config directive (similar to F00F_HACK auto-include with I586_CPU)? Because not all i686'es support SSE. So detect it automatically based on the CPU feature bits. Needing a kernel compile option for this is unforgivably lame. If you want to be able to disable it, use a tunable. Perhaps; the gist I get is that the compile option is for some field-testing. Maybe similarly appropriate would be something similar to NO_F00F_HACK; for example, CPU_DISABLE_SSE or CPU_NO_ENABLE_SSE (?). Just thinking out loud; the current method is ok with me. :) -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
New kernel option CPU_ENABLE_SSE
Hello -stable:
A new kernel config option CPU_ENABLE_SSE has appeared. :)
From recent cvsup of 15 August:
Edit src/sys/i386/conf/LINT
Add delta 1.749.2.77 2001.08.15.01.23.49 peter
So far I can't find any documentation about this feature
besides the brief comment in LINT, the release-notes mention
and the cvs log message (other pointers appreciated).
Questions:
Why might someone want to include this option (or not)?
Does this option entail a cost?
Assuming CPU_ENABLE_SSE is a Good Thing, why not make it
default with the cpu I686_CPU kernel config directive
(similar to F00F_HACK auto-include with I586_CPU)?
I guess my question boils down as why not support it
automa{t,g}ically? :) Either way is ok with me; I'm just
looking for an explanation and/or documentation.
Thanks,
-kc
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
Tracking -docs like -stable
Hello -stable -docs: I'm trying to "track" documentation similarly to -stable. I can cvsup the "docs-supfile" Just Fine, but what needs to be done afterward? After cvsup of doc-all, in what directory should I be when making/building? What are the relevant make-targets for documentation where can I find them? How do I properly omit building the .pdf and .ps versions? I can't find anything in The Books (Lehey v3 the Handbook) the docproj Web-site seems targeted toward documentation "authors" not toward documentation "trackers." The textproc/docproj port is installed. Naturally, faq/doc/book pointers most welcome. :) Many thanks, -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Mozilla build failure, 4-stable
Hello -stable -ports: I'm having trouble building mozilla. OS is 4-stable as of 2000/02/09. Ports tree is as of 2000/02/09. Due to disk space limitations, I'm using a "cleaned out" /usr/obj (its "own" filesystem) as the workspace; command (in c-shell) is "make WRKDIRPREFIX=/usr/obj | tee make.log" Last few lines from make.log are as folows: === Building for mozilla-0.7_1,1 /usr/ports/www/mozilla/Makefile:74: *** missing separator. Stop. *** Error code 2 Stop in /usr/ports/www/mozilla. *** Error code 1 Stop in /usr/ports/www/mozilla. *** Error code 1 Stop in /usr/ports/www/mozilla. -- Previous port-dependencies are ok. Any ideas as to problem(s)/fix(es)? Thanks, -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: XFree86-4.0.2 problems, 4.2-stable
Date: Wed, 31 Jan 2001 10:15:04 +0100 (CET) From: =?iso-8859-1?Q?=D8ystein_Skundberg?= [EMAIL PROTECTED] To: Kenneth W Cochran [EMAIL PROTECTED] cc: [EMAIL PROTECTED] Subject: Re: XFree86-4.0.2 problems, 4.2-stable On Tue, 30 Jan 2001, Kenneth W Cochran wrote: The recent Security Advisory (FreeBSD-SA-01:07) mentions that the BSD/OS ELF binary of Netscape works; where is that available? It is not in ports/packages. (And do things such as license terms allow its use on FreeBSD?) eskimo:/usr/ports/www$ ls bsdi* bsdi-netscape47-communicator: MakefileREADME.html files pkg-comment pkg-descr pkg-message pkg-plist bsdi-netscape47-navigator: MakefileREADME.html pkg-comment pkg-descr pkg-plist I suppose this is the one you mean? Ahhh! Thanks... Oops... The Makefile lists it as FORBIDDEN, due to a buffer-overflow, fixed in version 4.76. The latest BSDI-Netscape appears to be 4.75. :( I guess I'm back to my "original 2 problems..." 1. Fvwm95-2.0.43a Start/popup menu not working 2. Netscape Communicator 4.76 keymapping. The Big Change That Broke These Things was going from XFree86-3.3.6 to 4.0.2. Given the interactions of the various components involved that (IMO) this is more an "application" problem than a "system" problem, can someone suggest a Better Place To Ask besides FreeBSD-stable? Thanks, -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.2-stable, ports/packages in XF86 4.0.2
Date: Sat, 30 Dec 2000 21:15:22 -0600
From: Bruce Burden [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: 4.2-stable, ports/packages in XF86 4.0.2
2. The Netscape Communicator 4.76 package (from CD 1 of
the 4.2 set) will not install, complaining about the lack
of a.out X libraries. The "previous" installation of
Netscape would not start, leaving a log message of not
being able to find ld.so.6 (iirc).
I find that I need to add:
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH_AOUT}
to get Netscape to install and run. Since Netscape is still in
the a.out time frame, I can see why it doesn't look for
LD_LIBRARY_PATH_AOUT. Still, an ELF format Netscape would be nice...
Well, things work ok (for Netscape :) with XFree 3.3.6...
Both installing running. Also, XFree86 4.0.2 appears to
have/install a.out libraries... (?)
But this still sounds like Yet Another Reason to ditch Netwcape...
/etc/make.conf has XFREE86_VERSION=4 defined.
This simply causes /usr/ports/x11/XFree86-4 directory and
dependencies to be cleaned. Otherwise, /usr/ports/x11/XFree86
(currently 3.3.6) is being cleaned.
Ideas? These start looking like port/package problems... (?)
Did you install XFree86-4.0.2 from the package or the
ports collection? I get compile errors with pthread and Xthreads
when I attempt to install in from the ports collection, which
makes it rather difficult to install...
I installed from the precompiled binaries from xfree86.org.
Alas, I've so far found almost *no* FreeBSD documentation
wrt XFree86-4... :-/
-kc
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: 4.2-b buildworld end, sendmail.cf, kernel modules
From [EMAIL PROTECTED] Thu Nov 2 12:26:46 2000 Date: Thu, 2 Nov 2000 09:25:33 -0800 (PST) From: Gregory Neil Shapiro [EMAIL PROTECTED] To: Kenneth W Cochran [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: 4.2-b buildworld end, sendmail.cf, kernel modules kwc === etc kwc === etc/sendmail kwc rm -f freebsd.cf kwc (cd /usr/src/etc/sendmail m4 -D_CF_DIR_=/usr/src/etc/sendmail/../../contrib/sendmail/cf/ /usr/src/etc/sendmail/../../contrib/sendmail/cf/m4/cf.m4 freebsd.mc) freebsd.cf kwc chmod 444 freebsd.cf kwc "After:" kwc === etc kwc === etc/sendmail kwc What is (and/or was) going on here (sendmail-config building)? Are you sure you didn't have freebsd.cf in the obj directory from an earlier build? Not exactly, I'm afraid; I just noticed that "stanza" at the end of my buildworld log. Is this As Per Design or did somebody goof? The "before" output is from the 29th ( before) the "after" output is from the night of Nov 1. My guess is that "freebsd.cf" is something that "used to" exist, but is now deprecated, but I'd like to hear something (more-or-lese) "official." :) I can't find anything in any documentation of in the cvs list archive. -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: breakage with two ed network devices
From [EMAIL PROTECTED] Fri Oct 6 13:04:01 2000 To: Kenneth W Cochran [EMAIL PROTECTED] Subject: Re: breakage with two ed network devices Cc: John Reynolds~ [EMAIL PROTECTED], [EMAIL PROTECTED] Date: Fri, 06 Oct 2000 10:59:57 -0600 From: Warner Losh [EMAIL PROTECTED] : Given THAT information does anybody have any further clues? : Again, this machine is an Abit BP6, two Linksys Ether16 ISA : NICs. Kernel config for them is: : : device ed0 at isa? port 0x2c0 irq 15 iomem 0xd8000 : : Can this card (ed0) go to a different IRQ? Is that IRQ : disabled/reassigned (from PCI) in the BIOS/setup? Maybe that's where we should look. Does the ata probe for the slave somehow fail to release irq 15? The hardware config is fine (I've been over it in private email sevearl times). Ah, ok... :) : device ed1 at isa? port 0x340 irq 9 iomem 0xd8000 : : I might want to "move" this one, too; IRQ 9 is the "shared" : one it has always "frightened" me some... :) IRQ 9 is fine. Nothing wrong with it. It isn't shared at all. It used to be irq 2, but that's now used for chaining. That's the word I was looking for... :) Warner Thanks, -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: breakage with two ed network devices
From [EMAIL PROTECTED] Fri Oct 6 12:39:56 2000 From: John Reynolds~ [EMAIL PROTECTED] Date: Fri, 6 Oct 2000 09:35:51 -0700 (MST) To: Kenneth W Cochran [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: breakage with two ed network devices [ On Friday, October 6, Kenneth W Cochran wrote: ] Please pardon my "jumping in" and/or ignorance... ed0 living on an IRQ that is "reserved" (somehow) for one of the ATA "channels?" (ie. 14 and/or 15?) H. Yeah, I've got ed0 living on IRQ15. However, this h/w combo has been running since 3.3 (including 4.0-4.1-RELEASE). I wonder if its "previous" running/probing might have been a "glitch" (not as severe as a "bug" :) with prior drivers and that now, this "glitch" is being "exposed" by the "new" stuff(?) Hmmm... I might "question" an ATA-probe "there..." (?) Can this card (ed0) go to a different IRQ? Is that IRQ disabled/reassigned (from PCI) in the BIOS/setup? No, it's hardwired in the card. I read on the archives when I bought it to disable the PnP stuff on the card because it wouldn't work without it. So, I assigned it IRQs manually through their stupid little DOG program. 15 and 9 were the only ones their setup program could find that weren't "conflicts" with something else. I can certainly try to move ed0 onto a different IRQ. Maybe remove something change the IRQ just for testing? Is IRQ 15 BIOS-disabled (therefore making it available for things like ISA cards). Might be useful datapoints... I might want to "move" this one, too; IRQ 9 is the "shared" one it has always "frightened" me some... :) (Brain-cobweb-digging) I also notice that that the "iomem" is the same; shouldn't those be different segments? Probably so. Any suggestions for the second segment's starting position? LINT says nothing about it. Hmmm... These cards appear to be "shared-memory" cards. 1. IIRC (deep cobwebs now :), shared memory should not (cannot?) be cached, thus the possible need to "enable" the "memory hole" at 15M (in BIOS setup). IIRC (again :) this makes a 1mb non-cacheable "region" starting at 15M. 2. We would need to know the "shared memory segment size" of the cards how to set their (starting) addresses (any card -doc?); (conceivably) these would be values for "iomem" in your kernel-config. I couldn't find anything about "iomem" either, but that would be my guess. Hopefully Someone Who Knows will answer here ( maybe document that parameter? :) (I see Warner replying... ;) Hope I was at least slightly helpful... yeah, it was at least enlightening to see that IRQ14/IRQ15 are "meant" for ATA. That certainly does look like a smoking gun. However, I bring up the canonical fact that "it worked before this commit" As I mentioned above, its "working before" might have been a "glitch" (or maybe a "boo-boo" :). But I'd think that would be "cleared" if you "turn off" IRQ 15 in your BIOS. Fwiw, I run 4.1.1-s on a box so configured, IRQ 15 gets used "elsewhere" (the (PCI) NIC at this time). Hopefully I'll have time over the weekend to futz with the IRQs on these cards. Maybe I'll just ditch the damn things and go get two PCI NICs ... who knows ... I believe PCI NICs would be The Cure... My experience with (especially PnP) ISA cards on modern PCI systems leads me to conclude that (ISA/PnP) cards are Truly Evil(tm)... Thanks, -Jr I'm curious as to how it turns out... -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Parallel port in kernel config, lpt(4)
Hmmm... Ok... Why? ( why not the others?) What criteria can (should?) I use to determine whether I should use Interrupt-driven, BIOS, or polled-mode? -kc From [EMAIL PROTECTED] Tue Feb 15 01:52:20 2000 Date: Tue, 15 Feb 2000 17:50:26 +1100 Subject: Re: Parallel port in kernel config, lpt(4) Hi Kenneth, I use polled mode for printers... Eddie Kenneth W Cochran wrote: Hi again... This might be more appropriate for -questions, but this also appears to me to be related to this discussion-thread... The lpt(4) manpage describes interrupt-driven, BIOS-probed, polled ports. Under which circumstances might I want to use these various selections? IOW, how do I choose among these? Naturally, FAQ, book, doc-pointers are most welcome... Thanks, -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: HEADS UP!
From [EMAIL PROTECTED] Sat Aug 28 11:02:50 1999 Date: Sat, 28 Aug 1999 07:59:12 -0700 (PDT) From: "Brian F. Feldman" [EMAIL PROTECTED] Subject: HEADS UP! Within the next day, to be in the tree in time for the feature freeze, most of my changes to IPFW in 4.0 will be committed to 3.2. [...] __FreeBSD_version is going to be bumped up to 320002, and you'll probably also want to update your pidentd port afterwards (greatly simplified Both the ftp archive and the CD-ports-versions of pidentd are 2.8.5. Do we need to fetch something else or is this just a reinstall/recompile? [...] At the very least, please make sure to make a new kernel and modules, and make includes before recompiling/reinstalling src/sbin/ipfw/. Doesn't "make [build]world" also do a "make includes?" (I think so, but just "trying to make sure..." :) -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Kernel ppp (pppd) version 2.3.5 -- 2.3.8
What is the "status" of pppd more recent than 2.3.5 (2.3.8, for example) making it into -STABLE (RELENG_3)? Not a show-stopper, but I'm getting a strange "received bad configure-nak/rej" (at LOG_ERR level while trying to negotiate CCP) every time I connect. I do not get this behavior under Linux (Slackware 4.0/kernel 2.2.10/pppd-2.3.7). I don't recall getting it under Linux with pppd 2.3.5, though, either... IIRC the Linux version "properly" rejects the CCP negotiation it doesn't like... :) According to the pppd-2.3.8 sources, they have updated it for FreeBSD 3.0. I suppose I could install it "manually" but I'm not (yet) keen on messing with the source tree (ie. I don't want to mess-up the cvsup procedure). Is this worth my filing a pr? Thanks, -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
make world/buildworld failures sig11 AMI mainboard
Hello... I continue to get failures and/or coredumps while attempting "make world" or "make buildworld" on a system installed from the 3.2 CDs cvsup'ed to RELENG_3. These occur at seemingly random times/places in the process. I've tried it about 2 dozen times now, with no success. CVSUP'ing went fine. (I kept the log.) I believe I could almost quote the gcc-sig11 faq chapter verse... :/ Kernel building seems to work ok, but sometimes it, too, bombs out. I've had this problem with Linux, too, but not lately. (Slackware 4.0 with kernel 2.2.10 previous...) I think I may have eliminated RAM as the problem, as I've tried varying configurations amounts continue to have the problem. (Interesting to see how it works on a RAM-constrained system...) System hardware is as follows: American Megatrends (AMI) Atlas PCI-II mainboard (Series 727) (uses SiS 55xx-series chipset, I think... 5511?) Pentium 133 (P54C) 32mb ram (with parity) Number 9 Motion 771 2mb PCI video (S3-968) DPT PCI SCSI HBA (I forget the model #) with 4mb ecc cache. Seagate ST34573LW in SE mode Seagate ST32550W Plextor PX-32CS SCSI CD-ROM with 1.02 firmware There appears to be nothing in the BIOS setup relating to memory waitstates, etc.; I've tried changing the memory "speed" with no change in results... FBSD has rebooted my system a couple of times, too, I can't so far trace it... I don't recall Linux ever having done that. I've run Linux for a few years now various other *ix before that. I've also run BSDI more recently getting more "serious" with FBSD. System board manufacturer is no help. Have I any options besides replacing this mainboard? -kc To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
