On Mon, Mar 10, 2003 at 10:44:34 -0500, Mike Barcroft wrote:
Andrey A. Chernov [EMAIL PROTECTED] writes:
Many programs (from ports too) defines _ISOC99_SOURCE to get C99
functions, but we don't sense this define currently. Here is the fix for
review:
Cool. I didn't realize
199506L
#define _XOPEN_SOURCE 500
#define _LARGEFILE64_SOURCE 1
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
, and insecure.
Usually applications we build (like awk, etc.) could be fixed by simple
one line change:
srand(something) - sranddev()
It completely eliminates first value correlation problem.
--
Andrey A. Chernov
http://ache.pp.ru/
msg52685/pgp0.pgp
Description: PGP signature
. It is common and know problem for all mod-type
PRNGs. There is even good methods exists to eliminate this thing, see
http://www.physik.uni-giessen.de:8081/PhysOfFinance/PoF09.pdf
Shuffling Algorithm section for example. But all such methods will be
incompatible with rand_r()...
--
Andrey
On Sun, Feb 16, 2003 at 11:01:43 +0100, Dag-Erling Smorgrav wrote:
Andrey A. Chernov [EMAIL PROTECTED] writes:
[...]
Please disregard. Andrey does not know what he's talking about and
ignores any attempt at explaining what the real issue is and what real
users want.
Unless you specify
On Sun, Feb 16, 2003 at 13:27:38 +0300, Andrey A. Chernov wrote:
Unless you specify exact details of what I ignore, I'll be forced to
treat your reply as NO REVIEW and commit this changes.
Well, after numerous exchanges of nonsense messages a bit of details comes
from des, so I correct my
On Sun, Feb 16, 2003 at 11:58:57 +0100, [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED], Andrey A. Chernov writes:
On Sun, Feb 16, 2003 at 13:27:38 +0300, Andrey A. Chernov wrote:
Unless you specify exact details of what I ignore, I'll be forced to
treat your reply as NO REVIEW
On Sun, Feb 16, 2003 at 12:06:36 +0100, Dag-Erling Smorgrav wrote:
Andrey A. Chernov [EMAIL PROTECTED] writes:
Admins with no /etc/opieaccess AFFECTED!
Admins with no /etc/opieaccess IDIOTS for not running mergemaster!
First of all, there are many years of existen OPIE administration
.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
and completely ignoring what I say
I not bombarding you, I answer sequentally on each message and many of
them comes when I write answer.
About ignoring, I see situation, like you ignore me. BTW, do you ever
think that bombarding and ignoring terms can't co-exist, they are
oppisite?
--
Andrey
On Sun, Feb 16, 2003 at 12:06:36 +0100, Dag-Erling Smorgrav wrote:
Andrey A. Chernov [EMAIL PROTECTED] writes:
Admins with no /etc/opieaccess AFFECTED!
Admins with no /etc/opieaccess IDIOTS for not running mergemaster!
Moreover, admins WITH old /etc/opieaccess (i.e. without your line
users and admins to rewrite their
OPIE apps under new PAM framework. I always believe that non-destructive
for OPIE defaults (i.e. PAM only) solution is possible here, but not
being PAM specialist, can't demonstrate it. Recent des commits solve
problem correctly.
--
Andrey A. Chernov
http
handling.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Mon, Feb 17, 2003 at 01:51:20 +0300, Andrey A. Chernov wrote:
properly). If you tune opiezed+pamified apps to work as you need, pure
opized stops working and vice versa.
In this phrase I mean documented OPIE tuning of OPIE config files (old
way), without any new additions and requirements
already resolved, des commits acceptable for both parties
solution (which use part of my patch too).
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Sun, Feb 16, 2003 at 20:57:29 -0800, Kris Kennaway wrote:
On Sun, Feb 16, 2003 at 07:52:35PM -0800, Andrey A. Chernov wrote:
So, monotonically increased seed-first value correlation problem remains...
I think we should commit this patch (to -current) and fix all the
problems that pop
formulae generates acceptable quality numbers. Unlike in old
variant (which generates bad quality ones), the only problem remains is
first value monotonically increased with the seed.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd
)
- rhost = localhost;
+ if (rhost == NULL || strcasecmp(rhost, localhost) == 0)
+ rhost = ;
if (opieaccessfile(rhost) != 0 opiealways(pwent-pw_dir) != 0)
return (PAM_SUCCESS);
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL
On Sun, Feb 16, 2003 at 04:41:58 +0300, Andrey A. Chernov wrote:
des tries to fix OPIE config to add
additional things here not needed by standard OPIE setup at all.
To be more specific, exact breakage after des is:
Old non-PAMified OPIE variant: localhost allowed even there is no
/etc
.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
and doesn't support MNT_UPDATE.
I mean not right now situation, but it could fixed to handle them.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
-mounted as read-write after adjkerntz started, in the same manner as /
remounted read-write, i.e. with mount -u ?
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
into kernel. And for which reason? Only to heal DEVFS timestamps? Mount
workaround looks more light-weighted.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Thu, Feb 06, 2003 at 11:27:36 +0100, [EMAIL PROTECTED] wrote:
In message [EMAIL PROTECTED], Bruce Evans writes:
On Thu, 6 Feb 2003, Andrey A. Chernov wrote:
On Wed, Feb 05, 2003 at 23:44:08 +0100, [EMAIL PROTECTED] wrote:
2) Feb 6 01:36 (boot time)
3) Feb 6 04:36 (+3 TZ future
if there is any way to find the information they store and I don't
think such features are widespread.
I saw this too, but it is totally useless, even M$ can't handle such
BIOSes.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
operator 104, 0 Feb 5 22:34 xpt0
crw-rw-rw- 1 root wheel 2, 12 Feb 5 22:34 zero
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
standard /etc/wall_cmos_clock knob. It there any chance that
DEVFS comes up in the middle? If yes, is there any ideas for workaround?
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
108, 2 Feb 6 00:48 usb2
lrwxr-xr-x 1 root wheel3 Feb 6 00:48 vga - ttyv0
crw-rw-rw- 1 root wheel 2, 12 Feb 6 00:48 zero
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
1970 usb2
lrwxr-xr-x 1 root wheel3 Feb 6 01:36 vga - ttyv0
crw-rw-rw- 1 root wheel 2, 12 Jan 1 1970 zero
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
.
Clock jump happens as it supposed when adjkerntz(8) corrects machine clock
back to GMT via various CPU_* sysctl's. Could touched DEVFS stamps be
fixed back to something useful in the same sysctl code too?
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED
there?
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Tue, Feb 04, 2003 at 12:46:59 +0300, Andrey A. Chernov wrote:
Returning to current algorithm, I am interested in good NSHUFF value in
the range 100-2000. Do you have any findings there?
Apparently 100 is not enough too, I see repeated pattern in your
program. I'll try other values
On Tue, Feb 04, 2003 at 12:46:59 +0300, Andrey A. Chernov wrote:
So, if you define USE_WEAK_SEEDING and re-compile rand.c, you'll get even
worse results from your test. It means current variant is better then
previous. If you know even better algorithm wich pass restrictions above,
just tell
On Tue, Feb 04, 2003 at 12:58:40 +0300, Andrey A. Chernov wrote:
On Tue, Feb 04, 2003 at 12:46:59 +0300, Andrey A. Chernov wrote:
Returning to current algorithm, I am interested in good NSHUFF value in
the range 100-2000. Do you have any findings there?
Apparently 100 is not enough too
not too hopeful about 2000. I appeal to Asimov's
zero, one, infinity law.
I found that f.e. 50 is worse than 100, but 200 isn't better. 100 is
better than 0 because remove monotonically increased sequence.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED
On Tue, Feb 04, 2003 at 15:07:30 +0300, Andrey A. Chernov wrote:
On Tue, Feb 04, 2003 at 03:52:37 -0800, David Schultz wrote:
You can do better than the present generator with 32 bits of state.
See the following page by Neal Wagner (not to be confused with David Wagner):
http
/laws/rng.html
The attached patch, based on one of the m/k pairs suggested on that
page, results in the following:
I just think about 62089911 and 48271 too :-)
There is one bug in your patch: 0 is still illegal, so my fix required.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send
On Tue, Feb 04, 2003 at 16:10:06 +0300, Andrey A. Chernov wrote:
On Tue, Feb 04, 2003 at 14:00:27 +0100, Dag-Erling Smorgrav wrote:
David Schultz [EMAIL PROTECTED] writes:
You can do better than the present generator with 32 bits of state.
See the following page by Neal Wagner
On Tue, Feb 04, 2003 at 16:17:48 +0300, Andrey A. Chernov wrote:
On Tue, Feb 04, 2003 at 16:10:06 +0300, Andrey A. Chernov wrote:
On Tue, Feb 04, 2003 at 14:00:27 +0100, Dag-Erling Smorgrav wrote:
David Schultz [EMAIL PROTECTED] writes:
You can do better than the present generator
On Tue, Feb 04, 2003 at 16:28:45 +0300, Andrey A. Chernov wrote:
I'll produce working variant based on your patch...
When all done correctly, there is repeated pattern still, so some NSHUFF
drop required too:
1 7 e 4 a 0 7 d 3 a 0 6
See attached patch based on -current sources.
--
Andrey
at the end.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Tue, Feb 04, 2003 at 16:47:14 +0300, Andrey A. Chernov wrote:
On Tue, Feb 04, 2003 at 16:28:45 +0300, Andrey A. Chernov wrote:
I'll produce working variant based on your patch...
When all done correctly, there is repeated pattern still, so some NSHUFF
drop required too:
1 7 e 4
On Tue, Feb 04, 2003 at 15:23:28 +0100, Dag-Erling Smorgrav wrote:
Andrey A. Chernov [EMAIL PROTECTED] writes:
On Tue, Feb 04, 2003 at 14:43:57 +0100, Dag-Erling Smorgrav wrote:
All that being said, adding 1 to *ctx before returning it (see patch)
adresses both of your objections: a seed
eliminates 0 stuck problem, no additional visible effects. Even
with a != 0 values are monotonically increased, I try with
a == 123459876
0: 123459876
1: 185549787
2: 247639698
3: 309729609
4: 371819520
5: 433909431
6: 495999342
7: 558089253
8: 620179164
9: 682269075
--
Andrey A. Chernov
http
On Tue, Feb 04, 2003 at 17:36:04 +0300, Andrey A. Chernov wrote:
with a != 0 values are monotonically increased, I try with
a == 123459876
With your a == 62089911 (i.e. +1) the same:
0: 62089911
1: 124179822
2: 186269733
3: 248359644
4: 310449555
5: 372539466
6: 434629377
7: 496719288
8
framework for that, could you please
test it with NSHUFF picked from 100-2000 range?
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Mon, Feb 03, 2003 at 10:55:42 +, Mark Murray wrote:
How do you _know_ that your newly chosen magic number isn't going to cause
some kind of recurring (and too-short) sequence of numbers?
I run simple test for it, it is not too short.
--
Andrey A. Chernov
http://ache.pp.ru
On Mon, Feb 03, 2003 at 14:08:41 +0300, Andrey A. Chernov wrote:
On Mon, Feb 03, 2003 at 10:55:42 +, Mark Murray wrote:
How do you _know_ that your newly chosen magic number isn't going to cause
some kind of recurring (and too-short) sequence of numbers?
I run simple test
) is not affected to to its hashing nature. We talk about rand(3).
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Mon, Feb 03, 2003 at 14:26:00 +0300, Andrey A. Chernov wrote:
random(3) is not affected to to its hashing nature. We talk about rand(3).
to to = due to
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
);
}
@@ -137,7 +143,7 @@
unsigned long junk;
gettimeofday(tv, NULL);
- next = (getpid() 16) ^ tv.tv_sec ^ tv.tv_usec ^ junk;
+ srand((getpid() 16) ^ tv.tv_sec ^ tv.tv_usec ^ junk);
}
}
--
Andrey A. Chernov
http://ache.pp.ru/
msg51666
lists for exact arguments.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
++)
+ (void)do_rand(next);
}
}
--
Andrey A. Chernov
http://ache.pp.ru/
msg51491/pgp0.pgp
Description: PGP signature
of this PRNG is needed.
Don't have an idea about this thing yet, maybe some sign or variable size
change fix required.
BTW, note that new formulae also used in the kernel (by BSD developers)
and taken from there - libkern/random.c - so all you say is true there
too.
--
Andrey A. Chernov
http
), but gain
nothing this way.
Workaround I find so far is something like that
#define MASK 123459876
seed ^= MASK;
... calculate value ...
seed ^= MASK;
Which just add another magick value, but fix zero.
I am still searching...
--
Andrey A. Chernov
http://ache.pp.ru/
msg51498/pgp0.pgp
rand.c source.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Sun, Feb 02, 2003 at 13:26:21 +0300, Andrey A. Chernov wrote:
Workaround I find so far is something like that
#define MASK 123459876
I found nothing better. Here is fix for 0 problem I plan to commit:
--- stdlib/rand.c.old Sat Jan 4 20:39:19 2003
+++ stdlib/rand.c Sun Feb 2 14
that David Schultz just made?
This is fix form problem with 0, not for seed - 1st value correlation.
I can't deal with two problems with same time, lets be sequental.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
to some another algorithm, but keep in
mind that rand() must be simple and speedy. Now used variant is most
simpler, others are much more complex.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Sun, Feb 02, 2003 at 16:42:25 +0300, Andrey A. Chernov wrote:
On Mon, Feb 03, 2003 at 00:17:35 +1100, Tim Robbins wrote:
I believe that this change just moves the bad seed to 123459876; after
calling srand() with that seed, each call to rand() returns 0.
Yes. Nothing better
On Sun, Feb 02, 2003 at 17:02:23 +0300, Andrey A. Chernov wrote:
I'll produce and send it a bit later.
Here it is.
--- stdlib/rand.c.old Sat Jan 4 20:39:19 2003
+++ stdlib/rand.c Sun Feb 2 17:06:08 2003
@@ -72,10 +72,13 @@
*/
long hi, lo, x;
+ /* Can't
;
lo = x % 127773;
x = 16807 * lo - 2836 * hi;
- if (x = 0)
+ if (x 0)
x += 0x7fff;
return (x);
#endif /* !USE_WEAK_SEEDING */
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd
().
Objections?
We can't, simple because sequence must be repeated for the same seed
across the calls.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
variant and be sure that speed is
acceptable. What form RC4 distribution have?
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Sun, Feb 02, 2003 at 17:34:19 +, Mark Murray wrote:
Andrey A. Chernov writes:
Objections?
We can't, simple because sequence must be repeated for the same seed
across the calls.
RC4 is repeatable.
It seems we mean different things saying arc4random(), see my answer
On Sun, Feb 02, 2003 at 21:20:09 +0300, Andrey A. Chernov wrote:
On Sun, Feb 02, 2003 at 17:30:48 +, Mark Murray wrote:
Why not? Arc4 is a) deterministic and b) good for all bits.
If you mean arc4random() function - not, because it use true randomness,
if you mean RC4 algorithm
be repeatable across the calls for same seed, that
is all. It not means repeatable accross platforms or across different OS
versions. In fact it is already not repeatable across different OS'es, so
regression is limited. Also, regression must not stop bugs fixing progress
in anycase.
--
Andrey
in that discussion,
moreover we already change it once.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
already proven as better than what we currently have, so don't have such
problem as RC4-based PRNG probably have.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
that it will happens _each_ time for rand() due to rand_r()
requirement 1) to output the same sequence as rand() and to 2) to store
one word seed value each time. I.e. it will be reseed on each call.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd
, not rand(). It is
common practice for this type of PRNGs to throw out N values after seeding
to remove correlation and srand() not follow this. My first patch fix
this.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current
, this mistake is not mine, but inherited from
BSD developers who made it in the first place in the kernel.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Sun, Feb 02, 2003 at 13:06:08 -0800, Kris Kennaway wrote:
On Sun, Feb 02, 2003 at 06:10:49PM +0300, Andrey A. Chernov wrote:
So far, this is final variant for 0 problem fixing ready for committing.
Any objections?
What tests have you run on this code to ensure it doesn't still have
or better.
2) Implementing rand(3) with RC4 can be possible only if seed (i.e.
state) can be stored in single word (due to rand_r()) restrictions.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
place (this is commonly spreaded method for this PRNG).
It is false for the last patch I post which not stuck with any given seed.
--
Andrey A. Chernov
http://ache.pp.ru/
msg51605/pgp0.pgp
Description: PGP signature
() TYPE4 which internal state is 252 bytes.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
are needed to compare what we have now in random(3) with RC4. Easy and
understandable code not always mean better results. We can't switch
algorithms blindly, i.e. when their comparative quality remains unknown.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL
to say good bye for '-r' ?
Well, we still need it for writing the first disklabel on an otherwise
empty disk, but I think it could be implied in that case.
-B implies -r too. Currenty this check prevents my bootblocks from
writting.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe
is turned on on their side.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Mon, Dec 23, 2002 at 10:55:05 -0800, Matthew Dillon wrote:
That's very odd. I see them on my development box too which is just
talking FreeBSD-FreeBSD. We should not be seeing them at all.
I got about 200 of them per 6 hours. Nothing unusual, small webserver +
SMTP.
--
Andrey
# (Cyl. 16900 - 17500*)
c: 358420160unused0 0 # (Cyl.0 - 17500*)
Please fix this GEOM bug, to allow to update bootblocks at least.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
= (uschar)a - (uschar)b;
+ r = (int)((uschar)a) - (int)((uschar)b);
return r;
}
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
on compiler, i.e. does it implements value preseving or
unsigned preserving for 'char' type conversions. Or ANSI C vs. common C
mode. Better be safe for both.
Read 6.10.1.1 section here:
http://wwwrsphysse.anu.edu.au/doc/DUhelp/AQTLTBTE/DOCU_067.HTM
--
Andrey A. Chernov
http://ache.pp.ru
operation with it.
--
Andrey A. Chernov
http://ache.pp.ru/
msg48647/pgp0.pgp
Description: PGP signature
, commit.
--
Andrey A. Chernov
http://ache.pp.ru/
msg48017/pgp0.pgp
Description: PGP signature
On Tue, Nov 19, 2002 at 14:52:02 +0200, Ruslan Ermilov wrote:
It seems that this patch has never been committed. This is a critical
bug that should be fixed before 5.0-RELEASE is out.
I agree. There is no locale yet and I never see that patch.
--
Andrey A. Chernov
http://ache.pp.ru
On Wed, Nov 20, 2002 at 14:27:53 +1100, Tim Robbins wrote:
On Wed, Nov 20, 2002 at 04:38:38AM +0300, Andrey A. Chernov wrote:
On Tue, Nov 19, 2002 at 14:52:02 +0200, Ruslan Ermilov wrote:
It seems that this patch has never been committed. This is a critical
bug that should be fixed
On Tue, Nov 12, 2002 at 12:37:13 +0100, Dag-Erling Smorgrav wrote:
Andrey A. Chernov [EMAIL PROTECTED] writes:
Old bugfix for double Last login: was spammed in 3rd time, causing
following printout:
I can't reproduce this here.
Look at session.c, one Last login comes from
\n, time_string,
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Tue, Nov 12, 2002 at 14:47:51 +0100, Dag-Erling Smorgrav wrote:
Andrey A. Chernov [EMAIL PROTECTED] writes:
BTW, double-testes options.print_lastlog looks suspiciuos. For what
print_pam_messages() used here? It is unclear to me.
I think the idea is that we should define NO_SSH_LASTLOG
.
There was USE_LASTLOG on the way, which is currently on and checked before
DISABLE_LASTLOG, so DISABLE_LASTLOG does nothing. See loginrec.c
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Tue, Nov 12, 2002 at 15:28:41 +0100, Dag-Erling Smorgrav wrote:
Andrey A. Chernov [EMAIL PROTECTED] writes:
There was USE_LASTLOG on the way, which is currently on and checked before
DISABLE_LASTLOG, so DISABLE_LASTLOG does nothing. See loginrec.c
No, USE_LASTLOG is not defined
Old bugfix for double Last login: was spammed in 3rd time, causing
following printout:
zzz@xxx's password:
Last login: Wed Nov 6 17:12:40 from
Last login: Wed Nov 6 17:10:08 2002 from
Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994
...
--
Andrey A. Chernov
http
On Sun, Oct 27, 2002 at 03:37:47 +0300, Andrey A. Chernov wrote:
I have disk shared between FreeBSD and M$ Win, two slices, and got
incorrect disklabel with GEOM kernel. Namely cylinders and
sectors/unit fields are from _whole_ disk, not from just requested
slice.
Just found more
.0 -
778*)
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
On Wed, Oct 23, 2002 at 19:44:33 +0300, Adrian Penisoara wrote:
Hi,
Someone (ache it seems) forgot to add the sr_YU.ISO8859-[25]
directories in /usr/share/locale to the BSD.usr.dist mtree file.
Please check your BSD.usr.dist is not obsoleted. They are there from
v1.266
--
Andrey
make hierarchy and 'mergemaster -p' or 'make
installworld' interaction.
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
and let me know.
According to my test, signal 6 crashes happened with _both_ old pm3 port
and new ezpm port (first thing I try to do seeing them - upgrade to latest
cvsup, with ezpm, and see exact the same crashes as with old pm3 cvsup).
--
Andrey A. Chernov
http://ache.pp.ru/
To Unsubscribe
On Thu, Oct 03, 2002 at 08:11:10 +0400, Andrey A. Chernov wrote:
On Wed, Oct 02, 2002 at 20:51:40 -0700, Julian Elischer wrote:
Please back it out or do it properly!
this IS the backout.. it's now how it was before, including in 4.x
I mean - back out this backout - it damage 5.0
1 - 100 of 511 matches
Mail list logo
