Re: Localization and locale()?
hi, In article [EMAIL PROTECTED] you wrote: JS I am currently writing several programs that, for one reason or another, JS need to be localized in various sections. On Solaris, I can see what JS choices I have by running 'locale -a'. However, all my attempts to find a JS similar function on FreeBSD 3.4 have failed. ls -l /usr/share/locale JS I would have searched the mailing list archives, but they are, of course, JS currently down. Also, my search through the handbook also only showed JS examples for Russian and German encoding (section 12). JS For my specific problem, I need access to the following three character JS sets: JS es_ES.ISO8859-1 es_ES.ISO_8859-1 JS pt.PT.ISO8859-1 pt_PT.ISO_8859-1 JS en_US.ISO8859-1 en_US.ISO_8859-1 JS And within my program (Perl), I need to use the setlocale() function JS imported from the POSIX module (actually, from the locale_h header file). JS If I run this on FreeBSD, will the program die on me due to the apparent JS lack of a locale function? If one is available, where can I get it from? I just checked -- localhe.h is present in /usr/include directory. JS And finally, if these character sets are not installed on my system, what is JS the best way to go about getting them on there? Any help or insight would JS be appreciated, so thanks! -- /* Alexey Zelkin[EMAIL PROTECTED]*/ /* Tavric National University [EMAIL PROTECTED] */ /* http://www.ccssu.crimea.ua/~phantom [EMAIL PROTECTED] */ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Megahertz pccard
In message [EMAIL PROTECTED] Chris Webb writes: : FWIW, I'm still see the mysterious loss of interrupts after a suspend or : hibernate on my Vaio N505X with a 3com Megahertz card (now running : -current cvsuped and built this morning). Yes. That 's because we need acpi in order to properly suspend/resume the chipsets on these machines... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ftp 10.10
On 2000-Feb-09 14:09:34 +1100, Yoshinobu Inoue [EMAIL PROTECTED] wrote: So I think I'll make small changes to getaddrinfo() for it to also support shortend form(such as 172.16 for 172.0.0.16 above), after some more wait, maybe today. In which case, could you also make the following change (untested) to netstat(1) to remove the ambiguity in address abbreviations: Wmmm, this might be reasonable, but are not there any hidden thought on this? My feeling is that both changes should be applied together, but it would be nice to get a broader range of views. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Missing input stats in if_tun.c
It seems that with rev 1.72 of /src/sys/net/if_tun.c, if_ibytes and if_ipackets are no long updated in tunread(). I don't know why this was taken out, but these stats were nice for programs like wmnet. The following patch restores this function and works for me, although I may be missing something; the commit log for 1.72 is rather terse =-) Thanks! Scott Index: if_tun.c === RCS file: /usr1/ncvs/src/sys/net/if_tun.c,v retrieving revision 1.73 diff -u -r1.73 if_tun.c --- if_tun.c2000/01/29 01:10:24 1.73 +++ if_tun.c2000/02/09 06:12:36 @@ -674,6 +674,9 @@ } else family = AF_INET; + ifp-if_ibytes += tlen; + ifp-if_ipackets++; + return family_enqueue(family, top); } To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ata-zip drive is useable again!
todays current kernel made the ata-zip drive useable again. -- Fritz Heinrichmeyer mailto:[EMAIL PROTECTED] FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Megahertz pccard
In message [EMAIL PROTECTED] Gerald Abshez writes: : ep0: No irq?! You have an irq conflict. Make sure that pccard.conf.sample lists only those IRQs that are definitely free on your machine. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ftp 10.10
In message [EMAIL PROTECTED] Peter Jeremy writes: : Since it's sort-of related: netstat(1) will drop trailing 0's from : the routes it prints out, ie 10.2.3.0/24 will print as 10.2.3/24 : (though route(8) won't accept 10.2.3/24 as an input). : : IMHO, having a 172.16 mean a network address of 172.16.0.0 or a : host address of 172.0.0.16 is somewhat confusing... So? Having "rover" mean rover.village.org or rover.freebsd.org is also confusing, no? It all depends on what the context is as to what something means. This is no different than that. It is no different than having rover mean different things in different contexts. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ftp 10.10
On 2000-Feb-09 12:39:01 +1100, Yoshinobu Inoue [EMAIL PROTECTED] wrote: IMHO, having a 172.16 mean a network address of 172.16.0.0 or a host address of 172.0.0.16 is somewhat confusing... ... So I think I'll make small changes to getaddrinfo() for it to also support shortend form(such as 172.16 for 172.0.0.16 above), after some more wait, maybe today. In which case, could you also make the following change (untested) to netstat(1) to remove the ambiguity in address abbreviations: --- /usr/src/usr.bin/netstat/route.cMon Jan 10 08:31:25 2000 +++ route.c Wed Feb 9 13:22:45 2000 @@ -743,12 +743,6 @@ } if (cp) strncpy(line, cp, sizeof(line) - 1); - else if ((i 0xff) == 0) - sprintf(line, "%lu", C(i 24)); - else if ((i 0x) == 0) - sprintf(line, "%lu.%lu", C(i 24) , C(i 16)); - else if ((i 0xff) == 0) - sprintf(line, "%lu.%lu.%lu", C(i 24), C(i 16), C(i 8)); else sprintf(line, "%lu.%lu.%lu.%lu", C(i 24), C(i 16), C(i 8), C(i)); (Actually, I suspect the above should use inet_ntoa(3)). Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ftp 10.10
So I think I'll make small changes to getaddrinfo() for it to also support shortend form(such as 172.16 for 172.0.0.16 above), after some more wait, maybe today. In which case, could you also make the following change (untested) to netstat(1) to remove the ambiguity in address abbreviations: Wmmm, this might be reasonable, but are not there any hidden thought on this? As I checked the cvsweb, this code seems to be there from the beginning. I feel discussing and trying this after 4.0 will be safer, because this contradiction have been there for a long time. Yoshinobu Inoue } if (cp) strncpy(line, cp, sizeof(line) - 1); - else if ((i 0xff) == 0) - sprintf(line, "%lu", C(i 24)); - else if ((i 0x) == 0) - sprintf(line, "%lu.%lu", C(i 24) , C(i 16)); - else if ((i 0xff) == 0) - sprintf(line, "%lu.%lu.%lu", C(i 24), C(i 16), C(i 8)); To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000208-SNAP -- make world fails(/usr/src/tools/install.sh)
On Tue, 8 Feb 2000, John W. DeBoskey wrote: I've just installed a 4.0-2208-SNAP on a test machine, sources current as of 9am EST for the make world/make release. The following command fails almost immediately: cd /usr/src make world I would would do a cvsup first before making world. See /usr/share/examples/cvsup/standard-supfile. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: wierd audio properties..
On Tue, 8 Feb 2000, f.johan.beisser wrote: the card itself is a crystal CS 4232 (if i remember correctly) and had performed fine with OSS drivers under 3.4 (but didn't recieve audio from linux binaries). i have a card with a CS4232 chip in it also, but i have a different problem.. audio will only play once, after you play one thing and stop it audio cant get to the card anymore, mp3123 or xmms will just sit there.. the old pcm driver worked great for me, its been like this in current since some time in december. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
rpc.lockd... is done.
Amitha (the person who has been working on the lockd code) has finished most of his work. There are still some issues with handling async locks and cancel messages. Also we were not able to implement the full NLM protocol as the FreeBSD kernel does not currently request NFS locks (we should fix that ASAP). This code is *ALPHA*. Even we will not be running it on production servers in the near future. PS: the tarball is at "http://www.cs.rpi.edu/~crossd/FreeBSD/lockd-2208.tar.gz" PPS: I would like to set this up in CVS for everyone's ease, could someone please tell em how to do this, and to make it available via cvsup? (We already have a complete FreeBSD cvsup mirror at cvsup.cs.rpi.edu, this would just be another "module", right? -- David Cross | email: [EMAIL PROTECTED] Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ftp 10.10
also support shortend form(such as 172.16 for 172.0.0.16 above), after some more wait, maybe today. In which case, could you also make the following change (untested) to netstat(1) to remove the ambiguity in address abbreviations: Wmmm, this might be reasonable, but are not there any hidden thought on this? My feeling is that both changes should be applied together, but it would be nice to get a broader range of views. Yes, but about getaddrinfo(), I think it is backing to original(gethostbyname) behaviour before 1 month ago, rather than changing. Cheers, Yoshinobu Inoue Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: 4.0-20000208-SNAP -- make world fails(/usr/src/tools/install.sh)
Hi,
While updating the src on the newly installed machine would work,
it doesn't answer the real problem. The 'make release' target
in /usr/src/release is responsible for creating the src tarball
which should (and actually does) contain the tools directory.
The problem is that sysinstall is not actually untarring the
stools.* files (actually only stools.aa). The following patch
to dist.h and dist.c appear to fix the problem:
Index: dist.c
===
RCS file: /mirror/ncvs/src/release/sysinstall/dist.c,v
retrieving revision 1.166
diff -u -r1.166 dist.c
--- dist.c 2000/02/08 04:07:00 1.166
+++ dist.c 2000/02/09 05:14:16
@@ -119,6 +119,7 @@
{ "ssys", "/usr/src", SrcDists, DIST_SRC_SYS, NULL
},
{ "subin", "/usr/src", SrcDists, DIST_SRC_UBIN, NULL
},
{ "susbin","/usr/src", SrcDists, DIST_SRC_USBIN, NULL
},
+{ "stools","/usr/src", SrcDists, DIST_SRC_TOOLS, NULL
+ },
{ NULL },
};
Index: dist.h
===
RCS file: /mirror/ncvs/src/release/sysinstall/dist.h,v
retrieving revision 1.46
diff -u -r1.46 dist.h
--- dist.h 2000/01/04 05:06:22 1.46
+++ dist.h 2000/02/09 05:13:29
@@ -54,7 +54,7 @@
#define DIST_SRC_INCLUDE 0x00020
#define DIST_SRC_LIB 0x00040
#define DIST_SRC_LIBEXEC 0x00080
-/* 0x00100 */
+#define DIST_SRC_TOOLS 0x00100
#define DIST_SRC_RELEASE 0x00200
#define DIST_SRC_SBIN 0x00400
#define DIST_SRC_SHARE 0x00800
Thanks,
John
On Tue, 8 Feb 2000, John W. DeBoskey wrote:
I've just installed a 4.0-2208-SNAP on a test machine, sources
current as of 9am EST for the make world/make release.
The following command fails almost immediately:
cd /usr/src make world
I would would do a cvsup first before making world. See
/usr/share/examples/cvsup/standard-supfile.
- Donn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
any ideas on Vortex?
Just wondering, does anyone know if we will have a working driver for the Aureal Vortex soundcard by the time 4.0 is released? I'm just curious because I thought the driver for this card was supposed to be finished a long time ago.. = | Kenneth Culver | FreeBSD: The best OS around.| | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| = To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc and /usr/lib/libstdc++.so.3
John Polstra wrote: In article [EMAIL PROTECTED], Maxim Sobolev [EMAIL PROTECTED] wrote: Donn Miller wrote: I am running the lastest -current (just did a cvsup followed by a make world last night). I am getting these link errors when trying to compile the developement version of kdesupport, which I obtained thru cvsup. (KDE uses cvsup for its development versions.) I get the following errors. I have also installed the latest development snapshot of gcc 2.96 into /usr/local/bin, and I don't get these errors. gmake[5]: Entering directory `/usr/home/dmmiller/compile/kde/kdesupport/odbc/uni xODBC/odbcinst/cmd' /bin/sh ../../../../libtool --silent --mode=link gcc -mpentium -O3 -pipe -s -o odbcinst odbcinst.o ../libodbcinst.la ../../lst/libuodbclst.la /usr/lib/libstdc++.so.3: undefined reference to `exception type_info function' [...] gmake[5]: *** [odbcinst] Error 1 Absolutely the same is here on just builded/installed -current. Interesting that two days ago I had compiled kdesupport w/o this problem on the -current system compiled on February 3. Therefore bug in question was introduced during Feb 3 - Feb 8 period. Are you sure you're not just hitting this problem described in src/UPDATING? 2124: The default way that virtual tables in our default C++ No, because since 2124 I've recompiled both world (several times actually) and all C++ libs used by the kde. If you will read my previous message thoughtfully, you will notice that after Jan 24 I had successfully compiled kdesupport on system builded/installed on Feb 3. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
GNATS???
Hi, Does anyone could clarify approximate date when the GNATS is expected to be fixed? Thanks, Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ata-zip drive is useable again!
It seems F. Heinrichmeyer wrote: todays current kernel made the ata-zip drive useable again. I know, I committed the fix yesterday, I even mailed you so :) -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc and /usr/lib/libstdc++.so.3
In article [EMAIL PROTECTED], Maxim Sobolev [EMAIL PROTECTED] wrote: John Polstra wrote: Are you sure you're not just hitting this problem described in src/UPDATING? 2124: The default way that virtual tables in our default C++ No, because since 2124 I've recompiled both world (several times actually) and all C++ libs used by the kde. If you will read my previous message thoughtfully, you will notice that after Jan 24 I had successfully compiled kdesupport on system builded/installed on Feb 3. Sheesh, chill out. I'm just trying to help you. I did read your message "thoughtfully." That's why I wrote, "Are you sure ...?" rather than, "Hey dumbo, read UPDATING!" I thought (and still think) you might possibly have missed rebuilding one of the libraries. 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: gcc and /usr/lib/libstdc++.so.3
On Wed, 9 Feb 2000, John Polstra wrote: In article [EMAIL PROTECTED], Maxim Sobolev [EMAIL PROTECTED] wrote: No, because since 2124 I've recompiled both world (several times actually) and all C++ libs used by the kde. If you will read my previous message thoughtfully, you will notice that after Jan 24 I had successfully compiled kdesupport on system builded/installed on Feb 3. That's my experience also. I just rebuilt the world on Feb 8, and I rebuilt Qt, which KDE uses, last night. No dice. I still get errors like /usr/lib/libstdc++.so.3: undefined reference to `exception type_info node' /usr/lib/libstdc++.so.3: undefined reference to `exception virtual table' /usr/lib/libstdc++.so.3: undefined reference to `__builtin_vec_new' Sheesh, chill out. I'm just trying to help you. I did read your message "thoughtfully." That's why I wrote, "Are you sure ...?" rather than, "Hey dumbo, read UPDATING!" I thought (and still think) you might possibly have missed rebuilding one of the libraries. I rebuilt what I thought were the libs I needed, which would be Qt. I don't know if kdesupport is linking with Qt at all, but just in case, I rebuilt Qt with the new world. Still, the errors persist. I think the next step might be to notify the KDE developers via the comp.windows.x.kde NG. Is this bug specific to FreeBSD, or is it a bug of gcc 2.95.2 in general? Anyways, I installed gcc version 2.96 2131, which is a snapshot. I was able to compile kdesupport with no such errors. However, compiling kdelibs is what gives me the libstdc++ errors, because Qt is linked to gcc 2.95.2. I tried to compile Qt with gcc 2.96 2131. However, as I soon found out, the development version has a ghastly memory leak, which soon ate up all my memory and swap (64M+130M). So, I was unable to recompile Qt with 2.96 to complete the compilation. - Donn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: wierd audio properties..
On Tue, Feb 08, 2000 at 10:10:01PM -0600, Tim Seidl wrote: i have a card with a CS4232 chip in it also, but i have a different problem.. audio will only play once, after you play one thing and stop it audio cant get to the card anymore, mp3123 or xmms will just sit there.. the old pcm driver worked great for me, its been like this in current since some time in december. I also have a CS4232 and have the same problem. I think it's an AW32. -- Matthew Hunt [EMAIL PROTECTED] * Science rules. http://www.pobox.com/~mph/ * To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc and /usr/lib/libstdc++.so.3
John Polstra wrote: In article [EMAIL PROTECTED], Maxim Sobolev [EMAIL PROTECTED] wrote: John Polstra wrote: Are you sure you're not just hitting this problem described in src/UPDATING? 2124: The default way that virtual tables in our default C++ No, because since 2124 I've recompiled both world (several times actually) and all C++ libs used by the kde. If you will read my previous message thoughtfully, you will notice that after Jan 24 I had successfully compiled kdesupport on system builded/installed on Feb 3. Sheesh, chill out. I'm just trying to help you. I did read your message "thoughtfully." That's why I wrote, "Are you sure ...?" rather than, "Hey dumbo, read UPDATING!" I thought (and still think) you might possibly have missed rebuilding one of the libraries. OK, I've checked once more - all c++ libs I have in my /usr/lib:/usr/X11R6/lib:/usr/local/lib directories have been recompiled after c++ changes. Furthermore, when I'm forced this odbcinst to be linked against static libstdc++.a (by moving libstdc++.so* outside of /usr/lib) all problems dissapeared, so it could not be mixed libraries or problems in kdesupport itself. -Maxim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: any ideas on Vortex?
On Wed, 9 Feb 2000, Kenneth Wayne Culver wrote: | Just wondering, does anyone know if we will have a working driver for the | Aureal Vortex soundcard by the time 4.0 is released? I'm just curious | because I thought the driver for this card was supposed to be finished a | long time ago.. If my memory serves me correctly, the support for Vortex chipset family has been suspended due to lack of programming information. I hope the situation will get better when Aureal releases the technical documentation (which they promised to do on their website -- linux.aureal.com). Eugene -- Eugene M. Kim [EMAIL PROTECTED] "Is your music unpopular? Make it popular; make music which people like, or make people who like your music." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: GNATS???
Hi, Does anyone could clarify approximate date when the GNATS is expected to be fixed? The current target is late thursday PST, depending on a couple of factors. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: wierd audio properties..
Just wanted to say me too. I have not tried the old driver though. I just mostly did not worry about it, I just got a sound card, so I figured that it was because of the way I had something setup. Darren Wiebe [EMAIL PROTECTED] Matthew Hunt wrote: On Tue, Feb 08, 2000 at 10:10:01PM -0600, Tim Seidl wrote: i have a card with a CS4232 chip in it also, but i have a different problem.. audio will only play once, after you play one thing and stop it audio cant get to the card anymore, mp3123 or xmms will just sit there.. the old pcm driver worked great for me, its been like this in current since some time in december. I also have a CS4232 and have the same problem. I think it's an AW32. -- Matthew Hunt [EMAIL PROTECTED] * Science rules. http://www.pobox.com/~mph/ * To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ulimit weirdness
Is it just me, or did something change? It seems that now you can't raise resource limits after they've been lowered. I've had a 'ulimit -c 0' in my login profile for a while; previously when I needed to do debugging, I'd raise the limit to something reasonable at the shell prompt, and then debug away. Now it seems to be the case that once the (e.g,) core limit has been lowered, you can't raise it again. Am I just remembering this wrong? Here's a transcript from a "normal" user on a 4.0-current box, using /bin/sh: $ ulimit -a cpu time (seconds, -t) unlimited file size (512-blocks, -f) unlimited data seg size (kbytes, -d) 524288 stack size (kbytes, -s) 65536 core file size (512-blocks, -c) unlimited max memory size (kbytes, -m) unlimited locked memory (kbytes, -l) unlimited max user processes (-u) 531 open files (-n) 1064 sbsize (bytes, -b) unlimited $ ulimit -c 5000 $ ulimit -a cpu time (seconds, -t) unlimited file size (512-blocks, -f) unlimited data seg size (kbytes, -d) 524288 stack size (kbytes, -s) 65536 core file size (512-blocks, -c) 5000 max memory size (kbytes, -m) unlimited locked memory (kbytes, -l) unlimited max user processes (-u) 531 open files (-n) 1064 sbsize (bytes, -b) unlimited $ ulimit -c 6 ulimit: ulimit: bad limit: Operation not permitted $ ulimit -c 6000 ulimit: ulimit: bad limit: Operation not permitted $ Has something changed, or has it been like this all along? louie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Sig 11 installing XFree86
Hello, I was installing the 4.0 snapshot of 1/27/2000 when it asked if I wanted to install the XFree86 stuff.. I kept getting this error lib/X11/XF86Setup/texts/ja/help_keyboard.tcl lib/X11/XF86Setup/texts/ja/help_monitor.tcl lib/X11/XF86Setup/texts/ja/help_mouse.tcl lib/X11/XF86Setup/texts/ja/help_other.tcl lib/X11/XF86Setup/texts/ja/help_intro.tcl lib/X11/XF86Setup/texts/ja/help_modeselect.tcl man/man1/XF86Setup.1.gz man/man1/xmseconfig.1.gz 137 blocks sysinstall in free(): warning: junk pointer, too high to make sense. sysinstall in free(): warning: junk pointer, too high to make sense. sysinstall in free(): warning: junk pointer, too high to make sense. DEBUG: Signal 11 caught! That's bad! I was able to install it via /stand/sysinstall, but not from the install menu originally. I'm formatting that same machine tonight, and I'm installing the 2/09/2000 snapshot, and will report if I still get this error. Jeff Palmer [EMAIL PROTECTED] System Admin of my HOME machines, cuz I'm not smert enough to do it for a living. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS-UP, upcoming changes to ipfw: keep-state
[Bcc to -net as also relevant there] People, in the next day or so, with Jordan's approval, and in response to many queries i got about this, i am going to commit to -current (and then to -stable when it settles a bit) some ipfw patches which make the firewall stateful (only if you use the new features; otherwise ipfw behaves as usual). This will let you write things like (taken from a live -current): rizzo# ipfw show 00100 313 15907 allow tcp from any to any keep-state setup 002000 0 deny tcp from any to any 65535 1433 309926 allow ip from any to any ## Dynamic rules: 00100 279 13151 tcp 131.114.9.26 513 - 131.114.9.236 where the 'Dynamic rules' part is generated as a result of a match of rule 100. This should be useful to protect slow machines from attacks such as stream.c and the like. Also, the code should be fully integrated with bridging and dummynet. I would like people to give a try to the new code, point out bugs and possibly suggest enhancements if they have some ideas. The way the code works now: dynamic rules match the tuple protocol, dst/src port, dst/src ip They are stored in a hash table, whose size is configurable through a sysctl variable (default is 256). The max number of dynamic rules is limited with another sysctl variable (default 1000, but it can easily go up 2 orders of magnitude i think). When the max # of dynamic rules is reached, new ones are not added until the old ones expire. The expire time is set again using sysctl variables, defaults to a few seconds for SYN/FIN/RST and minutes for regular packets. (this will not save you from idle ssh/telnet connections timing out, but i have seen the same behaviour with commercial firewalls as well). Dynamic rules are checked before the whole ruleset (although by the time i commit the code there will be probably a way to tell exactly at which point to check dynamic rules). Note, this behaviour is probably appropriate for a workstation. If you build a router+ipfw/bridge+ipfw, then you might want different types of dynamic rules which only check part of the headers -- HERE I NEED YOUR INPUT!!! And of course, if you need some customized version of this stuff, feel free to talk to me. cheers luigi ---+- Luigi RIZZO, [EMAIL PROTECTED] . Dip. di Ing. dell'Informazione http://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) Mobile +39-347-0373137 ---+- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ftp 10.10
On 2000-Feb-08 22:05:32 +1100, "Daniel C. Sobral" [EMAIL PROTECTED] wrote: Yoshinobu Inoue wrote: If IPv4 dotted-decimal forms are given, getaddrinfo() calls finally inet_pton(). inet_pton() is defined in RFC2553 and it does not permit non-standard IPv4 dotted-decimal, such as 10.10 Do people have troubles with this change? Not supporting 127.1 violates POLA. Me, I hate 127.1. But some people expect it to work, and they have every right to. Since it's sort-of related: netstat(1) will drop trailing 0's from the routes it prints out, ie 10.2.3.0/24 will print as 10.2.3/24 (though route(8) won't accept 10.2.3/24 as an input). IMHO, having a 172.16 mean a network address of 172.16.0.0 or a host address of 172.0.0.16 is somewhat confusing... Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ftp 10.10
On 2000-Feb-09 15:29:45 +1100, Yoshinobu Inoue [EMAIL PROTECTED] wrote: Yes, but about getaddrinfo(), I think it is backing to original(gethostbyname) behaviour before 1 month ago, rather than changing. In which case I withdraw my request that netstat change at the same time. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Snapshots?
Hi all! Charon wrote: At 02:40 PM 2/7/00 -0500, Forrest Aldrich wrote: Why have there not been any snapshots of 4.0-CURRENT since 01/27/2000? (current.freebsd.org). Just curious... I've been trying to get a recent snapshot for a while too... There haven't been any since 2127 on ftp7.de.freebsd.org either. Well, 4.0 is in code freeze since then. Probably that's the reason why they stopped producing snapshots. [.] Actually, I think it's a problem with the non-existence of /etc/make.conf in the chroot()d release environment I haven't tried making release myself though :0( -- Brian [EMAIL PROTECTED][EMAIL PROTECTED] http://www.Awfulhak.org [EMAIL PROTECTED] Don't _EVER_ lose your sense of humour ! [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
IPv6 scoped addr format change
Hello, FYI, recently IPv6 scoped addr format is changed on KAME repository, so the change is also merged to 4.0. The scoped addr format is typically used for IPv6 link local addr. before: addr@scope after:scope%addr Before change, they were printed like this, %netstat -r -f inet6 Routing tables Internet6: DestinationGatewayFlags Netif Expire localhost localhost UH lo0 fe80::@xl0 link#1 UC xl0 fe80::@lo0 fe80::1@lo0Uc lo0 fe80::@gif0fe80::210:5af Uc gif0 After the change, they are printed like this, Internet6: DestinationGatewayFlags Netif Expire localhost localhost UH lo0 xl0%fe80:: link#1 UC xl0 lo0%fe80:: lo0%fe80::1Uc lo0 gif0%fe80::gif0%fe80::210:5af Uc gif0 The change from '@' to '%' is to prevent the confusion with existent notations such as user@host. And IPv6 addr is long and tend to be truncated at the end just seen as above gif0 Gateway, so placing scope part at the top of addr will be convenient. Cheers, Yoshinobu Inoue To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
/usr/ports/ too big?
Hello, I'm just doing a cvsup update of my system and -as many times before- I realize that /usr/ports/ takes a lot of time and also disk space to sync. # du -sk /usr/ports 71118 /usr/ports Am I the only one being little annoyed by this fact? Would it make any sense to offer some "castrated" ports repository. Like putting a target "overview" into each /usr/ports/*/Makefile to list all available subdiretories. Then, with some other command, one could fetch the current port's directory from the cvs server to install the port. Do these thoughts make any sense? Kai -- kai voigt hamburger chaussee 36 24113 kiel 04 31 - 22 19 98 69 http://k.123.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /usr/ports/ too big?
* Kai Voigt [EMAIL PROTECTED] [000209 13:26] wrote: Hello, I'm just doing a cvsup update of my system and -as many times before- I realize that /usr/ports/ takes a lot of time and also disk space to sync. # du -sk /usr/ports 71118 /usr/ports Am I the only one being little annoyed by this fact? Would it make any sense to offer some "castrated" ports repository. Like putting a target "overview" into each /usr/ports/*/Makefile to list all available subdiretories. Then, with some other command, one could fetch the current port's directory from the cvs server to install the port. Do these thoughts make any sense? Yes, this has been desired for some time, but without an actual implementation we're kinda stuck. :) -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: /usr/ports/ too big?
: a target "overview" into each /usr/ports/*/Makefile to list all available : subdiretories. Then, with some other command, one could fetch the : current port's directory from the cvs server to install the port. : : Do these thoughts make any sense? : :Yes, this has been desired for some time, but without an actual :implementation we're kinda stuck. :) : :-Alfred It's a nice problem to have, I guess :-) I really like the idea of having a target overview. It would be utterly trivial to have a module list in the Makefile and to change the dependancies to run 'make modulename' in the parent directory rather then in the subdirectory (which might not exist). There's only one person who can make something like this happen. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Upgrading to 4.0
[Redirected to -current] On Wed, Feb 09, 2000 at 11:49:30AM -0800, Cy Schubert wrote: Can FreeBSD be upgraded from 3.4-stable to 4.0-current from source. When I installed -current on my testbed I got a number of sig 12's (SIGSYS), e.g. fix one, reiterate, fix the next one, etc., that I finally gave up and installed 4.0-current from snapshot. The reason for asking is that I'm installing a console server in Vancouver, a 30 minute flight by helijet from Victoria. My options are to install -stable and subsequently install 4.1 from source, negating the requirement to travel to Vancouver to perform the installation, or install from CDROM or FTP requiring console access. Any thoughts? Without providing any in-depth details: 0. `uname -r' returns 3.x 1. make buildworld 2. make buildkernel 3. make installkernel 4. reboot with new kernel in signle-user mode 5. make -DNOINFO installworld 6. make buildkernel installkernel (again) 7. make installworld (again, without -DNOINFO) -- Ruslan Ermilov Sysadmin and DBA of the [EMAIL PROTECTED]United Commercial Bank, [EMAIL PROTECTED] FreeBSD committer, +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Upgrading to 4.0
In message [EMAIL PROTECTED], Ruslan Ermilov writes: [Redirected to -current] On Wed, Feb 09, 2000 at 11:49:30AM -0800, Cy Schubert wrote: Can FreeBSD be upgraded from 3.4-stable to 4.0-current from source. When I installed -current on my testbed I got a number of sig 12's (SIGSYS), e.g. fix one, reiterate, fix the next one, etc., that I finally gave up and installed 4.0-current from snapshot. The reason for asking is that I'm installing a console server in Vancouver, a 30 minute flight by helijet from Victoria. My options are to install -stable and subsequently install 4.1 from source, negating the requirement to travel to Vancouver to perform the installation, or install from CDROM or FTP requiring console access. Any thoughts? Without providing any in-depth details: 0. `uname -r' returns 3.x 1. make buildworld 2. make buildkernel 3. make installkernel 4. reboot with new kernel in signle-user mode 5. make -DNOINFO installworld 6. make buildkernel installkernel (again) 7. make installworld (again, without -DNOINFO) Excellent. I'll try it on my testbed and let you know how it goes. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX GroupInternet: [EMAIL PROTECTED] ITSD Province of BC "COBOL IS A WASTE OF CARDS." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ulimit weirdness
In article [EMAIL PROTECTED], Louis A. Mamakos [EMAIL PROTECTED] wrote: Is it just me, or did something change? It seems that now you can't raise resource limits after they've been lowered. I've had a 'ulimit -c 0' in my login profile for a while; previously when I needed to do debugging, I'd raise the limit to something reasonable at the shell prompt, and then debug away. Now it seems to be the case that once the (e.g,) core limit has been lowered, you can't raise it again. Am I just remembering this wrong? Yep, you're remembering wrong. You can raise the soft limit again, but not the hard limit. It's even documented in sh(1): ulimit [-HSacdflmnust] [limit] Set or display resource limits (see getrlimit(2)). If limit is specified, the named resource will be set; otherwise the current resource value will be displayed. If -H is specified, the hard limits will be set or displayed. While everybody is allowed to reduce a hard limit, only the supe- ruser can increase it. The -S option specifies the soft limits instead. When displaying limits, only one of -S or -H can be given. The default is to display the soft limits, and to set both the hard and the soft limits. If you want to lower the coredumpsize limit temporarily, use the soft limit like this: ulimit -Sc 5000 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
Dummy ethernet interface.
Is there some way to ifconfig up a dummy ethernet interface, one that will work like the loopback one (lo0) on FreeBSD? I'm playing around with a local caching named on a machine that has only lo0 and a ppp0 interface, and bind always replies with 'for authoritative replies ... blah blah' when I use host. I remember that having localhost.my.domain set to 127.0.0.1 and the reverse, but my (fictitious) hades.hell.gr - 10.0.0.1 seemed to solve this problem on linux. I looked through the LINT file in my sources [cvsuped: 7 Jan 2000], but could not find anything like that. Is there such a thing, or the time has come for me to start playing around with my kernel and ethernet drivers? A pseudo-ethernet device seems like a nice reason to start panicing my home PC, but I don't want to repeat other people's work if possible ;) -- Giorgos Keramidas, keramida @ ceid . upatras . gr For my public PGP key: finger [EMAIL PROTECTED] PGP fingerprint, phone and address in the headers of this message. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: HEADS-UP, upcoming changes to ipfw: keep-state
In article [EMAIL PROTECTED], Luigi Rizzo [EMAIL PROTECTED] wrote: This will let you write things like (taken from a live -current): rizzo# ipfw show 00100 313 15907 allow tcp from any to any keep-state setup 002000 0 deny tcp from any to any 65535 1433 309926 allow ip from any to any ## Dynamic rules: 00100 279 13151 tcp 131.114.9.26 513 - 131.114.9.236 where the 'Dynamic rules' part is generated as a result of a match of rule 100. Sounds cool, but could you please describe what it does? Apparently it adds a temporary pass rule between two endpoints, in response to a triggering rule that contains "keep-state". Is that right? I realize it's probably like ipfilter's keep-state feature. But that's not documented either. :-( 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, upcoming changes to ipfw: keep-state
Sounds cool, but could you please describe what it does? Apparently it adds a temporary pass rule between two endpoints, in response to a triggering rule that contains "keep-state". Is that right? correct, and this is what i tried to write in the second part of my HEAD-UP email... I realize it's probably like ipfilter's keep-state feature. But that's not documented either. :-( as a matter of fact i am just updating the ipfw manpage now... cheers luigi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ulimit weirdness
Yep, you're remembering wrong. You can raise the soft limit again, but not the hard limit. It's even documented in sh(1): Maybe the default in bash changed somewhere along the line (modifing the hard limit rather than the soft limit). Oh well, no problem. It's nice to know there's a reason for why something behave like they do, rather than ascribing some unexpected event to the passing of a random cosmic ray.. thanks, louie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: syscons: incorrect behavior of blinking cursor
On Wed, Feb 09, 2000 at 08:35:07PM +0200, Ruslan Ermilov wrote:
Hi!
1. Set cursor "blinking" or "destructive" (SC_BLINK_CURSOR)
2. Press Scroll Lock (cursor will go away)
3. Switch to another vtyX
4. Switch to the original vty, where you pressed Scroll Lock
5. Watch the cursor will appear at the same position as it was on vtyX.
The following patch fixes the problem.
--
Ruslan Ermilov Sysadmin and DBA of the
[EMAIL PROTECTED]United Commercial Bank,
[EMAIL PROTECTED] FreeBSD committer,
+380.652.247.647Simferopol, Ukraine
http://www.FreeBSD.org The Power To Serve
http://www.oracle.com Enabling The Information Age
Index: scvgarndr.c
===
RCS file: /usr/FreeBSD-CVS/src/sys/dev/syscons/scvgarndr.c,v
retrieving revision 1.5
diff -u -p -r1.5 scvgarndr.c
--- scvgarndr.c 2000/01/29 15:08:47 1.5
+++ scvgarndr.c 2000/02/09 23:52:53
@@ -225,10 +225,8 @@ vga_txtcursor(scr_stat *scp, int at, int
at%scp-xsize,
at/scp-xsize);
} else {
- if (scp-status VR_CURSOR_ON)
- (*vidsw[adp-va_index]-set_hw_cursor)(adp,
- -1, -1);
scp-status = ~VR_CURSOR_ON;
+ (*vidsw[adp-va_index]-set_hw_cursor)(adp, -1, -1);
}
} else {
scp-status = ~VR_CURSOR_BLINK;
Index: syscons.c
===
RCS file: /usr/FreeBSD-CVS/src/sys/dev/syscons/syscons.c,v
retrieving revision 1.335
diff -u -p -r1.335 syscons.c
--- syscons.c 2000/01/29 15:08:49 1.335
+++ syscons.c 2000/02/09 23:52:53
@@ -1806,7 +1806,8 @@ scrn_update(scr_stat *scp, int show_curs
scp-cursor_pos));
}
}
-}
+} else
+ sc_remove_cursor_image(scp);
#ifndef SC_NO_CUTPASTE
/* update "pseudo" mouse pointer image */
Re: ulimit weirdness
On 2000-Feb-10 09:03:12 +1100, John Polstra [EMAIL PROTECTED] wrote: but not the hard limit. It's even documented in sh(1): ulimit [-HSacdflmnust] [limit] ... given. The default is to display the soft limits, and to set both the hard and the soft limits. I've been bitten by this in the past as well. IMHO, this behaviour violates POLA, even if it is POSIX(?)-specified. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Upgrading to 4.0
On Wed, Feb 09, 2000 at 04:36:07PM -0600, nathan wrote: I've also had problems upgrading from 3.4-RELEASE to 4.0 i have a dual proc system, and have been EAGERLY anticipating 4.0 so i can install WINE, VMWARE, etc my process went like this 1. boot normally 2. killall -TERM inetd 3. cd /usr/src 4. make -j8 -DNOPROFILE=true buildworld 5. make -j8 -DNOPROFILE=true installworld step 4 completed no problem... step 5, however, always failed... THEN, i had the long, undesirable task of restoring my system back to 3.4 ... later.. i tried rebooting to single mode to do step 5.. but again.. it failed. after seeing your steps.. it makes sense pre-build the kernel to 4.0 _before_ installing world. however... could you provide a little more info on steps 5, 6, 7 specifically.. what does the -DNOINFO do ( i can't find it on my system.. yet) -DNOINFO is documented in src/Makefile.inc1, it is required for successful -current installworld from 3.x due to bootstrapping problems (-current install-info(1) has two new options). and why repeat the kernel build/install AND the installworld?? Hmm, just to be 100% sure. I would also recommend buildworld/ installworld right after 3.x-4.0 upgrade. But it is really not required, since `buildkernel' builds the -current kernel with the -current (latest) compiler. also... if this should work... i wonder why the fbsd Handbook (www.freebsd.org/handbook/makeworld.html) details a very different process than this one. Because this process is a complex transition step, while handbook describes the usual X.Y-RELEASE - X.Y-STABLE case. Note, that ir also does not say anything about aout-elf transition. lastly.. are your steps 2 3 the same as cd /sys/i386/conf vi CONFIG_FILE cd ../../compile/CONFIG_FILE make depend make make install Nope. There are special `buildkernel', `installkernel' targets in the src/Makefile.inc1. They are different from the procedure above in that they compile the -current kernel with the -current compiler, built in a host environment (i.e. with 4.0 gcc from /usr/src built on 3.x). ??? thanks for ANY additional info you can provide... i've spent a week reading/compiling/reading/testing/crashing/etc etc etc Without providing any in-depth details: 0. `uname -r' returns 3.x 1. make buildworld 2. make buildkernel 3. make installkernel 4. reboot with new kernel in signle-user mode 5. make -DNOINFO installworld 6. make buildkernel installkernel (again) 7. make installworld (again, without -DNOINFO) -- Ruslan Ermilov Sysadmin and DBA of the [EMAIL PROTECTED]United Commercial Bank, [EMAIL PROTECTED] FreeBSD committer, +380.652.247.647Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: syscons: incorrect behavior of blinking cursor
On Wed, Feb 09, 2000 at 08:35:07PM +0200, Ruslan Ermilov wrote:
Hi!
1. Set cursor "blinking" or "destructive" (SC_BLINK_CURSOR)
2. Press Scroll Lock (cursor will go away)
3. Switch to another vtyX
4. Switch to the original vty, where you pressed Scroll Lock
5. Watch the cursor will appear at the same position as it was on vtyX.
The following patch fixes the problem.
Thank you for the report and patch.
While your patch seems to work, it looks to me it's slightly over-kill
for this problem; we shouldn't need to call sc_remove_cursor_image()
every time the screen is refreshed in scrn_upcate().
Because this problem is caused by exchange_scr() not removing the text
cursor when changing to the vty where the cursor is not currently
shown, we had better fix exchange_scr().
The attached patch is simpler and fixes the problem. I verified it
works here. Please test. Thank you.
Kazu
Index: syscons.c
===
RCS file: /src/CVS/src/sys/dev/syscons/syscons.c,v
retrieving revision 1.335
diff -u -r1.335 syscons.c
--- syscons.c 2000/01/29 15:08:49 1.335
+++ syscons.c 2000/02/10 01:52:28
@@ -2335,6 +2337,8 @@
/* save the current state of video and keyboard */
sc_move_cursor(sc-old_scp, sc-old_scp-xpos, sc-old_scp-ypos);
+if (!ISGRAPHSC(sc-old_scp))
+ sc_remove_cursor_image(sc-old_scp);
if (sc-old_scp-kbd_mode == K_XLATE)
save_kbd_state(sc-old_scp);
Index: scvgarndr.c
===
RCS file: /usr/FreeBSD-CVS/src/sys/dev/syscons/scvgarndr.c,v
retrieving revision 1.5
diff -u -p -r1.5 scvgarndr.c
--- scvgarndr.c2000/01/29 15:08:47 1.5
+++ scvgarndr.c2000/02/09 23:52:53
@@ -225,10 +225,8 @@ vga_txtcursor(scr_stat *scp, int at, int
at%scp-xsize,
at/scp-xsize);
} else {
- if (scp-status VR_CURSOR_ON)
- (*vidsw[adp-va_index]-set_hw_cursor)(adp,
- -1, -1);
scp-status = ~VR_CURSOR_ON;
+ (*vidsw[adp-va_index]-set_hw_cursor)(adp, -1, -1);
}
} else {
scp-status = ~VR_CURSOR_BLINK;
Index: syscons.c
===
RCS file: /usr/FreeBSD-CVS/src/sys/dev/syscons/syscons.c,v
retrieving revision 1.335
diff -u -p -r1.335 syscons.c
--- syscons.c 2000/01/29 15:08:49 1.335
+++ syscons.c 2000/02/09 23:52:53
@@ -1806,7 +1806,8 @@ scrn_update(scr_stat *scp, int show_curs
scp-cursor_pos));
}
}
-}
+} else
+ sc_remove_cursor_image(scp);
#ifndef SC_NO_CUTPASTE
/* update "pseudo" mouse pointer image */
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: /usr/ports/ too big?
On Wed, 9 Feb 2000, Matthew Dillon wrote: : a target "overview" into each /usr/ports/*/Makefile to list all available : subdiretories. Then, with some other command, one could fetch the : current port's directory from the cvs server to install the port. : : Do these thoughts make any sense? : :Yes, this has been desired for some time, but without an actual :implementation we're kinda stuck. :) : :-Alfred It's a nice problem to have, I guess :-) I really like the idea of having a target overview. It would be utterly trivial to have a module list in the Makefile and to change the dependancies to run 'make modulename' in the parent directory rather then in the subdirectory (which might not exist). There's only one person who can make something like this happen. Flattening out the unecessarily deep ports directory structure would help, too. Probably, 98 percent of it could be done with a script, and it would greatly decrease cvsup time and space. Chuck Robey| Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Function Request
Hey guys, I really hate to be a bother, because I know how difficult maintaining program software (and yet you guys are responsible for an entire OS!) can be. So I'll try and get to the point. Some of the programs I help to maintain (and several others I only use) take advantage of several system calls that don't appear to be present in FreeBSD, and hence the software programs (much to my dismay) have to be deployed under Linux and some users are apparently successfully using the software under Windows. There are two sets of function calls to which I refer. The first is mremap(). The second is a set of DNS calls, for example, gethostbyname_r. gethostbyname_r differs from gethostbyname in its syntax, and most importantly, gethostbyname_r is thread-safe. (There are a few more _r calls relating to thread-safe DNS which I cannot recall offhand.) If its possible that something could be done to address this, I would really appreciate. I would love to upgrade a number of servers to FreeBSD. Anyway, thank you for your time. Sincerely yours, M. P. Halpin ([EMAIL PROTECTED]) = -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= M. P. Halpin "What can I say? [EMAIL PROTECTED]I was bored." -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= __ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://im.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Function Request
You might do better discussing this subject in freebsd-hackers. On 2000-Feb-10 16:01:44 +1100, "M. Halpin" [EMAIL PROTECTED] wrote: [Missing functions]. The first is mremap(). What does this function do? Is the function used by freely available software, if so can you give some examples. The second is a set of DNS calls, for example, gethostbyname_r. This does seem to be an oversight. Suitable functions appear to be defined in /usr/src/contrib/bind/lib/irs/gethostent_r.c. I'm not sure why they aren't available. BTW, the best way to get the functions implemented would be to provide the code as a patch against -current. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Function Request
On Thu, Feb 10, 2000 at 04:27:15PM +1100, Peter Jeremy wrote: You might do better discussing this subject in freebsd-hackers. On 2000-Feb-10 16:01:44 +1100, "M. Halpin" [EMAIL PROTECTED] wrote: [Missing functions]. The first is mremap(). What does this function do? Is the function used by freely available software, if so can you give some examples. http://www.freebsd.org/cgi/man.cgi?query=mremapapropos=0sektion=0manpath=Red+Hat+Linux%2Fi386+5.2format=html CONFORMING TO This call is Linux-specific, and should not be used in programs intended to be portable. 4.2BSD had a (never actually implemented) mremap(2) call with completely dif ferent semantics. I doubt there'd be much support for implementing mremap in our system given how proposals like that have gone in the past. -Chris -- [EMAIL PROTECTED] [EMAIL PROTECTED] Abbotsford, BC, Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
