Is there any plan to newbuslize for 3-stable?
Hi. I have a question about new-bus code. Currently device style of FreeBSD-4-current is changing to newbus. But is there any plan to newbuslize for 3-stable? If my patch for pcm/ESS sound chip apply to FreeBSD, may I send-pr with old-config style? Yes, current pcm sound driver is old-config, but "Cameron Grant" [EMAIL PROTECTED] is working to newbuslize. MIHIRA Sanpei Yoshiro To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
mmap bug
Oh, I'm sorry, I made a mistake when posting code. I posted incorrectly
patched version... This version correct :
#include stdio.h
#include stdlib.h
#include sys/types.h
#include sys/mman.h
#include unistd.h
#include fcntl.h
#include errno.h
main(int argc, char *argv[])
{
int fd;
int i;
int len=1024*1024*10; /*ie 10Mbytes*/
caddr_t addr;
char ttt[80];
int bunlink=0;
if (argc1 strcmp (argv[1], "-u")==0)
bunlink=1;
for (i=0;;i++)
{
sprintf (ttt,"%d",i);
printf ("mmapping %ld byte region on file %s\n", len, ttt);
fd=open(ttt,O_CREAT|O_RDWR,0666);
if (fd0)
{
printf("open error %ld\n",errno);
exit(1);
}
lseek(fd,len-1,SEEK_SET);
write(fd,"",1);
addr=mmap(0,len,PROT_READ|PROT_WRITE,MAP_SHARED,fd,0);
if (addr==MAP_FAILED)
{
printf("mmap error %ld",errno);
exit(1);
}
memset(addr,'x',len);
if ( munmap(addr, len) != 0 )
{
fprintf(stderr, "munmap failed\n");
exit(EXIT_FAILURE);
}
close(fd);
if ( bunlink ) unlink (ttt);
}
}
Thank you for answers.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: BSD-XFS Update
[EMAIL PROTECTED] (Alton, Matthew) writes: I am currently researching methods for implementing the 64-bit syscalls stat64(), fstat64(), lseek64() etc. delineated in the SGI design doc _64 Bit File Access_ by Adam Sweeney. Do the design docs indicate how inode numbers should interact with userland APIs? IIRC, inode numbers are 64-bit numbers in XFS. Since ino_t, st_ino of struct stat and d_fileno of struct dirent are only 32 bits, inode numbers may be truncated and not appear unique to userland. This would break the assumptions of some code (e.g. getcwd(3), when not using the kernel extension). To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BSD XFS Port BSD VFS Rewrite
Tony Finch [EMAIL PROTECTED] writes: Kenny Drobnack [EMAIL PROTECTED] wrote: This may be a stupid question, but what's to keep from putting xfs in FreeBSD? Is there something in the licenses that says you can't use GPL'ed software and software under the BSD License together? Yes. The BSD licence requirement for acknowledging UCB in any advertising conflicts with the GPL requirement that further restrictions should not be added to those already in the GPL. This prevents you from relicensing BSD software under the GPL. It does not prevent you from selling an OS that has both BSD and GPL bits, as long as the GPL bits come with full source. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
New tests for test(1)
Hi all I was writing a script yesterday, and I wanted to have a test to compare the modification time of two files. test(1) doesn't have the ability to do this. In the end I worked around this by using make(1), but it set me thinking - wouldn't it be a good idea to add some new tests to test(1), to compare files based on criteria like size or modification date? Anyone else think this is a good idea? -- Dr Graham WheelerE-mail: [EMAIL PROTECTED] Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax:+27(21)24-3656 Data/Network Security SpecialistsWWW:http://www.cequrux.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: New tests for test(1)
On Thu, 12 Aug 1999, Graham Wheeler wrote: Hi all I was writing a script yesterday, and I wanted to have a test to compare the modification time of two files. test(1) doesn't have the ability to do this. In the end I worked around this by using make(1), but it set me thinking - wouldn't it be a good idea to add some new tests to test(1), to compare files based on criteria like size or modification date? A suggestion for another way to implement such a test: ls -1t file1 file2 | head -1 will give you the newest of the two... That's what I use when I need to do such tests. I guess it's easier and faster than make. Anyone else think this is a good idea? -- Dr Graham WheelerE-mail: [EMAIL PROTECTED] Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax:+27(21)24-3656 Data/Network Security SpecialistsWWW:http://www.cequrux.com/ Nadav To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Various Questions
-- snip --
if (pswitch) {
/*
* If the device is not configured up, we cannot put it
in
* promiscuous mode.
*/
if ((ifp-if_flags IFF_UP) == 0)
return (ENETDOWN);
if (ifp-if_pcount++ != 0)
return (0);
ifp-if_flags |= IFF_PROMISC;
log(LOG_INFO, "%s%d: promiscuous mode enabled\n",
ifp-if_name, ifp-if_unit);
} else {
if (--ifp-if_pcount 0)
return (0);
ifp-if_flags = ~IFF_PROMISC;
---log(LOG_INFO, "%s%d: promiscuous mode disabled\n",
---ifp-if_name, ifp-if_unit);
Shouldn't this be:
if (ipf-if_flags IFF_PROMISC) {
ipf-if_flags = ~IFF_PROMISC;
log(LOG_INFO, "%s%d: promiscuous mode disabled\n", ifp-if_name,
ifp-if_unit);
}
Or is the test for IFF_PROMISC made earlier in the code? You
should only print a disabled message when it has previously
been enabled so that log file watchers can always match up
the up/down pairs.
Regards,
Niall
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: New tests for test(1)
Graham Wheeler [EMAIL PROTECTED] writes: I was writing a script yesterday, and I wanted to have a test to compare the modification time of two files. test(1) doesn't have the ability to do this. In the end I worked around this by using make(1), but it set me thinking - wouldn't it be a good idea to add some new tests to test(1), to compare files based on criteria like size or modification date? NetBSD's test(1) utility has this (-nt and -ot). We should probably merge in their changes. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Various Questions
On Thu, 12 Aug 1999 11:29:47 GMT, Niall Smart wrote: Or is the test for IFF_PROMISC made earlier in the code? You should only print a disabled message when it has previously been enabled so that log file watchers can always match up the up/down pairs. I've been using if.c modified exactly as suggested for a few months now and have experienced the intended results without apparent problems. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Various Questions
if (--ifp-if_pcount 0)
return (0);
ifp-if_flags = ~IFF_PROMISC;
---log(LOG_INFO, "%s%d: promiscuous mode disabled\n",
---ifp-if_name, ifp-if_unit);
Shouldn't this be:
if (ipf-if_flags IFF_PROMISC) {
ipf-if_flags = ~IFF_PROMISC;
log(LOG_INFO, "%s%d: promiscuous mode disabled\n", ifp-if_name,
ifp-if_unit);
}
Or is the test for IFF_PROMISC made earlier in the code? You
should only print a disabled message when it has previously
been enabled so that log file watchers can always match up
the up/down pairs.
yes that I think that would be a better idea to check to see if it is
actually in promiscuous mode first before printing out our disabled
message so all pairs match..however doesn't the following code
from above seem to gaurd against this situation : ?
if (--ifp-if_pcount 0)
return (0);
from what I can see, it only turns off promiscuous mode if
if_pcount reaches zero, ie. all requests for promiscuous mode
to be off account for all the previous requests for promiscuous
mode to be on..?
..then again I'm no expert kernel hacker (yet!) and I certainly
don't pretend to be one either, so I'll leave this to the
experts :-D
- Cillian
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: New tests for test(1)
On 12 Aug 1999 11:42:42 +0200, Dag-Erling Smorgrav wrote: NetBSD's test(1) utility has this (-nt and -ot). We should probably merge in their changes. Their code isn't useful in this case, since they've merged in a pdksh-derived version of test. How about we do the same? :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Various Questions
Sheldon Hearn wrote: On Thu, 12 Aug 1999 11:29:47 GMT, Niall Smart wrote: Or is the test for IFF_PROMISC made earlier in the code? You should only print a disabled message when it has previously been enabled so that log file watchers can always match up the up/down pairs. I've been using if.c modified exactly as suggested for a few months now and have experienced the intended results without apparent problems. But what happens if you write a program which does whatever ioctl is required to unpromiscify an interface and run it on an unpromiscuous interface, does it print a message to syslog even though promiscuous mode was never enabled in the first place? Time to start reading some code methinks Niall + To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BSD XFS Port BSD VFS Rewrite
On 12 Aug 1999 11:01:06 +0200 Dag-Erling Smorgrav [EMAIL PROTECTED] wrote: This prevents you from relicensing BSD software under the GPL. It does not prevent you from selling an OS that has both BSD and GPL bits, as long as the GPL bits come with full source. If you have an executable object which includes GPL'd code, you must supply FULL SOURCE for the *entire* object, not just the GPL'd bits. This is the real crux of the problem; the GPL has a virus-like nature. -- Jason R. Thorpe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: BSD XFS Port BSD VFS Rewrite
Jason Thorpe [EMAIL PROTECTED] writes: On 12 Aug 1999 11:01:06 +0200 Dag-Erling Smorgrav [EMAIL PROTECTED] wrote: This prevents you from relicensing BSD software under the GPL. It does not prevent you from selling an OS that has both BSD and GPL bits, as long as the GPL bits come with full source. If you have an executable object which includes GPL'd code, you must supply FULL SOURCE for the *entire* object, not just the GPL'd bits. We're talking separate binaries here. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Various Questions
On Thu, 12 Aug 1999 12:20:35 GMT, Niall Smart wrote: But what happens if you write a program which does whatever ioctl is required to unpromiscify an interface and run it on an unpromiscuous interface, does it print a message to syslog even though promiscuous mode was never enabled in the first place? Like I said, I seem to get the intended behaviour. vty1 - start trafshow Aug 12 12:26:41 axl /kernel: xl0: promiscuous mode enabled vty2 - start trafshow vty1 - kill trafshow vty2 - kill trafshow Aug 12 12:27:22 axl /kernel: xl0: promiscuous mode disabled :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: New tests for test(1)
this seems undesirable to me, since using it immediately makes your shell scripts nonportable. i liked the ls -t suggestion though. -- Aaron Smith [EMAIL PROTECTED] On Thu, Aug 12, 1999 at 11:18:50AM +0200, Graham Wheeler wrote: thinking - wouldn't it be a good idea to add some new tests to test(1), to compare files based on criteria like size or modification date? Anyone else think this is a good idea? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: New tests for test(1)
Aaron Smith wrote: this seems undesirable to me, since using it immediately makes your shell scripts nonportable. i liked the ls -t suggestion though. Portability is a Good Thing, but I write a lot of one-off scripts in which portability isn't an issue. Also, just because one uses standard shell commands is no guarantee of portability, as a shell script can invoke arbitrary programs, which may or may not be present or compatible across different hosts. -- Dr Graham WheelerE-mail: [EMAIL PROTECTED] Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax:+27(21)24-3656 Data/Network Security SpecialistsWWW:http://www.cequrux.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: New tests for test(1)
Hi, At 4:01 am -0700 12/8/99, Aaron Smith wrote: this seems undesirable to me, since using it immediately makes your shell scripts nonportable. i liked the ls -t suggestion though. Further, isn't test a builtin for most (all?) shells? Sounds like a can of worms to me... On Thu, Aug 12, 1999 at 11:18:50AM +0200, Graham Wheeler wrote: thinking - wouldn't it be a good idea to add some new tests to test(1), to compare files based on criteria like size or modification date? Anyone else think this is a good idea? -- Bob Bishop (0118) 977 4017 international code +44 118 [EMAIL PROTECTED]fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: New tests for test(1)
On Thu, 12 Aug 1999 12:26:41 GMT, Bob Bishop wrote: Further, isn't test a builtin for most (all?) shells? Sounds like a can of worms to me... If your only motivation for saying it's a can of worms is that test is usually a builtin, don't sweat it. Lots of scripts insist on using /bin/test . Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: New tests for test(1)
On Thu, 12 Aug 1999 12:22:39 +0200, Sheldon Hearn wrote: Their code isn't useful in this case, since they've merged in a pdksh-derived version of test. How about we do the same? :-) By the way, OpenBSD have _also_ incorporated NetBSD's test. *evil.grin* Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: New tests for test(1)
thinking - wouldn't it be a good idea to add some new tests to test(1), to compare files based on criteria like size or modification date? So far it has been policy for FreeBSD not to add options to commandline utilities that are replaceable by simple shell script constructs. Especially if that other construct is POSIX-compliant. Examples: - An option to date(1), which would print the machine's idea of the time, no matter what $TZ is set it. Easily replaceable by (unset TZ; date) - An option to a tool that puts out a single line of text to stdout. The option would make it print its line without the final newline. Easily replaceable by backquotes echo `thistool` Clearly, the functionality discussed falls into this category. ls -t and head are specified in POSIX, thus it isn't affected by the usualy shell script unportability like another poster implied. this seems undesirable to me, since using it immediately makes your shell scripts nonportable. i liked the ls -t suggestion though. Further, isn't test a builtin for most (all?) shells? Sounds like a can of worms to me... FreeBSD's /bin/sh uses the external /bin/test. Most other shells in common use have it built in. You are right that this would confuse people no end since most couldn't use the same test(1) arguments in theirs scripts and interactivly. In a word, I'm against it. Whatever you want this for, it's the far better solution to have your own test(1)-like utility in your personal search path. Martin -- % Martin Cracauer [EMAIL PROTECTED] http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: how fast get real/absolute path of file
"Steven Jurczyk" [EMAIL PROTECTED] writes: How fast get real / absolute path of specified file. I try use readlink, but this slow (for path /home/web/docs/index.htm must be done 4 or more (if this path have symlinks) readlink's - for /home, /home/web, /home/web/docs and /home/web/docs/index.htm). Is any faster/simpler method for getting absolute path of file? I would use realpath(3). What's your application where that's not fast enough? /assar To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: libcompat proposition
On Wed, 11 Aug 1999, Warner Losh wrote: In message [EMAIL PROTECTED] "Brian F. Feldman" writes: : What do you all think about growing a gnu subdirectory in src/lib/libcompat? : Things like a getopt_long implementation (yes, if it will be accepted, : I am volunteering to write it...) would go there, and all sorts of lame : GNU libc cruft that we can try to be more compatible with. src/gnu/lib/libgnucompat might be better if is was GPL code. We've been trying to keep GPL'd code walled off from other code in the system. I'd be rewriting the code to make it freed, and put it in libcompat/gnu. I wouldn't be taking encumbered code to put in a standard library that would normally be free... Warner Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Various Questions
But what happens if you write a program which does whatever ioctl is required to unpromiscify an interface and run it on an unpromiscuous interface, does it print a message to syslog even though promiscuous mode was never enabled in the first place? Like I said, I seem to get the intended behaviour. vty1 - start trafshow Aug 12 12:26:41 axl /kernel: xl0: promiscuous mode enabled vty2 - start trafshow vty1 - kill trafshow vty2 - kill trafshow Aug 12 12:27:22 axl /kernel: xl0: promiscuous mode disabled :-) If everything works ok , howabout one of the developers commits this modification to /sys/net/if.c ? - Cillian To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: New tests for test(1)
On Thu, 12 Aug 1999, Brian F. Feldman wrote: On 12 Aug 1999, Dag-Erling Smorgrav wrote: Graham Wheeler [EMAIL PROTECTED] writes: I was writing a script yesterday, and I wanted to have a test to compare the modification time of two files. test(1) doesn't have the ability to do this. In the end I worked around this by using make(1), but it set me thinking - wouldn't it be a good idea to add some new tests to test(1), to compare files based on criteria like size or modification date? NetBSD's test(1) utility has this (-nt and -ot). We should probably merge in their changes. Hmm... this is in pdksh too... In other words, I think we've come upon more reasons to switch. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: libcompat proposition
Brian F. Feldman wrote: On Wed, 11 Aug 1999, Warner Losh wrote: In message [EMAIL PROTECTED] "Brian F. Feldman" writes: : What do you all think about growing a gnu subdirectory in src/lib/libcompat? : Things like a getopt_long implementation (yes, if it will be accepted, : I am volunteering to write it...) would go there, and all sorts of lame : GNU libc cruft that we can try to be more compatible with. src/gnu/lib/libgnucompat might be better if is was GPL code. We've been trying to keep GPL'd code walled off from other code in the system. I'd be rewriting the code to make it freed, and put it in libcompat/gnu. I wouldn't be taking encumbered code to put in a standard library that would normally be free... If you're writing unencumbered code, placing it under libcompat/gnu may lead to confusion because all other directory paths containing gnu contain GPL'd code. Just stick it into libcompat. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: libcompat proposition
On Thu, 12 Aug 1999, Steve Kargl wrote: If you're writing unencumbered code, placing it under libcompat/gnu may lead to confusion because all other directory paths containing gnu contain GPL'd code. Just stick it into libcompat. That doesn't fit with the current organization. Choose: a. fsf b. gnu c. glibc If this were to be approved of, of course. -- Steve Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: libcompat proposition
In message [EMAIL PROTECTED] Steve Kargl writes: : If you're writing unencumbered code, placing it under : libcompat/gnu may lead to confusion because all other : directory paths containing gnu contain GPL'd code. : Just stick it into libcompat. Or libiberty :-) That way we can have a GPL-free libiberty, which would be something that many people would want. It would also force the FSF to move more of their code from GPL to LGPL since it is stallman's policy to release things under the LGPL when there are alternative interfaces available. Although the recent hacks by [EMAIL PROTECTED] to generically wrap any library in rcp calls so that the progrma using the library doesn't have any GPL tainted code compiled into its address space might change that I hate the GPL. It has too many different interpretations. Look at the currentsituation with Linux: Linus says loadable drivers in Linux aren't covered by the GPL, while Stallman insists that they are. Its interpretation is open to too many variables :-(. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: libcompat proposition
Brian F. Feldman wrote:
On Thu, 12 Aug 1999, Steve Kargl wrote:
If you're writing unencumbered code, placing it under
libcompat/gnu may lead to confusion because all other
directory paths containing gnu contain GPL'd code.
Just stick it into libcompat.
That doesn't fit with the current organization.
Choose:
a. fsf
b. gnu
c. glibc
d. other
src/lib/libcompat/{fsf,gnu,glibc} connotes GPL code.
src/lib/libcompat/other allows SysV, Solaris, Linux, etc.
compatibility functions.
--
Steve
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: libcompat proposition
In message [EMAIL PROTECTED] "Brian F. Feldman" writes: : There : is simply no reason to assume that anything under a gnu directory is GPLd, : or that anything GPLd is going to be under a gnu directory (which it's not.) I'm afraid there is. It has been stated many times in the past that all GPL'd software resides under gnu. This is true in the big (/usr/src/gnu) and in the small (src/sys/gnu). The gnu directory name is magic in the minds of many people, and has been for a long time in the FreeBSD project. While much of the actual software lives in /usr/contrib, those parts that are under GPL are still built in gnu/ It is confusing, despite your assertions to the contrary. That's just how FreeBSD has operated for as long as I can recall, certainly back to the 1.0 time frame. glibc or fsf do not carry these long term connocations. To some they might connote gpl'd code, but they are better choices for naming in the libcompat tree since it doesn't have the traditionally overloaded "gnu" term plus tell what the code is compatible with (which is how the directories in libcompat work. Contrib doesn't have a separate gnu dir, but that is irrelevant. Nothing is built in the contrib tree. It is all built in usr.bin or usr.sbin or gnu/usr.bin, etc. All the GPL'd parts of the contrib tree are built under gnu/... (it is a bug if they are not). Using it to support a gnu directory would likely have negative impact on the strength of your argument. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Whither makefiles for src/crypto/telnet/* ?
A long time ago I got some kinky modifications to telnet from a place in Germany the purpose of which was to encrypt telnet sessions. It did a Diffie-Hellman up front and used the common secret as a DES key sort of the way Kerberos does. It was called SRA telnet. It was vulnerable to monkey-in-the-middle, but it was better than nothing and unlike other encrypted session systems it had NO administrative overhead. I also added IDEA as an alternative encryption method just to sort of up the ante a bit. At one point I seem to remember that the cryto telnet sources sort of got combined inexorably with Kerberos, which made the idea of adding SRA in order to get a standalone encrypted telnet to be standard-issue sort of die. But today, just out of curiosity, I decided to see if it would be possible to resurrect the idea. In the scrypto section, I see that the telnet stuff is set aside nicely in its own spot. I was able to add my patches just fine, but it appears that the Makefiles are somewhere else. Maybe in with the kerberos stuff or something? Does anyone know how telnet actually gets built when you want a telnet/telnetd that uses encryption? I would once again like to add SRA to telnet/telnetd. There is something to be said for having something reasonably secure in the default (at least for the domestic audience) distribution. Yes, we can all go add the ssh port, but having an encrypted telnet work right out of the box is a good thing. So I can pretty easily turn this into something that can be added right into src/crypto/telnet, but I need to find out about the Makefile issue. Can anyone help? Thanks in advance. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: libcompat proposition
On Thu, 12 Aug 1999, Steve Kargl wrote: Brian F. Feldman wrote: If you're writing unencumbered code, placing it under libcompat/gnu may lead to confusion because all other directory paths containing gnu contain GPL'd code. Just stick it into libcompat. How about libcompat/gnuish? (Funny, it doesn't look gnuish.) -- Ben UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD 3.2 on a ThinkPad 360c [keyboard not working]
I am attempting to get FreeBSD 3.2 and/or 4.0 to go on a TP 360c. The problem I am having is that the keyboard works all the way up to sysinstall. I can use the keyboard in the visual kernel config/etc. I searched and found under 2.2 they suggested setting flags 0x10 on syscons. 0x10 isn't documented to do anything uner 3/4 but I tried anyway, nothing. I also noticed that flags 0x04 and 0x02 may be some use (on atkbc). I tried 0x4, 0x2, and 0x6 to no avail. help? Here are some additional details... I tried the 2.2.8-RELEASE install with the flags of '0x10' on sc0. That worked OK. I dug through the CVS repo and I have discovered that those are the XT keyboard options (flags 0x04 on atkbd). so I went into the CLI config on the 3.2-STABLE bootdisk at turned those flags on BOTH atkdb0 at atkbdc0 (just in case), still no luck. I have looked at the source for 2.2 syscons and 3.2 atkbd and I can not see what the difference is in the codeset initialization and keyboard translation for the 2 types. I would like to try 3.0-RELEASE, but I cannot find anything that old ;) Suggestions? -- David Cross | email: [EMAIL PROTECTED] Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science| Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: hey
That's because the resolver on the Sun box is archaic, whereas FreeBSD has an up-to-date (and legal) resolver. Can't remember which RFC defined the '_' as being illegal off-hand...but all modern resolvers will react the same. That site admin must be running an old implementation of BIND (or possibly NT!). -marc Marc Nicholas netSTOR Technologies, Inc. http://www.netstor.com "Fast, Expandable and Affordable Internet Caching Products" 1.877.464.4776 416.979.9000 fax: 416.979.8223 cell: 416.346.9255 On Thu, 12 Aug 1999, Michael Mannsberger wrote: a problem somebody had ping www.atayatirim.com.tr works under Sun but not in FreeBSD - why? FreeBSD doesn't like "_" in a URL bash-2.02$ ping www.atayatirim.com.tr ping: cannot resolve www.atayatirim.com.tr: Unknown server error bash-2.02$ nslookup www.atayatirim.com.tr Server: ns3.starmedia.com Address: 209.67.42.5 Non-authoritative answer: Name:ata_www_prm.atayatirim.com.tr Address: 195.174.236.9 Aliases: www.atayatirim.com.tr -mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: hey
On Thu, 12 Aug 1999, Michael Mannsberger wrote: ping www.atayatirim.com.tr works under Sun but not in FreeBSD - why? FreeBSD doesn't like "_" in a URL Uhm, that's a hostname, but yes, FreeBSD doesn't like it. Windows is okay with it, however. http://www.crynwr.com/crynwr/rfc1035/rfc1035.html#2.3.1. However explains why this hostname is not allowed. FreeBSD is not violating RFC. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - hawk% ping wam_notes.internal.chc-chimes.com ping: cannot resolve wam_notes.internal.chc-chimes.com: Unknown server error hawk% dig wam_notes.internal.chc-chimes.com |grep notes ; DiG 8.1 wam_notes.internal.chc-chimes.com ;; wam_notes.internal.chc-chimes.com, type = A, class = IN wam_notes.internal.chc-chimes.com. 1D IN CNAME notes.internal.chc-chimes.com. notes.internal.chc-chimes.com. 1D IN A 172.16.81.245 It should be noted that the dns server that my workstation queried is running FreeBSD and has no trouble _serving_ hostnames with an underscore. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
interacting with ISA PnP devices.
Hi, What is the path of least resistance for getting an unsupported ISA PnP device to the point where you can do I/O to it (inb,outb)? Do I need a driver, or is there some general purpose way for getting the device "up" to the point that you can use /dev/io and a user space application? (on -current) If I need to write a driver, would a device driver that just maps the device be considered useful (feasible to implement?)? This specific device is a "winmodem" which I believe I have enough hardware documentation to fiddle with, once I get past the ISA PnP interface. Thanks, -Ted (ISA PnP newbie) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Whither makefiles for src/crypto/telnet/* ?
On Thu, Aug 12, 1999 at 11:31:27AM -0700, Nick Sayer wrote: In the scrypto section, I see that the telnet stuff is set aside nicely in its own spot. I was able to add my patches just fine, but it appears that the Makefiles are somewhere else. Maybe in with the kerberos stuff or something? Does anyone know how telnet actually gets built when you want a telnet/telnetd that uses encryption? Just a me too. I would really like to know how this is doen also. -- --Travis When it comes to violence, morality and the young, we're the Idiot Nation, the laughingstock not only of the civilized world but of the highly-wired generation of kids we're supposedly trying to protect. Jon Katz To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re:(2) hey
Well, I am the person who has this problem. The RFCs does not explicitly say that we should not use underscore character as far as I understood. But it suggests which characters we should use. Also in RFC1033 it says (well the status of this one is UNKNOWN though) - The domain system allows a label to contain any 8-bit character. Although the domain system has no restrictions, other protocols such as SMTP do have name restrictions. Because of other protocol restrictions, only the following characters are recommended for use in a host name (besides the dot separator): "A-Z", "a-z", "0-9", dash and underscore - So Solaris does the right thing by understanding underscore I guess. Since it is not forbidden to use it in hostnames. http://www.crynwr.com/crynwr/rfc1035/rfc1035.html#2.3.1. - For example, when naming a mail domain, the user should satisfy both the rules of this memo and those in RFC-822. When creating a new host name, the old rules for HOSTS.TXT should be followed. This avoids problems when old software is converted to use domain names. The following syntax will result in fewer problems with many applications that use domain names (e.g., mail, TELNET). domain ::= subdomain | " " subdomain ::= label | subdomain "." label label ::= letter [ [ ldh-str ] let-dig ] ldh-str ::= let-dig-hyp | let-dig-hyp ldh-str let-dig-hyp ::= let-dig | "-" let-dig ::= letter | digit letter ::= any one of the 52 alphabetic characters A through Z in upper case and a through z in lower case digit ::= any one of the ten digits 0 through 9 - BTW. I could not really understand this explanation in RFC1035. This is very cryptic for me :( Thanks for the help Evren Yurtesen [EMAIL PROTECTED] Bill Fumerola wrote: On Thu, 12 Aug 1999, Michael Mannsberger wrote: ping www.atayatirim.com.tr works under Sun but not in FreeBSD - why? FreeBSD doesn't like "_" in a URL Uhm, that's a hostname, but yes, FreeBSD doesn't like it. Windows is okay with it, however. http://www.crynwr.com/crynwr/rfc1035/rfc1035.html#2.3.1. However explains why this hostname is not allowed. FreeBSD is not violating RFC. -- - bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp - - ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED] - hawk% ping wam_notes.internal.chc-chimes.com ping: cannot resolve wam_notes.internal.chc-chimes.com: Unknown server error hawk% dig wam_notes.internal.chc-chimes.com |grep notes ; DiG 8.1 wam_notes.internal.chc-chimes.com ;; wam_notes.internal.chc-chimes.com, type = A, class = IN wam_notes.internal.chc-chimes.com. 1D IN CNAME notes.internal.chc-chimes.com. notes.internal.chc-chimes.com. 1D IN A 172.16.81.245 It should be noted that the dns server that my workstation queried is running FreeBSD and has no trouble _serving_ hostnames with an underscore. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: changing root device to ...
Cillian Sharkey scribbled this message on Aug 12: is the system still booting off the IDE disk (if present) ? Yes. But not from the SCSI You can try setting the BIOS to boot from the SCSI disk which should do the trick..unless you have a crappy BIOS that doesn't let you do that.. :( another trick is to not include your IDE disks in the bios config... FreeBSD will still probe and detect ide disks even when the bios doesn't know about them, unlike floppy drives... I used to boot off a scsi drive w/ an idea drive when my bios didn't have more than a A, C, CDROM options for boot... -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re:(2) hey
Well, I am the person who has this problem. The RFCs does not explicitly say that we should not use underscore character as far as I understood. But it suggests which characters we should use. RFC 952 1. A "name" (Net, Host, Gateway, or Domain name) is a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus sign (-), and period (.). Note that periods are only allowed when they serve to delimit components of "domain style names". RFC 1101 The current syntax for network names, as defined by [RFC 952] is an alphanumeric string of up to 24 characters, which begins with an alpha, and may include "." and "-" except as first and last characters. This is the format which was also used for host names before the DNS. Upward compatibility with existing names might be a goal of any new scheme. The above two documents limit the characters that may be used a a _ is not one of them. FreeBSD behaves correctly in this manner. RFC 1033 is only a informational RFC and should not be treated as a standard. glenn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: (2) hey
Well, I am the person who has this problem. The RFCs does not explicitly say that we should not use underscore character as far as I understood. But it suggests which characters we should use. RFC 952 1. A "name" (Net, Host, Gateway, or Domain name) is a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus sign (-), and period (.). Note that periods are only allowed when they serve to delimit components of "domain style names". RFC 1101 The current syntax for network names, as defined by [RFC 952] is an alphanumeric string of up to 24 characters, which begins with an alpha, and may include "." and "-" except as first and last characters. This is the format which was also used for host names before the DNS. Upward compatibility with existing names might be a goal of any new scheme. The above two documents limit the characters that may be used a a _ is not one of them. FreeBSD behaves correctly in this manner. But the DNS is used to hold all sorts of information. For example, how do you reconcile domain names like: 42.10.202.144.IN-ADDR.ARPA in the DNS? It violates the "starts with alpha" "requirement" in 952 and 1101 that you quotes, yet we use these things all the time. In fact, you can send email to that domain name because it has an A record associated with it, as well as a PTR record. I've always thought that the code that barfs on these names in gethostbyname() really violates the "be conservative in what you send, and liberal in what you receive" thought that made the Internet work. Yeah, yeah, BIND does it, but that's no excuse, either. What do I know; I was just the first chair of the domain name working group in the IETF so many years ago before it got fashionable. grumble, louie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re:(2) hey
On Fri, 13 Aug 1999, Evren Yurtesen wrote: Well, I am the person who has this problem. The RFCs does not explicitly say that we should not use underscore character as far as I understood. This is a common misunderstanding. The only valid characters in hostnames to be used on the global internet are letters, numbers and the dash character, "-". Underscores are not valid, at all, period. I realize that the RFC's don't seem to be clear on this point, however you can rest assured that such is the case. Good luck, Doug To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: (2) hey
But the DNS is used to hold all sorts of information. For example, how do you reconcile domain names like: 42.10.202.144.IN-ADDR.ARPA in the DNS? It violates the "starts with alpha" "requirement" in 952 and 1101 that you quotes, yet we use these things all the time. In fact, you can send email to that domain name because it has an A record associated with it, as well as a PTR record. How do I reconcile it? Well I must admit that I have not seen that one before. However just because there is a domain out there that is incorrect and will resolve does not mean that we should allow others. The way I reconcile this is that we need a patch for the resolver and I will be sure to mail one to the Internet Software Consortium. There are a number of cases where there are issues with implimentations of protocols, TCP, RMON where they are fixed one problem at a time. I've always thought that the code that barfs on these names in gethostbyname() really violates the "be conservative in what you send, and liberal in what you receive" thought that made the Internet work. Yeah, yeah, BIND does it, but that's no excuse, either. I sort of agree with you here, however allowing this particular situation to occur has just increased the number of non standard domain names. What do I know; I was just the first chair of the domain name working group in the IETF so many years ago before it got fashionable. In that case you will know a hell of a lot more than me and I honestly do not want to contradict you. I was 11 when 952 was written and I do not claim to know the reasons or motivations behind the decisions that resulted in that draft. However the Internet is a great deal different, there are a lot more people with a great deal less knowledge and understanding maintaining things like DNS servers etc. I feel that the live and let live attitude that you expouse worked when people like yourself, Jon Pollard etc were the people controling things. That is just no longer the case. glenn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: (2) hey
Today Louis A. Mamakos wrote: RFC 952 1. A "name" (Net, Host, Gateway, or Domain name) is a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus sign (-), and period (.). Note that periods are only allowed when they serve to delimit components of "domain style names". RFC 1101 The current syntax for network names, as defined by [RFC 952] is an alphanumeric string of up to 24 characters, which begins with an alpha, and may include "." and "-" except as first and last characters. This is the format which was also used for host names before the DNS. Upward compatibility with existing names might be a goal of any new scheme. The above two documents limit the characters that may be used a a _ is not one of them. FreeBSD behaves correctly in this manner. But the DNS is used to hold all sorts of information. For example, how do you reconcile domain names like: 42.10.202.144.IN-ADDR.ARPA in the DNS? It violates the "starts with alpha" "requirement" in 952 and 1101 that you quotes, yet we use these things all the time. In fact, you can Read RFC 1123, it makes that perfectly valid. 2.1 Host Names and Numbers The syntax of a legal Internet host name was specified in RFC-952 [DNS:4]. One aspect of host name syntax is hereby changed: the restriction on the first character is relaxed to allow either a letter or a digit. Host software MUST support this more liberal syntax. -- Jack O'NeillSystems Administrator / Systems Analyst [EMAIL PROTECTED] Crystal Wind Communications, Inc. Finger [EMAIL PROTECTED] for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages /dev/null -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: (2) hey
On Thu, 12 Aug 1999, Louis A. Mamakos wrote: But the DNS is used to hold all sorts of information. For example, how do you reconcile domain names like: 42.10.202.144.IN-ADDR.ARPA in the DNS? It violates the "starts with alpha" "requirement" in 952 and 1101 E.. even if that argument weren't silly on its face, the 'starts/ends with alpha' requirement has been relaxed for some time now. First for legacy domains like 3com.com, and next for newer ones like 411.com. The only rule that is currently being enforced is that no label can begin or end with a dash. that you quotes, yet we use these things all the time. In fact, you can send email to that domain name because it has an A record associated with it, as well as a PTR record. That IS a violation of the standard, since A records are not valid for hosts in in-addr.arpa. What do I know; I was just the first chair of the domain name working group in the IETF so many years ago before it got fashionable. Well, things change. :) Doug -- On account of being a democracy and run by the people, we are the only nation in the world that has to keep a government four years, no matter what it does. -- Will Rogers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: (2) hey
How do I reconcile it? Well I must admit that I have not seen that one before. However just because there is a domain out there that is incorrect and will resolve does not mean that we should allow others. The way I reconcile this is that we need a patch for the resolver and I will be sure to mail one to the Internet Software Consortium. There are a number of cases where there are issues with implimentations of protocols, TCP, RMON where they are fixed one problem at a time. Well I just got done again. Apparently the alphanumeric starting poing is allowed. Either way I feel my point in valid. glenn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: (2) hey
That IS a violation of the standard, since A records are not valid for hosts in in-addr.arpa. And next I suppose you'll tell me that PTR records are not valid outsize of the IN-ADDR.ARPA portion of the DNS namespace? What people really miss is that the DNS is a distributed database with delegation, used for all sorts of purposes. Some of them are widely known and almost universal (e.g., "look up and address for this host"). Some parts of the namespace are used as indicies for special purposes (e.g., translate a 4 octet IP address into a DNS name). The DNS can store names where the values used for each octet of a label in a DNS name can have any value at all between 0 and 255, including " ", ".", and other rude things. The general purpose mechansim can be (ab)sed for all sorts of purposes not originally envisioned (like Hesiod - you want to exclude "_" from user names?) While gethostbyname() and it's ilk are used for one limited, scoped purpose is no reason to break previously working configurations. That the ISC got a hair up their ass to break all those previously working names is just a shame. Depending on my application, I might just want to have some part of the DNS namespace return object that look like IP addresses for domain names which are not "hosts." The current implemention of bind makes that impossible unless I want to resort to using the raw resolver routines, which is just busy-work. This is just an example of "smart-ass" software that believes it knows better than the user does. louie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Q: panic: pipeinit: cannot allocate pipe -- out of kvm -- code = 3
On Thu, 12 Aug 1999, Addr.com Web Hosting wrote: It happened more often then I am comfortable with (twice per day on one occasion). This is a machine running FreeBSD 3.0-STABLE on dual PII 400 with 1GB of ram and a DPT raid card. The machine is running semi-heavy load (http/mail/telnet/ftp), as well as nfs server and client. What could I do to avoid this sort of panic in the future? The first thing I would do is upgrade to a more recent -STABLE. Lots of things have changed since 3.0-STABLE. Even if this particular thing hasn't, there have been a number of nfs improvements, as well as assorted other changes. David Scheidt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: libcompat proposition
On Thu, 12 Aug 1999, Tim Vanderhoek wrote: src/lib/libgnucompat seems to be the best suggestion so far. I wonder where the line between libgnucompat and libfreebsdextension is, though. I've only been active here a few weeks but I've grown used to the "go ahead and do it" I know I'm about to get... Why not call it src/lib/libiberty and create a fully compatable version which is truly free? Quickly glancing through binutils-2.9's libiberty directory on gnudist.gnu.org (this is the cannonical version as near as I can tell) most of it is implemented in libc and quite a few files are PD. How would those functions which also exist in libc (or possibly other libraries, I don't know) be handled? Jamie To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: STAILQ macros..
In article [EMAIL PROTECTED], Daniel O'Connor [EMAIL PROTECTED] wrote: I am looking at the STAILQ macros defined in sys/queue.h and I am curious why it is necessary to declare stqh_last in the STAILQ_HEAD as a pointer to pointer, rather than just a pointer? (like the head pointer) When the list is empty, stqh_last points at stqh_first (which means it must be a pointer to pointer). That way, STAILQ_INSERT_TAIL doesn't have to treat an empty list as a special case. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "No matter how cynical I get, I just can't keep up."-- Nora Ephron To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: (2) hey
In message [EMAIL PROTECTED] "Louis A. Mamakos" writes: : It violates the "starts with alpha" "requirement" in 952 and 1101 : that you quotes, yet we use these things all the time. That requirement has been relaxed. See RFC 1123. Bottom line is that _ is an illegal character in a hostname, and FreeBSD is behaving correctly. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: (2) hey
In message 25455.934497542@localhost "Jordan K. Hubbard" writes: : So Solaris does the right thing by understanding underscore I guess. : Since it is not forbidden to use it in hostnames. : : It does not do the right thing and it is indeed forbidden. :) Also, all modern versions of bind specifically prohibit all characters that are not allowed to make writing buffer overflow easter eggs much harder. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Threaded X libraries
I'm attempting to build the X11 libs with the thread safety stuff (I beleive Linux can already be built like this) and have discovered when linking that we don't have the getpwnam_r getpwuid_r functions in out libc_r. Is anyone planning on adding these? Stephen It's all part of my plan to make SDL (Sam Lantinga's Simple Direct Media Layer) work. It dies quite frequently when starting sound graphics in some of the test apps. I am suspicious that it requires a threadsafe libX11. -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true."Robert Wilensky, University of California To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD 3.2 on a ThinkPad 360c [keyboard not working]
I am attempting to get FreeBSD 3.2 and/or 4.0 to go on a TP 360c. The problem I am having is that the keyboard works all the way up to sysinstall. I can use the keyboard in the visual kernel config/etc. I searched and foun d under 2.2 they suggested setting flags 0x10 on syscons. 0x10 isn't document ed to do anything uner 3/4 but I tried anyway, nothing. I also noticed that flags 0x04 and 0x02 may be some use (on atkbc). I tried 0x4, 0x2, and 0x6 t o no avail. help? Here are some additional details... I tried the 2.2.8-RELEASE install with the flags of '0x10' on sc0. That worked OK. I dug through the CVS repo and I have discovered that those are the XT keyboard options (flags 0x04 on atkbd). so I went into the CLI config on the 3.2-STABLE bootdisk at turned those flags on BOTH atkdb0 at atkbdc0 (just in case), still no luck. The flag 0x04 (ALT_SCANCODESET for the XT keyboard) is for atkbd (AT keyboard driver). It is not for atkbdc (keyboard controller driver). I have looked at the source for 2.2 syscons and 3.2 atkbd and I can not see what the difference is in the codeset initialization and keyboard translation for the 2 types. I would like to try 3.0-RELEASE, but I cannot find anything that old ;) You are quite right that the code in question was just moved from sc to atkbd and there is essentially no difference between the two versions. This is the first time that I hear the flag 0x10 for sc works in 2.X, but the flag 0x4 for atkbd does not in 3.1 or later :-( I think I heard just last month that the flag works for ThinkPad 360CE... You say the keyboard works the kernel config menu and up to sysinstall, but it does not work in sysinstall and you cannot install the OS. Would you see if hitting the CAPS LOCK key changes the CAPS LED light? Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Is there any plan to newbuslize for 3-stable?
If my patch for pcm/ESS sound chip apply to FreeBSD, may I send-pr
with old-config style?
Yes, current pcm sound driver is old-config, but "Cameron Grant"
[EMAIL PROTECTED] is working to newbuslize.
I create patch for 4-current sys/i386/isa/snd. It fix for
pcm/ESS-ISA sound driver.
All ESS-ISA specific changes are quoted in (d-bd_flags BD_F_ESS).
MIHIRA Sanpei Yoshiro
diff -uNr snd.org/CARDS snd/CARDS
--- snd.org/CARDS Wed Aug 11 10:36:53 1999
+++ snd/CARDS Wed Aug 11 10:21:33 1999
@@ -357,3 +357,4 @@
+$Id$
diff -uNr snd.org/README snd/README
--- snd.org/README Wed Aug 11 10:36:53 1999
+++ snd/README Wed Aug 11 10:21:33 1999
@@ -222,3 +222,5 @@
the product. Too bad that no one of the chip/card manufacturers I
have contacted by email regarding missing or inconsistent documentation
on their products did even care to reply to my messages.
+
+$Id$
diff -uNr snd.org/ad1848.c snd/ad1848.c
--- snd.org/ad1848.cWed Aug 11 10:36:53 1999
+++ snd/ad1848.cWed Aug 11 10:21:33 1999
@@ -40,6 +40,10 @@
* http://www.opti.com/for the OPTi931
*/
+/*
+ * $Id$
+ */
+
#include i386/isa/snd/sound.h
#if NPCM 0
diff -uNr snd.org/clones.c snd/clones.c
--- snd.org/clones.cWed Aug 11 10:36:53 1999
+++ snd/clones.cWed Aug 11 10:21:33 1999
@@ -33,6 +33,10 @@
* in the Voxware 3.5 distribution.
*/
+/*
+ * $Id$
+ */
+
#include i386/isa/snd/sound.h
#if NPCM 0
diff -uNr snd.org/dmabuf.c snd/dmabuf.c
--- snd.org/dmabuf.cWed Aug 11 10:36:53 1999
+++ snd/dmabuf.cWed Aug 11 10:21:33 1999
@@ -31,7 +31,12 @@
*
*/
+/*
+ *$Id$
+ */
+
#include i386/isa/snd/sound.h
+#include i386/isa/snd/sbcard.h
#include i386/isa/snd/ulaw.h
#define MIN_CHUNK_SIZE 256 /* for uiomove etc. */
@@ -183,12 +188,13 @@
* This happens if the size has changed _and_ the new size
* is smaller, or it matches the blocksize.
*/
- if (l != b-dl (b-dl == 0 || lb-dl || l == d-play_blocksize) ) {
+ if ((l != b-dl (b-dl == 0 || lb-dl || l == d-play_blocksize))
+ || (d-bd_flags BD_F_ESS)) {
/* for any reason, size has changed. Stop and restart */
DEB(printf("wrintr: bsz change from %d to %d, rp %d rl %d\n",
b-dl, l, b-rp, b-rl));
DEB(printf("wrintr: dl %d - %d\n", b-dl, l);)
- if (b-dl != 0)
+ if (b-dl != 0 ! (d-bd_flags BD_F_ESS))
d-callback(d, SND_CB_WR | SND_CB_STOP );
/*
* at high speed, it might well be that the count
@@ -281,12 +287,16 @@
else
timeout = 1 ;
ret = tsleep( (caddr_t)b, PRIBIO|PCATCH, "dspwr", timeout);
- if (ret == EINTR)
- d-flags |= SND_F_ABORTING ;
+ if (ret == EINTR || ((d-bd_flags BD_F_ESS) timeout != 1
+ ret == EWOULDBLOCK b-rl == b-bufsize)) {
+d-flags |= SND_F_ABORTING ;
+ splx(s);
+ break;
+ }
splx(s);
- if (ret == EINTR || ret == ERESTART)
+ if (ret == ERESTART)
break ;
-continue;
+ continue;
}
splx(s);
@@ -319,7 +329,8 @@
if ( b-dl == 0 ) /* dma was idle, restart it */
dsp_wrintr(d) ;
splx(s) ;
- if (buf-uio_resid == 0 (b-fp (b-sample_size - 1)) == 0) {
+ if (buf-uio_resid == 0 (b-fp (b-sample_size - 1)) == 0
+ ! (d-bd_flags BD_F_ESS)) {
/*
* If data is correctly aligned, pad the region with
* replicas of the last sample. l0 goes from current to
@@ -472,9 +483,13 @@
int l = min(b-fl - 0x100, d-rec_blocksize);
l = DMA_ALIGN_MASK ; /* realign sizes */
DEB(printf("rdintr: dl %d - %d\n", b-dl, l);)
+#ifdef ESS_RECORD_WITH_NORMAL_DMA
+ if (l != b-dl || d-bd_flags BD_F_ESS) {
+#else
if (l != b-dl) {
+#endif
/* for any reason, size has changed. Stop and restart */
- if (b-dl 0 )
+ if (b-dl 0)
d-callback(d, SND_CB_RD | SND_CB_STOP );
b-dl = l ;
d-callback(d, SND_CB_RD | SND_CB_START );
@@ -572,10 +587,14 @@
else
timeout = 1; /* maybe data will be ready earlier */
ret = tsleep( (caddr_t)b, PRIBIO | PCATCH , "dsprd", timeout ) ;
- if (ret == EINTR)
+ if (ret == EINTR || ((d-bd_flags BD_F_ESS) timeout != 1
+ ret == EWOULDBLOCK b-fl == b-bufsize)) {
d-flags |= SND_F_ABORTING ;
+ splx(s);
+ break;
+ }
splx(s);
- if (ret == EINTR || ret == ERESTART)
+ if (ret == ERESTART)
break ;
continue;
}
@@ -719,8 +738,12 @@
if ( b-dl ) {
Re: libcompat proposition
On Thu, 12 Aug 1999, Tim Vanderhoek wrote: On Thu, Aug 12, 1999 at 02:21:11PM -0400, Brian F. Feldman wrote: I don't care if most of the directories called "gnu" in the current tree contain GPLd code. How I had to read your message about 4 or 5 times before I realized that "Oh, the ``gnu'' in the directory name doesn't mean it's GPL'd code". And that was cognition time with context...without my conclusion would have been reverse and erroneous. src/lib/libgnucompat seems to be the best suggestion so far. I wonder where the line between libgnucompat and libfreebsdextension is, though. I like my previous idea of libcompat/fsf, unless for some reason we want libcompat only for BSD compatibility, in which case it will probably never be changing... After reading what Warner had to say, I am in agreement now that gnu should not be used. And perhaps a TRULY free libiberty would be nice... -- This is my .signature which gets appended to the end of my messages. Brian Fundakowski Feldman _ __ ___ ___ ___ ___ [EMAIL PROTECTED] _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: FreeBSD 3.2 on a ThinkPad 360c [keyboard not working]
You are quite right that the code in question was just moved from sc to atkbd and there is essentially no difference between the two versions. This is the first time that I hear the flag 0x10 for sc works in 2.X, but the flag 0x4 for atkbd does not in 3.1 or later :-( I think I heard just last month that the flag works for ThinkPad 360CE... You say the keyboard works the kernel config menu and up to sysinstall, but it does not work in sysinstall and you cannot install the OS. Would you see if hitting the CAPS LOCK key changes the CAPS LED light? Kazu I have tried all of the keys, none of them function as labeled (not even Caps Lock). The left shift seems to be a double-enter or similiar. -- David Cross | email: [EMAIL PROTECTED] Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science| Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD 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: mmap bug
On Thu, Aug 12, 1999 at 12:02:19PM +0100, Tony Finch wrote: Matthew Dillon [EMAIL PROTECTED] wrote: One solution would be to map clean R+W pages RO and force a write fault to occur, allowing the system to recognize that there are too many dirty pages in vm_fault before it is too late and flush some of them. The downside of this is that, of course, we take unnecessary faults. Surely they aren't unnecessary faults if they are required for correctness? They _are_ unnecessary faults, if other correct solutions exist. The second alternative - to mark system daemons as special sounds much more attractive. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Q: panic: pipeinit: cannot allocate pipe -- out of kvm -- code = 3
:On Thu, 12 Aug 1999, Addr.com Web Hosting wrote: : : It happened more often then I am comfortable with (twice per day on one : occasion). This is a machine running FreeBSD 3.0-STABLE on dual PII 400 : with 1GB of ram and a DPT raid card. The machine is running semi-heavy load : (http/mail/telnet/ftp), as well as nfs server and client. What could I do : to avoid this sort of panic in the future? : :The first thing I would do is upgrade to a more recent -STABLE. Lots :of things have changed since 3.0-STABLE. Even if this particular thing :hasn't, there have been a number of nfs improvements, as well as assorted :other changes. : : :David Scheidt The latest versions of both STABLE and CURRENT do a better job scaling KVM to main memory. Upgrading should fix this problem. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: mmap bug
Arun Sharma wrote: The second alternative - to mark system daemons as special sounds much more attractive. Ok, now define the difference between "system daemons" and any other daemon (or, for that matter, any other process). - mark Mark Newton Email: [EMAIL PROTECTED] (W) Network Engineer Email: [EMAIL PROTECTED] (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: New tests for test(1)
I was writing a script yesterday, and I wanted to have a test to compare the modification time of two files. I've written programs to do this before as well. A more portable approach is find file1 -newer file2 ... thinking - wouldn't it be a good idea to add some new tests to test(1), to compare files based on criteria like size or modification date? Anyone else think this is a good idea? It would be nice, but there are portability issues. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: mmap bug
On Fri, Aug 13, 1999 at 03:04:43PM +0930, Mark Newton wrote: Arun Sharma wrote: The second alternative - to mark system daemons as special sounds much more attractive. Ok, now define the difference between "system daemons" and any other daemon (or, for that matter, any other process). That's easy. $ ps aux | head USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 23924 5.0 30.2 41312 38716 ?? SSat05PM 191:41.92 /usr/X11R6/bin/ root 0 0.0 0.0 00 ?? DLs 31Jul99 0:02.30 (swapper) root 1 0.0 0.2 504 200 ?? ILs 31Jul99 0:00.05 /sbin/init -- root 2 0.0 0.0 00 ?? DL 31Jul99 0:03.18 (pagedaemon) root 3 0.0 0.0 00 ?? DL 31Jul99 0:00.00 (vmdaemon) root 4 0.0 0.0 00 ?? DL 31Jul99 0:03.55 (bufdaemon) root 5 0.0 0.0 00 ?? DL 31Jul99 12:06.17 (syncer) The daemons which are involved in freeing up pages during low memory conditions qualify as system daemons. Making sure that these daemons don't block avoids the deadlock. -Arun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Max simultaneous NFS mounts?
What is the (default) maximum number of simultanous NFS mounts in FreeBSD 2.2.8 and 3.2? I was looking at 3.2 and it appears that 63 is the max, and this is tunable with kernel config option NFS_MUIDHASHSIZ. Is this correct? What is the maximum possible setting? Last, where could I have found this information myself? Thanks very much. Greg -- Gregory S. Sutter "Software is like sex; it's better mailto:[EMAIL PROTECTED] when it's free." -- Linus Torvalds http://www.pobox.com/~gsutter/ PGP DSS public key 0x40AE3052 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Is there any plan to newbuslize for 3-stable?
Hi. I have a question about new-bus code. Currently device style of FreeBSD-4-current is changing to newbus. But is there any plan to newbuslize for 3-stable? If my patch for pcm/ESS sound chip apply to FreeBSD, may I send-pr with old-config style? Yes, current pcm sound driver is old-config, but Cameron Grant gand...@vilnya.demon.co.uk is working to newbuslize. MIHIRA Sanpei Yoshiro To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
mmap bug
Oh, I'm sorry, I made a mistake when posting code. I posted incorrectly
patched version... This version correct :
#include stdio.h
#include stdlib.h
#include sys/types.h
#include sys/mman.h
#include unistd.h
#include fcntl.h
#include errno.h
main(int argc, char *argv[])
{
int fd;
int i;
int len=1024*1024*10; /*ie 10Mbytes*/
caddr_t addr;
char ttt[80];
int bunlink=0;
if (argc1 strcmp (argv[1], -u)==0)
bunlink=1;
for (i=0;;i++)
{
sprintf (ttt,%d,i);
printf (mmapping %ld byte region on file %s\n, len, ttt);
fd=open(ttt,O_CREAT|O_RDWR,0666);
if (fd0)
{
printf(open error %ld\n,errno);
exit(1);
}
lseek(fd,len-1,SEEK_SET);
write(fd,,1);
addr=mmap(0,len,PROT_READ|PROT_WRITE,MAP_SHARED,fd,0);
if (addr==MAP_FAILED)
{
printf(mmap error %ld,errno);
exit(1);
}
memset(addr,'x',len);
if ( munmap(addr, len) != 0 )
{
fprintf(stderr, munmap failed\n);
exit(EXIT_FAILURE);
}
close(fd);
if ( bunlink ) unlink (ttt);
}
}
Thank you for answers.
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Re: changing root device to ...
is the system still booting off the IDE disk (if present) ? Yes. But not from the SCSI You can try setting the BIOS to boot from the SCSI disk which should do the trick..unless you have a crappy BIOS that doesn't let you do that.. :( With fdisk I set the partition as bootable on the SCSI disk and it seems to boot it now but it can't mount the root partition as I can't figure out what device name to use as my root device in the /etc/fstab. I tried all the /dev/sd0* permutations I could find. /dev/sd0a should point to your root partition on the SCSI disk Regards, - Cillian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: BSD-XFS Update
matthew.al...@anheuser-busch.com (Alton, Matthew) writes: I am currently researching methods for implementing the 64-bit syscalls stat64(), fstat64(), lseek64() etc. delineated in the SGI design doc _64 Bit File Access_ by Adam Sweeney. Do the design docs indicate how inode numbers should interact with userland APIs? IIRC, inode numbers are 64-bit numbers in XFS. Since ino_t, st_ino of struct stat and d_fileno of struct dirent are only 32 bits, inode numbers may be truncated and not appear unique to userland. This would break the assumptions of some code (e.g. getcwd(3), when not using the kernel extension). To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: libcompat proposition
ch...@calldei.com (Chris Costello) writes: I'm in favor of a libgnucompat rather than gnu functions in libcompat. And how would a libgnucompat be different from libiberty? Except of course that it would be maintained by the FreeBSD folks... Or that it would be maintained at all. ;--) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: BSD XFS Port BSD VFS Rewrite
Tony Finch d...@dotat.at writes: Kenny Drobnack kdrob...@mission.mvnc.edu wrote: This may be a stupid question, but what's to keep from putting xfs in FreeBSD? Is there something in the licenses that says you can't use GPL'ed software and software under the BSD License together? Yes. The BSD licence requirement for acknowledging UCB in any advertising conflicts with the GPL requirement that further restrictions should not be added to those already in the GPL. This prevents you from relicensing BSD software under the GPL. It does not prevent you from selling an OS that has both BSD and GPL bits, as long as the GPL bits come with full source. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
New tests for test(1)
Hi all I was writing a script yesterday, and I wanted to have a test to compare the modification time of two files. test(1) doesn't have the ability to do this. In the end I worked around this by using make(1), but it set me thinking - wouldn't it be a good idea to add some new tests to test(1), to compare files based on criteria like size or modification date? Anyone else think this is a good idea? -- Dr Graham WheelerE-mail: g...@cequrux.com Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax:+27(21)24-3656 Data/Network Security SpecialistsWWW:http://www.cequrux.com/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: New tests for test(1)
On Thu, 12 Aug 1999, Graham Wheeler wrote: Hi all I was writing a script yesterday, and I wanted to have a test to compare the modification time of two files. test(1) doesn't have the ability to do this. In the end I worked around this by using make(1), but it set me thinking - wouldn't it be a good idea to add some new tests to test(1), to compare files based on criteria like size or modification date? A suggestion for another way to implement such a test: ls -1t file1 file2 | head -1 will give you the newest of the two... That's what I use when I need to do such tests. I guess it's easier and faster than make. Anyone else think this is a good idea? -- Dr Graham WheelerE-mail: g...@cequrux.com Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax:+27(21)24-3656 Data/Network Security SpecialistsWWW:http://www.cequrux.com/ Nadav To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Various Questions
-- snip --
if (pswitch) {
/*
* If the device is not configured up, we cannot put it
in
* promiscuous mode.
*/
if ((ifp-if_flags IFF_UP) == 0)
return (ENETDOWN);
if (ifp-if_pcount++ != 0)
return (0);
ifp-if_flags |= IFF_PROMISC;
log(LOG_INFO, %s%d: promiscuous mode enabled\n,
ifp-if_name, ifp-if_unit);
} else {
if (--ifp-if_pcount 0)
return (0);
ifp-if_flags = ~IFF_PROMISC;
---log(LOG_INFO, %s%d: promiscuous mode disabled\n,
---ifp-if_name, ifp-if_unit);
Shouldn't this be:
if (ipf-if_flags IFF_PROMISC) {
ipf-if_flags = ~IFF_PROMISC;
log(LOG_INFO, %s%d: promiscuous mode disabled\n, ifp-if_name,
ifp-if_unit);
}
Or is the test for IFF_PROMISC made earlier in the code? You
should only print a disabled message when it has previously
been enabled so that log file watchers can always match up
the up/down pairs.
Regards,
Niall
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Re: New tests for test(1)
Graham Wheeler g...@cequrux.com writes: I was writing a script yesterday, and I wanted to have a test to compare the modification time of two files. test(1) doesn't have the ability to do this. In the end I worked around this by using make(1), but it set me thinking - wouldn't it be a good idea to add some new tests to test(1), to compare files based on criteria like size or modification date? NetBSD's test(1) utility has this (-nt and -ot). We should probably merge in their changes. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Various Questions
On Thu, 12 Aug 1999 11:29:47 GMT, Niall Smart wrote: Or is the test for IFF_PROMISC made earlier in the code? You should only print a disabled message when it has previously been enabled so that log file watchers can always match up the up/down pairs. I've been using if.c modified exactly as suggested for a few months now and have experienced the intended results without apparent problems. Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Various Questions
if (--ifp-if_pcount 0)
return (0);
ifp-if_flags = ~IFF_PROMISC;
---log(LOG_INFO, %s%d: promiscuous mode disabled\n,
---ifp-if_name, ifp-if_unit);
Shouldn't this be:
if (ipf-if_flags IFF_PROMISC) {
ipf-if_flags = ~IFF_PROMISC;
log(LOG_INFO, %s%d: promiscuous mode disabled\n,
ifp-if_name,
ifp-if_unit);
}
Or is the test for IFF_PROMISC made earlier in the code? You
should only print a disabled message when it has previously
been enabled so that log file watchers can always match up
the up/down pairs.
yes that I think that would be a better idea to check to see if it is
actually in promiscuous mode first before printing out our disabled
message so all pairs match..however doesn't the following code
from above seem to gaurd against this situation : ?
if (--ifp-if_pcount 0)
return (0);
from what I can see, it only turns off promiscuous mode if
if_pcount reaches zero, ie. all requests for promiscuous mode
to be off account for all the previous requests for promiscuous
mode to be on..?
..then again I'm no expert kernel hacker (yet!) and I certainly
don't pretend to be one either, so I'll leave this to the
experts :-D
- Cillian
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message
Re: New tests for test(1)
On 12 Aug 1999 11:42:42 +0200, Dag-Erling Smorgrav wrote: NetBSD's test(1) utility has this (-nt and -ot). We should probably merge in their changes. Their code isn't useful in this case, since they've merged in a pdksh-derived version of test. How about we do the same? :-) Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Various Questions
Sheldon Hearn wrote: On Thu, 12 Aug 1999 11:29:47 GMT, Niall Smart wrote: Or is the test for IFF_PROMISC made earlier in the code? You should only print a disabled message when it has previously been enabled so that log file watchers can always match up the up/down pairs. I've been using if.c modified exactly as suggested for a few months now and have experienced the intended results without apparent problems. But what happens if you write a program which does whatever ioctl is required to unpromiscify an interface and run it on an unpromiscuous interface, does it print a message to syslog even though promiscuous mode was never enabled in the first place? Time to start reading some code methinks Niall + To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: BSD XFS Port BSD VFS Rewrite
On 12 Aug 1999 11:01:06 +0200 Dag-Erling Smorgrav d...@flood.ping.uio.no wrote: This prevents you from relicensing BSD software under the GPL. It does not prevent you from selling an OS that has both BSD and GPL bits, as long as the GPL bits come with full source. If you have an executable object which includes GPL'd code, you must supply FULL SOURCE for the *entire* object, not just the GPL'd bits. This is the real crux of the problem; the GPL has a virus-like nature. -- Jason R. Thorpe thor...@nas.nasa.gov To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: BSD XFS Port BSD VFS Rewrite
Jason Thorpe thor...@nas.nasa.gov writes: On 12 Aug 1999 11:01:06 +0200 Dag-Erling Smorgrav d...@flood.ping.uio.no wrote: This prevents you from relicensing BSD software under the GPL. It does not prevent you from selling an OS that has both BSD and GPL bits, as long as the GPL bits come with full source. If you have an executable object which includes GPL'd code, you must supply FULL SOURCE for the *entire* object, not just the GPL'd bits. We're talking separate binaries here. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Various Questions
On Thu, 12 Aug 1999 12:20:35 GMT, Niall Smart wrote: But what happens if you write a program which does whatever ioctl is required to unpromiscify an interface and run it on an unpromiscuous interface, does it print a message to syslog even though promiscuous mode was never enabled in the first place? Like I said, I seem to get the intended behaviour. vty1 - start trafshow Aug 12 12:26:41 axl /kernel: xl0: promiscuous mode enabled vty2 - start trafshow vty1 - kill trafshow vty2 - kill trafshow Aug 12 12:27:22 axl /kernel: xl0: promiscuous mode disabled :-) Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: New tests for test(1)
this seems undesirable to me, since using it immediately makes your shell scripts nonportable. i liked the ls -t suggestion though. -- Aaron Smith aa...@mutex.org On Thu, Aug 12, 1999 at 11:18:50AM +0200, Graham Wheeler wrote: thinking - wouldn't it be a good idea to add some new tests to test(1), to compare files based on criteria like size or modification date? Anyone else think this is a good idea? To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: mmap bug
Matthew Dillon dil...@apollo.backplane.com wrote: One solution would be to map clean R+W pages RO and force a write fault to occur, allowing the system to recognize that there are too many dirty pages in vm_fault before it is too late and flush some of them. The downside of this is that, of course, we take unnecessary faults. Surely they aren't unnecessary faults if they are required for correctness? Tony. -- f.a.n.finchd...@dotat.atf...@demon.nete pluribus unix To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: New tests for test(1)
Aaron Smith wrote: this seems undesirable to me, since using it immediately makes your shell scripts nonportable. i liked the ls -t suggestion though. Portability is a Good Thing, but I write a lot of one-off scripts in which portability isn't an issue. Also, just because one uses standard shell commands is no guarantee of portability, as a shell script can invoke arbitrary programs, which may or may not be present or compatible across different hosts. -- Dr Graham WheelerE-mail: g...@cequrux.com Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax:+27(21)24-3656 Data/Network Security SpecialistsWWW:http://www.cequrux.com/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: New tests for test(1)
Hi, At 4:01 am -0700 12/8/99, Aaron Smith wrote: this seems undesirable to me, since using it immediately makes your shell scripts nonportable. i liked the ls -t suggestion though. Further, isn't test a builtin for most (all?) shells? Sounds like a can of worms to me... On Thu, Aug 12, 1999 at 11:18:50AM +0200, Graham Wheeler wrote: thinking - wouldn't it be a good idea to add some new tests to test(1), to compare files based on criteria like size or modification date? Anyone else think this is a good idea? -- Bob Bishop (0118) 977 4017 international code +44 118 r...@gid.co.ukfax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: New tests for test(1)
On Thu, 12 Aug 1999 12:26:41 GMT, Bob Bishop wrote: Further, isn't test a builtin for most (all?) shells? Sounds like a can of worms to me... If your only motivation for saying it's a can of worms is that test is usually a builtin, don't sweat it. Lots of scripts insist on using /bin/test . Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: New tests for test(1)
On Thu, 12 Aug 1999 13:15:52 +0200, Graham Wheeler wrote: Portability is a Good Thing, but I write a lot of one-off scripts in which portability isn't an issue. Not to mention that following NetBSD's lead on issues relating to portability probably is seldom a bad idea. :-) Give PR 13091 a bash. Or a sh. Whatever works for you. :-) Number: 13091 Synopsis: [PATCH] pdksh-derived replacement for test(1) Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: New tests for test(1)
On Thu, 12 Aug 1999 12:22:39 +0200, Sheldon Hearn wrote: Their code isn't useful in this case, since they've merged in a pdksh-derived version of test. How about we do the same? :-) By the way, OpenBSD have _also_ incorporated NetBSD's test. *evil.grin* Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: New tests for test(1)
thinking - wouldn't it be a good idea to add some new tests to test(1), to compare files based on criteria like size or modification date? So far it has been policy for FreeBSD not to add options to commandline utilities that are replaceable by simple shell script constructs. Especially if that other construct is POSIX-compliant. Examples: - An option to date(1), which would print the machine's idea of the time, no matter what $TZ is set it. Easily replaceable by (unset TZ; date) - An option to a tool that puts out a single line of text to stdout. The option would make it print its line without the final newline. Easily replaceable by backquotes echo `thistool` Clearly, the functionality discussed falls into this category. ls -t and head are specified in POSIX, thus it isn't affected by the usualy shell script unportability like another poster implied. this seems undesirable to me, since using it immediately makes your shell scripts nonportable. i liked the ls -t suggestion though. Further, isn't test a builtin for most (all?) shells? Sounds like a can of worms to me... FreeBSD's /bin/sh uses the external /bin/test. Most other shells in common use have it built in. You are right that this would confuse people no end since most couldn't use the same test(1) arguments in theirs scripts and interactivly. In a word, I'm against it. Whatever you want this for, it's the far better solution to have your own test(1)-like utility in your personal search path. Martin -- % Martin Cracauer craca...@cons.org http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: how fast get real/absolute path of file
Steven Jurczyk st...@home.pl writes: How fast get real / absolute path of specified file. I try use readlink, but this slow (for path /home/web/docs/index.htm must be done 4 or more (if this path have symlinks) readlink's - for /home, /home/web, /home/web/docs and /home/web/docs/index.htm). Is any faster/simpler method for getting absolute path of file? I would use realpath(3). What's your application where that's not fast enough? /assar To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Recreating LKM
Jung, Michael mj...@npc.net writes: Ok How does one recreate /dev/lkm for 4.0-Current? It is no longer in /dev/MAKEDEV. There's no LKM support in -current any longer. /assar To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
need some tools
hello, I would like to know, if there a way (a tools) to make a partition fat16. thanks. -- flav To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: libcompat proposition
On Wed, 11 Aug 1999, Warner Losh wrote: In message pine.bsf.4.10.9908112337400.81521-100...@janus.syracuse.net Brian F. Feldman writes: : What do you all think about growing a gnu subdirectory in src/lib/libcompat? : Things like a getopt_long implementation (yes, if it will be accepted, : I am volunteering to write it...) would go there, and all sorts of lame : GNU libc cruft that we can try to be more compatible with. src/gnu/lib/libgnucompat might be better if is was GPL code. We've been trying to keep GPL'd code walled off from other code in the system. I'd be rewriting the code to make it freed, and put it in libcompat/gnu. I wouldn't be taking encumbered code to put in a standard library that would normally be free... Warner Brian Fundakowski Feldman _ __ ___ ___ ___ ___ gr...@freebsd.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: need some tools
In message 199908121645.qaa13...@hermes.epita.fr free bsd writes: : I would like to know, if there a way (a tools) to make a partition fat16. fdisk to mark the partion as fat16, newfs_msdos to splat a file system onto it. Warner To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: Various Questions
But what happens if you write a program which does whatever ioctl is required to unpromiscify an interface and run it on an unpromiscuous interface, does it print a message to syslog even though promiscuous mode was never enabled in the first place? Like I said, I seem to get the intended behaviour. vty1 - start trafshow Aug 12 12:26:41 axl /kernel: xl0: promiscuous mode enabled vty2 - start trafshow vty1 - kill trafshow vty2 - kill trafshow Aug 12 12:27:22 axl /kernel: xl0: promiscuous mode disabled :-) If everything works ok , howabout one of the developers commits this modification to /sys/net/if.c ? - Cillian To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: New tests for test(1)
On 12 Aug 1999, Dag-Erling Smorgrav wrote: Graham Wheeler g...@cequrux.com writes: I was writing a script yesterday, and I wanted to have a test to compare the modification time of two files. test(1) doesn't have the ability to do this. In the end I worked around this by using make(1), but it set me thinking - wouldn't it be a good idea to add some new tests to test(1), to compare files based on criteria like size or modification date? NetBSD's test(1) utility has this (-nt and -ot). We should probably merge in their changes. Hmm... this is in pdksh too... DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no Brian Fundakowski Feldman _ __ ___ ___ ___ ___ gr...@freebsd.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
freebsd4.0 (a little bit offtopic)
gentlemen, i am writing a short article on differences between 4.0 vs 3.2 versions for our corporate magazine - it's focused especially on networking/hacking. Is there a list of new features/approach ? Or what is your experience ? (i am testing myself, but more people == more interesting opinions). Thank you. Martin Lizner +420-2-7911637 Konstantinova 1472 Praha 4 CR Xerox does it again and again To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: New tests for test(1)
On Thu, 12 Aug 1999, Brian F. Feldman wrote: On 12 Aug 1999, Dag-Erling Smorgrav wrote: Graham Wheeler g...@cequrux.com writes: I was writing a script yesterday, and I wanted to have a test to compare the modification time of two files. test(1) doesn't have the ability to do this. In the end I worked around this by using make(1), but it set me thinking - wouldn't it be a good idea to add some new tests to test(1), to compare files based on criteria like size or modification date? NetBSD's test(1) utility has this (-nt and -ot). We should probably merge in their changes. Hmm... this is in pdksh too... In other words, I think we've come upon more reasons to switch. DES -- Dag-Erling Smorgrav - d...@flood.ping.uio.no Brian Fundakowski Feldman _ __ ___ ___ ___ ___ gr...@freebsd.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message Brian Fundakowski Feldman _ __ ___ ___ ___ ___ gr...@freebsd.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: need some tools
On Thu, 12 Aug 1999, Warner Losh wrote: In message 199908121645.qaa13...@hermes.epita.fr free bsd writes: : I would like to know, if there a way (a tools) to make a partition fat16. fdisk to mark the partion as fat16, newfs_msdos to splat a file system onto it. Warner This should have gone to freebsd-questions, not either -net, -hackers, or BOTH. Brian Fundakowski Feldman _ __ ___ ___ ___ ___ gr...@freebsd.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: libcompat proposition
Brian F. Feldman wrote: On Wed, 11 Aug 1999, Warner Losh wrote: In message pine.bsf.4.10.9908112337400.81521-100...@janus.syracuse.net Brian F. Feldman writes: : What do you all think about growing a gnu subdirectory in src/lib/libcompat? : Things like a getopt_long implementation (yes, if it will be accepted, : I am volunteering to write it...) would go there, and all sorts of lame : GNU libc cruft that we can try to be more compatible with. src/gnu/lib/libgnucompat might be better if is was GPL code. We've been trying to keep GPL'd code walled off from other code in the system. I'd be rewriting the code to make it freed, and put it in libcompat/gnu. I wouldn't be taking encumbered code to put in a standard library that would normally be free... If you're writing unencumbered code, placing it under libcompat/gnu may lead to confusion because all other directory paths containing gnu contain GPL'd code. Just stick it into libcompat. -- Steve To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
Re: libcompat proposition
On Thu, 12 Aug 1999, Steve Kargl wrote: If you're writing unencumbered code, placing it under libcompat/gnu may lead to confusion because all other directory paths containing gnu contain GPL'd code. Just stick it into libcompat. That doesn't fit with the current organization. Choose: a. fsf b. gnu c. glibc If this were to be approved of, of course. -- Steve Brian Fundakowski Feldman _ __ ___ ___ ___ ___ gr...@freebsd.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve!_ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-hackers in the body of the message
