Re: Login.conf (Whose problem is this) ?

1999-07-05 Thread Sheldon Hearn
On Sat, 03 Jul 1999 18:57:06 MST, John Polstra wrote: This stuff is old and obsolete. LOGIN_CAP_AUTH isn't supported any more. (It never was fully supported, actually.) Don't use it. There's an open PR for this, PR 10115. I assume all that's required is that we smack the outdated

Re: Replacement for grep(1) (part 2)

1999-07-05 Thread Sheldon Hearn
On Mon, 05 Jul 1999 21:14:36 -0400, Jamie Howard wrote: It would be really swank if someone were to go over what I have and make sure it is correct. I know I was blowing $ before, and I think that is correct now. Hi Jamie, One way to make it easier for people to test drive your software

Re: docs/12377: doc patch for login_cap.

1999-07-08 Thread Sheldon Hearn
On Thu, 08 Jul 1999 00:03:10 +0100, Nik Clayton wrote: I have done. As far as I can tell, the submitter is saying "Yes, the information I was looking for was in the manual page, but it (specifically, that the "root" account doesn't use the "default" entry) is buried as a throw away

Re: docs/12377: doc patch for login_cap.

1999-07-09 Thread Sheldon Hearn
On Thu, 08 Jul 1999 20:59:58 +0100, Nik Clayton wrote: With that in mind, how about this patch (in conjunction with the patch to login.conf in the original PR, which just updates a comment)? This looks much better. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with

Re: more amd hangs

1999-07-10 Thread Sheldon Hearn
On Fri, 09 Jul 1999 12:00:52 MST, Doug wrote: The amd conf files are below, any insights or suggestions welcome. I can't remember whether it was you or someone else to whom I offered this advice not so recently, so forgive me if I've suggested this to you before. I've found that AMD

Re: a BSD identd

1999-07-10 Thread Sheldon Hearn
On Sat, 10 Jul 1999 13:06:33 -0400, "Brian F. Feldman" wrote: I don't see a point to that. I'm not sure whether you don't see the point in the existing behaviour, or whether you don't see the point in doing as I ask and supporting consistent behaviour in FreeBSD. The existing ident

Re: a BSD identd

1999-07-10 Thread Sheldon Hearn
On Sat, 10 Jul 1999 15:57:21 EST, Chris Costello wrote: The whole point of ident was -- and still is -- to authenticate or verify who created a specific TCP connection. Crhis, as Warner's already pointed out, you're wrong. :-) Ident's intended purpose is for me to give you something to

Re: a BSD identd

1999-07-11 Thread Sheldon Hearn
On Sun, 11 Jul 1999 01:49:59 -0400, "Brian F. Feldman" wrote: inetd already has the built-in equivalent to that. Maybe it's possible to make a REAL ident (*cough* the one I wrote) an option, inetd has that service off by default. That sounds much more like it. I will say that I suspect

Re: a BSD identd

1999-07-11 Thread Sheldon Hearn
On Sun, 11 Jul 1999 00:49:59 EST, Kevin Day wrote: However, pidentd is rather buggy of late, and tends to freak out a lot. If we could have an 'official' identd, I'd like it. :) I hope you can back that up with more than a desire to see "an official identd", whatever that means. Can you

Re: a BSD identd

1999-07-11 Thread Sheldon Hearn
On Sun, 11 Jul 1999 14:03:29 -0400, "Brian F. Feldman" wrote: And this service is very small, so it doesn't make inetd "huge". It's not feeping creaturism because I replaced the ident service there with a working one. Perhaps this is where we're missing each other. The ident service

Re: a BSD identd

1999-07-11 Thread Sheldon Hearn
On Sun, 11 Jul 1999 12:54:03 EST, Kevin Day wrote: Please see: ports/12596 (just added) ports/8042 Thanks! I've seen 8042 before, but yours looks a lot more useful, as I can't make sense of the older one. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with

Re: a BSD identd

1999-07-12 Thread Sheldon Hearn
On Sun, 11 Jul 1999 22:34:09 +0200, Mark Murray wrote: As long as the documentation is _clear_ that this is not a front-line security tool, but rather a thing to marginally augment logs with user-supplied info, then I'll buy it. This is why I put forward a motion to move pidentd out of

Re: a BSD identd

