Can you look into PR kern/29844 as well?
I think after your fix, it should fail even when invoked by super
user.
Regards,
In article <[EMAIL PROTECTED]>,
Seigo Tanimura <[EMAIL PROTECTED]> wrote:
>On Wed, 27 Feb 2002 15:44:23 +0900,
> HIROSHI OOTA <[EMAIL PROTECTED]> said:
oota> The fo
Re: "Re: /dev/rtc not configured message when starting VMWare2 on -current"
In article <[EMAIL PROTECTED]>,
Munehiro Matsuda <[EMAIL PROTECTED]> wrote:
>I have a hack^Wpatch that should fix your problem.
I think you need to prevent returning the value of uninitialized
variable (``error'')
Re: "Re: /dev/rtc not configured message when starting VMWare2 on -current"
In article <[EMAIL PROTECTED]>,
Munehiro Matsuda <[EMAIL PROTECTED]> wrote:
>I have a hack^Wpatch that should fix your problem.
I think you need to prevent returning the value of uninitialized
variable (``error'')
Hi, all,
Due to mail trouble, I couldn't join this thread, but I submitted PR
via web on this problem & fix (kern/31122). Your patch seems better
than what I attached to the PR (I didn't care about gid's in my patch).
My PR should be closed when the patch is commited.
In article <[EMAIL PROTECT
(I once tried to send this message which did not seem to reach to the
list, so I'm trying again. If you see this message twice, sorry for
it)
In article <[EMAIL PROTECTED]>,
Takanori Saneto <[EMAIL PROTECTED]> wrote:
>Hi, folks,
>I think there is problem about the
Besides procfs_rlimit(), there are several undefined symbols in
procfs.ko:
% nm /modules/procfs.ko | egrep ' U procfs_'
U procfs_read_fpregs
U procfs_read_regs
U procfs_sstep
U procfs_write_fpregs
U procfs_write_regs
Is this OK?
--
さねを mailto:san...@b
