these days.
Remember the idiot who patented the +/-50 2-digit year rule?
Again, nothing to worry about here.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
rly stupid to go after anyone in regards to this
particular patent, because the prior art is so obvious. But, then
again, this guy patented something that had prior art for years before
his patent so maybe he's just that stupid :-(
-
a huge library of prior-art to help us fight these
idiots. Go open source!
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
both pointing at the same point,
let the cat follow it around a bit, then split them into two different
dots going opposite directions.
If you have two cats get one following each dot, then collide the
dots.
-Matt
To Unsubscr
er the run level) to a master set of
startup files. Blech. Yuch. Ptooey!
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
:
:David Malone wrote (2001/06/11):
:> On Sun, Jun 10, 2001 at 05:20:50PM -0700, Peter Wemm wrote:
:> > I agree totally. This should have been done ages ago, I've been burned on
:> > it a few times, but never badly enough to go fix it.
:>
:> I've committed this
esses.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
h Cejka - the first patch was pretty good but didn't
quite hit the mark and now we have a new candidate patch that seems to
cover all the bases, which David Malone is reviewing and will
probably commit to -current (and me to stable afterwords).
:Matt Dillon wrote:
:> The issue here is first: since we are fixing a bug we might
:> as well be as compatible as possible with other platforms and,
:> second: on general principles it does make sense to keep SIG_IGN
:> operation independant from the newer SA_NOCLDWA
:
:On Thu, 14 Jun 2001, Matt Dillon wrote:
:
:>My advise: First make it work. THEN make it work better.
:
: Excellent advice, as long as you don't skip the steps of
:appropriately defining the problem domain and evaluating all of the
:possible solutions for it.
Well, now
My advise: First make it work. THEN make it work better.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ty good indication of how biased they
were. I'll bet they didn't even bother compiling up a kernel... something
that is utterly trivial in a FreeBSD system, and if they did they
certainly didn't bother tuning it.
-Matt
To U
insane. But for 4.2 it was turned off.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
:Of course, assuming dirpref and Ian's new directory cache have been MFC'd
:by the time 4.4 comes out, it will scream on that same benchmark.
:
:Mike "Silby" Silbersack
Yup! Even without dirpref.
-Matt
To Unsubscribe:
ut what is deleting or overwriting
the file and make it rename the file to something else instead, then have
a cron job that goes in every so often and deletes the renamed files
over X amount of time old.
-Matt
To Unsubscribe: send mail
vironments.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ctually running that kind of load had better be
able to afford (or be) a sysop who at least knows his ass from a hot rock!
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ested in keeping the
integrity of the machine as a whole together then it is tuning itself
to match some idiot who thinks he is gods own gift to humanity running
a benchmark.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTE
ds on the default configuration of their systems and anyone who
isn't willing to maintain them after they've been installed is throwing
away money. Lots of money. It's that simple. If your IT department
isn't up to the task then maybe you should consider firing
some time tuning it, then the only thing wrong with the picture is
*you*, Not the machine, Not the OS... but you. Don't blame your problems
on the machine if you aren't willing to lift a finger learning how it
works.
-Matt
:This is
accept()ing them in a tight loop is in fact more cpu-efficient then
waking up the process for each one. You get this effect under heavier
loads whether you are using select(), poll(), or kqueue().
-Matt
To Unsubscribe: send mail to [E
W2K box operating, the amount of work it takes to upgrade one, and the
amount of work it takes to fix one when something breaks.
(remainder removed)
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
pcorn?
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
'm sure people who run 4G machines can give you better information, I've
never run anything larger then 2G myself, though expect down the line
I'll begin needing 4G machines to support larger databases.
-Matt
To Unsubscribe: send mai
are serving
web pages and the pages do not fit entirely in ram, you are likely to
hit disk I/O limitations long before you hit network/cpu limitations.
Etc.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freeb
kernel modules.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
:
:On Tue, 19 Jun 2001, Matt Dillon wrote:
:
:> to handle more then 250 requests/sec. With the connection load you
:> want to handle, the chance of the data being cacheable in ram is
:> fairly low. So a disk-based caching proxy will drop connection
:> performance b
:
:On Wed, 20 Jun 2001, Matt Dillon wrote:
:
:> This is fairly easy to do. You can use SO_SNDBUF and SO_RCVBUF
:> socket opts to adjust the tcp buffer space. You can make the default
:> small and receive-centric and when you think you've got a good
:> connectio
:
:On Wed, Jun 20, 2001 at 12:04:22AM -0700, Matt Dillon wrote:
:>
:> A web proxy could be
:> round-robined fairly easily, but for a mail relay it is often a good
:> idea to split the incoming and outgoing mail into two separate round
:> robins (two separate gro
u built & run a kernel compiled with "options CAMDEBUG" ? This may
provide more insight into where things are going wrong.
--
Matt Emmerton
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
- Original Message -
From: "Dan Nelson" <[EMAIL PROTECTED]>
To: "David Gilbert" <[EMAIL PROTECTED]>
Cc: "Matt Emmerton" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Tuesday, Nov
Is it possible to use poll or select to detect a change in the status
bits of the parallel port? I tried something like this, and took bits
5 and 6 of the status register low and nothing seemed to happen. Is
what I am trying to do even possible, or I am supposed to take a
certain bit low to cause
happen for anyone else? (Mabe someone running 5.4 can test
> this?)
The first line is the average since the system was last booted; all other
lines are instantaneous.
--
Matt Emmerton
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
n/fsdb/fsdb.c.diff?r1=1.24&r2=1.25&f=h
Is this something that folks would like to see on FreeBSD? I've got
RELENG_5_4 and RELENG_6_0 boxes here in my office so I can whip up the
patches and do some testing in short order.
Regards,
--
Matt Emmerton
_
tell me. Thanks.
>
> Tony.
> --
> f.a.n.finch[EMAIL PROTECTED][EMAIL PROTECTED]
> 356 pungent unguent for stump-itch
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
I think you are ref
Committers who mess with VOP_LOOKUP (docs or otherwise), and make
a mistake, are automatically pardoned due to the fact that VOP_LOOKUP
is massively convoluted and messy that it has been known to be mistaken
for a turkish artichoke at times.
ause page table sharing is
not possible between cpu's under 3.x. Under 3.x UP there isn't
a problem.
Under 4.x there is no problem (UP or SMP).
-Matt
:
:---
:
:
:#include
:#include
:
:
x27;t even bother to zero that area... UNTIL that particular
page is mapped by some user process. That is the point where the partial
page-zeroing code comes into play. It has nothing to do with the idle
loop pre-zeroing but since its a generic routine (part of the VM core),
the idle
t all the speed, resolution,
and color depth you'll ever need for X short of playing hardcore
games.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ause interactive loads tend
not to allocate memory at a high rate, so the hysteresis points do not
get hit as often. Hmm. Maybe there's a bug in the hysteresis
calculation, I'll check it out.
-Matt
:> In regards to
:
:Matt,
:
:I noticed /tmp and /var/tmp are used slightly differently, for example, the
:contents of /tmp are not expected to survive a reboot, while /var/tmp is
:used for files you might need after a crash, like vi recovery files.
This may have been true at one time in the past, but these
:basically obsolete. As I understood it, the regular file system has
:sophisticated caching built in and effectively acts like a memory file
:..
:
:I noticed Matt Dillon wrote a handbook section on the VM system at
:http://www.freeBSD.org/handbook/internals-vm.html that includes
:some info on
lization xinetd[204] : open (/etc/xinetd.conf) failed:no
such file or
directory (errno=2)
xinetd [204]: {init_services} couldn't get confiduration.
Exit xinetd.
thank you for any insight. sorry if this is not wrapped right, as i am
using work
email via the web.
Matt
mail.insync.net
you for any insight. sorry if this is not wrapped right, as i
am
> using work
> email via the web.
> Matt
> mail.insync.net
Matthew Bettinger
Financial Synergies,Inc.
1177 West Loop South, Suite 1400
Houston,Texas 77027-9086
713-623-6600
713-623-6771 FAX
BEGIN:VCARD
VERSION:2
byte order, the conversion is necessary. If
this fixes Danny's problems, and doesn't break anyone else (Paul?), I'd
say it should be committed.
-Matt
:Umm.. I'm using the netboot just fine here for the ports cluster and
erical IP:
option root-path "999.999.99.99:/";
option option-128 "999.999.99.99:/images/swap";
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
:You can specify swap paritions with dhcpd just fine, just use
:the the numerical IP:
:
:option root-path "999.999.99.99:/";
:option option-128 "999.999.99.99:/images/swap";
:
: -Matt
You know, my writte
irq
other than that things seem to be running fine with a stray irq or not. ;->
matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
owing patch, though it might take more fiddling
:to get it right.
:
:(The patch is by Ian Dowse, Matt Dillon had a quick look at it and said
:it looked OK, we've been testing it for a bit here).
:
: David.
Ah yes, that problem... if Ian's patch solves the problem for Vadim, I
thin
rom locking up large
files that have lots of dirty pages for long periods of time.
-Matt
:
:Matt, I'm not sure if Paul mailed you yet so I thought I'd take the
:initiative of bugging you about some reported problems (lockups)
:when d
formation to come up with something good.
-Matt
:-Alfred
:
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
erned by max_page_launder.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
pages in the system then you would normally be able to
have. This 'feature' has had the unfortunate side effect of screwing
up the pageout daemon's algorithms, but that's fixable.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTE
elease is rolled before I commit it or whatever the final patch
winds up looking like.
-Matt
Index: vm_page.c
===
RCS file: /home/ncvs/src/sys/vm/vm_page.c,v
retrieving revision 1.147.2.3
diff
:On Tue, Oct 24, 2000 at 01:10:19PM -0700, Matt Dillon wrote:
:> Ouch. The original VM code assumed that pages would not often be
:> ripped out from under the pageadaemon, so it felt free to restart
:> whenever. I think you are absolutely correct in regards to the
:>
are useful only in
very, very, very specialized circumstances. In all other circumstances
they are no better then a pain in the rear.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ed,
:> so you do not have to preallocate or prereserve file space.
:
:So will address calculation + filesystem holes, and sufficiently large
:filesizes :-)
Uh, not with a 50:1 file size factor it won't.
-Matt
To Unsubscribe: send mail to [
:Hi, Matt! Thanks for the replies. I'll try and keep you interested ;-)
:
:Hmm... Perhaps you're still missing my original point? I'm talking about
:a file with 96GB in addressable bytes (well, probably a bunch of files,
:given logical filesize limitations, but let's say f
lly use the feature, at least not for 'permanent'
data sets.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
e filesystem to try to reorder nearby blocks,
but it was never designed to handle sparse files so
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
:Yes, there's a high probability of that. It's one of the reasons
:why people typically use the feature, at least not for 'permanent'
:data sets.
Ahhh... of course I meant 'typically do not use the feature'. Heh.
.bris.ac.uk/
No, we don't have anything like that, though our VFS layer could
support it.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
eral datastore problems, and nearly
all of these problems are tuned (or inherently) specific to the block
size of the underlying system. Using a sparse file for general data
store just isn't all that hot an idea, because by its very nature data
store is, well, storing data. Packin
e we could
implement some sort of free-space semantics trivially too, at least
for UFS, using a struct flock to pass the parameters to a fcntl.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
r the impression that SUN does that, does
anyone know?
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
1 2 98
Difference: around 132K less free memory for each instance of fgrep
that is run.
So fgrep, with an RSS of 496K, actually only eats up around 132K of
unsharable ram.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "
da0s1 auto
Presumably a '-z' option to disklabel would do the equivalent of what
the 'dd' in the above examples are doing.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
to do it at device-open and then save a reference that your
interrupt can then use.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
r everyone running VALinux hardware is going to be real
confused if they ever disklabel a disk manually.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
if all you want to
do is initialize a label on a slice.
-Matt
Index: sbin/disklabel/disklabel.c
===
RCS file: /home/ncvs/src/sbin/disklabel/disklabel.c,v
retrieving revision 1.28.2.
possibly getting it into
the release.
-Matt
Index: sbin/disklabel/disklabel.c
===
RCS file: /home/ncvs/src/sbin/disklabel/disklabel.c,v
retrieving revision 1.28.2.3
diff -u -r1.28.2.3 disklabel.c
--- s
perform any worse then declaring an array on the stack
in terms of performance.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
something that belongs in the kernel. The
only other choice would be to rewrite the code into a form suitable
for the kernel's smaller stack.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
This is quite odd. Anybody have any ideas?
(kgdb) back
#0 mi_switch () at machine/globals.h:119
#1 0xc0167711 in tsleep (ident=0xe19418c0, priority=8,
wmesg=0xc0291cfd "vget", timo=0) at ../../kern/kern_synch.c:467
#2 0xc0190193 in vget (vp=0xe19418c0, flags=393216, p=0xdca87780)
rgued
that even within the library those types of assumptions should not be
made unless absolutely necessary.
There isn't much we can do about the issue except fix the instances
of mis-programming as they show up.
-Matt
T
:Hi,
:
:I think I have a sufficient fix for PR kern/19572. Could somebody please
:Review/Comment this?
:To quote:
Looks reasonable to me! It certainly can't make things worse :-)
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
eel comfortable with it in your own testing, go ahead and
commit it to -current. But give it at least a good week's worth of
testing (or longer) before MFCing it to -stable.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "u
dy some code to
handle that sort of thing, but I haven't looked at it closely.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
stallation of boot blocks by disklabel
screwing up the partition table?
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ws up the dos partition
table.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
tion is, why is disklabel failing above? It shouldn't be
failing..it should let me label da0s1.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
alling the dummy fdisk partition table? That is, for the
case where -B is used on a slice (da0s1) verses on the whole-disk (da0)?
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
the same BTX error.
Anyone have any clue?
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
..
ok... I cleared the disk labels using dd. Hoa! That seems to have
fixed it allright!
Very weird. I was sure I zero'd the labels before I populated the disk,
but maybe not.
Thanks much! I was tearing my hair out on this one...
I've committed the disklabel patch, plus updated documentation for
disklabel.8, into 4.x.
Please report any problems directly to me.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers&qu
ly dedicated' disk label should at least
contain reasonable values -- be correct enough to pass BIOS muster.
I don't know enough about the partition format to know where the
BIOS calculation is failing.
-Matt
To Unsubscribe: send
Raw data on disk after 'disklabel -w -r da0 auto; disklabel -B da0 auto'
00f0 66 8b 46 08 52 66 0f b6 d9 66 31 d2 66 f7 f3 88 |f.F.Rf...f1.f...|
0100 eb 88 d5 43 30 d2 66 f7 f3 88 d7 5a 66 3d ff 03 |...C0.fZf=..|
0110 00 00 fb 77 44 86 c4 c0 c8 02 08 e8 40 91 88 fe |...wD
partition fails with some BIOSes ... it should be possible to fix it if
someone could track down what exactly is causing the divide-by-0 !
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ot file
is the default pxeboot with NFS support and the pxeboot.tftp was generated
by editing the /etc/make.conf file, setting the TFTP flag and recompiling
pxeboot. The files definately are different because I can change the DHCP
file to point to the other file and get different results at boot time.
NF
rite()n to and
instead is dirtied via the mmap, you will have a serious fragmentation
problem with the file. In order to avoid this problem any file appends
should occur using write() if possible, or the newly allocated space in
the file should be filled with zero's using writ
That was it. Updating the flash on the Intel NIC and she booted right up.
Thanks,
Matt
> -Original Message-
> From: Mathew KANNER [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 01, 2000 8:54 AM
> To: Matt Simerson
> Cc: '[EMAIL PROTECTED]'
> S
in the expire process. You can probably use MAP_NOSYNC safely in the
INND core, but don't use it to rebuild the history file in the expire
process.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
I'm going to take this off of hackers and to private email. My reply
will be via private email.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
:errr then keep me in the CC
:
:it's interesting
:
:--
: __--_|\ Julian Elischer
: / \ [EMAIL PROTECTED]
Sure thing. Anyone else who wants to be in the Cc, email me.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
ion. :)
:
:Nate
Heh. Well, I didn't think there'd be as much interest as there is,
so I guess I'll throw it back onto the mailing list.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
store rather then filling in holes.
Then rewrite the history file (e.g. 'cp'), and restart innd.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ng to flush the dirty pages, and to avoid the situation
where the filesystem runs out of space while trying to allocate backing
store, which will seg-fault the process.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubsc
es the rules a
little more reasonable for simple bug fixes like this you'll probably
get fried for doing it by bozos who have nothing better to do with their
time.
-Matt
:Index: phys_pager.c
:==
I wouldn't worry about madvise() too much. 4.2 has a really good
heuristic that figures it out for the most part.
(still reading the rest of your postings)
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscri
map
for (i = 0; i < 15; ++i) {
madvise(mapBase, mapSize, MADV_WILLNEED);
sleep(15);
}
munmap
close descriptor
}
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
301 - 400 of 616 matches
Mail list logo