1999-07-12 Thread Sheldon Hearn
On Sun, 11 Jul 1999 12:47:30 MST, Doug wrote: Finally, Brian might want to search the bugtraq archives before he commits anything. There have been quite a few identd related discussions, and it would be points in our favor if we didn't come out with anything that had known exploits.

Re: bin/12578: `` subshell taints PWD

1999-07-12 Thread Sheldon Hearn
Hi folks, I'm hoping someone here is interested in tracking down a bug in our /bin/sh . Changing directory within a backtick (``) subshell in sh taints the parent's working directory. The following sample code gives the expected result for /bin/csh, but breaks for /bin/sh cd /tmp echo .`cd /`.

Re: keymapping continued ...

1999-07-12 Thread Sheldon Hearn
On Mon, 12 Jul 1999 15:04:43 -0300, The Hermit Hacker wrote: Hopefully this makes a bit more sense? What doesn't make sense is the fact that a FreeBSD developer, who should know better, is mailing this sort of thing to freebsd-hackers. Sheldon. To Unsubscribe: send mail to [EMAIL

Re: more amd hangs

1999-07-12 Thread Sheldon Hearn
On 10 Jul 1999 12:56:41 -0400, R. Matthew Emerson wrote: I thought that it was almost never proper to soft-mount rw filesytems. Am I mistaken about this? I must admit, it sounds like sensible advice. The only NFS exports which I have to rely on are read-only mounts. The only time I

Re: Replacement for grep(1) (part 2)

1999-07-12 Thread Sheldon Hearn
On Mon, 12 Jul 1999 23:56:29 +0100, Jon Ribbens wrote: What about it? If an application does not need 100MB, it should not malloc it. If it does need it, it should malloc it and know that it is available if the malloc succeeds. You're rehashing stuff that's been discussed to death. Please

Re: bin/12578: `` subshell taints PWD

1999-07-13 Thread Sheldon Hearn
On Tue, 13 Jul 1999 18:13:42 +0200, Oliver Fromme wrote: Command substitution certainly has to spawn a subshell, even for built-in commands, because otherwise you could modify parent shell variables within command substitutions. But isn't that exactly what's happening here, where PWD is

Re: a BSD identd

1999-07-13 Thread Sheldon Hearn
On Mon, 12 Jul 1999 15:12:49 -0400, "Brian F. Feldman" wrote: It's "out with the bad, in with the good." Pidentd code is pretty terrible. Hi Brian, I let your comment above go at the time that you said it and I waited for Kevin Day to substantiate similar claims. Kevin very kindly took the

Re: OpenBSD's strlcpy(3) and strlcat(3)

1999-07-15 Thread Sheldon Hearn
[Hijacked from freebsd-security] On Thu, 15 Jul 1999 17:33:29 -0400, Garance A Drosihn wrote: What I wanted to do was have "estr" routines, where the destination is specified as the starting point and the ending point of the area available for the string (as two parameters). The routines

Re: OpenBSD's strlcpy(3) and strlcat(3)

1999-07-15 Thread Sheldon Hearn
On Thu, 15 Jul 1999 18:34:42 -0400, Tim Vanderhoek wrote: if (fooncat(string, append, sizeof(string)) != strlen(append)) ... which is rather evil, given that the second strlen(append) would be completely gratuitous if it weren't for the interface you're suggesting. Tim, you're doing

Re: Swap overcommit (was Re: Replacement for grep(1) (part 2))

1999-07-15 Thread Sheldon Hearn
On Thu, 15 Jul 1999 17:53:52 CST, [EMAIL PROTECTED] wrote: All I want for Christmas is a knob to disable overcommit. And what I'm pretty sure the majority of the readers on this list want is for those of you who really think it's necessary to do it yourselves. What? Nobody who wants to

Re: OpenBSD's strlcpy(3) and strlcat(3)

1999-07-20 Thread Sheldon Hearn
On Thu, 15 Jul 1999 18:40:17 CST, Warner Losh wrote: I can see your point. I don't know if I'll like your man pages better or not, but I'd be willing to give them a spin. Bring on the humble pie. It really isn't practical to try to have these pages match the approach of the existing pages.

Re: problems with the integrated tcp-wrappers.

1999-07-21 Thread Sheldon Hearn
[ Hijacked from freebsd-hackers ] On Tue, 20 Jul 1999 17:33:24 CST, Greg Skafte wrote: I've just recently switched from using the tcpwrappers port to the native tcpwrappers implemention the following config entries worked on the port but are not working with the native I've tested the

