[EMAIL PROTECTED] wrote:
http://lists.freebsd.org/pipermail/freebsd-hackers/2005-December/014986.html
The problem is that libnet defines ether_addr without regard for the fact
that it's defined in our system headers. This is a bug in libnet, not
FreeBSD.
No one claimed otherwise -- hence
On Sat, 31 Dec 2005, Armin Pirkovitsch wrote:
I have some troubles with my notebook and any version of FreeBSD (starting
with 6 since my sata controller wasn't supported earlier). It looks like as
it would end up in a deadlock which means i have no access to the debugger
nor to any other
Martin Cracauer wrote:
It's more likely to be a general instability from broken hardware.
Use prime95 (ports/math/mprime) to test your processor and thermal
stability (36 hours or so), and memtest86 (seperately).
I guess I should have mentioned that other systems work fine and run
stable
Robert Watson wrote:
On Sat, 31 Dec 2005, Armin Pirkovitsch wrote:
I have some troubles with my notebook and any version of FreeBSD
(starting with 6 since my sata controller wasn't supported earlier).
It looks like as it would end up in a deadlock which means i have no
access to the
On Sun, 1 Jan 2006, Armin Pirkovitsch wrote:
Robert Watson wrote:
I guess one of those parts creates the trouble, but I have no idea how to
trace it... Is there a way to run the whole thing in some kind of
debugger? Or is there a diffrent way to locate the problem?
The usual first step to
Howdy,
One of my new years resolutions was to become a bit more masochistic, so I
set out to see if I could build a kernel (and modules) without options
INET on HEAD.
This works flawlessly for the kernel part, but there are tons of issues when
building modules -- various problems encountered
Use prime95 (ports/math/mprime) to test your processor and thermal
stability (36 hours or so), and memtest86 (seperately).
Please use memtest86+ and not memtest86.
--
unzip ; strip ; touch ; grep ; finger ; mount ; fsck ; more ; yes ;
fsck ; umount ; sleep
Masanori OZAWA wrote:
[...]
Nice work! This is just a works for me. In only find some issues with
permissions that were already present in the previous implementation of
unionfs. Some of them are partially corrected in the useful copymode.
I mailed the details to the author.
the following
8 matches
Mail list logo
