Date: Fri, 3 Apr 2009 13:26:58 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Alexander Leidinger <Alexander@leidinger.net> Cc: freebsd-emulation@freebsd.org Subject: Re: HEADSUP: new linux infrastructure ports are committed Message-ID: <20090403102658.GU31897@deviant.kiev.zoral.com.ua> In-Reply-To: <20090403122251.43551d4yds72vq1w@webmail.leidinger.net> References: <23488525@bb.ipt.ru> <alpine.BSF.2.00.0904021222330.20710@thor.farley.org> <20090403082742.13151vhzr5fcjfdw@webmail.leidinger.net> <20090403095127.GS31897@deviant.kiev.zoral.com.ua> <20090403122251.43551d4yds72vq1w@webmail.leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--oXWu0ZmOTEBdKpMN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 03, 2009 at 12:22:51PM +0200, Alexander Leidinger wrote: > Quoting Kostik Belousov <kostikbel@gmail.com> (from Fri, 3 Apr 2009 =20 > 12:51:27 +0300): >=20 > >On Fri, Apr 03, 2009 at 08:27:42AM +0200, Alexander Leidinger wrote: > >>Quoting "Sean C. Farley" <scf@FreeBSD.org> (from Thu, 2 Apr 2009 > >>12:33:42 -0500 (CDT)): > >> > >>>What cannot be MFC'd besides TLS and NPTL? For syscalls that cannot > >>>be MFC'd, can calls be written that help to some degree without > >>>breaking ABI? The wiki page[1] is incomplete on what changes are to > >>>be MFC'd. I can say that fstatat64() seems popular (called by rm) > >>>in /var/log/messages. > >> > >>*at() can not be MFCed as it would change the native VFS ABI (Roman > >>implemented the FreeBSD side of *at() calls to be able to emulate the > >>linux *at() calls). > >It can be MFCed with low-impact KBI breakage, and I have re@ approval >=20 > You need to rebuild all FS then, don't you? Would FUSE in this case =20 > refuse to load when not rebuild? If not, what would be the impact of =20 > not rebuilding but loading it? No, fs modules are actually immune, mostly. What changes is the namei() binary interface. It is needed for new ZFS too, for what it worth. >=20 > >for the MFC. What actually stopped the merge is an issue with missed > >audit bits for dirfd descriptors. They are missed in HEAD too, so > >8.0 needs some action to finish this. >=20 > Thanks for the info, > Alexander. >=20 > --=20 > Scintillation is not always identification for an auric substance. >=20 > http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 > http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 --oXWu0ZmOTEBdKpMN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAknV5HEACgkQC3+MBN1Mb4hPTQCffvDYty9D14/J3VCcHc43XYFV tLIAoINlIWxRYWcHod/HYth6MERbcZZq =VKKb -----END PGP SIGNATURE----- --oXWu0ZmOTEBdKpMN--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090403102658.GU31897>