On Mon, 5 Aug 2019 18:04:00 -0600, Grant Taylor wrote:
> > Don't you have to go through some extra hoops (a flag to the mount
> > command or something) to mount over a non-empty directory?
>
> Nope.
>
> I don't recall ever needing to do anything like that in Linux.
Fuse complain about this,
On 8/5/19 8:45 PM, Grant Taylor wrote:
Even bigger hack.
I wouldn't be me if I didn't lob these two words out there:
mount namespaces
/me will see himself out now.
--
Grant. . . .
unix || die
On 8/5/19 6:28 PM, Jack wrote:
However, I keep wondering if an overlay file system might not be of
some use here. Start with /bin, containing only what's necessary to
boot before /usr is available.
I wonder how much of what would need to be in the pre-/usr /bin
directory can be provided by
On 2019.08.05 19:52, Ian Zimmerman wrote:
On 2019-08-04 19:36, Grant Taylor wrote:
Create the bin and sbin directories inside of the /usr directory
that is the mount point so that they are on the underlying file
system that /usr is mounted over top of. Then copy the needed
binaries to
On 8/5/19 5:52 PM, Ian Zimmerman wrote:
Don't you have to go through some extra hoops (a flag to the mount
command or something) to mount over a non-empty directory?
Nope.
I don't recall ever needing to do anything like that in Linux.
I do know that other traditional Unixes are more picky
On Mon, Aug 5, 2019 at 4:53 PM Ian Zimmerman wrote:
>
> Don't you have to go through some extra hoops (a flag to the mount
> command or something) to mount over a non-empty directory?
>
>
Not in my experience, I've done it many times (sometimes even on purpose :)
)
--
Manuel A. McLure WW1FA
6 matches
Mail list logo
