On Wed, Jan 30, 2002 at 01:47:24PM +, Mark Murray wrote:
No. We dont. But if Kerberos5 is asked for, then BSD telnet is linked
against Heimdal.
I'm testing the fix, and will commit in a day or two.
OK, great. I assume you'll import it on the vendor branch?
Yup!
M
--
o
@@
.\ Copyright (c) 2001 Mark R V Murray
.\ All rights reserved.
+.\ Copyright (c) 2002 Networks Associates Technologies, Inc.
+.\ All rights reserved.
+.\
+.\ Portions of this software were developed for the FreeBSD Project by
+.\ ThinkSec AS and NAI Labs, the Security Research Division
and not in contrib/opie. If you care about
machine independance, better use opielookup() directly.
No, that is OK. :-)
The FreeBSD PAM modules are all written from scratch as BSD PAM modules.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
automated scripts processing.
I have idea to solve it adding no_fake_prompts option to pam_opie to
control that per admin choice.
Yes. That would be a good move. :-)
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail
.
I believe pam_get_pass() should set PAM_AUTHTOK. Any objections?
Not from me :-)
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Here are the (hopefully) final patches. Any final objections before I
commit the lot?
According to EyeBall Mk1, this is fine! :-)
I haven't extensively tested the code, but the methods used and the
design are very sound, I believe.
M
--
o Mark Murray
\_ FreeBSD Services Limited
) = pwd-pw_expire)
+ retval = PAM_AUTH_ERR;
}
else {
--
Andrey A. Chernov
http://ache.pp.ru/
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
';
if (suser_override)
--
Andrey A. Chernov
http://ache.pp.ru/
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
, response, sizeof resp);
/*
* Opieverify is supposed to return -1 only if an error occurs.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
o Mark Murray
\_ FreeBSD
On Sun, Jan 20, 2002 at 19:47:55 +, Mark Murray wrote:
Do you mean that at at the very edge of password expiry, the user may
still be able log in (maybe some seconds later)? If so this is not a
credible threat.
Yes. Few seconds can be few hours or more in case network is down
On Sun, Jan 20, 2002 at 19:55:31 +, Mark Murray wrote:
This works, but strikes me as overkill. This is salt, not cryptographic
randomness, so 'srandom(junk)' is most likely better as a replacement
for srandomdev() (where 'junk' can be time(), pid or anything similar).
You can't
code that cares about the state should do the same.
True but not trivial. I'd be happy to commit working patches :-)
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
On Sun, Jan 20, 2002 at 23:14:13 +, Mark Murray wrote:
The PAM OPIE may only do OPIE authentication. It is entirely up to the
PAM stack to decide what the login policy is.
(Well, the PAM stack as specified by the pam configs in /etc/pam*)
Yes. And to allow PAM stack to make
On Sun, Jan 20, 2002 at 23:44:44 +, Mark Murray wrote:
Yes. And to allow PAM stack to make right decision, pam_opie pass special
information to PAM stack. Look at the patch, pam_opie not breaks from the
stack by yourself, it is /etc/pam* do that using information from
pam_opie
for modules which
have no authentication (like say, pam_motd, which prints /etc/motd
during the pam_session_open() phase). IGNORE may have other uses,
but I can't remember them offhand.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
will not change
_at_all_.
There will be no SRA unless you install secure/ telnet.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
! This will make src/crypto mandatory
if you want telnet(d). This will _not_ make crypto _use_ mandatory.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
Well, it would seem that the cu upgrade has totally hosed cu now:
# cu -l /dev/cuaa1 -s 9600
usage: tip [-v] [-speed] [system-name]
Can we get this fixed please?
Yes.
Import coming.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
There is already a patch in PR ports/30899. It is OK to commit it
IF you can test it first on a FreeBSD 4.x system (any architecture)
and also a -current Alpha system.
Cool! Thank you!
M
John
Mark Murray wrote:
John
I have a patch (courtesy of Brian Somers) that fixes M3. I
Erm, it _is_ fixed in the makefile. If you have a better method, lets hear
it. :-)
Back out the entire tip commit? This would also restore all the FreeBSD
changes clobbered by it. It doesn't even compile cleanly:
Entirely different problem.
M
--
o Mark Murray
\_ FreeBSD
] Sunbay Software AG,
[EMAIL PROTECTED]FreeBSD committer,
+380.652.512.251 Simferopol, Ukraine
http://www.FreeBSD.orgThe Power To Serve
http://www.oracle.com Enabling The Information Age
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
I have installed application software from port collection . How do I
make un-install ? If I want to upgrade the existing application , how do I
upgrade them ? Please advise
Please ask this question on [EMAIL PROTECTED]
M
--
o Mark Murray
\_ FreeBSD Services Limited
O
cp='cp -i'
alias mv='mv -i'
alias rm='rm -i
Another question , what is the function of PS2 and when to use it ? Please
advise
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
o Mark Murray
\_ FreeBSD
Mark, please back your 1.32 revision from share/examples/Makefile out,
Done.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
:-).
Actually, it is possible for there to be no copies: target in
src/share/examples/something. The copies: (actually copies::)
target is built up in a .for loop that may be empty.
The fix is a dummy copies:: target.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig
Forgot to mention, I had to make kcheckpass setuid root to make kcheckpass
itself work (just verified this on -stable).
Yes - this is documented. :-)
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL
in /usr/src/kerberos5/libexec.
*** Error code 1
Stop in /usr/src/kerberos5.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
Should I file a PR?
No. I have this :-)
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
It seems that we dont have a /usr/lib/pam_rhosts_auth.so.
Yes - I need to write one.
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
-v_interlock);
I get exactly the same thing.
Manual bactrace is:
panic
witness_unlock
_mtx_unlock_flags
vop_nolock
vop_defaultop
vn_lock
ffs_mountfs
ffs_mount
vfs_mountroot_try
vfs_mountroot
mi_startup
begin
M
--
o Mark Murray
\_ FreeBSD Services Limited
O.\_Warning: this .sig is umop ap
if opiechallenge() is
failed.
I don't know how it should work with OPIE. Could you please fixing
this, Mark?
Sure! I've never used rexecd, su could you please suggest a minimalist
test/command that I could use, and I'll get right to it. :-)
M
--
o Mark Murray
\_ FreeBSD Services
Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
the correct root FS))
If I undef acpi_load at boot, the system boots fine.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
As far as I can tell, there's nothing in the tree which uses libss any
longer, and hasnt been for quite some time. Is there any reason to
keep it?
Nope.
Right. Kill it.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
at
a later stage.
I have already asked for reviews on -audit. Those who are looking at my
patches should download again, because I have done some further fixes
and improvements.
I'll commit in three days from the date of this email if nothing comes
up.
M
--
Mark Murray
Warning: this .sig is umop ap
Does anyone know what changed?
(someone has suggested the change came about when PAM's session model was
changed)
Following up on my previous message; I've asked re@ for permission
to MFC the fix.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL
I need to MFC login(1) some more. Please try that, and if it
works, lets get it committed.
STABLE's PAM modules and support are quite a bit behind CURRENT's.
What are your /etc/pam.conf entries for login? See if borrowing
any CURRENT entries helps you.
M
--
Mark Murray
Warning: this .sig
According to Mark Murray:
Can you make it so that if NO_OPENSSL is not defined, then openssl is used?
I could of course but I don't think that having PUBKEYS by defaults (X.509
based, not the PGP ones) is probably not very useful yet as it is a fairly
recent option.
AUTOKEY should
an optional component.
I'm a bit reluctant to force openssl for just ntpd.
Can you make it so that if NO_OPENSSL is not defined, then openssl is used?
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
hope, before PAM use in su
is MFC'd.
I have just entered a PR on this.
cc'd to: markm
Joshua
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
.
Xwrapper
I'm not sure I follow you here...
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Why? Better way will be rewritting ports to use good-new OPIE.
wi-ftpd already have OPIE hooks, but I not sure they works. Popper needs
modifications. Doesn't know, if other ports using Skey exists.
I can do base software, but I haven't time to fill all ports.
M
--
Mark Murray
Warning
no water - the BSD books that I have point to MH and
Emacs in the same way.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
I've noticed that new PAM segfaults when I'm typing non-existing login
at console login prompt. Please fix.
This current, right? I'll sort it out. Thanks for the debug-sleuthing!
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED
: 7bit
Content-Disposition: inline;
filename=misc_conv.c.diff
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Is there any plan to port pam_ldap ( and nss_ldap )
to FreeBSD-CURRENT ?
No plans, but if you submit something, I would be interested.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
Hi
Those who made a buildworld without NO_PERL=true with sources
newer than Tue, 1 May 2001 02:25:25 -0700 (PDT), but older than
2001/05/02 14:18:33 PDT, must apply the following patch as root in
/usr/libdata/perl/BSDPAN directory.
(If you are tracking CURRENT, then CVSup and/or cvs update
was one).
Those patches of yours look reasonable.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
. For one, KERBEROS is no
longer needed. (fixed locally). WHEELSU needs to be properly documented.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
I update 4.3 RC to 5.0-CURRENT and have some troubles.
Why make buildworld build system without RSA support ?
And how i can correct this problem ?
System cvsuped today.
Go to /dev and remake all your devices.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail
stuff was disabled?
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
itself moan at you.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
pam_unix.so try_first_pass
sshdaccount requiredpam_unix.so
sshdpassword required pam_permit.so
sshdsession requiredpam_permit.so
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubs
in the ports. They may just work for you.
It shouldn't be too difficult to set up the other side - after all, there
is a need :-)
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
be able to do it with SSH (assuming that you can get out with
ssh!)
$ ssh -v -l yourname otherhost.example.com -L5559:cvsup.example.com:5559
Then doing a cvsup with the server set to 127.0.0.1 will work.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL
; with a tag on it to indicate that it is going
through the release engineering process to become 4.3-RELEASE (and
then 4.3-STABLE).
You have something that is stable, and is just close to the next
release.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTEC
It seems the compatibility with the previous minor of urandom has
been silently removed (I assume this happened with the last
update/cleanup of the random device). It took me two hours to figure
it out.
See src/UPDATING 2624
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
.sys.burst is still available for those very slow,
very high interrupt cases.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
R, "rndslp", hz/10);
+ if (harvestring.tail != harvestring.head) {
/* Suck the harvested entropy out of the queue and hash
* it into the appropriate pool.
*/
--
Mark Murray
Warning: this .sig is umop ap
.
Matt,
At it is very obvious to me that you have not even looked at the new
code, let alone run it, I suggest that you do both before further
engaging in this conversation.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe fr
they can get, and this method gives them that while allowing others
to throttle the harvester back.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
code does that. Do a "cat /dev/zero /dev/random"
to see it in action.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
if
97
98 for (pl = 0; pl 2; pl++)
99 yarrow_hash_init(random_state.pool[pl].hash, NULL, 0);
100
101 for (;;) {
Is DEBUG defined?
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsu
to tie down where this is
happening.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
maxusers to 128, and time a make world with interrupt
harvesting on, and again with it off.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
e not been keeping records, but
an overnight build has not yet progressed into my breakfast).
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
tweaking the "Computational intensity factor" ;-) by dropping
the kern.random.yarrow.bins:
# sysctl -w kern.random.yarrow.bins=2
And let me know how well that works.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
, and any overflows are discarded.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
320 seeds per second. Still overkill, but at least not the massive
overkill that its doing now.
Event != seed. I'll juggle numbers and see if I can come up with any
tweakables (sysctl's) that could give users more control here.
Thanks!
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
I reported it about a month ago, but the problem still persists. 5-current
buildworld can't be performed on reasonably recent 4-stable system, hence
source upgrade path from -stable to -current is broken. Please fix.
I just did this on 4-STABLE with no problems at all.
M
--
Mark Murray
Please review this patch as I'd like to commit it soon. Also, I'm not
100% sure what to do about libdes.so.3, so if you have commments on
that please let me know. Other than that, the patches should be close
to commitable.
Now is the time to toss that into compat/
M
--
Mark Murray
of a kernel dating to sun 4th feb. The PPro is
rock-stable. The PentiumMMX is very fragile, and will panic easily
(often in vm_fault) with a sig9 (IIRC).
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" i
Hi
Please review the patch at http://people.freebsd.org/~markm/no_lock_h.diff.
the idea is to remove sys/*/include/lock.h.
I tested it with the usual i386 stuff, and it is known to break the cy
driver because of the COM_(UN)LOCK macros (which is another issue).
M
--
Mark Murray
Warning
known about this for a good couple of months. I
can't remember specifically _how_ I know; suffice to say there has
been a fair bit of dialogue on the lists and Jason's progress-page
has a good overview.
http://people.freebsd.org/~jasone/smp/
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
EMAIL PROTECTED]X AGAINST HTML MAIL
http://freebsd.org.ru/~osa/ / \
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send
(LocalHostName, '.')) != NULL) {
+ *p++ = '\0';
+ LocalDomain = p;
+ } else
+ LocalDomain = "";
/*
* Close all open log files.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current"
On Sat, Jan 20, 2001 at 11:24:16AM +0200, Mark Murray wrote:
I don't agree with this change.
hostname != name-that-IP-address-resolves-to.
Dunno what you are talking about. That has nothing directly to do with
this. No one is talking about forcing you to change your hostname
on a 2xPII/350, 256M, two scsi disks on ahc, and ccd I have three times
now hung the machine so that only reset got any attention simply by
make -j 128 world
Do you have an easy way to narrow it down to CCD by doing the same
thing but without ccd involvement?
M
--
Mark Murray
kern.random.yarrow.bins=2
makes a difference for you.
Thanks!
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Murray wrote:
This is directly traceable to entropy harvesting by /dev/*random.
I know it's not an option if you need to use ssh, but not loading
random.ko will fix the sound problems when moving the mouse or
typing. It doesn't fix the 'hwptr went backwards' messages, though.
Please
Hi John
There seems to be same breakage in the atomic stuff:
link_elf: symbol atomic_load_acq_int undefined
KLD file random.ko - could not finalize loading
I back out the latest commit to sys/i386/include/atomic.h, and things
work a bit better (on my laptop).
M
--
Mark Murray
Warning
device's readable
oscillator, set to generate a noise waveform).
Slight overkill, when the TSC register is already used and deliberately
underestimated to improve randomness quality.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubs
I'm happy to accomodate folks, but the constant lack of concensus
combined with extreme positions is wearing a bit thin.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
with a crazy
MAC address, and then doesn't work. It doesn't even go UP.
MAC=00:00:80:00:00:80, FWIW.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
was recently added to -current and maybe it's had a strange effect on
makedepend or something
There was a make(1) problem a couple of weeks back. Resup, make-and-install
make(1), and you should be OK.
Dunno why, but ntp(d) tickled the bug.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
to
ensure a clean start there and started a buildworld. Six hours later,
=== usr.sbin/ntp/ntpd
Killed
Read what I said!!
Make-and-install _make_ (not anything else) first.
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED
ot; in the body of the message
:
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
PROTECTED] |
| http://peorth.iteration.net/~keichii | Yes, BSD is a conspiracy. |
+--+
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-audit" in the body of the message
--
Mark Murray
War
s) is:
panic
zerror
zfreei
NDFREE
nfsrv_lookup
nfs_nfsd
nfssvc
syscall(2f, 2f, 2f, 1, 0)
xint0x80
NFS activity (not mounting) triggers it. The panic happens on the
server box, which is a dual-cpu i386 class running an SMP kernel.
What else do you need?
M
--
Mark Murray
Warning: this
On Tue, Dec 26, 2000 at 02:00:54PM +0200, Mark Murray wrote:
I'm getting a reliable panic on CURRENT (2000/12/26) with INVARIANTS
set. I suppose I could "fix" this by taking out INVARIANTS, but it
seems to make more sense to try to get it fixed.
Do you have NF
to receive mail from all three of those
user-classes, because of the "direct-to-MX" spam issue. The solution
is to use your ISP's SMTP "smarthost" for your mail.
See http://mail-abuse.org/dul/
/OFFTOPIC
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe:
?
Thanks,
Pete...
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
et written at
shutdown. Are you fully up to date with your mergemaster(1)ing?
Now I use "init 0" for shutdown and "init 6" for reboot.
That is a bug if you are up to date. However, it is beyond my ken to fix.
M
--
Mark Murray
Join the anti-SPAM movement: http://www.cauce.o
301 - 400 of 743 matches
Mail list logo