MLINKS for select(2) FD_* macros

1999-07-21 Thread Sheldon Hearn
Hi folks, Would it be inappropriate to add select.2 MLINKS for FD_SET, FD_CLR, FD_ISSET and FD_ZERO? Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message

Re: cvs commit: src/usr.sbin/inetd inetd.c

1999-07-21 Thread Sheldon Hearn
[Hi-jacked from cvs-committers and cvs-all] On Wed, 21 Jul 1999 18:15:09 +0200, Poul-Henning Kamp wrote: There is another one you may want to look at, I have not figured it out yet: I try to start a ntpd from /etc/rc.local this way: nohup /usr/local/bin/ntpd -d -d

Re: xmms port broken

1999-07-21 Thread Sheldon Hearn
[Hijacked from freebsd-hackers and freebsd-questions] Hi Chris, You've cross-posted this message to two inappropriate lists. The freebsd-ports mailing list is what you really wanted. A copy of this message (with your original question intact) has been sent to that list on your behalf. Ciao,

Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.h

1999-07-23 Thread Sheldon Hearn
[Hijacked from cvs-committers and cvs-all] On Fri, 23 Jul 1999 11:28:12 +0200, Andre Albsmeier wrote: I observed some kind of denial of service on -STABLE: I was playing with the new nmap and did a 'nmap -sU printfix'. inetd was running as "inetd -l" and started sucking all the CPU time

Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.

1999-07-23 Thread Sheldon Hearn
On Fri, 23 Jul 1999 13:50:45 +0100, David Malone wrote: You could turn on wrapping and log them at a level at which syslog will ignore them. I'm not sure how much this would help with inetd chewing CPU time, but... If, indeed, inetd is really "chewing CPU time". Ciao, Sheldon. To

Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.h

1999-07-23 Thread Sheldon Hearn
On Fri, 23 Jul 1999 15:06:02 +0200, Andre Albsmeier wrote: But when inetd is run without -l it get 100%. Are you avoiding my question on purpose? :-) On Fri, 23-Jul-1999 at 14:29:19 +0200, Sheldon Hearn wrote: What does "sucking all the CPU time" mean? Does it mean that other

Re: cvs commit: src/usr.sbin/inetd builtins.c inetd.

1999-07-23 Thread Sheldon Hearn
On Fri, 23 Jul 1999 14:16:19 +0100, David Malone wrote: But when inetd is run without -l it get 100%. Interesting - does it still answer requests during this time? Yeah. What we really need to know is how many packets inetd actually received. The manpage excerpt that DES showed us

Mentioning RFC numbers in /etc/services

1999-07-24 Thread Sheldon Hearn
Hi folks, I plan to mention in the comments for each service in /etc/services, the latest RFC describing the service. I also plan to mention in the manpage for services(5) the e-mail address to which requests for "How do I get the RFCs" should be sent. If anyone is worried that I'll get RFC

Re: Mentioning RFC numbers in /etc/services

1999-07-24 Thread Sheldon Hearn
On Sat, 24 Jul 1999 08:25:55 EST, Chris Costello wrote: Are you going to be listing all the RFCs that apply? For example, DNS is 1033, 1034, and 1035, and NNTP is 0850 and 0977. I doubt I'll be listing obsoleted RFCs. :-) I'll do the best I can. Send me private mail if you'd like to

Re: [Fwd: wd0 DMA errors]

1999-07-25 Thread Sheldon Hearn
On Sun, 25 Jul 1999 10:59:26 MST, Doug wrote: No answer on -current, any help appreciated. We're probably all sitting here thinking "I'm sure this was asked and answered recently. He can read his CURRENT mail like the rest of us." For the terminally lazy, this was a bug in the pci

file(1) Magdir candidate: wintendo

1999-07-26 Thread Sheldon Hearn
Hi folks, 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. Just because a bloated file(1) magic database

Re: Mentioning RFC numbers in /etc/services

1999-07-26 Thread Sheldon Hearn
On 26 Jul 1999 12:59:57 +0200, Dag-Erling Smorgrav wrote: Don't. Instead, put it in a separate rfc(7) man page which you refer to in the services(5) man page. Cool! :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the

Re: file(1) Magdir candidate: wintendo

1999-07-26 Thread Sheldon Hearn
On Mon, 26 Jul 1999 23:30:08 +0200, Mark Murray wrote: You could start with "WinEXE". Save game file formats, not game executables. You think WinEXE tops my pcgames suggestion? Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of

