jhalfs build

Pednick · 03-17-2015, 04:57 PM

Anyone successfully install using jhalfs? I use:

"svn co svn://svn.linuxfromscratch.org/ALFS/jhalfs/trunk jhalfs-trunk"

every time there's errors during build, it's bad enough the instructions
are not very informative in that it should give more info, very frustrating.

Keith Hedger · 03-17-2015, 07:00 PM

Most long term users of lfs would suggest that new users do at least one build from the lfs/blfs book first before trying stuff like automatic builds as it gets you to know what and why you are doing certain things, you can then go on to deviate from the books with a much better idea of what you are doing and how to make changes.

Pednick · 03-17-2015, 07:06 PM

I understand, but was hoping if anyone had a tutorial for automated version.

hendrickxm · 03-18-2015, 02:43 AM

You could also try LFScript.
The latest version will build you a LFS/BLFS 7.6 with the possibility of a full desktop.
http://lfscript.org/wiki/index.php/Main_Page

It is a bit outdated at the moment, I hope Marcel will update the scripts.

Pednick · 03-18-2015, 05:39 AM

Thanks, I'll have a look.

Quote:

Originally Posted by hendrickxm

You could also try LFScript.
The latest version will build you a LFS/BLFS 7.6 with the possibility of a full desktop.
http://lfscript.org/wiki/index.php/Main_Page

It is a bit outdated at the moment, I hope Marcel will update the scripts.

ReaperX7 · 03-18-2015, 10:05 AM

To be honest, jhalfs is nice, but nothing beats writing your own buildscripts to automate your own builds.

I usually write my own scripts using the books before I start building. Once I get everything scripted, then I build. Plus, because I use a few add-in packages, it helps save time and trouble.

Pednick · 03-23-2015, 06:00 AM

I managed to install through jhalfs, well the first part after it says have a nice day but can't get into chroot the way it says in the book and I did the script with defaults. It won't chroot the book way can someone tell me how the script chroot ed so I can reboot by adding the boot, root passed and the rest. As you can tell, I'm no expert nor do I claim to be.

hendrickxm · 03-23-2015, 06:29 AM

If you are unsure, I suggest you try a standard LFS install before trying scripts. Or at least find out what the script is doing.

I can help you with scripted installs I used myself (Nutyx, MIX, LFScript, aryalinux and even CRUX).

To chroot, you need to mount proc, dev and sys:
# mount -t proc proc /proc
# mount --rbind /sys sys
# mount --rbind /dev dev

then you can chroot to the directory where you mounted your LFS (lfs uses /mnt/lfs)
# chroot /mnt/lfs /bin/bash

Pednick · 03-23-2015, 06:32 AM

Ok thank you.

Quote:

Originally Posted by hendrickxm

If you are unsure, I suggest you try a standard LFS install before trying scripts. Or at least find out what the script is doing.

I can help you with scripted installs I used myself (Nutyx, MIX, LFScript, aryalinux and even CRUX).

To chroot, you need to mount proc, dev and sys:
# mount -t proc proc /proc
# mount --rbind /sys sys
# mount --rbind /dev dev

then you can chroot to the directory where you mounted your LFS (lfs uses /mnt/lfs)
# chroot /mnt/lfs /bin/bash

Pednick · 03-25-2015, 04:13 PM

Update: Nevermind, just noticed, yes I know stupid move, there's a developement web page.

Well I got chroot to work and I figured out how to use the blfs_root tools but with lots of errors and then I noticed different versions of files of that from the ones on the web site. I built the svn version, maybe should've picked the branch, anyway gonna try that later. I'm guessing svn version is developer testing build.

ReaperX7 · 03-26-2015, 04:56 AM

The SVN edition is a sort of rolling release edition. I would recommend against using it unless you're testing SVN editions or you need to lookmfor critical updates in errata.

Pednick · 03-28-2015, 12:28 PM

Thank you for your info, I realized the errors I was making, live and learn eh, LOL.

Quote:

Originally Posted by ReaperX7

The SVN edition is a sort of rolling release edition. I would recommend against using it unless you're testing SVN editions or you need to lookmfor critical updates in errata.