Re: portsdb and portupgrade causes errors
On Thursday 23 December 2004 08:37 pm, whitevamp wrote: > i dont know weathere this place to be posting this to or not .. if > not point me in the right direction to go.. > > i have just updated my system to 5.3 frrom 4.9 and now every time i > goto run portsdb , or portupgrade iget the same error message.and i > also have a nother 5.3 box that was a fresh install of 5.3 thats > getting the same error > > I have checked this and iam doing a cvsup src all , and i have no > refuse files in any one of the conf files IE: make.conf , > pkgtools.conf (INDEX builds are > not supported with partial or out-of-date ports collections -- in > particular, if you are using cvsup, you must cvsup the "ports-all" > collection, and have no "refuse" files.) > and i have wiped out my intire ports tree IE: /usr/ports/* , and > recvsuped it with the same error showing up > > > so what would be giveing me this exact same error on both boxes?? > portsdb -Ufu > Updating the ports index ... Generating INDEX.tmp - please > wait..fr-mozilla-flp-1.7.3_1: "/usr/ports/www/mozilla-gtk2" > non-existent -- dependency list incomplete ===> french/mozilla-flp > failed > *** Error code 1 > 1 error > > > Before reporting this error, verify that you are running a supported > version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you > have a complete and up-to-date ports collection. (INDEX builds are > not supported with partial or out-of-date ports collections -- in > particular, if you are using cvsup, you must cvsup the "ports-all" > collection, and have no "refuse" files.) If that is the case, then > report the failure to [EMAIL PROTECTED] together with relevant > details of your ports configuration (including FreeBSD version, > your architecture, your environment, and your /etc/make.conf > settings, especially compiler flags and WITH/WITHOUT settings). > > Note: the latest pre-generated version of INDEX may be fetched > automatically with "make fetchindex". > > > *** Error code 1 > > Stop in /usr/ports. > *** Error code 1 > > Stop in /usr/ports. > failed to generate INDEX! > portsdb: index generation error > > vampextream# uname -a > FreeBSD vampextream.com 5.3-RELEASE-p2 FreeBSD 5.3-RELEASE-p2 #3: Wed > Dec 8 20:33:13 PST 2004 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/VAMPEXTREAM i386 > > > if theres any othere information that you need just let me know . > > and thankx for any help on this issue , inadvance. People usually report this sort of thing in freebsd-questions@freebsd.org or [EMAIL PROTECTED] These days it is best to run make fetch index from /usr/ports after you've run cvsup rather than build INDEX-5 for yourself. -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portsdb and portupgrade causes errors
On Thursday 23 December 2004 08:50 pm, Michael C. Shultz wrote: > > These days it is best to run make fetch index from /usr/ports > after you've run cvsup rather than build INDEX-5 for yourself. > > -Mike correction: run make fetchindex not make fetch index from /usr/ports ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portsdb and portupgrade causes errors
On Thursday 23 December 2004 09:42 pm, Brian Behlendorf wrote: > On Thu, 23 Dec 2004, Michael C. Shultz wrote: > > On Thursday 23 December 2004 08:50 pm, Michael C. Shultz wrote: > >> These days it is best to run make fetch index from /usr/ports > >> after you've run cvsup rather than build INDEX-5 for yourself. > >> > >> -Mike > > > > correction: > > > > run make fetchindex not make fetch index from /usr/ports > > Out of curiosity, why isn't the index included in the update > normally? > > Brian Beats me, I once suggested making a port of the INDEX files so they could be updated automatically, but the "powers that be" chose this solution instead. What is really annoying is everytime you run make update the INDEX files get wacked and adding ports/INDEX* to the refuse file no longer works :( -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portsdb and portupgrade causes errors
On Thursday 23 December 2004 09:59 pm, Kris Kennaway wrote: > On Thu, Dec 23, 2004 at 09:42:37PM -0800, Brian Behlendorf wrote: > > >run make fetchindex not make fetch index from /usr/ports > > > > Out of curiosity, why isn't the index included in the update > > normally? > > It changes dozens of times per day, and the deltas would be enormous. > > Kris Way back when, I used to get the INDEX when running cvsup unless I put it in the refuse file. Of coarse it was old and useless so one was better off building their own INDEX. So why cant we just receive the INDEX like we used to, but unlike before, l have it updated as often as is being done now? -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portsdb and portupgrade causes errors
On Thursday 23 December 2004 10:43 pm, you wrote: > On Thu, 23 Dec 2004, Michael C. Shultz wrote: > > Way back when, I used to get the INDEX when running cvsup unless > > I put it in the refuse file. Of coarse it was old and useless so > > one was better off building their own INDEX. So why cant we just > > receive the INDEX like we used to, but unlike before, l have it > > updated as often as is being done now? > > Because the way we used to do it required tremendous churn in the > CVS repository. And it was _still_ out of date. We in user land don't see that end of things :) Why does INDEX have to go into the CVS repository anyways? Guess that is why you all changed things around? > > The fact that you can't refuse it is a bug, and has been reported > to jdp. In the meantime, a cron script that does something like a > fetch and then a copy is your best bet. It's really not a bother, and with DSL it takes like 30 seconds to download it, but as I'm sure you can see many new users are getting tripped up by the change because now there is this extra make fetchindex step. I really think making the INDEX files into a port would be the best solution because every one understands ports and it could easily be done without creating churn on the CVS repository, just don't use a distinfo file and then you could update the source tarball at will without bothering anybody. my 2 cents worth -Mike > > There's really quite a bit of email in the mailing list archives > about why this was done. The short summary is that in the short > run there is some pain but in the long run this is a win for the > project, and the users. > > mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Trials and tribulations on mirroring....
On Tuesday 18 January 2005 09:46 pm, Karl Denninger wrote: > Hi folks; > > I've been running 4.x quite happily for some time, and am trying to > set up a box with 5.3 that hopefully will end up being a viable > platform to move over to. > > Tried on both 5.3-RELEASE and 5.3-STABLE (built this evening) > > Having some problems here... > > First, I discovered that vinum isn't "quite right" with 5.3. Ok, so > I moved to "gvinum", but ran into some really bizarre behavior there > too, where it was detaching subdisks apparently at random and on a > rebuild would occasionally crash with some really wild results. It > also doesn't load-balance reads (barf). All this was discovered > after I spent an afternoon getting it set up properly with the > "shadow" root and all. Bummer > > The instability is a real deal-breaker - this is supposed to > (eventually) be a production server, so it can't be "squirrelly". > > So, my next attempt (with a new, fresh load) was to give gmirror a > shot instead, since I only need Raid 1, and this looks like a > "better" option from that perspective given gvinum's squirrely and > not-all-there status at the moment. > > We.. the manual page (and the archives on the list here) > implies that I can do the following: > > 1. Set up the system on one of the two mirror disks. > > 2. In single user mode, use "gmirror label -v -b round-robin disk > ad4" to set up the pre-existing disk (with data on it), which I > booted from, as the "primary". > > 3. Then use "gmirror insert disk ad6" to add the secondary (mirrored) > disk, which will automatically sync it and bring them into a > consistent state. > > Only one small problem - the first command (in #2) fails, with: > > "Can't store metadata on ad4: Operation not permitted" > > This is true if the system is mounted read-only (in single user mode) > or read-write (in multiuser, with all filesystems mounted) > > Attempting to label the SECOND (bare) disk works, but of course > that's backwards and an "insert" would immediately destroy the > running system (I assume it would also fail with the same permission > error, but I've not tried it) - so that's not an option. > > I also tried it from the fixit disk, but the KLD cannot be loaded > from the fixit disk, and none of the commands work - so that appears > to not be an option either. > > How do you get this thing set up? The archives here (and man pages) > strongly imply that this works for a root filesystem and boot drive - > what am I missing? > > Need a Raid 1 solution that works to move over to the 5.x world out > here... I had a pentium 166 with four matched ide drives set up as Striped plexes that had better disk access than my current 1ghz system. I sure miss that! The only time FreeBSD let me down when they let stopped supporting vinum. Guess no OS is perfect -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Xorg 6.8.1
On Saturday 26 February 2005 01:19 pm, Gary Kline wrote: > On Sat, Feb 26, 2005 at 09:49:00PM +0100, Michael Nottebrock wrote: > > On Saturday, 26. February 2005 13:05, Godwin Stewart wrote: > > > On Sat, 26 Feb 2005 22:25:24 +1030, "Daniel O'Connor" > > > > > > <[EMAIL PROTECTED]> wrote: > > > > You don't need to update a port just because it depends on > > > > Xorg. The X API is quite stable so you can update just Xorg > > > > without expecting any problems. (I did XFree86 -> Xorg with > > > > zero problems for example) > > > > > > No, the problem's the other way round. Every time I want to > > > portupgrade something else, portupgrade also wants to upgrade > > > Xorg. > > > > edit /usr/local/etc/pkgtools.conf, find the HOLD_PKGS = [ line and > > change it to > > > > HOLD_PKGS = [ > > 'bsdpan-*', > > 'xorg-*', > > 'imake-*', > > ] > > > > I've been using that for a long time now, since Xorg 6.8.1 breaks > > vt-switching for me. > > Tweaking pkgtools.conf may help me if I move back to XFree, > and it's looking like I have no choice. xorg autoconfigs > itself to run at too high a res and nothing I do fixes it. > So, without highjacking this thread _too_ much, can anybody > give me the cmds to get back to XFree-4 on my 5.3 install? > > I tried several days ago and got fouled up. What xorg* > ports do I have to pkg_delete before I cd to > /usr/ports/x11/XFree-4 and type a 'make install'? > > thanks much, > > gary Try setting in /etc/make.conf X_WINDOW_SYSTEM=xfree86-4 There is an entry in /usr/ports/UPDATING about it. Upgrading with sysutils/portmanager should be able to reset all of your dependencies after that. -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Xorg 6.8.1
On Saturday 26 February 2005 02:49 pm, you wrote: > On Sat, Feb 26, 2005 at 01:38:22PM -0800, Michael C. Shultz wrote: > > Try setting in /etc/make.conf > > > > X_WINDOW_SYSTEM=xfree86-4 > > > > There is an entry in /usr/ports/UPDATING about it. > > > > Upgrading with sysutils/portmanager should be able to reset all of > > your dependencies after that. > > Thanks. I did make the change in make.conf, but only after > things began breaking when I tried to rebuild XFree86-4. > If/when I try again, I'll set that variable first! > > gary Gary, probably best to go with xorg anyways if your using 5-STABLE, but if you choose XFree86-4 for some reason I think portmanager will correctly rebuild all ports that depend on the XFree86-4 libraries. You wouldn't have to deinstall/reinstall everything manually. -Mike ___ 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 Boot CD Fails on PPRO 200 (BTX halted)
On Wednesday 02 March 2005 08:48 pm, Edwin Brown wrote: > I've built 5.3 Stable as of tonight 03/02/2005 with the following in > make.conf > > CPUTYPE=i686 > CFLAGS=-02 -pipe > > It was built on a p4. CFLAGS should be -O2 not -02 and you really may want to concider just -O -Mike ___ 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 Boot CD Fails on PPRO 200 (BTX halted)
On Wednesday 02 March 2005 09:09 pm, Edwin Brown wrote: > I didn't cut and paste that. I had to copy everything by hand. It's > correct in the make.conf. > > Best, > > Edwin > OK, did you try just using -O? There is a note about that in the make.conf file. -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Linking with CUPS Issue
On Thursday 03 March 2005 02:04 am, Jake Stride wrote: > I have had a look on google and the archives and although I have seen > people with a similar issue I have not been able to find an answer to > the issue I have. > > I am trying to compile the magicolor 2430DL printer dirvers and keep > running into the following error: > > [EMAIL PROTECTED] make > Linking rastertokmlf... > /usr/bin/ld: cannot find -lcups > *** Error code 1 try ls -l /usr/local/lib/libcups* to see if the libraries are in place if not install: /usr/ports/print/cups-base if they are try: ldconfig -m /usr/local/lib/ -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Apache Signal 11 (5.3-RELEASE-p3/4)
On Thursday 17 March 2005 10:28 am, Kyle Mott wrote: > I've already sent this question to freebsd-questions; forgive me if > this is the wrong list. > > This just very recently started to happen (and I haven't upgraded > Apache as of late either, or any other software for that matter). I > keep getting this in my kernel.log on 2 different hosts: > Mar 17 09:34:16 logsrv pid 38069 (httpd), uid 0: exited on signal 11 > (core dumped) > Mar 17 00:34:25 g1bs0n kernel: pid 9419 (httpd), uid 0: exited on > signal 11 (core dumped) > > Both hosts are running 'apache+mod_ssl-1.3.33+2.8.22' plus > 'php4-4.3.10', and a bunch of php modules that I don't want to list. > i was able to get Apache running on g1bs0n by not starting ssl; > however, Apache won't start on logsrv at all. > > Looking up man signal, SIGSEGV (11) is a segmentation violation. What > can cause this on 2 different machines that haven't been updated in a > while? I'm currently running a ports-cvsup, to verify that > apache+mod_ssl either does or does not need to be updated. > > > > -Kyle Mott Just a suggestion Build Apache with debug support, do a back trace on the .core file with GDB. That will let you narrow down the problem a bit. Then notify the ports maintainer. -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Apache Signal 11 (5.3-RELEASE-p3/4)
On Saturday 19 March 2005 04:58 am, Vlad wrote: > I have the same problem, started at some point since 5.3-p? > > I thought something is wrong with the particular server, but since > other people report the same issue, I started to doubt that. > > Apache has been built manually, so it has nothing to do with the > port. 1.3.33 Apache + mod_ssl + mod_perl > > Sorry, have no dumps. > > pid 70686 (httpd), uid 65534: exited on signal 11 > pid 58127 (httpd), uid 65534: exited on signal 11 > pid 58833 (httpd), uid 65534: exited on signal 11 > pid 30556 (httpd), uid 65534: exited on signal 11 > pid 35877 (httpd), uid 65534: exited on signal 11 > pid 95642 (httpd), uid 65534: exited on signal 11 > Below is from Karl Mott's trace after compiling with debug. If you did the same thing, compiled your Apache with debug then sent the trace to Apache's maintainer I'm sure he/she would be most grateful: (my analysis) The crash is likely happening here: ssl_engine_init.c:234 The remaining is interpreted this way http_main.c:5379 calls http_config.c:1664 which calls ssl_engine_init.c:234 (crash happens here I think ) from Karl's trace: > #11 0x28354fc0 in ssl_init_Module (s=0x809b038, p=0x809b010) at > ssl_engine_init.c:234 > #12 0x08055946 in ap_init_modules (p=0x809b010, s=0x809b038) at > http_config.c:1664 > #13 0x0805de5d in standalone_main (argc=2, argv=0xbfbfec60) at > http_main.c:5379 > #14 0x0805e647 in main (argc=2, argv=0xbfbfec60) at http_main.c:5767 -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Newbie Question About System Update
On Monday 18 April 2005 04:51 pm, Jim Campbell wrote: > I've been away from *NIX a few years. I have been playing with FreeBSD > for a week or so now with mixed results. I am using release 4.11 > because for some reason 5.3 has problems seeing my hard drives. 4.11, > Red Hat Linux and NetBSD have no such trouble. > > This afternoon I used the "Updating Sources with CVSup" in the FreeBSD > Cheat Sheets and everything worked as advertized. I believe that it > advised against using "make world" and suggested that I use "19.4.1 The > Canonical Way to Update Your System" in the Handbook. I went through > the following steps with no problem: > > # make buildworld > # make installworld > # mergemaster > # reboot This is how I do it: > # make buildworld > # make buildkernel > # make installkernel > # reboot > # make installworld > # mergemaster > # reboot -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RELENG_6 SATA drive error
I have one IDE and two SATA drives in my system. With FreeBSD 5.4 the system would not boot from the SATA drive so I use the IDE as the primary then mount the SATA drives in fstab. I tried upgrading to RELENG_6 and with the new kernel one of the SATA drives errors out and so can't be mounted. I don't have the error message using the 6.0 kernel but here is dmesg from 5.4 if it helps: ad4: 76319MB [155061/16/63] at ata2-master SATA150 ad6: 114473MB [232581/16/63] at ata3-master SATA150 It is at4 that is failing with 6.0, this drive never gives any problem under 5.4. Both SATA drives are plugged into the same really cheap addon pci card. I'll be happy to provide more detail if requested and I'm able. Thank you, -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RELENG_6 SATA drive error
> Michael C. Shultz wrote: > >I have one IDE and two SATA drives in my system. With > >FreeBSD 5.4 the system would not boot from the SATA > >drive so I use the IDE as the primary then mount > >the SATA drives in fstab. I tried upgrading to RELENG_6 > >and with the new kernel one of the SATA drives errors > >out and so can't be mounted. I don't have the error message > >using the 6.0 kernel but here is dmesg from 5.4 if it helps: > > > >ad4: 76319MB [155061/16/63] at ata2-master > >SATA150 > >ad6: 114473MB [232581/16/63] at ata3-master > >SATA150 > > > >It is at4 that is failing with 6.0, this drive never gives any problem > > under 5.4. Both SATA drives are plugged into the same really cheap addon > > pci card. > > > >I'll be happy to provide more detail if requested and I'm able. > > > >Thank you, > > > >-Mike > > On Tuesday 12 July 2005 11:36, Jayton Garnett wrote: > Are you using the correct cables? I had a problem when I changed system > cases and used the wrong cable when I put the drives back in (IDE cable > instead of a SATA cable) I now have FreeBSD 5.4-p3 booting up fine and > without error. I think this is a common problem, where people forget > about the minor details(I am sure we are all guilty of this at some time) Perhaps I was not clear in the original message: Both SATA drives work under 5.4, only one works under 6.0. -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Audigy LS and Netgear WG311 drivers
On Tuesday 06 September 2005 09:04, Brandon Beamer wrote: > I'm running FreeBSD 5.4. I have a Soundblaster Audigy LS and a Netgear > WG311 v3 wireless PCI card. The ath driver does not recognize the > Netgear card and the emu10k1 driver does not recognize the Audigy. I've > searched online and also found an "emu10kx" driver written by some guy, > but it doesn't recognize my specific chip id. > > Has anyone else had problems with these pieces of hardware, if so how > did you fix it/could you fix it. If not, does anyone have a wireless > card that they have working with FreeBSD so that I can go out and buy a > different one with confidence? I got the OSS comercial sound driver to work with an Audigy sound card but it wouldn't work when running X windows so I ended up giving the card away. That was nearly a year ago, maybe now the OSS driver works better? ref: http://www.opensound.com/freebsd.html -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HEADS UP! Debugging, SMP changed in RELENG_6
On Saturday 17 September 2005 21:00, Scott Long wrote: > All, > > I've turned off kernel deubgging (INVARIANTS, WITNESS, KDB) and malloc > debugging (the default is now 'aj) in the RELENG_6 branch in preparation > for 6.0-BETA5. I've also turned off SMP in the i386 and amd64 GENERIC > kernels and have added and SMP kernel config for those architectures. > All of these changes are nearly identical to what is in RELENG_5. All > of this was done to facilitate performance measurement of the upcoming > release and to recognize that our buglist is shrinking considerably and > thus the release will be coming soon. > > ### IMPORTANT ### > > If you are using a stock GENERIC kernel on amd64 or i386 and expect > multiple CPUs to be enabled, you must either switch to the SMP kernel > config, or add the 'options SMP' line back to the GENERIC config. > Multiple CPUs, including mutli-core and Hyperthreading, will only be > enabled when this option is included. Hyperthreading also requires > that you add the line 'machdep.hyperthreading_allowed=1' to > /boot/loader.conf. > > Given the growth of multicore offerings from AMD and Intel, the default > on SMP may change in future releases as SMP systems become ubiquitous. > Appropriate warning will be given on the mailing lists if this happens. > > Scott I've just spent the past few days trying to get 6.0 to work with my SATA drives with little results. Here is a DMESG when I booit with 5.4: ad0: 6149MB [13328/15/63] at ata0-master UDMA33 acd0: CDRW at ata1-master UDMA33 ad4: 76319MB [155061/16/63] at ata2-master SATA150 ad6: 114473MB [232581/16/63] at ata3-master SATA150 The drives work fine in 5.4, but with 6.0 ad4 errors out, you can see it with atacontrol but it can't be reinitialized and there is only /dev/ad4 but none of the slices. ad6 works ok during reads but anything more than very light writing and the system reboots. Given these drives work with 5.4 it seems a little more work needs to go into 6.0 before doing new releases I would hope. -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problems with PCI SATA controller (bug in ATA driver? both ATAng and ATAmkIII)
On Wednesday 19 October 2005 21:15, Brooks Davis wrote: > On Thu, Oct 20, 2005 at 04:30:48AM +0200, Alson van der Meulen wrote: > > (Please CC me in replies as I'm not a subscriber of this list) > > > > Update: I tested with an i810-based mainboard (Celeron 1GHz, RTL8139 > > ethernet, Promise SATAII 150 TX4 controller, 3 SATA disks in RAID 5, > > FreeBSD 6.0-RC1). It remained stable for two hours. I suspect this is > > because it has far less bandwith (iostat showed only about 3MB/s to the > > disks, as opposed to 12MB/s with the i915 mainboard). After I added a dd > > if=/dev/zero of=foo bs=128k (this increased the bandwidth usage to the > > disk to about 9MB/s according to iostat), it crashed in about 40 > > minutes. This suggests that it crashes because of the large amount of > > I/O. However, it's only about 10MB/s per disk (for three disks), so it > > doesn't seem to be that exotic to me. > > > > Since this is a completely different mainboard, it seems clearly a > > software issue to me. The built-in ICH6 controller works fine however, > > so it may be PDC*0518/SII311* specific (which basically means any PCI > > SATA controller available locally). > > The SII3112 is a piece of crap that won't work reliably. Order > something better (Soren recommends Promise cards). > > -- Brooks Why does the SII3112 work better in FreeBSD 5.4 than in 6.0? I have a Highpoint 1820 on order but it still bugs me having to toss hardware that worked in 5.4 inorder to keep current. -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Easy way to kill a 5.x/6.x box as a basic user.
On Thursday 27 October 2005 17:12, Carl Makin wrote:
> Morning All,
>
> I've been playing with some GIS software and 32Mb TIFF images. Running
> ImageMagick's "convert" utility under my normal user login to convert
> the image to gif or jpeg blows away the system every time. No panic
> seen on the console and no core dump found, the system just quietly
> reboots. Upon reboot /var is full and corrupt and takes ages for the
> background fsck to fix it so I normally boot into single user mode and
> do it myself.
>
> Is anyone else seeing this? I can happily supply an image that causes
> the problem if someone wants to try it.
>
>
> Carl.
>
Just a guess but it may be the software is opening too many files. Try
installing /usr/ports/sysutils/lsof then while your program is running
run lsof -c {watever you program name is} +r5. If you see screenfulls
of open files then thats the problem.
-Mike
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: burncd and dvd-drives
On Friday 04 November 2005 00:18, you wrote: > I was and am a great fan of the burncd utility. > Very fast, simple and cli.. > > But as almost any new computer is supplied with a dvd drive this nice > program has become quit useless. It does not support those drives. > > My question is: will it ever do? > > I mean, cd-rom drives are losing terrain with each day passed. > Or will I be "forced" to either buy an oldfashioned cdrom drive in my > new machines? ; or recompile for atapicam ? ; or any other solution? > > Maybe I ask for to much. I'm no programmer myself. I have no idea > whatsoever about the code changes needed in burncd to support at least > the burning of CD's. (dvd's are different). Why aren't you using cdrecord? http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-cds.html Pay attention to 16.6.9 Using the ATAPI/CAM Driver ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange warning while upgrading
On Sunday 06 November 2005 11:01, Guillaume R. wrote: > Hello > Today I decided to upgrade my box from 5.4 to 6.O. So I change the right > option in my stable-supfile and go through the process of upgrading. > I can't build the world, and the error message was: > "/usr/src/share/mk/bsd.compat.mk", line 36: warning: NOGAMES is deprecated > in favor of NO_GAMES. > So I remove /usr/obj only and retry. This time it works fine but in my .out > file (i used script in case it fails again) i could see those warnings a > lot and not only during the buildworld the same happen with the kernel > build and install and finally the installworld. > Does anyone got an idea where it comes from? > Thx That is a warning message, not an error. Look in /etc/make.conf you'll see somewhere in there NOGAMES, if you change it to NO_GAMES the message will go away. Do the same for all the other warnings ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: New user confused by need to do huge upgrade
On Monday 07 November 2005 15:49, Alistair wrote: > Hello, All > > I am a user of Linux for many years (and an aged BSD sysadmin from > 1985-1989), but laterly mainly use Gentoo. FreeBSD seemed to be a good > alternative, so I get the 6.0 release a few days after it was released. > > Being a Gentoo person, I like the ports system, but with limited time on > my hands, I also like the compiled packages. I can get a working system > from packages then compile my own ports as need or want be. Or so I > thought. > > I installed from two CDs, and got a working KDE system. Now, I want to > do Firefox from ports with my own make.conf for P4 optimisation. Good! > So, I sync with the sources using cvsup (just like emerge --sync) > change to the Firefox ports directory, type "make" and enter dependency > hell like has never been known before. Everything that depends upon > GTK2 must be updated before Firefox can be compiled! If you don't want to do an entire upgrade of gnome2 or KDE but just get Firefox right install sysutils/portmanager (version 0.3.2 is in ports right now) then run portmanager www/firefox It will upgrade the dependencies that just pertain to firefox first then either upgrade firefox or install it if you don't have it yet. When version 0.3.3 of portmanager gets into the ports tree (pr is submitted) you can do the entire kde/gnome upgrade with just portmanager -u -Mike > > I thought that FreeBSD would be more stable than Gentoo and Linux > distros in general. I now find that there is the most major release > step (5.4 to 6.0) and within a matter of a few days later, both Gnome > and KDE are subject to huge updates that require many hours (or maybe > days - it's not done yet) of CPU time. > > Maybe I am missing something. However, I just cannot see why this is > right. What I thought that FreeBSD would give me that Gentoo did not is > a coherent system within which deveopment was co-ordinated. Instead, I > seem to find the opposite. The core group can offer a major release of > the OS, while missing the fact that two hugely important development > groups are just days off their own major releases. > > Maybe there is a level of sanity I am missing as a newcomer to BSD, but > I would really like someone to tell me where to find it so that I can > stop having to use this bloody Windows laptop to post here ;-) > > Regards > A > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gnome-upgrade.sh
On Wednesday 09 November 2005 13:46, Paul T. Root wrote: > This script is one of the most frustrating things ever > written. > > I made a fresh install (from CD) of 6.0R. In the install > I added gnome2, sudo, and bash. That's it. Gnome came up fine. > bash is great, sudo works. > > Now, since gnome 2.12 is out, I want to upgrade to that. > Seems resonable. > > http://www.freebsd.org/gnome tells us not to use portupgrade > to upgrade gnome2. The upgrades get out of order. > > Ok fine, use gnome-upgrade.sh. And keep trying it says. > > I've run it better than a dozen times, now. It's still trying. > All day, I turn and look at it periodically, resolve whatever > problem it seems to be having and start it up again. > > 1 time it said that it was successful! Woo Hoo! Wait, 2 times, > it just finished... > > However it lies. What it's done is removed gnome completely. > > > The problem seems to lie in that downloads fail and so I get > a bunch of files in /usr/ports/distfiles that are not valid. > Using good old ftp, I grab the file needed and either build the > port and install or restart gnome-upgrade.sh > > I'm now assuming that since all gnome has been wiped off the > disk, that the thing to do is build/install the port directly. > Starting that up, I seem to be having the same downloading difficulties. As an alternative to gnome-upgrade.sh you may want to consider using sysutils/portmanager, all you need do is run portmanager x11/gnome2 It'll do the upgrade no problem, tested it twice now myself. -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gnome-upgrade.sh
On Wednesday 09 November 2005 14:41, Alistair wrote: > Michael C. Shultz wrote: > >On Wednesday 09 November 2005 13:46, Paul T. Root wrote: > >>This script is one of the most frustrating things ever > >>written. > >> > >>[Snip] > > > >As an alternative to gnome-upgrade.sh you may want to consider > >using sysutils/portmanager, all you need do is run > > > >portmanager x11/gnome2 > > > >It'll do the upgrade no problem, tested it twice now myself. > > > >-Mike > > Paul > > This script was the source of my many frustrations. On a dual-boot > Gentoo Linux (production) and FreeBSD (new) server, the script ran > night-after-night on a 2GHz P4 with no sign of completion. > > I admit that my experience of FreeBSD is limited, but my BSD experience > is sound and my Linux experience is extensive, but this one caught me out. > > I think it really is a documentation problem. As far as upgrading Gnome > is concerned, the message I got from the web site was that just running > the script was OK. It should have said, run this script to update > Gnome, but lots of functionaliity of your FreeBSD machine will be > unusable while it runs and it might take many days to complete, even on > a fast machine. > > Also, documentation of portmanager is almost entirely lacking. It is > not (AFAICT) mentioned in the handbook at all. > > I had such high hopes for FreeBSD 6 because earlier releases have been > so nearly ideal for one machine I have that shamelessly functions as > both a powerful 64-bit workstation and a file server. However, my > experience installing it on a 32-bit dual-boot-disc Gentoo Linux box has > been unsatisfactory (at least partly, if not mainly, my fault) so I > think I may do the safe thing and stick to Linux. > > Regards > Alistair > > 1973 MG Midget, with all the Frontline Spridget mods, except the K-Series! > That little monster can still better my 911 hands down in some tight > twisty bits! Here is a link to portmanager's submission for the handbook: http://portmanager.sunsite.dk/distfiles/ports-using.html see section 4.5.5.2 and the PR of the submission http://www.freebsd.org/cgi/query-pr.cgi?pr=88646 Then of course there is the man page portmanager(1) or its website http://portmanager.sunsite.dk -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gnome-upgrade.sh
On Wednesday 09 November 2005 18:26, Paul Root wrote: > Michael C. Shultz wrote: > > *** > > This message has been scanned by the InterScan for CSC-SSM and found to > > be free of known security risks. ***-*** > > port and install or restart gnome-upgrade.sh > > >> I'm now assuming that since all gnome has been wiped off the > >> disk, that the thing to do is build/install the port directly. > >> Starting that up, I seem to be having the same downloading difficulties. > > > > As an alternative to gnome-upgrade.sh you may want to consider > > using sysutils/portmanager, all you need do is run > > > > portmanager x11/gnome2 > > > > It'll do the upgrade no problem, tested it twice now myself. > > Interesting. The web page said specifically don't do portupgrade. I didn't say portupgrade, it is sysutils/portmanager > > My main problem is it's having trouble downloading, I think. I'm > not sure why. We found problems on our Pix (actually the new > ASA firewall) and the port the machine is on. We were getting half > duplex, but those are all fixed now. Curiously, command line ftp > never has a problem downloading, it's fetch (I think it's using fetch), > that can't seem to download. While your problem has nothing to do with gnome-upgrade.sh, portmanager is designed to automatically pickup from where it left off, so stopping and starting isn't a problem, and it won't remove a port until its replacement is successfully built so if the port didn't fetch you won't lose anything, portmanager will just move on to the next port that can be upgraded, it is very fail safe. -Mike Note: I removed [EMAIL PROTECTED] from the return address as it is a dupe of [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gnome-upgrade.sh
On Thursday 10 November 2005 09:42, Paul T. Root wrote: > I moved the machine to a DSL line here, and am running > portmanager. It seems to be working. > > We're going to investigate issues with this beta Cisco > ASA machine. I am very interested at how things go with your upgrade, please keep me informed. Just to let you know, the current version of portmanager is 0.3.3_2 if anything goes wrong check that first "portmanager -v". If any problems arise I am more than happy to work with you in solving them quickly. -Mike > > Michael C. Shultz wrote: > > *** > > This message has been scanned by the InterScan for CSC-SSM and found to > > be free of known security risks. ***-*** > > > > On Wednesday 09 November 2005 18:26, Paul Root wrote: > >>Michael C. Shultz wrote: > >>>*** > >>>This message has been scanned by the InterScan for CSC-SSM and found to > >>>be free of known security risks. ***-*** > >> > >>port and install or restart gnome-upgrade.sh > >> > >>>>I'm now assuming that since all gnome has been wiped off the > >>>>disk, that the thing to do is build/install the port directly. > >>>>Starting that up, I seem to be having the same downloading > >>>> difficulties. > >>> > >>>As an alternative to gnome-upgrade.sh you may want to consider > >>>using sysutils/portmanager, all you need do is run > >>> > >>>portmanager x11/gnome2 > >>> > >>>It'll do the upgrade no problem, tested it twice now myself. > >> > >>Interesting. The web page said specifically don't do portupgrade. > > > > I didn't say portupgrade, it is sysutils/portmanager > > > >>My main problem is it's having trouble downloading, I think. I'm > >>not sure why. We found problems on our Pix (actually the new > >>ASA firewall) and the port the machine is on. We were getting half > >>duplex, but those are all fixed now. Curiously, command line ftp > >>never has a problem downloading, it's fetch (I think it's using fetch), > >>that can't seem to download. > > > > While your problem has nothing to do with gnome-upgrade.sh, portmanager > > is designed to automatically pickup from where it left off, so stopping > > and starting isn't a problem, and it won't remove a port until its > > replacement is successfully built so if the port didn't fetch you won't > > lose anything, portmanager will just move on to the next port that can be > > upgraded, it is very fail safe. > > > > -Mike > > > > Note: I removed [EMAIL PROTECTED] from the return address as it is a > > dupe of [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gnome-upgrade.sh
On Thursday 10 November 2005 11:32, Paul T. Root wrote: > Things are running better now. I moved it to a dedicated > DSL line in my lab, and it's chugging along. > > I see an occasional g_vfs_done message fly across. Error 16 > on a read. > Something like > g_vfs_done: acd0[READ(offset=81920, length=2048) Error = 16 > > Opps, I crashed the machine. When I moved it, I unplugged the > USB DVD-RW and I had mounted one of the dist discs on there. > When I did a umount it paniced. My bad. > > acd0 would be the internal DVD drive. > > > It seems that problem with my network was indeed the > Cisco ASA box we're beta testing. We have the CSC module > installed which is a stand alone linux box running trend for > virus, intrusion, etc. And there is a bug in the ftp inspection. > Hangs things up. > > Ok, since I think the network is solved, I'll take this opportunity > to restart portmanager on the network. good luck :) -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gnome-upgrade.sh
On Friday 11 November 2005 01:43, Jan Grant wrote:
> Hope you don't mind me taking you up on your offer to someone else :-) -
> this is more of a feature request from a portupgrade user who'd like to
> migrate.
>
> On Thu, 10 Nov 2005, Michael C. Shultz wrote:
> > On Thursday 10 November 2005 09:42, Paul T. Root wrote:
> > > I moved the machine to a DSL line here, and am running
> > > portmanager. It seems to be working.
> > >
> > > We're going to investigate issues with this beta Cisco
> > > ASA machine.
> >
> > I am very interested at how things go with your upgrade,
> > please keep me informed. Just to let you know, the current
> > version of portmanager is 0.3.3_2 if anything goes wrong check
> > that first "portmanager -v". If any problems arise I am more
> > than happy to work with you in solving them quickly.
>
> I've been very interested in portmanager, but I'm facing a large
> migration task because I've come from a portupgrade environment (and the
> pain of migrating to portupgrade was bad enough :-) )
>
> Ideally I'd like to be able to manage my portupgrade rules and derive
> portmanager rules directly (at least for an interim period). There are a
> couple of things which stop me shifting over (which I'd like to do,
> since portupgrade still requires manual intervention too often). Note I
> don't have what I'd describe as a _complex_ portupgrade configuration,
> just a _large_ one.
>
> Firstly: unfortunately I believe that the wildcard-matching facility
> available in pkgtools.conf isn't available in portmanager (I can't tell
> from the man page or the sample, but it looks like that's not the case).
>
> My pkgtools.conf has hundreds(! - busy workstation) of entries along
> these lines - some entries apply to several ports, and the portupgrade
> toolset just basically uses the union of all matching rules:
>
> [[[
> '*/*' => 'BATCH=yes',
> '*/kde*' => 'WITH_KDE_DEBUG=yes',
> 'databases/p5-DBI' => 'WITH_PROXY=yes',
> 'deskutils/kdepim3' => 'WITH_KPILOT=yes',
> 'devel/gnomevfs2' => 'WITH_X11=yes',
> 'devel/sdl12' => 'WITH_X11=yes',
> 'devel/subversion' => 'WITH_PYTHON=yes WITH_MOD_DAV_SVN=yes
> WITHOUT_BDB=yes', ]]]
>
> ... and so on; so deskutils/kdepim3 gets built with
> BATCH=yes WITH_KPILOT=yes WITH_KDE_DEBUG=yes
> but more importantly, any future kde packages also get
> WITH_KDE_DEBUG=yes automatically.
>
> It'd be convenient if portmanager supported the same wildcard
> ability (it'd make the script to migrate settings from pkgtools.conf to
> portmanager much more straightforward).
>
> The second issue is the AFTERINSTALL feature of pkgtools.conf; although
> I make much less use of this, it's really handy to be able to specify
> things like:
>
> [[[
> AFTERINSTALL = {
> 'www/jakarta-tomcat5' => 'chmod a-x
> /usr/local/etc/rc.d/020.jakarta-tomcat*.sh', # ... etc
> }
> ]]]
>
> which let me encapsulate common small tweaks, post-installation.
>
> Do you have any suggestions about either of these? Lacking CFT at the
> moment or I'd dive into the source.
Port build options are covered in man portmanager(1). You didn't provide an
example where wild cards are used so I'm not sure what you mean there.
Here is how to handle this one:
> AFTERINSTALL = {
> 'www/jakarta-tomcat5' => 'chmod a-x
> /usr/local/etc/rc.d/020.jakarta-tomcat*.sh', # ... etc
> }
from portmanager(1) setting up pm-020.conf
#
# STOP/START these programs if they are updated
#
# Stop command will be run after program is built, before
# old installed version is removed
#
# Start command will be run after rebuilt program is
# installed and successfully registerd
#
# note:
# must have leading "/" in /{category}/{port dir}
# anything after /{category}/{port dir} is run as
# a sh shell command
#
#STOP|/mail/postfix /usr/local/sbin/postfix stop|
#START|/mail/postfix /usr/local/sbin/postfix start|
In your case you would do this:
STOP| www/jakarta-tomcat5 /usr/local/etc/rc.d/020.jakarta-tomcat*.sh|
Stopping/starting is a new feature just introduced in 0.3.3_3.
-Mike
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gnome-upgrade.sh
On Friday 11 November 2005 05:44, Jan Grant wrote: > On Fri, 11 Nov 2005, Michael C. Shultz wrote: > > On Friday 11 November 2005 01:43, Jan Grant wrote: > > > My pkgtools.conf has hundreds(! - busy workstation) of entries along > > > these lines - some entries apply to several ports, and the portupgrade > > > toolset just basically uses the union of all matching rules: > > > > > > [[[ > > > '*/*' => 'BATCH=yes', > > > '*/kde*' => 'WITH_KDE_DEBUG=yes', > > > 'databases/p5-DBI' => 'WITH_PROXY=yes', > > > 'deskutils/kdepim3' => 'WITH_KPILOT=yes', > > > 'devel/gnomevfs2' => 'WITH_X11=yes', > > > 'devel/sdl12' => 'WITH_X11=yes', > > > 'devel/subversion' => 'WITH_PYTHON=yes WITH_MOD_DAV_SVN=yes > > > WITHOUT_BDB=yes', > > > ]]] > > > > > > ... and so on; so deskutils/kdepim3 gets built with > > > BATCH=yes WITH_KPILOT=yes WITH_KDE_DEBUG=yes > > > but more importantly, any future kde packages also get > > > WITH_KDE_DEBUG=yes automatically. > > > > > > It'd be convenient if portmanager supported the same wildcard > > > ability (it'd make the script to migrate settings from pkgtools.conf to > > > portmanager much more straightforward). > > > > Port build options are covered in man portmanager(1). You didn't provide > > an example where wild cards are used so I'm not sure what you mean there. > > The asterisks in the snippet above are wildcards. When portupgrade looks > for the options to a port, it pattern-matches against all the entries. > The deskutils/kdepim3 is a simple example above. Silly me, I get it now. Not supported yet but I like the idea so am adding it to the things to do list. This one will be near the top. > > > Stopping/starting is a new feature just introduced in 0.3.3_3. > > Cheers, that's very handy. -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gnome-upgrade.sh
On Friday 11 November 2005 05:58, Jan Grant wrote: > On Fri, 11 Nov 2005, Michael C. Shultz wrote: > > [on wildcards in portmanager rules] > > > Silly me, I get it now. Not supported yet but I like the idea so am > > adding it to the things to do list. This one will be near the top. > > That's great! - especially since that pretty much makes it a mechanical > process to take pkgtools.conf and spit out a corresponding portmanager > config. > > Thanks Mike. I'll try to remember cc'ing you when I submit a change this. My guess is two days to a week, depends on if any new bugs are reported. -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gnome-upgrade.sh
On Friday 11 November 2005 05:58, Michael C. Shultz wrote: > On Friday 11 November 2005 05:58, Jan Grant wrote: > > On Fri, 11 Nov 2005, Michael C. Shultz wrote: > > > > [on wildcards in portmanager rules] > > > > > Silly me, I get it now. Not supported yet but I like the idea so am > > > adding it to the things to do list. This one will be near the top. > > > > That's great! - especially since that pretty much makes it a mechanical > > process to take pkgtools.conf and spit out a corresponding portmanager > > config. > > > > Thanks Mike. > > I'll try to remember cc'ing you when I submit a change this. My guess is > two days to a week, depends on if any new bugs are reported. > > -Mike One last thing, if you make a script that does the conversion, might I have a copy? Here is how I'll set up pm-020.conf to work: textproc/docproj|JADETEX=no| java/jdk14|-DMINIMAL| textproc/libxml2|THREADS=off SCHEMA=on MEM_DEBUG=off THREAD_ALLOC=off| */kde*|WITH_KDE_DEBUG=yes| */*|BATCH=yes| ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gnome-upgrade.sh
On Friday 11 November 2005 06:26, Jan Grant wrote: > On Fri, 11 Nov 2005, Michael C. Shultz wrote: > > On Friday 11 November 2005 05:58, Michael C. Shultz wrote: > > > On Friday 11 November 2005 05:58, Jan Grant wrote: > > > > On Fri, 11 Nov 2005, Michael C. Shultz wrote: > > > > > > > > [on wildcards in portmanager rules] > > > > > > > > > Silly me, I get it now. Not supported yet but I like the idea so am > > > > > adding it to the things to do list. This one will be near the top. > > > > > > > > That's great! - especially since that pretty much makes it a > > > > mechanical process to take pkgtools.conf and spit out a corresponding > > > > portmanager config. > > > > > > > > Thanks Mike. > > > > > > I'll try to remember cc'ing you when I submit a change this. My guess > > > is two days to a week, depends on if any new bugs are reported. > > > > > > -Mike > > > > One last thing, if you make a script that does the conversion, might I > > have a copy? Here is how I'll set up pm-020.conf to work: > > Surely. pkgtools.conf is actually a ruby script: I've no idea how > dynamically the rules are evaluated but something that works ona > prettystock bunch of settings should be close to trivial. Thank you. If it works well I might use it to have portmanager pick up settings from portupgrade "on the fly", or at least provide some sort of conversion command. Thanks :) -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gnome-upgrade.sh
On Friday 11 November 2005 07:23, Jan Grant wrote:
> On Fri, 11 Nov 2005, Michael C. Shultz wrote:
> > > > One last thing, if you make a script that does the conversion, might
> > > > I have a copy? Here is how I'll set up pm-020.conf to work:
> > >
> > > Surely. pkgtools.conf is actually a ruby script: I've no idea how
> > > dynamically the rules are evaluated but something that works ona
> > > prettystock bunch of settings should be close to trivial.
> >
> > Thank you. If it works well I might use it to have portmanager pick up
> > settings from portupgrade "on the fly", or at least provide some sort
> > of conversion command. Thanks :)
>
> Attached uses ruby to parse the pkgtools.conf (it relies on the
> portupgrade ruby package) - it'll spit out the appropriate sections
> (HOLD_PKGS, BEFOREBUILD, AFTERINSTALL and MAKE_ARGS) in what I think the
> portmanager format is (although the script is trivial, as you can see).
> Note that the MAKE_ARGS etc go through a hash/dictionary and
> consequently are unordered. A small snippet of the output I get from
> this:
>
> [[[
> CATEGORY/PORT|OPTION=| # do not delete this line!
>
> # Ignored packages from HOLD_PKGS
>
> IGNORE|bsdpan-*|
> IGNORE|x11/nvidia-driver|
> IGNORE|editors/openoffice*|
>
> # STOP entries come from BEFOREBUILD
>
>
> # START entries come from AFTERINSTALL
>
> START|/databases/postgresql7 chmod a+x
> /usr/local/share/postgresql/502.pgsql| START|/www/jakarta-tomcat5 chmod a-x
> /usr/local/etc/rc.d/020.jakarta-tomcat*.sh|
>
> # Package options from MAKE_ARGS
> # Note: pkgtools.conf will use the UNION of all matching lines
>
> security/gnupg|WITH_SUID_GPG=yes|
> devel/subversion|WITH_PYTHON=yes WITH_MOD_DAV_SVN=yes WITHOUT_BDB=yes|
> x11/kde3||
> deskutils/kdepim3|WITH_KPILOT=yes|
> www/gallery||
> www/rt*|WITH_FASTCGI=yes WITH_APACHE2=yes DB_TYPE=Pg DB_HOST=localhost
> DB_DATABASE=rt3 DB_USER=rt3| www/apache2|WITH_PROXY_MODULES=yes|
> multimedia/kdemultimedia*|WITH_LAME=yes WITH_XINE=yes WITH_MPEGLIB=yes|
> */*|BATCH=yes|
> java/jdk14|NATIVE_BOOTSTRAP=yes JAVA_HOME=|
> */kde*|WITH_KDE_DEBUG=yes|
> mail/exim|WITH_EXIMON=yes WITH_EXISCAN_ACL=yes WITH_TCP_WRAPPERS=yes
> WITH_PGSQL=yes WITHOUT_PERL=yes | ]]]
^^^
little glitch?
Works good, just one thing, portmanager has no dependencies, like to keep it
that way. How are you at awk? I use this awk script to do initial parsing of
the config file:
#!/bin/sh
#
# $1 = pm-020.conf $2 = output file name
#
echo "keyzzNULLzzvaluezzNULLzz" > $2;awk 'BEGIN{ FS = "|" } NF == 3 &&
$1 !~ /#/ && $1 !~ /CATEGORY\/PORT/ && $2 !~ /#/ {print $1 "zzNULLz
I'm no scripter so getting the above to work was painful ;)
-Mike
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gnome-upgrade.sh
On Friday 11 November 2005 07:29, Michael C. Shultz wrote:
> On Friday 11 November 2005 07:23, Jan Grant wrote:
> > On Fri, 11 Nov 2005, Michael C. Shultz wrote:
> > > > > One last thing, if you make a script that does the conversion,
> > > > > might I have a copy? Here is how I'll set up pm-020.conf to work:
> > > >
> > > > Surely. pkgtools.conf is actually a ruby script: I've no idea how
> > > > dynamically the rules are evaluated but something that works ona
> > > > prettystock bunch of settings should be close to trivial.
> > >
> > > Thank you. If it works well I might use it to have portmanager pick up
> > > settings from portupgrade "on the fly", or at least provide some sort
> > > of conversion command. Thanks :)
> >
> > Attached uses ruby to parse the pkgtools.conf (it relies on the
> > portupgrade ruby package) - it'll spit out the appropriate sections
> > (HOLD_PKGS, BEFOREBUILD, AFTERINSTALL and MAKE_ARGS) in what I think the
> > portmanager format is (although the script is trivial, as you can see).
> > Note that the MAKE_ARGS etc go through a hash/dictionary and
> > consequently are unordered. A small snippet of the output I get from
> > this:
> >
> > [[[
> > CATEGORY/PORT|OPTION=| # do not delete this line!
> >
> > # Ignored packages from HOLD_PKGS
> >
> > IGNORE|bsdpan-*|
> > IGNORE|x11/nvidia-driver|
> > IGNORE|editors/openoffice*|
> >
> > # STOP entries come from BEFOREBUILD
> >
> >
> > # START entries come from AFTERINSTALL
> >
> > START|/databases/postgresql7 chmod a+x
> > /usr/local/share/postgresql/502.pgsql| START|/www/jakarta-tomcat5 chmod
> > a-x /usr/local/etc/rc.d/020.jakarta-tomcat*.sh|
> >
> > # Package options from MAKE_ARGS
> > # Note: pkgtools.conf will use the UNION of all matching lines
> >
> > security/gnupg|WITH_SUID_GPG=yes|
> > devel/subversion|WITH_PYTHON=yes WITH_MOD_DAV_SVN=yes WITHOUT_BDB=yes|
> > x11/kde3||
> > deskutils/kdepim3|WITH_KPILOT=yes|
> > www/gallery||
> > www/rt*|WITH_FASTCGI=yes WITH_APACHE2=yes DB_TYPE=Pg DB_HOST=localhost
> > DB_DATABASE=rt3 DB_USER=rt3| www/apache2|WITH_PROXY_MODULES=yes|
> > multimedia/kdemultimedia*|WITH_LAME=yes WITH_XINE=yes WITH_MPEGLIB=yes|
> > */*|BATCH=yes|
> > java/jdk14|NATIVE_BOOTSTRAP=yes JAVA_HOME=|
> > */kde*|WITH_KDE_DEBUG=yes|
> > mail/exim|WITH_EXIMON=yes WITH_EXISCAN_ACL=yes WITH_TCP_WRAPPERS=yes
> > WITH_PGSQL=yes WITHOUT_PERL=yes | ]]]
>
> ^^^
> little glitch?
>
> Works good, just one thing, portmanager has no dependencies, like to keep
> it that way. How are you at awk? I use this awk script to do initial
> parsing of the config file:
>
> #!/bin/sh
> #
> # $1 = pm-020.conf $2 = output file name
> #
> echo "keyzzNULLzzvaluezzNULLzz" > $2;awk 'BEGIN{ FS = "|" } NF == 3 &&
> $1 !~ /#/ && $1 !~ /CATEGORY\/PORT/ && $2 !~ /#/ {print $1 "zzNULLz
>
> I'm no scripter so getting the above to work was painful ;)
>
> -Mike
Sorry I was being dumb. The ruby script is no problem, it will only run
if portupgrade is installed so a dependency won't have to be put on ruby.
-Mike
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gnome-upgrade.sh
On Friday 11 November 2005 08:32, Lowell Gilbert wrote: > "Michael C. Shultz" <[EMAIL PROTECTED]> writes: > > Works good, just one thing, portmanager has no dependencies, like to keep > > it that way. > > It's not necessary to consider that an issue: this functionality is > really only useful to someone who has had portupgrade installed > anyway. I just thought of that, thanks for confirming :) -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gnome-upgrade.sh
On Friday 11 November 2005 09:04, Lowell Gilbert wrote: > "Michael C. Shultz" <[EMAIL PROTECTED]> writes: > > On Friday 11 November 2005 08:32, Lowell Gilbert wrote: > > > "Michael C. Shultz" <[EMAIL PROTECTED]> writes: > > > > Works good, just one thing, portmanager has no dependencies, like to > > > > keep it that way. > > > > > > It's not necessary to consider that an issue: this functionality is > > > really only useful to someone who has had portupgrade installed > > > anyway. > > > > I just thought of that, thanks for confirming :) > > Yeah, my secret of success in programming is to not fool myself into > making things more complicated than I need to do. > > You could even leave the script out of the port completely, and just > include a URL to it in the pkg-message... Simple, quick and painless :) If users want to simply convert that is the way to go. I also had in mind a knob like this: WITH_PORTUPGRADE_CONF if selected then portupgrade's settings are just added to portmanager's each time portmanager is run so if folks want to experiment with each program settings don't get lost. -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: gnome-upgrade.sh
On Friday 11 November 2005 07:23, Jan Grant wrote: > On Fri, 11 Nov 2005, Michael C. Shultz wrote: > > > > One last thing, if you make a script that does the conversion, might > > > > I have a copy? Here is how I'll set up pm-020.conf to work: > > > > > > Surely. pkgtools.conf is actually a ruby script: I've no idea how > > > dynamically the rules are evaluated but something that works ona > > > prettystock bunch of settings should be close to trivial. > > > > Thank you. If it works well I might use it to have portmanager pick up > > settings from portupgrade "on the fly", or at least provide some sort > > of conversion command. Thanks :) > > Attached uses ruby to parse the pkgtools.conf (it relies on the > portupgrade ruby package) - it'll spit out the appropriate sections > (HOLD_PKGS, BEFOREBUILD, AFTERINSTALL and MAKE_ARGS) in what I think the > portmanager format is (although the script is trivial, as you can see). > Note that the MAKE_ARGS etc go through a hash/dictionary and > consequently are unordered. A small snippet of the output I get from > this: > > [[[ > CATEGORY/PORT|OPTION=| # do not delete this line! > > # Ignored packages from HOLD_PKGS > > IGNORE|bsdpan-*| > IGNORE|x11/nvidia-driver| > IGNORE|editors/openoffice*| > > # STOP entries come from BEFOREBUILD > > > # START entries come from AFTERINSTALL > > START|/databases/postgresql7 chmod a+x > /usr/local/share/postgresql/502.pgsql| START|/www/jakarta-tomcat5 chmod a-x > /usr/local/etc/rc.d/020.jakarta-tomcat*.sh| > > # Package options from MAKE_ARGS > # Note: pkgtools.conf will use the UNION of all matching lines > > security/gnupg|WITH_SUID_GPG=yes| > devel/subversion|WITH_PYTHON=yes WITH_MOD_DAV_SVN=yes WITHOUT_BDB=yes| > x11/kde3|| > deskutils/kdepim3|WITH_KPILOT=yes| > www/gallery|| > www/rt*|WITH_FASTCGI=yes WITH_APACHE2=yes DB_TYPE=Pg DB_HOST=localhost > DB_DATABASE=rt3 DB_USER=rt3| www/apache2|WITH_PROXY_MODULES=yes| > multimedia/kdemultimedia*|WITH_LAME=yes WITH_XINE=yes WITH_MPEGLIB=yes| > */*|BATCH=yes| > java/jdk14|NATIVE_BOOTSTRAP=yes JAVA_HOME=| > */kde*|WITH_KDE_DEBUG=yes| > mail/exim|WITH_EXIMON=yes WITH_EXISCAN_ACL=yes WITH_TCP_WRAPPERS=yes > WITH_PGSQL=yes WITHOUT_PERL=yes | ]]] Hey Jan, May I have a copy of your pkgtools.conf for testing purposes? Barring no more bugs to squash I'd like to start incorporating your script into portmanager tomorrow. I've decided to make a WITH_PKGTOOLS_CONF knob so if people compile that way portmanager just loads pkgtools.conf when it starts (using your script to do the translation). There will also be a command line switch that lets people use your script to add pkgtools.conf to the end of pm-020.conf if they prefer to go that way. -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Handbook DHCPD needs update?
On Sunday 27 November 2005 11:57, Mark Space wrote: > (This missive is going to both freebsd-stable and freebsd-doc.) > > Hi all, I just got done setting up my brand spankin' new FreeBSD 6 > (release) server for DHCPD, and I found an ommision in the online > handbook. I'm a newbie at FreeBSD but I'm pretty sure about this. > > In short, the handbook never mentions that one needs to add the > following lines to /etc/rc.conf: > > dhcpd_enable="YES" > dhcpd_ifaces="dc0" > > If one doesn't do that, the script that the handbook says to use to > start dhcpd won't work, even if you do it manually as the handbook > instructs: > > # /usr/local/etc/rc.d/isc-dhcpd.sh start > > > This won't work. This script snarfs values out of /etc/rc.conf, and > the default (in the script above) for dhcpd_enable is NO. Hence the > script alone won't start anything. (When you check the handbook, make > sure you scrolldown to section 24.5.7. The first part of the DHCP > section explains how to set up the client (dhclient). That part does > have the correct setup for /etc/rc.conf. Scroll down to the server > section, dhcpd, to see what I'm talknin' about.) > > Anyhoo, what's the best way to fix this? I could submit a patch, but it > might be faster for someone else. I've never submitted a patch to the > documentation. > > Peace, out. Might be better to post this in [EMAIL PROTECTED] -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Freebsd 5.3 screw up.... deleted /lib/libc.so.5
On Sunday 27 November 2005 16:42, ebm wrote: > After I deleted this very valuable file I realized what I did. Since I > don't have a old boot disk laying around is my only option to upgrade to > a newer version of freebsd? Try this: cd /usr/sbin ./sysinstall then install the minimal binary package afterwords to a cvsup/make buildworld to get current again -Mike ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic
On Thursday 08 December 2005 08:57, [EMAIL PROTECTED] wrote: > > From: Peter Jeremy <[EMAIL PROTECTED]> > > Date: 2005/12/08 Thu AM 01:34:42 PST > > To: Vizion <[EMAIL PROTECTED]> > > CC: Doug Barton <[EMAIL PROTECTED]>, freebsd-stable@freebsd.org > > Subject: Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic > > > > On Wed, 2005-Dec-07 13:34:53 -0800, Vizion wrote: > > >Well having run many very large scale projects myself I find it > > > difficult to accept either implication of this perspective. > > > > There's a massive difference between running a large commercial project > > and running a large open source project using volunteers. > > Not really I have done both and found that shared values and community > collaboration work the same. > > >On a commercial > > project, you can direct someone to do something and they have a choice of > > either doing it or finding another job. > > Well that kind of development environment (rule by dictat) does not work > very well. Developers are people who are engaged in a collaborative > process. If you encourage them to think like prima donas then they will > behave like prima donas rather than as part of an integrated team. > > >On a volunteer project, there's > > a limit to how far you can push someone to do something they don't enjoy > > before they just leave. > > Push has it limitations everywhere.. goals and communal rewards are better > in both volunteer and commercial projects. > > > > The first implication is that > > >we should be complacent about it and not seek to find a method to > > > improve the process. > > > > I don't think anyone is suggesting this. In my experience, the FreeBSD > > project is always open to process improvements - this is especially > > obvious in the documentation and release engineering areas. > > The question is about the degree of committment to process change not > whwther it is absent or present. The critique is there is tooo little > comitment to process change and too much resistance to greater > concentration on the quality of user docuimentation and the significance of > that work in the developmenmt cycle. > > > >>Most of our really top > > >>notch developers are actually very bad at documenting their work (I > > >> don't mean bad at being timely with it, I mean that they are bad at > > >> DOING it), and frankly their time is better spent elsewhere. > > > > > >That is a judgment call - franky my experience has been that developers > > > who are bad at ensuring their work is well documentated are second rate > > > rather than top rate developers. > > > > Software developers are notoriously poor at writing documentation for > > non-technical people. There are probably very few developers who > > enjoy writing end-user documentation (and can write). In my > > experience, especially on large projects, it's rare for developers to > > write the end-user documentation. > > NOTE I said" > F:ranky my experience has been that developers who are bad at > ENSURING > their work is well documentated are second rate rather than top rate > developers. The work of the technical writer needs to influence development > at the design stage! It does not matter whether the developer does or does > not write the the documentation but it does matter whether the developer is > COMIITED to both ensuring that there is proper documentation AND that the > documentation process is an integral part of the development process that > influences its outcome. > > >They may write a rough outline but > > it's the technical writers who actually do the documentation. > > The outline for user documentation needs to be structured BEFORE > development begins NOT as an afterthought. In a well structured > development environment documentation is part of DESIGN not post design > implementation . That is because thinking about end user at the design > stage is necessary if the outcome of the process is going to be user > centric. > > >The > > problem is finding people with technical writing skills who are > > interested in helping with FreeBSD. > > Freebsd needs to reorganize the way it develops if it is going to interest > techn ical writers. No technical writer wants to be associated with writing > documnets for developments that have been poorly designed for the end user. > Clearing up someone else's mess is no fun. If you treat technical writers > as people who come along afterwards and pick up yopur trash OF COURSE you > will not get them involved. You need to ask WHY it is difficult to get > them. It is because freebsd does not produce software with a focus on end > user satisfaction. This is a chicken and egg problem that can only be > solved by a fu8ndamental shift both the focus of development objectives and > the development process. > > > It's also worth noting that a number of FreeBSD developers are not native > > English speakers. It's probably unreasonable to expect them to write > > polished English documentation. > > > > >Wha
Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic
On Friday 09 December 2005 11:31, vizion wrote: > > -Original Message- > > From: Michael C. Shultz [mailto:[EMAIL PROTECTED] > > Sent: Friday, December 09, 2005 10:32 AM > > To: vizion > > Cc: 'Peter Jeremy'; 'Doug Barton' > > Subject: Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic > > > > On Friday 09 December 2005 09:39, vizion wrote: > > > > Vison, you are much better at writting florid prose on how and why > > > > FreeBSD is > > > > such an awful OS run by a team of Techies who care nothing about end > > > > users needs than you are at reading and comprehending simple > > > > instructions. > > > > > > > > What you write is almost believable, your writing skill is very good > > > > and > > > > > > convincing, only in this particualr case I know you are completely > > > > wrong > > > > > > and > > > > your failure to follow the simplest advice is why your machine is now > > > > non > > > > > > operational. Quit crying about non relevent issues and concentrate > > > > on solving your real problem - getting that darn machine to boot up. > > > > > > > > One last thought, name one OS that has better documentation than > > > > FreeBSD > > > > > > please, comercial or otherwise. Maybe there is such a beast, if so I > > > > am > > > > > > very > > > > curious to know what it is called. > > > > > > Mike > > > > > > Rather than replying to the list I am emailing you direct and cc onl;y > > > > the > > > > > individuals to whom you cc'd your original. > > > > > > Frankly I never ceased to be amazed at diversionary personalized > > > attacks that seem to be a regular occurrence on freebsd lists whenever > > > someone makes friendly but critical observations about freebsd. There > > > is a touchyness there which is a big deterrent to the engagement of > > > others > > > > and a > > > > > tendency to paternalize which, on rare occasions, is an unspeakably > > > ugly aspect of some freebsd interactions. > > > > > > I do not know the root cause of such over-defensiveness I am constantly > > > amazed when old timers do not recognize it. It is time to grow up and I > > > hope something will happen to discourage people from arguing ad > > > > personam. > > > > > Your remarks seem to have been written with the deliberate intention of > > > attacking the messenger rather than discussing the message. You did not > > > even aspire to achieving accuracy. > > > > > > The fact the my system did upgrade successfully from 5.3 to 5.4 by > > > following your advice does not give you the right to make false > > > > assumptions > > > > > about a failed upgrade from 5.4 to 6.0 that is due to a combination of > > > events that have nothing whatsoever to do with the topic under > > > > discussion, > > > > > advice that has been given or even freebsd or its documentation. It > > > > turns > > > > > out that a motherboard hardware failure was the casue of the upgrade > > > failure.. hence I have to do a total rebuild because the motherboard is > > > > no > > > > > longer available. > > > > And this is your excuse for attacking the FreeBSD organization? > > No and I have nott attacked "the organization". The c ritic of the way in > which documentation is not integrated ionto the freebsd development cycle > was made long before there was any motherboard failure. I do wish you > would stick to the facts. > > > > I'm sure > > > everyone feels bad for you that you have to get a new motherboard. I am > > confused as to how better coordination between developers and technical > > writers could have prevented it from failing though. > > I have not made that suggestion - only you have put forward that notion -- > come on laugh a bit - you are really being a bit wild and cranky over this > . The motherboard failure occurred after the discussion on > documentation not before you really are missing the point here. > > > > As for the use of perjorative terminology (florid prose) and false > > > accusations - I am really personally very disappointed in your > > > > reactions. > > > > > What you seemed to be saying was that you were unable
buildworld fails at sbin/ifconfig
I installed RELENG_4_9 from ftp5??.freebsd.org on 4 March then cvsup'ed stable and tried buildworld and received the following result. Other than buildworld fails everthing else seems to be running fine. I've tried searching the mail lists for anyone else with a similar problem and have come up with no results, seems most people load from CDROM, could that be why this only is failling for me? Thankyou. -Mike buildworld fails at: sbin/ifconfig message: cc -O -pipe -march=i486 -DUSE_IF_MEDIA -DINET6 -DUSE_VLANS - DUSE_IEEE80211 -DNS -Wall -Wmissing-prototypes -Wcast-qual -Wwrite- strings -Wnested-externs -I..-c /storage/usr.src/sbin/ifconfig/ ifconfig.c /storage/usr.src/sbin/ifconfig/ifconfig.c:244: `IFF_STATICARP' undeclared here (not in a function) /storage/usr.src/sbin/ifconfig/ifconfig.c:244: initializer element is not constant /storage/usr.src/sbin/ifconfig/ifconfig.c:244: (near initialization for `cmds[38].c_parameter') /storage/usr.src/sbin/ifconfig/ifconfig.c:245: `IFF_STATICARP' undeclared here (not in a function) /storage/usr.src/sbin/ifconfig/ifconfig.c:245: initializer element is not constant /storage/usr.src/sbin/ifconfig/ifconfig.c:245: (near initialization for `cmds[39].c_parameter') *** Error code 1 Stop in /storage/usr.src/sbin/ifconfig. *** Error code 1 Stop in /storage/usr.src/sbin. *** Error code 1 Stop in /storage/usr.src. *** Error code 1 Stop in /storage/usr.src. Actions taken: 1. searched stable mail group for ifconfig.c AND 244, no relevant results. Re sup'ed yesterday ( 5 march ) and today, no help. I am assuming I have a bad header file somewhere, anyone know where IFF_STATICARP is defined? -Mike ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