Re: XFree 3.3.4 not on ftp.freebsd.org?

1999-07-26 Thread Sheldon Hearn
On Mon, 26 Jul 1999 21:09:50 -0400, Tim Vanderhoek wrote: I seem to remember that you can get away with a simple "mkdir /var/db/pkg/xxx" to fake it. Can you think of any ports that test for the existance of XFree86 using the package system? They use USE_X_PREFIX or USE_X_LIB, both of which

securelevel too course-grained?

1999-07-26 Thread Sheldon Hearn
On Mon, 26 Jul 1999 20:48:28 MST, Matthew Dillon wrote: Subject: Re: securelevel and ipfw zero However, it does not allow you to do it if you are sitting at secure level 3. You don't think that this discussion highlights the growing inadequacy of the securelevel mechanism's lack

Re: XFree 3.3.4 not on ftp.freebsd.org?

1999-07-26 Thread Sheldon Hearn
On Mon, 26 Jul 1999 22:41:24 MST, Doug wrote: However right after 3.2-R came out there was a flurry of -questions mail about broken pkg dependencies because sysinstall wasn't properly registering the X install. Is this a different problem from the broken compat22 installation? If the

Re: replacing grep(1)

1999-07-27 Thread Sheldon Hearn
On 27 Jul 1999 13:37:35 +0200, Dag-Erling Smorgrav wrote: URL:http://www.freebsd.org/~des/software/grep-0.7.tar.gz I move that we replace GNU grep in our source tree with this implementation, once it's been reviewed by all concerned parties. When I committed the port

Re: replacing grep(1)

1999-07-27 Thread Sheldon Hearn
On Tue, 27 Jul 1999 08:19:38 -0400, "Brian F. Feldman" wrote: Getting rid of as much as possible, gradually, is a Very Good Thing; this is how we get stability and performance improvements. Only if the replacements are as stable and robust as their predecessors. In this case, the

Re: newsyslog owner.group - owner:group

1999-07-27 Thread Sheldon Hearn
On Tue, 27 Jul 1999 13:43:33 +0200, Sheldon Hearn wrote: Sorry for bringing this up without doing all my homework. Diffs in the pipeline. :-) Ha! Diffs that produce a win in the midst of an apparent lose-lose. We now continue to support the dot as a separator without breaking user

Re: newsyslog owner.group - owner:group

1999-07-27 Thread Sheldon Hearn
Hi Brian, Okay, your mail quoted below came around the same time I sent my diffs. This entire response assumes that you don't like the diffs. On Tue, 27 Jul 1999 08:10:47 MST, "David O'Brien" wrote: It was a one character fix in -CURRENT and I don't see any reason to ugly the code with

Re: replacing grep(1)

1999-07-27 Thread Sheldon Hearn
On Tue, 27 Jul 1999 23:18:14 +0900, "Daniel C. Sobral" wrote: I'm talking about cpdup, which can be found in http://www.backplane.com/FreeBSD/. Someone posted a port at the time, but I don't know if anyone ever committed the port. I'll commit a port in the next few days. Ciao, Sheldon.

Re: newsyslog owner.group - owner:group

1999-07-27 Thread Sheldon Hearn
On Tue, 27 Jul 1999 09:07:34 MST, "David O'Brien" wrote: To paraphase Bill Paul: G that's part of my last name. N! I was chatting to a buddy about this just after I sent you the diffs and actually mentioned to him that I thought I might have made this mistake again. Since the

Re: file(1) Magdir candidate: wintendo

1999-07-28 Thread Sheldon Hearn
On Tue, 27 Jul 1999 22:20:40 MST, "David O'Brien" wrote: 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). Hmmm. So file(1) is a contrib candidate? Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL

Re: file(1) Magdir candidate: wintendo

1999-07-28 Thread Sheldon Hearn
On Wed, 28 Jul 1999 12:03:25 +0100, Andy Doran wrote: You may want to verify this. I'm pretty sure that Christos Zoulas (another NetBSD guy) maintains file(1): [EMAIL PROTECTED] Confirmed. Other than the mistaken name, I think David obsoleted further discussion, since it really is the best

Re: bin/12852: Non-standard behavior of fread(3)

