our eyes will save you. ;-)
On one of my first linux desktops, I had a screensaver which displayed
rotated dumpscreens of all kinds of different Operation systems. Apple,
Basic, linux and BSOD.. (come to think about it BSD was not included)
my 2 cents ;-)
Best regards,
-Erik.
>
> Gr
r me, as I have no USB devices,
but I thought someone else would want this information.
Anyone else experiencing this?
--
+---+
Erik H. Bakke, Habatech AS | To be or not to be... |
E-Mail: e...@habatech.no
etails for the USB port as well as the 2940.
This will come as soon as I recompile a problematic kernel...
--
+---+
Erik H. Bakke, Habatech AS | To be or not to be... |
E-Mail: e...@habatech.no| Is si
el. (boot -v)
--
+---+
Erik H. Bakke, Habatech AS | To be or not to be... |
E-Mail: e...@habatech.no Date: 02-May-99 Time: 14:30:48| Is simply a
question of binary logic. |
This message was se
t rid of it, but these things can happen
from time to time :)
--
+---+
Erik H. Bakke, Habatech AS | To be or not to be... |
E-Mail: e...@habatech.no| Is simply a question of binary logic.
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
On Wed, Mar 22, 2000 at 03:46:12PM +0300, Grigory Kljuchnikov wrote:
> Thank you, Erik!
>
> I find rpc.lockd and start it manually. My test with NFS locking works right.
> But it don't start on boot by default if I enable NFS server in
> /stand/sysinstall and there is the com
>
> John
>
> I have a patch (courtesy of Brian Somers) that fixes M3. I believe
> he has submitted it to you.
>
> May I/We commit it?
>
> M
>
could this patch please be made available via HTTP or anon FTP?
so those of us unable to install cvsup can get it?
d that doesn't do it, so I
don't believe it's strictly hardware. I've posted my kernel config, uname,
and dmesg at http://www.smluc.org/~erik/fbsd/
I'm willing to work on this, but I don't want to duplicate effort or spend
too long fighting it if it's a stupi
" 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
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
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
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
/206c0us/5
I don't know if this is ClangSD-related. I haven't tried kernel debugging
before. Any pointers on how to proceed?
Thanks,
Erik
le-deadlock-detected-for-0xe0001187d880%2C-blocked-for-1801437-ticks-p28123802.html
and this i the result:
http://tinypic.com/r/2llegza/5
Any pointers on ho to debug this further?
Thanks,
Erik
Den 19/04/2010 kl. 17.03 skrev Attilio Rao:
> 2010/4/19 Erik Cederstrand :
>> Hi
>>
>> I'm testing ClangBSD in a VirtualBox client and ran into a panic on the
>> client, but I don't think it's clang-related. I haven't tried kernel
>> debug
Recently I've been trying to upgrade an early januarrry -current to
current -current. I've rebuilt the kernel several times over the last few
days (with new cvsup's) so i've eliminated any freak check-in mismatches.
During a make world (usually about 10-20 minutes in on my P100) everything
just c
I'm seeing a problem with uptime in recent -currents which doesn't make any
sense to me.
odin# uptime
uptime: /dev//umount: /proc: not currently mounted
umount:: No such file or directory
uptime: /dev// /var: not currently mounted
umount: /usr: n: No such file or directory
3:24PM up 1 day, 18:17
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
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
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
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
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
the merging of some TCP
> patches.
>
I noticed the same thing... then
try sysctl net.inet.tcp.delayed_ack=0
fixed the issue
--
-Erik <[EMAIL PROTECTED]> [http://math.smsu.edu/~erik]
The opinions expressed by me are not necessarily opinions. In all probability,
they are ra
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
.
Apart from the mentioned src/make.conf options, you might want to try removing
"makeoptions DEBUG=-g" from the kernel config, plus support for hardware you
will never need. The debugging symbols in /boot/kernel use a lot of space.
THanks,
Erik
ncing well-known and presumably harmless
LOR's if there isn't sufficient motivation to fix the source?
Erik
Den 05/01/2011 kl. 14.56 skrev Erik Cederstrand:
> Ignoring contrib code for the moment, I decided to look at usr.sbin.pw from
> 2011-01-05. There's one report
> (http://scan.freebsd.your.org/freebsd-head/usr.sbin.pw/2011-01-05-amd64/report-KkilQ3.html#EndPath)
> which turns
he analyzer doesn't know that this function never returns and continues to
flag a null dereference in step 8
What's the fix here?
I think the reports are an excellent way to get acquainted with FreeBSD code.
Marking and fixing the false positives would make bug-hunting in the remaining
reports more motivating :-)
Thanks,
Erik
there are some
> possible remedies:
>
> - get IPA to work with clang, or at least file a bug
I filed a bug with LLVM (http://llvm.org/bugs/show_bug.cgi?id=8914) but it
seems IPA bugs filed on the analyzer have been rejected in the past.
Erik
ed as such. If we begin spewing __dead2's
everywhere, it's bound to silence a valid bug somewhere down the line when e.g.
a conditional in a print_help() function is changed subtly so it doesn't always
reach exit().
Erik
- 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
Den 06/01/2011 kl. 20.56 skrev Tijl Coosemans:
> On Thursday 06 January 2011 09:01:09 Erik Cederstrand wrote:
>> Den 05/01/2011 kl. 20.36 skrev Jilles Tjoelker:
>>> On Wed, Jan 05, 2011 at 05:55:45PM +0100, Ulrich Spörlein wrote:
>>>> - get IPA to work with
g with 5 minutes of thinking. I'm
glad the most obvious things have already been done, and I'm sure you and
others have put a lot of effort into this. My question was more what, if
anything, can be done to speed up the cluster.
Also, how long does it take to complete an exp-run on the cluster?
Thanks,
Erik
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
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]"
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]
__
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
> >
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,
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]"
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,
he doc the card is supported in current, and later in 5.2. You
have to compile with device ath and device ath_hal
The OS panic with or without the device-setting for ath and ath_hal.
Do you now way the card is identified as a 3Com card insted of a D-Link???
Regards
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]
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
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
>
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.
un.sh mkdir.cfg
- LOR is triggered immediately
Erik
version of the headers instead of the clang
version. This has been fixed before in ClangBSD, but probably the logic to
decide on which headers to use are insufficient.
Thanks,
Erik
l 9.0-CURRENT FreeBSD 9.0-CURRENT #2 r208586:208611M: Thu
May 27 23:35:35 CEST 2010
r...@vb_fbsd8.local:/usr/obj/usr/home/erik/freebsd/clangbsd/src/sys/GENERIC
amd64
clangbsd# cd /usr/src/tools/regression/
clangbsd# prove fstest/tests/chflags
fstest/tests/chflags/00.t .. ok
fstest/tests/c
Den 31/05/2010 kl. 21.50 skrev Erik Cederstrand:
> I do have a problem with buildworld on an unmodified ClangBSD src/ tree
> within a ClangBSD VM. Clang barfs on the mmintrin.h headers when building
> it's own Lexer because it picks up the gcc version of the headers instead o
nning 'prove -r'. Some of the tests don't
contain .t files, so I assume they can't be run using 'prove'?
Also, I'd like to filter out the tests that don't apply on my system, e.g. zfs
tests.
Thanks,
Erik
les found. Unfortunately, some of the Makefiles start running tests
immediately, some have syntax errors etc., so I'll have to add some more logic.
Erik
Den 03/06/2010 kl. 21.54 skrev Giorgos Keramidas:
> On Thu, 03 Jun 2010 14:50:13 +0200, Alexander Leidinger
> wrote:
>> Quoting Erik Cederstrand (from Thu, 3 Jun 2010
>> 12:02:51 +0200):
>>
>>> Hi,
>>>
>>> I'd like to run the regress
ns 'sh regress.sh', so you could
run that and see how far it gets. Then obtain backtrace etc. when it crashes.
Erik
Den 03/06/2010 kl. 16.14 skrev Maxim Konovalov:
> On Thu, 3 Jun 2010, 15:15+0200, Erik Cederstrand wrote:
>
>> I just wrote a shell script to recurse into the subdirectories and
>> run make on the Makefiles found. Unfortunately, some of the
>> Makefiles start running
d please,
don't ask me innocently if I want to delete my local account when it's 4 AM :-)
I may be answering 'yes' in my sleep)
+1 from me on etcupdate in base.
Erik
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]"
-)
> 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.
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.
experienced minds consider it? :) I think
I'm going to wait an hour or two before trying to fix it, maybe someone
sees this as a quick fix
--
-Erik <[EMAIL PROTECTED]> [http://math.smsu.edu/~erik]
The opinions expressed by me are not necessarily opinions. In all probability
t you keep looking
> and hacking :-)
>
Looks like I'm out of this one, I got up this morning, cvsup'd and built
world just to make sure it was fresh, then I quit getting the crashes. I
d'no if the issue was fixed by something someone else did or what...
-
-Erik <[EMA
> On Wed, 3 Jul 2002, Erik Greenwald wrote:
> >
>
> > Looks like I'm out of this one, I got up this mor
c: At top level:
/usr/src/contrib/gdb/gdb/gdbserver/gdbreplay.c:266: warning: no previous
prototype for `play'
/usr/src/contrib/gdb/gdb/gdbserver/gdbreplay.c: In function `play':
/usr/src/contrib/gdb/gdb/gdbserver/gdbreplay.c:278: warning: implicit
declaration of function `write'
*
Mawson Lakes Blvd.
> [EMAIL PROTECTED] South Australia, 5095
>
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
--
-Erik <[EMAIL PROTECTED]> [
PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
--
-Erik <[EMAIL PROTECTED]> [http://math.smsu.edu/~erik]
The opinions expressed by me are not necessarily opinions. In all probability,
they are random rambling, and to be ignored. Failure
erse
engineering the card and building a driver from scratch... maybe
something that works with X the X way (dri/drm)
--
-Erik <[EMAIL PROTECTED]> [http://math.smsu.edu/~erik]
The opinions expressed by me are not necessarily opinions. In all probability,
they are random rambling, and t
The important
> question to ask is, who will do the dirty work?
>
> Scott
>
I'd be willing to help. I'm not exactly sure on what modifications to
gcc are required to shove it into the base, but I have time (not working
right now). :)
--
-Erik <[EMAIL PROTECTED]&
lworld thing again?
for your own code, you seem to lack -lstdc++
--
-Erik <[EMAIL PROTECTED]> [http://math.smsu.edu/~erik]
The opinions expressed by me are not necessarily opinions. In all probability,
they are random rambling, and to be ignored. Failure to ignore may resu
eem to reproduce it so it may have been a bug or something, I don't
know :)
--
-Erik <[EMAIL PROTECTED]> [http://math.smsu.edu/~erik]
The opinions expressed by me are not necessarily opinions. In all probability,
they are random rambling, and to be ignored. Failure to ignore may
ne
wants it, they can cvs an older version or something...
--
-Erik <[EMAIL PROTECTED]> [http://math.smsu.edu/~erik]
The opinions expressed by me are not necessarily opinions. In all probability,
they are random rambling, and to be ignored. Failure to ignore may result in
severe b
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
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
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
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
me to do
> the work required get the code submitted upstream.
Over the 15 odd years following this list, I've had to killfile only three
people. But your hostility and complete lack of understanding that nobody owes
you anything is unbearable. I'll make it four now. Goodbye.
Erik
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
rver. I haven't adapted it to the
Bugzilla that is running now, but it should be fairly easy. Maybe this could be
of use?
Erik
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubsc
ackaged base, don't use it. Build and install
from SVN instead. If you're using freebsd-update today, you essentially have
14.000 packages and a far less powerful CLI, so why is packaged base not a step
in the right direction?
Erik
___
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
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
Hi all,
I've been working on a project to make it possible to produce deterministic
builds with FreeBSD. By this I mean building a FreeBSD distribution twice from
the same code base and having all files in the two distributions match by md5
sum. Currently, this is not the case.
My main goal fo
Hi Ruslan,
Den 09/12/2011 kl. 14.37 skrev Ruslan Ermilov:
> On Fri, Dec 09, 2011 at 12:16:39PM +0100, Erik Cederstrand wrote:
>> I've been working on a project to make it possible to produce deterministic
>> builds with FreeBSD. By this I mean building a FreeBSD distributi
Den 15/12/2011 kl. 22.21 skrev Andrew Boyer:
> These two changes allow you to set PXE as the default MBR boot selection,
> which enables you to write a 'reboot to the network' script. We've found it
> to be very useful. What do people think?
I think this is very useful for e.g. re-installing
Hi,
I've created a patch that cleans up FreeBSD Makefiles that unconditionally set
the -g flag for GCC. The motivation for this is that it should be possible to
add or remove this flag globally via e.g. CFLAGS (it's part of my quest to
produce deterministic builds).
I'm not very familiar with
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
Roman,
Den 11/09/2012 kl. 14.38 skrev Roman Divacky :
>
> Upstream developers almost never use gcc4.2.1 as we do. So right now the
> ports maintainer must check whats wrong in the case the (upgraded) port
> doesnt compile with our in-tree gcc.
>
>
> It can be trivial USE_GCC=4.something but the
Den 12/09/2012 kl. 11.29 skrev Doug Barton :
> On 09/11/2012 02:52 AM, Erik Cederstrand wrote:
>> So can we do a sweep on the ports tree and mark the 2232 ports with
>> USE_GCC=4.2 until they can actually build with clang?
>
> Unfortunately it isn't that simple. We al
throw the switch.
Congratulations! I know that you and others of the Clang BSD have worked hard
for years on this, so it's nice to see the work finally paying off.
Erik
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listi
rrelevant" info like compiler version, hostname, username,
timestamp, absolute path etc. are a nuisance if they can't be turned off with
-fno-ident, -frandom-seed, -DSTRIP_FBSDID, ar -D and the like.
Thanks,
Erik
___
freebsd-current@freebs
buildkernel configuration in a central place and expect users to supply
information about whatever non-standard setup they did.
Erik
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
equire that
a larger part of the LLVM source tree is imported into src/contrib, though.
Erik
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
med for that.
You can't seriously blame LLVM for making progress. If ports rely on a specific
version of LLVM, it would be far better to create devel/llvm31, devel/llvm32
etc.
Erik
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd
produced cans, then foul cans will go unnoticed until a dog pukes all over the
carpet :-)
For this to change, we really need to catch up on years of neglect in e.g.
src/tools/regression/. I really applaud the people doing the thankless job of
changing th
Erich,
Den 11/02/2013 kl. 00.38 skrev Erich Dollansky :
> On Sun, 10 Feb 2013 15:57:01 +0100
> Erik Cederstrand wrote:
>
>> And as long as there is no automatic can taster doing quality
>> assurance of the produced cans, then foul cans will go unnoticed
>> until a do
ers are doing by running CURRENT
and reporting and fixing errors. At the same time, I look to e.g. LLVM and
their "no commit without a regression test" goal and think we could do way
better :-)
Erik
___
freebsd-current@freebsd.org mailing
Den 26/04/2012 kl. 11.35 skrev Konstantin Belousov:
> I think it is time to stop building the toolchain static. I was told that
> original reasoning for static linking was the fear of loosing the ability
> to recompile if some problem appears with rtld and any required dynamic
> library. Apparentl
Den 26/04/2012 kl. 22.30 skrev Chris Rees:
> On 26 April 2012 20:15, Matthew Seaman
> wrote:
>> On 26/04/2012 20:01, Chris Rees wrote:
>>> hydra# cd /usr/ports && time make MAKE=~crees/bin/make-static index
>>>
>>> Generating INDEX-9 - please wait.. Done.
>>> 729.770u 120.841s 7:45.10 182.8%
Den 01/05/2012 kl. 07.52 skrev Tim Kientzle:
>
> On Apr 30, 2012, at 6:41 AM, Erik Cederstrand wrote:
>>
>> Can anyone explain to me why the dynamically linked version is significantly
>> slower? What are the extra steps involved compared to a statically linked
>&g
Den 01/05/2012 kl. 15.55 skrev Gary Palmer:
>
> If you want a high-level view of what goes on run
>
> ldd `which ls`
>
> check that it has libraries to load and doesn't say "not a dynamic ELF
> executable", and then run:
>
> ktrace ls
> kdump | more
>
> All the system calls related to resolvi
Den 02/05/2012 kl. 13.56 skrev John Baldwin:
>>
>> Static version:
>> * 0.09 ms spent execve'ing /usr/bin/make
>> * The rest is mostly sysctl calls
>>
>> Dynamic version:
>> * 0.09 ms spent execve'ing ./dynamicmake and /libexec/ld-elf.so.1
>> * 0.18 ms spent loading libc.so.7 (incl. reading /etc/
1 - 100 of 146 matches
Mail list logo
