Re: ``struct stat'' issue

> I.e., the usec / nsec value of variable `st' (``struct stat'') isn't set > at all. In my reading of the used ``struct ext2_inode'' (variable `di') > there indeed is nothing better than the sec value being provided. Should > we explicitly set the usec / nsec value of `st' to zero? Yes. diskfs_

Re: ``struct stat'' issue

> On follow-up: do we want to modify all of the Hurd libraries and servers > (plus the GNU Mach maptime interface!) to also work on ``struct > timespec'' (with nanosecond resolution) instead of ``time_value_t'' (with > microsecond resolution; as it is used at the moment)? I'd leave Mach alone for

Re: ``struct stat'' issue

Off hand that looks fine to me. ___ Bug-hurd mailing list Bug-hurd@gnu.org http://lists.gnu.org/mailman/listinfo/bug-hurd

Re: fatfs compilation error

Hello! On Mon, Jun 11, 2007 at 01:19:30PM +0200, christian nastasi wrote: > I decided to work on a HURD public machine to develop my vfat translator. > First of all I retrieve the latest version of the fatfs translator, then I > decided to build it "stand-alone". > So I created a little makefile t

Re: ``struct stat'' issue

Hello! On Fri, Oct 05, 2007 at 03:29:27PM +0200, I wrote: > On Sun, Jun 10, 2007 at 11:35:20PM +0200, I wrote: > > Some months ago I created some patches for the ``struct stat'' issue > > (). Perhaps now the time has come > > for someone to review them? > > I