Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 09 Sep 1997 14:44:05 -0500
From:      Prashant Dongre <pdongre@opentech.stpn.soft.net>
To:        Greg Lehey <grog@lemis.com>
Cc:        Satoshi Asami <asami@cs.berkeley.edu>, FreeBSD Questions <questions@FreeBSD.ORG>, FreeBSD Hackers <hackers@FreeBSD.ORG>
Subject:   Re: /: file system is full
Message-ID:  <3415A705.96635908@opentech.stpn.soft.net>
References:  <19970909085107.25727@lemis.com> <199709090659.XAA18299@silvia.HIP.Berkeley.EDU> <19970909163248.43041@lemis.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Greg Lehey wrote:

> On Mon, Sep 08, 1997 at 11:59:37PM -0700, Satoshi Asami wrote:
> >  * The other alternative is, of course, to recommend a 45 MB root slice.
> >  * There's nothing so holy about /compat that it *should* be in the root
> >  * slice, but I don't like gratuituous symlinks either.  I'm copying
> >
> > IIRC, someone mentioned that /compat might be needed at startup before
> > mounting anything, and that is the reason why it is in /.
>
> Sure, that's the classical reason for putting something in /.  But I
> can't see that we're going to need Linux programs before /usr is
> mounted.
>
> > OTOH, this question seems to come up quite often and is quite a thorn
> > on our collective sides.  I would love to see it moved to
> > ${PREFIX}/compat (where I suspect it lives on most people's machines
> > anyway) if that is only a case of vast minority.
>
> The worst problem I could see with that would be the transition.  I'm
> copying -hackers; what do you guys think?
>
> (Ducks until Jordan's answer has died down :-)
> Greg

I am also having the same problem......

Can some of you throw light on this why and how can I overcome this.....

Sorry for not giving attention to this thread from the beginning......

Prashant.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3415A705.96635908>