On Fri, Nov 08, 2002 at 01:15:01PM -0500, Adam Thornton wrote:
> On Fri, Nov 08, 2002 at 10:58:30AM -0600, Rick Troth wrote:
> > >         If you use the cmsfs stuff, that information can all be on the
> > > 191 disk and read by the startup scripts.
> > What about a CMSFS that can do directories and specials (device files)
> > akin to the UMSDOS hack?
>
> If you create a CMS file called PROGRA~1 DIR I'll have to murder you.
> Just so you know.  Other than that, sure, sounds like a plan--I assume
> you mean that you use some filesystem convention like a file which
> always has some particular name, which contains a CMS filename to Unix
> directory mapping?

Perhaps (though it might be more work) use the same naming convention as is
used to encode long filenames on the ISO9660 filesystem, just to stick to a
well known and accepted convention?

I would *love* to see a CMSFS that can support things like device files so
we can finally put /dev somewhere other than the root filesystem, so / can
truly be made RO.  I worked on that using initrd, but cmsfs  would  be  so
much nicer (as long as it is efficient).  Then again, if devfs keeps going
the way it is, the need for a writable /dev may finally disappear!   I  do
fear though that it won't go all the way :(

        Kris

Reply via email to