I second this..
however we have miscfs,
How should we treat that? is miscfs really "trivialfs"?
should stuff move?
fs/miscfs?
in the same vein should netinet move under net? (hard because of the
includes in /usr/include.) The sys tree is getting ot be a bit unwieldy.
Maybe we nned to start doing this?
julian
On Fri, 3 Dec 1999, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Ustimenko S
> emen writes:
> >Hi!
> >
> >Promised somewhere in spring, i am now
> >almost ready to put HPFS driver into current.
> >
> >So i have question:
> >Where have to go driver sources
> >src/sys/hpfs or src/sys/i386/hpfs, or something else ?
> >Where have to go mount_hpfs:
> >src/sbin/i386/mount_hpfs?
>
> The code for a filesystem should not be architecture dependent.
>
> I would advocate for sys/fs/hpfs.
>
> We have too many filesystems cluttering up /sys already, we should
> start to cluster them in sys/fs
>
>
> --
> Poul-Henning Kamp FreeBSD coreteam member
> [EMAIL PROTECTED] "Real hackers run -current on their laptop."
> FreeBSD -- It will take a long time before progress goes too far!
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
