localhost adress
Since my last current (FreeBSD renaissance.homeip.net 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Fri Nov 21 17:49:36 CET 2003), I couldn't use anymore local network program like mlnet (telnet localhost 4000) or squid as my adress is 81.65.xx.xx (from my modem-cable) instead of 127.0.0.1. I didn't have this trouble with -CURRENT on the 17th of November. Is it related to tcp hostcache or is something weird in my config ? Anthony. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What's changed relating to localhost then?
I've just updated to 5.2-BETA today and have noticed that my spamd is now rejecting all connections from spamc because they are not coming from 127.0.0.1 any more. It's now using my public IP address of 82.x.x.x: Nov 22 14:38:30 womble spamd[657]: unauthorized connection from 82-32-25-111.cable.ubr04.azte.blueyonder.co.uk [82.32.25.111] at port 49167 I noticed somebody reported a similar thing earlier. It was me, I'm glad not to be dumb. I note also that metacity takes ages to start. I'm waiting a new change to network code in order to compile another -CURRENT. I'm actually in the process of reverting to a -current of 2003.11.14.00.00.00 because my xl0 ethernet card is acting up as mentioned in another thread so I want to see if it works with that kernel. (Can't go further back due to statfs). Also one of my machines running 5.2-BETA just hung dead within 5 minutes of booting. I don't have DDB etc configured though so can't tell why. Matt. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgraded to CURRENT = system is dead
I got trapped in the mess too but finally repaired it with a livecd. Let's hope the path for 5.2 RELEASE will be smoother for the less adventurous of us. I just ran into this very same thing today on a brand new installation. Upon reboot I can't even get to a shell. Was rather hoping someone had some more information about this. Running the installation on an IBM xSeries 305 with a P4. Going to try the installation fresh with a cvsup back to Nov 1st to see how it goes. Thank the Unix gods this wasn't a production machine. Antoine Jacoutot wrote: Selon Dylan Wylie [EMAIL PROTECTED]: The idea is that you need to build a new kernel with the new sources before you install world. You built your kernel before building the sources, so your kernel is based on old source. Quoting from another message: make buildworld make buildkernel make installkernel reboot make installworld -- yes... but I get this during the installworld: /libexec/ld-elf.so.1: Shared object libedit.so.4 not found Stop in /usr/src :( I just tried it again from scratch but got the same error... ! If anyone has an idea... -- In theory, there is no difference between theory and practice. In practice, there is. - Yogi Berra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: GCC tickling obscure hardware bug or...?
On Fri, 2003-09-12 at 12:56, [EMAIL PROTECTED] wrote: Quoting Scott Reese [EMAIL PROTECTED]: Hello all, I'm rephrasing my previous question to reflect new findings in my situation in the hopes that someone may have an idea of what's going on here (see thread Internal compiler error in reload_cse_simplify_operands from earlier this week). In a nutshell, I have upgraded my machine to a PIV 2.4 GHz processor on a VIA P4B 400 motherboard with 512 MB Samsung 2700 DDRAM. I have a 300 Watt power supply with a ball-bearing fan and a Seagate 40 GB HD. The problem I'm having that I did not see with my PIII is that I'm getting intermittent internal compiler errors when attempting to compile anything (again, see previous thread for an example). I even did a fresh install of the system yesterday in order to rule out something random getting hosed causing problems with my compiler. Through experimentation, I've found that toggling the CFLAGS from -O to -O2 or vice-versa works around the problem (actually, I've had greater success leaving my CFLAGS set to -O2 -pipe and occasionally bringing them back to -O -pipe when I run into an ICE and then setting them back again). My hunch is that some hardware bug is being tickled by gcc somehow. I don't think it's the standard broken hardware thing because I've not received any signal 11/7/4 errors at all and the system runs wonderfully. So far it's been up for over 24 hours, compiling ports and running without a hitch. The only strangeness is the compiler's behavior. Also, I should mention that I added options DISABLE_PSE options DISABLE_PG_G to my kernel config but the ICE's still persist, though they seem to be less frequent now. Attached is my dmesg, please let me know if anyone would like any more information about this or if you have any idea what might be going on here. Thank you, Scott Whenever I've had problems like this, it's been either bad memory, or bad memory settings in bios. I'd check both of those things. Sonofagun...I just tweaked the RAM settings yet another time and turned the speed down to 133 (recommended 166 in the mobo manual) and that seems to be working so far. Sorry for the noise, folks. These are known problems in 5.1-RELEASE but have been dealt with in -current, I'm waiting for 5.2 too in order to remove both the options DISABLE_PSE and DISABLE_PG_G. Furthermore GCC have been also improved and should more correctly support P4 with optimization levels higher than -O. Please check this mailing-list archives for more information. Anthony. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Anyone use WINE at all anywhere?
I used wine on 5.1-RELEASE in order to convert some binary cdrom format other than .iso (all those nice .ccd, .nrg, ...). I tried playing on my own copy of Starcraft but didn't successed yet however I didn't take much time to work on it. Except old games or mirc32 (for my gf), I'm not so much interested in wine but rather in vmware. If you have any patch to try, you're welcome. Is the re ANYONE that uses wine on -current...? for that matter, a -current user that uses wine on 4.x? julian ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: still data corruption with 5.1-R on Intel Pentium 4
There have been threads about data corruption in RAM on P4 and other i386 machines on this list. I also observed the problem, on my laptop with 5.0-R. It seemed to go away with 5.1-R, on the laptop. Recently I upgraded my home PC which is a P4 2.0A from 4.8-R to 5.1-R. No problems at first. Until I ran portsdb -Uu. I got a couple mysterious SIG4 and SIG11. Just to be sure I rebooted and tried again, same result. I rebooted another time, this time with ACPI disabled, and tried again, still the same. Then I rebuilt my kernel with options DISABLE_PSE and DISABLE_PG_G, as suggested by Terry in the old threads: Bingo, everything is fine now, no more SIG4 or SIG11 during portsdb -Uu. It seems the workarounds that we have in 5.1-R are not effective enough. What do you think? I'm having some SIG4 too when doing the massive operation portsdb -Uu. I don't mind too much because it's usually only two make process which die however I would like to know if DISABLE_PSE and DISABLE_PG_G impacts performance or not and if it's specific to BSD. I tried lately rebuilding world and kernel with CPU_TYPE=p3 in order to be sure it was not due to gcc over-optimizing for p4, we will see. Anthony. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Preliminary ELF prebinding patches available.
I've implemented per-executable ELF prebinding: ftp://ftp.jurai.net/users/winter/patches/prebind.patch Initial performance measurements are very encouraging. Is it similar to Linux's prelink implementation ? How does it compare with (feature, performance) ? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Any news for PR kern/48369 ext2fs no-go in FreeBSD 5(regression over 4.7)?
Hi! Is anybody working on this critical bug? Do you know what's the source of the problem? According to the PR report, it seems that mount_ext2fs works on some 5.x system... Working fine with ext3 and 5.0-p7. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
