Problems with COmpaq oonboard Symbios SCSI
I'm running FreeBSD on a Compaq Workstation Pro 400. The Compaq motherboard has an onboard Sybmios SCSI controller (like so many COmpaqs do) but also came with a SMART-2LS RAID controller which is what is being used to boot from. Now this all works fine, except for the fact that if I try to reboot the machine it requires the power to be physically turned off before it will boot again. If the machine is warm reset it will not get past the point in the BIOS where the onboard SCSI controller scans for drives. It simply freezes at that point and will not go any further. I first assumed that this was due to something odd the sym driver was doing when probing the device, so I built a kernel without it in. Same effect occurs :-( I;m currently running 4.2-STABLE on the machine (from a few days after the release) but the effect has existed since 4.2-RELEASE Anybody else seeing this ? -pcf. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
RE: Lucent IRQ mode problem
Sorry, forgot to inform about OS version: FreeBSD xxx.com 4.3-RELEASE FreeBSD 4.3-RELEASE #11 -Original Message- From: [EMAIL PROTECTED] [mailto:owner-freebsd- [EMAIL PROTECTED]] On Behalf Of John Andersson Sent: den 17 maj 2001 11:41 To: [EMAIL PROTECTED] Subject: Lucent IRQ mode problem Hi! I have a problem with the Lucent WaveLAN pccard inserted in a PCI pccard adapter (See log below for more specific information). I get the following error: pcic0: VLSI 82C146 at port 0x3e0 iomem 0xd irq 10 on isa0 pcic0: management irq 10 ... snip pccardd[87]: Card Lucent Technologies(WaveLAN/IEEE) [Version 01.01] [] matched Lucent Technologies (WaveLAN/IEEE) [(null)] [(null)] wi0: WaveLAN/IEEE 802.11 at port 0x240-0x27f irq 5 slot 0 on pccard0 ... snip pccardd[87]: wi0: Lucent Technologies (WaveLAN/IEEE) inserted. pccard:wi0: WaveLAN/IEEE inserted /kernel: wi0: tx buffer allocation failed --- ERROR --- /kernel: wi0: xmit failed pccardd[87]: pccardd started /kernel: wi0: device timeout /kernel: wi0: tx buffer allocation failed I have looked around on the net and found others with similar problems, most of the time does it seems to be some kind of IRQ conflict. I have tried lots of different IRQ on my computer, change the BIOS config to set the IRQ for the adapter and Lucent card to Legacy ISA (instead of PCI) and made sure that no other card have the same IRQ. Nothing seems to fix the problem. I have heard from someone else that had similar problem for Linux and they could fix it by changing irqmode to 0... Possibly has this something to do with different IRQ modes for PCI, ISA, and pccards. I have not found any similar option in FreeBSD, does it exists such an option somewhere or does it exists some other solution? TIA, John To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Administrative tag a possibility?
Mike Smith wrote: ... Say introducing a convention like '$!$' to denote an always to be acceptable change? No, not acceptable. In this case, mergemaster should be smart enough to notice that the file in question was unchanged before the merge, and just not irritate you in the first place. You've just won my vote! Nonetheless I think a simple pattern match like $!$ could've been implemented long ago - thus saving me uncounted q+i keypresses, whereas introducing smartness into a program might take a tad longer. Wasn't there a discussion on something like this ages ago? I seem to recall somebody suggesting MD5 checksums to see if a file has changed or not and acting acordingly. If you're worried about maintaining a database of checksums, why not place it in the file itself. Of course somebody'll mention recursion: if you grep -v CHECKSUM | md5 and compare with grep CHECKSUM, you've got something that works and is easy to maintain. Just my 2p worth :) Stewart. -- Stewart Morgan MEng AMIEEE Technical Director, Nameless-UK T: +44 117 974 55 44| A: The Production House F: +44 870 168 02 10|147a St. Michael's Hill E: [EMAIL PROTECTED] |Bristol W: www.nameless-uk.com |BS2 8DB To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Administrative tag a possibility?
Stewart Morgan wrote: Wasn't there a discussion on something like this ages ago? I seem to recall somebody suggesting MD5 checksums to see if a file has changed or not and acting acordingly. If you're worried about maintaining a database of checksums, why not place it in the file itself. Of course somebody'll mention recursion: if you grep -v CHECKSUM | md5 and compare with grep CHECKSUM, you've got something that works and is easy to maintain. That seems a little dangerous - perhaps some of the files will have md5 appearing in other lines for other reasons, and that would mess up this simple grep. Perhaps a more complicated tag in the file would be more appropriate. -- Stephen Montgomery-Smith [EMAIL PROTECTED] http://www.math.missouri.edu/~stephen To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Problems with COmpaq oonboard Symbios SCSI
Pete French [EMAIL PROTECTED] wrote: I'm running FreeBSD on a Compaq Workstation Pro 400. The Compaq motherboard has an onboard Sybmios SCSI controller (like so many COmpaqs do) but also came with a SMART-2LS RAID controller which is what is being used to boot from. Now this all works fine, except for the fact that if I try to reboot the machine it requires the power to be physically turned off before it will boot again. If the machine is warm reset it will not get past the point in the BIOS where the onboard SCSI controller scans for drives. It simply freezes at that point and will not go any further. I first assumed that this was due to something odd the sym driver was doing when probing the device, so I built a kernel without it in. Same effect occurs :-( I;m currently running 4.2-STABLE on the machine (from a few days after the release) but the effect has existed since 4.2-RELEASE Anybody else seeing this ? I have a Compaq Workstation AP500 at the office that will not reboot with Win2000. Windows shuts down to the point where the screen goes blank, but *nothing* happens after that. I chalked it up to something flaky in the Compaq BIOS. Jim To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Problems with COmpaq oonboard Symbios SCSI
I have a Compaq Workstation AP500 at the office that will not reboot with Win2000. Windows shuts down to the point where the screen goes blank, but *nothing* happens after that. I chalked it up to something flaky in the Compaq BIOS. I flashed it to the newest BIOS on the RAID controllers and the machine iteslf. It works fine under Win98, I havent tried Win2000 yet (not after what it did to one of my other machines) -pcf. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
pppoe crashes in 4.3-stable (14.5.2000)
Title: pppoe crashes in 4.3-stable (14.5.2000) user-mode ppp crashes when calling pppoe-providers. After starting ppp I get the following error message linker_file_sysinit netgraph.ko failed to register! 17 Fatal Trap 12: page fault while in kernel mode The kernel panics, and i got no further errors in logfiles. Netgraph is built directly into the kernel, also the tun-interface. what's going wrong ?
Re: pppoe crashes in 4.3-stable (14.5.2000)
Title: pppoe crashes in 4.3-stable (14.5.2000) Can you tell me exactly what options you put in your kernel? - Original Message - From: Bernd Fürwitt To: [EMAIL PROTECTED] Sent: Tuesday, May 15, 2001 12:37 PM Subject: pppoe crashes in 4.3-stable (14.5.2000) user-mode ppp crashes when calling pppoe-providers.After starting ppp I get the following error messagelinker_file_sysinit "netgraph.ko" failed to register! 17Fatal Trap 12: page fault while in kernel modeThe kernel panics, and i got no further errors in logfiles.Netgraph is built directly into the kernel, also the tun-interface.what's going wrong ?
Re: Administrative tag a possibility?
On Thu, May 17, 2001 at 07:43:27AM -0500, Stephen Montgomery-Smith wrote: That seems a little dangerous - perhaps some of the files will have md5 appearing in other lines for other reasons, and that would mess up this simple grep. Perhaps a more complicated tag in the file would be more appropriate. Not to mention that, AFAIK, once you add the checksum to the file, the checksum would be different because the file is no longer the same, ne? I am not aware of a way to include a checksum in the file being checked. Jamie -- Stephen Montgomery-Smith [EMAIL PROTECTED] http://www.math.missouri.edu/~stephen To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Administrative tag a possibility?
On Thu, May 17, 2001 at 09:31:27AM -0400, Jamie Norwood wrote: On Thu, May 17, 2001 at 07:43:27AM -0500, Stephen Montgomery-Smith wrote: That seems a little dangerous - perhaps some of the files will have md5 appearing in other lines for other reasons, and that would mess Read 'CHECKSUM' instead of 'md5' and your statement is correct. up this simple grep. Perhaps a more complicated tag in the file would be more appropriate. Not to mention that, AFAIK, once you add the checksum to the file, the checksum would be different because the file is no longer the same, ne? I am not aware of a way to include a checksum in the file being checked. Ehm, the original poster did the grep -v thing to avoid this, and I'm reasonably sure he also envisioned using a better tag than 'CHECKSUM' - it's the principle that's worth implementing. Anyway, I also haven't got any patches so I'll shut up now. --Stijn -- Tact, n.: The unsaid part of what you're thinking. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Administrative tag a possibility?
Uh, please don't use BCC to send to the list, it makes replying a tad impossible. On Thu, 17 May 2001, Jamie Norwood wrote: On Thu, May 17, 2001 at 07:43:27AM -0500, Stephen Montgomery-Smith wrote: That seems a little dangerous - perhaps some of the files will have md5 appearing in other lines for other reasons, and that would mess up this simple grep. Perhaps a more complicated tag in the file would be more appropriate. Not to mention that, AFAIK, once you add the checksum to the file, the checksum would be different because the file is no longer the same, ne? I am not aware of a way to include a checksum in the file being checked. There was a method in the message you quoted: - # Some config file # $FreeBSD: blah$ # $MD5-Checksum: abcdefg8273912$ # Foo a=1 b=2 - # (this is a Perl regexp, but it's possible with grep, somehow, I'm sure. CHECKSUM=`grep -v \$MD5-Checksum(: [0-9a-fA-F]*)?\$$ | md5` and it's easy enough to use sed to replace $MD5-Checksum$ lines with CHECKSUM, and also compare the two... CVS could even be setup to automagically insert the checksum, as it does with the $FreeBSD$ lines currently.. (Doing so whilst observing the various weird -ki flags to disable $$ expansions would be more difficult, however). -- David Taylor [EMAIL PROTECTED] PGP signature
Re: dual fxp ethernet, one doesn't work
VK == Vivek Khera [EMAIL PROTECTED] writes: VK I have three machines with dual fxp NICs on them. They are all Dell VK PowerEdge 1550 boxes, running 4.3-STABLE from yesterday (I updated the VK kernel from today to see if the latest patches to if_fxp.c fixes the VK problem, but it didn't). Ok... It seems that three of my machines don't like this particular hub. Curiously, they all had a dual fxp built into the motherboard. A single fxp on motherboard works fine with this hub. It is a linksys 5 port 10baseT. I plugged these machines into a new 3com switch and they worked fine (except for not auto-detecting full-duplex). -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D.Khera Communications, Inc. Internet: [EMAIL PROTECTED] Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: NIS/YP problems after cvsupdate
On Wed, 16-May-2001 at 20:24:35 +0200, Hartmann, O. wrote: Hello. Three weeks ago I did the last cvsupdate on our FBSD 4.3 boxes. On our master NIS/YP server rpc.ypxfrd is running due the fact all of our boxes within this area run FreeBSD 4.3. Until last weekend an cron driven make in /var/yp worked well. It pragated the maps every hour to the slave servers. Last weekend I did the first cvupdate, yesterday the last one. First thing I realized was that fxp now needs miibus code (??). well, now our master NIS server is stock in sending to the slaves. It gets timeouts and messages about pending transaction processes. what happened? Why is that an up and down with NIS/YP in FreeBSD? Nothing has been changed within the configuartion since the last month, so I'm sure this problem is either triggered by 'obsolete configs', but nothing has been changed that way or by changes in networking or NIS/.YP related things. Has anybody realized the same? Can you send me the ouput of a yppush -vvv some_map_name ? How many slave servers are you using? -Andre To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Exim stops working in 4.3-STABLE because of Perl problems?
Dear colleguas, 2001.05.13 00:03 Sheldon Hearn wrote: It may take me a while to set up a similar environment to try this out. Although I'm the mod_perl FreeBSD port maintainer, I haven't noticed any problems in the development branch of FreeBSD. If anyone else comes up with something before I do, don't keep quiet. ;-) Ciao, Sheldon. Yesterday I upgraded my 4.3-Stable /usr/src tree (with CTM), make buildworld...buildkernel...installkernel...installworld. I have a line PERL_THREADED= true in my /etc/make.conf. cd to /usr/ports/mail/exim/; make install. All seems good. When starting Exim: exim% exim -bV segmentation fault There was a message from Juha Saarinen in exim-users mailing list with priblem description and workaround. As was recommended by Juha I commented out the string : WITH_PERL= yes in port's Makefile and rebuild Exim. It works now. I don't need an embedded Perl but it would be good to not have such a problems in future. With my best wishes, Dmitry -- - /\ ASCII Ribbon Campaign \ / - NO HTML/RTF in e-mail - NO Word docs in e-mail X -- / \ [ Dmitry George Golub [EMAIL PROTECTED] ] [ electronic mail system administrator+7(3422)917-324 ] --- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Exim stops working in 4.3-STABLE because of Perl problems?
On Fri, 18 May 2001, Dmitry G . Golub wrote: Dear colleguas, 2001.05.13 00:03 Sheldon Hearn wrote: Yesterday I upgraded my 4.3-Stable /usr/src tree (with CTM), make buildworld...buildkernel...installkernel...installworld. I have a line PERL_THREADED= true in my /etc/make.conf. cd to /usr/ports/mail/exim/; make install. All seems good. When starting Exim: exim% exim -bV segmentation fault There was a message from Juha Saarinen in exim-users mailing list with priblem description and workaround. As was recommended by Juha I commented out the string : WITH_PERL= yes in port's Makefile and rebuild Exim. It works now. I don't need an embedded Perl but it would be good to not have such a problems in future. Hi Dmitry, The other workaround (it only just qualifies as that..) is to uncomment the PERL_THREADED line in /etc/make.conf, and rebuild and reinstall world. I had Exim 3.20 working fine, with embedded Perl, in 4.2-RELEASE and 4.2-STABLE, with Perl threads enabled. Something must have changed in 4.3-STABLE, but I don't know what. -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: starting ipfw
John Polstra wrote: In article [EMAIL PROTECTED], Randy Bush [EMAIL PROTECTED] wrote: i am trying ipfw and hitting a start problem. the machine boots up as if it has not been loaded. but my /etc/rc.conf says firewall_enable=YES # Set to YES to enable firewall functionality firewall_script=/etc/ipfw.rules # Which script to run to set up the firewall ^^^ should be firewall_type No, firewall_type would be one of simple or open or whatever. It is read by /etc/rc.firewall assuming that firewall_script= /etc/rc.firewall. Otherwise it has no effect. Probably ity would help to know what is in your (Randy's) /etc/ipfw.rules -- Stephen Montgomery-Smith [EMAIL PROTECTED] http://www.math.missouri.edu/~stephen To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Release tag
This week I upgraded a 4.1-RELEASE machine to 4.3-RELEASE via source. I did: cvs upgrade -r RELENG_4_3_0_RELEASE /usr/src make buildworld make kernel make installworld mergemaster reboot No problems. Then I upgraded to the new extra stable branch RELENG_4_3 via the same drill. But a uname -r still says 4.3-RELEASE. Would our illustrious cat-fur covered release engineer consider some slightly different tag to mark the difference between a system installed from the CDs and one that's tracking the security/bugfix branch? -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: digital camera
A cheap film camera and a scanner is still a better deal. I'm thinking of finally getting a digital camera. Is there one that seems to do better with freebsd? What about the software to move the pic(s) to the pc? Most of the cams seem to include Windows connectivity kits. Since I de-installed Windows a while ago, are there freebsd apps that work with digicams to transfer pics to pc? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
RE: Release tag
Did you make sure to recompile your kernel after the upgrade? !Dave David Andrzejewski Assistant Network Administrator Database Administrator Medical School Dept. of Pathology University of Wisconsin - Madison http://www.awyeah.net/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Chad R. Larson Sent: Friday, May 18, 2001 12:00 AM To: [EMAIL PROTECTED] Subject: Release tag This week I upgraded a 4.1-RELEASE machine to 4.3-RELEASE via source. I did: cvs upgrade -r RELENG_4_3_0_RELEASE /usr/src make buildworld make kernel make installworld mergemaster reboot No problems. Then I upgraded to the new extra stable branch RELENG_4_3 via the same drill. But a uname -r still says 4.3-RELEASE. Would our illustrious cat-fur covered release engineer consider some slightly different tag to mark the difference between a system installed from the CDs and one that's tracking the security/bugfix branch? -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: starting ipfw
firewall_enable=YES# Set to YES to enable firewall functionality firewall_script=/etc/ipfw.rules # Which script to run to set up the firewall $firewall_script is a script which is sourced from rc.network, not a configuration file for ipfw. The default is /etc/rc.firewall. Since /etc/ipfw.rules is likely not something that can be sourced by sh, you are getting errors. yup. the following works. firewall_enable=YES # Set to YES to enable firewall functionality firewall_type=/etc/ipfw.rules # Which script to run to set up the firewall firewall_flags=-q # Flags passed to ipfw when type is a file randy To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: digital camera
Though nowhere near as easy to use as Digital cameras. You still need to send the film off to be developed and then you'd better have a good scanner if you want the resulting images to look any good. I wouldn't even bother with that approach - whenever we get my girlfriend's pictures back (she's hopelessly wedded to the analog), we just get it on PhotoCD as well. - Jordan From: Leland [EMAIL PROTECTED] Subject: Re: digital camera Date: Thu, 17 May 2001 22:00:47 -0700 A cheap film camera and a scanner is still a better deal. I'm thinking of finally getting a digital camera. Is there one that seems to do better with freebsd? What about the software to move the pic(s) to the pc? Most of the cams seem to include Windows connectivity kits. Since I de-installed Windows a while ago, are there freebsd apps that work with digicams to transfer pics to pc? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: NIS/YP problems after cvsupdate
On Wed, 16-May-2001 at 21:30:36 +0200, Hartmann, O. wrote: On Wed, 16 May 2001, John Polstra wrote: Hello. Well, all of our FBSD boxes are equipted with Intel NIC (fxp) and 100MBit/full-duplex (the switches are also full duplex types). All other network facilities work well - only the master server isn't able to send out a transfer initiation to its slaves. when doing a 'ypinit -s MASTER-SERVER' on each client the client polls its maps successfully. This seems to be a problem of the ypxfrd daemon running on our master ... In the past I have had a similar, versy strange problem due the fact I compiled each part of the kernel and of the base sources of the base operating system with the option -march=i686 as a compileroption of CFLAGS and COPTFLAGS in make.conf. This triggered a very strange behaviour. This time this problem occured after a cvsupdate without changes in config matter ... :-( (I did make world and mergemaster only ...). Try this patch (no joke): --- libexec/rtld-elf/rtld.c.ORI Fri May 18 08:05:01 2001 +++ libexec/rtld-elf/rtld.c Fri May 18 08:03:24 2001 @@ -386,6 +386,8 @@ dbg(initializing key program variables); set_program_var(__progname, argv[0] != NULL ? basename(argv[0]) : ); +set_program_var(environ, dummy); +set_program_var(environ, dummy); set_program_var(environ, env); dbg(initializing thread locks); Maybe we should really reopen http://www.freebsd.org/cgi/query-pr.cgi?pr=12496 John, what do you think? -Andre :In article [EMAIL PROTECTED], :Hartmann, O. [EMAIL PROTECTED] wrote: : : Last weekend I did the first cvupdate, yesterday the last one. : First thing I realized was that fxp now needs miibus code (??). : : well, now our master NIS server is stock in sending to the slaves. : It gets timeouts and messages about pending transaction processes. : :Peter Wemm just fixed a similar problem on ref4.freebsd.org. He said :the cause of the problem was a full/half duplex mismatch between the :NIC and the switch. : :John :-- : John Polstra [EMAIL PROTECTED] : John D. Polstra Co., Inc.Seattle, Washington USA : Disappointment is a good sign of basic intelligence. -- Ch?gyam Trungpa : : -- MfG O. Hartmann [EMAIL PROTECTED] IT-Administration des Institut fuer Physik der Atmosphaere (IPA) Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinensaal) Tel: +496131/3924144 FAX: +496131/3923532 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message -- Division by zero error -- multiplying by zero to recover... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Old compiler (3.3-stable - 4-stable)
On Fri, May 18, 2001 at 03:56:55AM +0200, Roelof Osinga wrote: Alexey V. Neyman wrote: ... Not only that, even 3.5.1-RELEASE fails to compile world for RELENG_4. What about staying insecure for a few hours of make world on 4.2-RELEASE, if this worries you, you may turn on firewall, either enabling only trusted addresses or disabling all services in question, which were found to be insecure in 4.2-RELEASE (ftpd, ntpd...). That is not what I want to hear g. That my planned update route won't fly, I mean. As to the insecurity risks... nah, I won't loose any sleep over the slight and temporal insecurity. The worse that could happen is, well, what? Nothing springs to mind. We're not an interesting target to crackers. Anyway, the box is currently happily runing 3.5.1-STABLE. But you are saying that I should not go straight to the RELENG_4 tag. So what tag do you suggest? I've only done CVSups within the stable branches. and port and security ones naturally. So I don't know any other tags g. Couldn't find that page that listed the tags in the emanual either. I did look! Really. You should probably go to 4.1-Release or 4.2-Release first. Several reports indicate that they should work. The tags for those releases ar RELENG_4_1_0_RELEASE and RELENG_4_2_0_RELEASE respectively. -- Insert your favourite quote here. Erik Trulsson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