1999-07-28 Thread Sheldon Hearn
Hi folks, Could someone have a look at the patch proposed on PR 12852? I understand the motivation, since it seems reasonable to me that ferror() should return EBADF after an attempt to read from stdout. At the moment, ferror() returns 0 after an attempt to read from stdout. Thanks, Sheldon.

Re: bin/12852: Non-standard behavior of fread(3)

1999-07-29 Thread Sheldon Hearn
On Wed, 28 Jul 1999 20:13:18 +0200, Robert Nordier wrote: There's no question this needs changing. An ISO example actually reads along the lines of: The question, though, is whether it needs changing _now_, or whether this'll break a number of critical utilities that rely on the broken

Re: Mentioning RFC numbers in /etc/services

1999-07-29 Thread Sheldon Hearn
On Thu, 29 Jul 1999 09:04:20 +0100, Josef Karthauser wrote: A question that always baffled me (I'm fairly easy to baffle) is why we've got some numbers defined as both udp and tcp when the service type is only one or the other. Does anyone know? Probably because this question isn't

Re: file(1) Magdir candidate: wintendo

1999-07-29 Thread Sheldon Hearn
On Wed, 28 Jul 1999 09:55:24 MST, "David O'Brien" wrote: My major Duh!! If Christos sees this thread, my apologies. Hehe, now you know how it feels to be the guy who calls you Brian. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in

Re: interesting bug in /usr/bin/cmp

1999-07-29 Thread Sheldon Hearn
On Thu, 29 Jul 1999 00:52:27 -0400, "Brian F. Feldman" wrote: If noone has any objections, I will commit this and MFC it in a week or so. --- src/usr.bin/cmp/regular.c.origThu Jul 29 00:43:50 1999 +++ src/usr.bin/cmp/regular.c Thu Jul 29 00:44:54 1999 |---

No MAXUID ?

1999-07-29 Thread Sheldon Hearn
Hi folks, I've come up empty-handed hunting for a constant that defines the maximum UID supported by the system. I'm working on our passwd and pwd_mkdb stuff and want to get rid of the artificial limitation of 65535 (USHRT_MAX) imposed in (at least) pwd_mkdb. Have I missed a useful define, or

Re: No MAXUID ?

1999-07-30 Thread Sheldon Hearn
On 30 Jul 1999 15:38:30 +0200, Dag-Erling Smorgrav wrote: How many times do I have to go through this? Until I stuff a comment in the source that explains this. :-) There is no "artificial limitation in pwd_mkdb". pwd_mkdb warns against UIDs larger than 65535 because legacy software that

Re: No MAXUID ?

1999-07-31 Thread Sheldon Hearn
On Sat, 31 Jul 1999 13:39:16 -0400, Adrian Filipi-Martin wrote: I'd be in favor of adding a /etc/pwd_mkdb.conf or some similar file. Eeeuw! :-) I'm not in favour of this idea, but issuing a single warning for one or more UID's encountered isn't behaviour that would make retrofitting

Re: Mentioning RFC numbers in /etc/services

1999-07-31 Thread Sheldon Hearn
On Fri, 30 Jul 1999 15:05:14 MST, Doug wrote: I still haven't heard anyone answer the two key (IMO) questions. Your questions are easier answered in reverse order: and how do you justify the additional cost to parse the file for every single system call that uses it? The

Re: No elf(5) man page (docs/7914)

1999-07-31 Thread Sheldon Hearn
On Fri, 30 Jul 1999 23:46:26 +0200, Jeroen Ruigrok/Asmodai wrote: If no-one objects I'll submit a manpage per a.out(5) style tomorrow for review untill it's ready for inclusion. Anyone who objects to your submissions is a woes -- real bastards wait for you to do the work before shooting you

Re: replacing grep(1)

1999-07-31 Thread Sheldon Hearn
On Fri, 30 Jul 1999 22:07:26 -0400, Tim Vanderhoek wrote: b$ time ./grep -E '(vt100)|(printer)' longfile /dev/null b$ time grep '(vt100)|(printer)' longfile /dev/null You think that's fair? Surely you can't expect Jamie's extended regex support to outperform GNU's simple regex support?

Re: Mentioning RFC numbers in /etc/services

1999-07-31 Thread Sheldon Hearn
On Fri, 30 Jul 1999 15:10:18 MST, Doug wrote: On some of the machines I administer I have some custom entries for /etc/services that make more sense than the defaults, especially for the ports 1023. Would you need these entries if inetd let you specify port numbers instead of service

Re: Mentioning RFC numbers in /etc/services

