On Thu, Dec 03, 2020 at 10:50:50PM +0100, Pierre Labastie wrote:
>
> This is the old method. It's better to use the menu: run make from the
> jhalfs-svn dir then choose "Use Book --> Beyond Linux From Scratch" in
> the menu. Some Other menu entries allow to customize the installation
> paths, the init system, etc.
>
I saw the menu mentioned in my earlier reading, but maybe I forgot
about that. Like many new things, it's hard for me until I get a
grip of what is going on.
>
> Ah, that's the problem: the tools are installed in a different
> directory ($HOME/blfs_root by default), so you should cd to that
> directory, and work from there (edit envars.conf in that directory, and
> run make there)
>
Must admit, from reading I somehow formed the impression that
/blfs_root was a top-level directory. Anyway, since that is the old
way I renamed ~/blfs_root to something else (in case I was again
misunderstanding).
> >
> > Looking at the BLFS Makefile, I had the impression that just running
> > 'make' should be enough to create something I could look at to see
> > what could be run, and what might need adjustment before I tried to
> > build something simple ('which' seems a pretty simple first package)
> > and see what happened. But that appears to be the wrong command, or
> > else run from the wrong place.
>
> Yes, that should be ok provided you start from the installed directory,
> not the jhalfs subversion tree.
>
And then I ran 'make' in jhalfs-svn. Interestingly, it copied over
all the files to blfs_root, including my edited envars.conf and a
diff of the edit I'd created to remind me what to change.
One of the things I'll need to eventually sort out is where to keep
things needed when repeatedly running jhalfs in chroot (my other
disk partitions are not mounted).
>
> Well, "README.BLFS" "3.1 INSTALLATION ON A RUNNING SYSTEM" is all I can
> propose.
>
> But I guess what is misleading is:
> -------
> 4. USAGE::
>
> From now on, all the work must be done from inside the installation
> root directory.
> -------
> I need to reword that to tell it is the directory chosen as "Root of
> the tools directory" in the menu.
>
> (or "$HOME$BLFS_ROOT" when running install-blfs-tools.sh directly)
>
I'm sure that in time it will all seem obvious to me. One small
hicup trying to build 'which' - I'd not realised that /sources was
owned by user lfs in my original build (a hack in my build system,
but in my manual builds it is a mountpoint for nfs so I don't
notice). Reading the script led me to look in ./logs/. I think I
like some of this.
Now to work out what to build ;-)
>
> Note that it may be interesting to run "update-lfs.sh" so that lfs
> packages appear in the menu only if they are newer than the installed
> one (next time Bruce updates lfs).
>
> HTH
> Pierre
>
Yes, again that was very helpful. I haven't created entries for the
LFS packages, my current thinking is that I'll be using my own
scripts for LFS and then hoping to do a series of build tests on the
same base LFS version.
Later, I might try to start with LFS - the fun of sorting out
console (font), fstab, hostname (different when running jhalfs
although obviously in chroot the old name shows)), hosts, firmware
and of course the kernel config when I have a setup that I know
works (at least on _this_ machine, new ones are always
"interesting") is a side-excursion from trying to see if I can do
this adequately by building in chroot, and then perhaps booting the
new system as a normal user to test some of it. Decision, decisions
;-)
ĸen
--
To say that it (his hair) was black and bound up in a ponytail is to
miss the opportunity of using the term 'elephantine'. It was hair
with personality. -- The Thief Of Time (about the monk, Sato).
--
http://lists.linuxfromscratch.org/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
