logical american wrote:
To all:
Here are some things I noticed while currently following v7.5 of the LFS
book
1. In the Chapter 3.1 Introduction for creating the LFS partition, I
actually
was able to successfully do this as an original logged-in usr on
openSuse v13.1 by
running the Partition editor inside Yast while running under the live
openSuse v13.1 KDE Desktop dvd which I had to download and iso image burn,
and then reboot to, in order to avoid problems with mount setting up on
the original /sda drive as / which stopped everything as the partition
editor will
not work on a mounted partition (well it will, but chaos can result)
After coming up under live KDE desktop, I could then access all 3 hard
drives and partition them at will (and my own peril)
The partition editor both created the partition and formatted the
filesystem
as ext4, and I choose my 3rd drive just to be safe on both.
However when it came time to actually create directories, I was forced to
use root privileges to do so, since the partition editor had created
everything as root owner and group.
So my first question?
Should creating the lfs user and lfs group be done before doing any
work on creating work spaces on the hard drive?
Not really. Creating partitions needs to be done as root.
2. After creating the lfs user and lfs group, and setting up the bash
environment, I used the following commands on the $LFS partition.
%chown -R lfs sources
%chown -R lfs tools
%chgrp -R lfs sources
%chgrp -R lfs tools
Running
%ls -adl *
showed what I expected to see: (plus also all nested subdirectories and
files)
drwx------ 2 root root 16384 Jun 28 10:54 lost+found
drwxrwxrwt 3 lfs lfs 4096 Jun 28 18:38 sources
drwxr-xr-x 2 lfs lfs 4096 Jun 28 18:46 tools
(The lost+found folder came from the partition editor operations)
/tools is usually root.root, but what you have won't hurt anything.
Since sources is 4777, the owner of that directory makes no difference.
3. I am now stopped at Section 5.3 General Compilation Instructions because
the assumed CLI commands do NOT match
%which bash
/bin/bash
%which sh
/bin/sh
%which gawk
/bin/gawk
%which bison
which: no bison in (/tools/bin:/bin:/usr/bin)
I am on openSuse which uses Yast, not bison or yacc. Does bison need to
be installed? I assume that the "sh" is set incorrectly also, although
syntactically it is correct.
Yes, you need to install bison. As far as sh goes, what does 'ls -l
/bin/sh' give you? It needs to be a symbolic link to /bin/bash.
yast and bison are NOT the same tool. Use yast to install bison.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
