Subject: Re: Strange behaviour after installing arla
To: Torsten Harenberg <harenberg@physik.uni-wuppertal.de>
From: Love <lha@stacken.kth.se>
List: port-alpha
Date: 06/16/2003 01:06:44
=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Torsten Harenberg <harenberg@physik.uni-wuppertal.de> writes:
> On Sun, 8 Jun 2003, Love wrote:
>
>> Your kernel isn't compiled with INSECURE, so LKM's can't be loaded becau=
se
>> securelevel > 1.
>>
>> Load it in the boot sequence (when securelevel isn't set) or compiled a
>> kernel with option INSECURE.
>
> Hi Love,
>
> thanks for your quick reply. Your hint works, at least arla comes up now
> :). But: as soon as I access any AFS resource, I got a kernel panic. Log
> says:
[...]
> Is there anybody out there who's running arla on NetBSD/alpha, with whom I
> could syncronise kernel and arla settings?
I think the kernel module is build w/o DIAGNOSTIC, but the alpha GENERIC
kernel is built with option DIAGNOSTIC, I think that causes your problem.
Love
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (NetBSD)
iQIVAwUBPuz8BhZyDLTSep3UAQJvpxAAs2KHU5KUMfkyyvvZ8HHFuYD1OmxzwD6D
IQnu4isNxN7GbKIErq1peYN3Xel4XNw/mhFdlg3Sj3IjIn4SmpooRXAdcgI92KBH
CP5G3o0z6jIHj0qB+L3ySMg91GgJ4UqDOWzZGdZzaYbT5l6W3cHJqo1igcJr14XQ
2HMxXVXJn3ENZrlFLtdDvsIZU6slZR3fEuhkpwiPQVQQWxiP3sbIBt7Vs/1lPGO5
U3a8zfKNQu7RZTs1UkYdR7+CpNumxVBbO9R6bHY3Z0t7wOY3XuUha76BjPEU59Fl
L7EPIr27HDHoSSB4JvpXzyLMROipGap1pYAEe7JLFC8IeEjo+Bekeq3Gh7zibLlw
qeLRVQki0LIzYyZB5gNrOYznsGAX/VP+p0BU9D6+30G8/WZ+AJ12KAtF3f03otv0
bi9SSkhlyiG59PcK8oznEGnoo+sBjLuUg7NPcfXqXv9++/dlPC4xfNOhuwLIr3MS
wTb/EOUbzuZnBGXuTG3azLxEmNXzX4iKYQvl5XsOMJL5WScAj8tmNsCgLryZghGh
XEf83YVOGE/bKpT5qH5EBsaAHq0sB2t5yvgIopIlcJcwhz3TdVs7Nwro4m6vHLD0
sWPS7Jti/zunY887CK/DfYSd+W4Uj4TJDkXB3tm61oIAbtXlxMx01dwgVmXDaHsJ
eyUTK0jp6SI=3D
=3DlGK3
=2D----END PGP SIGNATURE-----