Hi,
I'm trying to get htop to work, but that requires linproc.
So building and loading linproc I get:
l# kldload linprocfs
kldload: can't load linprocfs: Exec format error
So I go Grrrmbbblll, try som more things, rebuild kernel and modules...
Only to find out this morning in the reports that /v
On Thu, Sep 06, 2012 at 09:22:47AM +0200, Willem Jan Withagen wrote:
> # kldload linux
> kldload: can't load linux: Exec format error
>
> This time I know I have to look in to messages:
> But that is not so easy:
> Sep 6 09:14:02 zfs kernel: link_elf_obj: symbol
> freebsd32_exec_copyin_args undef
06.09.2012 11:22, Willem Jan Withagen пишет:
Hi,
I'm trying to get htop to work, but that requires linproc.
So building and loading linproc I get:
l# kldload linprocfs
kldload: can't load linprocfs: Exec format error
So I go Grrrmbbblll, try som more things, rebuild kernel and modules...
Only
On 2012-09-06 11:29, Борис Самородов wrote:
[stuff about problems with loading linux.ko deleted ]
>> So how do I get freebsd32_exec_copyin_args defined
>>
>> Any insights appreciated,
>
> Is it FreeBSD-amd64? (uname -a is a good start)
> If yes, have you got i386 compatibility? (kernel con
Hi,
i'm trying to setup some fault management for ZFS. My first idea would
be to use devd. It looks like PCBSD already has some examples for this
[1]. Is there any documentation regarding which subsystem and types
exist for ZFS ?
Regards,
Leon
[1] http://lists.freebsd.org/pipermail/freebsd-stable
schrieb Attilio Rao am 09.08.2012 20:26 (localtime):
> On 8/8/12, Harald Schmalzbauer wrote:
>> schrieb Pavel Polyakov am 06.03.2012 11:20 (localtime):
> mount -t unionfs -o noatime /usr /mnt
>
> insmntque: mp-safe fs and non-locked vp: 0xfe01d96704f0 is not
> exclusive locke
schrieb Harald Schmalzbauer am 06.09.2012 17:52 (localtime):
> schrieb Attilio Rao am 09.08.2012 20:26 (localtime):
>> On 8/8/12, Harald Schmalzbauer wrote:
>>> schrieb Pavel Polyakov am 06.03.2012 11:20 (localtime):
>> mount -t unionfs -o noatime /usr /mnt
>>
>> insmntque: mp-safe
Hello,
for people needing to setup various production systems, multiple times
for the same basic hardware but for different purposes, and mainly for
people installing embedded systems, my collection of scripts/Makefiles
named "deploy-tools" may be of interest.
It makes use of standard FreeBSD mak
Hello,
I'm playing with releng_9_1 on a neat intel server, pre-production.
Since ESXi5.0-768111 doesn't supprot the second on-board NIC/PHY of my
BearTooth board, I tied to pass through the device into my FreeBSD VM.
The NIC get's recogniced, but isn't usable because "Setup of Shared code
failed"
82579 is not a NIC, its a PHY, and it you look at the current code you will
see the support
is in there. So the real question is what the actual NIC is, how about a
pciconf -lv?
Next, how are you trying "to pass through the device into my FreeBSD VM",
what is
the virtualization environment.
Widel
10 matches
Mail list logo