On 5/17/2017 10:29 PM, Ken Moffat wrote:
On Wed, May 17, 2017 at 09:39:59PM -0600, Alan Feuerbacher wrote:
On 5/17/2017 9:00 PM, Ken Moffat wrote:
Generally, replying to the list works better.
Oops, sorry. Done.
I was merely trying
to tease out information, you'll need to find somebody running
systemd to help on the details of that.
Ok. Anybody?
That sounds as if systemd is running. That would mean that
filesystems and disk drivers are successfully loaded.
That's what I also concluded, from the fact that a login prompt appeared.
If you got a login prompt then you would be able to login. That
desn't match what you said about the machine hanging. Something
writing out '[ OK ]' is NOT a login prompt.
No, it's *after* the string of [OK] that a login prompt appears, and one
more line, then it hangs. See my original post.
Oy! The reason I'm going for systemd is the challenge. Also to get a full
UEFI boot working.
I don't think UEFI needs systemd. Actually, I don't think anything
except gnome needs systemd.
I understand that. But I want to see if the latest methods will work
with LFS. Fedora and Ubuntu use all that. I also want to try Gnome and
several other systems.
Are you relying on nfs or another sort of network filesystem such as
samba ? I can recall that getting nfs to work in systemd was a
PITA.
No.
Well, that makes it more of the general situation then.
Yes.
Do you need an initrd ?
Everything I've read indicates Yes: BLFS, ArchLinux, RodsBooks.
Really ? Arch uses an initrd so that it can provide a
general-purpose binary kernel with everything in modules. BLFS does
not usually require an initrd (there might be special cases, such as
encrypted filesystems). And I know nothing about Rod, or his books.
I'm following the BLFS book, ch. 5, "About initramfs":
"There are only four primary reasons to have an initramfs in the LFS
environment: loading the rootfs from a network, loading it from an LVM
logical volume, . . . or for the convenience of specifying the rootfs as
a LABEL or UUID. Anything else usually means that the kernel was not
configured properly."
I'm using LVM and LABEL/UUID (experimenting).
Part of the reason I'm going to this trouble is to end up with a hard drive
containing LFS that I can put in another computer and expect to run Linux
with minimal changes. Again this is a learning exercise.
OK, for putting it in different hardware you probably do need an
initrd.
Ok.
For deciding what needs to be built in, look at lsmod on a running
(distro) system and assume all used modules are needed.
There are upwards of 100 modules listed, which I have no clue about.
I do not believe that any distro needs that many modules to boot.
I counted: 116 modules.
But if you have a desktop, google can usually give you an idea about
what they do.
I'll take a look.
The general LFS method is to tune the kernel to the hardware. Yes,
if you want a "run anywhere" system then things are different.
I'm thinking that I'm kind of making a private distro, although that's
not really my goal.
But
can I suggest that you try breaking the problem into smaller parts ?
1. Enough of a kernel (filesystem, disk driver(s)) to be able to
boot to runlevel 3 on the current system.
2. Once that works (maybe there are other problems in your build -
anything is possible), adjust the kernel config for the current
machine so that it can run Xorg (the various kernel graphics
drivers) if you wish to do that, similarly sound, working USB ports
of the various flavours.
3. Using an initrd.
Sounds like a plan. Can you point to any reading material to allow me to
do step 1. without running into the LVM issue mentioned above, with
respect to "About initramfs"?
Alan
--
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
