Re: The Matrix screensaver, v.0.2
On Fri, 20 Aug 1999, Andrzej Bialecki wrote: c'mon, you didn't expect me to put an intro scene from the movie, did you? Yeah, that's something - MPEG screensaver... only a few GB. I need to think about it. I wonder where in phk's rules for binary files in the tree that would fall. Just make sure to uuencode the mpeg first. : -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: if_de.c breakage ?
On Sat, 21 Aug 1999, Mike Smith wrote: Argh! I knew that taking it out of sys/systm.h was a bad idea. 8( I committed the fix for this, FYI, after it tripped someone up on IRC. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: The Matrix screensaver, v.0.2
On 27 Aug 1999, Ville-Pertti Keinonen wrote: Of course this is getting off topic, or have there been any FreeBSD-current related homicides that I haven't heard about? ;--) Have there even been any actual trials directly related to FreeBSD? There was a signup sheet going around at the last 'Brucified Anonymous' meeting, but I guess that never materialized. :- -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: umount problem
On Sun, 5 Sep 1999, Janick Taillandier wrote: With a very recent kernel (less than a day), when I halt my Dell laptop, I get the following message: syncing disks... 4 done umount of /users failed (19) umount of /usr failed (19) umount of / failed (19) The operating system has halted. Please press any key to reboot. I get the _exact_ same error (well, mine is /var /usr and /). No softupdates. I have a Dell Latitude that can be abused to find out the cause of this. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Automating filesystem check at boot time
On Thu, 23 Sep 1999, Rodney W. Grimes wrote: You need to find and fix what ever it is that is not dieing when being told to die. Your work around is a bandaid that only hides the real problem, which is probably a bug some place in something. amd and NFS are good first conidates. Just what process does it complain that it is unable to kill, or does it just say could not kill? Vinum is usually the culprit for me, though I haven't built a world on most of these machines for a while, so this may be fixed. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS UP: sigset_t changes committed
On Thu, 30 Sep 1999, Marcel Moolenaar wrote: The upgrading from -stable to -current is currently being tested by Bill Fumerola. I can imagine that some might be broken in that case. This I will attempt to fix, then... As others have mentioned 3.3-STABLE right now cannot build 4.0-CURRENT kernels. Without the 4.0-CURRENT kernel, I can't build the 4.0 world to build the 4.0 kernel, and so on. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: my make world is broken !
On Thu, 30 Sep 1999, Juan Amado Becerril Castillo wrote: Suggestions ??? Not mail the list 3 f'ing times, to start. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: kernel broken? (pcm)
On Tue, 12 Oct 1999 [EMAIL PROTECTED] wrote: We have enough breakages with the _documented_ kernel options that we don't need to go hunting down oddities. : Does it mean that I throw away my PR with patches to the 'newpcm' files which add 'abs' definition and therefore make it possible to make kernel with makeoptions CONF_CFLAGS=-fno-builtin ? P.S. It seems to me that this option (or its absent) can severely influence kernel run time efficience (not in the 'abs' case, of course ;-). No. I was merely joking around. We welcome your patches. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ipfilter no longer in -CURRENT, whats the direction? (off toipfw?)
On Wed, 13 Oct 1999, Thomas Stromberg wrote: So my question is, what's the direction we're taking here? The author was given commit privledges to maintain this in the tree, obviously this was not done. Peter encouraged a KLD port, and I hope someone steps up and makes one. Others have eluded to upgrading it, but I never see those imports. It's a shame, but I'm glad that Peter cleared the bitrot. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: CMAP2 busy ?
On Thu, 28 Oct 1999, Khetan Gajjar wrote: #0 boot (howto=256) at ../../kern/kern_shutdown.c:280 280 dumppcb.pcb_cr3 = rcr3(); (kgdb) quit That's useless, every panic will look like that. Please see the handbook's instructions for good debugging tips. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/etc pccard.conf.sample
On Thu, 28 Oct 1999 [EMAIL PROTECTED] wrote: I have friends who happen to have Xircom multifunc cards (which _are_ CardBus) - would you guys like me to try and test them? I can get them long enough to test them out with the newconfig functionality. There are two versions of the XIRCOM realport multifunc cards, one that is Cardbus and one that isn't. I have the latter. if_xe is broken now, BTW. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Sv: copy-on-write optimized faults
On Sun, 31 Oct 1999, Louis A. Mamakos wrote: And my mine... I get zero COW optimized faults. THE E-MAIL EXPLICITLY SAID ONLY TO POST IF YOU HAVE MORE THEN 0 FAULTS I hope one day the people who don't read this list carefully miss something really important and it eats your system as a result. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: need patch review - NFS fixes for IP binding
On Thu, 11 Nov 1999, Joe Greco wrote:
And, despite those efforts, some of us went and bludgeoned the code into
a more trivial case ("bind to address nn.nn.nn.nn") for local use anyways.
Looks like the jail code will do something similar w/o source changes.
isc-dhcpd is even uglier in this regard.
--
- bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp -
- ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] -
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Make world this morning.
On Tue, 16 Nov 1999, Edwin Culp wrote: /usr/src/games/larn/monster.c: In function `hitm': /usr/src/games/larn/monster.c:856: syntax error before `amt' My first breakage of world, how neat. Thanks to Marcel for fixing what was the result of me having too many local copies of src/games on my laptop and checking one and committing another. Sorry -CURRENT folks.. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - PS. Sorry wpaul. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc 2.95.2
On Tue, 16 Nov 1999, Manfred Antar wrote: -DDEFAULT_CONFIG=\"/usr/ X11R6/lib/X11/rstart/config\" -DNOPUTENV server.c server.c: In function `putenv': server.c:790: argument `s' doesn't match prototype /usr/include/stdlib.h:117: prototype declaration *** Error code 1 (continuing) There are a _lot_ of things broken with this port. I've already marked it broken for the above reason. There is the /lib/cpp problem, the -lcrypto problem, it doesn't build the servers you tell it to. Ugh. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc 2.95.2
On Tue, 16 Nov 1999, Manfred Antar wrote: I think this is all related to the compiler update as I did a good build Friday or Saturday before the change. If it is, then some thing wierd is going on. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc 2.95.2
On Wed, 17 Nov 1999, Sheldon Hearn wrote: XFree86 makes it through the ports ``build'' target just fine. It breaks in ``install''. That's why I told Manfred I wasn't seeing the problem. I'd imagine the confusion is caused by the install target (improperly) building things. Yet another problem. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: installing onto ami mega raid.
[moving this off -current] On Sun, 21 Nov 1999, Alfred Perlstein wrote: Unfortunatly all the amr systems I have are now in production, I can not test a new install on them. The way I did manage to do the install was nfs mounting another machine's /, /usr, and /var then using dump/restore to init the system over a hand done disklabel on the amr (disklabel, not sysinstall). I'm sorry. Mike, I have a brand spanking new poweredge with PERC SC/2 give me (or Jeremy, CC'd) a call at the number in my .signature and we'll test whatever you want us to. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - PS. Jeremy, I'm talking about 'tiger'. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
powerpc tinderbox failure
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /home/tinderbox/ppc/obj/home/tinderbox/ppc/src/ppc/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- === bin/df cc1: warnings being treated as errors /home/tinderbox/ppc/src/bin/df/df.c: In function `prtstat': /home/tinderbox/ppc/src/bin/df/df.c:395: warning: passing arg 1 of `getbsize' from incompatible pointer type /home/tinderbox/ppc/src/bin/df/df.c: In function `update_maxwidths': /home/tinderbox/ppc/src/bin/df/df.c:448: warning: passing arg 1 of `getbsize' from incompatible pointer type *** Error code 1 Stop in /home/tinderbox/ppc/src/bin/df. *** Error code 1 Stop in /home/tinderbox/ppc/src/bin. *** Error code 1 Stop in /home/tinderbox/ppc/src. *** Error code 1 Stop in /home/tinderbox/ppc/src. *** Error code 1 Stop in /home/tinderbox/ppc/src. _ BootBox.Net - Your Home on the Internet http://www.bootbox.net Get an @bootbox.net webmail account - http://webmail.bootbox.net Get Dialup Internet Access for only $8.95/mo http://isp.bootbox.net Host Your Website For Free- http://webhosting.bootbox.net Put Your E-Commerce Business Online Virtually Free - http://bcommerce.bootbox.net _ Select your own custom email address for FREE! Get [EMAIL PROTECTED] w/No Ads, 6MB, POP more! http://www.everyone.net/selectmail?campaign=tag To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: installworld broken?
On Tue, Feb 29, 2000 at 03:53:06AM -0800, Alfred Perlstein wrote: install -C -c -o root -g wheel -m 644 ses/Makefile /usr/share/examples/ses/Makefile install -C -c -o root -g wheel -m 644 ses/getencstat/Makefile /usr/share/examples/ses/getencstat/Makefile install: mkstemp: /usr/share/examples/ses/getencstat/INS@2802 for /usr/share/examples/ses/getencstat/Makefile: No such file or directory You need rev 1.188 of BSD.usr.dist for the fix. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM (temporarily at Walnut Creek...) e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: when is 4.0 up for release ?
On Tue, Mar 07, 2000 at 05:52:07PM -0600, Dan Potter wrote: Has anyone thought about the problem I posted a few days ago (getcwd() breaks on unionfs in some conditions)? That seems like a pretty big problem to me... maybe not too many people use unionfs though, I don't know. If someone would give me a tip about where I should look in the kernel I would fix the problem myself but I am lost when you move past the specific fs driver. Someone else will probably point this out to you, but: BUGS THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK) AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. USE AT YOUR OWN RISK. BEWARE OF DOG. SLIPPERY WHEN WET. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: openssh question
On Mon, Mar 06, 2000 at 11:29:39AM +0100, Edwin Kremer wrote: " I do not recommend use of OpenSSH (or SSH1 generally, for that matter). There hasn't been much followup on this. Anybody here who cares to comment on this? What issues are relevant here and how bad is it? I'm sure he'd much prefer you use the version that puts money in his pocket. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: RC3
On Fri, Mar 10, 2000 at 09:26:12PM +0200, Daniel Mpolokoso wrote: I've managed to install RC3 without a hitch. The only problem I have is that I can't get the XFree86 setup to configure X to run on my graphics hardware: pci0: Intel 82810E (i810E GMCH) SVGA controller at 1.0 irq 11 My Compaq desktop using the Intel 810e motherboard. Any pointers? This requires a special module that only works with Linux, AFAIK. I have no idea if an effort to port it exists. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 5.0?
On Mon, Mar 13, 2000 at 03:57:18PM -0500, Forrest Aldrich wrote: I noted the tag on the kernel today was updated to 5.0-CURRENT... where is 4.0-RELEASE? Multiple choice test: (1) There's a secret consipiracy going around to keep the release of it really, really quiet. (2) The consipiracy is to keep _you_ from knowing about it. (3) It hasn't been released yet because the rough edges are still being taken care of and polished of. (4) The developers all dropped FreeBSD and are now running Redhat. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Why not gzip iso images?
On Fri, Mar 17, 2000 at 11:42:43AM -0800, Kris Kennaway wrote: No it doesn't. Download the binary installation files onto another machine, and burn a CD with them (you must have a mechanism to burn a CD if you were intending to burn an ISO image of one). Then use this CD as the media to get the distribution bits from. If our intent was to make installation a living hell, then yes this an excellent idea. An ISO is a single file to download / burn and is the most straightforward way of making your installation media. Everyone from the guru to the warez monkey understands burning an ISO. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: AMI MegaRAID lockup? not accepting commands.
On Sun, Mar 19, 2000 at 09:00:35PM -0500, John W. DeBoskey wrote: amr0: AMI MegaRAID mem 0xf6c0-0xf6ff irq 14 at device 10.1 on pci2 amr0: firmware 1.01 bios 1p00 128MB memory amrd0: MegaRAID logical drive on amr0 amrd0: 172780MB (353853440 sectors) RAID 5 (optimal) The adapter does not lockup while testing with bonnie and such. However, we have a 50Gig CVS repository sitting on the raid volume. When we do a 'cvs co' of -HEAD, it causes it to lockup. The following messages are repeating continuously: Mar 19 16:02:59 cvs /kernel: amr0: controller wedged (not taking commands) Mar 19 16:03:00 cvs /kernel: amr0: I/O error - dead Mar 19 16:03:00 cvs /kernel: amr0: cmd 2 ident 178 drive 0 Mar 19 16:03:00 cvs /kernel: amr0: blkcount 12 lba 59506736 Mar 19 16:03:00 cvs /kernel: amr0: virtaddr 0xd3089000 length 6144 Mar 19 16:03:00 cvs /kernel: amr0: physaddr c880 nsg 2 Mar 19 16:03:00 cvs /kernel: amr0: 1abea000/4096 Mar 19 16:03:00 cvs /kernel: amr0: 25d2b000/2048 Ditto, less the kernel messages. Every process wedged into biord and I couldn't reboot the machine or do much of anything (no DDB, g). Rebooting this resulted in all the of the disks being marked 'failed' by the controller and I had to remark them 'online' and boot. A very long night(well, whatever 3am is..) of fscking followed. It was not fun. amr0: AMI MegaRAID mem 0xf6c0-0xf6ff irq 10 at device 10.1 on pci2 amr0: firmware 3.13 bios 1.43 16MB memory amrd0: MegaRAID logical drive on amr0 amrd0: 173390MB (355102720 sectors) RAID 5 (optimal) -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0 sysinstall fails to recognize disks
On Wed, Mar 22, 2000 at 02:42:44PM -0500, Forrest Aldrich wrote: Since this is a fairly current issue, I'm posting this appropriately. I have a DELL server that has hooked up to it a PowerVault, with 8 36gb 10krpm LVD drives. The system has recognized these previously and dmesg shows them present; however, /stand/sysinstall says that I don't have ANY disks installed when using Label or Fdisk. The PowerVault is connected to a controller. Knowledge of which one would help. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 2nd call for reviews and tests: buf-bio patch
On Tue, Apr 04, 2000 at 08:14:40AM +0200, Jeroen Ruigrok/Asmodai wrote: Ehm. Not as if your VM stuff wasn't causing disruption. Needed, granted, but disruptive as well. And ucd-snmp has been broken quite some time (still is?) due to the work. And I know of a lot of people who actively use it. Not that it matters, but I fixed the code and submitted back a patch to ucd-snmp maintainers and its part of the snmp codebase now. Most of it was taken directly from the matching changes to vmstat, I believe. That is unless I missed something, or something else changed recently. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
On Tue, Apr 18, 2000 at 09:48:11AM +0200, Poul-Henning Kamp wrote: Listen, we are talking about an email which is shorter than the list of open PRs, and if people actually *DO* something about it it will get shorter fast The only reason it is a long report right now is that people are sloppy! I have large amounts of patches that fix a lot of these. They were done by myself and Nathan Ahlstrom. I'm currently making sure that they don't trade warning fixes for style errors, and I will start committing them. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Stale modules (Re: panic in the morning)
On Thu, Apr 20, 2000 at 11:24:49AM +0200, Stijn Hoop wrote:
\begin{newbie question}
So why aren't the modules built with the kernel instead of with the world?
\end{newbie question}
I bitched about this on committers the other day and marcel told me it was being
worked on.
--
Bill Fumerola - Network Architect
Computer Horizons Corp - CVM
e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
Office: 800-252-2421 x128 / Cell: 248-761-7272
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: SMP changes and breaking kld object module compatibility
On Mon, Apr 24, 2000 at 04:46:43AM -0500, Richard Wackerbarth wrote: From the USER's perspective, anything that requires me to as much as reload a module/program that I have already installed "breaks" it. The fact that it is only necessary to recompile it in order to fix it only means that it is easy to fix IF I have the source code. No-one forces you to upgrade you systems. Partial upgrades are something that are nice when they work, but understood when they don't. We don't accept bug reports (typically) when a person hasn't upgraded their world, kernel, and modules. I don't understand why we're accepting preemptive bitching. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP changes and breaking kld object module compatibility
On Mon, Apr 24, 2000 at 02:02:28PM -0500, Richard Wackerbarth wrote: That is also partly why you are also lacking the respect and support of a wider audience. If you act like FreeBSD is just a "developer's sandbox", that's what it will be. If you want it to be something greater than that, you must consider what you are doing to third party developers and end users. Developers and early adopters are the ones tracking -STABLE. Users are installing binary snapshots and releases. No-one in their right mind would release a module for "4.0-STABLE sometime between april and may". They release for 4.0-RELEASE or 4.1-RELEASE, this would not cause problems for those people. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: SMP changes and breaking kld object module compatibility
On Mon, Apr 24, 2000 at 02:14:50PM -0700, Rodney W. Grimes wrote: Developers and early adopters are the ones tracking -STABLE. Users are installing binary snapshots and releases. Some users do install snapshots and/or releases. Snap shots occur on a regular basis and are affected by this change in API. If they use the module from the same snapshot/release, it's not a problem. No-one in their right mind would release a module for "4.0-STABLE sometime between april and may". They release for 4.0-RELEASE or 4.1-RELEASE, this would not cause problems for those people. Ahh.. the problem occurs with user Z running snap 4.0-stable 4/30 when trying to use vendor X module for 4.0-release. Get it?? When the requirements for software are "FooBaz Version 1.2" that means "FooBaz Version 1.2". If the vendor markets software as "FreeBSD version 4.0 or later", that's their problem. The entire point is that somewhere the user has decided to upgrade their system, and they need to know what the consequences are before taking the plunge. If they upgrade their system half-ass (kernel, but not modules) they are digging their own grave. If they have 3rd party modules, they need to understand that those modules may not work if you're tracking changes. That's life. I don't expect my 3rd party voodoo 3000 drivers for Win98 to work in Win2000 either. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Archive pruning
On Mon, Apr 24, 2000 at 08:59:46PM -0500, Richard Wackerbarth wrote: Do we really need 5 year old history? a) yes, we need the history. b) do we need it "online everywhere"? I think the answer is "no". However the sandbox engineers think differently. c) I've brought this up more than once. Do "they" care? Normally "we" stop caring when we see your name in the From: header. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/boot/i386/boot0 Makefile boot0.s boot0.m
On Tue, May 23, 2000 at 08:20:48AM -0400, John Baldwin wrote: This should fix the world. Whistler: I want peace on earth and good will toward man. Bernard Abbott: Oh this is ridiculous. Martin Bishop: He's serious. Whistler: I want peace on earth and good will toward man. Bernard Abbott: We are the United States Government. We don't do that sort of thing. Martin Bishop: You're just gonna have to try. Bernard Abbott: Ok, I'll see what I can do. Whistler: Thank you very much. That's all I ask. -- from the movie Sneakers -- Bill Fumerola - Network Architect / Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Buildworld successful
On Fri, Jun 30, 2000 at 11:37:10AM -0400, Hasan Diwan wrote: Around 10am PDT yesterday, -CURRENT built and installed without an error. My only concern is why we need to have a hard link between /bin/csh and /bin/tcsh. For reasons you can find out by reading the mailing list archives. -- Bill Fumerola - Network Architect / Computer Horizons Corp - CHIMES e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bin/19635: add -c for grand total to df(1), like du(1) does
On Tue, Jul 04, 2000 at 09:56:43PM +0200, Blaz Zupan wrote: Ok, so let's say my / is 100% full, my /usr is 50% full and my /var is 20% full. What would the total number tell me? That my file systems are 56.6% full. That tells me nothing about my root file system running out of space, so this number is completely useless to me. I have to agree with Sheldon, where is the use to this number? If you would use the "total" field to monitor diskusage on / then you get what you deserve. Think about doing something like $ df -c/disk0 /disk1 /disk2 ... /diskX To just monitor a cluster of disks. -- Bill Fumerola - Network Architect / Computer Horizons Corp - CHIMES e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: bin/19635: add -c for grand total to df(1), like du(1) does
On Thu, Jul 06, 2000 at 06:09:54PM +0200, Paul Herman wrote:
Naturally, "no reason not to put it in" is most certainly *not* a
reason to put it in. I would like to hear some to sway me one way or
the other.
Spoiler:
df /disk1 /disk2 | \
awk '/^\// {t+=$2;u+=$3;} END { print "Total:", t,u,t-u,u*100/t; }'
...and "slaping 'df -c' into a pie chart" usually intails running it
through some parser like this, anyway... or?
[hawk-billf] /home/billf du -s /usr/src/sys/i386 /usr/ports/math | \
awk '{t+=$1; print $0} END { print t, "\ttotal" }'
6282/usr/src/sys/i386
15288 /usr/ports/math
21570 total
[hawk-billf] /home/billf du -cs /usr/src/sys/i386 /usr/ports/math
6282/usr/src/sys/i386
15288 /usr/ports/math
21570 total
Precedence.
--
Bill Fumerola - Network Architect / Computer Horizons Corp - CHIMES
e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: randomdev entropy gathering is really weak
On Sun, Jul 16, 2000 at 08:26:44PM +0200, Mark Murray wrote: Gotcha - fix coming; I need to stash some randomness at shutdown time, and use that to reseed the RNG at reboot time. ... and for installations where ssh-keygen is run the first time the system boots? -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
installkernel broken?
A little context
CROSSENV= MAKEOBJDIRPREFIX=${OBJTREE} \
COMPILER_PATH=${WORLDTMP}/usr/libexec:${WORLDTMP}/usr/bin \
LIBRARY_PATH=${WORLDTMP}${SHLIBDIR}:${WORLDTMP}/usr/lib \
OBJFORMAT_PATH=${WORLDTMP}/usr/libexec \
PERL5LIB=${WORLDTMP}/usr/libdata/perl/5.6.0
STRICTTMPPATH= ${WORLDTMP}/usr/sbin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games
INSTALLTMP= ${TMPDIR}/install.${TMPPID}
IMAKEENV= ${CROSSENV} \
PATH=${STRICTTMPPATH}:${INSTALLTMP}
installkernel:
cd ${KRNLOBJDIR}/${INSTALLKERNEL}; \
${IMAKEENV} MACHINE=${MACHINE} KERNEL=${INSTALLKERNEL} \
${MAKE} KERNEL=${INSTALLKERNEL} install
Now, why are we looking in ${WORLDTMP}/usr/sbin when what we should be
looking in is ${WORLDTMP}/usr.sbin? Same with /usr/bin != /usr.bin...
Disgruntled and reverting back to making kernels the way they were intended,
--
Bill Fumerola - Network Architect, BOFH / Chimes, Inc.
[EMAIL PROTECTED] / [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: installkernel broken?
On Wed, Jul 26, 2000 at 08:56:03AM -0700, Marcel Moolenaar wrote:
Now, why are we looking in ${WORLDTMP}/usr/sbin when what we should be
looking in is ${WORLDTMP}/usr.sbin? Same with /usr/bin != /usr.bin...
WORLDTMP is a place to *install* binaries we made during the build. We
don't install in /usr.bin or /usr.sbin; we install in /usr/bin and
/usr/sbin resp.
And then we try and install the kernel using those utilties that are in
directories that don't exist:
crazyhorse# make kernel=GENERIC installkernel
cd /usr/obj/usr/src/sys/GENERIC; MAKEOBJDIRPREFIX=/usr/obj
COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin
LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib
OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec
PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.6.0
PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/tmp/install.1532
MACHINE=i386 KERNEL=GENERIC make KERNEL=GENERIC install
make: not found
*** Error code 127
crezyhorse# ls -l /usr/obj/usr/src/{,i386/}usr{.,/}{s,}bin/make/make
ls: /usr/obj/usr/src/i386/usr.bin/make: No such file or directory
ls: /usr/obj/usr/src/i386/usr.sbin/make: No such file or directory
ls: /usr/obj/usr/src/i386/usr/bin/make: No such file or directory
ls: /usr/obj/usr/src/i386/usr/sbin/make: No such file or directory
ls: /usr/obj/usr/src/usr.sbin/make: No such file or directory
ls: /usr/obj/usr/src/usr/bin/make: No such file or directory
ls: /usr/obj/usr/src/usr/sbin/make: No such file or directory
-rwxr-xr-x 1 root wheel 112614 Jul 26 08:20 /usr/obj/usr/src/usr.bin/make/make
Disgruntled and reverting back to making kernels the way they were intended,
So, what's broken then?
Look where we define the PATH and look where I finally found make.
We seem to not be sticking it in the places we look to build with virgin
binaries.
--
Bill Fumerola - Network Architect, BOFH / Chimes, Inc.
[EMAIL PROTECTED] / [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: installkernel broken?
On Wed, Jul 26, 2000 at 10:02:40AM -0700, Marcel Moolenaar wrote: Make sure you have /usr/src/Makefile.inc1 rev 1.162 or up. The installkernel was using the wrong buildcontext (ie IMAKEENV). IMAKEENV was changed to have the very restricted path that broke the installkernel target as you describe above. This has been fixed in 1.162. okay. I'm going to go find who made our local cvsup mirror stop mirroring and feed them to the paper shredder. thanks. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic at shutdown
On Mon, Jul 31, 2000 at 10:37:48PM -0700, R Joseph Wright wrote: I just built a new world/kernel yesterday, and now I get a panic when I shut down. I ran gdb on the dump: .. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 2998272 initial pcb at 25b1c0 panicstr: lockmgr: pid 1, not exclusive lock holder 0 unlocking panic messages: --- --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:303 303 dumppcb.pcb_cr3 = rcr3(); type 'bt', this tells us just about as much as if you said "it crashed". though, by the panic message, this seems to be a known bug.. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with sym device driver?
On Tue, Aug 29, 2000 at 09:18:07AM -0700, John Polstra wrote: WARNING: / was not properly dismounted pid 271 (ldconfig), uid 0: exited on signal 11 (core dumped) Er, why is ldconfig dumping core? guess it's the linux ldconfig and it hasn't been brandelf'd after obrien made a change that required that. /guess -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Call for libtermcap ressurection from the dead
On Sat, Sep 16, 2000 at 04:23:42AM +0400, Andrey A. Chernov wrote: Avdantages: 1) We'll be 100%-compatible with all libtermcap programs again. 2) Save LOTS of space for static binaries since libtermcap is extremally small. Opinions? I don't object. The namespace collisions in src/games with ncurses functions are really, really bad, and though just not linking to ncurses is sort of a hackish fix, this would at least mask the problems until further into the future when I have time to change function names. :- -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Network bridge on current.
On Thu, Sep 28, 2000 at 12:38:40AM -0700, Julian Elischer wrote: I am not sure about Luigi's bridging code. I know the dummynet stuff seems to connect with the ipfw code but I don't think that the bridge code does... (I may be wrong) So I don't know how you plan on filtering the bridged segments.. You are wrong, but we'll forgive you. :- from bridge(4): net.link.ether.bridge_ipfw Set to 1 to enable ipfw filtering on bridged packets. Note that ipfw rules only apply to IP packets. from ipfw(8): Each incoming or outgoing packet is passed through the ipfw rules. If host is acting as a gateway, packets forwarded by the gateway are pro- cessed by ipfw twice. In case a host is acting as a bridge, packets for- warded by the bridge are processed by ipfw once. the 'bridged' keyword can be used to match only bridged packets, so: ipfw add allow tcp from any to any 22 setup bridged ipfw add allow tcp from any 22 to any established bridged would allow ssh over a bridge, but in the absence of other rules, wouldn't allow it to the actual machine (or if the machine is also a router(?!) it wouldn't route ssh sessions either.) -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: interesting problem
On Sat, Sep 30, 2000 at 06:47:17PM -0500, Tony Johnson wrote: It appears that I am not the only one who has seen this. Don't call this an unsubstantiated comment... It's not just me. I didn't quote anything else of your message because this is the obvious problem: No one questioned if you had a problem, no one questioned if you were or weren't the only person to have a problem. However, if you're not willing to get good debugging information in the way that the developers ask for then we have a branch made just for you. -current helps those who help themselves. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs servers load
On Sat, Oct 07, 2000 at 04:17:45PM -0400, Jon Parise wrote: Time to put the cvsup servers on the map with ICBM coordinates maybe? I think that would actually be quite useful (or, at the very least, purely informative). I've often thought it would be neat if in sysinstall the ftpX.freebsd.org mentioned next to it which provider the mirror site [primarily] used or at least the name of the entity that was hosting it. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs servers load
On Sat, Oct 07, 2000 at 11:59:41PM -0600, Wes Peters wrote: . o O I feel another Xearth markers file coming. ftp servers, cvsup servers, www servers, etc? -rw-r--r-- 1 billf ncvs 2398 May 7 15:23 /usr/ports/astro/xearth/files/freebsd.ftp.markers -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: current.freebsd.org
On Sun, Oct 08, 2000 at 07:13:56PM -0700, Bill Woods mail wrote: Yea, guess so, but I cant help but notice this started after the buyout by BSDI The clue boat left the docks and you were standing on the pier. Might I suggest a long walk... -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: POSTFIX-- Wietse: tweak and go! --pkg port: both duds
On Wed, Oct 11, 2000 at 03:34:42PM -0700, dannyman wrote: I am a Postfix weenie. I don't care what the "default" MTA that comes with FreeBSD is, but I like that 4.x is better at giving you a choice in the matter. If someone wanted to maintain Postfix in the FreeBSD source tree as an alternative to Sendmail, I don't see what's wrong with that ... same for Qmail and the like. The main objection I would seis that you're then bloating FreeBSD's source tree with every MTA known to man. The answer? Jihad? Or make EVERY MTA an option for the base system? Or just do as has been done for time immemorial and leave Sendmail where it has always been ... :) For the hundred millionth time, the right way to do all of this is in the "everything is a package" approach, which everyone agrees is the right answer, but no one has turned out code to do yet. All time spent anywhere other then churning out the code for the that design is wasted. We don't need another MTA in the default system, some would argue we don't need the current on we have. We do need a more configurable install and adding more MTAs isn't going to help. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Fragments refused by ipfw
On Thu, Oct 12, 2000 at 04:13:31PM +0900, Jun Kuriyama wrote:
Host A is my desktop box (-current), host B is NFS server (3-stable).
Sometimes (at heavy load on NFS?), my access to NFS server is locked.
At that time, following messages are logged.
ipfw: -1 Refuse UDP hostB hostA in via fxp0 Fragment = 925
I used ipfw with default accept but no rules. I have not seen such
message before.
To be perfectly honest I don't see what code path could cause this, if
it hits the default rule we jump out of ipfw right away:
for (; chain; chain = LIST_NEXT(chain, chain)) {
again:
f = chain-rule;
if (f-fw_number == IPFW_DEFAULT_RULE)
goto got_match ;
[...]
got_match:
#if STATEFUL /* stateful ipfw */
/*
* If not a dynamic match (q == NULL) and keep-state, install
* a new dynamic entry.
*/
if (q == NULL f-fw_flg IP_FW_F_KEEP_S)
install_state(chain);
#endif
*flow_id = chain ; /* XXX set flow id */
/* Update statistics */
f-fw_pcnt += 1;
f-fw_bcnt += ip-ip_len;
f-timestamp = time_second;
/* Log to console if desired */
if ((f-fw_flg IP_FW_F_PRN) fw_verbose)
ipfw_report(f, ip, rif, oif);
/* Take appropriate action */
switch (f-fw_flg IP_FW_F_COMMAND) {
case IP_FW_F_ACCEPT:
return(0);
That's the entire codepath of a default rule hit. The message you're
seeing is from ipfw_report(), which shouldn't be called from the
default rule match either.
--
Bill Fumerola - Network Architect, BOFH / Chimes, Inc.
[EMAIL PROTECTED] / [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Fragments refused by ipfw
On Fri, Oct 13, 2000 at 02:37:04PM +0900, Jun Kuriyama wrote: After some debug, PULLUP_TO() in case IPPROTO_UDP. Is reason for this failing of m_pullup()? Yes. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: divert as module?
On Sun, Oct 22, 2000 at 09:52:03PM +0200, Leif Neland wrote: I want to install ipfw and natd to a machine working as isdn-router, which I lost the kernel config for I connect to the world via userland-ppp and isdnd. I don't have any ipfw or divert compiled in the kernel, but I can load ipfw.ko, so the firewall rules can work (I now see my isp sends IGMP's to me...) Stop right here. If you didn't compile IPDIVERT in the kernel, the hooks aren't in the tcp/ip stack and you're screwed. Figuring out a way to fix this is on my TODO list, though I don't have any ideas that don't cost a performance hit for non-DIVERT users. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ipfw question.
On Thu, Oct 26, 2000 at 01:31:03PM -0700, Glen Gross wrote:
I built a 4.1.1 kernel, and the module was built, but when I load the ipfw
module with
#kldload ipfw
it defaults to a deny_all policy, even though I have default_to_accept in my
kernel configuration.
This makes it difficult to configure remotely without getting locked out of the
system.
Is there a way to cause the ipfw module to default to a different policy upon
loading?
For now it appears that I am locked out, until I can access the console.
Your kernel configuration has ABSOLUTLY NOTHING to do with your module builds.
[hawk-billf] /usr/src cat sys/modules/ipfw/Makefile
# $FreeBSD: src/sys/modules/ipfw/Makefile,v 1.13 2000/05/27 01:13:50 peter Exp $
.PATH: ${.CURDIR}/../../netinet
KMOD= ipfw
SRCS= ip_fw.c
NOMAN=
CFLAGS+= -DIPFIREWALL
#
#If you want it verbose
#CFLAGS+= -DIPFIREWALL_VERBOSE
#CFLAGS+= -DIPFIREWALL_VERBOSE_LIMIT=100
#
#If you want it to pass all packets by default
#CFLAGS+= -DIPFIREWALL_DEFAULT_TO_ACCEPT
#
Guess what you should uncomment
--
Bill Fumerola - Network Architect, BOFH / Chimes, Inc.
[EMAIL PROTECTED] / [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ipfw question.
On Thu, Oct 26, 2000 at 01:36:40PM -0700, Glen Gross wrote: Thanks, I suppose I should have been able to figure that one out... if I could log in! I will fix it when I get home. :-) Playing with firewalls without out-of-band (serial console, nocmonkey, etc) is dangerous. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ipfw question.
On Thu, Oct 26, 2000 at 03:10:35PM -0700, David O'Brien wrote:
So one doesn't have to change the source, would you be willing to add
WANT_foo logic so one could just set it in /etc/make.conf? Or add
${IPFIREWALL_OPTS} to CFLAGS and then IPFIREWALL_OPTS could be set in
/etc/make.conf?
Having read the rest of this thread my position is "willing, able, but
unsure if its needed". I'll talk with Peter when he's back on this
side of the Pacific.
--
Bill Fumerola - Network Architect, BOFH / Chimes, Inc.
[EMAIL PROTECTED] / [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: umount -f busted
On Tue, Nov 07, 2000 at 01:13:41PM -0700, Warner Losh wrote: I just tried to umount -f /home, where /home was an NFS mounted file system on a network that was no longer attached to my laptop. In the past this has just worked, even if processes were hung in disk wait state. When I tried it last night on an Oct 29th kernel, I got EBUSY and the file system remained mounted. This can't be right. Is there any way to really force it short of a reboot? That's just the way it seems to be. Mount with 'intr,soft' for better luck with this. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: umount -f busted
On Wed, Nov 08, 2000 at 07:43:24AM -0700, Warner Losh wrote: It is a problem that I could have sworn worked before SMPNG. Negative, this occurs on releng_4 machines for me as well. It also was occuring on my -current workstation that was about 110 days old before a disk went out, so it was definatly pre-smpng. -- Bill Fumerola - Lame Duck, BOFH / Chimes, Inc. [EMAIL PROTECTED] / [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libc.so.4 not found
On Sat, Nov 25, 2000 at 12:18:43AM -0800, Derek Schene' wrote: On a fresh hard drive I installed 5.0 20001123 Current and got the following after installation: Local package initialization:/usr/libexec/ld-elf.so.1: Shared object "libc.so.4" not found we bumped the libc version to 5, but we didn't make compat4 libaries available for installation yet. I'll renew my annoyance with the fact that we just bumped this without even figuring out why things broke or if we could change them in a way to save functionality without having to bump the version number[1]. We also never propogated this bump to RELENG_4, so the release shipped with the worst of both worlds. To answer your question, though: I'd suggest just symlinking libc.so.4 to libc.so.5, nothing terrible should happen. This should work until we get our act together regarding this change. -- Bill Fumerola - security yahoo / Yahoo! inc. - [EMAIL PROTECTED] / [EMAIL PROTECTED] 1. to my knowledge. I tried to keep up on this thread but its possible someone figure it out and we just didn't revert the libc bump. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
gasp broke world.
Doug, 'gasp' broke world. targ-env.h: No such file or directory -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
On Wed, 8 Dec 1999, Soren Schmidt wrote: The same thing is about to apply to the woxware sound code, we have a new shiny system that works and is much better designed... For some definitions of "works". -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADSUP: wd driver will be retired!
On Thu, 9 Dec 1999, Jeroen Ruigrok/Asmodai wrote: For some definitions of "works". Low shot. If not for Cameron and Sanimura-san we would still be left dangling with the hopeless kludge of pcm vs VoxWare. They finally put their effort into something which all questions plus remarks on the topic would already have released a long time ago. It wasn't meant to be low or insulting. I'm making the simple obervation that my office has been oddly silent ever since switching to newpcm. It's not for unwillingness to test patches either. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vinum start needs block device
On Sun, 12 Dec 1999, Peter Wemm wrote:
-if (drive-vp-v_type != VBLK) { /* only consider bl
ock devices */
+if (!vn_isdisk(drive-vp)) { /* only consider bl
Note: this fixes some recent problems (Hi Greg!) that I've been
having.
I'm now a happy puppy once again.
--
- bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp -
- ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] -
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Speaking of moving files (Re: make world broken building fortunes )
On Mon, 13 Dec 1999, Louis A. Mamakos wrote: So how about /usr/sbin/chown - /sbin/chown so that MAKEDEV works with just the root file system mounted? As one who just got his ass bitten by this, I would vote yes. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vinum start needs block device
On Mon, 13 Dec 1999, Greg Lehey wrote: Note: this fixes some recent problems (Hi Greg!) that I've been having. Really? I thought they were more serious. So did I. Although, I did a 'make world' after I saw the change go in, so the fix could have come from a different commit. In any event 'vinum stripe /dev/da1e /dev/da2e' doesn't pagefault that machine anymore. PNPBIOS is a different story... -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pnp, sound and LINT in -current
On Wed, 15 Dec 1999, Julian Elischer wrote: Somethifn I have not bee tracking has happened with config, and "controller pnp" as it no longer likes it. however LINT doesn't help because it still has comments refering to 'enable pnp'. Are these old? and if not, how do I now do this? [hawk-billf] /home/billf grep pnp.c /sys/conf/files isa/pnp.c optional isa if you have isa, you now have pnp, as I understand it. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCCARD vs GENERIC
On Sun, 19 Dec 1999, Warner Losh wrote: 4) The xe and wi drivers are not enabled in GENERIC but are in PCCARD. No reason at all not to have them in GENERIC. I think that the 40k that we saved in removal of old cdrom devices would more than make up for the extra pcic/pccard/wi/xe devices, but I'm biased. I'd love to see the xe driver in GENERIC, however I'd also love to see it _working_, not just compiling. My recent attempts to look at the code have proven just how little I know about device drivers. I have a few of these cards Warner, and would send one (you could even send me those cards I gave you at the con and I'll send one of these in that box.. :-). -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PCCARD vs GENERIC
On Sun, 19 Dec 1999, Warner Losh wrote: In message [EMAIL PROTECTED] Bill Fumerola writes: : I'd love to see the xe driver in GENERIC, however I'd also love to see : it _working_, not just compiling. My recent attempts to look at the code : have proven just how little I know about device drivers. Think of it as an opportunity :-) My timesheet for last week had 100+ hours, I don't need more work. :- I think that I have cards that would be supported by xe. I don't have the time to get them working on the old pccard system. I would make time on a consulting basis, but I really want to spend most of my spare time on the newcard stuff in advance of 4.0. Okay, I have cardbus versions of this card too, if you need those for your newcard stuff. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: fsck not cleaning on first try
On Sun, 19 Dec 1999, Alex Zepeda wrote: Hmm. It happened again. This time I was playing around with the vmware stuff (the linux procfs thingy refused to buildsorta, but FWIW, I think this is the way to go, not bloating *our* procfs), and eventually when run panic'd the system. I just rebooted it (nearly a day later), and fsck cleaned it and printed some info, but then mount refused to mount it. A simple reboot from the comandline seems to have worked. Hmmm indeed. Ditto. mount was telling me my fs wasn't clean, but after I rebooted it was fine and it didn't fsck that second time. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: error with install, Unable to make device nodes...
On Mon, 20 Dec 1999, Mike Heffner wrote: Unable to make device node of /dev/ad0s1b in /dev! The creation of filesystems will be aborted. If I switch to the second virtual terminal it says: DEBUG: Scanning disk ad0 for root filesystem DEBUG: Scanning disk ad0 for swap partitions DEBUG: MakeDev: Unable to lookup user "root". [ last line repeated several times ] aol Me too. /aol This is not a Danish thing however, this fails with scsi drives as well. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc compile error
On Tue, 28 Dec 1999, Amancio Hasty wrote: Yes, I can rightfully claim that you cannot build XFree86 3.9 xxx dated December 24 with the default gcc compiler on FreeBSD -current. I am running FreeBSD -current and XFree86 3.9xxx current. Typically this empty space would contain the output of the build failure, more details, or even a patch. You might want to find out why your mailer is thrashing it. Thats nice . Now we have a compiler which fails to build X. This seems like hyperbole. I'm able to build X just fine with the -current compiler, so to directly imply that we can't do so flies in the face of common sense and experience. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc compile error
On Tue, 28 Dec 1999, Amancio Hasty wrote: The details were previously posted by . Good Nite Whatever ate the details on your previous post seems to be at it again. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc compiler problem part deux
On Wed, 29 Dec 1999, Amancio Hasty wrote: There are packages such as XFree86 which called directly the installed cpp. Those packages which rely on the old behavior of /usr/libexec/cpp for instance defining __FreeBSD__ are now broken . ... and they will be fixed through bug reports. We now know what was causing your mishaps with XFree86, this has already been corrected in the port, but you are using the straight source. Perhaps our XFree86 liason can correct this behavior before XFree86 makes a release off of this branch. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: fsck of /, related to last post.
On Thu, 30 Dec 1999, David Gilbert wrote: Related to my last post, the system came up and started to fsck. It appears, with current, that the system will refuse to r/w mount root even though the fsck has complete successfully. Is this an rc-file out-of-date issue, or has something changed in the kernel. Reboot. I don't know why it works, but it does. :- -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: fsck of /, related to last post.
On Thu, 30 Dec 1999, David Gilbert wrote: Bill Reboot. I don't know why it works, but it does. :- Right... I already knew that, but it's a manual reboot... and this is "suboptimal" (ie. requiring operator intervention). Indeed. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: xntpd - VERY old folks, how about updating? :-)
On Sun, 2 Jan 2000, Karl Denninger wrote: Why the hell Walnut Creek wastes their money on your type REMAINS beyond my comprehension. It really hasn't been a problem for anyone but you. It's more successful, then say, alternative top level domain projects that have gone nowhere. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: One final note and a bite me to you
On Sun, 2 Jan 2000, Karl Denninger wrote: Theo was right in splitting off from you folks. I should have followed him a couple of years ago and done my own split. Now, its simply not worth it. Not that you'll listen, but: OpenBSD split from NetBSD. FreeBSD is and always has been a seperate project from NetBSD. Your credibility isn't getting any better. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic in newpcm ( was Re: Ouch! Something broke (possibly ATA))
On Tue, 4 Jan 2000, Alex wrote: and I apologise for wrongfully accusing it. The panic is in fact caused by newpcm (Cameron CC'd). DDB trace can be provided upon request (is there a way to save it into a file instead of having to write it down on a piece of paper?) Serial consoles are your friend. I recently started using them and am never going back. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Opera Beta and FreeBSD
On Wed, 5 Jan 2000, Lutz Albers wrote: Works fine, but you need the glibc-2.1 libraries (i.e. from RedHat 6.1), as it is linked against these. Keep in mind that this is no beta, but a 'technical preview', many functions are still missing. FWIW, the linux_base port in http://www.FreeBSD.org/~marcel/ works fine, and probably should be committed. I'm running Nutscrape on that port on several different machines and they're all just fine. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Neomagic Sounddriver hangs HP OB4150
On Mon, 10 Jan 2000, #Michael Class wrote: The Laptop is equipped with the following Neomagic-Chip: chip1: NeoMagic MagicMedia 256AX Audio controller irq 10 at device 0.1 on pci1 The Stack-Backtrace looks exactly the same as the other mail mentioned. A little bit further digging into this shows me that on this Laptop every read access to the second memory-area of the chip in the range of 0x600-0x8ff brings the machine to a halt. I can read successfully from the areas with offset 0x0-0x5ff and 0x900-0xFFF. The Header-File states that the mixer-I/O Area starts at offset 0x600. This access brings the machine to a halt during boot. Any suggestions of what I could try? Try providing us with real data. The boot message you gave us is when pcisupport.c matches it, not when neomagic. matches it. It is impossible to recieve the above message and then have the neomagic code fall on its face. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
RE: load spike strangeness
On Sat, 8 Jan 2000, FreeBSD wrote: list if you insist on attacking me there. Maybe Karl was right, some people in the FreeBSD organization really do think they are above the rest of us. I however do not share that belief. So, are you done? If you had half of the etiquette and knowledge on e-mail you previously have stated you have, you'd realize that phk doesn't (nor does anyone with a @FreeBSD.org) speak for the FreeBSD organization. Please crawl back into the hole you came out of. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PNPBIOS + Dell PowerEdge = panic()
Hola,
As the subject indicated PNPBIOS and Dell PowerEdge servers seem
to be a recipe for disaster. This doesn't bother me too terribly
much as I don't need PNPBIOS for anything on this machine, but I
figured the new-bus folks didn't have enough to do, so I'd help.
This machine is a dual pIII/450 w/512MB. This is not SMP specific, BTW.
This post exposes my DDB and newbus stupidity. If this was gdb,
I'd at least try and pull out some sort of relevent data. I have
a guess that the sheer amount/range of the ports and iomem has
something to do with it. That or the fact one starts with 0.
Thanks and e-mail me privatly or catch me on IRC (bfumerola) if
you want me to try things with this server.
--
- bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp -
- ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] -
The relative part:
unknown0: PNP0c02 at port
0x800-0x83f,0x850-0x85f,0xe0-0xef,0x22,0x2e-0x2f,0x80,0xaa00-0xaa7f iomem
0-0x9,0x10-0x1fffdfff,0xfff8-0x,0xf-0xf,0xec000-0xe
irq 15 on isa0
panic: pmap_mapdev: Couldn't alloc kernel virtual memory
mp_lock = 0002; cpuid = 0; lapic.id = 0100
Debugger("panic")
Stopped at Debugger+0x35: movb$0,in_Debugger.555
The full boot -v:
-- Forwarded message from Bill Fumerola [EMAIL PROTECTED] --
SMAP type=01 base= len= 000a
SMAP type=02 base= 000f len= 0001
SMAP type=01 base= 0010 len= 1fefe000
SMAP type=02 base= 1fffe000 len= 2000
SMAP type=02 base= fff8 len= 0008
SMAP type=02 base= fec0 len= 0001
SMAP type=02 base= fee0 len= 0001
Copyright (c) 1992-2000 The FreeBSD Project.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 4.0-CURRENT #0: Fri Jan 14 20:51:21 GMT 2000
[EMAIL PROTECTED]:/usr/src/sys/compile/GLUEPNP
Calibrating clock(s) ... TSC clock: 447668222 Hz, i8254 clock: 1193124 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter "i8254" frequency 1193182 Hz
CLK_USE_TSC_CALIBRATION not specified - using old calibration method
CPU: Pentium III/Xeon (447.69-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x673 Stepping = 3
Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,XMM
real memory = 536862720 (524280K bytes)
Physical memory chunk(s):
0x1000 - 0x0009efff, 647168 bytes (158 pages)
0x0030 - 0x1fffbfff, 533708800 bytes (130300 pages)
avail memory = 518021120 (505880K bytes)
Programming 24 pins in IOAPIC #0
IOAPIC #0 intpin 2 - irq 0
SMP: CPU0 apic_initialize():
lint0: 0x0700 lint1: 0x00010400 TPR: 0x0010 SVR: 0x01ff
FreeBSD/SMP: Multiprocessor motherboard
cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee0
cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee0
io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0
bios32: Found BIOS32 Service Directory header at 0xc00ffe80
bios32: Entry = 0xffe90 (c00ffe90) Rev = 0 Len = 1
pcibios: PCI BIOS entry at 0xcc0e
pnpbios: Found PnP BIOS data at 0xc00fe2d0
pnpbios: Entry = f:e2f4 Rev = 1.0
Other BIOS signatures found:
ACPI: 000fdef0
Preloaded elf kernel "pnpbios" at 0xc02e4000.
Pentium Pro MTRR support enabled
md0: Malloc disk
Creating DISK md0
Math emulator present
SMP: CPU0 bsp_apic_configure():
lint0: 0x00010700 lint1: 0x0400 TPR: 0x0010 SVR: 0x01ff
pci_open(1):mode 1 addr port (0x0cf8) is 0x8090
pci_open(1a): mode1res=0x8000 (0x8000)
pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71a08086)
devclass_alloc_unit: pcib0 already exists, using next available unit number
npx0: math processor on motherboard
npx0: INT 16 interface
pci_open(1):mode 1 addr port (0x0cf8) is 0x
pci_open(1a): mode1res=0x8000 (0x8000)
pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71a08086)
pcib0: Intel 82443GX host to PCI bridge on motherboard
found- vendor=0x8086, dev=0x71a0, revid=0x00
class=06-00-00, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
map[10]: type 1, range 32, base f000, size 26
found- vendor=0x8086, dev=0x71a1, revid=0x00
class=06-04-00, hdrtype=0x01, mfdev=0
subordinatebus=1secondarybus=1
found- vendor=0x1011, dev=0x0024, revid=0x03
class=06-04-00, hdrtype=0x01, mfdev=0
subordinatebus=3secondarybus=2
found- vendor=0x8086, dev=0x7110, revid=0x02
class=06-01-00, hdrtype=0x00, mfdev=1
subordinatebus=0secondarybus=0
found- vendor=0x8086, dev=0x7111, revid=0x01
class=01-01-80, hdrtype=0x00, mfdev=0
subordinatebus=0secondarybus=0
found- vendor=0x8086, dev=0x7112, revid=0x01
class=0c-03-00, hdrtyp
Re: PNPBIOS + Dell PowerEdge = panic()
On Mon, Jan 17, 2000 at 05:12:14PM -0800, Mike Smith wrote: The problem here is that the i386 nexus_alloc_resource() unconditionally calls pmap_mapdev() to map any memory-type resource into the kernel. This is definitely a bad idea; IMHO we should only do this when the resource is actually activated (and obviously free it when deactivated). Commentary? Should I just commit the change and see what happens? 8) Naturally, I know nothing of the implications, but I'd certainly test patches since I can reproduce this with the greatest of ease. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problems with PCMCIA Cards
On Wed, Jan 19, 2000 at 03:50:49PM -0700, Wes Peters wrote: Mmm... Good point. This means updating code and compiling a new kernel every time Joe's hardware company sticks their own name on a generic OEM PCI or PCCard, doesn't it? I love this industry. Do the above and try and figure out and track down if the marketing information matches what actually shows up on the product, now find out if it works exactly the same or if there is some stupid quirk that Joe's Hardware added to the chip Welcome to Bill Paul's hell. :- -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: when is FreeBSD-4.0 up for release ?
On Fri, Jan 21, 2000 at 05:34:20PM -0800, David O'Brien wrote: So every little date event needs a confirmation?? Why isn't the fact that JKH didn't resend the event not mean that it is in effect? David, It's been previously stated that the feature freeze (is/was) planned for Jan 15 and would take effect when jkh made the announcement. If he hasn't made the announcement committers (and submitters like Will) are to assume that it hasn't taken place. This is the normal for announcements for freezes for as long as I've been a committer, or as long as I can remember, whichever is shorter. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 3.4-4.0 ... *almost* ...
On Wed, Feb 02, 2000 at 02:40:06PM -0400, The Hermit Hacker wrote: === lib/libcom_err/doc install-info --quiet --defsection="Programming development tools." --defentry="* libcom_err: (com_err).A Common Error Description Library for UNIX." com_err.info /usr/share/info/dir install-info: unrecognized option `--defsection=Programming development tools.' Try `install-info --help' for a complete list of options. *** Error code 1 Source tree is as of Feb 1st, so only 24hrs old, but I don't recall seeing anything go throughthe list concerning the above ... Without looking at the specifics, I'd say that libcom_err depends on one of the new features of install-info (and the new version hasn't been merged from current). yet another thing to add to the bootstrap tools (or whatever they've called, I haven't followed the naming convention thread..) -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /usr/src/Makefile.inc1: make update
On Mon, Feb 07, 2000 at 10:31:17PM +0100, Christian Weisgerber wrote: Why does "make update" in /usr/src also include a cvsup of /usr/ports? Since /usr/ports and /usr/docs have Makefiles and "update" targets of their own, and the alternative update by cvs doesn't cover /usr/ports either, I suggest to remove the /usr/ports cvsup from Makefile.inc1's "update" target. As the person who implemented PORTSSUPFILE, I'd object. Originally SUPFILE2 was set to the ports-supfile, so to preserve original behavior (that is, updating ports along with src/) that stayed in. To some of us, updating both at the same time is rather convinient as well. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /usr/ports/ too big?
On Sat, Feb 12, 2000 at 01:58:14PM -0600, Richard Wackerbarth wrote:
On Sat, 12 Feb 2000, David O'Brien wrote:
TAKE THIS TO [EMAIL PROTECTED] *
Agreed. This is where the depth of the discussion should take place.
This is NOT a -current issue!!
I beg to differ. Any significant change to the status-quo is a -current issue.
To adopt ANY SIGNIFICANT CHANGE without widespread public notice is just
inviting grumblings of "backroom politics". Just see what happens if the City
Council votes to close Main Street and explains " this was discussed at a Public
Hearing before the Public Works Commission"
And some of us, myself included, are advocating making FreeBSD into a small set
of ports!
I guess that doesn't affect very many people :-)
You are very wrong. We are not "adopting significant change", we are discussing
possibilities. Discussions related to ports/packages belong on freebsd-ports.
Please read the mail charters.
--
Bill Fumerola - Network Architect
Computer Horizons Corp - CVM
e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED]
Office: 800-252-2421 x128 / Cell: 248-761-7272
PS. The reason that "Public Works Commissions" of the world exist is because
City Councils trust their departments to make informed reccomendations.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: /var/db/pkg/.mkversion
On Wed, 31 Mar 1999, Jordan K. Hubbard wrote: I think this entire thing is a massive botch and needs to be removed as a bad idea ASAP. I think that's jumping to conclusions a little too quickly. Jordan, we are eliminating a LOT more future PRs and FAQs by using this method. A few permission and installation oversights (no software can ever be tested on every possible instance.) should not constitute removal of the whole idea. - bill fumerola - bi...@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfume...@computerhorizons.com - bi...@freebsd.org - To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