1999-08-02 Thread Sheldon Hearn
On 02 Aug 1999 13:05:17 +0200, Dag-Erling Smorgrav wrote: The correct way to do this is to fix getservbyname() so it accepts port numbers. Would this not still require modifications to /etc/services for services not already mentioned in that file? Ciao, Sheldon. To Unsubscribe: send mail

Re: Mentioning RFC numbers in /etc/services

1999-08-02 Thread Sheldon Hearn
On 02 Aug 1999 13:19:01 +0200, Dag-Erling Smorgrav wrote: Would this not still require modifications to /etc/services for services not already mentioned in that file? Allow me to re-quote the message I answered: I vote for allowing inetd.conf to specify a port number instead of a

Re: Mentioning RFC numbers in /etc/services

1999-08-02 Thread Sheldon Hearn
On Sat, 31 Jul 1999 23:00:15 MST, Doug wrote: Would you need these entries if inetd let you specify port numbers instead of service names? Errr... while that may be of value to someone, it has nothing to do with the issue Ben and I were discussing. Yes yes. I'm not trying to

Re: Mentioning RFC numbers in /etc/services

1999-08-02 Thread Sheldon Hearn
On Mon, 02 Aug 1999 07:30:32 -0400, Daniel Eischen wrote: Are you also going to allow getservbyport to lookup names? And how are you going to squish a name into an int? :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the

quad_t and portability

1999-08-06 Thread Sheldon Hearn
Hi folks, I want to patch wc(1) so that it uses quad_t instead of u_long. This is necessary if wc(1) is to produce sensible results for files containing more than 4GB of data. The changes made to NetBSD to support this are conditional on NO_QUAD being undefined. Do I need to worry about this?

Re: quad_t and portability

1999-08-06 Thread Sheldon Hearn
On Fri, 06 Aug 1999 15:29:25 +0200, Sheldon Hearn wrote: I want to patch wc(1) so that it uses quad_t instead of u_long. This is necessary if wc(1) is to produce sensible results for files containing more than 4GB of data. Yes yes, before you jump on my head, I meant u_quad_t. :-) Ciao

Re: Using legacy sysinstall to upgrade live system

1999-08-11 Thread Sheldon Hearn
On Wed, 11 Aug 1999 00:07:41 MST, "Jordan K. Hubbard" wrote: Nonetheless, for the expected installation experience one is encouraged to boot the desired OS release's installation media and select an upgrade instead of a new install. Gotcha. So you'd be interested in diffs that teach

Re: Using legacy sysinstall to upgrade live system

1999-08-11 Thread Sheldon Hearn
On Wed, 11 Aug 1999 17:08:10 CST, Wes Peters wrote: It's OK to let the users shoot their feet off, but they may not know they're about to shoot their feet off. Giving them an alert would be polite. I'll feel more comfortable about letting them shoot their feet off if you can point out

Re: Using legacy sysinstall to upgrade live system

1999-08-11 Thread Sheldon Hearn
On Wed, 11 Aug 1999 20:34:59 -0400, Tim Vanderhoek wrote: I suggest that it would be beneficial for you to let them shoot off their feet... I have used legacy sysinstall to upgrade a live multiuser system before and will probably do so again. Hair-raising. :-) Anyway, I've snuffled

Re: Various Questions

1999-08-12 Thread Sheldon Hearn
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

Re: New tests for test(1)

1999-08-12 Thread Sheldon Hearn
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.

Re: Various Questions

1999-08-12 Thread Sheldon Hearn
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

Re: New tests for test(1)

1999-08-12 Thread Sheldon Hearn
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 .

Re: New tests for test(1)

1999-08-12 Thread Sheldon Hearn
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

Re: New tests for test(1)

1999-08-13 Thread Sheldon Hearn
On Thu, 12 Aug 1999 11:41:31 -0400, "Brian F. Feldman" wrote: NetBSD's test(1) utility has this (-nt and -ot). We should probably merge in their changes. Hmm... this is in pdksh too... Don't go there. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with

Re: New tests for test(1)

1999-08-13 Thread Sheldon Hearn
On Fri, 13 Aug 1999 15:36:24 +1000, Peter Jeremy wrote: It would be nice, but there are portability issues. Hi Peter, I'm only replying to your mail because you're the last person to mention portability as a case againsdt NetBSD's test(1). Just how many other platforms need to support an

Re: libcompat proposition

