Quoting Warren Block :
On Tue, 19 Apr 2016, Aleksander Alekseev wrote:
Why Wikipedia, specifically? There are a lot of places that describe
quicksort. How about just
Note: This implementation of qsort() is designed to avoid the
worst-case complexity of N**2 that is often seen with stand
Quoting "O. Hartmann" :
Since a couple of days I get this weird console-and-log-spamming message:
ath0: stuck beacon; resetting (bmiss count 4)
The machine in question is running the most recent CURRENT right now:
FreeBSD 11.0-CURRENT #2 r272471: Fri Oct 3 13:03:58 CEST 2014 amd64
and the b
m.
That build is intended to become the official release unless some
last-minute showstopper problem is found. (Unlikely, but has happened before.)
The build is being distributed in advance of the official announcement
to make sure it is available on all mirrors at the moment the
announcement is made
am will still
be in use when two-digit years becomes a problem!"
--
Erik Trulsson
ertr1...@student.uu.se
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any
orks) is to use csup/cvsup to download a
local copy of the whole CVS repository and then use cvs to checkout
/usr/src from this copy.
Before the switch to subversion this was the preferred way.
--
Erik Trulsson
ertr1...@student.uu.se
___
freebsd-cur
- Bumps __FreeBSD_version to 900030
Are there any ports which link to the old version of libdialog, and if
so, what will happen to them?
Why not keep the old version as libdialog and instead use a new name
for the new library (libndialog or whatever) ?
(I am not saying you should do
d I will post results :)
The only difference between Athlon XP and Athlon MP is that the MP
variants are certified for multi-processor use (in reality most Athlon
XP also worked just fine in multi-processor systems, or could easily be
modified to do so.) Available instructions and registers are ident
No, it does not need to do that. It might be a good idea (but I am far
from convinced of it), but there most certainly is no *need* to move in
that direction.
--
Erik Trulsson
ertr1...@student.uu.se
___
freebsd-current@freebsd.org mailing list
http
cense changed such that
clause 3 (the advertising clause) no longer apply. This would seem to
include mkdir.c
Most of the files in the source tree have not had their copyright
notices updated to reflect this.
See http://www.freebsd.org/copyright/license.html for details on this
license.
On Mon, Nov 17, 2003 at 09:00:20AM -0500, Michael Edenfield wrote:
> * Erik Trulsson <[EMAIL PROTECTED]> [031116 23:21]:
> > On Sun, Nov 16, 2003 at 07:24:00PM -0700, Brent Jones wrote:
> > > This is just a case of OS evolution. /sbin used to be the place where
>
you still need
> a place to have statically linked recovery utilities, /rescue was
> created. Now you see the duplicates in /bin (or /usr/bin) and /rescue
> instead.
Do you have any references for this? Every single place that I can
find explains /sbin as "system b
7;t use the commands in /bin due to problems with
dynamic linking you are unlikely to be helped by the commands in /sbin
being statically linked. (For one thing you won't be able to get a
shell since those normally reside in /bin.)
--
Erik Trulsson
[EMAIL PROTECTED]
On Fri, Oct 31, 2003 at 06:20:17PM +0100, Stefan Farfeleder wrote:
> On Fri, Oct 31, 2003 at 04:43:37PM +0100, Erik Trulsson wrote:
>
> > Perhaps not smaller in terms of the sizeof operator, but why can't one
> > have a 16-bit char, and an int8_t which occupies 16 bits,
about. (Some would say that this was a
> rather belated recognition of a choice the industry made two decades
> ago There was, however, a 36-bit implementation of FIPS 151-2, by
> UNISYS.)
--
Erik Trulsson
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nderstood something.
>
> Basically, this is just an experimental protocol that's being played
> with here, and if it ever becomes real, then it will need an IANA
> protocol number assignment before it's widely deployed.
Are you sure that IANA would be the right organisation,
seable mailing lists,
> >>FreeBSD site, CVS via WWW, PRs, ports and docs.
Note that there are many web-archives of the mailing lists. Lots of
them are run by other people. You need to talk to them too.
> >>
> >>As I think, simple form will be enough to stop
> >
ENT,
with the tag for that being '.' as usual.
>
> I'm not sure if 'RELENG_5_2' will work...
I am sure it will not work, since that tag does not yet exist, and will
not exist until 5.2-RELEASE is almost ready to go.
--
Erik Trulsson
[EMAIL PROTECTED]
__
is something sinister
> going on?
>
> Just wonderin'
>
> Andrew Lankford
>
--
Erik Trulsson
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
tly quite stable (not
counting any commits made during the last 48 hours or so since I have
not yet tested any of those), but it is of course possible that other
people have run into bugs in components of the kernel that I don't use.
(Note: I do not have PAE enabled in the kernel. I have
the value will be preserved.)
>
> See section for 6.3.1.3 for the details.
Yes, please do.
>
> That's why I said 'as if' in my other mail.
--
Erik Trulsson
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.
-)
> but that
> is another story :). [no need to answer this... unless we take it out
> of this thread]
>
>
> >And to answer the original question:
> >It is valid to assume that -1 converted to an unsigned integer type
> >will never be equal to 0.
two's complement there is no need to change the representation when
converting signed to unsigned values, while this can be needed when
using sign-magnitude or one's-complement.
And to answer the original question:
It is valid to assume that -1 converted to an unsigned integer type
will never be equal to 0.
--
Erik Trulsson
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
warnings are generated. When
compiled with 'gcc -O1 -Wall' you get a warning that 'a' might be used
uninitalized. (This is the case for gcc 2.95.x at least. I believe the
situation is the same with gcc 3.x)
--
Erik Trulsson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
eds to be modified again.
>
> Please, oh please, don't change that behavior in
> srand()/rand().
>
> - Dave Rivers -
--
Erik Trulsson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
also be worth noting that if a good PRNG is needed then one
should not use random() or rand() since on some systems their output is
not very random.
--
Erik Trulsson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
a SiS 5591,
which it isn't. It is a SiS 5513.)
--
Erik Trulsson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
to turning off A and J (implicitly, ie by not specifying them)?
Read again. J automatically sets R.
Yes, not having J set should improve performance noticeably compared
with having J set.
--
Erik Trulsson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
s is true also for many 486 boxes too.
> > > So even if 386 stuff were in the default kernel, you'd likely have
> > > other issues in making sysinstall work and have to do custom
> > > hacking...
> >
> > Add to this that Bosko's workaround for the CPU bug with PSE/PGE
> > includes loading the kernel at 4M rather than 1M.
--
Erik Trulsson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
d those are generally
not portable between major releases it is not very likely it will work.
--
Erik Trulsson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ting PAUSE instruction:
Register esp changed: 0xbfbffb20 -> 0xbfbffae4
Both machines running 4.6-PRERELEASE
--
Erik Trulsson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
quot;
but rather from its own start file under /usr/local/etc/rc.d/ after
disabling sendmail with sendmail_enable="NO" (now "NONE"), which I
think should be the standard behaviour for alternative MTAs.)
So, if one uses qmail this change does require you to modify the
sendmail_* optio
argued that there should be some cache-coherence protocol
between the CPU and the AGP device. Not knowing how AGP is specified I
don't know if this interaction between the CPU and AGP is a bug or just
working as specified. I suspect it is the latter though.
--
Erik Trulsson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
" perhaps??
I.e. describing the desired state of the feature instead of the desired
action to be taken.
There are of course several people who feel that the current behaviour
is the intuitive and obviously correct interpretation and would prefer
not to have it changed.
--
Erik Trulsson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
revision 1.24.2.4
date: 2001/07/16 03:28:26; author: peter; state: Exp; lines: +11 -56
MFC: unify libscrypt/libdescrypt into libcrypt.
--
Erik Trulsson
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
about that. (This might of course
indicate that the manpage isn't in sync with reality.)
Somebody who knows what is up with rpc.lockd is welcome to comment.
>
> On Wed, 22 Mar 2000, Erik Trulsson wrote:
>
> > On Wed, Mar 22, 2000 at 12:04:55PM +0300, Grigory Kljuchnikov
On Wed, Mar 22, 2000 at 12:04:55PM +0300, Grigory Kljuchnikov wrote:
> Thierry, thank you for the information,
> but it's very bad that there isn't NFS locking in FreeBSD.
> I'm afraid I need to move my FreeBSD NFS server to Solaris
> for x86.
>
> I don't understand why NFS locking isn't in Fre
36 matches
Mail list logo
