The design phase for FreeBSD 4.0 is coming to a close. There are a couple
of things I'm planning on (belatedly) for the SCSI tape driver. I'd like
feedback and suggestions about these and other things, so pass 'em my way.
One change I'm thinking about is probably controversial, so I'd like
Reread/reresponse, sorry- ENOCOFFEE:
1 filemark can not be used for EOT, it is EOF, you can't tell if what you
read next is another file or not that may have been left by a previosly
longer usage on the tape.
Well, read until *BLANK CHECK* seems to be what the driver
Okay- I hear you both.
What do you do with QIC drives which cannnot write 2FM then?
Can you give me a model of a QIC drive that has the ``can't write 2 FM's''
and I'll see if I can find one so that I can see this problem first hand
and propose a solution to it. I find it extreamly hard to
No. Make it a port. Policy, remember? 8)
I guess the anti-bloatists would have a point on this one...
I would not object to a port. It certainly eliminates the
bike shed arguments over it.
Did anyone bother to look at /usr/src/games/trek/main.c:
** C version by Eric P. Allman
"Rodney W. Grimes" wrote:
"Accidental" removals from the lists are so common that I give up. I no
longer even try to get back on them -- it's been happening for _years_ now,
and I have made multiple complaints about it, and if it's not a problem
"Accidental" removals from the lists are so common that I give up. I no
longer even try to get back on them -- it's been happening for _years_ now,
and I have made multiple complaints about it, and if it's not a problem for
whoever runs the mailing lists, then I just don't care that
On Thu, Oct 07, 1999 at 10:09:23AM -0700, Matthew Dillon wrote:
Intel's ECC implementation is not perfect (1), but it's good enough to
catch these sorts of problems.
Just as an interesting side note, we had a motherboard which
supported ECC ram and had ECC ram in it and which
:Hi again,
:
: Whoops: a few hours after downgrading to 3.1-STABLE I had a double fault
:error (strange, it didn't look like a normal panic screen, just the
:message and the content of three registers, then the syncing disks
:message). It seems that I might be wrong about hardware not being
[CC: trimmed to -current]
But this still doesn't entirely solve the problem. You still have
to build and install a new kernel before installing the world.
While this is typically what most -current folks do anyways, it
still prevents backing up to a previous kernel after the
Hi,
In the recent discussion about the breakage of the upgrade path from
-stable to -current numerous suggestions and other kinds of remarks have
been made. In this light I have the following proposal. Please share
your thoughts...
NOTE: This proposal only discusses upgrading from
Why are the tools being built using new syscalls? What causes this?
Mainly historical bugs. Includes are installed too early and they only
match the new syscalls. Tools are built using the new includes, so they
need new libraries to be consistent. Therefore the new libraries are
built
On Thu, Sep 30, 1999 at 06:25:56AM -0700, Rodney W. Grimes wrote:
Cons
o Upgrading from 3.3 and before to -current is only possible after
an upgrade to post 3.3.
Not good.
We recommend that 2.2.x people upgrade to the latest 2.2-STABLE offering
before trying to jump
On Thu, 30 Sep 1999, Harold Gutch wrote:
Uhm, that's the way I see it being _right now_ as well. What I
was thinking of, was that things would go smoother if you
wouldn't upgrade _right now_, but in [insert some time in the
near future here], as things would perhaps be "fixed" by then.
On Tue, Sep 28, 1999 at 09:11:31AM +1000, Greg Lehey wrote:
Good software shouldn't panic.
I wish _I_ could convince some people of this :-(.
Most certainly is. Could use the functionality to add to a plex's size for
striped or RAID5, but a bit of planning cures that. 8-)
It's
As Rodney W. Grimes wrote ...
On Tue, Sep 28, 1999 at 09:11:31AM +1000, Greg Lehey wrote:
Good software shouldn't panic.
I wish _I_ could convince some people of this :-(.
rather than having to recover each logical volume. It would also be
nice if you could recover mirrored
I'm just suggesting here that it would be nice if the authors of
this code would make it _equally functional_ to what was removed.
It's not nice to remove functionality unconditionally and then
provide no replacement at all...
That work is underway, and something to understand about
From: "Rodney W. Grimes" [EMAIL PROTECTED]
Date: Fri, 24 Sep 1999 03:00:55 -0700 (PDT)
Another thing that ISP coulds start doing (we are in process with
this now, but on a monitoring only basis, instead of a deny we
just log them) is to block all outbound from AS tcp 25 set
would immediately unsubscribe to any isp that decided this was acceptable
behavior on their part.
I agree.
Your work also has a serious security concern if it allows this you to
directly attatch to it's port 25.
No it doesn't, but you do bring up another good point why not to
At 03:00 AM 9/24/1999 -0700, you wrote:
Another thing that ISP coulds start doing (we are in process with
this now, but on a monitoring only basis, instead of a deny we
just log them) is to block all outbound from AS tcp 25 setup packets.
Hmm, maybe I'm interpreting this wrong (I hope so),
I agree.
Your work also has a serious security concern if it allows this you to
directly attatch to it's port 25.
No it doesn't, but you do bring up another good point why not to use the
ISP's mail server. Security. I don't want email to bounce on your box
and
[Charset iso-8859-1 unsupported, filtering to ASCII...]
I administer a number of remote FreeBSD boxes and starting with 3.x
they have been unreliable at rebooting. We all know FreeBSD wants to
keep running forever, however it seems to be at the expense of
reboot stability. I have found the
...
One question comes to mind: is there a way that the TSCs could become
desynchronized somehow? Even though all CPUs run at the same frequency,
isn't there a strong possibility for slight frequency deviation since
we use crystal oscillation instead of a more accurate atomic breakdown
On Sat, 18 Sep 1999 01:16:52 + (GMT), Adam Strohl [EMAIL PROTECTED]
said:
I've been getting this too on 4.0-C, just rebuild last night, still there.
top displays:
CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0%
idle
On my dual-PPro Intel BB440FX system
OK, Upgraded my Asus P2B-D machien from BIOS version 1008 to 1010, the
problem disappeared. Popped back to my old 1008 BIOS, problem came back.
So far about alls I have confirmed is that the problem does not exists
with BIOS 1009 when the apm code is not compiled into the kernel. I'll
have a
In article [EMAIL PROTECTED],
Garrett Wollman [EMAIL PROTECTED] wrote:
[POLLEXTEND, POLLATTRIB, POLLNLINK, POLLWRITE]
It is probably undocumented. I was a bit reluctant to document it
since I know that the interface is not correct. One of these days,
I (or more likely some
Hi,
The following patch to /usr/src/release/Makefile allows the
specification of the variable FASTCLEAN, which instead of doing
a recursive rm on CHROOTDIR, simply umounts/newfs/mounts. Of
course, this is only useful if your CHROOTDIR location is a
separate mount point (which mine is:
On Sat, 04 Sep 1999 21:34:09 -0700, Mike Smith [EMAIL PROTECTED] said:
The enumerator should assign these resources to a placeholder; I was
thinking the nexus was as good an owner as any. If there's an
"unknown" device that's probably even better.
Some of them should be claimed by
Nick Hibma wrote:
Please review the following patch to get all the log files in one place.
The commit will be accompanied by a HEADS UP. If no one objects I will
commit this in a couple of days.
The only thing I don't like about this is that it introduces a point of
Rodney W. Grimes writes:
What verion of the cvs binary are you running (cvs -v)?
Concurrent Versions System (CVS) 1.10 `Halibut' (client/server)
Are you getting a copy of CVSROOT?
yes...as part of src-all, but it's not used as *my* CVSROOT.
What is the content of *your
I've just committed the revised TCP timer code. There are some
user visible changes:
User visible TCP timers are now in units of the system clock
(10ms for the i386), not those of the slowtimeout (500ms). So
if you have customized one of these values, (e.g.:
John Polstra [EMAIL PROTECTED] writes:
The tags are expanding just fine up here in Seattle. :-)
I wish you would have included the rest of the output from your cvs
status command. It sounds a lot like your source tree was checked
out with "-ko". That would show up in the "Sticky
On Wed, 25 Aug 1999, Wilko Bulte wrote:
The USA... your prices tend to be a lot better than ours. I could can the
T2P4 but that would also mean I had to can the SIMMs (everything is DIMMs
now), get an AGP videocard and can the perfectly fine Millenium II (I need
the extra PCI slot
On Tue, 24 Aug 1999, Richard Tobin wrote:
Origin = "AuthenticAMD" Id = 0x580 Stepping=0
You have one of the first K6-2s off the line. There were definite problems
with these, and as such, they were specially distinguished by having 66
printed on top.
I have a 0x580
On Sun, 22 Aug 1999, Ollivier Robert wrote:
According to Narvi:
"Falling letters like in the movie with red bills"
Pill :)
That very important... The screensaver triggered me to see the movie
again. A. I love it.
Yeah, it's gotta be the perfect hacker's movie.
In message [EMAIL PROTECTED] Archie Cobbs writes:
: Not that easily.. how are you going to make ipfw dynamically know
: which ports have listeners and which don't?
By filtering all RST packets?
That would be closer than my set of rules, but has the undesired effect
of filtering what may be
[Charset iso-8859-1 unsupported, filtering to ASCII...]
This is an ACK. I like those names, the idea is okay given that
the documentation for it reflects what has been discussed here in
this thread so folks can understand this is a very simple security
measure.
Hmm, dumb question
Geoff Rehmet writes:
After the discussions regarding the "log_in_vain"
sysctls, I was thinking about a feature I would
like to implement:
Instead of sending a RST (for TCP) or Port Unreachable
(for UDP) where the box is not listening on a socket,
I would like to implement a
Brian W. Buchanan writes:
Can anyone think of any reason why this feature should
not be implemented?
I like that idea... net.inet.{tcp,udp}.drop_in_vain ?
Why do we need a sysctl knob for this when it can be easily accomplished
with IPFW?
Not that easily.. how are you
Rodney W. Grimes writes :
Now what would a box with so much security concern such that
it needed this knob be doing running an ftp session though
your point is valid and acceptable for low security boxes. And
I can see the real benifit that having this knob for those boxes
In message 37580f03.88efb...@sitara.net, John R. LoVerso writes:
But, consider going back to the discusssions leading up to the Host
Requirements
RFC (1122). The particular problem was that the original timeout value for
keepalives was tiny (a few minutes). 1122 dictated the corrections
Considering the number of hosts on the net today, which come and
go with no warning and with dynamic IP assignments, I would propose
that we disregard what the old farts felt about TCP keepalives,
and enable the sysctl net.inet.tcp.always_keepalive as default.
Setting this will make all
If ``make cleandir'' is leaving some cruft in any form behind anyplace
in the build tree things are broken.
Sounds very reasonable to me. Running the same command twice to get
things really clean sounds suspicious ;-)
Let me explain ``make cleandir'' then.
Perhaps you missed the
Wilko Bulte wrote:
PERL_SRC=/usr/obj/usr/src/gnu/usr.bin/perl/perl
Writing Makefile for DynaLoader
== Your Makefile has been rebuilt. ==
== Please rerun the make command. ==
false
false: not found
*** Error code 1
I periodically see this one reported, and It is always repaired
Hi,
There are two things going on with the route setup.
if [ x$defaultrouter != xNO ] ; then
static_routes=default ${static_routes}
route_default=default ${defaultrouter}
fi
1) since route_default is never used, it should be deleted, ignore that
Pierre Beyssac wrote:
Wouldn't it be sensible to issue a warning (or panic) when
increasing the reference count reaches 0, rather than causing a
later kernel segfault? It would involve some overhead though, and
I'm not sure having 2^32 routes is currently realistic since most
machines
Rodney W. Grimes wrote:
Pierre Beyssac wrote:
Wouldn't it be sensible to issue a warning (or panic) when
increasing the reference count reaches 0, rather than causing a
later kernel segfault? It would involve some overhead though, and
I'm not sure having 2^32 routes is currently
401 - 446 of 446 matches
Mail list logo