1999-08-13 Thread Sheldon Hearn
On Fri, 13 Aug 1999 09:16:09 -0400, Jamie Howard wrote: I saw someone say that anything NetBSD did in the name of portability must be right (in the test thread). :) Close, but what I said was more along the lines that following NetBSD's footsteps on issues relating to portability is

Re: New tests for test(1)

1999-08-13 Thread Sheldon Hearn
On Fri, 13 Aug 1999 12:50:54 -0400, "Brian F. Feldman" wrote: I fully agree with this. If it can be cleanly added to the current test(1) (which it can), we should have it, even if it were JUST for the sake of portability. Ah, but I'm not proposing that we add new functionality to the

Re: Using legacy sysinstall to upgrade live system

1999-08-14 Thread Sheldon Hearn
On Fri, 13 Aug 1999 17:51:10 MST, dannyman wrote: Uhmmm, what if we don't have a floppy drive? Then you probably have a CDROM drive or a network interface, both of which can be used to get sysinstall onto your machine. :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with

Re: IDE quirk in 3.2-STABLE kernel ?

1999-08-16 Thread Sheldon Hearn
Hi folks, I didn't see any pointers other than pilot error raised in the recent thread with subject line: Subject: Re: IDE quirk in 3.2-STABLE kernel ? Perhaps those of you who're in support of the pilot error notion could have a look at PR 13174 and comment? The originator claims that his

Re: How much memory (max) will FreeBSD use?

1999-08-16 Thread Sheldon Hearn
On Mon, 16 Aug 1999 22:45:28 -0400, "Stephen J. Roznowski" wrote: On a stock system (3.2 and 4.0), how much RAM will a system be able to use? Will a stock system use all 4GB? I expect that someone else will answer your question. I just want to clear up a possible misunderstanding that could

Re: Kerberos 5 integration.

1999-08-16 Thread Sheldon Hearn
On Tue, 17 Aug 1999 00:51:27 -0400, "Matthew N. Dodd" wrote: Who were the parties that were heading up the Kerberos 5 integration? I have questions. Seek Ye first the kingdom of Mark. (markm) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe

Re: BSD XFS Port BSD VFS Rewrite

1999-08-17 Thread Sheldon Hearn
On Tue, 17 Aug 1999 00:30:02 CST, Warner Losh wrote: Acutally, the Nintendo 64 uses the Vr4300 series of chips from NEC. !!! I've been dethreading this subject line for a few days now, so I'm quite relieved to see this, the one e-mail message which I happened to check in on to make sure

Re: cvs commit: src/bin/test test.c

1999-08-18 Thread Sheldon Hearn
[Hi-jacked out of cvs-committers cvs-all] On Tue, 17 Aug 1999 17:18:53 MST, Brian Feldman wrote: green 1999/08/17 17:18:53 PDT Modified files: bin/test test.c Log: The new test(1) did not use access() correctly. I don't know why, since supposedly it's

Re: Change to /sys/net/if.c /sys/dev/syscons/syscons.c

1999-08-20 Thread Sheldon Hearn
On Fri, 20 Aug 1999 15:09:59 +0100, Cillian Sharkey wrote: + log(LOG_INFO, "%s%d: promiscuous mode disabled\n", + ifp-if_name, ifp-if_unit); You're the second person other than me to request this. :-) So are there any _objections_ to having the kernel match

Re: Change to /sys/net/if.c /sys/dev/syscons/syscons.c

1999-08-20 Thread Sheldon Hearn
On Fri, 20 Aug 1999 15:55:45 +0100, Cillian Sharkey wrote: Maybe..there was a lot of talk on another mailing list (-current I think?) about boot messages, level of verbosity etc. etc. so perhaps we should wait until this has been decided.. ? This has nothing to do with the boot messages,

