Re: -current, racoon, ipsec
Grr... ok, that might be solved when putting IPSEC in the kernel config, but the second part still stands, I guess. (Why include libipsec code when it is in the base tree... they should be compatible) Just use the port. I presume the included copy of ipsec is there for other platforms. Which coredumps when there is no matching SPD in the list, but well,that's minor. The other thing is that I haven;t gotten a single encrypted session to work, but that will wait until after the holiday :) Mark -- Nice testing in little China... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current, racoon, ipsec
On Sat, 15 Jul 2000, Mark Huizer wrote: Grr... ok, that might be solved when putting IPSEC in the kernel config, but the second part still stands, I guess. (Why include libipsec code when it is in the base tree... they should be compatible) Just use the port. I presume the included copy of ipsec is there for other platforms. Which coredumps when there is no matching SPD in the list, but well,that's minor. The other thing is that I haven;t gotten a single encrypted session to work, but that will wait until after the holiday :) You should *definitely* talk to the KAME guys with any bugs you find in racoon. I have a couple of problems I discovered in my testing tonight prior to the 4.0 merge, and there are still 5 days until the ports freeze in which to correct them. *Any* help you can give to sumikawa-san will mean a better IPSEC-enabled 4.1-RELEASE. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current, racoon, ipsec
Grr... ok, that might be solved when putting IPSEC in the kernel config, but the second part still stands, I guess. (Why include libipsec code when it is in the base tree... they should be compatible) they are NOT compatible. security/racoon really needs to compile libipsec by itself. itojun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
weird application coredumps ....
Hi, Since a recent update of my CURRENT system i get weird coredumps from at least two applications which just worked fine previously. The two programs are tintin++ (mud-client) ... and licq (when trying to set myself to "away-mode"). I have tried recompiling/reinstalling both applications thinking it may have been caused by the new binutils import ... but i am still getting the exact same crashes. Is there anybody else there that is having these same symptoms, or someone that may have an idea of what might be going wrong ? -- Pascal Hofstee daeron @ shadowmere . student . utwente . nl Managers know it must be good because the programmers hate it so much. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weird application coredumps ....
On Sat, 15 Jul 2000, Pascal Hofstee wrote: Since a recent update of my CURRENT system i get weird coredumps from at least two applications which just worked fine previously. The two programs are tintin++ (mud-client) ... and licq (when trying to set myself to "away-mode"). Just a wild guess, but this could be because of the recently added /etc/malloc.conf options -- (which are just for debuging purposes for now...) -Paul. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/etc/defaults make.conf src/secure/lib/libcrypto Makefile Makefile.inc
On Sat, Jul 15, 2000 at 01:45:02PM +0900, Jun Kuriyama wrote: At Fri, 14 Jul 2000 02:18:21 -0700 (PDT), Peter Wemm [EMAIL PROTECTED] wrote: Be consistant about WITH_ vs MAKE_ flags. We have a precedent of using MAKE_foo for things like MAKE_KERBEROS etc. Use that. I managed to confuse myself last time and made make.conf different to the code. ;-( Hmm, my box failed with WITH_IDEA=YES and USA_RESIDENT=NO. Do you have any idea about this? it seems that parts of the build-system have switched to "MAKE_IDEA" and some parts still use "WITH_IDEA" ... try defining them both in /etc/make.conf (this is of course something that should be fixed) -- Pascal Hofstee daeron @ shadowmere . student . utwente . nl Managers know it must be good because the programmers hate it so much. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weird application coredumps ....
On Sat, Jul 15, 2000 at 11:36:30AM +0200, Paul Herman wrote: On Sat, 15 Jul 2000, Pascal Hofstee wrote: Since a recent update of my CURRENT system i get weird coredumps from at least two applications which just worked fine previously. The two programs are tintin++ (mud-client) ... and licq (when trying to set myself to "away-mode"). Just a wild guess, but this could be because of the recently added /etc/malloc.conf options -- (which are just for debuging purposes for now...) Well ... for a wild guess it was Right On Top ... After searching the freebsd-current mailling list i located the bit about malloc.conf ln -sf j /etc/malloc.conf --- fixed the problems i was having Thanks ... (maybe a HEADS UP in UPDATING ??) -- Pascal Hofstee daeron @ shadowmere . student . utwente . nl Managers know it must be good because the programmers hate it so much. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: New boot0 not work with ahc
On Fri, Jul 14, 2000 at 01:38:44PM -0700, John Baldwin wrote: Errm, do you have some more details? I sent you more details personally. The only difference I think is underlaying old HP Vectra BIOS to wich SCSI BIOS pass unknown int13 and HP Vectra BIOS hangs. -- Andrey A. Chernov [EMAIL PROTECTED] http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weird application coredumps ....
In message [EMAIL PROTECTED], Pascal Hofste e writes: On Sat, Jul 15, 2000 at 11:36:30AM +0200, Paul Herman wrote: On Sat, 15 Jul 2000, Pascal Hofstee wrote: Since a recent update of my CURRENT system i get weird coredumps from at least two applications which just worked fine previously. The two programs are tintin++ (mud-client) ... and licq (when trying to set myself to "away-mode"). Just a wild guess, but this could be because of the recently added /etc/malloc.conf options -- (which are just for debuging purposes for now...) Well ... for a wild guess it was Right On Top ... After searching the freebsd-current mailling list i located the bit about malloc.conf ln -sf j /etc/malloc.conf --- fixed the problems i was having No, not "fixing the problems", "obscuring the problems". The tintin++ code contains errors, and you should fix them. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weird application coredumps ....
In message [EMAIL PROTECTED] Pascal Hofstee writes: : Thanks ... (maybe a HEADS UP in UPDATING ??) I have an entry in UPDATING already, don't I? Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: weird application coredumps ....
On Sat, 15 Jul 2000, Pascal Hofstee wrote: ln -sf j /etc/malloc.conf --- fixed the problems i was having Thanks ... (maybe a HEADS UP in UPDATING ??) Nope, the new malloc flags are hilighting bugs in your application..they should be fixed, not ignored :-) (this was the whole point of setting those flags in -current, they've already found several other bugs) Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Build broken?
The build broke this morning, and is still broken as of a few moments ago. The problem is that systat tries to use the (apparently now missing) m_mtypes element of the mbstat structure: su-2.04# pwd /usr/src/usr.bin/systat su-2.04# make cc -O -pipe -march=pentium -I/usr/src/usr.bin/systat/../../sys -c /usr/src/usr.bin/systat/mbufs.c /usr/src/usr.bin/systat/mbufs.c: In function `showmbufs': /usr/src/usr.bin/systat/mbufs.c:111: structure has no member named `m_mtypes' /usr/src/usr.bin/systat/mbufs.c:112: structure has no member named `m_mtypes' /usr/src/usr.bin/systat/mbufs.c:133: structure has no member named `m_mtypes' /usr/src/usr.bin/systat/mbufs.c:134: structure has no member named `m_mtypes' *** Error code 1 Stop in /usr/src/usr.bin/systat. And yes, "make buildworld" stops with the same set of error messages. /usr/src/usr.bin/netstat handles this correctly. It does leave one wondering why this the mbuf type names aren't shared in some way - though these seem to be the only places that it's used. Thanx, mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Build broken?
* Mike Meyer [EMAIL PROTECTED] [000715 07:29] wrote: The build broke this morning, and is still broken as of a few moments ago. The problem is that systat tries to use the (apparently now missing) m_mtypes element of the mbstat structure: su-2.04# pwd /usr/src/usr.bin/systat su-2.04# make cc -O -pipe -march=pentium -I/usr/src/usr.bin/systat/../../sys -c /usr/src/usr.bin/systat/mbufs.c /usr/src/usr.bin/systat/mbufs.c: In function `showmbufs': /usr/src/usr.bin/systat/mbufs.c:111: structure has no member named `m_mtypes' /usr/src/usr.bin/systat/mbufs.c:112: structure has no member named `m_mtypes' /usr/src/usr.bin/systat/mbufs.c:133: structure has no member named `m_mtypes' /usr/src/usr.bin/systat/mbufs.c:134: structure has no member named `m_mtypes' *** Error code 1 Stop in /usr/src/usr.bin/systat. And yes, "make buildworld" stops with the same set of error messages. /usr/src/usr.bin/netstat handles this correctly. It does leave one wondering why this the mbuf type names aren't shared in some way - though these seem to be the only places that it's used. oops, I just applied a patch assuming the submitter had actually checked his delta thoroughly. I should have a fix asap unless Ian can supply one faster. sorry, -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
No Subject
subscribe freebsd-current subscribe cvs-all To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: rtld-elf
[Whew! Could you set your mail format to plain text next time? That MimeCroSoft stuff is awfully hard to read on real computers.] In article 00cf01bfed15$43ab2910$[EMAIL PROTECTED], Tony Johnson [EMAIL PROTECTED] wrote: Hmmm.. I have been experiencing a problem when I installworld with = freebsd-5.0. The install breaks with rtld-elf when the install put the = new copy of ld-elf.s0.1 onto my system. Most f my prgrams signal 11 = until I put the old ne back. Is there smething I was supposed t do = befre this?? Yours is the only trouble report I've seen for the new version of the dynamic linker. Please tell me exactly what kind of CPU your system has in it. Also please send me the output from "dmesg". Thanks, John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
In article [EMAIL PROTECTED], Sheldon Hearn [EMAIL PROTECTED] wrote: Warner, Mark says that this applies if you used CTM to get cvs's ,v files, not CTM. Also, he clarified the last sentence for me, by saying that it's the crypto ,v files that need to be removed and not the checked out crypto files. There has been a whole lot of confusing info floating around here. Let me try to straighten this out. 1. If you are using CVSup in checkout mode, you don't have a problem. Go away and don't read any more of this. :-) 2. If in the past you have been getting your crypto files from the US or Canada, you don't have a problem. Go away and don't read any more of this. 3. If you are running a CVSup mirror site, you don't have a problem. Go away and don't read any more of this. 4. If you use CVSup to fetch the "*,v" files and then use the "cvs" command to check out your source tree, then you need to delete the *checked out sources* in these trees: src/crypto src/eBones src/secure src/sys/crypto Then check out these sources again using the "cvs" command. Do NOT delete your "*,v" files -- they are perfectly fine. 5. If you are using CTM to receive the "*,v" files and then using the "cvs" command to check out your source tree, then I don't know whether you need to delete your ",v" files and replace them or not. Hopefully Mark will clarify this if he hasn't already done so. But you definitely DO need to delete your *checked out sources* in these trees: src/crypto src/eBones src/secure src/sys/crypto Then check out these sources again using the "cvs" command. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: **HEADS UP** if you used to cvsup the crypto repo from internat !
In article [EMAIL PROTECTED], Udo Erdelhoff [EMAIL PROTECTED] wrote: What about the non-US cvsup mirrors? Mirror sites don't have a problem, and they shouldn't do anything special. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
vika@mtu-net.ru
Âû õîòèòå çàáûòü î ñóåòå, îêóíóòüñÿ â ìèð ðîìàíòè÷åñêèõ ãðåç? Îòêðîéòå ïóòü ê íåáåñíîìó áëàæåíñòâó, îñòàâüòå áåñêîíå÷íûå ïðîáëåìû - ïðåëåñòíàÿ íèìôà ïðåäëàãàåò Âàì îòäîõíóòü, ðàññëàáèòüñÿ è óòîíóòü â îêåàíå áëàæåíñòâà è ñëàäîñòðàñòèÿ. Ìîå ñòðîéíîå òåëî è íåæíûå ðóêè ïîâåðãíóò Âàñ â ïó÷èíó íåçàáûâàåìûõ îùóùåíèé è, ïîñåòèâ ìåíÿ îäíàæäû, Âû áóäåòå âîçâðàùàòüñÿ ê âíîâü è âíîâü Âîò íåêîòîðûå âíåøíèå äàííûå: Âèêà - øàòåíêà, 21 ãîä, ðîñò 175 ñì, âåñ 52 êã, ðàçìåð îäåæäû 44, áþñò ¹3; Òåëåôîí: (095) 723-04-67 Ïðåäëàãàþ Âàì ïîñìîòðåòü ìàëåíüêèé ñòðèïòèç. show .exe
