. and it's doing so simply to scan the history file
line-by-line
--
Darryl Okahata
darr...@sr.hp.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Hewlett-Packard, or of the
little green men that have been f
edly been
done since then. I've heard that it's "almost usable" (whatever this
means).
--
Darryl Okahata
darr...@sr.hp.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Hewlett-Packard, or of the
litt
I
find all this hand waving, venting of hot air, and attempted kicking of
hind parts rather boring. I've got better and often more enjoyable
things to do. For those of you who enjoy all this name-calling and
dirt-flinging, I've got one thing to say: grow up and get a life.
--
D
sk space (3 times if
> you include the original CVS archive).
--
Darryl Okahata
darr...@sr.hp.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Hewlett-Packard, or of the
little green men that have been fo
r loader, and complete overkill
> for such an application.
I'm curious: in your opinion, what is the purpose of Unix?
Personally, I'd much rather use a single OS for everything --
including word processing. I don't -- today -- but that's where I'd
like to be.
-
atenated devices), I saw pretty bad write performance with the
default filesystem frag size. Increasing the frag size (via newfs),
increased performance substantially.
--
Darryl Okahata
darr...@sr.hp.com
DISCLAIMER: this message is the author's personal opinion and does not
Greg Lehey wrote:
> On Friday, 18 June 1999 at 1:14:20 -0700, Darryl Okahata wrote:
>
> > Possible marginally-related data point: with the 3.1-RELEASE vinum,
> > and with striped drives (yes, I know the original user is using
> > concatenated devices), I saw pret
ontrolled hierarchy with lots of files. I'd really like
to put my MH mail messages under cfs, but I've got too many files (I
can't afford having a 200+MB cfsd).
The memory is not freed until you unmount (and then, the memory is
only free'd for use by other cf
y only paged in occasionally.
Well, yes. ;-)
However, on a somewhat aging 128MB laptop, a 200+MB cfsd puts the
system into swap h*ll pretty quickly. I think cfsd has some linked
lists which thrash a lot of pages.
--
Darryl Okahata
[EMAIL PROTECTED]
DISCLAIMER: this
rhaps?). I haven't looked into exactly why, and was largely lamenting
the insult after injury
--
Darryl Okahata
[EMAIL PROTECTED]
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technolog
ain hierarchy. The reason is that cfsd uses a 1024-entry hash table
at the top level; everything's a linked list below that (I think). Due
to the size of this table, cfsd will thrash the disk if the system goes
into swap.
I may play with bumping the table size up to 128K or so (I'm
fsd: 445MB 80-90MB
1024K bucket cfsd: 458MB 30-35MB (<20MB typ)
Of course, increasing the number of buckets increased the initial
cfsd size (to 14-16MB, in the case of the 1M buckets), but that's
acceptable.
[ And the cfsd process doesn'
ou must have enabled WOL on the motherboard.
That's it.
Now, you only have to send the special WOL packets to the system to
be woken up (someone's already mentioned the software, in another
posting, which also does not require any special driver support). I've
used both FreeBSD and Wi
seem to do that.
Yes, definitely (thanks for the addition!). Many older power
supplies cannot supply enough current on the +5VSB rail to support WOL.
--
Darryl Okahata
[EMAIL PROTECTED]
DISCLAIMER: this message is the author's personal opinion and does not
constitute the s
s in the English language. ]
I don't think you need *support* in the driver. What you do need is
for the driver/ACPI *bugs* to be fixed (any existing BIOS-configured
settings like WOL need to be preserved and not destroyed by the driver).
--
Darryl Okahata
[EMAIL PROTECT
27;t surprise me if it also affected
some version of NT.
--
Darryl Okahata
[EMAIL PROTECTED]
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been
ia an ampmeter
(although, as modern PC power supplies supposed are now supposed to be
power-factor-corrected, an ampmeter can give good results).
--
Darryl Okahata
[EMAIL PROTECTED]
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opin
er", but
that's a pale, feeble dust speck compared to purify (assuming that you
even manage to get checker working).
--
Darryl Okahata
[EMAIL PROTECTED]
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Te
", instead.
For USB hard disks, at least (which may also apply to cameras), you also
need to be running a pretty recent version of -STABLE; I'm pretty sure
that 4.5-RELEASE can't be used (which is what you're using). I know
that a -STABLE of around mid-February will *NOT* w
ade to the
latest FreeBSD-STABLE.
--
Darryl Okahata
[EMAIL PROTECTED]
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.
To Unsubscribe
have are:
* USB not functional on a laptop after a resume (being worked on in
-current, I see).
* Intermittent, "umass0: Phase Error, residue = 8192", hangs when
transferring "large" amounts of data (~10MB-30MB). I'm hoping that
this isn't an hardware problem.
. and it's doing so simply to scan the history file
line-by-line
--
Darryl Okahata
[EMAIL PROTECTED]
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Hewlett-Packard, or of the
little green men that have been fo
bit has supposedly been
done since then. I've heard that it's "almost usable" (whatever this
means).
--
Darryl Okahata
[EMAIL PROTECTED]
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or polic
f the things mentioned about how Linux was better than FreeBSD, was,
um, the "development process" (and my words are much more charitable
than his). Looking at the current flamefests, and thinking about what
was said by the Major Linux Personage, I'd have to say that there's
ing thread, you can look up on the archives to read
> how it goes.
And how is the newbie supposed to know this, if no one tells them?
Also, telling them via insults and the like is, well, rude.
> Basically, the person doesn't like the present
> behavior, and would like
Wes Peters <[EMAIL PROTECTED]> wrote:
> Darryl Okahata wrote:
> >
> > ... however, how the H*LL are the clueless newbie hordes supposed
> > to know or learn this? As much as we'd like them to be, they're not
> > exactly born with this knowledge,
7;s confusing, actually), perhaps not.
[ And, yes, I'm more than willing to submit proper docbook patches, if
they'll be made available to newbies (e.g., on the web page FAQ)
within a reasonable amount of time. ]
--
Darryl Okahata
[EMAIL PROTECTED]
DISCLAIMER: this
h it can be comparable to
grep in some cases.
I've got mixed feelings about global. On the one hand, you can't
beat it for locating where a function is defined, and it's very good at
showing where a variable is used. However, for best results, you have
to remember to use different
670+/usr/local/www/db/text/1999/freebsd-hackers/19991017.freebsd-hackers
Side note: Shigio Yamaguchi <[EMAIL PROTECTED]> has found some issues
and bugs regarding GLOBAL, and so GLOBAL is not as bad as the article
makes it out to be.
--
Darryl Okahata
[EMAIL PROTECTED]
DISCLAIMER
few people appear to have this problem (I
appear to be the only one). If you want to see what I did, see:
http://www.freebsd.org/cgi/getmsg.cgi?fetch=116906+120859+/usr/local/www/db/text/1999/freebsd-mobile/19991107.freebsd-mobile
--
Darryl Okahata
[EMAIL PROTECTED]
DI
> memory is the best and fastest way out of these situations. Unless
I'll second this. I've had memory problems in the past, and every
memory checker I used said that the memory was good. Only by swapping
out the bad memory (I don't have access to an hardware memory
the time, sorry).
--
Darryl Okahata
[EMAIL PROTECTED]
http://web.sr.hp.com/~darrylo/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
32 matches
Mail list logo
