On Thu, Dec 30, 2010 at 09:45:40PM -0500, Blake Morgan wrote:
> The reason I have been avoiding the differen didstro is because I'm confused
> about the partitioning. Would I not partition durin the install and do it in
> the shell? Would I follow the books instructions during the install? I don't
> understand how to partition for LFS using another distro.
In that case, I suspect you are not yet ready for LFS. But, I've
been using PCs since the 1980s and partitioning holds no fears for
me. I've also seen people manage to complete their LFS systems even
though it appeared to me that they weren't ready. So ...
The disk needs some partitions on it. On one of those you will
create the LFS root ('/') system. The other partitions are
"whatever you need". If this is going to be a desktop, I recommend
you create at least two partitions for '/' (the current system you
are building, the next, and perhaps a third - maybe more than this
if you wish to follwo the LFS-development book), a swap partition
(or maybe two of those if you suspend to disk - one for swap, the
other for suspending), somewhere for /home, and a /boot partition
(at the inside end of the disk - the slowest part) because that
makes switching from one LFS install to a later one fairly easy.
Extended partitions. The primary partitions limit you to a maximum
of 4 partitions, which probably isn't enough.
Beyond that, you might feel the need to put /var on a different
partition (so, again, probably a _pair_ of these for current and
next LFS). People have suggested that e.g. /usr or /usr/local
should be separate - most people don't need that, but if you want to
do it, repeat them for *each* system you plan to build.
My first LFS installation had a multitude of partitions, and was
not ideal - it had seemed to me that separating /usr/local would be
a good idea, but I had overlooked that everything there links to
/lib/libc. So, when I built a newer LFS on a different partition,
everything in /usr/local was linked to the non-existent old version
of libc and no longer worked reliably. The key thing to remember is
that we build a new system whenever we upgrade the toolchain, we
don't normally install a newer gcc, glibc, or binutils into the
current system [ OK, some of us did install a patched glibc for
2.12.1, but that was exceptional ]
My experience is that fdisk, cfdisk, sfdisk, and parted are all
reasonably straightforward if you understand what you are doing.
The distros tend to wrap these in dumbed-down interfaces in their
installers (typically, they want a mount point for a partition - if
it is for a future system, just leave it blank).
Your system, your choice. But ext4 is now probably a safer choice
than ext2 or ext3 when you make the filesystems ;-)
ĸen
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
