1wk...@gmail.com writes:
> Unfortunately, the map_at_zero sysctl didn't work for me. The
> following massage still recorded in dmesg.
>
>> linux: pid 1378 (acroread): syscall inotify_init not implemented
>
> I set the sysctl variable just before the kernel boot. After loading
> kernel and module
Unfortunately, the map_at_zero sysctl didn't work for me. The
following massage still recorded in dmesg.
> linux: pid 1378 (acroread): syscall inotify_init not implemented
I set the sysctl variable just before the kernel boot. After loading
kernel and modules and before booting the kernel, esca
Boris Samorodov writes:
> darc...@gmail.com (Denise H. G.) writes:
>
>> the same problem here for the port on 8.0-RC1.
>> And I tried to use zh_CN-acroread8, but it does not even start up,
> just
>> aborts before the GUI appears.
>
> Try this:
> -
> # sysctl security.bsd.map_at_zero=1
> -
darc...@gmail.com (Denise H. G.) writes:
> the same problem here for the port on 8.0-RC1.
> And I tried to use zh_CN-acroread8, but it does not even start up, just
> aborts before the GUI appears.
Try this:
-
# sysctl security.bsd.map_at_zero=1
-
If that helps then updating to a more res
1wk...@gmail.com writes:
> Hi,
>
> Similar problem.
> I'm using ja-acroread9 from ports on 8.0-RC1.
> The following message was recorded.
>
> linux: pid 1378 (acroread): syscall inotify_init not implemented
>
> Does it mean some features are missing in linux emulation environment?
>
> # I'm not su
Hi,
Similar problem.
I'm using ja-acroread9 from ports on 8.0-RC1.
The following message was recorded.
linux: pid 1378 (acroread): syscall inotify_init not implemented
Does it mean some features are missing in linux emulation environment?
# I'm not subscribing this ml, sorry.
> On Thu, Jun 18,
