On Sat, Jan 11, 2014 at 03:14:38PM -0500, William Darryl Jackson wrote: > On 01/11/2014 02:51 PM, Chris Staub wrote: > > On 01/11/14 14:47, William Darryl Jackson wrote: > >> On 01/11/2014 02:33 PM, Chris Staub wrote: > >>>> > >>> Your output says there is something mounted on /media/lfs, yet you keep > >>> saying you are assigning LFS=/mnt/lfs. > >> I was trying to follow the instructions precisely. I agree this seems to > >> be the cause of the problem. This is an external drive that auto mounts > >> to the (user) media folder, and (root) dev folder. The only reason it > >> says media/lfs is because I added a label in gparted. Debian is using > >> uuid identifiers - which is causing me problems. Would it help if I > >> replaced LFS=/mnt/lfs with something else? Also, I have 2 partitions on > >> that external drive. They both mount showing 500GB, when the drive is > >> only 500GB. > >> > >> Thanks. > >>
Using automounting for where you intend to build LFS is probably a bad idea. Actually, in my personal view automounting is always a bad idea : I don't expect the system to try to second-guess what I want to do ;) You need to be root at certain places in the LFS build, so you might as well be root to mount /mnt/lfs. Just remember to become user LFS when the book does. We used to have certain things which _required_ /mnt/lfs, now I believe you can mount the build anywhere and have a reasonable chance of success if you make the consequential changes. But if it breaks, you get to keep both pieces. So, /mnt/lfs is what we recommend. > > Sorry, but if you really need to ask this, LFS is just too advanced for > > you. I suggest going here - > > http://www.linuxfromscratch.org/lfs/view/7.4/prologue/prerequisites.html > > - for starters, and learning about how to actually use Linux, especially > > on the command line, before attempting something like LFS. > That was a bit harsh. I have been using command line for 3 years. That > is long enough for me to attempt to learn more about Linux, which is > what I thought LFS is all about. I have learned enough now to not bother > the list with silly questions. > I _will_ reiterate that you seem to have a fundamental problem with how you are mounting the external drive : each partition should be smaller than the total size of the drive, and when both are mounted you ought to be able to see different partition numbers, and sizes, in the output from 'mount' and 'df'. Debugging this problem for yourself will help you when it comes to other problems with your new LFS system. LFS *is* about learning linux - but mostly in the sense of how the various packages fit together to produce a usable minimalist system. By paying attention to the details of how each package is built, you will perhaps learn a little about how to use sed and patch. But other common tools will only get brief mentions. I think awk probably gets used in checking the host requirements. Some people have apparently built LFS "to learn linux"- for me, that would have been unnecessarily difficult. Read the links Chris pointed to, read the book _before_ you try to follow it (to get an overview of what is to be done), and then if you think you are ready, please check the host requirements. I will also add that I recommend that people build and install a kernel before trying LFS (in situations where that is possible) - i.e. use an upstream kernel, come up with a .config which boots *without* an initrd [ build in the root filesystem and whatever you need for your disk drives ], test, strip things out and/or add other things until the kernel both boots and does everything you need it to do. For this, edit /boot/grub.cfg as root [ review what the book says for kernel configs ] AND add your own identifier in the EXTRAVERSION so that a later rebuild to get a better config will not overwrite the modules from the current attempt. Of course, some people leave the fun of finding a useful kernel config until they have completed LFS. Personally, I find it a lot easier to debug any problems on my own builds (yes, I still get boot problems) - mostly from upgrades to the BLFS packages which I build before I boot, e.g. for nfs, but I can still remember that I had issues when I updated my (very) old server system to LFS-6.8 because of config changes I had forgotten about over the years - if the kernel .config is "known good" : people get all sorts of one-off problems when building LFS for the first time, e.g. by botching one of the packages [ /me scowls at ncurses and libz ]. And if you do get more problems when you are building LFS, please mention where you are in the book when you ask for advice. Have fun, building and booting LFS isn't about ticking boxes on a ToDo list. ĸen -- das eine Mal als Tragödie, dieses Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