Re: proposed change for /etc/periodic/* scripts

1999-08-23 Thread Sheldon Hearn
On Mon, 23 Aug 1999 09:59:29 +0100, Cillian Sharkey wrote: Ideas / Comments / Suggestions ? Diffs ? :-) Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message

Re: ls(1) options affecting -l long format

1999-08-23 Thread Sheldon Hearn
On Mon, 23 Aug 1999 01:00:05 MST, "Brian F. Feldman" wrote: The reason I say it doesn't make sense is that you shouldn't be asking for a long listing with ls -l if you want numeric ids, you should be using ls -n. Instead of your alias, you should just be using ls -n where you'd otherwise

Re: ls(1) options affecting -l long format

1999-08-23 Thread Sheldon Hearn
On Mon, 23 Aug 1999 11:36:00 +0200, Sheldon Hearn wrote: If there are no objections (other than the obvious backward issue of compatibility) in the next few days, I'll bring Chris's change in (with a style fix), as well as teaching -o to imply -l. Eeek, I've been confused. Our -o

Re: ls(1) options affecting -l long format

1999-08-23 Thread Sheldon Hearn
On Mon, 23 Aug 1999 13:13:14 +0200, Sheldon Hearn wrote: The -n option will imply -l, but -o will be a no-op unless at least one of -n and -l is specified. Manpage changes will be included in the deal. The diff for this change is available from: http://www.freebsd.org/~sheldonh

Re: ls(1) options affecting -l long format

1999-08-24 Thread Sheldon Hearn
On Mon, 23 Aug 1999 14:23:21 +0200, Sheldon Hearn wrote: The -n option will imply -l, but -o will be a no-op unless at least one of -n and -l is specified. Manpage changes will be included in the deal. I've been playing with the ls(1) that this patch produces and now that I've had some

mkfifo default creation mode 0777

1999-08-26 Thread Sheldon Hearn
Hi folks, I'm about to add a flag to mkfifo that allows you to specify creation mode. NetBSD does this already. However, there's a difference in the way our mkfifo and NetBSd's mkfifo create files. We create with permissions 0777 modified by umask. NetBSD creates with permissions 0666 modified

Re: HEADS UP Reviewers. VFS changes to be committed.

1999-08-26 Thread Sheldon Hearn
On Thu, 26 Aug 1999 08:28:29 GMT, Alfred Perlstein wrote: Am I to take it that silence is accpetance? I'll be committing this to -current tonight or tomorrow unless I get feedback. Recent discussions with bde and eivind indicate that at least some of the code you're about to touch has one

Re: df and procfs

1999-08-26 Thread Sheldon Hearn
On Thu, 26 Aug 1999 18:21:43 +0200, Neil Blakey-Milner wrote: (The man page seems to be in error, though, when it says that "sysctl vfs" tells what kinds of filesystems are available.) lsvfs should give a good indication. My dog! You learn something new every day. :-) Thanks, Sheldon.

Re: HEADS UP Reviewers. VFS changes to be committed.

1999-08-26 Thread Sheldon Hearn
On Thu, 26 Aug 1999 11:45:47 -0400, Bill Fumerola wrote: This would be post #3 of the same code and changes that no-one has reponded to. I hear you, and I was aware of that when I made my comments. Basically, it's a waste of time saying such a thing, so either be prepared to wait longer, or

REQ: Help with apparently impossible error in Makefile.inc1

1999-08-27 Thread Sheldon Hearn
Hi folks, While testing out a change I'm proposing for src/Makefile.inc1 (see my PR 13398, which proposes the addition of a WHICH_GAMES knob), I've hit my head against something I can't figure out. Basically, I have the following in Makefile.inc1: | .if !defined(NOGAMES)

Re: REQ: Help with apparently impossible error in Makefile.inc1

1999-08-27 Thread Sheldon Hearn
On Fri, 27 Aug 1999 08:06:29 -0400, Garance A Drosihn wrote: Each line that 'make' executes is executed in it's own environment, Forgive me father, I am but a worm. *lick* Thanks, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the

Re: Please review: rc file changes

1999-08-27 Thread Sheldon Hearn
Hi folks, What follows is a diff that presents Doug's changes (which must have required quite a bit of effort, thanks!) in a slightly different format which I think the grumpies here might prefer. Specifically, case statements look more like what a lot of folks are used to seeing, and

Re: Please review: rc file changes

1999-08-30 Thread Sheldon Hearn
On Sat, 28 Aug 1999 16:46:11 MST, Doug wrote: Hoping I'm running out of nits, :-) Hi Doug, 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

Re: More than 32 signals. Thought?

1999-08-30 Thread Sheldon Hearn
On Mon, 30 Aug 1999 15:55:56 +0200, Marcel Moolenaar wrote: The Linux trick I like to add is to have sigset_t always be the last field in structures so that the impact of enlarging sigset_t is minimal. On LITTLE_ENDIAN machines? Cia, Sheldon. To Unsubscribe: send mail to [EMAIL

  1   2   3   4   5   >