Sorry about the message format. Someone else complained before I had a
chance to see how it was set. It should be set to plain text now. Sorry
When I was using cvsup I was allowing cvsup to edit already placed source
code. So on Friday Morning, I deleted all my cvs source code and cvsup all
On Friday, 14th July 2000, "Rodney W. Grimes" wrote:
I suspect an interaction between the ATA driver and VIA chipsets,
because other than the network, that's all that is operating when I see
the underruns. And my Celeron with a ZX chipset is immune.
I've seen them on just about everything,
5. If you are using CTM to receive the "*,v" files and then using
the "cvs" command to check out your source tree, then I don't know
whether you need to delete your ",v" files and replace them or not.
You do need to delete your ,v files in this case (only for the crypto
dirs).
M
--
Mark
In article [EMAIL PROTECTED]
[EMAIL PROTECTED] writes:
sada2000/07/15 07:59:02 PDT
Modified files:
bin/mv mv.c
Log:
To make inherit file flags when mv(1) moves file between directories
on different file systems.
PR:bin/12375
On Fri, Jun 23, 2000 at 08:36:32AM +0200, Mark Murray wrote:
Building world failed on my machine... (with USA_RESIDENT=NO)
Does IDEA stuff compiled by default?
I messed this up. Fix coming.
Something seems to be wrong with the logic concerning IDEA stuff.
I ask because I can't build the
With a recently (10:00 BST) cvsup'd and built world / kernel:
last pid: 288; load averages: 0.05, 0.04, 0.01up 0+00:03:27
15:53:02
32 processes: 1 running, 31 sleeping
CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100%
idle
Mem: 282M Active, 17M Inact, 20M
This is possible /usr/src/UPDATING entry:
2716:
mtree now NOT follows symlinks by default, old behaviour restored to be
compatible with rest of *BSD camp. New -L option added to follow
symlinks. This require manual mtree rebuilding before 'make world'
--
Andrey
...any time soon? It's been in current since 3/16 so it would seem MFCable,
but what do I know. Nick? (I run 4-stable and don't plan to run -current
any time soon, _and_ I want to buy a Rio 500, but not if I can't hook it to
FreeBSD.)
Sent to both -current and -stable as both lists seem
I found that I always got the same fortune quote after reboot, over and over
again. It means that /dev/random produce exact the same values after reboot.
It means that machine timer or keyboard not used for enthropy gathering.
Using keyboard alone not helps for automatic tasks because it can be
On Friday, 14th July 2000, "Rodney W. Grimes" wrote:
I suspect an interaction between the ATA driver and VIA chipsets,
because other than the network, that's all that is operating when I see
the underruns. And my Celeron with a ZX chipset is immune.
I've seen them on just about
Also sprach Andreas Klemm ([EMAIL PROTECTED]):
I'm using -current of yesterday and tcsh.
When installing a FreeBSD port and I interrupt a "make all install clean"
session, when make is in the "make fetch target", the fetch process isn't
killed and continues to run alone although the "make"
Thus spake Alfred Perlstein ([EMAIL PROTECTED]):
http://people.freebsd.org/~alfred/pxe/
Nice article!
I think that's worth going into the handbook, after you reworked the
things you talked about :)
Alex
--
cat: /home/alex/.sig: No such file or directory
To Unsubscribe: send mail to
I found that I always got the same fortune quote after reboot, over and over
again. It means that /dev/random produce exact the same values after reboot.
It means that machine timer or keyboard not used for enthropy gathering.
Using keyboard alone not helps for automatic tasks because it can
At 9:25 PM -0700 7/14/00, Thomas D. Dean wrote:
How would this work with printers on local networks?
Say, a print server 192.168.1.73?
If you do not have a special DNS entry for that printer,
then this new synthetic-printcap option would do nothing
for you. In other words, you would continue
At 12:09 AM -0400 7/15/00, Louis A. Mamakos wrote:
I almost hate to bring this up, but I think the unnamed-here
proposed replacement for our lpd allows you to set your PRINTER
environment variable to something like
[EMAIL PROTECTED]
louie
For what it's worth, I think that feature is a
I found that I always got the same fortune quote after reboot, over and over
again. It means that /dev/random produce exact the same values after reboot.
There were some special instructions for the new random device:
2) If you do not have the randomdev module loaded, ssh will
fail in
On Sun, Jul 16, 2000 at 08:26:44PM +0200, Mark Murray wrote:
Gotcha - fix coming; I need to stash some randomness at shutdown time, and
use that to reseed the RNG at reboot time.
... and for installations where ssh-keygen is run the first time
the system boots?
--
Bill Fumerola - Network
On Sun, Jul 16, 2000 at 08:26:44PM +0200, Mark Murray wrote:
Gotcha - fix coming; I need to stash some randomness at shutdown time, and
use that to reseed the RNG at reboot time.
... and for installations where ssh-keygen is run the first time
the system boots?
The situation is
On Sun, Jul 16, 2000 at 09:42:29PM +0200, Mark Murray wrote:
On Sun, Jul 16, 2000 at 08:26:44PM +0200, Mark Murray wrote:
Gotcha - fix coming; I need to stash some randomness at shutdown time, and
use that to reseed the RNG at reboot time.
... and for installations where
Recently, when building a kernel (about 20 minutes as of this email),
I set
NO_MODULES= false
in /etc/make.conf. The modules still weren't built with the kernel.
- Donn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
I found that I always got the same fortune quote after reboot, over and over
again. It means that /dev/random produce exact the same values after reboot.
It means that machine timer or keyboard not used for enthropy gathering.
Using keyboard alone not helps for automatic tasks because it can
Donn Miller wrote:
Recently, when building a kernel (about 20 minutes as of this email),
I set
NO_MODULES= false
in /etc/make.conf. The modules still weren't built with the kernel.
The value is normally unimportant, thus NO_MODULES=false ==
NO_MODULES=true == ...
To enable
On Sun, 16 Jul 2000, Mark Murray wrote:
On Sun, Jul 16, 2000 at 08:26:44PM +0200, Mark Murray wrote:
Gotcha - fix coming; I need to stash some randomness at shutdown time, and
use that to reseed the RNG at reboot time.
... and for installations where ssh-keygen is run the first
On Sun, 16 Jul 2000, Andreas Klemm wrote:
Something seems to be wrong with the logic concerning IDEA stuff.
I ask because I can't build the security/p5-Net-SSLeay port anymore
which is for example needed for webmin.
Compare r1.2 of /usr/src/crypto/openssl/crypto/evp/evp.h with r1.4.
Kris
On Sun, 16 Jul 2000 11:41:37 -0700 (PDT), "Rodney W. Grimes"
[EMAIL PROTECTED] said:
Ohh... and a finally note, DEC blew the chip design by only including
a 160byte threshold point given that PCI 2.0 spec says it should have
been 500bytes!!
It wouldn't be the first thing DEC had screwed up
On Sun, 16 Jul 2000 16:46:58 -0400, Christopher Masto [EMAIL PROTECTED] said:
Huh? Security through ignorance?
Remember that `lpr' is setuid-root and uses a ``privileged'' port for
its communications. Many sites may still be using trusted-host
``authentication'' internally, and LPRng's
In article 000c01bfeef3$8c71b8f0$[EMAIL PROTECTED],
Tony Johnson [EMAIL PROTECTED] wrote:
So on Friday Morning, I deleted all my cvs source code and cvsup
all new copies from scratch. I did a make world and the compile
finished successfully.
Whew, you had me worried for awhile there.
On Sun, 16 Jul 2000 11:41:37 -0700 (PDT), "Rodney W. Grimes"
[EMAIL PROTECTED] said:
Ohh... and a finally note, DEC blew the chip design by only including
a 160byte threshold point given that PCI 2.0 spec says it should have
been 500bytes!!
It wouldn't be the first thing DEC had
On Sun, 16 Jul 2000 11:41:37 -0700 (PDT), "Rodney W. Grimes"
[EMAIL PROTECTED] said:
Ohh... and a finally note, DEC blew the chip design by only including
a 160byte threshold point given that PCI 2.0 spec says it should have
been 500bytes!!
It wouldn't be the first thing DEC had
any reason that we should be seeing these now:
mfs_badop[vop_getwritemount]
mfs_badop[vop_getwritemount] = 45
mfs_badop[vop_getwritemount]
mfs_badop[vop_getwritemount] = 45
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Sun, 16 Jul 2000 11:41:37 -0700 (PDT), "Rodney W. Grimes"
[EMAIL PROTECTED] said:
Ohh... and a finally note, DEC blew the chip design by only including
a 160byte threshold point given that PCI 2.0 spec says it should have
been 500bytes!!
It wouldn't be the first thing DEC had
On Sun, Jul 16, 2000 at 08:15:05PM -0400, Garrett Wollman wrote:
On Sun, 16 Jul 2000 16:46:58 -0400, Christopher Masto [EMAIL PROTECTED] said:
Huh? Security through ignorance?
Remember that `lpr' is setuid-root and uses a ``privileged'' port for
its communications. Many sites may still
On Sun, 16 Jul 2000, Mike Smith wrote:
The problem is that the randomdev stuff should be a delete option, ie. it
should be built as part of the kernel unless EXPLICITLY excluded, not the
wrong way around as it is at the moment.
Exactly, randomdev should be compiled-in by default.
Christopher Masto [EMAIL PROTECTED] writes:
On Sun, Jul 16, 2000 at 08:15:05PM -0400, Garrett Wollman wrote:
On Sun, 16 Jul 2000 16:46:58 -0400, Christopher Masto [EMAIL PROTECTED] said:
Huh? Security through ignorance?
Remember that `lpr' is setuid-root and uses a ``privileged''
¨ßÅƤI
ij¢¾æ`B
ÈñÆAu¶Gb`vª©êéæB
µ©àA^_È̾B
Ðï×̽ßÉ©Ä¿åB
http://216.101.214.74/LoveLovePussyKing/index-namasex.html
»ê¶áAܽË[B
ä©è
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the
Hi All,
I just did something foolhardy -- and yet instructive. Pls let
me relate.
As I had polluted my system with an unstable recent CURRENT, I
decided to rebuild from a more stable CURRENT. I (eventually)
choose "cvs co -D 2000.06.21.04.00". Works great.
Given the difficulty in finding
36 matches
Mail list logo
