autoconf undefined macros
Hi, The 2.13_1 complains about this: ladoga:/usr/home/admin/nsouch/ggi-core/libgiiautoconf configure.in:157: warning: AC_TRY_RUN called without default to allow cross compiling autoconf: Undefined macros: configure.in:247:AC_CHECK_WINFUNCS(gettimeofday strdup nanosleep usleep _exit \ configure.in:39:AC_LIBTOOL_DLOPEN configure.in:40:AC_LIBTOOL_WIN32_DLL ladoga:/usr/home/admin/nsouch/ggi-core/libgii And autoconf-2.50 gives me: ladoga:/home/admin/nsouch/ggi-core/libgiiautoconf configure.in:8: error: possibly undefined macro: AM_INIT_AUTOMAKE configure.in:10: error: possibly undefined macro: AM_MAINTAINER_MODE configure.in:11: error: possibly undefined macro: AM_DISABLE_STATIC configure.in:39: error: possibly undefined macro: AC_LIBTOOL_DLOPEN configure.in:40: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL configure.in:41: error: possibly undefined macro: AM_PROG_LIBTOOL configure.in:247: error: possibly undefined macro: AC_CHECK_WINFUNCS configure.in:397: error: possibly undefined macro: AM_CONDITIONAL configure.in:665: error: possibly undefined macro: AM_CONFIG_HEADER Do you have any clue? Thanks, Nicholas -- Alcôve Technical Manager - [EMAIL PROTECTED] - http://www.alcove.com Open Source Software Developer - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Quick question on kgdb
Possibly dumb question: OK, you specified makeoptions DEBUG=-g in your kernel config file. Did you also run config(8) with the -g option? G'luck, Peter -- The rest of this sentence is written in Thailand, on On Sat, Jun 30, 2001 at 10:59:35PM -0400, [EMAIL PROTECTED] wrote: Both the kernel and kernel.debug files are of exactly the same size - about 3.3 Megs . This is inspite of having the DEBUG=-g option being set in the MYKERNEL directory. Any other clues, why this could be happening. I also tried the other procedure of using 'make depend' etc as outlined in the doc, but that produced the same results. What else could I be missing? -AG David Malone [EMAIL PROTECTED] wrote: On Sat, Jun 30, 2001 at 12:14:51AM -0400, [EMAIL PROTECTED] wrote: when I load up the installed kernel in / with 'gdb -k kernel' .. it says debugging symbols not found The kernel which is installed is stripped of debugging symbols - you sound find a kernel.debug with symbols in teh compile directory. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: autoconf undefined macros
On Mon, Jul 02, 2001 at 08:30:35AM +0200, Nicolas Souchu wrote: Hi, The 2.13_1 complains about this: ladoga:/usr/home/admin/nsouch/ggi-core/libgiiautoconf configure.in:157: warning: AC_TRY_RUN called without default to allow cross compiling autoconf: Undefined macros: configure.in:247:AC_CHECK_WINFUNCS(gettimeofday strdup nanosleep usleep _exit \ configure.in:39:AC_LIBTOOL_DLOPEN configure.in:40:AC_LIBTOOL_WIN32_DLL ladoga:/usr/home/admin/nsouch/ggi-core/libgii And autoconf-2.50 gives me: ladoga:/home/admin/nsouch/ggi-core/libgiiautoconf configure.in:8: error: possibly undefined macro: AM_INIT_AUTOMAKE configure.in:10: error: possibly undefined macro: AM_MAINTAINER_MODE configure.in:11: error: possibly undefined macro: AM_DISABLE_STATIC configure.in:39: error: possibly undefined macro: AC_LIBTOOL_DLOPEN configure.in:40: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL configure.in:41: error: possibly undefined macro: AM_PROG_LIBTOOL configure.in:247: error: possibly undefined macro: AC_CHECK_WINFUNCS configure.in:397: error: possibly undefined macro: AM_CONDITIONAL configure.in:665: error: possibly undefined macro: AM_CONFIG_HEADER Do you have any clue? Have you tried this with a newer automake, too? AFAIK, the newer versions of autoconf and automake are totally in-backwards-compatible :( G'luck, Peter -- because I didn't think of a good beginning of it. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
TCP Problems in 4.3 ?
Hello Hackers, i think the tcp code in 4.3-RELEASE (and at least stable from last week) has a serious bug in tcp handling: I use LPRng 3.6.20 and openssh on the 4.3 box, lpd-server is on a 4.1 box. Issuing 4-5 lpq's in a minute gives Connection timed out. First i thought it may be a problem with LPRng, but scp'ing large files doesnt work anymore, too. Even ssh hangs sometimes. I tried to disable the newreno stuff with sysctl, didnt change anything. Why i suspect a tcp problem? The host scp connects to shows: LAST_ACK in state (netstat), The host initiating the scp connection shows ESTABLISHED in state. I hope its no problem on my side, but i checked the archive before and I did not have this behaviour on 4.2 Any ideas? Andre To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Linux Applications Over PPP
The only strange occurrence I've seen that sounds even vaguely similar is that if you leave out a nameserver line in /compat/linux/etc/hosts, it *doesn't* default to 127.1. Try adding a nameserver line (if you haven't already got one). Hi, Six million *.rpm files later, I've finally got the Linux version of Mozilla working properly. However, neither the Linux versions of Mozilla or Opera seem to be able use my PPP connection - they simply can't connect to anything, even when I'm fully connected and browsing using the FreeBSD version of Mozilla. Why is this? What setting do I need to alter to enable Linux apps to use my PPP connection? Regards, John. ppp.conf (username/password hashed out!): # # PPP Sample Configuration File # Originally written by Toshiharu OHNO # Simplified 5/14/1999 by [EMAIL PROTECTED] # # $FreeBSD: src/etc/ppp/ppp.conf,v 1.2 1999/08/27 23:24:08 peter Exp $ # default: # # Make sure that device references the correct serial port # for your modem. (cuaa0 = COM1, cuaa1 = COM2) # set device /dev/cuaa0 set log Phase Chat LCP IPCP CCP tun command set speed 57600 set dial ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \\ AT OK-AT-OK ATE1Q0M0 OK \\dATDT\\T TIMEOUT 40 CONNECT set timeout 120 set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 add default HISADDR enable dns anytime: set phone 08089933001 set authname set authkey -- Brian [EMAIL PROTECTED][EMAIL PROTECTED] http://www.freebsd-services.com/brian@[uk.]FreeBSD.org Don't _EVER_ lose your sense of humour ! brian@[uk.]OpenBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: TCP Problems in 4.3 ?
I use LPRng 3.6.20 and openssh on the 4.3 box, lpd-server is on a 4.1 box. Issuing 4-5 lpq's in a minute gives Connection timed out. First i thought it may be a problem with LPRng, but scp'ing large files doesnt work anymore, too. Even ssh hangs sometimes. I tried to disable the newreno stuff with sysctl, didnt change anything. Why i suspect a tcp problem? I had similar problems with 4.3, my ssh and telnet sessions were giving timeouts when they were inactive for about 2 hours (ofcourse this was not an autologout or something). The problem was fixed when I downgraded (for another reason) to 4.2. Regards, Eugene To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: autoconf undefined macros
On Mon, Jul 02, 2001 at 11:21:11AM +0300, Peter Pentchev wrote: On Mon, Jul 02, 2001 at 08:30:35AM +0200, Nicolas Souchu wrote: Hi, The 2.13_1 complains about this: ladoga:/usr/home/admin/nsouch/ggi-core/libgiiautoconf configure.in:157: warning: AC_TRY_RUN called without default to allow cross compiling autoconf: Undefined macros: configure.in:247:AC_CHECK_WINFUNCS(gettimeofday strdup nanosleep usleep _exit \ configure.in:39:AC_LIBTOOL_DLOPEN configure.in:40:AC_LIBTOOL_WIN32_DLL ladoga:/usr/home/admin/nsouch/ggi-core/libgii And autoconf-2.50 gives me: ladoga:/home/admin/nsouch/ggi-core/libgiiautoconf configure.in:8: error: possibly undefined macro: AM_INIT_AUTOMAKE configure.in:10: error: possibly undefined macro: AM_MAINTAINER_MODE configure.in:11: error: possibly undefined macro: AM_DISABLE_STATIC configure.in:39: error: possibly undefined macro: AC_LIBTOOL_DLOPEN configure.in:40: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL configure.in:41: error: possibly undefined macro: AM_PROG_LIBTOOL configure.in:247: error: possibly undefined macro: AC_CHECK_WINFUNCS configure.in:397: error: possibly undefined macro: AM_CONDITIONAL configure.in:665: error: possibly undefined macro: AM_CONFIG_HEADER Do you have any clue? Have you tried this with a newer automake, too? AFAIK, the newer Newer than 2.50? versions of autoconf and automake are totally in-backwards-compatible :( So the 2.13_1 version seems to be the closest to my configure.in file. Then, could it be some missing macros in the FreeBSD installation? Nicholas -- Alcôve Technical Manager - [EMAIL PROTECTED] - http://www.alcove.com Open Source Software Developer - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: autoconf undefined macros
On Mon, Jul 02, 2001 at 01:58:08PM +0200, Nicolas Souchu wrote: On Mon, Jul 02, 2001 at 11:21:11AM +0300, Peter Pentchev wrote: On Mon, Jul 02, 2001 at 08:30:35AM +0200, Nicolas Souchu wrote: Hi, The 2.13_1 complains about this: ladoga:/usr/home/admin/nsouch/ggi-core/libgiiautoconf configure.in:157: warning: AC_TRY_RUN called without default to allow cross compiling autoconf: Undefined macros: configure.in:247:AC_CHECK_WINFUNCS(gettimeofday strdup nanosleep usleep _exit \ configure.in:39:AC_LIBTOOL_DLOPEN configure.in:40:AC_LIBTOOL_WIN32_DLL ladoga:/usr/home/admin/nsouch/ggi-core/libgii And autoconf-2.50 gives me: ladoga:/home/admin/nsouch/ggi-core/libgiiautoconf configure.in:8: error: possibly undefined macro: AM_INIT_AUTOMAKE configure.in:10: error: possibly undefined macro: AM_MAINTAINER_MODE configure.in:11: error: possibly undefined macro: AM_DISABLE_STATIC configure.in:39: error: possibly undefined macro: AC_LIBTOOL_DLOPEN configure.in:40: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL configure.in:41: error: possibly undefined macro: AM_PROG_LIBTOOL configure.in:247: error: possibly undefined macro: AC_CHECK_WINFUNCS configure.in:397: error: possibly undefined macro: AM_CONDITIONAL configure.in:665: error: possibly undefined macro: AM_CONFIG_HEADER Do you have any clue? Have you tried this with a newer automake, too? AFAIK, the newer Newer than 2.50? I meant the automake version, not autoconf. versions of autoconf and automake are totally in-backwards-compatible :( So the 2.13_1 version seems to be the closest to my configure.in file. Then, could it be some missing macros in the FreeBSD installation? If the configure.in and Makefile.am files (and similar) are created for autoconf-2.50 *and* automake 1.4 (e.g. 1.4d), they won't work with any combination of autoconf = 2.50 and automake 1.4. Trust me, I've tried. The only thing I *haven't* tried so far is actually try to update my automake to 1.4d or similar. G'luck, Peter -- If there were no counterfactuals, this sentence would not have been paradoxical. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
i810E driver?
Is anyone working on an i810E driver for BSD? Specifically something that will enable the 3D hardware acceleration and make it useful for OpenGL, X, etc? I'm looking at this for a pet summer project, and wanted to make certain I wasn't duplicating any effort. All these Dell boxes come with the i810E as the integrated video chip, and it's really a fantastic chip, nice acceleration, but drivers are scarce.. The redhat driver sucks too, barely implemented. Thanks Jeremy Lakey [EMAIL PROTECTED]
Orca performance data collector
Hello, I am writing (in fact I am getting a lot of code from /usr/src/usr.bin/vmstat) an Orca data collector for FreeBSD. I think it would be great to have the performance data available in Orca. I am thinking about representing the following parameters: CPU load CPU usage (user, system, interrupt, idle). ¿Do you think it is better to add nice + user to have a single user value, or is it better to separate them? Spawned process/sec Number of processes Interface stats: in, out (bps) in, out (packets) errors/s nocanput (perhaps packets not send because of buffer outages?) deferred collisions TCP bits/sec TCP packets/sec TCP retransmissions + duplicates TCP new connection rate TCP open connections TCP reset state TCP listen drop rate MBUFs Disks: operations/sec transfer rate transfer size run % or time to complete an operation (BTW... is it possible to get read and write statistics instead of a sum?) Cache hits (inode and directory) Memory (usage, etc). Any more interesting parameters? An example of Orca can be seen in http://www.gps.caltech.edu/~blair/orca/. It is really useful to watch the system performance. Borja. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: TCP Problems in 4.3 ?
On Mon, Jul 02, 2001 at 03:53:53PM +0400, Eugene L. Vorokov wrote: I use LPRng 3.6.20 and openssh on the 4.3 box, lpd-server is on a 4.1 box. Issuing 4-5 lpq's in a minute gives Connection timed out. First i thought it may be a problem with LPRng, but scp'ing large files doesnt work anymore, too. Even ssh hangs sometimes. I tried to disable the newreno stuff with sysctl, didnt change anything. Why i suspect a tcp problem? I had similar problems with 4.3, my ssh and telnet sessions were giving timeouts when they were inactive for about 2 hours (ofcourse this was not an autologout or something). The problem was fixed when I downgraded (for another reason) to 4.2. Sure there isn't something in between which does a timeout after 2h? (default value for checkpoint firewall-1). I had the same problem and it was the fw-1. (Yes, I have set keepalive to on) regards, jochen -- Dipl. Inf. Jochen Kaiser kind@IRCNET, phone +49 9131 85-28134 Network Administration mailto:[EMAIL PROTECTED] Regionales Rechenzentrum Universitaet Erlangen-Nuernberg, Germany GPG public key: http://www.uni-erlangen.de/~unrza2/public_key.txt To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
catching ip packets from module
Hello, can please someone enlighten me how can a module catch ip packets before they actually enter the stack, the way ipfw or ipf does ? I tried to look at the sources, but ipfw seems to do it some very specific way which is based on some in-kernel hacks to make it possible (ofcourse correct me if I'm wrong), and ipf does so many things at startup so I can't figure out which function does what :( I just want to add my handler so that all packets would be passed to it before entering the kernel ... Thanks for the information. Regards, Eugene To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: TCP Problems in 4.3 ?
On Mon, Jul 02, 2001 at 03:53:53PM +0400, Eugene L. Vorokov wrote: I use LPRng 3.6.20 and openssh on the 4.3 box, lpd-server is on a 4.1 box. Issuing 4-5 lpq's in a minute gives Connection timed out. First i thought it may be a problem with LPRng, but scp'ing large files doesnt work anymore, too. Even ssh hangs sometimes. I tried to disable the newreno stuff with sysctl, didnt change anything. Why i suspect a tcp problem? I had similar problems with 4.3, my ssh and telnet sessions were giving timeouts when they were inactive for about 2 hours (ofcourse this was not an autologout or something). The problem was fixed when I downgraded (for another reason) to 4.2. Sure there isn't something in between which does a timeout after 2h? (default value for checkpoint firewall-1). I had the same problem and it was the fw-1. (Yes, I have set keepalive to on) No, there was only a FreeBSD 4.2 with options BRIDGE in between. And anyway, if firewall would be a problem, why this problem doesn't appear with 4.2 ... Regards, Eugene To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: why not two ep pc-cards in one system ?
You mean in /etc/defaults/pccard.conf ? or in /etc/rc.conf ? thanks. : hostname pccardd[87]: No free configuration for card 3Com Corporation You need a second config line to the 3com entry. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message _ Get your FREE download of MSN Explorer at http://explorer.msn.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
[Q] msgs
Hello, msgs reminded me the old UNIX news command and then, I started to fiddle around it. As I want to post stuff, it works good with msgs -s. However, in the man pages, they suggest: The line msgs: | /usr/bin/msgs -s should be included in /etc/mail/aliases (see newaliases(1)) to enable posting of messages. after running newaliases, I expected (maybe shouldn't I?) I could email to msgs 'user' to post a news. But I'm getting an error: Jul 2 11:17:45 gateway sendmail[35214]: f62FHjx35214: from=root, size=48, class=0, nrcpts=1, msgid=[EMAIL PROTECTED], relay=root@localhost Jul 2 11:17:45 gateway sendmail[35216]: f62FHjx35214: to=| /usr/bin/msgs -s, ctladdr=msgs (1/0), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=30048, dsn=5.3.0, stat=unknown mailer error 13 Jul 2 11:17:45 gateway sendmail[35216]: f62FHjx35214: f62FHjw35216: DSN: unknown mailer error 13 and hints? regards, ian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
FreeBSD 4.0-release installation problems
A few days ago I got my Dell 8100 (1.5 ghz and 128 Mb of ram) in the mail. Naturally I desided to install Freebsd 4.0 on it along with preinstalled WindowsME. So I used Partition Magic to cut the 40 gig windows partition and add a partition for freebsd (about 5 gigs allocated). The installation ran pretty smoothly, it probed my hardware fine and everything seemed to be working ok. During the installation process freebsd prompted me to choose a boot loader, I choose the freebsd boot manager (booteasy). When I rebooted my machine The boot easy prompt came on F1 for windows and F2 for freebsd, I hit F2 because I wanted freebsd to load. When I hit F2 all I heard was my internal speaker beep - one of those annoying warning beeps and nothing attempted to load. when I hit F1 windows loaded fine. I began thinking it was some sort of BIOS configuration problem so I went in bios and no luck there eather.. I have heard about some system BIOS having an issue with exceeding 1024 cylinders or whatnot, but this is for OLD machines not new 1.5 ghz machine.. If anyone has information on my problem or can offer suggestions please email me... I will take you out for a cup of coffee or lunch if you help me get freebsd running (joking) anyways have a great summer bsd cadets and stay away from the heat.. Scared Dell user, Zac Speidel Please email me: [EMAIL PROTECTED] __ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail http://personal.mail.yahoo.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Status of encryption hardware support in FreeBSD
I think you've missed the fact that the '486 solution requires an add-on board (priced at $80.) and the faster cpu solution doesnt. That adds a lot of margin to get a faster MB, more than enough to compensate for the board. Not necessarily. The upgraded motherboard also requires a faster processor, and the two parts added together are almost certainly going to be more than $80. There is nothing more annoying than someone who argues subjects he clearly knows nothing about. I agree. :) You are way off on your pricing. Way off. A 633 Celeron is under 50. Q1 for petes sake. The cost difference would be less than $20. in quantity. It would be less than $80. Q1. That's just CPU. You've left off the motherboard, as well as the memory and other supporting hardware required for the CPU to do the work. Theres an old saying about being penny-wise and pound foolish. Using a 486 in todays networking and cost environment is just plain moronic. See your first sentence. You *really* don't know what you are talking about. Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: FreeBSD 4.0-release installation problems
(Responding on-list so there's no flood of private responses. Considered cross-posting to move the thread, but hoping it will just die on -hackers.) This topic would probably be better suited to freebsd-questions. Date: Mon, 2 Jul 2001 09:00:15 -0700 (PDT) From: Zac M. Speidel [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: FreeBSD 4.0-release installation problems FYI: 1. Not sure why you're running 4.0-R 2. Processor speed means nothing. A PC BIOS is a PC BIOS is a PC BIOS, and they all have the same limitations. 3. Consider a small (8 MB is more than enough) partition to hold /boot. Note that I'm using partition in the WinDOS/Linux sense; a slice would be the correct BSD term. Eddy --- Brotsman Dreger, Inc. EverQuick Internet Division Phone: +1 (316) 794-8922 Wichita/(Inter)national Phone: +1 (785) 865-5885 Lawrence --- Date: Mon, 21 May 2001 11:23:58 + (GMT) From: A Trap [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Please ignore this portion of my mail signature. These last few lines are a trap for address-harvesting spambots. Do NOT send mail to [EMAIL PROTECTED], or you are likely to be blocked. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: catching ip packets from module
* Eugene L. Vorokov [EMAIL PROTECTED] [010702 10:19] wrote: Hello, can please someone enlighten me how can a module catch ip packets before they actually enter the stack, the way ipfw or ipf does ? I tried to look at the sources, but ipfw seems to do it some very specific way which is based on some in-kernel hacks to make it possible (ofcourse correct me if I'm wrong), and ipf does so many things at startup so I can't figure out which function does what :( I just want to add my handler so that all packets would be passed to it before entering the kernel ... Thanks for the information. Look at src/sys/net/if_ethersubr.c, there's hooks for netgraph that you can ab^H^Huse. :) -- -Alfred Perlstein [[EMAIL PROTECTED]] Ok, who wrote this damn function called '??'? And why do my programs keep crashing in it? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: processes private data
On Fri, Jun 29, 2001 at 01:34:19PM +0100, Doug Rabson wrote: When you get a new struct file from falloc(), VFS has nothing to do with it. As you can see from the streamsopen() code, you can change f_ops (which by default points at badfileops) and f_data (defaults to zero) to point at your own functions and data. The point is that you are creating a new file. The VFS-owned file which ended up calling the open driver entrypoint will be discarded in favour of your new one. But, what about all the locking stuff in vn_()? How can I know if I actually need them? Nicholas -- Alcôve Technical Manager - [EMAIL PROTECTED] - http://www.alcove.com Open Source Software Developer - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Filesystem ACL's
Couple of questions, and my apologies for repeating something that may have been mentioned recently... Are Filesystem ACL's something we can look forward to seeing in FreeBSD? Also, is there a place I can view the progress and/or the current status of the project? Finally, what does it take to implement this functionality? If this is a feature already in production, please just smack me upside the head, and point me to the correct man page. Thanks! -- Robert Hough ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Linux Applications Over PPP
Brian Somers wrote: The only strange occurrence I've seen that sounds even vaguely similar is that if you leave out a nameserver line in /compat/linux/etc/hosts, it *doesn't* default to 127.1. Try adding a nameserver line (if you haven't already got one). Thanks for the suggestion, but it has still not solved the problem. In fact there wasn't even a /compat/linux/etc/hosts file, so I created one, containing the line: 127.0.0.1 localhost Dionysus (Dionysus is the hostname of my machine). Unfortunately this had no effect, even after unloading and reloading the linux.ko module to ensure it parsed the new configuration file. /compat/linux/etc/hosts.conf is set so it parses hosts first as well. Any ideas? It's completely bizarre, Linux emulation has always worked perfectly for me before... John. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
RE: Filesystem ACL's
see www.trustedbsd.org especially the usenix paper. -Original Message- From: Robert Hough [mailto:[EMAIL PROTECTED]] Sent: Monday, July 02, 2001 16:32 To: [EMAIL PROTECTED] Subject: Filesystem ACL's snip Are Filesystem ACL's something we can look forward to seeing in FreeBSD? snip To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Filesystem ACL's
-Original Message- From: Robert Hough [mailto:[EMAIL PROTECTED]] Are Filesystem ACL's something we can look forward to seeing in FreeBSD? snip * Yonatan Bokovza [EMAIL PROTECTED] [010702 13:05] wrote: see www.trustedbsd.org especially the usenix paper. Well FreeBSD 5 has a bunch of the ACL stuff ported to it. -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Filesystem ACL's
Nothing for sure yet, but AFAIK, a couple ideas presented at USENIX are being considered. - Original Message - From: Robert Hough [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, July 02, 2001 9:31 AM Subject: Filesystem ACL's Couple of questions, and my apologies for repeating something that may have been mentioned recently... Are Filesystem ACL's something we can look forward to seeing in FreeBSD? Also, is there a place I can view the progress and/or the current status of the project? Finally, what does it take to implement this functionality? If this is a feature already in production, please just smack me upside the head, and point me to the correct man page. Thanks! -- Robert Hough ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Linux Applications Over PPP
is there a /compat/linux/etc/resolv.conf? On Mon, 2 Jul 2001, John Toon wrote: Brian Somers wrote: The only strange occurrence I've seen that sounds even vaguely similar is that if you leave out a nameserver line in /compat/linux/etc/hosts, it *doesn't* default to 127.1. Try adding a nameserver line (if you haven't already got one). Thanks for the suggestion, but it has still not solved the problem. In fact there wasn't even a /compat/linux/etc/hosts file, so I created one, containing the line: 127.0.0.1 localhost Dionysus (Dionysus is the hostname of my machine). Unfortunately this had no effect, even after unloading and reloading the linux.ko module to ensure it parsed the new configuration file. /compat/linux/etc/hosts.conf is set so it parses hosts first as well. Any ideas? It's completely bizarre, Linux emulation has always worked perfectly for me before... John. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Linux Applications Over PPP
On Mon, 2 Jul 2001, Julian Elischer wrote: is there a /compat/linux/etc/resolv.conf? At one stage you needed one as the linux binaries expected a different format. ppp updates the BSD one but not the Linux one.. On Mon, 2 Jul 2001, John Toon wrote: Brian Somers wrote: The only strange occurrence I've seen that sounds even vaguely similar is that if you leave out a nameserver line in /compat/linux/etc/hosts, it *doesn't* default to 127.1. Try adding a nameserver line (if you haven't already got one). Thanks for the suggestion, but it has still not solved the problem. In fact there wasn't even a /compat/linux/etc/hosts file, so I created one, containing the line: 127.0.0.1 localhost Dionysus (Dionysus is the hostname of my machine). Unfortunately this had no effect, even after unloading and reloading the linux.ko module to ensure it parsed the new configuration file. /compat/linux/etc/hosts.conf is set so it parses hosts first as well. Any ideas? It's completely bizarre, Linux emulation has always worked perfectly for me before... John. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Filesystem ACL's
On Mon, Jul 02, 2001 at 02:20:56PM -0400, Tom Gottheil wrote: Nothing for sure yet, but AFAIK, a couple ideas presented at USENIX are being considered. POSIX.1e ACL support is present in -current. -- Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org PGP signature
Re: Filesystem ACL's
At 1:31 PM + 7/2/01, Robert Hough wrote: Couple of questions, and my apologies for repeating something that may have been mentioned recently... Are Filesystem ACL's something we can look forward to seeing in FreeBSD? Also, is there a place I can view the progress and/or the current status of the project? Robert Watson is doing a lot of work in the area of ACL's and access mechanisms in general. He will probably scarce for the next month or so, though. Something about getting married or honeymoons, iirc. joke about laptop's deleted You could check www.trustedbsd.org, or also search thru the freebsd-security mailing list for recent messages from Robert about 'TrustedBSD paper at USENIX'. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Status of encryption hardware support in FreeBSD
In a message dated 07/02/2001 12:16:47 PM Eastern Daylight Time, [EMAIL PROTECTED] writes: You are way off on your pricing. Way off. A 633 Celeron is under 50. Q1 for petes sake. The cost difference would be less than $20. in quantity. It would be less than $80. Q1. That's just CPU. You've left off the motherboard, as well as the memory and other supporting hardware required for the CPU to do the work. Entire PIII MBs are available for under $60. Your concept that the delta in cost between a 486 chipset and PIII is more that that is utterly ridiculous PIII chipsets and 486 chipsets cost the same in quantity. Try using a resource other than your Radio Shack catalogue please. B To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Status of encryption hardware support in FreeBSD
On Mon, Jul 02, 2001 at 06:08:31PM -0400, [EMAIL PROTECTED] wrote: In a message dated 07/02/2001 12:16:47 PM Eastern Daylight Time, [EMAIL PROTECTED] writes: You are way off on your pricing. Way off. A 633 Celeron is under 50. Q1 for petes sake. The cost difference would be less than $20. in quantity. It would be less than $80. Q1. That's just CPU. You've left off the motherboard, as well as the memory and other supporting hardware required for the CPU to do the work. Entire PIII MBs are available for under $60. Your concept that the delta in cost between a 486 chipset and PIII is more that that is utterly ridiculous PIII chipsets and 486 chipsets cost the same in quantity. Try using a resource other than your Radio Shack catalogue please. Might be true, but embedded folks tend to use something else than a run-of-the-mill mainboard. I think this whole thread boils down to: YMMV. Let it die (please..) -- | / o / / _ Arnhem, The Netherlandsemail: [EMAIL PROTECTED] |/|/ / / /( (_) Bulte http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: import NetBSD rc system
On Thu, Jun 14, 2001 at 01:42:36PM +0200, Cyrille Lefevre wrote: in fact, the require keyword isn't sufficient in it's own. there should be pre_require and post_require keywords since nfsd needs to start mountd before to start nfsd then rpc.statd and rpc.lockd have to be started after nfsd. Sorry to jump in an old discussion, I don't read fbsd-hackers often enough, apparently. In this situation, wouldn't you rather take the solaris option of putting nfs_servers in their own startup option and start the servers desired (maybe you don't want rpc.lockd) according to normal rc.conf knobs. For services as tightly coupled as this that seems like a much better way of guaranteeing ordering, and the whole package could then depend on portmap. It's not like you'd ever want nfsd and not mountd, or vice versa. -- David Terrell| But remember that layman is just a polite [EMAIL PROTECTED] | word for idiot. http://wwn.nebcorp.com/ | - Neal Stephenson To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: catching ip packets from module
On Mon, Jul 02, 2001 at 07:32:13PM +0400, Eugene L. Vorokov wrote:
Hello,
can please someone enlighten me how can a module catch ip packets before
they actually enter the stack, the way ipfw or ipf does ? I tried to look
at the sources, but ipfw seems to do it some very specific way which
is based on some in-kernel hacks to make it possible (ofcourse correct me
if I'm wrong), and ipf does so many things at startup so I can't figure
out which function does what :( I just want to add my handler so that
all packets would be passed to it before entering the kernel ...
the way ipfw or ipf does? by adding hacks^H^H^H^Hooks into ip_{in,out}put()
search for ip_fw_chk_ptr and fr_checkp, those are the money functions.
everything else is just setup and reaction.
as far as non-hacks that do similar things, as alfred points out netgraph
is probably the most modular way to drop in raw-frame-needing-module-X.
--
Bill Fumerola - security yahoo / Yahoo! inc.
- [EMAIL PROTECTED] / [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Question on making a custom release
FreeBSD warriors: Steps I took to try to make a release. Followed the FreeBSD FAQ about making a custom release: supfile looks like this: *default host=cvsup3.freebsd.org *default base=/usr *default prefix=/usr/local/cvstree *default release=cvs *default delete compress use-rel-suffix src-all Next Ran this command: cvsup -g supfile Then I: setenv CVSROOT /usr/local/cvstree cd /usr/src make buildworld cd /usr/src/release make release BUILDNAME=4.3-CUSTOM CHROOTDIR=/usr/local/latest43/release CVSROOT=/usr/local/cvstree NOPORTS=1 NODOC=1 -- Builds for a couple of hours then I get this error: -- Rebuilding man page indices -- cd /usr/src/share/man; make makedb makewhatis /usr/share/man makewhatis /usr/share/perl/man rm -rf /tmp/install.95817 -- elf make world completed on Tue Jul 3 04:37:59 GMT 2001 (started Tue Jul 3 02:41:43 GMT 2001) -- + touch /tmp/.world_done + cd /usr/src/release/sysinstall cd: can't cd to /usr/src/release/sysinstall jett# *** Error code 2 Stop in /usr/src/release. I want to know which /usr/src/release/sysinstall? The one created in /usr/local/cvstree?, /usr/local/latest43/release?, or my /usr/src/release/sysinstall on my host machine. Note: My current kernel has the psuedo-device vn configure in and installed. I am root, but I did run cvsup as a user in the root's wheel group. So no /usr/local/latest43/release/R/ftp directory created. -Does anyone have any hints on what went wrong? -CRG To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
patch for cr_uid checks against zero in -CURRENT
I was reading handbook/contrib.html to find useful things to do today.
There's a mention about replacing explicit checks of cr_uid against
zero with calls to suser() or suser_xxx().
The following little script, was what I used to look for cr_uid
occurences.
#!/bin/sh
( find . -type f | xargs egrep -C5 'cr_uid' ) |\
sed -e 's/cr_uid//g' |\
less -r
The output is rather long, and skimming through it, I found out that
the following files contained explicit checks of cr_uid against zero:
./dev/digi/digi.c
./fs/msdosfs/msdosfs_vfsops.c
./fs/nwfs/nwfs_vnops.c
./fs/smbfs/smbfs_vnops.c
./fs/umapfs/umap_vnops.c
./gnu/ext2fs/ext2_alloc.c
./gnu/ext2fs/ext2_lookup.c
./gnu/ext2fs/ext2_readwrite.c
./gnu/ext2fs/ext2_vnops.c
./kern/kern_ktrace.c
./kern/kern_sig.c
./netinet/in_pcb.c
./netinet6/in6_pcb.c
./netinet6/ipsec.c
./netinet6/raw_ip6.c
./nfs/nfs_subs.c
./nfs/nfs_vnops.c
./ufs/ffs/ffs_alloc.c
./ufs/ffs/ffs_vfsops.c
I am not sure if I can test the attached patch for all the changes
that it does, so here it is with any comments, suggestions,
corrections, welcome :-)
-giorgos
Index: ./dev/digi/digi.c
===
RCS file: /home/ncvs/src/sys/dev/digi/digi.c,v
retrieving revision 1.11
diff -c -u -r1.11 digi.c
--- ./dev/digi/digi.c 2001/06/20 14:52:08 1.11
+++ ./dev/digi/digi.c 2001/07/02 15:30:18
@@ -801,7 +801,7 @@
}
goto open_top;
}
- if (tp-t_state TS_XCLUDE p-p_ucred-cr_uid != 0) {
+ if (tp-t_state TS_XCLUDE suser(p)) {
error = EBUSY;
goto out;
}
Index: ./fs/msdosfs/msdosfs_vfsops.c
===
RCS file: /home/ncvs/src/sys/fs/msdosfs/msdosfs_vfsops.c,v
retrieving revision 1.79
diff -c -u -r1.79 msdosfs_vfsops.c
--- ./fs/msdosfs/msdosfs_vfsops.c 2001/06/28 03:47:50 1.79
+++ ./fs/msdosfs/msdosfs_vfsops.c 2001/07/02 15:31:47
@@ -263,7 +263,7 @@
* If upgrade to read-write by non-root, then verify
* that user has necessary permissions on the device.
*/
- if (p-p_ucred-cr_uid != 0) {
+ if (suser(p)) {
devvp = pmp-pm_devvp;
vn_lock(devvp, LK_EXCLUSIVE | LK_RETRY, p);
error = VOP_ACCESS(devvp, VREAD | VWRITE,
@@ -310,7 +310,7 @@
* If mount by non-root, then verify that user has necessary
* permissions on the device.
*/
- if (p-p_ucred-cr_uid != 0) {
+ if (suser(p)) {
accessmode = VREAD;
if ((mp-mnt_flag MNT_RDONLY) == 0)
accessmode |= VWRITE;
Index: ./fs/nwfs/nwfs_vnops.c
===
RCS file: /home/ncvs/src/sys/fs/nwfs/nwfs_vnops.c,v
retrieving revision 1.20
diff -c -u -r1.20 nwfs_vnops.c
--- ./fs/nwfs/nwfs_vnops.c 2001/05/26 11:57:37 1.20
+++ ./fs/nwfs/nwfs_vnops.c 2001/07/02 15:32:20
@@ -150,7 +150,7 @@
break;
}
}
- if (cred-cr_uid == 0)
+ if (suser_xxx(cred, 0, 0) == 0)
return 0;
if (cred-cr_uid != nmp-m.uid) {
mode = 3;
Index: ./fs/smbfs/smbfs_vnops.c
===
RCS file: /home/ncvs/src/sys/fs/smbfs/smbfs_vnops.c,v
retrieving revision 1.2
diff -c -u -r1.2 smbfs_vnops.c
--- ./fs/smbfs/smbfs_vnops.c2001/04/29 11:48:34 1.2
+++ ./fs/smbfs/smbfs_vnops.c2001/07/02 15:33:13
@@ -155,7 +155,7 @@
break;
}
}
- if (cred-cr_uid == 0)
+ if (suser(cred, 0, 0) == 0)
return 0;
if (cred-cr_uid != smp-sm_args.uid) {
mode = 3;
Index: ./fs/umapfs/umap_vnops.c
===
RCS file: /home/ncvs/src/sys/fs/umapfs/umap_vnops.c,v
retrieving revision 1.33
diff -c -u -r1.33 umap_vnops.c
--- ./fs/umapfs/umap_vnops.c2001/05/23 09:42:13 1.33
+++ ./fs/umapfs/umap_vnops.c2001/07/02 15:36:04
@@ -152,7 +152,7 @@
(*credpp) = crdup(savecredp);
credp = *credpp;
- if (umap_bug_bypass credp-cr_uid != 0)
+ if (umap_bug_bypass suser_xxx(credp, 0, 0))
printf(umap_bypass: user was %lu, group %lu\n,
(u_long)credp-cr_uid, (u_long)credp-cr_gid);
@@ -160,7 +160,7 @@
umap_mapids(vp1-v_mount, credp);
- if (umap_bug_bypass
Re: Status of encryption hardware support in FreeBSD
[EMAIL PROTECTED] wrote: Entire PIII MBs are available for under $60. Your concept that the delta in cost between a 486 chipset and PIII is more that that is utterly ridiculous PIII chipsets and 486 chipsets cost the same in quantity. Try using a resource other than your Radio Shack catalogue please. Now try to imagine a whole PC on a smaller board than a PIII CPU cartridge. If you can't, get a copy of the Embedded Systems magazine and look at the pictures in it. -SB To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: TCP Problems in 4.3 ?
On Mon, 2 Jul 2001, Andre Grosse Bley wrote: Hello Hackers, i think the tcp code in 4.3-RELEASE (and at least stable from last week) has a serious bug in tcp handling: I use LPRng 3.6.20 and openssh on the 4.3 box, lpd-server is on a 4.1 box. Issuing 4-5 lpq's in a minute gives Connection timed out. First i thought it may be a problem with LPRng, but scp'ing large files doesnt work anymore, too. Even ssh hangs sometimes. I tried to disable the newreno stuff with sysctl, didnt change anything. Why i suspect a tcp problem? Your description isn't exactly clear, but your problem may be fixed by applying the patch and following the directions in my recently posted message Re: select fails to return incoming connect on FreeBSD-4.3 - see the freebsd-net archives. Note that the patch addresses _only_ problems with connections being established to the same host / port in a quick hurry. There are no known problems with connections terminating once a connection is established. I'm unable to ascertain which possibility you're describing when you say that scp transfers fail. If you're having trouble at the connection setup stage, apply the patch and flip the sysctl. Then see if it fixes your problem and get back to me. Thanks, Mike Silby Silbersack To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: TCP Problems in 4.3 ?
On Mon, 2 Jul 2001, Eugene L. Vorokov wrote: I had similar problems with 4.3, my ssh and telnet sessions were giving timeouts when they were inactive for about 2 hours (ofcourse this was not an autologout or something). The problem was fixed when I downgraded (for another reason) to 4.2. Regards, Eugene Hm. 2 hours is exactly the amount of idle time which causes keepalives to be sent. However, I'm not away of any bugs in keepalive handling, and I just tested that 2 weeks ago (both between freebsd boxes and freebsd and windows 98.) Did you have TCP_COMPAT_42 defined? Can you provide any other information about the problem? Were you behind NAT or something strange? Thanks, Mike Silby Silbersack To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
ftpd....
I was looking at a bunch of bug reports, and quite a few pertain to ftpd. Anyone thinking about going through and just cleaning it up from head to toe? Not a complete rewrite or anything, but just alot of straightening up. If no one is doing this now, I have no problem attempting to tackle this. Anyone have any input or ideas before i set out on this? Mike Wiacek To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: ftpd....
On Mon, Jul 02, 2001 at 11:55:14PM -0400, Mike Wiacek wrote: I was looking at a bunch of bug reports, and quite a few pertain to ftpd. Anyone thinking about going through and just cleaning it up from head to toe? Not a complete rewrite or anything, but just alot of straightening up. If no one is doing this now, I have no problem attempting to tackle this. Anyone have any input or ideas before i set out on this? Sane patches are always accepted. Kris PGP signature
Re: ftpd....
Be aware that ftpd is likely to be replaced in the near future, as there's a strong desire to converge on the LukeM FTP tools. --BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jul 02, 2001 at 11:55:14PM -0400, Mike Wiacek wrote: I was looking at a bunch of bug reports, and quite a few pertain to ftpd. Anyone thinking about going through and just cleaning it up from head to toe? Not a complete rewrite or anything, but just alot of straightening up. If no one is doing this now, I have no problem attempting to tackle this. Anyone have any input or ideas before i set out on this? Sane patches are always accepted. Kris --BOKacYhQ+x31HxR3 Content-Type: application/pgp-signature Content-Disposition: inline -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7QVxJWry0BWjoQKURAlHKAKCBMkn6RxKNhJ5orFnzR8zDmGsvqQCg1vZb LFf2EgxG8lOIsy/SSKGsR7M= =D4WO -END PGP SIGNATURE- --BOKacYhQ+x31HxR3-- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
