On Monday, 23 August 1999 at 8:47:34 +0200, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Greg Lehey writes:
Why should it be made unavailable ?
So that certain multiple accesses can be done atomically.
You don't need that. You initialize a index to 0, and whenever the
sector
In message [EMAIL PROTECTED], Greg Lehey writes:
Why should it be made unavailable ?
So that certain multiple accesses can be done atomically.
You don't need that. You initialize a index to 0, and whenever the
sector with that index is written, you increment it.
At any one time you know
On Mon, 23 Aug 1999, Sheldon Hearn wrote:
The OpenGroup Single UNIX Specification is quite clear on the following
issue: -g, -n and -o all imply -l. Of course, the OpenGroup spec uses -g
for something we don't offer. Our -g is a backward compatibility option.
Yes, I agree that that's what
On Monday, 23 August 1999 at 9:47:40 +0200, Poul-Henning Kamp wrote:
In message [EMAIL PROTECTED], Greg Lehey writes:
Why should it be made unavailable ?
So that certain multiple accesses can be done atomically.
You don't need that. You initialize a index to 0, and whenever the
sector
Bah, so FreeBSD will be InSecureBSD ? Well, so long as the ITAR bear
stands around making grizzly noises at people, it seems.
I wouldn't count on that. As far as I can tell, what's holding KAME
integration up is the fact that they're not done merging with INRIA
yet.
A news about
On 23-Aug-99 Greg Lehey wrote:
I'm a little surprised that there's any objection to the concept of
mandatory locking. In transaction processing, locking is not
optional, and if any process at all can access a file or set of files
without locking, you can't guarantee the database
Evren Yurtesen writes :
it is possible to detect operating systems from their behaviours
of replying to packets.
see the program queso from ports/packages.
but anyway you can change the login prompt from /etc/gettytab file
Also have a look at ports/security/nmap, and go to
Hi,
Currently, the reports that are generated and emailed to root are
fine in what they do. however, a lot of the time there is actaully
nothing of interest in these reports if nothing has gone wrong
on the system etc. Basically I only want to know about the changes
that have happened. This
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
[ Geoff Rehmet ]
Another question that comes in to this is - how good a tool is nmap
for evaluating the predictability of the sequence numbers we generate?
Just a funny (?) aside - while playing about with nmap here a while back,
a colleague accidentally discovered that our Digital (or Compaq
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
Hi,
I've got a problem with my machine at home which is slightly BSD related
(cause ONLY BSD could handle the problem:))).
So: At this moment, I've got a 2.2.7-FreeBSD and an NT installed on my
PC.
There are two hard drives in the PC, the primary master IDE drive is a
2.5 Quantum drive, it
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 and the
Hi all,
if I put command like "system(/usr/local/bin/radacct)" in logout.c
everything goes normal but _if_ user logout normally that is, at prompt user
type logout
the problem is when user login using ssh and connection terminated by
accident such as the client hang and have reboot, utmp wasn't
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:
While going through old cvs commit log, I spotted this:
Index: param.h
===
RCS file: /home/ncvs/src/sys/sys/param.h,v
retrieving revision 1.50
diff -u -r1.50 param.h
--- param.h 1999/06/20 08:34:24 1.50
+++ param.h
[EMAIL PROTECTED] (John-Mark Gurney) writes:
Christopher Seiwald scribbled this message on Aug 18:
It's a pretty straightforward change to bypass the insertion sort for
large subsets of the data. If no one has a strong love for qsort, I'll
educate myself on how to make and contribute
What would be the right releasetag to use in order to build
a 3.2-STABLE 'release' (make release)? Would that be RELENG_3 ?
From looking at 'cvs log Makefile' in the top of the source tree
I get:
symbolic names:
RELENG_3_2_PAO: 1.222.2.4.0.2
RELENG_3_2_PAO_BP: 1.222.2.4
[EMAIL PROTECTED] (Greg Lehey) writes:
Again, if we have two concurrent transactions, we stand to gain money:
the updated balance is likely not to know about the other transaction,
and will thus "forget" one of the deductions.
Now I suppose you're going to come and say that this is bad
On 23 Aug 1999, Ville-Pertti Keinonen wrote:
[EMAIL PROTECTED] (Greg Lehey) writes:
Again, if we have two concurrent transactions, we stand to gain money:
the updated balance is likely not to know about the other transaction,
and will thus "forget" one of the deductions.
Now I
Hi,
A friend (Juha) has written a new device driver for another
batch of video capture cards from LifeVide, Genoa and ATIech
which use the Zoran and Philips SAA chipset.
The driver is likely to be called ztv
If I add this to FreeBSD, where is the best place
Keep it in /usr/src/sys/pci
Or
On Mon, 23 Aug 1999, Cillian Sharkey wrote:
Keeping records would be handy alright..but cutting out all
the "everything is ok" msgs would reduce reading time..having
an option for full report OR just the important results should satisfy
everyone..
What I do run things through a filter that
On Mon, 23 Aug 1999, Wilko Bulte wrote:
What would be the right releasetag to use in order to build
a 3.2-STABLE 'release' (make release)? Would that be RELENG_3 ?
Yes. Though RELENG_3 is a branch tag.
RELENG_3_2_PAO: 1.222.2.4.0.2
RELENG_3_2_PAO_BP: 1.222.2.4
Greg Lehey wrote:
all done in the kernel anyway. In userland, we'd use a different
example:
I make a number of financial transactions over the Internet. In
each case, the system checks my account balance, transfers the money
and deducts it from my account:
1. Check balance.
Daniel O'Connor wrote:
On 23-Aug-99 Greg Lehey wrote:
I'm a little surprised that there's any objection to the concept of
mandatory locking. In transaction processing, locking is not
optional, and if any process at all can access a file or set of files
without locking, you can't
On Mon, 23 Aug 1999 11:28:20 -0400
Dennis [EMAIL PROTECTED] wrote:
I heard a rumor that freebsd runs on a sparc, but I dont see any backing
for that. Is it in the works?
FreeBSD does not run on the SPARC. I think they've been talking about it
for ... what, 5 years now... but it
(I believe it got bounced due to my mistake in To: line.
sorry if you got it multiple times)
Hello, if this mailing list is inappropriate please tell me so.
I contacted radisson hotels for FreeBSDCon reservation with
special discount, to get the following
When I did a remote geographic disk based mirroring product a few
years ago, I just had an ioctl that said that this disk was special
for a while. Then the open routine would fail. This flag was cleared
in the close routine (and by the companion ioctl). I did allow users
to open the device w/o
On Tue, 24 Aug 1999, Jun-ichiro itojun Hagino wrote:
I contacted radisson hotels for FreeBSDCon reservation with
special discount, to get the following email - they don't know
about special rate code "FreeBSDCon". What is the exact code for
reservation? Do any of
On Mon, 23 Aug 1999, Dennis wrote:
I heard a rumor that freebsd runs on a sparc, but I dont see any backing
for that. Is it in the works?
dennis
It is more correct to say that it passes in and out of the thoughts of
people from time to time, with very little code that has actually
At 9:59 AM +0100 8/23/99, Cillian Sharkey wrote:
* if there are no passwd/group diffs found, don't print anything
out (not even the header). Same for setuid etc. diffs.
I have one change to one of the scripts, the one checking for mail
spool files. I changed it to recognize the spool file
Garance A Drosihn wrote:
I think this would need to be "knob-ized". I will ignore these
status reports for some time, and then some event comes up
where I am interested in reviewing all of them. If a partition
goes over 90%, for instance, I will want to know if it's been
growing 1% a
At 1:11 AM +0900 8/24/99, Daniel C. Sobral wrote:
Daniel O'Connor wrote:
I think its a good idea, and hey if people object it can always
be an option like -
option NO_MANDATORY_LOCKING
Phew, that was tough.
When introducing security holes, the default should be the hole
not being
Bill Fumerola wrote...
On Tue, 24 Aug 1999, Jun-ichiro itojun Hagino wrote:
I contacted radisson hotels for FreeBSDCon reservation with
special discount, to get the following email - they don't know
about special rate code "FreeBSDCon". What is the exact code for
On Mon, 23 Aug 1999, Kenneth D. Merry wrote:
Unfortunately, you have to call the local hotel to get reservations, and
not the toll-free national hotline. The hotel in Berkeley doesn't have a
toll free number, so after sitting on hold with the Berkeley Radission for
15 minutes, burning long
Bill Fumerola wrote...
On Mon, 23 Aug 1999, Kenneth D. Merry wrote:
Unfortunately, you have to call the local hotel to get reservations, and
not the toll-free national hotline. The hotel in Berkeley doesn't have a
toll free number, so after sitting on hold with the Berkeley Radission
Hi list,
About the problem bellow, I bought a 2940 Adaptec Ultra2 Wide SCSI
controller, but it didn't work too.
I wrote to Justin T. Gibbs and he told me that my problem is not SCSI.
Somebody has any idea?
[]s,
Luiz Morte da Costa Junior
Analista de RedesE-mail: [EMAIL
On 23-Aug-99 Cillian Sharkey wrote:
yes perhaps an /etc/periodic.conf would be good, to control the level
of verbosity and/or set options for each script ?
I've hacked periodic here so that the scripts can be turned off with knobs in
a periodic.conf file. This would simplify customizing new
Has anyone else gotten this server board to work?
I've got an N440BX and have been considering getting the L440GX+ but
haven't because I don't know if it works..
Kevin
On Mon, 23 Aug 1999, Luiz Morte da Costa Junior wrote:
Hi list,
About the problem bellow, I bought a 2940 Adaptec
At 10:12 PM +0200 8/23/99, Mark Murray wrote:
Folk are all skirting around a very convenient (and necessary)
loophole; in cases where there _is_ mandatory locking, there
is always some meta-user which is allowed to violate this.
If we include non-unix systems in the discussion, this isn't
always
On Mon, 23 Aug 1999, Garance A Drosihn wrote:
At 11:29 AM -0400 8/23/99, Chuck Robey wrote:
I think mandatory locking should exist, but only be available to root.
If a program needs this, it must run with root privs, so that ordinary
users cannot wedge the machine, but (as usual) root can
Chuck Robey wrote:
I think Garrett's fears are of folks unwittingly wedging machines too
easily, so real mandatory locking ought to be restricted to programs
that root can set up.
And those fears are well-founded, but your proposed solution just creates
another set of bottlenecks. Making
On Monday, 23 August 1999 at 15:28:01 -0400, Garance A Drosihn wrote:
At 3:28 PM +0930 8/23/99, Greg Lehey wrote:
I'm a little surprised that there's any objection to the concept
of mandatory locking. In transaction processing, locking is not
optional, and if any process at all can access a
Geoff Rehmet writes:
Also have a look at ports/security/nmap, and go to
www.insecure.org.
Hm, just did that. While reading up on nmap, I saw this:
"TCP Initial Window -- This simply involves checking the window
size on returned packets. [...] In their "completely rewritten"
TCP
Hi Greg, hackers list,
I don't want to express an opinion about the need or otherwise
for mandatory locking, but I would appreciate a teensy
clarification of the problem domain:
On Mon, Aug 23, 1999 at 05:43:45PM +0930, Greg Lehey wrote:
To write a block to a RAID-5 device, you need to:
On Mon, Aug 23, 1999 at 03:28:01PM -0400, Garance A Drosihn wrote:
Anyway, I am also puzzled as to why there would be much objection
to the option of mandatory locking. My initial systems-programming
If you provide mandatory locks that can be broken, then many of the
objections may
On Mon, Aug 23, 1999 at 10:12:38PM +0200, Mark Murray wrote:
In process-space, this is the kernel. In file-space, this should
be root. Processes that require mandatory locking must revoke
superuser before attempting locks.
I don't like restricting the breaking of mandatory locks to the
On Mon, Aug 23, 1999 at 12:28:32AM -0700, Christopher Seiwald wrote:
The alteration that I've tried and tested is to have the isort bail
back to qsort if it does more than N swaps. I put N at 1024, which
Perhaps a ratio: #comparisons : # swaps
If the ratio gets too high, then bail.
--
On Mon, 23 Aug 1999 17:44:47 -0700
"Dave Walton" [EMAIL PROTECTED] wrote:
Hm, just did that. While reading up on nmap, I saw this:
"TCP Initial Window -- This simply involves checking the window
size on returned packets. [...] In their "completely rewritten"
TCP stack for
The thing about well-intentioned but incorrect locking code is that
it will appear to work fine, until it trips over the one code path
where it forgets to lock some file that it should have locked. And
even then, the code will "work" just fine, until multiple processes
are accessing that
On Mon, Aug 23, 1999 at 10:59:10PM -0400, Chuck Robey wrote:
Dunno about that.. if you're using advisory locking, you know to say
"lock the file, then read the data, do your calculation, write it out,
and unlock". This manditory locking sounds like an invitation for
disaster. "I don't
On Mon, 23 Aug 1999, Christopher Masto wrote:
Bleah.. I can't count the number of times I've seen idiotic code like:
open file
read data
close file
open file for write
write data
close file
Mandatory locking of the type above doesn't force such a thing to work.
What has that code
On Monday, 23 August 1999 at 23:11:30 -0400, Christopher Masto wrote:
On Mon, Aug 23, 1999 at 10:59:10PM -0400, Chuck Robey wrote:
Dunno about that.. if you're using advisory locking, you know to say
"lock the file, then read the data, do your calculation, write it out,
and unlock". This
On Mon, Aug 23, 1999 at 11:16:21PM -0400, Chuck Robey wrote:
On Mon, 23 Aug 1999, Christopher Masto wrote:
Bleah.. I can't count the number of times I've seen idiotic code like:
open file
read data
close file
open file for write
write data
close file
Mandatory locking of
On Tue, Aug 24, 1999 at 12:52:10PM +0930, Greg Lehey wrote:
No, I think you're confusing opening and locking. It's something like
this:
User 1User 2
open file open file
lock file read file (blocks)
diddle file
On Monday, 23 August 1999 at 23:27:27 -0400, Christopher Masto wrote:
On Mon, Aug 23, 1999 at 11:16:21PM -0400, Chuck Robey wrote:
On Mon, 23 Aug 1999, Christopher Masto wrote:
Bleah.. I can't count the number of times I've seen idiotic code like:
open file
read data
close file
open file
I am involved in a messaging system at work in which we need to send/receive
large amounts of small (one line messages) SMTP messages. We are currently using
Sendmail 8.9.3
on HPUX.
Our application sends messages down a FIFO to a daemon process that is reading from
the FIFO. This process then
I am involved in a messaging system at work in which we need to send/receive
large amounts of small (one line messages) SMTP messages. We are currently using
Sendmail 8.9.3
on HPUX.
Our application sends messages down a FIFO to a daemon process that is reading from
the FIFO. This process then
Thank you for your reply. At what point should I set this socket option? I
am assuming right after the socket is allocated??
I will try this and post my results tomorrow night.
For those wondering, I cannot just execute Sendmail directly, there are many
architectural reasons for this
On Tue, 24 Aug 1999, Wayne Cuddy wrote:
Date: Tue, 24 Aug 1999 00:38:21 -0400 (EDT)
From: Wayne Cuddy [EMAIL PROTECTED]
To: FreeBSD Hackers List [EMAIL PROTECTED]
Subject: network performance vs. linux on small transfers
I am involved in a messaging system at work in which we need to
As an (former) implementer of fast TCP/IP peer-peer communications, I'd have
to agree with Dave, and say that it is definitely the TCP_NODELAY option.
You'll find that disabling the TCP-ACK delay will greatly increase your
performace.
The reason that it is so "slow" is because the TCP/IP stack
On Tue, 24 Aug 1999, kadal wrote:
On Tue, 24 Aug 1999, Wayne Cuddy wrote:
Date: Tue, 24 Aug 1999 00:38:21 -0400 (EDT)
From: Wayne Cuddy [EMAIL PROTECTED]
To: FreeBSD Hackers List [EMAIL PROTECTED]
Subject: network performance vs. linux on small transfers
I am involved in a
Wayne Cuddy scribbled this message on Aug 24:
Thank you for your reply. At what point should I set this socket option? I
am assuming right after the socket is allocated??
I will try this and post my results tomorrow night.
For those wondering, I cannot just execute Sendmail directly,
According to kadal:
you may also try other MTA such as qmail, postfix, etc.
Postfix (and qmail I think) support SMTP PIPELINING, which greatly reduce
latency. It is very interesting for small messages.
--
Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED]
FreeBSD
Hi,
I am going through the networking code
for the stable release.
In the file ip_input.c there is a
call to a function ip_nat_init() in the function
ip_init(). However I have been unable to
locate the code for this function (ip_nat_init()).
Could somebody please tell me in which
file
On Wed, 18 Aug 1999, Marc Ramirez wrote:
Oh! I was under the impression that it just didn't work, even with
correct perms, but I use FreeBSD. Lemme try it... Can't mount, even
with 0666 on /dev/fd0. Maybe I'm being stupid. Wouldn't be the first
time!
It's controlled by a sysctl in
On Wed, Aug 18, 1999, Sheldon Hearn 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 ksh-derived, and it's not broken in pdksh. I've added
:On Wed, 18 Aug 1999, Poul-Henning Kamp wrote:
:
: Matt doesn't represent the FreeBSD project, and even if he rewrites
: the VFS subsystem so he can understand it, his rewrite would face
: considerable resistance on its way into FreeBSD. I don't think
: there is reason to rewrite it, but there
I am in the process of upgrading a NIS master using version 2.1.0 to version
3.2. The 'Makefile' has been customized to include automount maps for our
IRIX machines as was the 'Makefile' in the old NIS Master. The problem is
that for some reason the program 'yp_mkdb' in 3.2 is much more picky. It
Any supported cards in 3.2.x? The HCL pages don't list any:(
Thanks,
--- David
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
2. Advisory locks are hung off private backing objects.
I'm not sure. The struct lock * is only used by layered filesystems, so
they can keep track both of the underlying vnode lock, and if needed their
own vnode lock. For advisory locks, would we want to keep track both of
I am in the process of upgrading a NIS master using version 2.1.0 to version
3.2. The 'Makefile' has been customized to include automount maps for our
IRIX machines as was the 'Makefile' in the old NIS Master. The problem is
that for some reason the program 'yp_mkdb' in 3.2 is much more picky. It
Matt doesn't represent the FreeBSD project, and even if he rewrites
the VFS subsystem so he can understand it, his rewrite would face
considerable resistance on its way into FreeBSD. I don't think
there is reason to rewrite it, but there certainly are areas
that need fixing.
You are
On Tue, 17 Aug 1999, Brian C. Grayson wrote:
On Tue, Aug 17, 1999 at 07:17:45PM -0700, Wilfredo Sanchez wrote:
A group of us at Apple are trying to figure out how to handle
situations where a filesystem with "foreign" user ID's are present.
Have you looked at mount_umap(8)? I
On Sunday, 22 August 1999 at 22:04:38 -0700, Matthew Dillon wrote:
Somehow you need to get a lock.
You mean have one program make a fcntl call that causes other
programs to return an error or block if they try to open that
file while the first program holds an open descriptor?
According to Brian F. Feldman:
-O lets you do explicit inlining, and -O2 enables -finline-functions.
You meant -O3 of course.
-O3Optimize yet more. This turns on everything -O2
does, along with also turning on -finline-func-
tions.
--
Ollivier
On 23-Aug-99 Greg Lehey wrote:
I'm a little surprised that there's any objection to the concept of
mandatory locking. In transaction processing, locking is not
optional, and if any process at all can access a file or set of files
without locking, you can't guarantee the database
In message 19990823152849.h83...@freebie.lemis.com, Greg Lehey writes:
Why should it be made unavailable ?
So that certain multiple accesses can be done atomically.
You don't need that. You initialize a index to 0, and whenever
the sector with that index is written, you increment it.
At any
On Monday, 23 August 1999 at 8:47:34 +0200, Poul-Henning Kamp wrote:
In message 19990823152849.h83...@freebie.lemis.com, Greg Lehey writes:
Why should it be made unavailable ?
So that certain multiple accesses can be done atomically.
You don't need that. You initialize a index to 0, and
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
Archie's mod to qsort:
| - if (swap_cnt == 0) { /* Switch to insertion sort */
| + if (n = 32 swap_cnt == 0) { /* Switch to insertion sort */
As Akira Wada points out, this eliminates the benefit of the optimization
in the first place, which is to let isort take over if the data is
In message 19990823162813.i83...@freebie.lemis.com, Greg Lehey writes:
Why should it be made unavailable ?
So that certain multiple accesses can be done atomically.
You don't need that. You initialize a index to 0, and whenever the
sector with that index is written, you increment it.
At
On Mon, 23 Aug 1999, Sheldon Hearn wrote:
The OpenGroup Single UNIX Specification is quite clear on the following
issue: -g, -n and -o all imply -l. Of course, the OpenGroup spec uses -g
for something we don't offer. Our -g is a backward compatibility option.
Yes, I agree that that's what
On Monday, 23 August 1999 at 9:47:40 +0200, Poul-Henning Kamp wrote:
In message 19990823162813.i83...@freebie.lemis.com, Greg Lehey writes:
Why should it be made unavailable ?
So that certain multiple accesses can be done atomically.
You don't need that. You initialize a index to 0, and
Bah, so FreeBSD will be InSecureBSD ? Well, so long as the ITAR bear
stands around making grizzly noises at people, it seems.
I wouldn't count on that. As far as I can tell, what's holding KAME
integration up is the fact that they're not done merging with INRIA
yet.
A news about
On 23-Aug-99 Greg Lehey wrote:
I'm a little surprised that there's any objection to the concept of
mandatory locking. In transaction processing, locking is not
optional, and if any process at all can access a file or set of files
without locking, you can't guarantee the database
Evren Yurtesen writes :
it is possible to detect operating systems from their behaviours
of replying to packets.
see the program queso from ports/packages.
but anyway you can change the login prompt from /etc/gettytab file
Also have a look at ports/security/nmap, and go to
Hi,
Currently, the reports that are generated and emailed to root are
fine in what they do. however, a lot of the time there is actaully
nothing of interest in these reports if nothing has gone wrong
on the system etc. Basically I only want to know about the changes
that have happened. This would
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
[ Geoff Rehmet ]
Another question that comes in to this is - how good a tool is nmap
for evaluating the predictability of the sequence numbers we generate?
Just a funny (?) aside - while playing about with nmap here a while back,
a colleague accidentally discovered that our Digital (or Compaq
Ideas / Comments / Suggestions ?
^ ^^^
Well ?
Diffs ?
I haven't actually done any work on this (yet)
but I might see what I can hack together..
;)
Cillian
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe
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 use
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 1999-08-23 (09:59), Cillian Sharkey wrote:
and the same for all the other tests..basically if there's nothing
to report don't print anything (not even the header) otherwise
print the header and the results..
Ideas / Comments / Suggestions ?
I have changes to this effect active on a
Currently, the reports that are generated and emailed to root are
fine in what they do. however, a lot of the time there is actaully
nothing of interest in these reports if nothing has gone wrong
on the system etc. Basically I only want to know about the changes
that have happened. This would
Hi,
I've got a problem with my machine at home which is slightly BSD related
(cause ONLY BSD could handle the problem:))).
So: At this moment, I've got a 2.2.7-FreeBSD and an NT installed on my
PC.
There are two hard drives in the PC, the primary master IDE drive is a
2.5 Quantum drive, it is
Make sure they always generate some output so that a message
does get mailed. On more than once occasion I noticed that one
of my boxes keeled over or the network broke when I didn't
get my expected daily output from that machine.
My proposal would only *cut down* on all the white space,
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 and the
On Mon, Aug 23, 1999 at 09:59:29AM +0100, Cillian Sharkey wrote:
* if there are no passwd/group diffs found, don't print anything
out (not even the header). Same for setuid etc. diffs.
* For the 'df' status, only report filesystems that are over
a certain capacity (95% or only xxMb
On 23-Aug-99 Brian Somers wrote:
I think its a good idea, and hey if people object it can always be an
option
like -
option NO_MANDATORY_LOCKING
Not quite - developers have to deal with the mess that it would cause
- Matt for example says:
Well, I think it would be a useful option,
1 - 100 of 163 matches
Mail list logo
