Date: Wed, 21 Nov 2018 11:13:59 +0100 From: matias@pizarro.net To: =?UTF-8?Q?T=C4=B3l_Coosemans?= <tijl@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: 13.0-CURRENT: Linux syscall inotify_init regression? Message-ID: <55b43c92a9c3f6ae7fac909ea355b8c1@pizarro.net> In-Reply-To: <20181121104602.2a398d93@kalimero.tijl.coosemans.org> References: <21eed091d01a216a4fb2ff85c5199e31@pizarro.net> <20181121104602.2a398d93@kalimero.tijl.coosemans.org>
index | next in thread | previous in thread | raw e-mail
I see, what I took for the symptom of the absence of the stub is actually the stub doing what it should be doing 8P No, the kernel doesn't panic, Sublime just dies. Now that I know that the stub is actually there, I realize it is probably a problem with Sublime itself. I have now installed the previous version (sublime build 3143) that I knew was working in 12.0-CURRENT and there you go, it works. Thanks for your help and sorry for the noise :D On 21/11/2018 10:46, Tijl Coosemans wrote: > On Wed, 21 Nov 2018 10:22:27 +0100 matias@pizarro.net wrote: >> Hi Tijl and all, >> >> Thanks for r340631 and r340674. I am currently running r340703 and I >> thought this might be of interest to you: I get the following error >> when >> trying to run Sublime Text 3 on X: >> >> kernel: linux: pid 104 (io_worker): syscall inotify_init not >> implemented >> >> I understand there should be a stub in place, even though the inotify >> syscall is not supported, shouldn't there be? > > Yes, there is a stub that prints the message you see. What exactly is > the problem? Does the kernel still panic? Can you provide the > core.txt > file in that case? > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org"help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55b43c92a9c3f6ae7fac909ea355b8c1>