ially on SPARC and ARM.
Thanks,
Erik
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
sd-arch/2010-April/010143.html
Erik
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Den 29/10/2012 kl. 11.30 skrev Dimitry Andric :
> On 2012-10-29 09:12, Erik Cederstrand wrote:
>>
>> The code in the report is /sbin/zpool, so I assume it's not KERNEL code. As
>> I wrote in my email, I can see B_TRUE and B_FALSE are defined as boolean_t
>> in
/opensolaris/sys/types.h But I can't see that boolean_t is
defined anywhere in the included headers as long as KERNEL is not defined. As
far as I can see, sys/gnu/fs/xfs/xfs_types.h isn't referenced directly or
indirectly in any of the headers included in zpool_main.c.
Erik
___
ined.
I'm sure that ZFS wouldn't work if B_TRUE or B_FALSE were undefined, I just
can't figure out where it's happening. I need a hint :-)
Thanks,
Erik
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/list
h patches
I think they're too open-ended to enter in the wiki as-is, but I'd also like to
not spam the wiki with lots of almost-identical tasks. What's the best way to
suggest them for CodeIn?
Erik
___
freebsd-hackers@freebsd.org mail
ull
pointer is OK. I'd appreciate an explanation :-)
Thanks,
Erik
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
pe? Or are there better ways to enforce the
invariant?
Thanks,
Erik
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Clang Analyzer reports about 100 cases of "Allocator sizeof operand mismatch",
for example:
http://scan.freebsd.your.org/freebsd-head/sbin.umount/2012-09-23-amd64/report-k4ThD9.html#EndPath
The reports seem to be valid, but I'm no export. I can work out that the above
should probably be fixed b
Den 19/09/2012 kl. 11.19 skrev Erik Cederstrand :
> The below below patch will let the analyzer reason correctly about the code,
> and removes the report mentioned above (and a handful others in ncurses). It
> doesn't touch contrib code, but I'm not happy about changi
;s used so many other places. Any other ideas for how to best solve
this?
Kind regards,
Erik Cederstrand
Index: lib/ncurses/ncurses/ncurses_cfg.h
===
--- lib/ncurses/ncurses/ncurses_cfg.h (revision 240638)
+++ lib/ncurses/ncurses/
Den 14/09/2012 kl. 13.03 skrev Ivan Voras :
> On 14/09/2012 09:49, Erik Cederstrand wrote:
>> Hello hackers,
>>
>> I'm looking through the Clang Analyzer scans on
>> http://scan.freebsd.your.org/freebsd-head looking for false positives to
>> report b
Hello hackers,
I'm looking through the Clang Analyzer scans on
http://scan.freebsd.your.org/freebsd-head looking for false positives to report
back to LLVM. There are quite a list of reports suggesting to change vfork()
calls to posix_spawn(). Example from /bin/rpc:
http://scan.freebsd.your.or
Den 03/09/2012 kl. 09.25 skrev Junior White :
> hi all,
> I build a new kernel and install it, but don't known how to test the my
> new kernel's performance.
> I have read the Regressin and Performance Testing Guide in developer's
> handbook. But where is
> the test program is, and how do i in
Hi Ali,
Den 17/04/2012 kl. 12.35 skrev ali mousa:
> Hi all
>
> I'm working on a new tool that may increase Operating System
> performance. I'm looking for a tool that can measure OS performance
> especially FreeBSD, so I can compare after and before applying the
> patch.
Take a look at the
Den 18/01/2012 kl. 03.21 skrev Devin Teske:
> Looking at bin/164192...
>
> I'm left wondering to myself...
> How on Earth did a regression-by-typo introduced in SVN r214735 go 14 months
> without being noticed?
Because the regression tests in FreeBSD don't cover this part of the code?
:-)
Eri
primarily asked about was if the problem in
question also exists on FreeBSD. That is something that AIX people are
unlikely to know anything about.
--
Erik Trulsson
ertr1...@student.uu.se
___
freebsd-hackers@freebsd.org mailing list
http://lists.free
Hi Joerg,
Den 02/12/2010 kl. 13.49 skrev Joerg Sonnenberger:
> On Thu, Dec 02, 2010 at 11:08:09AM +0100, Erik Cederstrand wrote:
>> I wonder if I could hack __FILE__ to be a path relative to src/. That
>> would be a way to fix all the source file paths I see.
>
> I hav
ut apart from a build error I'm investigating now, this doesn't
help with all cases. __FILE__ is used liberally in at least src/sys/sys/.
I wonder if I could hack __FILE__ to be a path relative to src/. That would be
a way to fix all the source file paths I see.
Erik
Den 02/12/2010 kl. 03.44 skrev Ryan Stone:
> Does the C file use the __FILE__ macro?
There are a bit over 1000 files with checksum mismatches, but they seem to
differ in the same way. I've picked an example: /usr/lib/libbsnmp.a
It contains the string
"/usr/home/erik/freebsd/
Den 25/11/2010 kl. 13.08 skrev Erik Cederstrand:
> rodata.str1.4:
> --
> Some *.o files (all?) contain the path to the corresponding source file:
>
> Contents of section .rodata.str1.4:
> 2f757372 2f686f6d 652f6572 696b2f66 /usr/home/erik/f
> 0
Den 25/11/2010 kl. 20.17 skrev Mark Johnston:
> On Thu, Nov 25, 2010 at 01:08:58PM +0100, Erik Cederstrand wrote:
>> Kernel modules:
>> --
>> In the ELF section .gnu-debuglink, there is a link to the corresponding
>> *.ko.symbols file. It seems to
Den 25/11/2010 kl. 13.08 skrev Erik Cederstrand:
> Symbol tables:
>
> For example, libstand.a shows up in a diff. Looking with objdump, I see the
> contained _setjmp.o file has the following symbol table:
>
> SYMBOL TABLE:
> ldf *ABS*
g now, but I'd like
to know what is actually going on.
Symbol tables:
For example, libstand.a shows up in a diff. Looking with objdump, I see the
contained _setjmp.o file has the following symbol table:
SYMBOL TABLE:
ldf *ABS* 0000
/usr/home/erik/fr
make WITH_DETERMINISTIC=true buildworld/kernel
If I could get sendmail config scripts to see src.conf, then it would be
possible to place the flag in src.conf.
Normal "make buildworld" should be unaffected by the patch. I have attempted to
keep the diff as small as possib
ining the
output of "svn stat", "svn diff", src.conf, make.conf, SRCDIR and OBJDIR
locations, the full buildworld/kernel command and whatever else could affect
the build outcome.
Erik
Den 14/11/2010 kl. 21.32 skrev Dimitry Andric:
> On 2010-11-14 21:22, Erik Cederstrand wrote:
>> I'm curious as to why this might be useful? Would the mtime of the
>> file not be be sufficient? I can only think of debugging purposes, but
>> apart from the timestamp, two
tical, so I
think the rev. number is more useful. Is the timestamp not just a remnant from
the CVS days?
If it is useful, why not brand all binaries with a rev. number and a timestamp?
Erik
_llvm_lib_VMCore_PrintModulePass.cpp__BDCFB9C615PrintModulePassE
> N135_GLOBAL__N__usr_home_erik_freebsd_head_src_lib_clang_libllvmcore_.._.._.._contrib_llvm_lib_VMCore_PrintModulePass.cpp__BDCFB9C617PrintFunctionPassE
I'm not sure what to do with this except pass it on to the LLVM lists.
Erik
eful on amd64 though. No amd64 machines have ISA
> slots in which to place an ISA PnP adapter.
Are you really sure about that?
See http://www.ibase.com.tw/2009/mb945.htmL or
http://www.adek.com/ATX-motherboards.html for what certainly looks like
counter-examples.
--
Er
Den 21/10/2010 kl. 19.57 skrev Ulrich Spörlein:
> On Mon, 11.10.2010 at 11:35:42 +0200, Erik Cederstrand wrote:
>>
>> I'm beginning to think that it should at least be optional. Removing e.g.
>> build times, mtimes and path to OBJDIR or SRCDIR might not make ev
1000.sr?page=0,0 )
There could be differences in rotational speed between different models
(but no such difference has been reported yet), but they all have a
fixed RPM.
--
Erik Trulsson
ertr1...@student.uu.se
___
freebsd-hackers@freebsd.org ma
re.
I'm beginning to think that it should at least be optional. Removing e.g. build
times, mtimes and path to OBJDIR or SRCDIR might not make everyone happy.
Any hints to why kernel module checksums don't match?
Thanks,
Erik
e src
repo internally, plus unique identifiers.
freebsd.cf, freebsd.submit.cf, sendmail.cf and submit.cf record the absolute
OBJDIR path to sendmail
What do you think?
Thanks,
Erik
Den 06/10/2010 kl. 14.35 skrev Erik Cederstrand:
> Den 06/10/2010 kl. 13.07 skrev Erik Cederstrand:
>
>> Is something like the following acceptable? Without risking changes to
>> buildworld/distribution just now, this would allow me to dump contents of an
>> archive an
Den 06/10/2010 kl. 13.07 skrev Erik Cederstrand:
> Is something like the following acceptable? Without risking changes to
> buildworld/distribution just now, this would allow me to dump contents of an
> archive and re-insert them with '0' for mtime, uid and gid before ch
zero always.
Is something like the following acceptable? Without risking changes to
buildworld/distribution just now, this would allow me to dump contents of an
archive and re-insert them with '0' for mtime, uid and gid before checking
checksums, without affecting normal ar behaviour.
Den 06/10/2010 kl. 10.06 skrev per...@pluto.rain.com:
> Erik Cederstrand wrote:
>
>> It seems I can at least normalize the .a files using something
>> like the following to weed out timestamps and uid/gid:
>>
>> % ar -x /usr/lib/libfetch.a
>> % chown 0:0 *
nlib or ld do care. If they don't, we could set
> this timestamp to zero always.
Yeah, I had a look at the code too. I was thinking maybe it would help to add a
modifier to replace timestamps, uids and gids with '0' when inserting a file,
to respect POLA.
Thanks,
Erik
Den 05/10/2010 kl. 15.59 skrev Erik Trulsson:
> On Tue, Oct 05, 2010 at 03:28:36PM +0200, Erik Cederstrand wrote:
>> Hello hackers,
>>
>> I got reminded of a problem I had a couple of years back compressing
>> FreeBSD jails. I was using bsdiff for the compression and
On Tue, Oct 05, 2010 at 03:28:36PM +0200, Erik Cederstrand wrote:
> Hello hackers,
>
> I got reminded of a problem I had a couple of years back compressing
> FreeBSD jails. I was using bsdiff for the compression and found out
> that md5 sums of static libraries (.a files) in /usr
1200728973 0 0 100644 17180 `
---
> http.o/ 1200723258 0 0 100644 17180 `
[...]
I'm wondering if this is necessary, or if this can possibly be turned of with a
knob somewhere.
Thanks,
Erik
st. I'm
testing ClangBSD in a VirtualBox VM which makes it easy to recover after hosing
the operating system.
Erik
a month ago are definitely gone, but I don't think
> dumpspecs is one of them.
Andrius, would it make sense to create e.g. a wiki page tracking the status and
current known problems with compiling ports with clang? Just like there's a
wiki page ClangBSD status.
I think it would make it easier for lurkers to jump in and test things, and
help whittle away at the problems.
Thanks,
Erik
I can not find
> anything similar, except just creating some virtual filesystem on my
> own and obviously this is not what I want to do.
sysctl(3) seems to be the usual way of getting information from the
kernel.
--
Erik Trulsson
ertr1...@student.uu.se
HISTORY section in the manpage says that mktemp(1) originated with
OpenBSD so if anything it is the OpenBSD implementation that ought to
be used as a reference.
If the GNU implementation behaves differently, then I would say it is
likely the GNU version which is
you use mergemaster's -F flag which seems to exist for exactly this
type of situation.
>
> BTW what does cvsup (in CVS mode) do with an RCS file to which only a
> branch tag has been added? How does it mirror such a change? Just
> curious.
It will add the tag to the file
Den 04/06/2009 kl. 18.06 skrev Tim Kientzle:
Erik Cederstrand wrote:
LLVM provides a linker (http://llvm.org/cmds/llvm-ld.html) but "it
doesn't interact correctly with conventional nm/ar/etc" (http://lists.cs.uiuc.edu/pipermail/cfe-dev/2009-June/005296.html
).
In what
m Eli Friedman[1] this is not possible
without at least some hacking.
The LTO work in GNU ld[2] is under GPLv3[3], as is gold[4], which
makes backporting patches a sticky issue.
Erik
[1] http://lists.cs.uiuc.edu/pipermail/cfe-dev/2009-June/005296.html
[2] http://gcc.gnu.org/wiki/LinkTimeOptimizati
mail/cfe-dev/2009-June/005296.html
). There's the ELF toolchain project (elftoolchain.sourceforge.net/)
but a BSD-licensed ld hasn't been developed yet.
What would be the best way to get LTO to work on FreeBSD?
Thanks,
Erik
UTF-32 code point.
>
> Sincerely,
> Alexander Churanov
> ___
> freebsd-hackers@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "fr
NULL0
> #endif
>
> That way, if we are using GCC 4+ we use their __null definition,
> otherwise if we are not c++ we use the standard (void *)0, and then if
> we are 64bit we use 0L, and finally anything else uses 0. A quick
> amd64 kernel compile seems to
0 years'
> (I suppose it is related to either the date listed on the copyright,
> or to the date of some remarkable event for the author).
>
--
Erik Trulsson
ertr1...@student.uu.se
___
freebsd-hackers@freebsd.org mailing list
http://lists.fr
p seconds are evil and a
PITA and essentially impossible to handle 'correctly' since various
standards differ on how they should be handled. What to do about them is
less clear however.)
--
Erik Trulsson
ertr1...@student.uu.se
___
fr
On Fri, Dec 05, 2008 at 12:50:38AM -0800, Garrett Cooper wrote:
> On Fri, Dec 5, 2008 at 12:44 AM, Erik Trulsson <[EMAIL PROTECTED]> wrote:
> > On Fri, Dec 05, 2008 at 12:35:31AM -0800, Garrett Cooper wrote:
> >> On Thu, Dec 4, 2008 at 11:22 PM, Ed Schouten &
cl.
> -Garrett
The !!bar construction to map {0, not-0} to {0,1} is fairly common in C
programming, and I would certainly expect any experienced C programmer to
recognize it.
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
BSD was used in OSX will almost certainly depend
on which version of MacOS X you look at.
It is quite possible that the latest version of OSX uses code from
FreeBSD 5.x, but I guarantee that the first release of OSX did not.
(This is easily seen from the fact the MacOS X 10.0 was first relea
Mach,
and some parts were of course written by Apple themselves (or taken from
other places.)
So, even though it is in part derived from FreeBSD, you should not expect
any sort of binary compatibility between them.
--
Erik Trulsson
[EMAIL PROTECTED]
___
l program for this interface? ancontrol doesn't seem
> to work. wicontrol isn't there
> at all on my system.
ifconfig(8) is used for configuring all network interfaces, wireless as well
as wired. See also the wlan(4) and rum(4) manpages.
-
g edge: why gcc 4.2.0 and not
> 4.2.1 as it is used in 7.X?
Take a close look at the date of the message you were replying to. It is
somewhat old.
(There seems to have been a mail-server hiccup somewhere.)
--
Erik Trulsson
[EMAIL PROTECTED]
___
people,
> mailing lists, books, web pages, etc.) that you want to recommend instead of
> taking some time to help teach me.
You could try picking up one of Tanenbaum's other books: "Structured
Computer Organization", which among
ime' (the value 20 may have to be adjusted) and send that as the last thing
in the shutdown scripts, which should cause the UPS to shutdown shortly
after 'shutdown -p' has turned off the computer.
>
>
> [1] http://www.networkupstools.org/doc/2.2.0/shutdown.html
> [2] http:
ns. like a start till I do a exit or
> quit the application. Is there a utility like
> that ?
You mean something like script(1) ?
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd
On Sun, Apr 20, 2008 at 11:24:32PM -0600, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Erik Trulsson <[EMAIL PROTECTED]> writes:
> : On Sun, Apr 20, 2008 at 12:02:09PM +0300, emily becker wrote:
> : > Hi,
> : >
> : > I have a questi
like this.
Each process runs in its own address space, and therefore the compiler
(actually: the linker) can know exactly where in this address space things
will end up.
(The above is true for FreeBSD and just about all other Unix-derived
systems. Other systems can do things differently.)
get: i386-undermydesk-freebsd
> Configured with: FreeBSD/i386 system compiler
> Thread model: posix
> gcc version 4.2.1 20070719 [FreeBSD]
> zod:~$ uname -a
> FreeBSD zod.isi.edu 8.0-CURRENT FreeBSD 8.0-CURRENT #5: Tue Apr 1
> 13:00:38 PDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/sr
fairly
easily be moved to run on an SMP machine, but it will do a lot of work
that is not necessary under SMP and thus not make very good use of the
hardware.
Moving from SMP to cluster is more difficult. One can emulate the missing
hardware support in software, but this has a very high over
split the files in smaller chunks.
Files are tried in this order:
boot/loader.rc.split
boot/loader.rc.gz.split
boot/loader.rc.gz
boot/loader.rc
However, I only got the plain files to work reliably.
Erik
___
freebsd-hackers@freebsd.org mailing
> sigaction(SIGABRT, &action, NULL); /* reset to default */
> sigprocmask(SIG_SETMASK, &mask, NULL); /* just in case ... */
> kill(getpid(), SIGABRT);/* and one more time */
> exit(1);/* this should never be executed ... */
> }
>
On Sun, Feb 03, 2008 at 04:31:34PM +0100, Dag-Erling Smørgrav wrote:
> Dag-Erling Smørgrav <[EMAIL PROTECTED]> writes:
> > Erik Trulsson <[EMAIL PROTECTED]> writes:
> > > Yep, it seems that GNU sort allocates a quite large buffer by default when
> > > the siz
from stdin.)
A quick check in the source code indicates that it tries to size this buffer
according to how much memory the system has (and according to any limits set
on how much memory the process is allowed to use.)
The size of this buffer can be controlled with the --buffer-size opti
e_Format
which contains several links to documents describing plenty of details.
You can also read the elf(5) manpage in FreeBSD
If that information is not what you are looking for you will have to ask
much more specific questions (which hopefully somebody will be able to
answer.)
ook on databases or distributed systems might also be useful, since
the problems with locking and concurrent accesses are essentially the same
in all these areas.)
>
> I do not know. The hardware I developed earlier was able to handle this by
> aborting both bus cycles.
>
> It was
rantee I will stick with,
> religiously, for now on.
There are two different kinds of output you get at boot time.
The first is all the messages from the kernel as probes and configures all
the hardware. The second is the output from the startup scripts that run
after the kernel has finished
; Hi,
>>>>
>>>> Which of the architectures FreeBSD supports (if any) have strict memory
>>>> alignment requirements? (in the sense that accessing a 32-bit integer
>>>> not aligned on a 32-bit address results in a ha
PR database for a bug related to the
> incorrect control word setting but came up empty handed. If nothing
> has been filed to date I will go ahead and submit a PR.
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
htt
.enable to 1, and find and fix the
> hang-on-close bug in the pts code (if it hasn't been fixed already)
This last option is only available if you are running 7-CURRENT though.
The pts code is not in 6-STABLE (or older.)
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
uter) and then I tried to stop the service using
the normal 'stop' invocation. This of course did not work which was very
annoying. (The above is IMO the proper order to do this - if it worked.)
There has been several times when I have been annoyed by the fact that stop
needs the _enable
d and not-recommended for several years now.
The correct sequence to upgrade is described in /usr/src/UPDATING and does
not involve 'make world'.
Personally I think the better solution would be to remove the 'world' target
completely from the makefiles, but there is proba
; 04. myk by Marvell (88E8056 -- gigabit NIC)
>
The msk(4) driver should support that chip. This driver is also available
in both -CURRENT and 6-STABLE and thus will appear in both FreeBSD 6.3 and
7.0.
--
Erik Trulsson
[EMAIL PROTECTED]
___
ht_info=16778279,200,201&turl=http%3A%2F%2Fkbserver.netgear.com%2Fkb_web_files%2Fn101624.asp&answer_id=6141591#__highlight
for some more information on the different versions of some Netgear
switches.
--
Erik Trulsson
[EMAIL PROTECTED]
___
f
eleting the
file. I sent some mail to the patches maintainer if he could reproduce it.
Anykind of help on how to get this working is appreciated. I'll be glad
to provide any extra info if you just ask.
Cheers, Erik
#0 sccnupdate (scp=0xc09cc140) at /usr/src/sys/dev/syscons/syscons.
Oh and i tested it on 6.1-RELEASE on my own livecd. It works!
Oliver Fromme wrote:
M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Doug Barton <[EMAIL PROTECTED]> writes:
> : Erik Udo wrote:
> : > That's nice. But NetBSDs init.c
PERFECT! Just what i needed. Thanks :)
Oliver Fromme wrote:
M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Doug Barton <[EMAIL PROTECTED]> writes:
> : Erik Udo wrote:
> : > That's nice. But NetBSDs init.c executes /etc/rc before cal
I just made patch. It's supposed to run /etc/rc before chrooting. This is
the NetBSD "way" of doing it. All i can say is that it compiled. So if
anyone can look at it before i get to test it becouse i might be forgetting
something. (i can't even test it now)
diff attached.
O
Nah, forget that patch, it's missing alot of stuff.
On 1/3/07, Erik Udo <[EMAIL PROTECTED]> wrote:
I just made patch. It's supposed to run /etc/rc before chrooting. This is
the NetBSD "way" of doing it. All i can say is that it compiled. So if
anyone can look at
M. Warner Losh wrote:
Oh! I see. Reading the actual code is instructive...
Run /etc/rc, maybe chroot and run a different /etc/rc... That makes
a lot more sense...
Warner
Yes, it allows for me to create the new chroot, becouse in a livecd it's
a disk image. Maybe the /etc/rc is a bit misl
That's nice. But NetBSDs init.c executes /etc/rc before calling
chroot(), and that's what i'm looking for, and for a moment tried to
implement, but i'm not very familiar with FreeBSD code :)
For example that kenv() came to me as a suprise. I'll have to try to
implement the NetBSD way where /et
tiuser mode in a chrooted enviroment? I guess
the only way to do that is to modify init.c
Any help/feedback is appreciated.
Cheers, Erik
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe,
Kris Kennaway wrote:
On Mon, Dec 25, 2006 at 11:17:21PM +0200, Erik Udo wrote:
I'm making a live cd and i just hit a wall with uzip.
I started by creating a null 1GB file, which i filled with FreeBSD.
After that i compressed the file with mkuzip.
Any attempts to mount this compressed
f anyone has any ideas on how to get this working, or what's wrong,
please tell me.
Cheers,
Erik
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
f anyone has any ideas on how to get this working, or what's wrong,
please tell me.
Cheers,
Erik
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
r optimization
the bugs are exposed.
>
> In situations like this, the flag is useful.
Yes, -fno-strict-aliasing is indeed useful to get some old, buggy code (as
well as some new, buggy code) to work until the code in question can be
fixed.
--
Erik Trulsson
[EMAIL PROTECTED]
_
t; >gcc simple-drawing.c -o simple-drawing -L/usr/X11R6/lib -l/usr/X11R6/include
^^
Wrong options letter. You should use '-I' (upper case 'i'), not '-l' (lower
case 'L')
>
ionfs/
Should i use this?
Can i mount one singe memory device on top of the root-directory? I'd
want my whole system writeable.
If not, then can aynone please tell me how i can have a stable,
writeable livecd.
I'm thinking of using FreeBSD 6.
m already has zlib 1.2.3 (-CURRENT since about 6 months ago,
and RELENG_6 since about a week ago.)
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe,
being that the MacOS is
> derived
> from kernel of the FreeBSD.
>
> It will be that somebody could explain this better to me.
>
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/
>
> -Pat
> ___
> freebsd-hackers@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nt to the file name associated
with the file being executed. The list of arguments must be terminated
by a NULL pointer.
[...]
Note that it says "one or more pointers to null-terminated strings".
NULL is not a pointer to a null-terminated string, which means that you must
have at least one non-NULL pointer before the teminating NULL.
--
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sly pointed to by
foo and will still be filled with garbage.
If your program needs zeroed memory you should use calloc() or do the
zeroing yourself - malloc doesn't do it.
What is guaranteed is that any garbage in the memory returned by
malloc() will have been created by the same process, so that
1 - 100 of 171 matches
Mail list logo
