Date: Fri, 27 Aug 2010 01:45:33 -0400 From: Anish Mistry <mistry.7@osu.edu> To: freebsd-current@freebsd.org Cc: Kostik Belousov <kostikbel@gmail.com>, Ed Schouten <ed@80386.nl>, Ian FREISLICH <ianf@clue.co.za> Subject: Re: fusefs-kmod broken? Message-ID: <201008270145.40699.mistry.7@osu.edu> In-Reply-To: <E1OnYSy-0001e9-Vv@clue.co.za> References: <E1OnY55-0001YZ-0L@clue.co.za> <20100823134723.GC64651@hoeg.nl> <E1OnYSy-0001e9-Vv@clue.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Monday 23 August 2010 10:57:40 Ian FREISLICH wrote: > Ian FREISLICH wrote: > > So, in this case is the fusefs module broken? I'm guessing it is. > > I don't like the way fuse_fileops is initialised in fuse4bsd. I > > would prefer for the struct to be zeroed and then the fo_xxx > > implimented bits set as appropriate. That way when the struct is > > changed, you don't get stung again. > > I am an idiot - that will have no effect. This patch needs to be > included in sysutils/fusefs-kmod/files Would you file a PR with the patch accounting for the correct __FreeBSD_version__? Thanks, -- Anish Mistry [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iEYEABECAAYFAkx3UQQACgkQxqA5ziudZT0PbQCgyzpcJSFupM20S5rsGh3osZw3 Nb8AnjO1XKofGyaNsqhRF8/AbXSjEjOK =ablL -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201008270145.40699.mistry.7>