[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#669647: Hurd features [Was: ITP: hurd-cvsfs -- CVS virtual filesystem for the GNU Hurd]



Roger Leigh, le Mon 23 Apr 2012 10:43:00 +0100, a écrit :
> > They are already there.
> 
> OK.  I was informed otherwise when I was working on all the
> tmpfs-related code.

Things evolve, we do spend time on useful features :) Tmpfs has recently
been fixed.

> Does Hurd support ext3/4 yet?

No.

> > > - sysfs
> > 
> > Err, I don't think it's a good idea to let people think it is ok to use
> > extremely-linuxish things there.
> 
> kFreeBSD supports both linprocfs and linsysfs.

Linsysfs is extremely small: from what I see on asdfasdf, it only
exposes two bits of information for each scsi host.

> If you're going to integrate well with the rest of the Debian system,
> the reality is that this stuff is needed.

/sys is a moving thing, and full of a lot of details.  I believe BSD
people will agree that they don't want to spend time on that.

> > > Yet we are carrying
> > > around large amounts of code and extra initscripts to generate
> > > mtab for the only system which does not support /proc/mounts
> > > (Hurd).  A procfs translator (even an incomplete one) would
> > > allow all this (barely tested) cruft to be dropped.
> > 
> > We have an incomplete procfs already.  It doesn't have /proc/mounts,
> > because it's not a trivial thing to implement: since mounts are
> > distributed, there is no central place where filesystems are to be
> > recorded.  There are plans to somehowe build one.  In the meanwhile
> > things are working already.  I don't think spending time on a feature
> > just to remove some existing code is the best way to spend our time,
> > either.
> 
> It's not just a case of "working already".  I spent several days
> writing and testing all that code.  From scratch.  Just for Hurd.

Ah, we weren't aware of that.

Samuel



Reply to: