On Thu, Sep 05, 2019 at 03:08:52PM +0300, Furkan İnciroğlu wrote: > Hi there, > > I have just finished LFS and I want to start BLFS. I want to ask you about > BLFS disk partition. I have already got 32 GB LFS disk(sda) and I created new > BLFS virtual machine and attached this disk on new machine . Should I create > a secondary disk(sdb) for BLFS? and mount this new disk on somewhere? Could > you help about it? > > Best regards,
Your question sounds odd, at least to me. So, I'll try to work through a few points. Sorry, this will be somewhat long. First, in linux you rarely use the whole disk (sda, sdb) - you create partitions (either the old dos-style MBR partitions, or the newer EFI partitions). A partition *can* occupy the whole disk, so for my '/data' storage (3GB drive) I need to use gpt partitioning to allow a partition bigger than 2TB, and I then use a single sdX1 partition. Second, partitions are give filesystems wheich are mounted at mountpoints. If the only purpose of the filesystem is to hold data (my example above) it can be mounted at a non-standard place such as /data or /scratch or perhaps under /mnt or /media, e.g. /media/photos. But that is not a great idea for programs and libraries. So, if your system is to store a lot of data then a separate disk image might be useful. In BLFS, we usually put programs in /usr, but for some things /opt/somewhere is used (e.g. /opt/texlive, /opt/kde). Those might be places to mount an extra partition if you are running out of space. If your 32GB becomes short of space, even after deleting old things you do not need, then you might want to move *some* directories to the new disk. I haven't used virtual machines for some time, and when I did they were always for very limited purposes, small and containing only one system. And having built one, I then used that to build the next one on a different "disk" when I needed to. In general, source files and whatever is in /home are usually the things which eventually take large amounts of space. Oh, and building large (desktop) packages (browsers and their engines) needs a lot of disk space. While you are only using virtual machines, if you want to try out different combinations of packages you might want to back up the base LFS system to a separate "disk" and eventually load that to try different sets of packages (e.g. different desktops, or different mail systems, or different webservers, depending on what you want to do). But of course, you should always back up a system in case of accidents. Summary: you need to think about what you want to do on this system (e.g. for a webserver a system can be much smaller than for a full-fat desktop), and make the partitions to suit. I'm guessing that if the system logs don't eat all your space (been there with nouveau and also with kernel bugs) then you can manage happily with 32GB. N.B. for *real* hardware, I would partition differently with at least /boot, two systems (current, next), swap if needed, /home. OTOH, some people do not separate /home and copy the files that they care about when creating a replacement system. ĸen -- thread 'main' panicked at 'giraffe', /tmp/rustc-1.32.0-src/src/test/run-fail/while-panic.rs:17:13 -- http://lists.linuxfromscratch.org/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page Do not top post on this list. A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? http://en.wikipedia.org/wiki/Posting_style
