[PATCH] automated make -j value
With multi-socket systems becoming more prevalent, and the continued
increase in cores per processors, I thought it would be nice for
'make -j' to gain some automation.
Attached is a patch that makes -j- be the same as
-j `sysctl -n kern.smp.cpus` and -j= be twice that.
I've also thought that maybe just supporting -j- would be better - with
a definition of
num_core = `sysctl -n kern.smp.cpus`
-j = MAX(num_core * 5 / 4, num_core + 1)
the idea being one would want a few more jobs than cores, but not a whole
lot more.
comments? (redirected back to list)
--
-- David ([EMAIL PROTECTED])
Index: main.c
===
RCS file: /home/ncvs/src/usr.bin/make/main.c,v
retrieving revision 1.160
diff -u -p -r1.160 main.c
--- main.c 17 Jul 2006 19:16:12 - 1.160
+++ main.c 14 Dec 2006 02:26:15 -
@@ -456,11 +456,20 @@ rearg:
char *endptr;
forceJobs = TRUE;
+ size_t jLlen = sizeof(jobLimit);
jobLimit = strtol(optarg, endptr, 10);
- if (jobLimit = 0 || *endptr != '\0') {
- warnx(illegal number, -j argument -- %s,
- optarg);
- usage();
+ if ((*optarg == '-' || *optarg == '=')
+ *endptr != '\0') {
+ sysctlbyname(kern.smp.cpus, jobLimit, jLlen,
+ NULL, 0);
+ if (*optarg == '=')
+ jobLimit *= 2;
+ } else {
+ if (jobLimit = 0 || *endptr != '\0') {
+ warnx(illegal number, -j argument -- %s,
+ optarg);
+ usage();
+ }
}
MFLAGS_append(-j, optarg);
break;
Index: make.1
===
RCS file: /home/ncvs/src/usr.bin/make/make.1,v
retrieving revision 1.99
diff -u -p -r1.99 make.1
--- make.1 29 Sep 2006 21:17:10 - 1.99
+++ make.1 14 Dec 2006 04:19:22 -
@@ -218,6 +218,14 @@ may have running at any one time.
Turns compatibility mode off, unless the
.Fl B
flag is also specified.
+The special values
+.It Ar -
+and
+.It Ar =
+causes
+.It Ar max_jobs
+to be set to the value returned from the kern.smp.cpus sysctl and twice
+kern.smp.cpus respectively.
.It Fl k
Continue processing after errors are encountered, but only on those targets
that do not depend on the target whose creation caused the error.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Anything weird about size or layout of 'struct thread'?
For a reason I haven't tracked down, this patch results in a panic on
6-STABLE when taking the GENERIC kernel and adding WITNESS, INVARIANTS,
INVARIANT_SUPPORT, MUTEX_DEBUG, KDB, KDB_TRACE, DDB.
Index: sys/proc.h
===
RCS file: /home/ncvs/src/sys/sys/proc.h,v
retrieving revision 1.432.2.11
diff -u -p -u -1 -r1.432.2.11 proc.h
--- sys/proc.h 4 Sep 2007 22:40:40 - 1.432.2.11
+++ sys/proc.h 18 Sep 2007 15:28:11 -
@@ -292,2 +292,3 @@ struct thread {
u_int64_t td_sticks; /* (k) Statclock hits in system mode. */
+ u_int xx_one;
u_int td_uuticks; /* (k) Statclock hits (usr), for UTS. */
The Panic(tm) [both on i386 and amd64]:
Timecounter TSC frequency 2192270208 Hz quality 800
Timecounters tick every 1.000 msec
panic: mutex sched lock not owned at ../../../kern/kern_fork.c:807
KDB: stack backtrace:
kdb_backtrace(c0a3d9d6,c0cd2f40,c0a3c5fc,e6fd2cd0,100,...) at 0xc07641de
= kdb_backtrace+0x2e
panic(c0a3c5fc,c0a3c715,c0a39de4,327,c83be4b3,...) at 0xc0744667 =
panic+0xb7
_mtx_assert(c0cd2c40,9,c0a39de4,327,,...) at 0xc0738ec7 =
_mtx_assert+0x87
fork_exit(c07297f0,c84b5c30,e6fd2d38) at 0xc072804a = fork_exit+0x5a
fork_trampoline() at 0xc099373c = fork_trampoline+0x8
--- trap 0x1, eip = 0, esp = 0xe6fd2d6c, ebp = 0 ---
It should not be a dependancies or stale issue - as I rm the kernel
compile directory before config'ing the kernel and I still get the panic.
Ideas?
--
-- David ([EMAIL PROTECTED])
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Useful tools missing from /rescue
Yar Tikhiy wrote: I've had to use /rescue recently and felt lack of a few basic tools in it, namely pgrep(1), head(1), tail(1), tee(1), and a text filter, e.g., sed(1). Well, in fact most functionality of pgrep(1), head(1), tail(1), and even tee(1) can be emulated if one has sed(1), but the tools are so tiny and convenient that it's a pity not to have them all handy during hard times. I also don't see the need for pgrep - I think needing that says your system is running multiuser pretty well. Also head and tail - why not just add 'more' as that would give more functionality if you're trying to read a file in /etc to fix something. In addition, there are chflags and chmod in /rescue, but there's no chown in it, so the toolset is a bit incomplete. I don't see the purpose of chown - if you have to fall back to /rescue you're user 'root' - and you're trying to fix enough so you can use standard /*lib /*bin chflags is needed so you can overwrite a file and chmod is needed so you can chmod +x something - those needs are clear. Please don't pestimize the build - unless there is a clear benefit. -- -- David ([EMAIL PROTECTED]) Q: Because it reverses the logical flow of conversation. A: Why is top-posting (putting a reply at the top of the message) frowned upon? Let's not play Jeopardy-style quoting ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Useful tools missing from /rescue
On Sat, Oct 13, 2007 at 10:01:39AM +0400, Yar Tikhiy wrote: On Wed, Oct 03, 2007 at 07:23:44PM -0700, David O'Brien wrote: I also don't see the need for pgrep - I think needing that says your system is running multiuser pretty well. First of all, I'd like to point out that /rescue doesn't need to be as minimal as /stand used to. Now, /rescue is a compact yet versatile set of essential tools that can help in any difficult situation when /*bin:/usr/*bin are unusable for some reason, not only in restoring a broken system while in single-user mode. A .. As for pgrep+pkill, it can come handy if one has screwed up his live system and wants to recover it without dropping the system to single-user. But if we take this just a little bit farther then why don't we go back to a static /[s]bin except for the few things one might need LDAP, etc.. for? That is, what's the purpose in continuing to duplicate /[s]bin into /rescue? /rescue should be just enough to reasonably get a system who's shared libs are messed up working again. /stand was a left-over from installation and not intended to be a sysadmins' savor - it just happened to be because we didn't clean up / after the bits were laid down. A valid objection to this point is that pgrep's job can be done with a combination of ps(1) and sed(1), so it's just a matter of convenience. I guess I'm still having trouble understanding why one would need 'ps' to fix a shared libs issue. Now is a reason to keep adding stuff to /rescue. Also why one would be running 'ps -aux', which is the only way I can think of to get more than one screen of output if a system is in trouble. The price for it in terms of disk space is next to nothing, and there are quite useless space hogs in /rescue already (see below on /rescue/vi.) Considering how few people are skilled in ed(1) these days, we have little choice but include vi. I won't speak for everyone, but I really like to use fancy shell commands, particularly during hard times: loops, pipelines, etc. So I don't have to enter many commands for a single task or browse I guess I'm not creative enough in the ways I've screwed up my systems and needed tools from /rescue. 8-) I don't see the purpose of chown - if you have to fall back to /rescue you're user 'root' - and you're trying to fix enough so you can use standard /*lib /*bin .. Having /rescue/chown is just a matter of completeness of the ch* subset of /rescue tools because chown's job can't be done by any other stock tools. If /rescue is complete enough, one can find more applications for it. E.g., the loader, a kernel, and /rescue /rescue wasn't intended to be well orthogonal. /rescue was part of he corner stone of the deal to switch to shared /[s]bin. -- -- David ([EMAIL PROTECTED]) ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Useful tools missing from /rescue
On Thu, Oct 18, 2007 at 02:04:21AM +0400, Yar Tikhiy wrote: On Mon, Oct 15, 2007 at 10:38:26AM -0700, David O'Brien wrote: I guess I'm not creative enough in the ways I've screwed up my systems and needed tools from /rescue. 8-) Just try to installworld FreeBSD/amd64 over a running FreeBSD/i386. ;-) I strongly feel that shouldn't be supported on a live system. So to me it shouldn't be an excuse to put a duplicated copy of /usr/[s]bin into /rescue. It is a delicate thing to get right - and there are easy ways to do it today: Boot from disc1; mount / and /usr; mv /mnt/etc /mnt/etc.hold; rm -rf the bits in bin,sbin,libexec; then run the install.sh from the disc1; mv /mnt/etc /mnt/etc.new ; mv /mnt/etc.hold /mnt/etc -- -- David ([EMAIL PROTECTED]) ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tcpdump(1) additions.
On Tue, Jun 29, 1999 at 06:54:06PM -0400, Bill Fumerola wrote: Unless there is strong feelings against it, I'd like to commit the smb patches (as seen on www.samba.org) Cool! I've been meaning to do this for quite some time. HOWEVER, please reference this PGP signed email (I'll send you the full copy) in the commit message: Sender: [EMAIL PROTECTED] From: Andrew Tridgell [EMAIL PROTECTED] To: [EMAIL PROTECTED] In-reply-to: [EMAIL PROTECTED] ([EMAIL PROTECTED]) Subject: Re: tcpdump patches copyright References: [EMAIL PROTECTED] Message-Id: [EMAIL PROTECTED] Date: Thu, 7 Jan 1999 10:47:03 +1100 yes, you are welcome to use those files under the tcpdump copyright. ..snip.. Note that the Tcpdump patches from www.samba.org are under the GPL. Andrew Tridgell also warned: I should warn you though that there are some security issues with my tcpdump-smb patches. It is possible for a malicious user to put packets on the wire that will cause a buffer overflow in the SMB parser in that code. That could lead to a root exploit. I just haven't got around to fixing it yet. -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: cvs commit: src/usr.bin/ftp Makefile fetch.c ftp.1 ftp.c ftp_var.h main.c util.c
... compared to the sources as of today. This gives minimal semantic difference from the way it worked before the change (which was that if FTP_PASSIVE_MODE existed, ftp used passive mode). I have to agree with Eivind, I know of people in my lab that have FTP_PASSIVE_MODE defined to nosense values since that is all that was required before. Now what are these poor souls to do when they upgrade to 3.3-R and their environment stops working -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: cvs commit: src/usr.bin/ftp Makefile fetch.c ftp.1 ftp.c ftp_var.h main.c util.c
On Fri, Jul 02, 1999 at 05:15:14PM -0700, Mike Smith wrote: I have to agree with Eivind, I know of people in my lab that have FTP_PASSIVE_MODE defined to nosense values since that is all that was required before. Now what are these poor souls to do when they upgrade to 3.3-R and their environment stops working Unless they were dumb enough to set it to "no", the "right" fix would have it keep working. So that makes three of us that believe the check should be agaist "no" rather than "yes". -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Reading CIS from kernel?
The Xircom ethernet driver needs to read/write PCCARD attribute memory from its probe routine, in order to identify the type of card and to beat ... then making crdread() and crdwrite() (in /sys/pccard/pccard.c) non-static and calling them directly from the driver code would be an easy workaround. Since no one has repsonded to this querry, I will be un-staticizing these so they will be available to drivers. -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Will FreeBSD ever see native IPv6 ??
So is FreeBSD *EVER* going to see native IPv6 ??
I attended a talk by a group of Intrusion Detection researchers. They
were basing their research on FreeBSD because they needed divert
sockets and found FreeBSD worked perfectly for this in this respect.
However, once they needed IPv6 and IPsec guess what happened??? They
moved to Linux and now have such a time investment in their custom kernel
hacks FreeBSD will never be an option for them again.
NetBSD and OpenBSD get more and more coverage from IPv6/IPsec
capabilities every day. FreeBSD has lost considerable ground if we want
to be a platform of choice for network and security researchers.
Now ever LSOF has IPv6 support for NetBSD and OpenBSD...
- Forwarded message from Vic Abell [EMAIL PROTECTED] -
Date: Wed, 21 Jul 1999 10:53:51 -0500
Subject: 64 bit lsof for Solaris 7; IPv6 support for {Net,Open}BSD
IPv6 Support for {Net,Open}BSD
==
..snip..
An lsof 4.45 pre-release distribution of the NetBSD and OpenBSD
sources with the IPv6 updates is available at:
..snip..
- End forwarded message -
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: newsyslog owner.group - owner:group
This one raised a number of eyebrows and a few people asked you to hold on to legacy support for a single release. It's a reasonable request, given the obscure error message one gets for providing the previously supported syntax: newsyslog: error in config file; bad permissions: /var/log/exim/mainlog exim.mail 640 7 *24Z I will be adding the ":" syntax to -STABLE before 3.3-R, and it will accept both ":" and ".". It was a one character fix in -CURRENT and I don't see any reason to ugly the code with supporting both syntaxes in -CURRENT. The change will be documented in 4.0-R's release notes. If people don't read that, then they will be in trouble in many other ways. Anyway, it has been only ":" in -CURRENT for a while now, and I haven't received any death threats, so people must not be tripping over this on a daily basis. :-) The problem with printing out warnings is ``newsyslog'' is usually run from cron(8), and anything printed out will often not be seen as I am of the opinion many do not read root's mail. -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: newsyslog owner.group - owner:group
COMPATIBILITY Previous versions of the chown utility used the dot (``.'') character to distinguish the group name. Begining with FreeBSD 4.0, this has been changed to be a colon (``:'') character so that user and group names may contain the dot character. Hum... I think I should change this text slightly. I should not refer to chown(8) so strongly. It's on my list now. :-) -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: newsyslog owner.group - owner:group
On Tue, Jul 27, 1999 at 05:25:23PM +0200, Sheldon Hearn wrote: Hi Brian, To paraphase Bill Paul: G that's part of my last name. -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: newsyslog owner.group - owner:group
A better patch would check to see if the text to the right of the '.'
is a valid group... However, the above will still parse
fred.jones:fred.jones
in the most desirable way, so I suppose the validity checking is
overkill.
This is what I plan to commit (w/in minutes):
-if ((group = strchr(q, ':')) != NULL) {
+if ((group = strchr(q, ':')) != NULL ||
+(group = strrchr(q, '.')) != NULL) {
It the becomes [almost totally] non-ambigitous (since the separator is
required) and allows "david.obrien.staff". In my mind more people use
dots in usernames than group names. Anyay, it is documented to use :,
and I am just trying to be "liberal in what is accepted" (w/o
obfuscating the code).
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: replacing grep(1)
$ uname -a
$ grep foo NONEXIST
Segmentation fault (core dumped)
$ gdb /usr/bin/grep grep.core
...
(no debugging symbols found)...
Core was generated by `grep'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libz.so.2...(no debugging symbols found)...done.
Reading symbols from /usr/lib/libc.so.3...done.
Reading symbols from /usr/libexec/ld-elf.so.1...done.
#0 0x280a8538 in ftello (fp=0x0)
at /FBSD/src/lib/libc/../libc/stdio/ftell.c:76
76 if (fp-_seek == NULL) {
(gdb) where
#0 0x280a8538 in ftello (fp=0x0)
at /FBSD/src/lib/libc/../libc/stdio/ftell.c:76
#1 0x280a84e1 in ftell (fp=0x0) at /FBSD/src/lib/libc/../libc/stdio/ftell.c:59
#2 0x80490b7 in free () at /FBSD/src/lib/libc/../libc/stdlib/malloc.c:1089
#3 0x80499f1 in free () at /FBSD/src/lib/libc/../libc/stdlib/malloc.c:1089
#4 0x804968b in free () at /FBSD/src/lib/libc/../libc/stdlib/malloc.c:1089
#5 0x8048d3d in free () at /FBSD/src/lib/libc/../libc/stdlib/malloc.c:1089
(gdb)
--
-- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED])
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: file(1) Magdir candidate: wintendo
I've had some interesting comments from David Bushong, motivating for inclusion of his Magdir candidate on PR 12554. He makes a strong case for a bloated file(1) Magdir. The only thing we're battling with is a filename for his submission. My advice would be to submit his PR to Chris Demtrito(sp?), file's maintainer. Then import NetBSD's file (Chris is a NetBSD guy). Thus we see what Chris calls it, and we stay in sync with the offical distribution. ...something on my list of things to update in src/contrib/ over the summer. -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Will FreeBSD ever see native IPv6 ??
various researchers and early-adopters, all of which can go to the KAME site and grab the patches to 3.2-stable if they want to play now, today. If we haven't done a good enough job of making that clear and are suffering from defections to other *BSDs because of this, then we just need to get the word out better. :-) Since KAME is probably closest to unified, I think we need to point people to the "offical" IPv6 patch set. The problem is the IPv6 wanting user does not know which of the available stacks to go with. It is easy to feel one would have to download 3 different stacks and experiement with all to determine which one works well. Lets help these people out. How about adding this to 3.3's RELEASE notes and a pointer from our website? (maybe also http://www.freebsd.org/handbook/install.html) -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: file(1) Magdir candidate: wintendo
My advice would be to submit his PR to Chris Demtrito(sp?), file's You may want to verify this. I'm pretty sure that Christos Zoulas (another NetBSD guy) maintains file(1): [EMAIL PROTECTED] My major Duh!! If Christos sees this thread, my apologies. There is no excuse for me not checking the source to make sure I was accurate before opening my mouth. -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: file(1) Magdir candidate: wintendo
My major Duh!! If Christos sees this thread, my apologies. David, I was trying to be helpful; sorry if my msg came across wrong. ^ Not in the least. I was being stupid and that's all. I'm certainly not mad about anything. (1) I don't like it when people just toss "facts" off the top of their head w/o making sure they are facts. I went against this. (2) people often get my name wrong, which is slightly irritating, and here I did it to someone else. -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Initio INI-* SCSI card support
Has anybody taken a look at the FreeBSD driver source at http://www.initio.com/source.zip for the INI-* cards? Is this something we should import into -CURRENT? -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Please review: rc file changes
I've had a week-end away from a keyboard to think about this. The only reason we have to use case statements for case-insensitive variable testing is because sh(1) doesn't offer any upper/lower case handling Also so that common settings can be added. Besides "yes" and "no" there could be other forms of wanting and not wanting. -- -- David([EMAIL PROTECTED] -or- [EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Fetch/wget/ftp: How to do a recursive ftp-get?
But which tool can do a command-line, recursive ftp-get? NcFTP versions 2 3 can. There are also purely command-line versions, called ncftpget ncftpput in the `ncftp3' port. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Developer assessment (was Re: A bike shed ...)
Let me give you some advice on FreeBSD list etiquette. You quoted *_114_* lines just to add FIVE?? Are you so busy you can't figure out how to delete lines in your editor? It is replies like this that have run many of the knowledgeable people from this list. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Which egcs port should I use?
On Sat, Nov 13, 1999 at 03:06:26AM +0100, Bjoern Fischer wrote: Which egcs would you recommend, if I want to minimize the hassle to switch from that egcs to the FreeBSD4.x native egcs? /usr/ports/lang/egcs. It is the one that is released code. ``gcc-devel'' is equivent to our -CURRENT and can bleed just as bad. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Proposal for the kill-list (userland nfs)
On Tue, Oct 05, 1999 at 03:49:31PM -0700, Alec Wolman wrote: Digital Unix, aka Compaq Tru64 Unix, formerly know as DEC OSF/1 supports this syntax. In fact, this is the only syntax it supports, IIRC, so FreeBSD is not the only OS to use it. Ultrix was the one that only suported this syntax. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Human readable df
On Mon, Nov 29, 1999 at 11:57:48PM -0700, Warner Losh wrote: Note, this uses the "traditional computer science SI extention" units. Where M == 1 20, G == 1 30, etc. Disk drive manufacturers use the real SI units where M == 10 ^ 6, G == 10 ^ 9, Some implimentations of ``df -h'' use "-h" for base 2, and "-H" for SI units. I believe Mike Haro's additions supports both. Same for ``du'' of course. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Human readable df
On Mon, Nov 29, 1999 at 10:37:08PM -0800, Kris Kennaway wrote: Here's a patch to add -h flag to df to produce human readable output. This makes it easier to read if the disk is big. You should submit this as a PR so it doesn't fall through the cracks (although it looks like Chris might take care of it, he seems to like adding options to commands :-) Mike Haro has this ready to commit in -CURRENT for quite some time. I've been pushing him to get it in 4.0-R. Please send any patches etc, to [EMAIL PROTECTED] so he can merge all the good ideas into one commit. -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: cvs commit: src/gnu/usr.bin/cc/cc_fbsd Makefile
On Thu, Jan 13, 2000 at 07:18:12AM -0500, Daniel Eischen wrote: Use _open internally within libc and libpthread. Have one "open" entry point that is the cancellation version of open. This is what it appears Solaris 7 does. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
desire for ftp.internat.freebsd.org mirror
Access to ftp.internat.freebsd.org from the USA (and presumably elsewhere) is an abomination. Isn't there *anyone* with an permanate FTP server that could officially mirror the crypto bits from ftp.internat.freebsd.org? -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: kerneld for -current
On Tue, May 30, 2000 at 10:17:22AM -0400, Yevmenkin, Maksim N, CSCIO wrote: is there any interest in ``kerneld'' (a-la Linux) for FreeBSD? i've got some working prototype Could you summerize what it offers and does? -- -- David ([EMAIL PROTECTED]) Disclaimer: Not speaking for FreeBSD, just expressing my own opinion. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: fixing flex definitions?
On Mon, Mar 05, 2001 at 02:55:22PM -0800, John Baldwin wrote: I'm guessing YY_PROTO is like __P() so it can be "compilable with a KR Old Testament compiler." Yes. And in this case, the output of lex *must* be portable to KR. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
doFS.sh newfs parameters for install floppy
Does anyone know of *any* problems with committing this diff?
It changes the % free space from the 8% default to 0.
Index: doFS.sh
===
RCS file: /home/ncvs/src/release/scripts/doFS.sh,v
retrieving revision 1.24.2.3
diff -u -r1.24.2.3 doFS.sh
--- doFS.sh 2001/01/14 08:24:48 1.24.2.3
+++ doFS.sh 2001/03/09 00:23:53
@@ -55,7 +58,7 @@
vnconfig -s labels -c /dev/r${VNDEVICE} ${FSIMG}
disklabel -Brw /dev/r${VNDEVICE} ${FSLABEL}
- newfs -i ${FSINODE} -T ${FSLABEL} -o space /dev/r${VNDEVICE}c
+ newfs -i ${FSINODE} -T ${FSLABEL} -o space -m 0 /dev/r${VNDEVICE}c
mount /dev/${VNDEVICE}c ${MNT}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: if_fxp - the real point
On Thu, Mar 08, 2001 at 06:13:07PM -0800, Alex Zepeda wrote: However, there *ARE* some of us who aren't intimate with your fxp problems. The problem does exist. I have a board that the `fxp' driver splits this out for: fxp0: warning: unsupported PHY, type = 17, addr = 2 fxp1: warning: unsupported PHY, type = 17, addr = 2 You've got a valid problem. Go away. "You've got a valid problem, go away." huh?? His points are very valid about maintenance of the `fxp' driver. His views on how to make something happen are what is a little out of touch. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: if_fxp - the real point
On Sat, Mar 10, 2001 at 10:30:08AM -0600, Peter Seebach wrote: For that matter, is the fxp still the most-recommended driver on Alpha? It *never* has been the recommended driver on FreeBSD/Alpha. The fxp driver has had issues on Alpha for a long time. Andrew will fix something with it, then it breaks again for some, etc... DG has an Alpha, but I don't think he has ever turned it on. He certainly has never done and Alpha-specific fxp fixes that I am aware of. The `guaranteed to work on Alpha driver' is anything supported by the `de' driver, as that is what the built-in NIC is on older Alpha's so OS's have no choice but deal with them. After that, I would say any of the `xl' 3Com cards. Bill Paul tested his just about all his drivers on an Alpha when developing them. The really nice thing about the `xl' 3Com cards is they don't have the alignment requirements of most of the other NICs in existence. Thus you can get really good performance on the Alpha. Behind the `xl' 3Com cards, would be any DEC 21143 based NIC which is supported by Bill Paul's `dc' driver. The nice thing about `de' and `dc' cards is SRM recognizes them. I got the impression there were some alignment issues that might be cheaper to solve on i386 than Alpha. Both `xl' and `fxp' cards do not have strict alignment issues (which makes them very nice and reduces a memory copy). The problems with the `fxp' cards is simply how its driver works on the Alpha. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Solution: Sendmail 8.11.3 on FreeBSD 4.2
On Tue, Mar 13, 2001 at 06:26:29PM +0300, Zaitsev Serg wrote: I have upgrade the Sendmail 8.11.3 on FreeBSD 4.2. But on FreeBSD 4.2 I got trouble with /usr/libexec/mail.local . Filling up /var/spool/mqueue a lot of files. /var/mail/user was empty. Mail stopped. chmod u+s /usr/libexec/mail.local Now mail works again. Perhaps you should read the documentation we supplied on this issue. bash$ cat /usr/src/UPDATING Updating Information for FreeBSD STABLE users This file is maintained by [EMAIL PROTECTED] Please send new entries directly to him. See end of file for further details. A reverse chronology since 4.0 was released is included, followed by the common items quick how-tos, followed by entries for versions of -current prior to 4.0 Release. ..snip.. 20001020: ** WARNING ** Sendmail has been updated. ** WARNING ** o mail.local(8) is no longer installed as a set-user-id binary. ..snip.. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: optimizing apache with php and nfs mounts
On Mon, Mar 12, 2001 at 10:34:32PM -0800, Gordon Tetlow wrote: On Mon, 12 Mar 2001, Dan Phoenix wrote: CC="gcc -O6 -fomit-frame-pointer" OPTIM="-O2 -DBUFFERED_LOGS" could some c guru tell me if this would be bad to use to an apache optimization? I need to compile apache on my own not with ports looking at makefile in apache13 in ports collection i see these optimization flags. along with --mmap-static module. can you use both -06 and -02 for optmization at the same time? -fomit-frame-pointer as well? -O6 and -O2 do seem a bit contradictory. I'm guessing it just uses -O6. -fomit-frame-pointer is not enabled per the -O flags so that does do something, but it does make it rather difficult to track down problems without a frame pointer. _ _ __/\_____ (_) __ _ | |__ __/\__ \/ / __| | | / _` | | '_ \\/ /_ _\ \__ \ | | | (_| | | | | | /_ _\ \/ |___/ |_| \__, | |_| |_| \/ |___/ Where did you even get the idea "-O6" did *_ANYTHING_*?? Don't people ever read the documentation anymore. 1. The highest -O setting GCC accepts is "-O3". 2. The base, system C compiler is known to produce bad code with -O2. We have been proclaiming this since as long as I have been with the Project. I probably qualify for the latter Optimizations are good and all, but I look at it this way: It's a mission critical webserver, I don't want it crashing. As a result, we compile ours with nothing higher that -O2 and no unusual optimizations. Sure, it might be a bit slower than it could have been, Do people ever actually test this? Or is there just the assumption that the more "optimizations" on the `cc' command line is a Great Thing(tm)? People do realize that for some code, -O2 is much worse than -O? Also for much code there is no difference in performance. Rather than do what you "think" will give the best results, why not actually benchmark it? but we don't have to worry about chasing down compiler bugs that interact strangly with the webserver code. Also, I think anything higher than -O2 actually produces a larger binary (it inlines functions whenever possible). 1. You need to use -O if you don't want to chase bugs 2. It is -O2 and above (ie, _includes_ -O2) that produces a larger binary. See -Os if you want smaller. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: optimizing apache with php and nfs mounts
On Tue, Mar 13, 2001 at 10:08:00AM -0800, Gordon Tetlow wrote: Actually, we did. Of course, our production stuff is still compiled with gcc 2.7.2.1. I think. Whatever the standard system compiler for FreeBSD-3.2 is. And that was at a time when the world was still compiled with -O2, wasn't it? The world has _NEVER_ been compiled at -O2 by default, nor has it ever been officially recommended. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Solution: Sendmail 8.11.3 on FreeBSD 4.2
On Wed, Mar 14, 2001 at 11:57:51AM +1000, Greg Black wrote: $ uname -rs FreeBSD 4.2-RELEASE $ cat /usr/src/UPDATING cat: /usr/src/UPDATING: No such file or directory Perhaps the documentation should be installed more thoroughly. If one is building and installing a new [latest] sendmail, they have /usr/src populated. Or was the new Sendmail compiled manually and installed using sources downloaded manually from ftp.sendmail.org? If so, then this whole discussion should be on a sendmail.org list, not FreeBSD one. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Solution: Sendmail 8.11.3 on FreeBSD 4.2
On Wed, Mar 14, 2001 at 12:27:02PM +1000, Greg Black wrote: This is the point where we disagree. The information in this file is in fact of interest to somebody who does a fresh install from CD as the simple way to upgrade from an earlier release. Huh??? If you do a fresh install from CD, you will get a sendmail+sendmail.cf+mail.local that are all in sync and setup properly. This thread (unless I majorly misunderstood it), is about someone taking a 4.x-RELEASE system and upgrading the sendmail to the latest 4-STABLE version. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: optimizing apache with php and nfs mounts
On Wed, Mar 14, 2001 at 01:19:31AM -0800, Alex Zepeda wrote: However, even the pgcc web page describes -O2 as safe. I won't even to there... Yes, scanning thru the ML leads me to believe some of these optimizations are pretty much untested. Which is kinda funny, since the ia32 bits are the most used ones or so it seems. Not untested -- but you should go grab a graduate text on compiler optimizations and familiarize yourself with the complexity of the problem. If hello_world.c showed a problem with an optimization, I guarantee it would be fixed. The current test case of holding up the entire FreeBSD kernel as showing an optimization problem doesn't cut it. If you care to trim it down to a single module showing the problem -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: if_fxp - the real point
On Wed, Mar 14, 2001 at 11:37:34AM -0800, Alfred Perlstein wrote: ALL the time. Microsoft has given the UC-Davis security and formal verification lab a multi-year grant to look at this problem. (the approach being researched is "model checking") How does one get the forms for these sort of grants? :) Write white paper, submit to M$. Or network at conference, have M$ friend tell you a proposal would be meet open arms. The typical University/research way of getting [commercial] grants. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: if_fxp - the real point
On Wed, Mar 14, 2001 at 02:41:53PM -0800, Kent Stewart wrote: With 2000 and above, your system will check for non-digitally signed dll's and etc. Being signed has nothing to do with correctly working. The project I was speaking about wanted to be able to do something about you buying that wonderful new video card, or ATA-100 card -- receving the vendor's device driver and finding it decreases the stability of your system. Windows has a specification and convention of how drivers should be written. How do you know some driver actually follows it? That is the basic problem this grant is researching. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: if_fxp - the real point
On Wed, Mar 14, 2001 at 04:51:14PM -0500, Dennis wrote: Why would they need to do that? Every time you load a program it updates the libraries, breaking older programs. Its a philosophical problem. You dont need a grant to figure it out. You JUST DON'T GET IT [academic research]. And any attempt to explain it to you will obviously be wasted time. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: optimizing apache with php and nfs mounts
On Wed, Mar 14, 2001 at 03:12:41PM -0800, Alex Zepeda wrote: Not untested -- but you should go grab a graduate text on compiler optimizations and familiarize yourself with the complexity of the problem. Care to recommend any starting places. You've piqued my interest. http://www.amazon.com/exec/obidos/ASIN/1558603204/ref=sim_books/107-1570516-8126104 Advanced Compiler Design and Implementation by Steven S. Muchnick (typical graduate text cost of $93.00!) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: /bin/ps thing
On Fri, Mar 16, 2001 at 11:04:43AM +, Jordan DeLong wrote: It seemed that send-pr was just for reporting issues, not for fixing them also Nope. At the bottom of the send-pr form, is a "How to fix" section. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: GCC Upgrade?
On Sat, Mar 17, 2001 at 10:46:42AM -0800, Alfred Perlstein wrote: GCC 2.95.3 was just released. I did notice that there are some bug fixes ... in the optimizer, and some various other fixes etc. Considering the recent discussion about incorrect code generation due to -O2 and above, I really, really don't think these fixes will help -O2. I need to do more testing with GCC 3.0, but I do have [some] hope. are there any plans to import this new release into the FreeBSD source ... some bugs in the optimizer". David will sync our compiler with the latest version when he feels that it's ready for FreeBSD. I was going to do it Friday, but the distribution file had yet to make it to any of the mirror sites. It probably has by now. So I'll do it Monday. GCC 2.95.3 will hi 4-STABLE after April 1st. Heck, April 1st might actually be the best day to do it. So if RELENG_4 is unfrozen by then, that's when I'll MFC it. ;) -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: GCC Upgrade?
On Mon, Mar 19, 2001 at 02:54:52PM +0100, Titus von Boxberg wrote: Since at least aug. 2000 (according to the mailing list archives) the exception handling in base system g++ is broken (at least for multithreaded programs) I am not aware of exception handling being broken (more so than in 4.x). Can you point me to a PR, or send me a _small_ sample program? -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: gcc and exceptions and frame.c
On Mon, Mar 19, 2001 at 04:32:36PM -0500, Alexander N. Kabaev wrote: It there any particular reason why you are using gcc295 from ports instead of FreeBSD stock compiler? I would assume because he has a 3.4 box: $ g++295 -v specs from /usr/local/lib/gcc-lib/i386-portbld-freebsd3.4/2.95.2/specs and the stock compiler there is 2.7.2.3. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: GCC Upgrade?
On Mon, Mar 19, 2001 at 08:12:18PM -0500, Alexander N. Kabaev wrote: The fix has been posted on the gcc-devel mailing list and Berndt Schmidt even included it into some of GCC 2.95.3-testXX release. And that time I decided that my job is done, but apparently Berndt managed to revert (most likely, by mistake) before release. I think my relative unrelated changes have been killed as part of the bigger sjlj exceptions rewrite by Mike Henderson :( From: Bernd Schmidt [EMAIL PROTECTED] Subject: 2.95.4 plans Date: Fri, 16 Mar 2001 16:18:03 + (GMT) To: [EMAIL PROTECTED] Now that 2.95.3 is out, I'll again accept suggestions what to include in 2.95.4, so please send candidate patches and bug reports. One major item that needs fixing is the sjlj eh problem; the fix for this had to be taken out of the 2.95.3 release since it introduced too many other problems. I would bring up the issue again with Bernd. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: GCC Upgrade?
On Tue, Mar 20, 2001 at 04:31:06PM -0500, Alexander N. Kabaev wrote: I certainly do not see that happening in FreeBSD 4-STABLE any time soon. It never will. FreeBSD-CURRENT might switch to DWARF2 some day, David O'Brien is the right person to ask about that. It will happen right after I MFC GCC 2.95.3. DWARF2 is required by the IA-64 psABI, and is supported better on the Alpha. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: 4.3-BETA world crashing 4.2-RELEASE kernel ?
First let me say to anyone reading the email I am replying to:
_ _ ___ __ _ _ _
| _ \ ___| \ | |/ _ \_ _|__| | ___ | |_| |__ (_)___
| | | |/ _ \ | \| | | | || | / _` |/ _ \ | __| '_ \| / __|
| |_| | (_) | | |\ | |_| || || (_| | (_) | | |_| | | | \__ \
|/ \___/ |_| \_|\___/ |_| \__,_|\___/ \__|_| |_|_|___/
On Wed, Mar 21, 2001 at 12:58:04PM -0700, Matt Simerson wrote:
# cd /usr/src
# make buildkernel KERNEL=KERNEL_CONFIG_FILE_NAME
# cd /usr/src; make buildworld
# make installworld
# make installkernel
# mergemaster
# reboot
The order or "make buildworld" and "make buildkernel" are 100% totally
BACKWARDS.
Lets explain why: There are times when the kernel source is changed to
use constructs of newer compiler/assembler/linker tools. Thus the kernel
will not build with an older set of tools. The what "make buildkernel"
does is use the tools (ie, those built from the most up to date sources)
that are built during "make buildworld" to compile a new kernel. Thus
"make buildworld" must PROCEED "make buildkernel".
Second, the install order above is not the conservative, careful
approach. One should issue "make installkernel reboot" after the
"make buildkernel" to ensure the new kernel works sufficiently well. If
not, one can always fall back to ``kernel.old''. Since there is no
``world.old''; after one does the "make installworld" backup tapes are
the only way of taking the system back to its previous state.
--
-- David ([EMAIL PROTECTED])
GNU is Not Unix / Linux Is Not UniX
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
Re: 4.3-BETA world crashing 4.2-RELEASE kernel ?
On Thu, Mar 22, 2001 at 12:51:00PM -0700, Matt Simerson wrote: Actually, they aren't backwards. You've gone and snipped the parts of my original message that show that the commands are being executed at the same time. I read you message twice and came away with the same idea. You should write more clearly. Maybe I'm understanding you incorrectly here but according to what you just said, a "make buildkernel" will fail unless you have a set of compiler/assembler/linker tools in /usr/obj that were built from the make buildworld process. This is inaccurate at best and I suspect it's just plain wrong. I can "rm -r /usr/obj/*", "cd /usr/src; make clean", and then "make buildkernel KERNEL=BLAH" and it will succeed and build a happy little fully functionaly kernel. I've done this hundreds of times with success. The ability to do a `make buildkernel' with an empty /usr/obj is a new feature. But back to your misunderstanding. What part about "if the kernel source is changed to use language features not supported by the existing installed tools, you cannot build a kernel with them" do you not understand?? You obviously was not active when 4.x upgraded Binutils from 2.9.1 to 2.10.0 and the many of the asm bits were changed at the same time to remove work arounds and bogusness done to satisfy Binutils 2.9.1. Second, the install order above is not the conservative, careful approach. One should issue "make installkernel reboot" after the "make buildkernel" to ensure the new kernel works sufficiently well. Maybe that's _YOUR_ method for installing but it's not necessarily the best one. Kernel's are not guaranteed to be backwards compatible and I've installed a shiny new kernel that worked just fine and allowed my machine to come up single user but because of some rude change in /etc/rc, ipfw, or any of a number of places the machine couldn't make it to multi-user and allow me to get back in (via the network). That you're doing this remotely is your problem. Ask any of the developers living on -CURRENT where often one wants to back out of a newly compiled world. The method I gave is the most sure and careful way. That you don't have consoles on your machines so you could do this properly doesn't mean what I posted isn't the safest and should be followed unless has special needs. Success at building and installing the kernel, world, AND running mergemaster gives me a reasonably good chance that when I issue the reboot, it'll come up nice and happy. I'm happy for you. But you have major flaws in your method where problems can bite you hard. As I said, I want users to know and use the safest method. I've seen enough email from users that were all confused about the right steps -- often getting confused from posts such as yours where you [hopefully] understand the consequences of your method and can deal with them. Many do not want to or cannot. Second, if I'm going through the bother of compiling a buildworld it's because I want the latest version of world on my system. Want != ability. I want a latest version of 5-CURRENT on my laptop, but CardBus is broken right now, so I am living with a Dec world. Such is life. If there are some problems with the new kernel, I'm not going to revert back to world.old. I'll fix whatever is screwed up with kernel and proceed. Oh! Want a job as a kernel hacker then? I'd like to have my CardBus working again (in current). Also my AHA-2930u2 on a K6-2 machine... -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: GCC Upgrade?
On Wed, Mar 21, 2001 at 01:35:30PM -0500, Alexander N. Kabaev wrote: This patch will work. According to Berndt Schimidt, there are some problems with it on HP/UX and that was the main reason why it was backed out. I never saw any ill effects on i386 with this patch though, while good efects include: a) working sjlj exceptions b) ability to compile QT2 with exceptions enabled and with -O2 flag without consuming ~400M memory for abnormal call egdes in GCC flow optimization pass. It has been committed now and will be MFC'ed to stable after tax day. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Intel driver doc's Take 2.
On Sat, Mar 24, 2001 at 06:31:44PM +0100, Luigi Rizzo wrote: 2) even if you have hardware with an "fxp" on board, adding a second supported card is cheap and easy -- nothing like having to put in a second video card; Many, many U1-form-factor systems have two fxp on-board NICs. No room to add third (and fourth) supported NIC. K THNX. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Intel driver doc's Take 2.
On Sat, Mar 24, 2001 at 03:11:54PM -0500, Dennis wrote: Most drivers are written without full docs. Feh. *EVERY* wpaul written Ethernet driver was written _with_ having the full docs. wpaul will not write a driver otherwise. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: problems with: /usr/src/lib/libc
On Sun, Mar 25, 2001 at 08:09:31PM +0200, Jochen Kaiser wrote: why are all my .o files in /usr/obj/usr/src/lib/libc and not in /usr/src/lib/libc ? Because that is how our make framework works w/in /usr/src See the readme in /usr/share/mk/ I changed syscalls.master, created new syscall, made headers in /usr/src/include and tried to make the libs via make install in /usr/src/lib/libc. ... How May I fix it? cd /usr/src/lib/libc make cleandir make cleandir # do NOT do a `make obj' make depend make make install If that does not work, then rm -rf /usr/obj/* and try again. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Vinum stripe size (was: tuning a VERY heavily (30.0) loaded server)
On Tue, Mar 27, 2001 at 05:16:53PM +0930, Greg Lehey wrote: No, there's no requirement for it to be a prime number. The only problem is that with 32 MB cylinder groups and a power of two stripe size and subdisk count, you end up with all the superblocks on one subdisk, The change I made to newfs to make "-c 22" the default, removes this power-of-two issue. Correct? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: gcc 2.95.3 and STL
On Wed, Mar 28, 2001 at 10:26:56AM +0200, Arjan Knepper wrote: What is preffered the build-in STL (/usr/include/g++) or STLport? The one bundled with (and matches) G++ of course. Unless you find your code just will not work with it. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: # of bpf devices
On Wed, Mar 28, 2001 at 02:49:53PM -0500, Dennis wrote: It seems that only 256 bpf devices are supported. How painful would it be to increase that number...I assume its an 8bit varable somewhere? Are there other caveats? It's pretty trivial. Send a patch when you are done. I was hoping to get some useful insight before I looked into it..or if there was a sound reason for not expanding them. Im hopeful someone brighter will answer. You did. "pretty trival". I.E. will not take much work, and no good reason not to expand them. Since you've said so many times you can hack your own system, sounds like PHK told you what you needed to know. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: # of bpf devices
On Wed, Mar 28, 2001 at 01:56:21PM -0800, Mike Smith wrote: Anyway, I just had a quick look, and I think that your basic problem is that MAKEDEV uses the wrong encoding for devices above 255. This is fixed in -CURRENT, and if you bring back the unit2minor changes from there to -STABLE you should be in business. They were MFC'ed right before 4.3-BETA. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: if_fxp - the real point
On Thu, Mar 29, 2001 at 09:40:05PM -0500, Dennis wrote: 3com never has, Uh, how do you think Bill Paul wrote the xl driver? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Intel driver doc's Take 2.
On Fri, Mar 30, 2001 at 08:49:55PM +0100, Koster, K.J. wrote: Its not a "proprietary tree". I dont have time to clean it up and submit patches. But you do seem to have time to keep arguing with people??? I'm sure you'll have time to bitch again if 4.4 doesn't meet your needs because you didn't submit some patch you needed. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Security problems with access(2)?
On Sun, Apr 01, 2001 at 10:55:23AM +1000, Greg Black wrote: Many years ago I implemented a new interface that I called eaccess() which replicated the work of access, but tested against the effective uid and gid. I'd like to see that introduced more widely. That still isn't suffient (and even more scary) unless the parameter is a file handle or FILE pointer. We need an faccess() call, plain and simple. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Security problems with access(2)?
On Sun, Apr 01, 2001 at 11:02:11PM -0400, Robert Watson wrote: eaccess_file(2) - Using effective credentials, check to see if the requested access is permitted on the file or directory identified by the provided pathname. Why not stick to existing naming practices? eaccess() eaccess_fd(2) - Using effective credentials, check to see if the requested access is permitted on the file or directory associated with the provided open file descriptor. Nope, faccess(2) (see fstat(2), flock(2), fchdir(2),...) and feaccess(2) faccess(3) - Using effective credentials, check to see if the requested access is permitted on the file or directory associated with the provided open file stream. What's wrong with faccess(fileno(...)) and feaccess(fileno(...))? -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: Idea about modules build
On Mon, Apr 16, 2001 at 09:51:20AM +0400, Vladimir B. Grebenschikov wrote: I have idea about modules build/install process: Warner (imp) was to commit this fuctionality to 5-current (and back port to releng_4 after 4.3-RELEASE). -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: x86-64 Hammer and IA64 Itainium
On Tue, Apr 17, 2001 at 03:57:37PM -0400, [EMAIL PROTECTED] wrote: I would like to see this too, however I think you have to sign NDA's and the like to be a part of the AMD effort to develop for it. Understandable I guess. Yes. I now have a copy of the Virtutech Simics x86-64 simulator. That is all I'm prepared to say at this point. Also they only seem interested in boosting Linux adoption of the new AMD 64 bit procs. *shrug* NOT IN THE LEAST!!! Please do not spread this FUD before asking. There will be a FreeBDS logo at www.x86-64.org as soon as the FreeBSD Project can get a webpage up describing our plans and effort for it to link to. I could really use some help in this area. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: x86-64 Hammer and IA64 Itainium
On Tue, Apr 17, 2001 at 02:06:56PM -0700, Jeremiah Gowdy wrote: I'm talking about FreeBSD using the gcc x86-64 compiler to port FreeBSD to x86-64. What other compiler would we use?? I have access to the SuSE x96-64 compiler effort. I'm talking about a FreeBSD project to port to x86-64. I'm not talking. I'm doing. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: x86-64 Hammer and IA64 Itainium
On Wed, Apr 18, 2001 at 12:51:17PM -0700, Doug White wrote: (Yes I know the emulator is ass-slow and a gigantic beast, but it does work, right?) The public simulator took 12 hours to get to the twirler of our boot loader. I guess it would have booted the i386 kernel I was feeding it in just under 2 weeks. This was on a 950MHz Athlon. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: x86-64 Hammer and IA64 Itainium
On Fri, Apr 20, 2001 at 08:32:32AM -0700, Jeremiah Gowdy wrote: You're taking me out of context my friend. I was responding to this: ... I was saying that gcc can be used by anyone without signing any NDAs. Ah. Sorry for the misudertanding. You are of course correct. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: UFS block size vs. write speed
On Fri, Apr 20, 2001 at 07:52:03AM -0700, Alfred Perlstein wrote: Soft updates isn't an "async" or "sync" thing. It combines synchronous and asynchronous transfers. If I'm not mistaken, all metadata is synchronously written, and all data is asynchronously written. You're mistaken, what you're describing is the old non-async/non-softupdates way. ^ actually its called "nosync". To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: gcc -O bug
On Thu, Apr 26, 2001 at 09:44:36AM -0400, Jason Andresen wrote: Er, isn't this the kind of problem the GCC folks are more likly to be able to fix? In general yes. But it doesn't hurt to double check here to make sure you your ducks in row before going to the GCC lists. I see later in this thread DES found it was a coding problem, not GCC optimizer problem. At least in GCC 2.9.5 (not the latest mind you) this problem still ^ 2.95[.3] -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: pax(1) gzip functionality
On Thu, Apr 26, 2001 at 02:54:25AM -0700, Kris Kennaway wrote: Please review the following code from OpenBSD; it adds -z and -Z options to pax(1) to gzip(1) the archives created. Sigh. They could have generalized this just a little and supported Bzip2 at the same time. Please let me know after you commit this so I can do this. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: pax(1) gzip functionality
On Thu, Apr 26, 2001 at 04:42:44PM +0100, Brian Somers wrote: On Thu, Apr 26, 2001 at 02:54:25AM -0700, Kris Kennaway wrote: Please review the following code from OpenBSD; it adds -z and -Z options to pax(1) to gzip(1) the archives created. Sigh. They could have generalized this just a little and supported Bzip2 at the same time. Please let me know after you commit this so I can do this. Is this necessary ? What's the problem with using a pipe ? Isn't this the same argument as the xargs one we've just gotten through ? What's wrong with: tar cf - foo | gzip foo.tar.gz gzip -dc foo.tar.gz | tar xf - Someone deemed them too inconvient for the number of times they are invoked. I'm not going to enter that discussion, but _if_ gzip support is added, I feel bzip2 support should be added to be orthogonal with today's uses. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: BSDI and Marketing 101
On Thu, Apr 26, 2001 at 08:00:35PM -0400, Dennis wrote: At 08:12 PM 04/26/2001, David O'Brien wrote: On Thu, Apr 26, 2001 at 07:03:47PM -0400, Dennis wrote: I saw BSDIs retail product of FreeBSD in a local bookstore the other day, and it became sadly clear why LINUX, although highly inferior, is so much more widely used. Right next to Freebsd (priced at $129.95) was Mandrake LINUX for $29.95. I should use your quote from this morning... but I won't. You don't understand channel marketing. And I'll just leave it at that. Actually I do. Channel marketing requires a marketing base, which they dont have. You have to establish a base before you can gouge. What you fail to realize is computer stores and bookstores *want* and have requested the $129.95 product. They want even more expensive ones than that. The really don't care for $29.95 products as the margins are too low for their liking -- unless they feel the product is a leader one. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: x86-64 Hammer and IA64 Itainium
On Thu, Apr 26, 2001 at 05:59:06PM -0500, Michael C . Wu wrote: IIRC, KA-64 does not even have an emulator yet. Are you making a distinction between emulator and simulator? Such that SimNow! and VirtuHammer don't fall into what you are speaking of? -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: x86-64 Hammer and IA64 Itainium
On Thu, Apr 26, 2001 at 08:08:48PM -0700, Jeremiah Gowdy wrote: What's KA-64 ? AMD internal name for the x86-64. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: BSDI and Marketing 101
On Fri, Apr 27, 2001 at 05:50:01PM -0400, Dennis wrote: I guess you missed the POINT, which was that mandrake was selling the same I guess you missed the POINT. I see you are conveniently totally ignoring the fact that the channel wants $129 items. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Trouble with 4.3-RELEASE compiler
On Fri, Apr 27, 2001 at 07:40:22PM -0300, Joao Carlos Mendes Luis wrote: I was installing a squid server with 4.3-RELEASE, and found that FreeBSD has now a bug in the compiler that affects squid. The default compilation of squid is with CFLAGS=-g -O2 -Wall, and this setup triggers the bug. ... Should this be a reason to roll back the compiler to version 2.95.2, as it was before Tue Apr 10 19:23:19 2001 UTC, when it changed to 2.95.3? What to do with the upcoming CDs? No. It means the squid maintainer didn't do a proper job and make it so that the system CFLAGS were used. Granted most don't know to export CFLAGS to GNU configure when they run the configure script. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: fd driver hacking to recover data
On Thu, May 10, 2001 at 07:07:53AM +0200, Luigi Rizzo wrote: i think you can try dd from the raw device (/dev/rfd) using the iseek Uh, the raw device is /dev/fd. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: subscribe
On Fri, May 11, 2001 at 05:01:13PM -0700, Jordan Hubbard wrote: Argh! I'm sorry folks, I almost always remember to delete the cc line when I send somebody that particular form letter so as not to spam the list myself, but this time I forgot to do that before typing the send command. Bad Jordan, no cookie! Why is it we can't have majordomo filter these out and send the people your form reponce. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
wint_t
What is the proper definition of wint_t? curses.h has it as a long int, however NetBSD (and GCC's libstdc++) has it as an int. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: gcc (cpp) include search path problem
On Thu, May 24, 2001 at 05:55:38AM -0400, Brent Verner wrote: IMO, the search path for cpp should include /usr/local/include, especially since we install ports there. That would be wrong. We install ports where ever you tell the system to. That could be /usr/reall-cool-FreeBSD-treats/ or anything. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: general speed differences between 4.1.1-RELEASE and 4.3-RELEASE
On Fri, May 25, 2001 at 11:21:06PM -0700, Ed Hudson wrote: enclosed is a .jpeg of an xgraph of the following interactive test: Are you setup such that you could do the same test on a stock Red Hat 6.2, 7.0, and 7.1 box? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Preliminary Tuning man page (was Re: Benchmarking FreeBSD (w
On Fri, May 25, 2001 at 03:33:19PM -0700, John Baldwin wrote: Nice! One thing to note in the filesystem tuning is that newfs can turn on softupdates at newfs time now with -U, at least in -current. Stable too. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: What changed in ld?
On Fri, Jun 01, 2001 at 02:42:34AM -0500, G. Adam Stanislav wrote: I have recently upgraded from FreeBSD 3.1 to 4.3-20010525-STABLE. And thus upgraded your assembler and linker from GNU Binutils 2.9.1 to 2.10.1. When you upgrade to 4.4-FreeBSD you will get GNU Binutils 2.11. That tells me something has changed in the way ld handles the .bss section between 3.1 and 4.3 - either on purpose or as a bug. This would be a question for the GNU Binutils mailing list to find out why they changed anything. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Fixing documented bug in env(1)
On Thu, May 31, 2001 at 09:29:38PM -0700, Dima Dorfman wrote: Although this is a documented shortcoming, it's quite unnecessary given how easy it is to fix it. Any objections to allowing '--' to mean end of env. variable assignments? The orthoginal way (with grep, mv, et. al.) would be to use '==', not '--' as that is the problematic character. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Fixing documented bug in env(1)
On Mon, Jun 04, 2001 at 12:49:43AM +1000, Greg Black wrote: | For whatever it's worth, it seems more reasonable to me | to use '--' instead of '=='. Since '--' has NO equals | sign in it, it clearly can't be the setting of an | environment variable. If we're voting on this, I'm very strongly in favour of `--'. Why? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Fixing documented bug in env(1)
Mark you've given the justification and logic behind `==' much, much better than I did. Thanks! :-) -- -- David ([EMAIL PROTECTED]) P.S. typically I don't quote a whole message like this, but I think it is important that at least read this one and honestly consider it. On Sat, Jun 02, 2001 at 05:18:45PM +0100, Mark Valentine wrote: people use -- to end subsequences of arguments all the time. No, they use ``--'' to indicate to getopt(3) the end of the _options_ and the _start_ of the arguments. Since env(1) uses getopt(3), ``--'' already has meaning to env(1); it allows environment variables and commands which start with ``-'' (the former is obviously invalid). $ env -i -- -t args currently allows execution of command ``-t''. However, what Dima proposes doesn't seem to be harmful, just slightly confusing, and less surprising than inventing a new delimieter such as ``==''. $ env -i -- foo=bar -- 4=4 args has two distinct uses of `--'' as per Dima's proposal, the first tells getopt(3) to stop processing options, and the second tells the argument processing code to stop looking for variable assignments (i.e. ``4=4'' is a command). To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: MFC'ing new md(4) functionality?
On Mon, Jun 04, 2001 at 07:46:18PM -0700, Dima Dorfman wrote: Is there any reason not to MFC the new md(4) functionality Zero reason not to. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: MFC'ing new md(4) functionality?
On Tue, Jun 05, 2001 at 07:10:56AM -0500, Jacques A. Vidrine wrote: On Mon, Jun 04, 2001 at 07:46:18PM -0700, Dima Dorfman wrote: mdconfig(8) and mdioctl.h aren't in -stable so those can be brought over verbatim, Dumb question: Can we just add a RELENG_4 tag to the files in such a case? You could get by doing things that hackish way. But it can be prone to error. The proper way is to ``cvs add'' them in a directory checked out on the branch. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: MFC'ing new md(4) functionality?
On Tue, Jun 05, 2001 at 06:33:17PM +0200, Poul-Henning Kamp wrote: Others see it differently, it would seriously break a lot of people who are using -stable in embedded applications. Can you expand on this? I assume you know we are not talking about disabling vn(4). To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: need help: gdb -k 4.16/7
On Wed, Jun 06, 2001 at 10:32:39AM -0700, Dorr H. Clark wrote: Interestingly, the 4.16 distribution archived at ftp://www.gnu.org does not exactly match the version in the FreeBSD 2.2.x release, and doesn't build cleanly either. Not sure why you find this so surprising. Install the 2.2.x sources and you will have the gdb sources that built the original gdb. If you want to update that to 4.17 or higher, use CVS to find the changes from the vendor branch and you will then have our modifications. Alternately, you could get the RCS files for 2.2.x's GDB and do a vendor import of 4.17 and fix the merge conflicts. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Re: import NetBSD rc system [summary]
On Thu, Jun 14, 2001 at 10:48:49AM -0700, Jordan Hubbard wrote: I think that since we use CVS around here, we should simply import the Some time tonight I will be vendor importing the NetBSD rc system. (no it will not be functional at that time). I am doing this to help the various efforts that are working on this so they can pass round patches vs. entire files. Doing the vendor import will also help remind us the goal here is to adopt the NetBSD RC system -- not go off and have a second syndrome party, or other results of NIH. Once the vendor import is done, we can coordinate with the NetBSD folks the minor changes that FreeBSD will require to use their system. There may be places where the NetBSD RC system could doing things better, but the ongoing relationship we can create with NetBSD is something far more valuable than a few efficiency/functionality tweaks. If we do find short comings we should resolve them by working with the NetBSD guys. With any hope, maybe BSD/OS could pick up this RC system also. ** ** I ask that no one commit to NetBSD RC files until diffs have been ** posted on [EMAIL PROTECTED] for review and we have agreement ** ** that the change is necessary. ** -- -- David([EMAIL PROTECTED]) Disclaimer: Not speaking for Wind River systems. I am making no claims or promises about BSD/OS. I am speaking purely with a FreeBSD hat on, stating a wouldn't it be nice prase. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Re: import NetBSD rc system [summary]
On Thu, Jun 14, 2001 at 10:08:48PM +0300, Peter Pentchev wrote: Some time tonight I will be vendor importing the NetBSD rc system. (no it will not be functional at that time). Erm.. Sheldon Hearn has expressed a desire to discuss things with Luke Mewburn in the hope of coming to some mutual agreement as to directions and improvements. My actions in no way changes Sheldon's efforts. In fact it helps them. We will have a way to see proposed changes in the form of a diff. This makes it easy to see where we are deviating from the NetBSD RC system. It also gives Sheldon the diff to send to Luke for discussion. If Luke agrees and makes a change in the NetBSD RC sources, we will get the fruits of Sheldon's effort on the next vendor import. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Query: How to tell if Microsoft is using BSD TCP/IP code?
Doesn't any one remember Netiquette these days and trim what they are replying to?? [ thread left below to see how bad this is getting.. ] On Fri, Jun 15, 2001 at 02:42:35PM -0700, Jordan Hubbard wrote: This is a good reference, but sadly it only really refers to the sockets paradigm as first popularized by BSD, which means they could have followed the API without touching a single line of BSD code. To reiterate: What I'm looking for is some true, hard evidence that Microsoft has used BSD code in any of their operating systems. A number of people have sent me anecdotal evidence and I heard from a friend type stories, but sadly I cannot use any of that. What I need is tangible proof - the people working on this story have already heard all the stories and now what they're looking for is the kind of confirmation that can be cited and independently verified. I can't name names, but suffice it to say that it will be a small (and very visible) coup for us if we can help them prove this. Thanks. - Jordan From: Joseph A. Mallett [EMAIL PROTECTED] Subject: Re: Query: How to tell if Microsoft is using BSD TCP/IP code? Date: Fri, 15 Jun 2001 17:06:23 -0400 (EDT) http://msdn.microsoft.com/library/psdk/winsock/apistart_9g1e.htm mentions BSD, not sure if is direct enough. I'm downloading the SDK right now so I can grepmonkey through the latest and greatest headers, etc. HTH -- [ Joseph Mallett[EMAIL PROTECTED] ] [ http://srcsys.org ] [ xMach Core Team xMach: Proactively Unbloated Microkernel BSD ] [ FreeBSD, NetBSD, xMach User; (Obj)C(++) Coder ] [ http://xMach.org ] On Fri, 15 Jun 2001, Joseph A. Mallett wrote: Do you happen to have any of their Winsock propoganda handy (specifically developer materials or winsock.h header file)? I know for a fact that they have said repetedly that some of it was taken directly from Berkely. I'm just not sure where... I'm going to start digging through my stuff to see if I can find anything. -- [ Joseph Mallett[EMAIL PROTECTED] ] [ http://srcsys.org ] [ xMach Core Team xMach: Proactively Unbloated Microkernel BSD ] [ FreeBSD, NetBSD, xMach User; (Obj)C(++) Coder ] [ http://xMach.org ] On Fri, 15 Jun 2001, Jordan Hubbard wrote: I've had several marketing types approach me recently for details as to whether or not Microsoft was using the BSD TCP/IP stack and/or user utilities, and though it's always been common knowledge in the community that they were, when I set about to prove it I found it to be less easy than I'd thought. I've strings'd various binaries and DLLs in my copy of Windows 98 but have yet to find anything resembling proof. Does anyone out there have any details or discovery techniques for confirming or disproving this assertion either way? It would be very useful (for us) from a PR standpoint to know. Thanks! - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: import NetBSD rc system
On Sat, Jun 16, 2001 at 07:58:06AM -0700, Gordon Tetlow wrote: I'll submit the patches I have for this that make it work in both FreeBSD and NetBSD. BTW, why do we use libutil.h and they use util.h? Just the way things are. I like Matt's idea (I think it was Matt) to have a new_rc switch. I'll look at adding the code for it and submitting a patch, You are going off on a tangent. You are worried about the flag day before we even have a flag to run up the poll. /etc/rc.subr ported What changes were needed here? I basically added a function called checkwildno() that is similar to checkyesno that returns 1 for NO (plus variants) or '' and returns 0 for anything else. This gets rid of alot of case statements in the modules, making them simple if's. Again, why don't we just concentrate on porting the NetBSD scripts and not the second system enhancements? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: import NetBSD rc system
On Sat, Jun 16, 2001 at 08:04:42AM -0700, Gordon Tetlow wrote: I also had an idea to break out the network init into several different pieces falling under 2 headings LINK (ether, atm) and NETWORK (ipx, ipv4, ipv6, atalk). I've started work on breaking everything out and was wondering if I should continue with it or if it just too much of a change. Yes it is too much of a change. Let me restate again that the idea right now is to just *minimally* port the NetBSD RC scripts. Once we have a system booting with RCng, we can see where it blows and discuss changes. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Changes to the /etc/rc* boot system
On Mon, Jun 18, 2001 at 11:32:24PM -0700, Doug Barton wrote: I think that we're closer to agreement here than it may appear. Last I heard from obrien he was overloaded, and wasn't looking to head this up himself unless no one else was going to do it. At this point I view myself as more of a facilitator than the one coming up with the patches. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: whois(1) patch for review
On Fri, Jun 22, 2001 at 03:37:17AM +0200, Dag-Erling Smorgrav wrote: Mike Barcroft [EMAIL PROTECTED] writes: Arg.. I wish you had contacted me before doing this work. From looking at your patch, your using an old copy of my work. The newest one is available at: http://testbed.q9media.net/freebsd/whois.patch and will be committed very-shortly-now(tm). Since Mike's patch is a style cleanup with no functional impact except plugging a memory leak, I feel it's better to commit it first, and merge in Alexey's patch later, after it's been reviewed by this forum. Uh wrong. There were other non-style bits than just the memory leak. For instance the cast changes are functionalty related, not style. It should have been done in two commits. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: whois(1) patch for review
On Thu, Jun 21, 2001 at 04:08:21PM +0300, Alexey Zelkin wrote: For example you can have following string in your whoisservers configuration file (system wide -- /usr/share/misc/whoiservers or personal ~/.whoisservers): System wide configuration files should be in /etc, not /usr/share/misc. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
