Space saver: mount --bind mention in the book?
ewt at avajadi.org
Tue Oct 1 04:36:11 PDT 2002
Maybe a use case would help in understanding the problem with the mount --bind approach:
I regularly create new servers by putting a blank harddrive in the cradle of my workstation and building an LFS system on that harddrive. I then take that harddrive and put it in the system I'm building, mostly servers (which is irrellevant, but let's try and be a bit social here, too, eh? :) .
Now, if I were to use /usr/src on the workstation as the /usr/src on the LFS partition aswell by using mount --bind, I wouldn't have access to those files after I'd moved the harddrive. Granted, this may sometimes be a desirable behaviour under special circumstances, but for most cases, it would just make life harder.
Ian Molton <spyro at f2s.com> uttered the following on Mon, 30 Sep 2002 22:29:04 +0100:
> Sorry, I cant agree.
> for example, if you use mount --bind to access the packages you want to
> compile, then you acttually are using LESS stuff copied from the host,
> as those packages stay on the host and are never copied to the new LFS.
Eddie Olsson <ewt at avajadi.org>
Fingerprint: 2778 87FA 6708 58C0 8261 DFEB C8FA 4591 6E36 FCCB
Key ID: 6E36FCCB
`Those who desire to give up freedom in order to gain security will not
have, nor do they deserve, either one.' - Thomas Jefferson
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-dev' in the subject header of the message
More information about the lfs-dev