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.
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
I really shouldn't be answering, since you've mailed the wrong mailing
list, but I can't resist. :-)
> the following config entries worke
[ 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 t
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 majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
[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 > /usr/ntp/
[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,
She
[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
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 Unsub
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
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 ind
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 numb
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 se
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 code
On Sun, 25 Jul 1999 21:50:55 MST, jko...@freebsd.org wrote:
> Yes, but /if/ KTRACE is present, today's code allows you to bypass
> the lack of read permissions on an executable. That shouldn't be
> allowed. The current behaviour could be regarded as a security
> hole actually :).
This doesn't
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 i
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 majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the
On Mon, 26 Jul 1999 22:17:20 +0200, Mark Murray wrote:
> "Wintendo" is a bad name for anything official. Try to find MS's
> official name for the format(s).
You're hoping for a standard name for file formats of games used on
Microsoft platformat? There are two words in that question that one
d
On Mon, 26 Jul 1999 22:46:31 +0200, Sheldon Hearn wrote:
> You're hoping for a standard name for file formats of games used on
> Microsoft platformat?
Duh, I'm being obtuse. Your question indicates that I've phrased my
proposal in such a way as to suggest that this is for
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 majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body
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
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 lac
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 p
Hi David,
Your commit catalogued in the cvs log for newsyslog.c:
revision 1.23
date: 1999/06/28 03:15:02; author: obrien; state: Exp; lines: +2 -2
Syntax for user/group is changed from "user.group" to "user:group" to be
consistant with chown(8).
This one raised a number of eyebrows and a few
On Tue, 27 Jul 1999 06:54:32 -0400, Tim Vanderhoek wrote:
> It used to be that packages would depend on X, but Sheldon reminded me
> (although I think it was accidental :-) that XFree86 was added to
> PACKAGE_IGNORE_DEPENDS to prevent this.
PKG_IGNORE_DEPENDS is what I had in mind. :-P
Ciao,
S
On Tue, 27 Jul 1999 06:57:49 -0400, Tim Vanderhoek wrote:
> Consider also adding owner:group support to -stable in order to
> provide the longest change-over period possible.
You have to read the CURRENT newsyslog(8) manpage before you realize
that this is a lose-lose situation:
COMPATIBILITY
On 27 Jul 1999 13:37:35 +0200, Dag-Erling Smorgrav wrote:
> 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 (textproc/freegrep),
On 27 Jul 1999 13:48:21 +0200, Dag-Erling Smorgrav wrote:
> > Version 0.3 broke port-building badly. Does version 0.7 make it through
> > a build of a whole stack of ports?
>
> Yes.
Excellent. I'll nuke the port once you've merged the new grep to STABLE.
:-)
Later,
Sheldon.
To Unsubscribe:
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 implement
On Tue, 27 Jul 1999 07:49:22 EST, David Scheidt wrote:
> Does any have numbers about how much slower the new grep is?
Just by the way, if the latest version somehow uses mmap without my
having noticed, then I've ontroduced a red herring. ;-)
Version 0.3 certainly didn't use mmap. As I understa
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 use
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 supp
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.
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 th
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 majord...@freeb
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): chris...@zoulas.com.
Confirmed. Other than the mistaken name, I think David obsoleted further
discussion, since it really is the be
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.
T
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
beh
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 accomp
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 majord...@freebsd.org
with "unsubscribe freebsd-hackers" i
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
|--- src/usr.bin/cmp/regular.c
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 sh
On Fri, 30 Jul 1999 00:53:56 MST, Mike Smith wrote:
> It probably belongs in param.h, and you can probably safely calculate it
> as (uid_t)0 - 1;
Excellent.
Another question I should have asked in my original mail is this: are
there magical reasons why we should want pwd_mkdb to bleat for ever
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
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
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 informati
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
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?
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 na
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
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
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
On 02 Aug 1999 13:27:44 +0200, Dag-Erling Smorgrav wrote:
> I don't see in what way an application could break if getservbyname()
> suddenly accepted numeric port specifications. It won't ``stop working
> as intended'', it'll keep on working as it always used to, plus a
> little more.
My applic
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 majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of t
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? Is
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.
Hi folks,
I've just gotten feedback from PR 12777, in which at least 2 people are
complaining that sysinstall as installed by 3.1-RELEASE can not be used
to upgrade a live machine to 3.2-RELEASE on the fly.
I've told both parties that they need to use a boot floppy with the
correct version of sy
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 sysi
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 _a
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 arou
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 exac
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.
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 th
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 .
On Thu, 12 Aug 1999 13:15:52 +0200, Graham Wheeler wrote:
> Portability is a Good Thing, but I write a lot of one-off scripts
> in which portability isn't an issue.
Not to mention that following NetBSD's lead on issues relating to
portability probably is seldom a bad idea. :-)
Give PR 13091 a
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,
Shel
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 majord...@freebsd.org
with "un
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 _e
Hi folks,
The pdksh-derived test(1) used by NetBSD and OpenBSD has made it through
a ``make world'' and package run on my box. It passes the regression
tests supplied with our own test(1) in exactly the same way as our own
test(1) does, and shows no noticeable performance difference.
I've mentio
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 _seldo
On Fri, 13 Aug 1999 12:52:05 -0400, "Brian F. Feldman" wrote:
> Direct veto by core member (Jordan) prevents this. I really think it
> should be in libcompat, the more I consider every option.
Regardless of what Jordan says, you should do your best to put it where
most other folks put it. Other
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 exis
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 majord...@freebsd.org
w
On Fri, 13 Aug 1999 23:42:48 MST, "Dave Walton" wrote:
> If you really want to work on an encrypted telnet, check out The
> Stanford SRP Authentication Project (http://srp.stanford.edu/srp/).
> I'd love to see SRP integrated into the FreeBSD telnet/telnetd.
Cool, another non-exportable syste
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
kern
On Mon, 16 Aug 1999 17:48:22 MST, dannyman wrote:
> The point of it is, it's easy enough to download the floppies, but
> it's really hard to boot a system off an .flp image. :p
Presumably you saw the posted trick about dd'ing the floppy image to
your swap partition and booting off _that_? :-)
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
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 majord...@freebsd.org
with "unsubscribe freebsd-
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 that
[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 i
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 matc
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,
Hi folks,
Chris Costello recently committed (and then backed out at my request) a
change to ls(1) that made -n (numeric ID's instead of names) imply -l
(long format).
The OpenGroup Single UNIX Specification is quite clear on the following
issue: -g, -n and -o all imply -l. Of course, the OpenGro
On Mon, 23 Aug 1999 09:59:29 +0100, Cillian Sharkey wrote:
> Ideas / Comments / Suggestions ?
Diffs ?
:-)
Ciao,
Sheldon.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
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
On Mon, 23 Aug 1999 10:18:40 +0100, Cillian Sharkey wrote:
> I haven't actually done any work on this (yet)
> but I might see what I can hack together..
>
The reason I suggest that you provide diffs first is that it's difficult
to comment on your proposal without
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
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/~sh
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 t
On Tue, 24 Aug 1999 12:59:49 -0400, Dan Seguin wrote:
> Can somebody tell me where to find the defintion for struct user that's
> contained in struct proc?
This is trick question, yes?
sys/proc.h struct proc
sys/user.h struct user
:-)
Ciao,
Sheldon.
To Unsubscribe: send mail to m
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 b
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
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,
Shel
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
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) && exists(${.CURDIR}/ga
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 majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of
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 conditiona
On Sun, 29 Aug 1999 12:40:20 +0200, Leif Neland wrote:
> if isyes ${thisvariable}
>
> case $1 of
> [Yy][Ee][Ss])
> exit 0
> ;;
> *)
> exit 1
> ;;
> esac
I hope you mean "in" instead of "of" and "return" instead of "exit". :-)
I like this. One of the reasons I like it so much is becaus
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 h
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 majord...@free
On Mon, 30 Aug 1999 12:26:06 CST, Warner Losh wrote:
> : On LITTLE_ENDIAN machines?
>
> Endian shouldn't matter.
Yup, it was the kind of stupid comment someone who doesn't actually know
what's going on would make. ;-)
I hadn't cottoned on to the notion of using an array.
Thanks,
Sheldon.
T
1 - 100 of 471 matches
Mail list logo
