Re: [lfs-support] systemd behaviour

[Douglas R. Reno]

On 4/3/21 10:08 AM, Thomas Seeling wrote:

Hallo dear list,


for years I have a small helper in /etc/profile.d to search for an
existing ssh-agent instance for my user and set the SSH_* environment
variables accordingly if it finds one. If none is running it does the
usual eval $(ssh-agent) thing.

In the last days I built LFS 10.1 systemd version to compare sysV and
systemd styles and educate myself further.

When exiting and re-entering I noticed that it asks me - again - for my
SSH key credentials and eventually my previous instance of ssh-agent is
gone.

Is it standard behaviour of systemd to kill all processes since login?
My sysV install behaves like expected and ssh-agent stays alive. How
would I start ssh-agent so that it will survive logoff? An additional
layer of "nohup"?

Stay healthy,
Thomas
--
Do you wanna be a legend or a passing footprint on the sands of time?


Hi Thomas,

Try setting KillUserProcesses=no in /etc/systemd/logind.conf. That 
should do the trick for what you're looking to do


- Doug

--
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

Re: [lfs-support] ssh connect fails at kexinit msg 20 preauth

[Douglas R. Reno]

On 3/29/21 4:25 AM, Thomas Seeling wrote:

Hallo dear list,

I have successfully compiled LFS 10.1 on my legacy P4 (32 bit) with jhalfs-4212 
(svn) on an existing LFS 10.0.
Compilation went fine overnight, after installing a kernel it boots fine.
Next step was compiling openssh 8.4 to make it headless again (I had exchanged 
some cables on my KVM switch to watch it boot for the first time).
Compilation went fine here as well, sandbox user exists, sshd starts, but 
connection fails and I have absolutely no clue what goes wrong. sshd_config and 
host keys are the same files I use on the same system, LFS 10.0 partition. I 
tried with different users, ssh keys, tried permissions on .ssh, 
authorized_keys, etc.

The last ssh message is "[server ip] closed connection". Using -vvv I see it 
fails after exchanging msg type 20 preauth kexinit.
I started sshd -e -D -d -d -d and the last messages here tell me the exact same 
thing: kexinit msg type 20 preauth kexinit happens and then the sandbox cleanup 
kicks in. There is no error message why it fails in this stage.

LFS 10.1 uses openssl 1.1.1j which works fine for me on the other system (I 
recently started to upgrade all my systems to 1.1.1k last week but I'm not sure 
this would make a difference for my current problem).

Usually for ssh problems it boils down to some permissions too wide open but I 
think I got that covered. I even checked /tmp for 1777 which is my favourite to 
overlook ;)

I'm out of ideas where to look so maybe someone here has some hints for me 
please?

Stay healthy,
Thomas
--
"Do you wanna be a legend or a passing footprint on the sands of time?"


Hi Thomas,


We've encountered this before on non-x86_64 platforms, especially on i686.

It was in the development book, but was deleted when updating to 
OpenSSH-8.5p1. I'll file an errata for it at my next commit, but here's 
what you need to do:


if [ "$(uname -m)" != "x86_64" ]; then
l1="#ifdef __NR_pselect6_timeyr"
l2="        SC_ALLOW(__NR_pselect6_time64),"
l3="#endif"
sed -e "/^ifdef __NR_read$/ i $l1\n$l2\n$\l3" -i sandbox-seccomp-filter.c
fi

And then rebuild OpenSSH using the instructions in the book.

This happens because OpenSSH added a SECCOMP sandbox into 8.4p1 that was 
incompatible with newer glibcs on most non-x86_64 platforms. The sed 
basically allows the __nr_pselect6_time64 syscall through the sandbox.


I hope this helps!

- Doug

--
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

Re: [lfs-support] Test FAIL: nptl/tst-mutex10 on 8.8.1. Installation of Glibc

[Douglas R. Reno]

On 2/17/21 6:42 AM, coolnodje wrote:

I have this test "FAIL: nptl/tst-mutex10" failing when doing "make
check" in the "8.8.1. Installation of Glibc " part.

I thought I would report this as it's not listed as a test expected to fail.

Otherwise test went fine with only "io/tst-lchmod" and "
misc/tst-ttyname", as can be expected.

I'm running LFS from a Virtualbox Debian testing instance.


Hello,

Some tests like nptl/tst-mutex10 can fail intermittently when running in 
Virtualbox and other hypervisors. You should be good to continue. Thank 
you for bringing it up


- Doug

--
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

Re: [lfs-support] Compile error glibc2.33 -> binutils-2.36.1

[Douglas R. Reno]

On 2/11/21 2:19 PM, Ken Moffat wrote:

On Thu, Feb 11, 2021 at 12:01:12PM -0600, Bruce Dubbs wrote:

On 2/11/21 8:38 AM, Ken Moffat wrote:

On Thu, Feb 11, 2021 at 11:17:27AM +0100, Pierre Labastie wrote:

I've now applied that to 5.10.15-rc1 and confirmed it builds and
boots.  Gotta go out right now for provisions, will use my other
mail to inform the relevant people that this fixes builds with
binutils-2.36.1 when I get back.

The 5.10.15 kernel is now out, but I can confirm that the patch above has
NOT been incorporated.

Do we know when 5.11 will be released?  We are scheduled to go into package
freeze on Sunday, but if it is not fixed yet, I think we should wait for it.

   -- Bruce


5.11 is expected on Sunday night.  We normally wait for .1 versions
(and the patch has missed 5.10.16 by the look of things (5.10.16-rc1
was released before I sent my mail), no idea if it will arrive in
5.10.18 - it looks as if it had been filed under "breaks clang, but
that is maybe broken anyway" (although Linus apparently now uses
it).

And we are expecting the (low severity) new version of OpenSSL next
Tuesday.

Broadening this, any thought on the change to adapt glibc for (at
least) older AMD K10 hardware ?


On the glibc change, we should definitely proceed I think. I can 
reproduce it on Sandy Bridge Intel as well, and my SysV box is affected too.


This is a tough one, hopefully Bruce has more insight. We could just do 
-rc1 with Linux 5.11 (no point version), but not sure if that's the best 
way to approach things either


- Doug

--
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

Re: [lfs-support] Fwd: Too Many GLIBC Test Failures?

[Douglas R. Reno]

On 12/10/20 10:54 PM, Jeff Forehand wrote:
Sorry, but I am sending this again because I was not subscribed yet 
when I sent it the first time.


-- Forwarded message -
From: *Jeff Forehand* mailto:skinny...@gmail.com>>
Date: Sat, Dec 5, 2020 at 5:15 PM
Subject: Too Many GLIBC Test Failures?
To: >



I am in Chapter 8.8 of the LFS-Systemd 10.0 build book. The glibc 2.32 
"make check" test is resulting in 23 FAILs (see attached - I have 
trimmed out the non-failures). My host system is Ubuntu 20.04LTS 
running on a mid-2000s i7 processor. I have done some searching 
through the archives, but nothing very recent pops up which may 
indicate that my setup is uniquely broken.


Are there any failures in the list that are showstoppers? The first 
one, "c++-types-check," seems like one that should pass in my limited 
knowledge on this subject.


All of the builds up to this point seem to have gone well. Anyone have 
an idea where I may have messed this up?


Thanks in advance for your help,
Jeff


Hi Jeff,

I looked at the test output that you sent, and I do agree that something 
is amiss. The question is... what exactly is going on...


Let's start here - do you have the virtual filesystems mounted? If 
there's something going on with /dev, /dev/pts, and others, I can 
absolutely understand things like fd_to_filename and memfd_create failing.


What kernel version is in use (uname -r)?

We haven't heard a report of Ubuntu 20.04LTS causing problems yet - but 
that's not to say that it isn't having an impact of some kind either. 
Generally, when I bootstrap a system for the first time, I use the 
latest Debian release. There are significant differences in packages 
though between Debian 10 and Ubuntu 20.04LTS.


- Doug

-- 
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

Re: [lfs-support] LFS in Virtualbox - Saving possible

[Douglas R. Reno]

On 12/9/20 6:45 AM, David Brandl @ davidb.at wrote:

Hi!

I´m planning to build LFS on Lubuntu in Virtualbox - is it possible to 
continue work if I save the session?


Thanks a lot!



Hello!


If you're on Virtualbox, saving the session would mean saving the state 
of the VM. You should easily be able to continue after resuming the VM.


I hope this helps!

- Doug

--
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

Re: [lfs-support] Chapter 10. Making the LFS System Bootable - LFS 10.0/development

[Douglas R. Reno]

On 11/26/20 4:58 PM, rhubarbpie...@vivaldi.net wrote:


Pseudo filesystems  --->

   [*] Tmpfs POSIX Access Control Lists [CONFIG_TMPFS_POSIX_ACL]
   [*] Tmpfs extended attributes [CONFIG_TMPFS_XATTR]

Tmpfs extended attributes now appears hard coded with no option 
available.  Could/should the line be deleted?


I neglected including this with an earlier post regarding a similar item.


Thank you for the report! :-)

Fixed at r12065

- Doug

--
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

Re: [lfs-support] LFS10 5.5.Glibc-2.32 LSB compliance

[Douglas R. Reno]

On 11/25/20 7:59 PM, Yotta Point wrote:
On Thu, Nov 26, 2020 at 10:53 AM Douglas R. Reno 
mailto:ren...@linuxfromscratch.org>> wrote:



On 11/25/20 7:45 PM, Yotta Point wrote:



On Thu, Nov 26, 2020 at 10:40 AM Douglas R. Reno
mailto:ren...@linuxfromscratch.org>> wrote:


On 11/25/20 7:28 PM, Yotta Point wrote:

Hi,

I managed to build the LFS for 32Bit and now I am trying to
make it a 64Bit version.
I am stuck at step 5.5 Glibc build in the LSB compliance.

case $(uname -m) in i?86) ln -sfv ld-linux.so.2
$LFS/lib/ld-lsb.so.3 ;; x86_64) ln -sfv
../lib/ld-linux-x86-64.so.2 $LFS/lib64 ln -sfv
../lib/ld-linux-x86-64.so.2 $LFS/lib64/ld-lsb-x86-64.so.3 ;;
esac
the second ln is failing saying "No such file or directory"
which seems normal to me because the first line create a
symlink at $LFS/lib64 that links to a library, and the
second line is trying to access the symlink "$LFS/lib64" as
if it was a directory. I am missing something here ?

Thanks for your help !


Hi,


For 32-bit systems, only the line that starts with i?86 is
necessary. For 64-bit systems, you'd follow x86_64.

Note that most users copy and paste that block of commands
into their terminal so the system follows what part is needed.

- Doug

-- 
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


Hey, thanks for your quick reply.
Maybe I did not correctly explain my issue. In the x86_64) case,
there are 2 commands.  "ln -sfv ../lib/ld-linux-x86-64.so.2
$LFS/lib64" and " ln -sfv ../lib/ld-linux-x86-64.so.2
$LFS/lib64/ld-lsb-x86-64.so.3". The second ln is giving me back
"No such file or directory" and I think it's because the first
"ln" is making "$LFS/lib64" a symlink to a library, and the
second ln is trying to access "$LFS/lib64" as if it was a directory.

Sorry if my first post was not explicit enough.


Hi,

No worries on explicitness, I might be misunderstanding the
question as well. I'm going off of the fact that you said that
you're building 32-bit LFS (which is something Thomas and I
primarily do).

If you're building a 32-bit system, you should most certainly
ignore the block for x86_64. /lib64 is for $LFS/lib64 is for a
couple of symbolic links to libraries used to provide
compatibility with existing 64-bit binaries on 64-bit systems. On
a 32-bit system, you shouldn't have $LFS/lib64 :-) you can ignore
the block for x86_64.

To revert that (you don't want 64-bit libraries on a 32-bit
system), run: "rm -fv $LFS/lib64".

- Doug

-- 
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


Thanks Douglas,
I already managed to make the 32Bit LFS and I am trying now to make a 
64Bit version, that's why I am looking at the 64Bit case.



Hi,

I'm sorry, I misread your original question!

$LFS/lib64 should've been created back in 4.2 (Creating a limited 
directory layout in LFS filesystem). What I would do is this:


"rm -fv $LFS/lib64"

"mkdir -pv $LFS/lib64"

And then restart that command block following the x86_64 instructions 
instead of the i?86 ones. For convenience, I'd just copy and paste the 
whole block into my terminal.


- Doug

-- 
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

Re: [lfs-support] LFS10 5.5.Glibc-2.32 LSB compliance

[Douglas R. Reno]

On 11/25/20 7:45 PM, Yotta Point wrote:



On Thu, Nov 26, 2020 at 10:40 AM Douglas R. Reno 
mailto:ren...@linuxfromscratch.org>> wrote:



On 11/25/20 7:28 PM, Yotta Point wrote:

Hi,

I managed to build the LFS for 32Bit and now I am trying to make
it a 64Bit version.
I am stuck at step 5.5 Glibc build in the LSB compliance.

case $(uname -m) in i?86) ln -sfv ld-linux.so.2
$LFS/lib/ld-lsb.so.3 ;; x86_64) ln -sfv
../lib/ld-linux-x86-64.so.2 $LFS/lib64 ln -sfv
../lib/ld-linux-x86-64.so.2 $LFS/lib64/ld-lsb-x86-64.so.3 ;; esac
the second ln is failing saying "No such file or directory"
which seems normal to me because the first line create a symlink
at $LFS/lib64 that links to a library, and the second line is
trying to access the symlink "$LFS/lib64" as if it was a
directory. I am missing something here ?

Thanks for your help !


Hi,


For 32-bit systems, only the line that starts with i?86 is
necessary. For 64-bit systems, you'd follow x86_64.

Note that most users copy and paste that block of commands into
their terminal so the system follows what part is needed.

- Doug

-- 
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


Hey, thanks for your quick reply.
Maybe I did not correctly explain my issue. In the x86_64) case, there 
are 2 commands.  "ln -sfv ../lib/ld-linux-x86-64.so.2 $LFS/lib64" and 
" ln -sfv ../lib/ld-linux-x86-64.so.2 $LFS/lib64/ld-lsb-x86-64.so.3". 
The second ln is giving me back "No such file or directory" and I 
think it's because the first "ln" is making "$LFS/lib64" a symlink to 
a library, and the second ln is trying to access "$LFS/lib64" as if it 
was a directory.


Sorry if my first post was not explicit enough.


Hi,

No worries on explicitness, I might be misunderstanding the question as 
well. I'm going off of the fact that you said that you're building 
32-bit LFS (which is something Thomas and I primarily do).


If you're building a 32-bit system, you should most certainly ignore the 
block for x86_64. /lib64 is for $LFS/lib64 is for a couple of symbolic 
links to libraries used to provide compatibility with existing 64-bit 
binaries on 64-bit systems. On a 32-bit system, you shouldn't have 
$LFS/lib64 :-) you can ignore the block for x86_64.


To revert that (you don't want 64-bit libraries on a 32-bit system), 
run: "rm -fv $LFS/lib64".


- Doug

-- 
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

Re: [lfs-support] LFS10 5.5.Glibc-2.32 LSB compliance

[Douglas R. Reno]

On 11/25/20 7:28 PM, Yotta Point wrote:

Hi,

I managed to build the LFS for 32Bit and now I am trying to make it a 
64Bit version.

I am stuck at step 5.5 Glibc build in the LSB compliance.

case $(uname -m) in i?86) ln -sfv ld-linux.so.2 $LFS/lib/ld-lsb.so.3 
;; x86_64) ln -sfv ../lib/ld-linux-x86-64.so.2 $LFS/lib64 ln -sfv 
../lib/ld-linux-x86-64.so.2 $LFS/lib64/ld-lsb-x86-64.so.3 ;; esac
the second ln is failing saying "No such file or directory" 
which seems normal to me because the first line create a symlink at 
$LFS/lib64 that links to a library, and the second line is trying to 
access the symlink "$LFS/lib64" as if it was a directory. I am missing 
something here ?


Thanks for your help !


Hi,


For 32-bit systems, only the line that starts with i?86 is necessary. 
For 64-bit systems, you'd follow x86_64.


Note that most users copy and paste that block of commands into their 
terminal so the system follows what part is needed.


- Doug

-- 
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

Re: [lfs-support] lfs vs. lfs-systemd: --bindir

[Douglas R. Reno]

On 9/18/20 1:39 AM, Hans Meier wrote:

Hello,

During building lfs-10.0-systemd I noticed that on some places the 
--bindir option is different to the lfs-10.0 build.


Is that correct?

Here some examples:

  lfs-10.0 lfs-10.0-systemd
8.22. Attr-2.4.48  --bindir=/bin  no --bindir option
8.23. Acl-2.2.53   --bindir=/bin  no --bindir option
6.29. Sed-4.8  --bindir=/bin  --bindir=/bin



Regards,
  Hans


Hi Hans,


If I remember correctly, these are based off requirements in systemd (in 
earlier versions of meson, systemd's meson.build file would refuse to 
look for files outside of those locations). However, I think it needs to 
be re-examined. One of our end goals is to have as little differences in 
instructions as possible between the two books.


Thank you for bringing it up

- Doug

--
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

Re: [lfs-support] Source

[Douglas R. Reno]

On 8/12/20 5:03 AM, LLSJ Krüger PrEng wrote:

HI,

I'm new here.

I just want to ask one question: Where can I, if possible and allowed,
obtain the source code for the LFS-multilib (SysV) book?

I want to compile a 'nochunks' issue  for offline reading, I have
difficulty with online chunk by chunk reading.

Kind regards.


Louis.


Hi Louis,


You can obtain the source code by running the following command:


svn co svn://svn.linuxfromscratch.org/LFS


In your case, if all you want is the multilib branch:


svn co svn://svn.linuxfromscratch.org/LFS/branches/multilib


To render the book, just run 'make REV=sysv nochunks'. If you want the 
systemd version, replace 'sysv' with 'systemd'.


Running 'make' as is will generate chunked HTML files, with a default of 
SysV, and a default location of ~/public_html.



- Doug

--
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

Re: [lfs-support] FTP Error

[Douglas R. Reno]

On 5/26/20 3:46 PM, Greekforce1821 wrote:
Good evening gentlemen, I am having some issues with the FTP in BLFS 
terminal, as you can see in the photo, I tried to login to 
ftp://ftp.gnu.org  
using the command ftp ftp.gnu.org  but it pops up 
the error that says ftp> invalid command. How can I fix this?


Good evening,

You're going to want to do this:

"open ftp://ftp.gnu.org";

Inside of your FTP command.


I'll note that it's been a very long time since I've done this though 
(5+ years), normally I download wget before rebooting.


-- 
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

Re: [lfs-support] Updating secutiy fixes

[Douglas R. Reno]

On 5/8/20 12:40 PM, Bud Rozwood wrote:

Hi,

I am reading the BLFS errata for the stable sysv version and I was 
wondering if, when following the instructions for the development 
book, would I need to install the updated recommended dependencies as 
well?


For example, for Firefox it gives a note that without the 
recommended dependencies, it will use out of date or packages with 
security holdes. So, for Firefox, would I not only install the updated 
version as well as the updated recommended dependencies?



Hi Bud,


For the most part, I'd suggest upgrading the recommended dependencies as 
well. It primarily depends on whether your existing versions work or 
not. We don't normally test building newer versions of packages against 
older dependencies, only the ones in the development book.


Ken probably has some better input/advice :)

- Doug

--
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

Re: [lfs-support] vim test_autocmd fails

[Douglas R. Reno]

On 4/17/20 2:13 PM, Bud Rozwood wrote:
On Fri, Apr 17, 2020 at 3:12 PM Bud Rozwood > wrote:


Hi,

I'm not sure why this test fails but I have noticed it was
mentioned on GitHub a couple times:

https://github.com/vim/vim/releases/tag/v8.1.0466

and

https://github.com/vim/vim/commit/8fb1b47a5e24892b23c3923a07d8a850d99b14b2

for example. I've attached my log file for reference.

But I even tried it on the latest version 8.2.0510 instead of
8.2.0190, as in the book.

PS. I accidentally ran that last test

VIMRUNTIME=../../runtime  ../vim -f  -u unix.vim -U NONE
--noplugin --not-a-term -S runtest.vim test_autocmd.vim --cmd 'au
SwapExists * let v:swapchoice = "e"' > /dev/null

in the test directory as root without thinking. I ran it again as
"nobody" and it returned a .res file that was empty.

I hope I didn't screw something up I'd hate to restart again.


FYI, vim seems to run fine when I use it afterwards.

I think this is one of those tests that uses functions that are rarely 
used in vim. You should be good to continue, although I'd recommend that 
you delete your vim build directory and rebuild it just to be on the 
safe side.


-- 
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

Re: [lfs-support] make check fails for Bison-3

[Douglas R. Reno]

On 4/16/20 8:12 AM, Bud Rozwood wrote:

Hi,

I've ran make check after flex was installed and I get some errors 
regarding the diagnostic tests and I'm not sure why. I've followed the 
book up to that point to a t.


Although it seems that these tests are optional and even the log for 
bison in lfs i7 test-log 
 
is empty. The test suite for flex ran without errors:


grep FAIL log_dir/chapter06/flex.txt
# XFAIL: 0
# FAIL:  0

I've attached my test log for bison if you want to look at it.

If this isn't serious, I guess I should move on.

It doesn't seem to be serious. I've downloaded the log, and it looks 
like there's 11 failures out of 575. Here's the relevant part of the log 
for anyone looking for it:


Diagnostics.

130: Warnings    FAILED 
(diagnostics.at:107)
131: Single point locations  FAILED 
(diagnostics.at:152)
132: Tabulations and multibyte characters    FAILED 
(diagnostics.at:208)
133: Special files   FAILED 
(diagnostics.at:234)
134: Complaints from M4  FAILED 
(diagnostics.at:257)
135: Carriage return FAILED 
(diagnostics.at:279)
136: CR NL   FAILED 
(diagnostics.at:307)
137: Screen width: 200 columns   FAILED 
(diagnostics.at:346)
138: Screen width: 80 columns    FAILED 
(diagnostics.at:379)
139: Screen width: 60 columns    FAILED 
(diagnostics.at:412)
140: Suggestions FAILED 
(diagnostics.at:436)

141: Indentation with message suppression    ok


Since all of the other tests are passing, I think you're good to 
continue. The skipped ones are primarily for languages that aren't 
installed.


I'll note that I'm not sure how long it's been since we've run the test 
suite for bison. Our automated build system normally doesn't go back to 
bison to rebuild it for testing. I think that it's tested when it's 
updated though.



- Doug

-- 
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

Re: [lfs-support] linux 5.5.9: shutdown -h hangs on detaching cdrom

[Douglas R. Reno]

On 4/13/20 2:29 PM, Stephen Berman wrote:

On Sun, 12 Apr 2020 18:47:08 +0100 Ken Moffat  wrote:


On Sat, Apr 11, 2020 at 06:43:22PM +0200, Stephen Berman wrote:

On Fri, 10 Apr 2020 15:51:22 -0500 Bruce Dubbs  wrote:


On 4/10/20 3:29 PM, Stephen Berman wrote:

I've built current development LFS using jhalfs and when I invoke (via
sudo or logged in as root) `shutdown -h now', the system appears to hang
while trying to detach the cdrom block device.  Here are the last two
lines printed to the terminal after issuing that command:
Bringing down the loopback interface..[OK]
sr 5:0:0:0: tag#21 timing out command, waited 120s
and every 2 minutes, the last line repeats with a different tag#.  So
far I haven't had the patience to wait more than six minutes, then I
power off the machine with the start button.  I know this is the cdrom
because on booting there are these messages:
[6.633004] scsi 5:0:0:0: CD-ROMHL-DT-ST DVDRAM GH24NSD1
LW00 PQ: 0 ANSI: 5
[ 6.679083] sr 5:0:0:0: [sr0] scsi3-mmc drive: 48x/12x writer dvd-ram cd/rw
xa/form2 cdda tray
[6.679101] cdrom: Uniform CD-ROM driver Revision: 3.20
[6.689325] sr 5:0:0:0: Attached scsi CD-ROM sr0
[6.689399] sr 5:0:0:0: Attached scsi generic sg1 type 5
In addition, the message "timing out command, waited %lus\n" comes from
the function scsi_softirq_done in linux-5.5.9/drivers/scsi/scsi_lib.c.
This only happens with `shutdown -h' or `shutdown -hP', not with
`shutdown -r'.  Moreover, on the same computer I also have LFS 8.4 with
kernel 4.20.12, and there `shutdown -h' works fine.  So it seems to be
an issue with kernel 5.5.9.  When I built the latter I used `make
oldconfig' with the config file of kernel 4.20.12, accepting the
defaults for all new options.  Comparing the two config files, I didn't
notice any evidently relevant difference, e.g. involving SCSI options.
I suppose it's also possible there is some other difference between LFS
8.4 and the current development version that could be involved, but I
have no idea what to look for.  Does anyone here have any ideas or
suggestions for how to track down what's causing the hang and stop it?

Since it is bringing down the loopback interface it is running the bootscript
S90localnet properly.  The only other script is S99halt and that only does
'halt -d -f -i -p'.

-d Don't write the wtmp record.
-f Force halt or reboot, don't call shutdown(8).
-i Shut  down  all network interfaces just before halt or reboot.
-p When  halting  the system, switch off the power.

Try using 'poweroff' or 'init 0' and see if anything changes.  You can also
try using an older kernel with the current build to validate that it is a
kernel problem.

Thanks for the suggestions.  I tried `poweroff' and the effect was the
same as `shutdown -h', hanging on detaching the cdrom device.  (I didn't
try `init 0' -- as the LFS book says, "init 0 is an alias for the halt
command", so shouldn't it have the same result?)  But I did, on this
system, build and install kernel 4.20.12 from LFS 8.4 -- and when I
booted it and then did `shutdown -h now', the system shut down and the
machine powered off, just as in LFS 8.4.  So that pretty clearly points
the finger at kernel 5.5.9.

I've tried searching the web but found nothing about this problem.  I'm
not sure how best to proceed.  It would be tedious and time-consuming to
build all released kernels between 4.20.12 and 5.5.9, though I might try
one or two, or maybe the current 5.6.2.  If you or anyone else has more
advice, I'm all ears.

Steve Berman

Hi Steve,

it seems a very uncommon problem,

Apparently so, yet I don't think I have unusual hardware; the SCSI drive
in question is an LG DVDRAM model GH24NSD1.


   so some questions just in case:

Do you have a CD in the drive when you try to shutdown ?

No.


Is the CD using an old or obscure driver (I'm thinking of old PATA
drives, I guess anything older than that is unlikely to still be
usable.

AFAICT the drive uses the standard SCSI driver, at least I'm not aware
of, nor see in the kernel config file, anything specific to this model
or LG in gneral.


  Hmm, that prompts me to ask if the CD drive is working with
this kernel ?

Yes, I can play CDs and DVDs (with VLC) and mount and read CDRs on it.


Recent kernels have seen a lot of overhauls in the kernel
infrastructure. perhaps your .config for versions after 4.20.12 has
lost something it needs for the CDROM.  Seems unlikely, since it
shows up, but testing that it works will dispel that suggestion.

Consider it dispelled.


For finding which commit caused a problem, you really need to run
git bisect.  I hope you are aware that the stable kernels maintained
by Greg KH use a different git tree from Linus' upstream, and that
while in Linus' tree there is a progression from 4.20.0 to 5.6.0, in
Greg's stable trees the progressions are 4.20.0 to 4.20.last, 5.0.0
to 5.0.last, etc.

I didn't know this, thanks for point

Re: [lfs-support] CoreUtils warnings

[Douglas R. Reno]

On 3/28/20 5:35 PM, Rob wrote:

This with LFS stable on Debian 10 host
Chapter 5.19, coreutils-8.31

configure: WARNING: libacl development library was not found or not usable.
configure: WARNING: GNU coreutils will be built without ACL support.
configure: WARNING: libattr development library was not found or not usable.
configure: WARNING: GNU coreutils will be built without xattr support.
configure: WARNING: libcap library was not found or not usable.
configure: WARNING: GNU coreutils will be built without capability support.
configure: WARNING: libgmp development library was not found or not usable.
configure: WARNING: GNU coreutils will be built without GMP support.

Are these things I need to worry about?


No they aren't :)

In Chapter 5, those libraries won't be available yet. When you rebuild 
that package in Chapter 6, those warnings will fade away. These are for 
optional features that aren't necessary in the temporary system built in 
/tools.


--
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

Re: [lfs-support] Linux kernel doesn't see partitions

[Douglas R. Reno]

On 3/26/20 5:43 PM, Jason Gauthier wrote:



On Thu, Mar 26, 2020 at 5:51 PM Douglas R. Reno 
mailto:ren...@linuxfromscratch.org>> wrote:



On 3/26/20 3:03 PM, Jason Gauthier wrote:

I'm to the point where grub needs to be installed.
I've built LFS on a loopback device, so there isn't a physical
drive to install grub to.

I booted a debian recovery disk, and I installed and configured
grub.
Since I'm going to use this on a QEMU system I set the linux
parameter to
"linux /boot/vmlinuz-5.5.3-lfs-9.1 root=/dev/vda1 ro"

Grub loads, and boots the kernel.  But the kernel halts because
it cannot find the root filesystem. Specifically, it says,
"Please append a correct "root=" boot option; here are the
available partitions:
But there aren't any partitions listed.

My grub.cfg:
set default=0
set timeout=5

insmod ext2
set root=(hd0,1)

menuentry "GNU/Linux, Linux 5.5.3-lfs-9.1" {
        linux   /boot/vmlinuz-5.5.3-lfs-9.1 root=/dev/vda1 ro
}


Appreciate any pointers.  I "feel" like the kernel might not know
about the disk subsystem, but I didn't deviate from
compilation options, and I've been out of the kernel compilation
game for a long time so I don't know what's even defaulted or
modular anymore.



Hi Jason,


I've had something similar happen before. I presume because you're
mentioning vda1 that you're using VirtIO disks? I have one system
that uses those - it's a VM inside of a Proxmox instance far far
away from me (which I rarely ever use now). Proxmox uses libvirt
with Qemu IIRC. You'll want to ensure that the following options
are built into your kernel:

SCSI_VIRTIO=y

VIRTIO_BLK=y

VIRTIO_BLK_SCSI=y

VIRTIO=y



Thank you! The trick was that NONE of this stuff was enabled by 
default, and most of it should not be set to 'm'.  I got the system 
booted!
Now, there isn't any network, but at least I've booted my first LFS.  
This was fun, but I'm using this as a platform to help me build 
software for yet another platform.



There is a VIRTIO network adapter too:

VIRTIO_NET=y

See if that helps :)


Also, if you're using VIRTIO graphics, try this to get a framebuffer:

VIRTIO_PCI=y

VIRTIO_IOMMU=y

VIRTIO_BALOON=y

DRM_VIRTIO_GPU=y


There are others in the VIRTIO section, but I'm not sure if they are 
needed or not in your configuration. It looks like at some point they 
added a Virtio Drivers section under Device Drivers, but I'm not sure 
what that requires. The VIRTIO-based system I have is running 4.19.


-- 
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

Re: [lfs-support] Linux kernel doesn't see partitions

[Douglas R. Reno]

On 3/26/20 3:03 PM, Jason Gauthier wrote:

I'm to the point where grub needs to be installed.
I've built LFS on a loopback device, so there isn't a physical drive 
to install grub to.


I booted a debian recovery disk, and I installed and configured grub.
Since I'm going to use this on a QEMU system I set the linux parameter to
"linux /boot/vmlinuz-5.5.3-lfs-9.1 root=/dev/vda1 ro"

Grub loads, and boots the kernel.  But the kernel halts because it 
cannot find the root filesystem.  Specifically, it says, "Please 
append a correct "root=" boot option; here are the available partitions:

But there aren't any partitions listed.

My grub.cfg:
set default=0
set timeout=5

insmod ext2
set root=(hd0,1)

menuentry "GNU/Linux, Linux 5.5.3-lfs-9.1" {
        linux   /boot/vmlinuz-5.5.3-lfs-9.1 root=/dev/vda1 ro
}


Appreciate any pointers.  I "feel" like the kernel might not know 
about the disk subsystem, but I didn't deviate from 
compilation options, and I've been out of the kernel compilation game 
for a long time so I don't know what's even defaulted or modular anymore.



Hi Jason,


I've had something similar happen before. I presume because you're 
mentioning vda1 that you're using VirtIO disks? I have one system that 
uses those - it's a VM inside of a Proxmox instance far far away from me 
(which I rarely ever use now). Proxmox uses libvirt with Qemu IIRC. 
You'll want to ensure that the following options are built into your kernel:


SCSI_VIRTIO=y

VIRTIO_BLK=y

VIRTIO_BLK_SCSI=y

VIRTIO=y


The crypto and GPU drivers are rather important too if you're not going 
to be using the Qemu defaults, but focus on getting your system booting 
before worrying about those.


-- 
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

Re: [lfs-support] Glibc-2.31 issues

[Douglas R. Reno]

On 2/16/20 7:38 AM, Pierre Labastie wrote:

Le 14/02/2020 à 23:43, TomW a écrit :

On 2/7/20 3:23 PM, Douglas R. Reno wrote:


On 2/6/20 1:05 PM, Tom Willhite wrote:

Just a heads up FYI.   I failed to build latest systemd-svn using a 1 month
old tools tball by hand.   Systemd-244 ninja got to machinectl and errored
out.   So I fired up a jhalfs build using latest svn version of it and that
built ok but upon first boot I get ncsd systemd service not starting.
Obviously the book needs some mods.   I can create a /var/run/ncsd and
start the service but it isn't enough to make it function.   Anything
network related is broke like ssh and resolved.   I won't clutter up this
post with exact errors because you will run into it all soon and see it
yourselves.     New toolchain stuffgotta expect some of this I
suppose.   Archetech

Hi Archetech,


I wanted to let you know that I've begun looking into this (I'm running
jhalfs on my 32-bit and 64-bit systems because one of them could be affected
by a time_t bug, and the other one is likely to have the glibc problems that
you're reporting).


This will be my first system with glibc-2.31, so I'll likely have to run
through a portion of BLFS to test the patch with glibc-2.31 as well (I might
do this on my 32-bit machine because it takes longer to build than anything
else, and I like to start that one ahead of package freeze anyway).


 From the v244-stable repository, it looks like systemd may need fixes for
BTRFS/LVM2 filesystems, as well as some patches for libcap-2.29+ (can
someone check on that please? libcap-2.29+, linux-5.5, and glibc-2.31 seems
to be causing problems for at least hwdb if not udev itself based off what
I've seen in the systemd stable repository).


The PolicyKit security vulnerability is also fixed in the stable repository
as well, so I'll backport that too.


Thank you for reporting,


- Doug



I tried reinstalling systemd per the blfs book and it makes no improvement.
The build errors  right after it processes udev.pc and gives eof being off.
Got any ideas on how to repair?

I tested the toolchain and it seems ok.



Just FYI, I'm currently building systemd BLFS SVN on top of systemd LFS
9.1-rc1, And I see none of the errors you are talking about.

But I've had some similar problems (solved) with systemd+jhalfs a while ago,
see http://wiki.linuxfromscratch.org/blfs/ticket/12595#comment:6 and 
following...

Pierre



I've now built systemd-244 in BLFS with all dependencies except Qemu, 
iptables, cryptsetup, and zsh (I don't normally build those, except for 
cryptsetup, and that comes later). I didn't have any problems booting 
the machine or building the package.


Archetech, which optional dependencies do you have installed, and which 
ones do you not have installed? Also, make sure that you have seccomp 
support enabled in your kernel please


--
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

Re: [lfs-support] systemd 'Installation of the kernel' - LFS 9.0/development

[Douglas R. Reno]

On 2/16/20 7:37 PM, Xi Ruoyao wrote:

On 2020-02-16 00:38 -0600, Douglas R. Reno wrote:

I also adjusted the path for the Frame Pointer Unwinder (it is now under
"x86 Debugging" in the Kernel Hacking menu). This was done at r11751

Is there any reason we must use this option?  I chosed Orc Unwinder and
everything just continues to working properly now.


At one point in time, we didn't have libelf in LFS, and as a result we 
couldn't compile the kernel with the ORC unwinder (see 
http://wiki.linuxfromscratch.org/lfs/ticket/4186 ).



I think it's obsolete though and I can probably remove it.

--
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

Re: [lfs-support] systemd 'Installation of the kernel' - LFS 9.0/development

[Douglas R. Reno]

On 2/15/20 8:13 AM, rhubarbpie...@vivaldi.net wrote:


Some questions/thoughts about the ‘Installation of the kernel’ systemd 
documentation.



Hello,

Thank you for reporting this, I'm going to follow up here (I just 
submitted a change to LFS that handles these kernel configuration fixes)




Where is the following?

   General setup →
   [ ] Enable deprecated sysfs features by default
- 

In a previous version of the kernel, this was valid (both would appear 
at the same time). Now that is no longer the case, so I have adjusted it 
(this option only exists when the one above it, 
[CONFIG_SYSFS_DEPRECATED], is enabled)


Would the full path for ‘[*] Open by fhandle syscalls’ be clearer?

   General setup →
    [*] Configure standard kernel features (expert users) --→
 [*] open by fhandle syscalls
- 

Yes it would, I changed the text there so that it matches what 
Linux-5.5+ uses.


Is ‘[ ] Fallback user-helper invocation for firmware loading’ the 
following?


    Device Drivers --→
    Generic Driver Options --→
 Firmware Loader --→
 [ ] Enable the firmware sysfs fallback mechanism
-- 



Yes it is, that's another Linux-5.4/5.5 change (I didn't research the 
exact one). I've adjusted the text for that as well.
Should ‘[*] Export DMI identification via sysfs to userspace’ be moved 
above the Device Drivers section and below General setup?


I've moved the "Firmware Drivers" section above the "Device Drivers" 
section, so that should be factored in. That was changed as part of the 
kernel menu redesign.
A small matter, but should the wording of ‘Kernel automounter version 
4 support (also supports v3)’ be:


   Kernel automounter version 4 support (supports v3, v4 and v5)

Yes it should! The description in the book was implemented in a past 
kernel version. I've adjusted that.



I also adjusted the path for the Frame Pointer Unwinder (it is now under 
"x86 Debugging" in the Kernel Hacking menu). This was done at r11751



Thank you for bringing this up!

- Doug

--
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

Re: [lfs-support] systemd 'Installation of the kernel' - LFS 9.0/development

[Douglas R. Reno]

On 2/15/20 8:13 AM, rhubarbpie...@vivaldi.net wrote:


Some questions/thoughts about the ‘Installation of the kernel’ systemd 
documentation.



Where is the following?

   General setup →
   [ ] Enable deprecated sysfs features by default
- 



Would the full path for ‘[*] Open by fhandle syscalls’ be clearer?

   General setup →
    [*] Configure standard kernel features (expert users) --→
 [*] open by fhandle syscalls
- 



Is ‘[ ] Fallback user-helper invocation for firmware loading’ the 
following?


    Device Drivers --→
    Generic Driver Options --→
 Firmware Loader --→
 [ ] Enable the firmware sysfs fallback mechanism
-- 



Should ‘[*] Export DMI identification via sysfs to userspace’ be moved 
above the Device Drivers section and below General setup?


A small matter, but should the wording of ‘Kernel automounter version 
4 support (also supports v3)’ be:


   Kernel automounter version 4 support (supports v3, v4 and v5)

When I get approval from Bruce, I'll adjust the kernel configuration. 
I'm going to be away for the next 8 hours at least though.

--
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

Re: [lfs-support] Glibc-2.31 issues

[Douglas R. Reno]

On 2/7/20 2:19 PM, Alan Feuerbacher wrote:



On 2/6/2020 12:05 PM, Tom Willhite wrote:
Just a heads up FYI.  I failed to build latest systemd-svn using a 1 
month old tools tball by hand.   Systemd-244 ninja got to machinectl 
and errored out.   So I fired up a jhalfs build using latest svn 
version of it and that built ok but upon first boot I get ncsd 
systemd service not starting.  Obviously the book needs some mods.  
 I can create a /var/run/ncsd and start the service but it isn't 
enough to make it function.   Anything network related is broke like 
ssh and resolved.   I won't clutter up this post with exact errors 
because you will run into it all soon and see it yourselves.     New 
toolchain stuffgotta expect some of this I suppose.   Archetech


Does this mean that the latest systemd development version is broken 
for now?



I completed a build a couple of days ago and it does not boot. I get 
an error like this:



The device /dev/disk/by-uuid/c23., which is supposed to contain 
the root file system, does not exist.


Please fix this problem and exit this shell.


Alan


Unfortunately, yes. I'm working on a patch to solve these problems, it 
should be in the book in the next day or two, if not sooner (depending 
on build times).



Thank you,


- Doug

-- 
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

Re: [lfs-support] Glibc-2.31 issues

[Douglas R. Reno]

On 2/6/20 1:05 PM, Tom Willhite wrote:
Just a heads up FYI.   I failed to build latest systemd-svn using a 1 
month old tools tball by hand.   Systemd-244 ninja got to machinectl 
and errored out.   So I fired up a jhalfs build using latest svn 
version of it and that built ok but upon first boot I get ncsd systemd 
service not starting.  Obviously the book needs some mods.   I can 
create a /var/run/ncsd and start the service but it isn't enough to 
make it function.   Anything network related is broke like ssh and 
resolved.   I won't clutter up this post with exact errors because you 
will run into it all soon and see it yourselves.     New toolchain 
stuffgotta expect some of this I suppose.   Archetech


Hi Archetech,


I wanted to let you know that I've begun looking into this (I'm running 
jhalfs on my 32-bit and 64-bit systems because one of them could be 
affected by a time_t bug, and the other one is likely to have the glibc 
problems that you're reporting).



This will be my first system with glibc-2.31, so I'll likely have to run 
through a portion of BLFS to test the patch with glibc-2.31 as well (I 
might do this on my 32-bit machine because it takes longer to build than 
anything else, and I like to start that one ahead of package freeze anyway).



From the v244-stable repository, it looks like systemd may need fixes 
for BTRFS/LVM2 filesystems, as well as some patches for libcap-2.29+ 
(can someone check on that please? libcap-2.29+, linux-5.5, and 
glibc-2.31 seems to be causing problems for at least hwdb if not udev 
itself based off what I've seen in the systemd stable repository).



The PolicyKit security vulnerability is also fixed in the stable 
repository as well, so I'll backport that too.



Thank you for reporting,


- Doug

-- 
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

Re: [lfs-support] Building editor-manual

[Douglas R. Reno]

On 1/22/20 7:40 PM, Scott Andrews wrote:


On 1/22/20 3:03 PM, Bruce Dubbs wrote:

On 1/22/20 12:15 PM, Douglas R. Reno wrote:


On 1/22/20 11:40 AM, Scott Andrews wrote:
I am trying to build the lfs editor manual after downloading the 
source with svn


executing make nochunks returns the following error

 $ make nochunks
xsltproc --xinclude --nonet -stringparam profile.condition html \
--output ~/lfs-editors-guide/LFS-EDITORS-GUIDE.html \
  stylesheets/lfs-nochunks.xsl index.xml
I/O error : Attempt to load network entity 
http://docbook.sourceforge.net/release/xsl/1.69.1/xhtml/profile-docbook.xsl 

warning: failed to load external entity 
"http://docbook.sourceforge.net/release/xsl/1.69.1/xhtml/profile-docbook.xsl"; 

compilation error: file stylesheets/lfs-nochunks.xsl line 8 element 
import
xsl:import : unable to load 
http://docbook.sourceforge.net/release/xsl/1.69.1/xhtml/profile-docbook.xsl 


make: *** [Makefile:43: nochunks] Error 5

I have built the LFS SVN successfully so I am of the opinion that 
is a problem related to the building process used in the Makefile


Any way to get this to work?


Hi Scott,

I'm not sure on this as I haven't tried to build the editor manual, 
but my guess is that it's using an older version of the stylesheets. 
Bruce is probably the person to answer this one, but I can answer 
the question below:



Also How would you build the LFS-9.0 from the BOOK source?


If you're looking to render the book, do this (from within the 
trunk/BOOK folder of an SVN checkout):


make REV=sysv BASEDIR=~/wherever_you_want_your_files_output_to

To do a systemd build, replace "sysv" with "systemd" in the above 
command.


Here's an example from mine:

make REV=systemd BASEDIR=~/public_html/lfs-trunk-sysd


Or for the book, just use the defaults with 'make'.  sysv is the 
default.  Look at the Makefile for the other defaults.


As to why the LFS-EDITORS-GUIDE is not building, it is probably 
because the dependencies are not installed or configured properly.  
Here is what you need:


libxml2
libxslt
DocBook XSL Stylesheets (docbook-xsl-nons-1.79.2 in BLFS)
DocBook XML DTD-4.5 (docbook-4.5 in BLFS)
tidy

Pay close attention to the configuration of the docbook packages and 
their dependencies.


Also I note that there are some issues with the editor's guide 
because we haven't updated it lately.  Checking...


There has only been one minor change in the last 14 years, but the 
contents are still valid AFAICS.


I had to comment out hide-endtags and drop-font-tags in tidy.conf due 
to using a newer version of tidy and I also had to:


sudo mkdir -p /usr/share/xml/docbook/xsl-stylesheets-current/images/
sudo touch 
/usr/share/xml/docbook/xsl-stylesheets-current/images/dummy.png


  -- Bruce



This link does not exist any more

http://docbook.sourceforge.net/release/xsl/1.69.1/xhtml/profile-docbook.xsl 



I can confirm this, it seems that the oldest version that they have 
available on Sourceforge is 1.70.1 (2006-05-26 is the datestamp).


On an unrelated note, it seems that development has moved to Github: 
https://github.com/docbook/xslt10-stylesheets


--
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

Re: [lfs-support] Building editor-manual

[Douglas R. Reno]

On 1/22/20 11:40 AM, Scott Andrews wrote:
I am trying to build the lfs editor manual after downloading the 
source with svn


executing make nochunks returns the following error

 $ make nochunks
xsltproc --xinclude --nonet -stringparam profile.condition html \
--output ~/lfs-editors-guide/LFS-EDITORS-GUIDE.html \
  stylesheets/lfs-nochunks.xsl index.xml
I/O error : Attempt to load network entity 
http://docbook.sourceforge.net/release/xsl/1.69.1/xhtml/profile-docbook.xsl
warning: failed to load external entity 
"http://docbook.sourceforge.net/release/xsl/1.69.1/xhtml/profile-docbook.xsl";
compilation error: file stylesheets/lfs-nochunks.xsl line 8 element 
import
xsl:import : unable to load 
http://docbook.sourceforge.net/release/xsl/1.69.1/xhtml/profile-docbook.xsl

make: *** [Makefile:43: nochunks] Error 5

I have built the LFS SVN successfully so I am of the opinion that is a 
problem related to the building process used in the Makefile


Any way to get this to work?


Hi Scott,

I'm not sure on this as I haven't tried to build the editor manual, but 
my guess is that it's using an older version of the stylesheets. Bruce 
is probably the person to answer this one, but I can answer the question 
below:



Also How would you build the LFS-9.0 from the BOOK source?


If you're looking to render the book, do this (from within the 
trunk/BOOK folder of an SVN checkout):


make REV=sysv BASEDIR=~/wherever_you_want_your_files_output_to

To do a systemd build, replace "sysv" with "systemd" in the above command.

Here's an example from mine:

make REV=systemd BASEDIR=~/public_html/lfs-trunk-sysd

--
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

Re: [lfs-support] e2fsprogs-1.45.5 make check hanging after 5 hours

[Douglas R. Reno]

On 1/12/20 10:54 AM, Alan Feuerbacher wrote:

On 1/12/2020 9:00 AM, Bruce Dubbs wrote:

On 1/12/20 12:33 AM, Alan Feuerbacher wrote:


On 1/11/2020 11:19 PM, Bruce Dubbs wrote:

On 1/11/20 11:46 PM, Alan Feuerbacher wrote:
I'm building the development version of LFS systemd, and today 
found that a few programs had been updated, so I'm building them 
again.


e2fsprogs-1.45.5 built ok, but make check is still hanging after 5 
hours. I'll let it run all night and see what happens. Any clues 
as to the hanging?


Version 1.45.4 checked ok.


The checks took about seven minutes for me. Most tests output a 
line like


f_h_badnode: hash directory with bad HTREE nodes: ok

What was the last test that passed for you?

  -- Bruce


I'm not quite sure how to answer that. There are many pages of test 
output. The last line before the hang is:


m_hugefile_slack: mke2fs create hugefile fs with slack: ok


The next lines should be

f_bbfile: bad blocks in files: ok
f_zero_group: fallback for damaged group descriptors: ok
j_short_trans: transaction nuking the bitmaps: ok
d_fallocate: fallocate sparse files and big files: ok
f_preen: preen shouldn't destroy backup superblocks: ok
r_move_itable: filesystem resize which requires moving the inode 
table: ok

...

You can try deleting tests/f_bbfile and rerunning the tests.
You can also chech to see how much space you have free in the lfs 
partition and how much memory you have free.


Other than that, I do not have any other ideas.

  -- Bruce

After hanging for 13 hours, I Control-C'd it, but that didn't kill the 
process. Apparently the Fedora host system had also hung, since when I 
tried to do other normal things, various things were broken. I 
couldn't even log out normally, and had to power down the computer.


After I powered back up, Fedora seemed ok, so I went back into the 
chroot environment in my normal way, and tried rebuilding the previous 
e2fsprogs-1.45.4 . Although it passed the tests the first time around 
in Section 6 of the LFS book, this time it failed the tests (I've 
saved logfiles of make and make check). So I have to conclude that 
something in the later software installations (I've installed a great 
many BLFS programs) has broken e2fsprogs. Comments?


Then I tried building e2fsprogs-1.45.5 again. This time, make check 
ran without hanging, but ended with virtually the same test failure 
messages as for 1.45.4 (I've saved logfiles of make and make check). 
The last bit of failure message is:


##

. . .

making check in tests
make[1]: Entering directory '/sources/e2fsprogs-1.45.5/build/tests'
Running e2fsprogs test suite...

/bin/cp ../../tests/mke2fs.conf.in mke2fs.conf
../../tests/scripts/gen-test-data > test_data.tmp
Creating test_one script...
f_illitable_flexbg: illegal inode table with FLEX_BG: ok
r_expand_full: expand a totally full filesystem: failed
f_imagic_fs: imagic filesystem with imagic inodes: ok
f_badsymlinks: corrupted symlinks: ok
m_64bit_flexbg: mkfs with 64bit and flex_bg: ok
u_mke2fs_opt_oddsize: e2undo with mke2fs -z and non-32k-aligned bdev
size: failed
f_baddir2: salvage last directory entry: ok
d_dumpe2fs_group_only: dumpe2fs group only mode: ok
../../tests/u_corrupt_blk_csum_force/script: line 22: / 1024 : syntax
error: operand expected (error token is "/ 1024 ")
make[1]: *** [Makefile:384: ../../tests/u_corrupt_blk_csum_force] Error
1
make[1]: Leaving directory '/sources/e2fsprogs-1.45.5/build/tests'
make: *** [Makefile:419: check-recursive] Error 1

##

At this point I'm thinking of starting from scratch on a new hard 
drive, but that's an awful lot of time and work, and I don't want to 
do that until I understand what's happening with the above tests.


Alan


Good morning Alan,


What version of the kernel is in use on your host system? I noticed you 
said that you'd completed some BLFS packages - if you reboot into LFS 
and try the tests again, does it have the same problem? What you said 
originally sounds like a kernel panic or OOPS.


On my development system (a 4-core Core i5-6600k Skylake machine), I had 
no problems with the tests. I have almost all of BLFS installed, 
including all of the packages in the Filesystems chapter (I have to for 
Parted and friends for gvfs + udisks). My kernel version is 5.3.14.


u_mke2fs: e2undo with mke2fs: ok
f_encrypted_lpf: encrypted lost+found directory: ok
r_64bit_big_expand: : skipped (slow test)
r_resize_inode: filesystem resize with a resize_inode present: ok
f_resize_inode: e2fsck with resize_inode: ok
e_brel_bma: block relocation table using memory array implementation: 
skipped

f_inlinedata_flags: check incorrect inline_data flags: ok
m_raid_opt: raid options: ok
m_minrootdir: create fs image from dir, then minimize it: ok
f_dirlink: directory hard links: ok
357 tests succeeded 0 tests failed
Creating test_script...
make[1]: Leaving directory '/sources/e2fsprogs-1.45.4/build/tests'

The tests took me about a 60 seconds to complete.

- Doug

--

Re: [lfs-support] Where to place downloaded "blfs-systemd-units-20191026" ?

[Douglas R. Reno]

On 1/4/20 12:41 PM, Alan Feuerbacher wrote:


I'm at the end of the LFS book and installing a few helpful
BLFS programs, using
Beyond Linux® From Scratch (systemd Edition) - Version 2020-01-03

At the end of installing Cyrus SASL-2.1.27 you're supposed to
run "make install-saslauthd" after downloading the file in
"blfs-systemd-units-20191026". The question is where this
should be downloaded to.

The section BLFS Systemd Units states:

. . . When a systemd unit is requested from BLFS Systemd Units,
simply change to the directory, and as the root user, execute
the given make install- command. . .

Change to what directory?

I've downloaded the blfs-systemd file to $LFS/sources and to
$LFS/sources/cyrus-sasl-2.1.27, switched to those directories,
and executed "make install-saslauthd". It fails with the
message:

make: *** No rule to make target 'install-saslauthd'.  Stop.

I've done this hundreds of times with no problems when I last
built LFS several years ago, with no issues.

What am I missing?

The section also states:

It is advisable to peruse each systemd unit before installation
to determine whether the installed files meet your needs.

I've looked at the "blfs-systemd-units-20191026" file, but
vim indicates nothing useful inside.

Alan

Place the blfs-systemd-units tarball in the same place as the other 
tarballs. Extract it using the tar command like you would normally, and 
then cd into it (example: tar -xf blfs-systemd-units-20191026.tar.xz && 
cd blfs-systemd-units-20191026)


You can then run a "vi blfs/units/saslauthd.service" for example and 
make sure that it fits your needs. In the majority of cases, it should 
meet the needs of the user by default. Since you're specifically 
mentioning Cyrus SASL, make sure you view blfs/default/saslauthd just to 
make sure that it meets the needs that you're looking for.


Thank you,

- Doug

-- 
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

Re: [lfs-support] compile 32-bit kernel on a 64-bit LFS?

[Douglas R. Reno]

On Wed, Dec 11, 2019, 9:57 AM Thomas Seeling  wrote:

> Hallo,
>
> > make i386_defconfig
> > make menu config (to customize the kernel)
>
> would it be sufficient to use the exact .config file from the previous
> compile on a 32-bit system?
>

It should be, you already have the "64-bit System" portion not ticked on
your 32-bit kernel config I presume. That should be all you need, but it's
been a while since I've done it. My 32-bit system, an Intel Core Duo (no 2,
it's the 32-bit only Core variant), compiles its own kernel. Its not nearly
as painful as a P4 though.

>
> Tschau...Thomas
> --
> Do you wanna be a legend or a passing footprint on the sands of time?
>

Nice signature!

> --
>
-- 
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

Re: [lfs-support] kernel compilation requires cpio?

[Douglas R. Reno]

On 11/30/19 3:11 PM, Bruce Dubbs wrote:

On 11/30/19 1:15 PM, Thomas Seeling wrote:

Hallo,


I started LFS 9.0 on a fresh partition and it stopped at step 158 (of my
jhalfs numbering) where it compiles the kernel ... it nearly finishes
but then complains about cpio missing.

   CC  kernel/rseq.o
   AR  kernel/built-in.a
   GZIP    kernel/config_data.gz
   CC [M]  kernel/configs.o
   CHK kernel/kheaders_data.tar.xz
   GEN kernel/kheaders_data.tar.xz
./kernel/gen_kheaders.sh: line 61: cpio: command not found
make[2]: *** [kernel/Makefile:131: kernel/kheaders_data.tar.xz] Error 
127

make[1]: *** [Makefile:1085: kernel] Error 2

I built cpio on the fly and it seems to work now but I cannot remember I
needed to build cpio before for the base system (I'm a happy user since
LFS 6). I've built cpio afterwards anyway for initramfs and early
microcode loading but not for the initial kernel compilation.

Is this something new like the requirement for rsync?


I don't know right now.  I am going to start an update to LFS today 
and there are several new packages, including the kernel.  I don't 
normally rebuild the kernel in chroot, but I'll do that this time.


  -- Bruce

I bumped into this one a while back. I suggest that we document that the 
option needs to be disabled in the LFS kernel configuration page. The 
option is misleading, making users think that they'd benefit from it 
because it installs system headers in a convenient way for the system to 
access. The kernel configuration option in question is CONFIG_IKHEADERS, 
and it uses cpio to generate the kheaders_data.tar.xz file that is 
accessible in /proc. I think Ken mentioned that Android is the primary 
consumer - this might be an artifact of Google trying to mainline their 
kernel changes for Android.


--
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

Re: [lfs-support] Known Working Distro for Latest Stable

[Douglas R. Reno]

On 2019-11-26 14:39, Bruce Dubbs wrote:

On 11/26/19 1:27 PM, Xi Ruoyao wrote:

On 2019-11-26 12:54 -0600, Bruce Dubbs wrote:

On 11/26/19 9:30 AM, Xi Ruoyao wrote:


But on Arch (and some other distributions) non-login bash loads
/etc/bash.bashrc before .bashrc.  The environments in bash.bashrc
may
pollute the LFS building environment.  For example, on Arch, our
$PS1
(set in .bash_profile, should be '\u:\w\$ ') would be overwritten
(become `[\u@\h \W]\$ ').


With the exception of PS1, is there anything else in
/etc/bash.bashrc
that interferes with the lfs user's environment?  We could easily
fix
the PS1 issue by adding

PS1='\u:\w\$ '

to our .bashrc.


On Arch Linux it also sets $PROMPT_COMMAND, and then sources
/usr/share/bash_completion/bash_completion (!).


We could also add a note for the user to check the contents of
/etc/bash.bashrc and, if needed, move it out of the way.

Also, I wonder if using

exec env -i HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash --rcfile
~/.bashrc

would disable sourcing /etc/bash.bashrc.


No.  I tried that.

I found a solution with Google:

/home/lfs/.bash_profile:

 exec env -i ENV=$HOME/.bashrc \
 HOME=$HOME TERM=$TERM PS1='\u:\w\$ ' /bin/bash --posix

/home/lfs/.bashrc:

 set +o posix
 set +h
 umask 022
 #  (same as LFS book)

"--posix" will start POSIX mode and disable rc file loading.  Then we
use "ENV=$HOME/.bashrc" to tell bash to load our .bashrc file.  At 
last

use "set +o posix" in .bashrc to exit POSIX mode.


That looks good.  I don't have a system that uses /etc/bash.bashrc so
I can't test it.  If you say it works for you, I'll add it.



Also, I am running into an issue I haven't noticed before.  On my
existing system if I try to log in as user lfs with .bash_profile set,
it automatically starts bash and then puts it into the background.

# su - lfs
[1]+  Stopped su - lfs
# jobs
[1]+  Stopped su - lfs
# fg
su - lfs
lfs:~$

The rules in the book work OK as .bash_profile is not present when we
initially change to user lfs and then we source .bash_profile.  That
works.

It could have something to do with PAM and su, but I'm not sure.  Has
anyone else seen this?

  -- Bruce


Yes I have, it's happening on Debian 10 and on LFS now. I'm not sure 
what's causing it

--
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

Re: [lfs-support] Kernel panic when loading init on real hardware, fine in VM

[Douglas R. Reno]

On 11/26/19 12:11 PM, JackMacWindows wrote:

Hello,
I've just finished setting up an x86_64 LFS installation on a flash 
drive. I have followed the LFS 9.0 book almost exactly, except that I 
upgraded the kernel to 5.2.21, and I'm using UEFI instead of BIOS for 
GRUB using the hint given in Chapter 8.4. To test the new setup, I ran 
a QEMU VM using the OVMF EFI, booting from the drive via -hda. It 
worked fine, booting to the Bash prompt and everything. I then tested 
the installation on real hardware, but the kernel panicked saying it 
couldn't find init. But even after setting init=/sbin/init, Linux 
still panicked saying "Requested init /sbin/init failed (error -2)". I 
have tried reinstalling sysvinit to no avail, and I have been unable 
to reproduce the issue in any VM (QEMU, VirtualBox). Loading the 
kernel manually in QEMU (-kernel) works too, which bypasses the UEFI 
entirely. I've also tried using different computers, but they still 
have the same problem. Does anybody have any idea why this may be 
happening?


Hi Jack,

It seems that you're getting your system to initialize the kernel, so 
that's a good sign. At this point, this normally leads to a driver 
problem (although I only have legacy systems, I have UEFI/secure boot 
disabled on my newer equipment). I'm assuming that you have another 
distro on your real hardware, but if you don't, you can boot something 
like SystemRescueCD off a CD or USB drive to check this. At a terminal, 
execute the following:


lspci -vv | grep driver


The next thing you're going to want to do is run 'make menuconfig' in 
your kernel sources, and then press the "/" key (shortcut for "Find"), 
and type in the name of each driver (it'll be in the output of "kernel 
driver in use:"). Make sure that each one is enabled (built in, not 
modules), especially the driver for your SATA controller.


After that, make sure that you have the proper filesystem support built 
in. I know you've got it to boot in a VM though, so I'm sure this is 
redundant, but it's important to make sure it's enabled anyway :-)


-- 
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

Re: [lfs-support] Known Working Distro for Latest Stable

[Douglas R. Reno]

On 11/25/19 6:56 PM, Bran Stringer wrote:
Does anyone have a recommendation for a distro they know has worked 
for the latest stable as a host? I just fresh installed CentOS Linux 
release 7.7.1908 (Core) and immediately ran into trouble with gcc 
pass1. I successfully built an LFS host February of this year using 
Fedora 28 I think it was as a host.


Thanks in advance!

- Bran



Hi Bran,


When I bootstrap a new LFS system from scratch, I normally use Debian. 
Debian 10 "Buster" works great for bootstrapping purposes. I will note 
that I have a PowerMac G4 running Ubuntu LFS 16.04 LTS (I know it has 
the same versions as normal 16.04), and the GCC is too old (gcc5 is 
shipped with Ubuntu 16.04). I recommend Ubuntu 18.04 or higher if you're 
going to be bootstrapping LFS 9.0 or higher.


TL;DR - I recommend Debian 10 "Buster", it works the best in my 
experience (especially on x86_64 and i686).


- Doug

--
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

Re: [lfs-support] Seems to be error and/or missing package v9.0 BLFS Systemd - Chapter 2

[Douglas R. Reno]

On 10/25/19 9:11 AM, Bruce Hill wrote:

On Wed, Oct 23, 2019 at 09:41:32PM -0500, Trent wrote:

 From here:

http://www.linuxfromscratch.org/blfs/view/stable-systemd/introduction/systemd-units.html


The link is for Systemd Units


Download: 
http://www.linuxfromscratch.org/blfs/downloads/9.0-systemd/blfs-systemd-units-20180105.tar.bz2


Instead of downloading a file, it takes you to


  Page not found!

Perhaps you mistyped the URL?

In the case of a broken link, please contact the webmaster
.


Clicking on the "contact the webmaster" appears to do nothing.


Trent


Perhaps you DID mistype the URL. Try copy and paste:

mingdao@workstation ~/LFS $ wget  
http://www.linuxfromscratch.org/blfs/downloads/9.0-systemd/blfs-systemd-units-20180105.tar.bz2
--2019-10-25 09:10:15--  
http://www.linuxfromscratch.org/blfs/downloads/9.0-systemd/blfs-systemd-units-20180105.tar.bz2
Resolving www.linuxfromscratch.org (www.linuxfromscratch.org)... 
192.155.86.174, 2600:3c01::f03c:91ff:fe70:25e8
Connecting to www.linuxfromscratch.org 
(www.linuxfromscratch.org)|192.155.86.174|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8383 (8.2K) [application/x-bzip2]
Saving to: ‘blfs-systemd-units-20180105.tar.bz2’

blfs-systemd-units-20180105.tar.bz2 
100%[==>]
   8.19K  --.-KB/sin 0s

2019-10-25 09:10:15 (81.4 MB/s) - ‘blfs-systemd-units-20180105.tar.bz2’ saved 
[8383/8383]


Greetings,


This was fixed soon after it was discovered yesterday which is why it 
works now. Originally, the file was not present in the correct directory 
on the server side:


-rw-rw-r-- 1 bdubbs lfswww 8383 Oct 24 09:14 
blfs-systemd-units-20180105.tar.bz2


It was also originally tarred up in .xz format, but was listed as a .bz2 
format in the book. It will continue as a .xz in the future due to the 
potential of bzip2 requiring rustc.


--
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

Re: [lfs-support] Important software missing from LFS Basic System

[Douglas R. Reno]

On 10/24/19 12:34 AM, DJ Lucas wrote:




Poor naming and I haven't actually tested that last one, but it is 
available. Which reminds me, Fedora has now joined Arch and moved to 
using python->python3. Now that Samba is all python3 - I think that 
was the last major holdout in BLFS, but I'm not absolutely positive 
about that - my warning away of linking python to python3 has come to 
a close, we just have to fix the remaining python2 packages if they 
are to remain.


--DJ

I believe telepathy's build is Python 2 only as well. I'm starting to 
wonder if it might be worth doing upstream's job for them though. I 
ordered a book for this last week that covers transitioning existing 
code from python2 to python3. Now that we have Python-3.8 though, with 
it's changes to the type system, the text could be different.


--
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

Re: [lfs-support] Systemd-Journald Flood of "Missed kernel messages" While Running

[Douglas R. Reno]

On 2019-10-20 13:35, Jared Stevens wrote:

Hi everyone,

I have just gotten my LFS 9.0 build with Systemd up and running and
was able to successfully boot and login.

However, I am experiencing an issue where the following log message
will appear over and over again on the console screen:

SYSTEMD-JOURNALD[1460]: /DEV/KMSG BUFFER OVERRUN, SOME MESSAGES LOST

Viewing the SYSTEMD-JOURNALD with _JOURNALCTL -R_ shows literally
thousands of the same entry repeated:

Oct 19 22:35:54 lfs-jws kernel: *** thread awakened
Oct 19 22:35:54 lfs-jws kernel: *** thread sleeping
Oct 19 22:35:54 lfs-jws kernel: scsi cmd done, result=0x0
Oct 19 22:35:54 lfs-jws kernel: Bulk Status S 0x53425355 T 0x17ece R 0
Stat 0x0
Oct 19 22:35:54 lfs-jws kernel: Bulk status result = 0
Oct 19 22:35:54 lfs-jws kernel: -- transfer complete
Oct 19 22:35:54 lfs-jws kernel: Status code 0; transferred 13/13
Oct 19 22:35:54 lfs-jws kernel: xfer 13 bytes


Hi Jared, this is unrelated to the kernel problem here, but you might 
want to check your hard drive. Normally the kernel doesn't spam scsi 
messages to the logs unless something is wrong or configured improperly. 
It could be a DVD drive with a bad DVD in it too, or something similar. 
Try running a 'dmesg' as well.


You might be able to stop journald in the meantime, but it might start 
spamming on the console with what's ending up in the logs

--
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

Re: [lfs-support] Bash: /usr/{literally everything}: no such file or directory

[Douglas R. Reno]

On 10/14/19 2:06 PM, Jared Stevens wrote:


We need to address the "no such file or directory" problem first.
Can you run:

ldd /bin/ls

Please and get back to us with the results? What you should get
(used on an SVN system):

renodr [ /sources ]$ ldd /bin/ls
    linux-vdso.so.1 (0x7ffe3b1e8000)
    libcap.so.2 => /lib/libcap.so.2 (0x7fcfff8c)
    libc.so.6 => /lib/libc.so.6 (0x7fcfff6fc000)
    /lib64/ld-linux-x86-64.so.2 (0x7fcfff8e2000)

I believe that your glibc installation might be corrupt. If your
glibc install is corrupt, try using this:

sln libc-2.30.so  /lib/libc.so.6

And then running 'ldconfig'.

We've made some progress!

So the initial output of *'ldd /bin/ls'* was:

*bash: /usr/bin/ldd : /bin/bash: bad interpreter: No such file or 
directory*


And the output of '*sin libc-2.30.so  
/lib/libc.so.6'* was:


*bash: sin: command not found*

Regardless, I ran the*'ldconfig' *command anyways and after a brief 
pause was given the following output:


*ldconfig: Cannot mmap file /usr/lib/libdbus-1.so*

HOWEVER, following this command I was finally able to run commands in 
the /bin directory once again (such as 'ls'), and the output of*'ldd 
/bin/ls'* changed to:


*linux-vdso.so.1 (0x7ffea7f1a000)
libcap.so.2 => /lib/libcap.so.2 (0x7f1b55ef5000)
libc.so.6 => /lib/libc.so.6 (0x7f1b55d31000)
/lib64/ld-linux-x86-64.so.2 (0x7f1b55f1f000)*

Unfortunately, the 'sin' command still outputs the same result. So now 
it appears there is an issue with the libdbus file.


My PATH variable was also restored to how it was before these events 
took place:


*PATH=/opt/rustc/bin:/usr/local/sbin:/usr/local/bin:/bin:/usr/bin:/sbin:/usr/sbin:/opt/ant/bin:/opt/jdk/bin:/opt/qt5/bin*

So while everything but that one error with libdbus looks back to 
normal for the moment, I am afraid to try and install (or reinstall) 
anything or change any file locations or settings until I know for 
sure this issue is resolved.


What would you recommend my next steps going forward should be to fix 
libdbus and ensure this issue has been fixed? Furthermore, as I have 
made it this far and you have the experience, what should I do to 
finish the transition from System V to systemd smoothly to avoid 
another potential catastrophe such as this?


As for the dbus problem, try running:

ln -sv ../../lib/libdbus-1.so.3.19.11 /usr/lib/libdbus-1.so

Make sure that you have that library in /lib first

As for some further advice on the sysv to systemd transition, be 
prepared to rebuild X from scratch. You might encounter problems if 
ConsoleKit is installed too. If you have elogind installed, please 
uninstall it. You'll want to rebuild Xorg Libraries, Xorg Applications, 
and xorg-server at minimum (and that should do the trick...)


-- 
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

Re: [lfs-support] Bash: /usr/{literally everything}: no such file or directory

[Douglas R. Reno]

On 10/14/19 12:33 AM, Jared Stevens wrote:
So I have little doubt that I have somehow managed to completely ruin 
my LFS build and will likely have to start all over again (for what 
will be the fourth time). I figured I would throw one last Hail Mary 
and ask in here for any suggestions, however, before giving up on 
two/three weeks of hard work.


So just a little backstory, I initially built my LFS system using the 
*System V *version of the book. I was able to boot and had made 
progress all the way up to Xorg.


However, I was having issues with getting certain modules/services to 
load and run properly on my system, and having no experience 
whatsoever with System V (only systemd in my past experiences with 
Linux), I decided to see if I could*switch my system over to systemd.*


Initially, there weren't any problems. I was able to install 
Systemd-241 no problem, and I moved the rc.d and init.d directories 
elsewhere to hopefully prevent any old scripts from being called.


Of course this now meant that I had to reinstall certain programs and 
their systemd symlinks as opposed to the System V bootscripts. I had 
been doing this for most of the day today with little issue.


While I was looking back over previously installed programs for 
changes from System V to systemd, I noticed the section in LFS's 
Glibc-230 install where it calls for _systemd support files for 
_*_nscd_, *which were not installed when I initially built Glibc-230.


Here is where I made my first mistake: to install the support files 
for *nscd*, I assumed I would have to re-make the *GLibc* package and 
install them. So to follow the LFS book's commands properly (where it 
uses "CC="gcc -ffile-prefix-map=/tools=/usr" before the configure) I 
extracted my saved "tools" directory I had saved from the build back 
into my LFS build in chroot and reran the configure, make, and make 
check commands for GLibc.


To avoid potential problems and because my existing GLibc install was 
working fine, however, I did NOT run "make install." Instead, I ran 
just the install commands for nscd as follows:


install -v -Dm644 ../nscd/nscd.tmpfiles
/usr/lib/tmpfiles.d/nscd.conf
install -v -Dm644 ../nscd/nscd.service
/lib/systemd/system/nscd.service

Afterwards, I removed the GLibc directory and attempted to continue 
with my transfer to systemd. However, this is when all hell broke loose.


Now, whenever I enter the chroot environment (haven't even tried 
booting the thing because I doubt I could), although I can login as 
root and mount all of the disk partitions properly, Bash cannot find 
absolutely anything in the /usr, /sbin, or /bin directories any longer.


For example, I will receive the following error for simple commands 
such as 'ls':


bash: /bin/ls: No such file or directory

This is despite the fact that such file DOES in fact exist. Assuming I 
had messed up my $PATH variable, I tried restoring it by executing:


export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

However, this did not fix my issue. I tried retracing my steps in LFS 
to see if a symlink was broken or something, but even though I can run 
'ls' and other commands when running off of the /tools bash symlink, 
attempts at running the normal bash is completely broken.


I haven't the slightest clue what I did wrong to affect Bash during 
the GLibc systemd attempted fix as I never touched bash until after 
the problem manifested (I may have made it worse while trying to fix 
it, however). Furthermore, I never overwrote my existing GLibc install.


I appreciate any suggestions that may help with my problem. I also 
accept if I have managed to royally destroy my build and would be 
better off starting over again as well.


Hi Jared,

Firstly, I don't recommend moving from SysV to systemd on the same 
build, however it is possible and I used to do it. We need to address 
the "no such file or directory" problem first. Can you run:


ldd /bin/ls

Please and get back to us with the results? What you should get (used on 
an SVN system):


renodr [ /sources ]$ ldd /bin/ls
    linux-vdso.so.1 (0x7ffe3b1e8000)
    libcap.so.2 => /lib/libcap.so.2 (0x7fcfff8c)
    libc.so.6 => /lib/libc.so.6 (0x7fcfff6fc000)
    /lib64/ld-linux-x86-64.so.2 (0x7fcfff8e2000)

I believe that your glibc installation might be corrupt. If your glibc 
install is corrupt, try using this:


sln libc-2.30.so /lib/libc.so.6

And then running 'ldconfig'.


The reason why this might fix it is that 'sln' is linked statically so 
that you can use it in the event that the dynamic linker is not 
available or functioning properly. It was written to fix broken glibc 
installations so that you're not stuck completely rebuilding your system.


-- 
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

Re: [blfs-support] gdm: how to use a non us keyboard?

[Douglas R. Reno via blfs-support]

On 8/23/19 11:01 AM, Pierre Labastie via blfs-support wrote:

On 23/08/2019 11:50, Christopher Gregory via blfs-support wrote:



Sent: Friday, August 23, 2019 at 9:05 PM
From: "Christopher Gregory via blfs-support" 

To: blfs-supp...@lists.linuxfromscratch.org
Cc: "Christopher Gregory" 
Subject: Re: [blfs-support] gdm: how to use a non us keyboard?




Sent: Friday, August 23, 2019 at 7:25 PM
From: "Pierre Labastie via blfs-support" 

To: blfs-supp...@lists.linuxfromscratch.org
Cc: "Pierre Labastie" 
Subject: Re: [blfs-support] gdm: how to use a non us keyboard?

On 23/08/2019 04:14, Christopher Gregory via blfs-support wrote:

Hello,

There is a thread from earlier this year that I found regarding gdm and non-us 
keyboards.  Though some of it is systemd related, the same files should be able 
to be modified for e-logind:

https://forums.nomachine.com/topic/wrong-keyboard-layout-during-login-in-ubuntu

The main fix seems to be at the last post, but even in that post the person who 
posted the solution refers to a post they made further up.

Regards,

Christopher.


Sent: Friday, August 23, 2019 at 10:14 AM
From: "Ken Moffat via blfs-support" 
To: "BLFS Support List" 
Cc: "Ken Moffat" 
Subject: Re: [blfs-support] gdm: how to use a non us keyboard?

On Thu, Aug 22, 2019 at 06:41:21PM +0200, Pierre Labastie via blfs-support 
wrote:

Hi,

I've completed the build of BLFS Sysv-elogind on LFS-9.0-rc1. Apart from what
I've already reported, things are going rather well, but I have a problem with
gdm: At first I thought it was not working, since I could not log in, while I
could "startx" gnome, or lxde without problem.

Then, I noticed that when "startx'ing" gnome, the keyboard was set to us,
while I have:
Section "InputClass"
 Identifier "libinput keyboard catchall"
 MatchIsKeyboard "on"
 MatchDevicePath "/dev/input/event*"
 Driver "libinput"
 Option "XkbLayout" "fr"
in /etc/X11/xorg.conf.d/40-libinput.conf

Inside gnome, I could add a keyboard using the settings manager, and switch to
the fr layout, but this made me think that the keyboard layout in gdm was
still us. So I typed my password as if I was on a us keyboard (well, not so
easy :), and bingo, gnome started...

So gdm is working, but I've not found any way to have it use a French kb 
layout...

I've tried adding "setxkbmap fr" at the end of /etc/gdm/Init/Default, but it
did not work.
So I do not know where to set this.

Note that American or British users are not likely to be affected :)

Pierre

Actually, British users will affected a little (but clearly not as
much as people with azerty or qwertz keyboards) - in Britain we have
'£' where americans have '#', we swap '"' and '@', and '#' + '~',
'|' + '\' move around (ISTR British '|' and '\' are on a key
position which American keymaps lack).

Good Luck with this, there are lots of old reports related to this,
but things may have changed in newer versions of gnome.  The Arch
wiki appears to suggest updating the Xorg configuration (or using
localectl for systemd) and restarting X (presumably a reboot if in
runlevel 5).

I notice you have done this in 40-libinput.conf as the catchall, in
my own builds I separate the keyboard definition to an earlier file.

The example at Arch for Xorg, linked from the gdm page
https://wiki.archlinux.org/index.php/GDM is
https://wiki.archlinux.org/index.php/Xorg/Keyboard_configuration#Using_X_configuration_files
with 00-keyboard.conf, so it gets read first, and uses
Identifier "system-keyboard" - I can't believe that the name
_ought_ to be important, but perhaps it is.

On the desktop where I'm writing this with a British keyboard I
have:

10-quirks.conf

Default modifications for specific pointing devices or a specific
accelerometer.

11-keyboard.conf

My own keyboard settings (two extended variant gb maps with compose
and group switching) - described as Identifier "keyboard-all" :

Section "InputClass"
 Identifier "keyboard-all"
 Driver "libinput"
 # for my own russian variant, specific to a gb keyboard, I put it in gb
 Option "XkbLayout" "gb,gb"
 # I assume that the model will remain as evdev
 Option "XkbModel" "evdev"
 # add my own 'deader' gb variant - more dead keys
 Option "XkbVariant" "deader,rusphon"
 Option "XkbOptions" 
"ctrl_alt_bksp,grp:lctrl_lwin_rctrl_menu,compose:caps"
 MatchIsKeyboard "on"
EndSection

40-libinput.conf

which includes

Section "InputClass"
 Identifier "libinput keyboard catchall"
 MatchIsKeyboard "on"
 MatchDevicePath "/dev/input/event*"
 Driver "libinput"
EndSection

All I can suggest is to move the keyboard definitions to an earlier
file and restart X (which probably means rebooting from runlevel 5).

Ah, I continued looking for anything which might be relevant (rather
than the more common unsolved, or solved by an upgrade, results) and
found an old (January 2015) comment in a mageia thr

Re: [lfs-support] version check

[Douglas R. Reno]

On 8/4/19 10:16 AM, Jack Ditchburn wrote:

Pierre,

Thanks for the swift reply.

I now have

bash, version 4.4.20(1)-release
/bin/sh -> /bin/bash
Binutils: (GNU Binutils for Ubuntu) 2.30
bison (GNU Bison) 3.0.4
/usr/bin/yacc -> /usr/bin/bison.yacc
bzip2,  Version 1.0.6, 6-Sept-2010.
Coreutils:  8.28
diff (GNU diffutils) 3.6
find (GNU findutils) 4.7.0-git
GNU Awk 4.1.4, API: 1.1 (GNU MPFR 4.0.1, GNU MP 6.1.2)
/usr/bin/awk -> /usr/bin/gawk
gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
g++ (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
(Ubuntu GLIBC 2.27-3ubuntu1) 2.27
grep (GNU grep) 3.1
gzip 1.6
Linux version 4.15.0-54-generic (buildd@lgw01-amd64-014) (gcc version 
7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #58-Ubuntu SMP Mon Jun 24 
10:55:24 UTC 2019

m4 (GNU M4) 1.4.18
GNU Make 4.1
GNU patch 2.7.6
Perl version='5.26.1';
Python 3.6.8
sed (GNU sed) 4.4
tar (GNU tar) 1.29
texi2any (GNU texinfo) 6.5
xz (XZ Utils) 5.2.4
g++ compilation OK

So all sorted I think.

Jack



Please try not to top post.


It looks great to me!

-- 
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

Re: [lfs-support] Issue with Linux-5.2.1 and the network interface (systemd)

[Douglas R. Reno]

On 7/21/19 4:56 PM, Wayne Blaszczyk wrote:

On Sun, 2019-07-21 at 20:36 +1000, Wayne Blaszczyk wrote:

On Sat, 2019-07-20 at 21:24 -0500, Douglas R. Reno wrote:

On Sat, Jul 20, 2019, 8:23 PM Wayne Blaszczyk  wrote:

This is the first time I'm building against the 5.2 kernel and have come across 
some issues.

Firstly, the network interface does not come up automatically.
The systemd boot process seems to hang on systemd-time-wait-sync. (At this 
point in time I do have the logon on prompt and I can log in)
If I execute 'ip link set dev enp0s3 up', the network interface does come up 
successfully and all the systemd jobs complete.
If I boot the same image with linux kernel 5.1.x, I don't have this issue.

Has anyone come across this

Hi Wayne,

I just found an upstream patch for this. Can you try it please?

https://github.com/systemd/systemd/issues/12784

I'm going to begin developing a patch.

My linux-5.2.1 environment has been trashed.
I'll kick of another build overnight with kernel 5.2.2 and will report back.

Regards,
Wayne.

I've confirmed that the following patches fixes the issue.

https://github.com/systemd/systemd/commit/4eb086a38712ea98faf41e075b84555b11b54362.patch
https://github.com/systemd/systemd/commit/9f6e82e6eb3b6e73d66d00d1d6eee60691fb702f.patch

Regards,
Wayne.



Hi Wayne,

I've started tracking this in BLFS Ticket #12230 
(http://wiki.linuxfromscratch.org/blfs/ticket/12330) and LFS Ticket 
#4506 (http://wiki.linuxfromscratch.org/lfs/ticket/4506) since it will 
require a patch to be placed in both books


--
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

Re: [lfs-support] Issue with Linux-5.2.1 and the network interface (systemd)

[Douglas R. Reno]

On 7/21/19 5:38 PM, Dave wrote:


On 7/21/19 5:56 PM, Wayne Blaszczyk wrote:

On Sun, 2019-07-21 at 20:36 +1000, Wayne Blaszczyk wrote:

On Sat, 2019-07-20 at 21:24 -0500, Douglas R. Reno wrote:
On Sat, Jul 20, 2019, 8:23 PM Wayne Blaszczyk 
 wrote:
This is the first time I'm building against the 5.2 kernel and 
have come across some issues.


Firstly, the network interface does not come up automatically.
The systemd boot process seems to hang on systemd-time-wait-sync. 
(At this point in time I do have the logon on prompt and I can log 
in)
If I execute 'ip link set dev enp0s3 up', the network interface 
does come up successfully and all the systemd jobs complete.
If I boot the same image with linux kernel 5.1.x, I don't have 
this issue.


Has anyone come across this

Hi Wayne,

I just found an upstream patch for this. Can you try it please?

https://github.com/systemd/systemd/issues/12784

I'm going to begin developing a patch.

My linux-5.2.1 environment has been trashed.
I'll kick of another build overnight with kernel 5.2.2 and will 
report back.


Regards,
Wayne.

I've confirmed that the following patches fixes the issue.

https://github.com/systemd/systemd/commit/4eb086a38712ea98faf41e075b84555b11b54362.patch 

https://github.com/systemd/systemd/commit/9f6e82e6eb3b6e73d66d00d1d6eee60691fb702f.patch 



Regards,
Wayne.

Question, are these patches for system V? from the address they say 
systemd.


Dave

These patches are systemd-specific, fixing issues in systemd-networkd. 
I'm still catching up, but your messages seem to be related to SysV, 
which is likely a different problem

--
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

Re: [lfs-support] Issue with Linux-5.2.1 and the network interface (systemd)

[Douglas R. Reno]

On Sat, Jul 20, 2019, 8:23 PM Wayne Blaszczyk 
wrote:

> This is the first time I'm building against the 5.2 kernel and have come
> across some issues.
>
> Firstly, the network interface does not come up automatically.
> The systemd boot process seems to hang on systemd-time-wait-sync. (At this
> point in time I do have the logon on prompt and I can log in)
> If I execute 'ip link set dev enp0s3 up', the network interface does come
> up successfully and all the systemd jobs complete.
> If I boot the same image with linux kernel 5.1.x, I don't have this issue.
>
> Has anyone come across this
>

Hi Wayne,

I just found an upstream patch for this. Can you try it please?

https://github.com/systemd/systemd/issues/12784

I'm going to begin developing a patch.

>
-- 
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

Re: [lfs-support] LFS 8.4 stalled at chapter 6 intltool-0.51.0

[Douglas R. Reno]

On 5/31/19 5:33 AM, Jack Ditchburn wrote:

List,

I am stuck at the subject line location in LFS 8.4. I am getting the 
below error:


(lfs chroot) root:/sources/intltool-0.51.0# ./configure --prefix=/usr
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for perl... /usr/bin/perl
checking for perl >= 5.8.1... 5.28.1
checking for XML::Parser... configure: error: XML::Parser perl module 
is required for intltool


My compilation of XML:Parser was error free (see below)

All tests successful.
Files=15, Tests=141,  0 wallclock secs ( 0.05 usr  0.01 sys +  0.44 
cusr  0.05 csys =  0.55 CPU)

Result: PASS
(lfs chroot) root:/sources/XML-Parser-2.44# make install
make[1]: Entering directory '/sources/XML-Parser-2.44/Expat'
Manifying 1 pod document
make[1]: Leaving directory '/sources/XML-Parser-2.44/Expat'
Manifying 6 pod documents
Files found in blib/arch: installing files in blib/lib into 
architecture dependent library tree
Installing 
/tools/lib/perl5/site_perl/5.28.1/x86_64-linux/auto/XML/Parser/extralibs.all
Installing 
/tools/lib/perl5/site_perl/5.28.1/x86_64-linux/auto/XML/Parser/Expat/Expat.a
Appending installation info to 
/tools/lib/perl5/5.28.1/x86_64-linux/perllocal.pod



According to this, it's installing XML-Parser in /tools, but Perl should 
be installed in /usr at this point.


Please check your PATH and make sure it's got /tools/bin at the end, and 
make sure you used "/tools/bin/bash --login +h" in the chroot command. 
That will ensure that you're not pulling executables out of /tools if 
they've been installed in the final system already.


-- 
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

Re: [lfs-support] Stalled on LFS 8.4 Section 6.7 - None of the executables can be found

[Douglas R. Reno]

On 2019-05-29 06:32, Vineet Jain wrote:

Hello,

I am building LFS from version 8.4 and run into issues in actually
building of the LFS System.
For me the Part II that is Preparing the host system seems to have
been completed successfully but the actual construction of LFS is
failing.

On trying to execute MAKE MRPROPER from the linux-4.20.12 folder
it gives me the error
/bin/sh: sed: command not found
Makefile:624: arch//Makefile: No such file or directory
make: *** No rule to make target 'arch//Makefile'.  Stop.

In fact other executables like tar, files also cannot be executed.

_Host sys being used is_
Ubuntu 18.04.2 LTS

_Version Check output_
Binutils for Ubuntu) 2.30
bison (GNU Bison) 3.0.4
/usr/bin/yacc -> /usr/bin/bison.yacc
bzip2,  Version 1.0.6, 6-Sept-2010.
Coreutils:  8.28
diff (GNU diffutils) 3.6
find (GNU findutils) 4.7.0-git
GNU Awk 4.1.4, API: 1.1 (GNU MPFR 4.0.1, GNU MP 6.1.2)
/usr/bin/awk -> /usr/bin/gawk
gcc (Ubuntu 7.4.0-1ubuntu1~18.04) 7.4.0
g++ (Ubuntu 7.4.0-1ubuntu1~18.04) 7.4.0
(Ubuntu GLIBC 2.27-3ubuntu1) 2.27
grep (GNU grep) 3.1
gzip 1.6
Linux version 5.0.5-050005-generic (kernel@tangerine) (gcc version
8.3.0 (Ubuntu 8.3.0-3ubuntu1)) #201903271212 SMP Wed Mar 27 16:14:07
UTC 2019
m4 (GNU M4) 1.4.18
GNU Make 4.1
Perl version='5.26.1';
Python 3.6.7
sed (GNU sed) 4.4
tar (GNU tar) 1.29
texi2any (GNU texinfo) 6.5
xz (XZ Utils) 5.2.2
g++ compilation OK



Your host system and requirements look OK.


The deviation from the book is
- did not delete the individual source folders after installation


This is a big problem. You'll need to restart from Chapter 5, and make 
sure that you remove source directories. That leads to contamination, 
because you might build with the wrong compiler - or when you get to 
Chapter 6, end up with problems like you've shown.



- did not compare the installations logs with the ones published on
the site so not certain if the installation of all temporary
components did go through correctly or not.



That's really unnecessary, I only recommend reviewing the logs if you're 
seeing weird test failures.



Am I missing a setting that needs to be done or do I need to
re-prepare the host system and start all over again ?



You'll need to start over, unfortunately. Make sure that you delete the 
individual source folders after installation.


- Doug
--
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

Re: [lfs-support] LFS-8.4 Perl segfaults during build

[Douglas R. Reno]

On 5/9/19 8:09 AM, Baho utot wrote:


On 5/9/19 2:40 AM, Ken Moffat wrote:

On Wed, May 08, 2019 at 09:47:40PM -0400, Baho utot wrote:

More info on segfaults:

built perl on pclinuxos saw no segfaults during the build

Opened the syslog and boom here it is:

May  8 21:41:16 desktop kernel: perl[16059]: segfault at 
7ffeba075ff8 ip

7ff75122dd85 sp 7ffeba076000 error 6 in
Storable.so[7ff751223000+14000]
May  8 21:41:16 desktop kernel: perl[16066]: segfault at 
7ffc0742bff8 ip

7fb95267653c sp 7ffc0742c000 error 6 in
Storable.so[7fb95266b000+14000]
May  8 21:41:16 desktop kernel: perl[16072]: segfault at 
7ffd42292ff8 ip

7f09a4b851fc sp 7ffd42293000 error 6 in
Storable.so[7f09a4b7b000+14000]
May  8 21:41:17 desktop kernel: perl[16095]: segfault at 
7fff15dbbff8 ip

7f09a780fa72 sp 7fff15dbc000 error 6 in
libperl.so[7f09a7761000+15d000]
May  8 21:41:17 desktop kernel: perl[16099]: segfault at 
7ffde0594ff8 ip

7fd4ad18d1f2 sp 7ffde0594fe0 error 6 in
Storable.so[7fd4ad183000+14000]
May  8 21:41:17 desktop kernel: perl[16109]: segfault at 
7ffed745ffc0 ip

7f5b83ac1ebd sp 7ffed745ffc0 error 6 in
ld-2.29.so[7f5b83ab9000+1e000]
May  8 21:41:17 desktop kernel: perl[16132]: segfault at 
7fffb59a8fd8 ip

7f9972d4f3cb sp 7fffb59a8fd0 error 6 in
Storable.so[7f9972d43000+14000]
May  8 21:41:17 desktop kernel: perl[16172]: segfault at 
7fffa7a92fe8 ip

7f0f722d11fe sp 7fffa7a92ff0 error 6 in
libc-2.29.so[7f0f7226d000+154000]
May  8 21:41:17 desktop kernel: perl[16174]: segfault at 
7ffc911c7fc8 ip

7f1b3a047e4b sp 7ffc911c7fc0 error 6 in
libc-2.29.so[7f1b39fe5000+154000]
May  8 21:41:17 desktop kernel: perl[16181]: segfault at 
7ffe790b9ff8 ip

7fcd75ed7e4b sp 7ffe790b9ff0 error 6 in
libc-2.29.so[7fcd75e75000+154000]

It looked like it built correctly from watching the build but if you 
don't

look in the syslog you will not know that they occured

Can some one have a look in their syslog after they just built perl 
to see

if it was clean?

I did the following:

tail -f /var/log/syslog

Yes it is syslog on pclinuxos and not sys.log


As it happens, I'm stuck in building current LFS-svn (failed sanity
check after installing gcc in chroot).  So, I've still got the
syslog from building perl in chapter 5, and yes, loads of segfaults
(but not as many as from the gcc tests).

So, presumably perl-5.26 is constructed differently from 5.26. Maybe
a side-effect of the work the perl maintainers put into fixing CVEs
last year.

And the reason why you saw these on the screen in LFS, but not in
pclinuxos is probably a matter of kernel/bootscript configuration:
For the LFS bootscripts, see section 7.6.5 'Configuring the Linux
Console' ('LOGLEVEL') : I'm using "4"

or for the kernel itself (this is from 5.0)
#
# printk and dmesg options
#
CONFIG_PRINTK_TIME=y
CONFIG_CONSOLE_LOGLEVEL_DEFAULT=7
CONFIG_CONSOLE_LOGLEVEL_QUIET=4
CONFIG_MESSAGE_LOGLEVEL_DEFAULT=4

Normally, if I look at the syslog after a build, it is at the end
and by that stage anything from chapter 5 is by definition not
interesting.

Summary: these segfaults fro mperl, and not just from running the
tests, turn out to be normal and can be configured out of the terms.
So, I was wrong in saying that they only came from failign tests.
Well, not the first time I've been wrong, I'm sure it will happen
again.

Hope the rest of it goes ok, and then when you hit problems in BLFS
please ask - but remember that not everyone has the same interests,
and very few people build exactly the same desktop packages.



I have also tried perl-5.28.2 same issue.

BLFS is a bit down the road,  want to get LFS-8.4 working oon a 
raspberry pi first




Here's some advice on that from my experiments a while back with it:

GCC needs a patch (applies cleanly in Pass 1, 2, and CH6):

https://intestinate.com/pilfs/patches/gcc-5.3.0-rpi3-cpu-default.patch 
(THIS IS FOR Pi 3s)


--
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

Re: [lfs-support] LFS 8.4 - Doubt at 6.35 with libltdl

[Douglas R. Reno]

On 4/22/19 2:02 PM, Francesc Ortiz Becerra wrote:
Thanks for your patience. But I'd found a message after make check on 
libtool:
123: compiling softlinked libltdl FAILED (standalone.at:35 
)
124: compiling copied libltdl FAILED (standalone.at:50 
)
125: installable libltdl FAILED (standalone.at:67 
)
126: linking libltdl without autotools FAILED (standalone.at:85 
)
130: linking libltdl without autotools FAILED (subproject.at:115 
)


Is it safe to continue? If not, what can I do to solve the fail?

I attached  the testsuite.log

Thanks again.
--
Francesc Ortiz


Hi Francesc,


These are listed as known failures on the page. You are safe to 
continue. :-)


- Doug

-- 
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

Re: [lfs-support] tclInt.h error in Expect-5.45.4

[Douglas R. Reno]

On 3/25/19 9:19 PM, Chris6 wrote:
Received this error message when running ./config for Expect-5.45.4 in 
LFS Stable 8.4:


   "checking for Tcl private include files... configure: error: 
Cannot find private header tclInt.h in /mnt/lfs/sources/tcl8.6.9"


I looked in the tcl8.6.9 file and the only reference to tclInt.h is in 
the second line of the file but it is in the initial comment section.  
How can I get the tclInt.h error fixed.  Thanks



Sent with ProtonMail  Secure Email.



Did you run "make install-private-headers" when building Tcl?
-- 
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

Re: [lfs-support] coreutis-8.30 multibyte problem

[Douglas R. Reno]

On 3/20/19 5:55 PM, José Carlos Carrión Plaza wrote:

El 19 mar 2019, a las 19:27, José Carlos Carrión Plaza  escribió:



El 19 mar 2019, a las 17:14, Bruce Dubbs  escribió:

On 3/19/19 11:05 AM, José Carlos Carrión Plaza wrote:

Enviado desde mi iPhone

El 19 mar 2019, a las 14:46, Pierre Labastie  escribió:

On 19/03/2019 13:43, José Carlos Carrión Plaza wrote:
Hello co-listers:

I’ve installed LFS 8.4. I’ve built several BLFS packages without problem and 
X-Window is running (with motif-2.3.8). At the booting of MariadB I’ve detected 
the following problem:

-bash-5.0# echo foobar | LANG=POSIX cut -c4
b
-bash-5.0# echo foobar | LANG=en_US.iso8859-1 cut -c4
b
-bash-5.0# echo foobar | LAN=en_US.utf8 cut -c4

Seems "G" is missing at the end of "LAN".


-bash-5.0#

I’m almost sure I’ve properly applied the coreutils-8.30-i18n-1.patch at LFS 
chapter 6. Just in case, I’ve rebuilt coreutils-8.30 applying patch with a 
clean environment:

-bash-5.0$ env -i TERM="$TERM" HOME=“$HOME" 
PATH="/bin:/sbin:/usr/bin:/usr/sbin" LC_ALL=POSIX /bin/bash
bash-5.0$

I’ve built coreutils (with patch, indeed) as LFS book reads without problem and 
all tests passed, but test-getlogin as expected.
The problem with cut command remains.

What (and where) I’ve made the mistake? Is it safe to continue?

Of course. It’s a typo.
-bash-5.0# echo foobar | LANG=en_US.utf8 cut -c4
gives no output

It does for me:

$ echo foobar | LANG=en_US.utf8 cut -c4
b

— Bruce


Maybe the architecture? I’m on i686…


Answering myself...

On x86_64:

$ echo foobar | LANG=en_US.utf8 cut -c4
b

With the permission of masters, I’m going to regard on coreutils patch looking 
for an architecture bug.

Regards.

J. C.



Chiming in here,


I just ran a test on my i686 box while waiting for a build to complete.


renodr [ /sources ]$ echo foobar | LANG=en_US.UTF-8 cut -c4


renodr [ /sources ]$

I'm not getting any output either.

It's running 20190101-systemd

--
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

Re: [lfs-support] Potential damage of $LFS/tools setting in section 4.2 and 4.3 of LFS book.

[Douglas R. Reno]

On Tue, Mar 19, 2019, 11:12 AM Bruce Dubbs  wrote:

> On 3/19/19 2:25 AM, niuneilneo wrote:
> > As described in the title, the $LFS/tools setting could be harmful for
> > the current linux distros. Because there already exists /tools folder in
> > current Debian/Ubuntu distros, and it is not possible to correctly set
> > the symlink between the $LFS/tools and /tools. Even if I brutally delete
> > the /tools folder, and set the symlink, the host system will complain
> > that "Too many levels of symbolic links" for simple commands like tar,
> > and all LFS operations following will not be able to execute.
> >
> > I wonder this problem is caused by the dead cycle between the /tools and
> > $LFS/tools. So I suggest totally remove this setting or warn user not to
> > set this variable when some host distros default  have /tools in their
> > root folder.
>
> We need to verify this.  What specific version of Debian has /tools?
> LFS has used /tools for almost 20 years.  I think it is unlikely that
> Debian started to use it.
>

Debian Testing didn't have it last time I tried.

OP, what version of Debian and/or Ubuntu did you use to find this? We need
to verify for ourselves.

The only purpose I can think of for Debian to use /tools is to hide a
recovery system that can be used in the event of a failed update.
-- 
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

Re: [lfs-support] LFS 8.4 - 6.54. Procps-ng-3.3.15 - make check Error

[Douglas R. Reno]

On 2019-03-04 22:47, Darren Wu wrote:

Hello.

(Host system: "Linux HP-Arch 4.20.13-arch1-1-ARCH #1 SMP PREEMPT Wed
Feb 27 19:10:28 UTC 2019 x86_64 GNU/Linux")

(Complete log is in attached file.)

I get the following when running "make check". Is it critical or OK to 
ignore?


Regards,
Darren Wu

-
[...]

=== ps tests ===

Schedule of variations:
unix

Running target unix
Using /tools/share/dejagnu/baseboards/unix.exp as board description
file for target.
Using /tools/share/dejagnu/config/unix.exp as generic interface file 
for target.

Using ./config/unix.exp as tool-and-target-specific interface file.
Running ./ps.test/ps_output.exp ...
FAIL: ps with output flag %cpu,pcpu,%mem,pmem
FAIL: ps with output flag 
blocked,sig_block,sigmask,caught,sigcatch,sig_catch

Running ./ps.test/ps_personality.exp ...
Running ./ps.test/ps_sched_batch.exp ...

=== ps Summary ===

# of expected passes8
# of unexpected failures  2
WARNING: Couldn't find tool init file
Test run by root on Tue Mar  5 04:01:36 2019
Native configuration is x86_64-pc-linux-gnu

[...]

make[3]: *** [Makefile:518: check-DEJAGNU] Error 1
make[3]: Leaving directory '/sources/procps-ng-3.3.15/testsuite'
make[2]: *** [Makefile:590: check-am] Error 2
make[2]: Leaving directory '/sources/procps-ng-3.3.15/testsuite'
make[1]: *** [Makefile:1837: check-recursive] Error 1
make[1]: Leaving directory '/sources/procps-ng-3.3.15'
make: *** [Makefile:2293: check] Error 2
-


While I don't have these errors on a fresh 8.4 build, I think it should 
be safe to continue.


On that note, I'd like someone else to chime in here as well, because 
there is a chance that I could be incorrect.

--
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

Re: [lfs-support] Ninja patch discarded ?

[Douglas R. Reno]

On 2/14/19 6:38 PM, Ken Moffat wrote:

In r11506, amongst the several upgrades including glibc was an
upgrade to ninja-1.9.0.  As part of that, the LFS-specific patch to
restrict the number of jobs was discarded.

I don't recall seeing this mentioned, so I wonder why ?  I've
certainly mentioned it on the qtwebengine page, and it makes
measuring for 4 cores a lot easier on a machine with more.

ĸen


I was about to ask this myself - what happened with this?

For some of my systems, this will lead to fatal consequences if I don't 
find a way to *safely* turn off CPU cores without the risk of killing 
the system in the process. This patch made it a lot easier.


--
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

Re: [lfs-support] some observations about LFS 8.3 + jhalfs

[Douglas R. Reno]

On 1/1/19 6:09 AM, Thomas Seeling wrote:

Hallo and a happy new year,

On all occasions the makefile stopped after 146-revisedchroot with 
the sudo

the bug. Can you send me the "configuration" file you have used?


I'll try to recreate. I started fresh yesterday, and now the Makefile 
contains CHROOT2. I hope I can remember which options I used previously.



Apart from that I'm quite happy with jhalfs.


found another one: ncurses from LFS is built without libtinfo, so I 
can't run BLFS first stage make in /blfs_root - it's bailing out on 
not being able to load libtinfo.so for mconf.


I modified the configure options for ch. 6 ncurses and added
    --with-termlib=tinfo    \
This works and I could invoke make for setting BLFS options.

Any idea why I cannot use passwd in the chroot environment? I tried to 
set the root password before rebooting, and passwd simply does not ask 
for keyboard input.
I worked around this by copying the password line for root from 
/etc/shadow to /mnt/lfs/etc/shadow.


Can you check if you have virtual filesystems mounted? All five of the 
primary (/dev, /dev/pts, /proc, /sys, /run) are needed to get 'passwd' 
to function correctly in chroot. I've run into that before.

Tschau...Thomas

--
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

Re: [lfs-support] minor typo in book 8.3 chapter 7.8

[Douglas R. Reno]

On 12/31/18 12:05 PM, Rick Shelton wrote:

7.8. Creating the /etc/inputrc File
"It works by tranlating keyboard inputs into specific actions."

It is also present in the development version of the book, Version SVN-20181227.

~rick


Hi Rick,


Just fixed at r11496. Thank you!

--
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

Re: [lfs-support] Help: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0, 0)

[Douglas R. Reno]

On 11/29/18 3:37 PM, JD wrote:



On 11/29/2018 02:18 PM, Bruce Dubbs wrote:

On 11/29/2018 02:49 PM, JD wrote:

1. If the kernel does not have the required driver,
how did LFS end up on the drive?
2. Just exactly what driver are you referring to?
 "Driver" is a generic term which is used to to refer to different
interfaces in the kernel.
YOU claim that  to say "re-install" is a strange piece of advice.
I, actually, everyone, would love to hear from you just exactly which
driver the OP is missing.


1. LFS got on to the hard drive using the host's drivers.

2. The specific driver needed depends on the HW.  Try rebuilding the 
kernel with make defconfig; make


  -- Bruce


Hey Bruce,
you are saying that LFS varies and depends on the hardware??
Exactly which hardware?
The disk IO layer drivers are dependent on type of disk HW interface 
at the lowest level.
Above that an abstraction layer is used, and it is possible (if 
necessary) to build yet

another abstraction layer above that.
The FS's LFS layer is built on top of the "block io" layer, as the 
file system works

with BLOCKS.
So, please explain what type of hardware is  LFS dependent on?



Would you happen to be here for inquiries on Large File Support (LFS), 
not Linux From Scratch? The two things are entirely separate, and "Large 
File Support" was coined many years after the Linux From Scratch 
distribution was started.


--
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

Re: [lfs-support] md5sum for libcap

[Douglas R. Reno]

On 11/22/18 10:49 AM, Bruce Dubbs wrote:

On 11/22/2018 08:21 AM, Ronald P Guilmet wrote:

"I just downloaded the wget-list and md5sum files

the md5sum test fails at libcap.

This is the downloaded md5sum file:
b839e5d46c2ad33fc8aa2ceb5f77  libcap-2.26.tar.xz

If I run:    md5sum libcap-2.26.tar.xz
I get:
968ac4d42a1a71754313527be2ab5df3  libcap-2.26.tar.xz"

I downloaded the https://ftp.gnu.org/gnu/wget/wget-1.19.5.tar.gz. I 
checked the md5, and it matches. I'm not sure if you have to checksum 
every file. The main source is good.


These are the correct values:

b839e5d46c2ad33fc8aa2ceb5f77  libcap-2.25.tar.xz
968ac4d42a1a71754313527be2ab5df3  libcap-2.26.tar.xz

  -- Bruce



Did you grab the new stealth-update?

--
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

Re: [lfs-support] md5sum for libcap

[Douglas R. Reno]

On Wed, Nov 21, 2018, 11:02 AM Morten Håkestad  Hi,
>
> I just downloaded the wget-list and md5sum files
>
> the md5sum test fails at libcap.
>
> This is the downloaded md5sum file:
> b839e5d46c2ad33fc8aa2ceb5f77  libcap-2.26.tar.xz
>
> If I run:md5sum libcap-2.26.tar.xz
> I get:
> 968ac4d42a1a71754313527be2ab5df3  libcap-2.26.tar.xz
>
> Regards
> Mort1
> --
> 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


That fix is in my sandbox. It'll be in my next commit, probably two hours
out.

>
>
-- 
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

Re: [lfs-support] Announcing Basic BLFS (beta)

[Douglas R. Reno]

On Wed, Sep 26, 2018 at 2:44 PM Pierre Labastie 
wrote:

> On 9/26/18 8:05 PM, Hazel Russman wrote:
> > On Wed, 26 Sep 2018 14:47:23 +0100
> > Richard Melville <6tric...@gmail.com> wrote:
> >
> >> On 26 September 2018 at 13:59, Xi Ruoyao 
> wrote:
> >>
> >>> On 2018-09-26 12:06 +0100, Hazel Russman wrote:
>  On Tue, 25 Sep 2018 22:25:33 +0100
>  Ken Moffat  wrote:
> > Second question: can you https:// to google ?
>  Yes. And to Linux Questions. It's only the LFS site that's causing
>  problems.
> >>>
> >>> Whoa!  www.linuxfromscratch.org does not have HTTPS support now.
> >>
> >>
> >> It would appear so; I just checked.
> >>
> >> Richard
> > If you have a web page that asks for registration passwords, then surely
> it ought to use encryption.
> >
>
> Actually, the registration web page is explicit about this:
> "You may enter a privacy password below. This provides only mild security,
> but
> should prevent others from messing with your subscription. Do not use a
> valuable password as it will occasionally be emailed back to you in
> cleartext."
>
>
> Pierre
>
>
Does Trac have a notice like this?
-- 
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

Re: [lfs-support] LFS 8.3 - Chap 6 - Binutils 2.31.1 test error

[Douglas R. Reno]

On Mon, Sep 10, 2018, 2:19 AM José Carlos Carrión Plaza  wrote:

> Hi co-listers:
>
> First of all, thanks for your great work on LFS-8.3.
>
> I'm building LFS-8.3 on an:
>
> IBM eServer 206m -[8485E1G]-/M11ip/M11ix, BIOS IBM BIOS Version
> 1.45-[PAE145AUS-1.45]- 01/23/2009
>
> with a
>
>   Intel(R) Pentium(R) 4 CPU 3.00GHz (family: 0xf, model: 0x4, stepping:
> 0x9)
>
> and S.O.: Linux From Scratch 8.1
>
> When I "make check" binutils-2.31.1, I've got only one unexpected error,
> but it seems not in "debug_msg.sh" like the book reads. It appears like:
>
> ))
>  === ld tests ===
>
> Schedule of variations:
>  unix
>
> Running target unix
> Using /tools/share/dejagnu/baseboards/unix.exp as board description file
> for target.
> Using /tools/share/dejagnu/config/unix.exp as generic interface file for
> target.
> Using /sources/binutils-2.31.1/ld/testsuite/config/default.exp as
> tool-and-target-specific interface file.
> Running /sources/binutils-2.31.1/ld/testsuite/ld-aarch64/aarch64-elf.exp
> ...
> [...]
> Running /sources/binutils-2.31.1/ld/testsuite/ld-i386/export-class.exp ...
> Running /sources/binutils-2.31.1/ld/testsuite/ld-i386/i386.exp ...
> FAIL: Build ifunc-1a with -z ibtplt
> Running /sources/binutils-2.31.1/ld/testsuite/ld-i386/no-plt.exp ...
> Running /sources/binutils-2.31.1/ld/testsuite/ld-i386/tls.exp ...
> [...]
>  === ld Summary ===
>
> # of expected passes1843
> # of unexpected failures1
> # of expected failures4
> # of untested testcases1
> # of unsupported tests20
> /sources/binutils-2.31.1/build/ld/ld-new 2.31.1
> 
>
> May I continue with the Chapter 6 or I have to back on Chapter 5?
>
> Thanks in advance.
>
> Regards
>
> --
> José Carlos Carrión Plaza
> Universidad de Murcia
>
> --
> 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


Keep on going, that's expected.

>
>
-- 
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

Re: [lfs-support] Info on package bzip2-1.0.6 in LFS 8.2

[Douglas R. Reno]

On Thu, Sep 6, 2018 at 10:30 AM Hazel Russman 
wrote:

> On Thu, 6 Sep 2018 16:11:22 +0200 (CEST)
> Terence Waterhouse  wrote:
>
> > Dear sir,
> >
> >
> >
> > Although I have been using exclusively Linux for many many years it is
> only a few days ago I decided to buils my own system using LFS v.8.2. I am
> not quite certain which list this post should actually be on, but I
> subscribed to this list because I shall probably need it later... I do not
> generally post unnecessary questions, and indeed, I don't post questions at
> all. So here goes :
> >
> >
> >
> > Building LFS 8.2 went smoothly until section 5.18 bzip2-1.0.6. When I
> tried to untar the package I got the following output:
> >
> >
> >
> > tar: This does not look like a tar archive gzip:
> >
> > stdin: not in gzip format
> >
> > tar: Child returned status 1
> >
> > tar: Error is not recoverable: exiting now
> >
> >
> >
> > In fact it is apparently a html file according to 'file' output with a
> tar.gz extension. I first downloaded the original packages with the
> wget-list file, then, meeting this problem, ran wget with the specific file
> name. No succes. I tried the site http//:www.bzip.org and could find no
> trace of the sources. A visit to the site will tell you why.
> >
> >
> >
> > I tried all the usual tricks to unpack it with absolutely no succes. To
> cut things short I spent 2 days searching the web to no avail then sent off
> a desperate search for "what happened to bzip2?" This search produced the
> following link :
> >
> >
> >
> > https://lwn.net/Articles/762264/
> >
> >
> >
> > I also found on this page the following link to the source files of
> bzip2 and it is the only link I have been able to find:
> >
> >
> >
> >
> https://web.archive.org/web/2014073512/http://www.bzip.org/1.0.6/bzip2-1.0.6.tar.gz
> >
> >
> >
> > Download
> >
> > replace the package obtained from wget-list
> >
> > untar
> >
> > and carry on as usual.
> >
> >
> >
> > I might attract your attention to the fact that the post at lwn.net is
> dated August 9th 2018 and so is recent.
> >
> >
> >
> > As LFS uses bzip2 extensively it seemed to me that this information
> might be of some use. I can only hope that the newly downloaded version
> works. . .
> >
> >
> >
> > Many many thanks for the great work, I will let you know if I run into
> any difficulties with the package.
> >
> > I leave it to your judgement as to how to address this potentially
> important issue.
> >
> >
> >
> > Yours sincerely
> >
> >
> >
> > Terence Waterhouse
> >
> I just checked. It's not on Anduin. There's a link but it leads nowhere.
> That's strange because I had no problem finding it in 8.3-rc2.
>
> --
> Hazel Russman
>
>
Guys/Gals,

Check out this link -
http://ftp.gnome.org/pub/gnome/teams/releng/tarballs-needing-help/bzip2/bzip2-1.0.6.tar.gz

GNOME has it as well :-)
-- 
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

Re: [lfs-support] Booting LFS with systemd

[Douglas R. Reno]

On Thu, Jul 19, 2018 at 8:47 AM Frans de Boer  wrote:

> On 06-07-18 16:44, Bruce Dubbs wrote:
> > On 07/06/2018 01:20 AM, Frans de Boer wrote:
> >> On 07/05/2018 11:56 PM, Bruce Dubbs wrote:
> >>> On 07/05/2018 02:48 PM, Frans de Boer wrote:
>  On 06/30/2018 01:29 PM, Hazel Russman wrote:
> > On Fri, 29 Jun 2018 01:25:29 -0400
> > Michael Shell  wrote:
> >
> >> On Thu, 28 Jun 2018 16:06:00 +0800
> >> Xi Ruoyao  wrote:
> >>
> >>> Now I only use "initrd" directive to update CPU microcode and fix
> >>> the
> >>> buggy ACPI DSDT of my laptop (another sad story).
> >>
> >> .
> >>
> >> And as there now seems to be several people who suffer with the
> >> ACPI DSDT driver bug, you guys should make sure upstream is aware
> >> of the problem, if they aren't already.
> >>
> > ...
> >>Cheers,
> >>
> >>Mike
> >>
> >> --
> > I did a git bisect on my system, but I couldn't make much sense of
> > the result. The commit it finally settled on didn't seem to have
> > anything to with acpi.
> >
> > [quote]
> > Bisecting: 2 revisions left to test after this (roughly 1 step)
> > [9af9b94068fb1ea3206a700fc222075966fbef14] x86/cpu/AMD: Handle SME
> > reduction in physical address size
> >
> > Bisecting: 0 revisions left to test after this (roughly 1 step)
> > [33c2b803edd13487518a2c7d5002d84d7e9c878f] x86/mm: Remove
> > phys_to_virt() usage in ioremap()
> >
> > Bisecting: 0 revisions left to test after this (roughly 0 steps)
> > [7744ccdbc16f0ac4adae21b3678af93775b3a386] x86/mm: Add Secure
> > Memory Encryption (SME) support
> > [unquote]
> >
> > I sent the result to the kernel acpi development list but never got
> > an answer. If someone else on this list wants to try, I can send
> > him my complete bisect logs.
> >
> > --
> > Hazel
>  This quite frustrating. After recompiling, following the book to the
>  letter, I still get a frozen LFS system.
>  One thing I do note however is that the freezing always occurs after
>  systemd has detected that it is on a virtual machine. A number of
>  error messages is send, but due to ratelimiting I can't see them
>  because they are suppressed.
> 
>  I had even rebuild everything with systemd-232, and that worked as
>  before. But after 232, things started to behave strange. Now way to
>  debug systemd, whatever I do
> 
>  Help?
> >>>
> >>> I don't mean to be pedantic, but I really don't think you would run
> >>> into these types of problems using System V.  Why not try that?
> >>>
> >>>   -- Bruce
> >>>
> >> Hi Bruce,
> >> With System V there is - of course - no problem. The thing is that
> >> systemd - if it runs well - is somewhat easier to use because of the
> >> use of .service files.
> >
> > I'll have to disagree that service files are easier.  What I do agree
> > with is that they are more consistent among distros.  The boot scripts
> > for System V are really quite easy to read and, if needed, write.
> >
> >   I also noticed that some packages are only shipping
> >> .service(.in) files and have abandon the use of sysVinit files.
> >
> > Then they are abandoning those distros that do not use systemd such as
> > the BSDs and Devuan.  But those distros can easily add their own boot
> > scripts.  I'll note that all the BLFS packages that need boot scripts
> > have them,
> >
> >> Combined with the fact that most distributions have embraced systemd
> >> as their primary or only init system let me believe that we are stuck
> >> with this piece of ever growing mutation. And as LFS is a teaching
> >> ground, it should - however reluctant - incorporated this too.
> >
> > As a teaching tool, NOT using systemd is essential.  There is far too
> > much done by systemd in an opaque manner that System V demonstrates and,
> > if desired,implemented in custom ways.
> >
> >> Also, the goal is that someone fire-up their basic hardware with a LFS
> >> born OS, but for testing or use in VM's development is nowadays mostly
> >> within the VM realm.
> >
> > When I teach LFS in class, I always have the students use real HW, There
> > are too many things that VMs hide,
> >
> >-- Bruce
> >
> Bruce,
>
> I agree that VM's hide some issues and I do understand you position
> about systemd. Although I disagree to some level. After all, should we
> learn people how to crackup a (very) old car or the new generally
> available way using some sort of key. Just focusing only on System V is
> precisely what industries mean when they talk about "they are not being
> taught the modern technics.".
> Remember the days past, the discussion of having systemd included in the
> LFS book? Eventual it was included. Now the next "new" thing maybe?
>
> Why not using VM's when one can continue developing without having to
> reboot into an incomplete system environment.

Re: [lfs-support] compile 4.17.7 32 bit

[Douglas R. Reno]

On Tue, Jul 17, 2018, 10:40 PM Ken Moffat  wrote:

> On Wed, Jul 18, 2018 at 04:31:47AM +0100, Ken Moffat wrote:
> > > I used a Core2Duo for about 6 years.  It is a native x86_64 system,
> but can
> > > run 32-bit kernels and thus 32-bit systems.
> > >
> > No idea what the bug on x86_64 is, I'm behind on reading lkml, but I
> > think it is likely that 'i386' might mean 'on x86 machines running
> > as 32-bit'.
> >
> > And apparently there is a one patch revision for 4.17.8 due on
> > Thursday, no idea if it might help or not:
> >
> > https://lkml.org/lkml/2018/7/17/443
> >
> >  and
> >
> > https://lkml.org/lkml/2018/7/17/505
> >
> It *does* affect all 32-bit x86 :
>
> https://lkml.org/lkml/2018/7/16/809
>
> > Qemu test results:
> >   total: 171 pass: 159 fail: 12
> > Failed tests:
> >   i386:Broadwell:q35:defconfig:smp:rootfs
> >   i386:Skylake-Client:q35:defconfig:smp:rootfs
> >   i386:SandyBridge:q35:defconfig:smp:rootfs
> >   i386:Haswell:pc:defconfig:smp:rootfs
> >   i386:Nehalem:q35:defconfig:smp:rootfs
> >   i386:phenom:pc:defconfig:smp:rootfs
> >   i386:Opteron_G5:q35:defconfig:smp:initrd
> >   i386:Westmere:q35:defconfig:smp:initrd
> >   i386:core2duo:q35:defconfig:nosmp:rootfs
> >   i386:Conroe:pc:defconfig:nosmp:rootfs
> >   i386:Opteron_G1:pc:defconfig:nosmp:initrd
> >   i386:n270:q35:defconfig:nosmp:rootfs
> >
> > All 32-bit i386 boot tests crash.
>
> And the reply was that the known fix is not yet in Linus's tree, so
> it can't be applied to stable until Linus commits it.
>
> So the one patch in 4.17.8-rc won't help 32-bit.
>
> ĸen
> --
>   Keyboard not found, Press F1 to continue
>

Guys,

Heads up, this is affecting sporadic x86_64 PCs too. A sizable chunk of my
64bit machines refuse to boot with 4.17.7 and even a few 32bit ones with
4.17.6. There is obviously something wrong here that needs fixing.

>
-- 
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

Re: [lfs-support] Booting LFS with systemd

[Douglas R. Reno]

On Thu, Jul 5, 2018, 4:56 PM Douglas R. Reno  wrote:

>
>
> On Thu, Jul 5, 2018 at 2:54 PM Frans de Boer  wrote:
>
>> On 06/30/2018 01:29 PM, Hazel Russman wrote:
>> > On Fri, 29 Jun 2018 01:25:29 -0400
>> > Michael Shell  wrote:
>> >
>> >> On Thu, 28 Jun 2018 16:06:00 +0800
>> >> Xi Ruoyao  wrote:
>> >>
>> >>> Now I only use "initrd" directive to update CPU microcode and fix the
>> >>> buggy ACPI DSDT of my laptop (another sad story).
>> >>
>> >> .
>> >>
>> >> And as there now seems to be several people who suffer with the
>> >> ACPI DSDT driver bug, you guys should make sure upstream is aware
>> >> of the problem, if they aren't already.
>> >>
>> > ...
>> >>Cheers,
>> >>
>> >>Mike
>> >>
>> >> --
>> > I did a git bisect on my system, but I couldn't make much sense of the
>> result. The commit it finally settled on didn't seem to have anything to
>> with acpi.
>> >
>> > [quote]
>> > Bisecting: 2 revisions left to test after this (roughly 1 step)
>> > [9af9b94068fb1ea3206a700fc222075966fbef14] x86/cpu/AMD: Handle SME
>> reduction in physical address size
>> >
>> > Bisecting: 0 revisions left to test after this (roughly 1 step)
>> > [33c2b803edd13487518a2c7d5002d84d7e9c878f] x86/mm: Remove
>> phys_to_virt() usage in ioremap()
>> >
>> > Bisecting: 0 revisions left to test after this (roughly 0 steps)
>> > [7744ccdbc16f0ac4adae21b3678af93775b3a386] x86/mm: Add Secure Memory
>> Encryption (SME) support
>> > [unquote]
>> >
>> > I sent the result to the kernel acpi development list but never got an
>> answer. If someone else on this list wants to try, I can send him my
>> complete bisect logs.
>> >
>> > --
>> > Hazel
>> This quite frustrating. After recompiling, following the book to the
>> letter, I still get a frozen LFS system.
>> One thing I do note however is that the freezing always occurs after
>> systemd has detected that it is on a virtual machine. A number of error
>> messages is send, but due to ratelimiting I can't see them because they
>> are suppressed.
>>
>> I had even rebuild everything with systemd-232, and that worked as
>> before. But after 232, things started to behave strange. Now way to
>> debug systemd, whatever I do
>>
>> Help?
>> Frans.
>> --
>> 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
>
>
> Hi,
>
> I see you're using Virtualbox. systemd has special instructions that have
> to do with running inside of hypervisors, and VirtualBox is one of them.
>
> I have a Windows machine here with Virtualbox installed. I'll give it a
> shot, I've been looking for an excuse to do it anyway.
>

Or rather, QEMU. Sorry about that.

It uses the same core, and the hypervisor comment still applies. Disregard
the above.

>
-- 
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

Re: [lfs-support] Booting LFS with systemd

[Douglas R. Reno]

On Thu, Jul 5, 2018 at 2:54 PM Frans de Boer  wrote:

> On 06/30/2018 01:29 PM, Hazel Russman wrote:
> > On Fri, 29 Jun 2018 01:25:29 -0400
> > Michael Shell  wrote:
> >
> >> On Thu, 28 Jun 2018 16:06:00 +0800
> >> Xi Ruoyao  wrote:
> >>
> >>> Now I only use "initrd" directive to update CPU microcode and fix the
> >>> buggy ACPI DSDT of my laptop (another sad story).
> >>
> >> .
> >>
> >> And as there now seems to be several people who suffer with the
> >> ACPI DSDT driver bug, you guys should make sure upstream is aware
> >> of the problem, if they aren't already.
> >>
> > ...
> >>Cheers,
> >>
> >>Mike
> >>
> >> --
> > I did a git bisect on my system, but I couldn't make much sense of the
> result. The commit it finally settled on didn't seem to have anything to
> with acpi.
> >
> > [quote]
> > Bisecting: 2 revisions left to test after this (roughly 1 step)
> > [9af9b94068fb1ea3206a700fc222075966fbef14] x86/cpu/AMD: Handle SME
> reduction in physical address size
> >
> > Bisecting: 0 revisions left to test after this (roughly 1 step)
> > [33c2b803edd13487518a2c7d5002d84d7e9c878f] x86/mm: Remove phys_to_virt()
> usage in ioremap()
> >
> > Bisecting: 0 revisions left to test after this (roughly 0 steps)
> > [7744ccdbc16f0ac4adae21b3678af93775b3a386] x86/mm: Add Secure Memory
> Encryption (SME) support
> > [unquote]
> >
> > I sent the result to the kernel acpi development list but never got an
> answer. If someone else on this list wants to try, I can send him my
> complete bisect logs.
> >
> > --
> > Hazel
> This quite frustrating. After recompiling, following the book to the
> letter, I still get a frozen LFS system.
> One thing I do note however is that the freezing always occurs after
> systemd has detected that it is on a virtual machine. A number of error
> messages is send, but due to ratelimiting I can't see them because they
> are suppressed.
>
> I had even rebuild everything with systemd-232, and that worked as
> before. But after 232, things started to behave strange. Now way to
> debug systemd, whatever I do
>
> Help?
> Frans.
> --
> 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


Hi,

I see you're using Virtualbox. systemd has special instructions that have
to do with running inside of hypervisors, and VirtualBox is one of them.

I have a Windows machine here with Virtualbox installed. I'll give it a
shot, I've been looking for an excuse to do it anyway.
-- 
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

Re: [lfs-support] Chapter 6 glibc 'make check' freezes. - LFS 8.2

[Douglas R. Reno]

On Wed, Jun 27, 2018 at 7:08 PM Ken Moffat  wrote:

> On Wed, Jun 27, 2018 at 06:19:25PM -0500, Douglas R. Reno wrote:
> > Hi Ken,
> >
> > I still have the build directory around (I'm actually going to tar it up
> > for diagnosis), but I'm going to continue and see what I can make of it.
> >
> > I'd rather run these with gdb so I can set breakpoints and find out where
> > the errors with nptl are resulting at, so I'm going to tar it up and
> > continue building.
> >
> > I got a lot of random error codes like 124, 127, 137, etc. from the
> tests.
>
> A quick gurgle suggests 124 might be timed out.
>
> 127 is common in BLFS test failures, program not found on $PATH.
>
> Gurgle also suggests 137 means the program got SIGKILL.
>
> ĸen
> --
>   Keyboard not found, Press F1 to continue
> --
> 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


To put a cherry on top of the cake, I'm having issues with syntax warnings
out of Perl. Apparently the REGEX structure changed in 5.28, and several
packages don't like it. It'll be fatal in 5.32, but I can understand if
it's unexpected behavior as the result of a deprecated feature. I'll look
into it more as I'm going along here.
-- 
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

Re: [lfs-support] Chapter 6 glibc 'make check' freezes. - LFS 8.2

[Douglas R. Reno]

On Wed, Jun 27, 2018 at 5:58 PM Ken Moffat  wrote:

> On Wed, Jun 27, 2018 at 04:45:48PM -0500, Douglas R. Reno wrote:
> > On Wed, Jun 27, 2018 at 4:43 PM Ken Moffat 
> wrote:
> > >
> > > The 8.3 release is months away, by which time anybody still here
> > > will have forgotten about this.  If there is a problem in the book
> > > (possible, at the moment x86_64 is getting very little testing, and
> > > i686 much less than that), the svn book is what needs to be tested.
> > >
> > I can vouch for SVN having some issues, check out my glibc test results
> > here with SVN-20180625:
> >
> > http://linuxfromscratch.org/~renodr/glibc-test-fails.txt
> >
> > My results were (on a Xeon-based KVM platform):
> >
> > Summary of test results:
> > 127 FAIL
> >5584 PASS
> >  29 UNSUPPORTED
> >  16 XFAIL
> >   2 XPASS
> > make[1]: *** [Makefile:304: tests] Error 1
> > make[1]: Leaving directory '/sources/glibc-2.27'
> > make: *** [Makefile:9: check] Error 2
> >
> > I'm refusing to move on until I find out what's going on here. 127
> failures
> > is a little too high for my liking.
>
> My own results from 20180615 (using config.fsf in gmp and
> CFLAGS,CXXFLAGS of -O2 -march=native on everything that didn't
> ignore them) were
>
> UNSUPPORTED: elf/tst-audit10
> UNSUPPORTED: elf/tst-avx512
> XPASS: elf/tst-protected1a
> XPASS: elf/tst-protected1b
> UNSUPPORTED: math/test-double-libmvec-alias-avx512
> UNSUPPORTED: math/test-double-libmvec-alias-avx512-main
> UNSUPPORTED: math/test-double-libmvec-sincos-avx512
> UNSUPPORTED: math/test-float-libmvec-alias-avx512
> UNSUPPORTED: math/test-float-libmvec-alias-avx512-main
> UNSUPPORTED: math/test-float-libmvec-sincosf-avx512
> UNSUPPORTED: misc/tst-pkey
> FAIL: misc/tst-preadvwritev2
> FAIL: misc/tst-preadvwritev64v2
> UNSUPPORTED: misc/tst-ttyname
> UNSUPPORTED: nptl/test-cond-printers
> UNSUPPORTED: nptl/test-condattr-printers
> UNSUPPORTED: nptl/test-mutex-printers
> UNSUPPORTED: nptl/test-mutexattr-printers
> UNSUPPORTED: nptl/test-rwlock-printers
> UNSUPPORTED: nptl/test-rwlockattr-printers
> UNSUPPORTED: resolv/tst-resolv-res_init
> UNSUPPORTED: resolv/tst-resolv-res_init-thread
> UNSUPPORTED: resolv/tst-resolv-threads
> UNSUPPORTED: sunrpc/tst-svc_register
> Summary of test results:
>   2 FAIL
>5718 PASS
>  20 UNSUPPORTED
>  16 XFAIL
>   2 XPASS
>
> Looking at your results:
>
> 1. We agree on the XPASS.
> 2. You have a lot more unsupported in math/, perhaps because you are
>in a KVM.
> 3. Your resolv/ and sunrpc/ tests apparently passed, again perhaps
>because of CPU differences
> 4. Your failures are almost all in nptl.
>
> I recall that trying to fathom why tests failed can be painful, but
> do you still have the build dir ?  If so, perhaps there is something
> in an nptl/ directory giving a bit more information.
>
> ĸen
> --
>   Keyboard not found, Press F1 to continue
> --
>
>
Hi Ken,

I still have the build directory around (I'm actually going to tar it up
for diagnosis), but I'm going to continue and see what I can make of it.

I'd rather run these with gdb so I can set breakpoints and find out where
the errors with nptl are resulting at, so I'm going to tar it up and
continue building.

I got a lot of random error codes like 124, 127, 137, etc. from the tests.
-- 
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

Re: [lfs-support] Chapter 6 glibc 'make check' freezes. - LFS 8.2

[Douglas R. Reno]

On Wed, Jun 27, 2018 at 4:43 PM Ken Moffat  wrote:

> On Wed, Jun 27, 2018 at 04:11:00PM -0500, rhubarbpie...@gmail.com wrote:
> > On 06/18/2018 02:09 PM, rhubarbpie...@gmail.com wrote:
> > >
> > > I'm attempting to compile LFS 8.2 on a 32-bit machine and 'make check'
> > > in glibc of Chapter 6 freezes at the following output:
> > >
> > >../scripts/evaluate-test.sh conform/symlist-stdlibs-XOPEN2K8 $?
> false
> > > false >
> > > /sources/glibc-2.27/build/conform/symlist-stdlibs-XOPEN2K8.test-result
> > >readelf: Warning: unable to apply unsupported reloc type 32 to
> > > section .debug_info
> > >
> > > I'm running 8.2 on a 64-bit machine but haven't done so with 32-bit
> > > architecture.  I omitted the following from binutils and gcc (pass 1)
> > > respectively:
> > >
> > > case $(uname -m) in x86_64) mkdir -v /tools/lib && ln -sv lib
> > > /tools/lib64 ;; esac
> > >
>
> According to
> https://docs.oracle.com/cd/E19683-01/817-3677/chapter6-26/index.html
> the 32-bit x86 relocation types are 0 to 11.
>
> According to http://refspecs.linuxbase.org/elf/x86_64-abi-0.98.pdf
> (page number 69) 32 is R_X86_64_SIZE32 if on x86_64.
>
> I think something about your build assumes it is on x86_64.  Is the
> host system 32-bit or 64 ?  If you build 32-bit on a 64-bit system,
> running linux32 at the beginning might help (and also using the fsf
> config scripts for gmp).
>
> >
> > This I'll file as a mystery as I had no hits on this post and have no
> > further thoughts on my end.  I guess it's "possible" the problem is
> specific
> > to my box and LFS 8.2 as I believe I compiled 8.1 on this box without the
> > problem.  I'll attempt to compile LFS 8.3 to see if the problem recurs.
>
> The 8.3 release is months away, by which time anybody still here
> will have forgotten about this.  If there is a problem in the book
> (possible, at the moment x86_64 is getting very little testing, and
> i686 much less than that), the svn book is what needs to be tested.
>
> ĸen
> --
>   Keyboard not found, Press F1 to continue
> --
>
>
I can vouch for SVN having some issues, check out my glibc test results
here with SVN-20180625:

http://linuxfromscratch.org/~renodr/glibc-test-fails.txt

My results were (on a Xeon-based KVM platform):

Summary of test results:
127 FAIL
   5584 PASS
 29 UNSUPPORTED
 16 XFAIL
  2 XPASS
make[1]: *** [Makefile:304: tests] Error 1
make[1]: Leaving directory '/sources/glibc-2.27'
make: *** [Makefile:9: check] Error 2

I'm refusing to move on until I find out what's going on here. 127 failures
is a little too high for my liking.
-- 
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

Re: [lfs-support] LFS website is down？ Anyone meets this problem？

[Douglas R. Reno]

On Thu, May 10, 2018 at 8:48 AM, niuneilneo  wrote:

> I am unable to access all the website pages belonged to the *.
> linuxfromscratch.org
>   domain. My system time is Thu May 10 13:45:59 UTC 2018.
>
> Lei Niu
>
> --
> 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
>
>
I've been seeing this problem as well.

I get a ERR_CONNECTION_REFUSED out of my browser.
-- 
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

Re: [lfs-support] LFS-8.1 Chapter 6.20. GCC-7.2.0

[Douglas R. Reno]

On Wed, Jan 3, 2018 at 7:35 PM, Baho Utot  wrote:

> I can not figure this out.
>
> I have rebuilt the whole thing from beginning to end and I always get the
> following upon the test for this chapter.  All previous tests are good.
>
> I made a script to do the test which give me the command followed by the
> result then the line with Book: is what I am supposted to get.
>
>
> I simply can not figure out why I get the results I do.
>
> If any one has some insight please educate me on why the difference with
> the book.
>
>
> readelf -l a.out | grep ': /lib'
>
> [Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]
> Book: [Requesting program interpreter: /lib64/ld-linux-x86-64.so.2]
>
> grep -o '/usr/lib.*/crt[1in].*succeeded' dummy.log
>
> /usr/lib/../lib/crt1.o succeeded
> /usr/lib/../lib/crti.o succeeded
> /usr/lib/../lib/crtn.o succeeded
> Book: /usr/lib/gcc/x86_64-pc-linux-gnu/7.2.0/../../../../lib/crt1.o
> succeeded
> Book: /usr/lib/gcc/x86_64-pc-linux-gnu/7.2.0/../../../../lib/crti.o
> succeeded
> Book: /usr/lib/gcc/x86_64-pc-linux-gnu/7.2.0/../../../../lib/crtn.o
> succeeded
>
>
> grep -B4 '^ /usr/include' dummy.log
>
> #include <...> search starts here:
>  /usr/include
> Book: #include <...> search starts here:
> Book:  /usr/lib/gcc/x86_64-pc-linux-gnu/7.2.0/include
> Book:  /usr/local/include
> Book:  /usr/lib/gcc/x86_64-pc-linux-gnu/7.2.0/include-fixed
> Book:  /usr/include
>
> grep 'SEARCH.*/usr/lib' dummy.log |sed 's|; |\n|g'
>
> SEARCH_DIR("=/tools/x86_64-pc-linux-gnu/lib64")
> SEARCH_DIR("/usr/lib")
> SEARCH_DIR("/lib")
> SEARCH_DIR("=/tools/x86_64-pc-linux-gnu/lib");
> Book: SEARCH_DIR("/usr/x86_64-pc-linux-gnu/lib64")
> Book: SEARCH_DIR("/usr/local/lib64")
> Book: SEARCH_DIR("/lib64")
> Book: SEARCH_DIR("/usr/lib64")
> Book: SEARCH_DIR("/usr/x86_64-pc-linux-gnu/lib")
> Book: SEARCH_DIR("/usr/local/lib")
> Book: SEARCH_DIR("/lib")
> Book: SEARCH_DIR("/usr/lib");
>
>
>
> grep "/lib.*/libc.so.6 " dummy.log
>
> attempt to open /lib/libc.so.6 succeeded
> Book: attempt to open /lib/libc.so.6 succeeded
>
>
> grep found dummy.log
>
> found ld-linux-x86-64.so.2 at /lib/ld-linux-x86-64.so.2
> Book: found ld-linux-x86-64.so.2 at /lib/ld-linux-x86-64.so.2
>
> removed 'dummy.c'
> removed 'a.out'
> removed 'dummy.log'
>
>

The difference in the book is due to paths being different between
architectures. GCC is programmed for i686 predominantly, and the paths are
changed with symlinks like shown above for x86_64.
-- 
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

Re: [lfs-support] [blfs-support] LFS on Windows

[Douglas R. Reno]

On Mon, May 15, 2017 at 10:30 AM, Paul Rogers 
wrote:

> Not too long ago we had a question about installing LFS on/with Windows,
> but it'd be fair to say there was little to say about it.  I ran across
> this article today:
>
> https://arstechnica.com/information-technology/2017/
> 05/windows-server-will-add-the-linux-subsystem-join-the-insider-program/
>
> Not too much info there, but it does have some links.
>


I've been working on it a little bit recently. One of my friends gave me
remote access (RDP and Chrome Remote Desktop) to a Windows Server 2016 and
Windows 10 PC. I've run into some interesting issues with the standard
Ubuntu install, in particular because the syscalls are emulated, and it's
VERY slow... but it works (with a ton of modifications).

When I get a system completed, I'll take notes and spread the knowledge.

It's also worth noting that parallelization doesn't work, and because of
the emulation, the overhead is HUGE.If I run -j4, it actually slows it down
by a factor of four because it can only run one large process at a time.

For future reference, the system that I've been playing with this on has an
i7-7700k with 16GB of RAM (it's his gaming rig). The SBU value is over 15
minutes...

I've been using jhalfs on it, but I'm tempted to do a build manually and
record it so that we have a general idea of how long it takes.

Also, sudo barely works (I had to modify jhalfs to let me run as root), and
it's impossible to mount filesystems, even if you create a file for LFS and
mount that as an ext4 in /mnt/lfs instead. I also had to create a symlink
from /proc/self/mounts to /etc/mtab as well, as that did not come as
default.

I actually needed autoconf/automake/autogen because GCC wanted to try
compiling for a new architecture and requested it.

TL;DR - finished the temporary toolchain after 16 hours, and it's really
slow... but it's functional.

Douglas R. Reno
--LFS/BLFS systemd maintainer
-- 
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

Re: [lfs-support] the new Linux Subsystem in Win 10

[Douglas R. Reno]

On Apr 29, 2017 4:47 AM, "Simon Geard"  wrote:

On Sat, 2017-04-29 at 01:35 -0500, Rob wrote:
> Last year I heard that M$ was including a Ubuntu-based subsystem in
> its Windows 10 product. I wasn't sure this was actually going to work
> very well, but apparently it does.
> Can this be used to build LFS? I'm not sure it can because of the
> ext* file systems you would need, but i'm curious nonetheless.

Interesting question. From what I've read of it, the mechanism
basically involves having the Windows kernel expose an implementation
of the Linux syscall interfaces... so to userspace, it's just Linux
binaries talking to what they think is a Linux kernel.

That said, I don't know whether the emulation goes far enough to do an
LFS build... e.g. does it provide support for /sys or /proc or kernel
interfaces other than syscalls? It's designed to make life easier for
developers porting server apps between Windows and Linux, but such apps
don't generally need those interfaces - they just need glibc to work -
so the emulation may not be sufficient for everything.


/proc, /sys, and /dev are implemented. It actually boots Upstart when
executing the subsystem. I at least remember that much
-- 
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

Re: [lfs-support] the new Linux Subsystem in Win 10

[Douglas R. Reno]

On Sat, Apr 29, 2017 at 1:35 AM, Rob  wrote:

> Last year I heard that M$ was including a Ubuntu-based subsystem in its
> Windows 10 product. I wasn't sure this was actually going to work very
> well, but apparently it does.
> Can this be used to build LFS? I'm not sure it can because of the ext*
> file systems you would need, but i'm curious nonetheless.
>

I had the same idea, but didn't get around to it. Probably could at least
use it as a chroot system...
-- 
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

Re: [lfs-support] Completed, only /lib or /lib64

[Douglas R. Reno]

On Sat, Apr 22, 2017 at 2:49 PM, Frans de Boer  wrote:

> On 22-04-17 17:54, Bruce Dubbs wrote:
>
>> Frans de Boer wrote:
>>
>>> Dear Reader,
>>>
>>> The current instance of LFS-dev still requires the use of /lib64 (as a
>>> link to /lib).
>>>
>>
>> No it does not.  /lib64 is a directory, not a symlink.  It contains
>> exactly two files, both symbolic links:
>>
>> $ ls -l /lib64
>> total 0
>> lrwxrwxrwx 1 root root 27 Feb 13 19:28 ld-linux-x86-64.so.2 ->
>> ../lib/ld-linux-x86-64.so.2
>> lrwxrwxrwx 1 root root 27 Feb 13 19:28 ld-lsb-x86-64.so.3 ->
>> ../lib/ld-linux-x86-64.so.2
>>
>> If have made changes to eliminate the use of the /lib64
>>
>>> link. Also, all relevant hard-coded references to /lib64 in the used
>>> packages are replaced with /lib. The only place I did not touched sofar,
>>> where the manuals and documentation. Oh, I did this for both developments
>>> (vinit and systemd).
>>>
>>
>> When we released 8.0 we checked that nothing was installed in /usr/lib64
>> or, except for the above, nothing else in /lib64.
>>
>> You need to explain a little better what you see as the issue.
>>
>>   -- Bruce
>>
>>
>> Likewise, instead of using /lib I targeted the use of /lib64 without the
>>> use of a symbolic link /lib. That took some more time, but the part using
>>> only vinit is now ready and booting and more importantly, working.
>>> Systemd
>>> needs some tweaking, but given available time, that has to wait a little
>>> longer.
>>>
>>> By the way, to do it right, one needs changes in the toolchain (crucial)
>>> as well in the next stage.
>>>
>>> If interested, I can extract all additions and provide them to be
>>> included
>>> in some future development cycle.
>>> I also sure that some commands can be more integrated and/or refined, but
>>> that is a next step.
>>>
>>> Kind Regards,
>>> Frans.
>>>
>>
>> Ok, my mistake: lib64 contains some links, I found out how to eliminate
> the use of lib64 at all.
>
> The case of using lib64 instead of lib required some more work since many
> packages use hard-coded references to lib. Since the FHS does not mandate
> the use of lib - it's in fact optional if using lib64/32 - I tried to find
> a way to create a system without the use of lib, but instead use lib64 or
> lib32 only. In that way the system is aware again of its architecture
> instead of using the antiquated - but historical grown - lib directory.
> No worry, the architectural independent /var/lib is still there.
>
> --- Frans.
>
>

Frans,

We need /lib64 for binary compatibility for other distributions. Some of us
need that more than others. As a university student, I especially need it.
-- 
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

Re: [lfs-support] Why does the udevadm settle command drive my video card crazy?

[Douglas R. Reno]

On Wed, Feb 15, 2017 at 12:45 AM, Hazel Russman 
wrote:

> On Thu, 9 Feb 2017 17:31:36 +
> Hazel Russman  wrote:
>
> > I've just completed LFS on my laptop, a Samsung machine with Vaio
> > electronics. The video card is a Vaio Chrome 9.
> >
> > I already knew that this card has compatibility issues. I had
> > problems after installing NuTyX, because the NuTyX initrd tried to
> > set up a framebuffer console which the card objected to. It went
> > black, then cycled slowly through the other available solid colours
> > (white, red, green...) until I rebooted. Thierry Nutt advised me to
> > blacklist the fb module and rebuild the kernel so as to bypass the
> > initrd, and this solved the problem.
> >
> > I didn't expect the same kind of trouble with lfs, but I got
> > identical symptoms during the startup process. The kernel booted
> > successfully and the init scripts started to run; then while the udev
> > script was running, everything went black. I checked the logs
> > afterwards and they showed that the initialisation had in fact run to
> > completion. It was only the video output that had failed.
> >
> > I edited some additional echo messages into the script and
> > established that it was the "udevadm settle" command that caused the
> > video problem. And when I blacklisted the fb module, the problem
> > disappeared.
> >
> > What is it about this command that affects my video card?
> >
>
> I'm replying to my own post just to tidy things up. It turns out that
> udevadm settle was a complete red herring. This command takes a long
> time to execute, so there's rather a high chance of something else
> happening coincidentally at the same time. The real cause of the
> problem was the kernel loading the viafb module followed by fbcon. It's
> fbcon that crashes the screen. If it is blacklisted, the boot
> completes normally.
>
> Actually it always completes normally according to the logs. It's just
> that you can't see it doing so with the screen misbehaving. In any
> case, the problem is purely with the Via Chrome graphics card and
> nothing to do with LFS.
>
> --
>
> H Russman
> --
>

Hazel,

Just for fun, I'm compiling LFS on a VIA-based Netbook by HP (well, if you
call waiting for three days for GCC to compile *fun*, seems sort of
masochistic to me), and I found that you can enable VIA Unichrome Graphics
Support in the kernel. It's under "Legacy Drivers (DANGEROUS)" or something
similar in the kernel's Graphics Options in Device Drivers. You might want
to try that and see if that helps at all. It's untested by me, I'm nowhere
close to that point yet, and probably won't have time to play with it until
after release.
-- 
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

Re: [lfs-support] Is it possible to use gentoo stage3 as tools or temporary system?

[Douglas R. Reno]

On Mon, Jan 30, 2017 at 3:55 PM, Michele Bucca 
wrote:

> Il 30 gen 2017 10:52 PM, "Bruce Dubbs"  ha scritto:
> >
> > Tim Tassonis wrote:
> >>
> >> On 01/30/2017 10:11 PM, Chris Statzer wrote:
> >>>
> >>>
> >>>
> >>> On Mon, Jan 30, 2017 at 7:17 PM, ssmtpmailtesting ssmtpmailtesting
> >>> mailto:ssmtpmailtest...@gmail.com>>
> wrote:
> >>>
> >>> Is it possible to use gentoo stage3 as tools or temporary system?
> >>>
> >>>
> >>> http://distfiles.gentoo.org/releases/x86/autobuilds/
> 20170124/stage3-i686-20170124.tar.bz2
> >>>
> >>>
> >>>  20170124/stage3-i686-20170124.tar.bz2>
> >>>
> >>>
> >>> Then is it possible to skip chapter 5 to make tools or toolchain or
> >>> temporary system?
> >>>
> >>>
> >>> It is possible, and exactly what I did after my first run though LFS.
> >>> Extract it to the root. Chroot to it. Install grub, bc. and compile the
> >>> kernel. Reboot. You already have wget etc etc. I built Xorg etc
> >>> following BLFS and worked flawlessly. Would be happy to answer any
> other
> >>> questions.
> >>
> >>
> >>
> >> Of course it is possible. It might also be possible to use an existing
> >> debian or redhat install as temporary toolchain.
> >>
> >> It just undermines the whole point of Linux From Scratch. The "from
> >> scratch" actually means that you build the whole systen from scratch.
> Like
> >> this, you fail to do that. You will compile at least:
> >>
> >> Glibc-2.24
> >> Zlib-1.2.8
> >> File-5.28
> >> Binutils-2.27
> >> GMP-6.1.1
> >> MPFR-3.1.4
> >> MPC-1.0.3
> >>
> >> with the gentoo compiler and not the one that you built yourself.
> >
> >
> > One thing that is quite reasonable is to build /mnt/lfs/tools (Chapter
> 5) and archive it.  You can then reuse it for any new version of LFS unless
> a package comes up that needs something newer.  But that hasn't happened in
> years.
> >
> > I'll note that on my system, I takes only about 20 minutes to build
> Chapter 5.
> >
> > -rw-rw-r-- 1 lfslfs0 Jan 23 18:08 034-binutils-pass1
> > ...
> > -rw-rw-r-- 1 lfslfs0 Jan 23 18:28 064-xz
> >
> > Yes, it is automated.
> >
> >   -- Bruce
> >
> Using ALFS?
> >
>
>
Yeah, he uses jhalfs, as do I as of late. Too much time to be invested in
doing it manually at this time.
-- 
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

Re: [lfs-support] glibc tests on a VIA nano processor: 2 unexpected failures

[Douglas R. Reno]

On Sun, Jan 22, 2017 at 3:41 PM, Hazel Russman 
wrote:

> On Sun, 22 Jan 2017 12:55:56 -0600
> Bruce Dubbs  wrote:
>
> > Hazel Russman wrote:
> > > I am building LFS on a Sony laptop. It is the first LFS I have built on
> > > this machine, in fact the first I have ever built for a non-intel
> > > processor.
> > >
> > > There are 8 failures in the glibc tests, mostly in math (which the book
> > > suggests are to be expected on non-intel/non-amd chips). The 2 getaddr
> > > failures are also expected. But I also have fails in csu/test-multiarch
> > > and nss/test-netdb. Are these significant?
> >
> > That's hard to say without analyzing the actual failures.  However 8
> > failures out of 2500 tests in a complex library like glibc is probably
> not
> > significant.  The tests most likely make some implicit assumptions that
> > the processor does not satisfy.
> >
> >-- Bruce
> I have now checked the out files. nss/netdb gets timed out. I shall try it
> again with TIMEOUTFACTOR set and see if that makes any difference.
>
> csu/test-multiarch fails to find one of the cpu's architecture flags.
> [code]
> Checking HAS_CPU_FEATURE (SSSE3):
>   init-arch 0
>   cpuinfo (ssse3) 1
>  *** failure ***
> [code]
>
> /proc/cpuinfo shows ssse3 flag is set.
> @Douglas Reno: This also shows that /proc directory is correctly mounted.
>

OK, I just wanted to make sure of that. A thread on LQ suggested it.

I'd hope that it isn't actually trying to use that flag in the compiler.
That could lead to a sticky situation of unexecutable code.
-- 
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

Re: [lfs-support] glibc tests on a VIA nano processor: 2 unexpected failures

[Douglas R. Reno]

On Sun, Jan 22, 2017 at 12:38 PM, Hazel Russman 
wrote:

> I am building LFS on a Sony laptop. It is the first LFS I have built on
> this machine, in fact the first I have ever built for a non-intel processor.
>
> There are 8 failures in the glibc tests, mostly in math (which the book
> suggests are to be expected on non-intel/non-amd chips). The 2 getaddr
> failures are also expected. But I also have fails in csu/test-multiarch and
> nss/test-netdb. Are these significant?
>
> --
> H Russman
>

Greetings Hazel

After looking up the csu/test-multiarch test, I have a couple suggestions:

Make sure that your virtual kernel filesystems exist (cat /proc/cpuinfo
should do the trick)

Increase the timeout factor...

I unfortunately cannot confirm whether or not these are critical, so you
might want to check the .out files from the failed tests and see if those
have any clues.
-- 
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

Re: [lfs-support] New directory layout and FHS 3.0

[Douglas R. Reno]

On Thu, Dec 29, 2016 at 12:59 AM, Hazel Russman 
wrote:

> On Wed, 28 Dec 2016 23:47:45 +0100
> Frans de Boer  wrote:
>
> > I have said that I will forward some patches to get rid of the
> > [...]/lib64 notions after I have tested my older patches against the
> > newest sources.
> >
> > I have created several source code changes and tested them, only to find
> > out that glibc, gcc, libcap and perl have at some places hard coded the
> > path to [...]/lib64 if an x86_64 machine is detected. I can change most
> > of it with good result.
> >
> > Still I do not send the changes yet because I am more and more convinced
> > that on machines with multiarch capabilities one should always use a
> > qualifier in the directory name for libraries.
> > Now, LFS is about teaching others how to start building your own
> > operating system and minimal support utilities. The project started out
> > in the era of 32-bit machines, adopted the 64-bit machine on the fly by
> > use of links to legacy library directories who's naming is no longer
> > discriminatory any more. What if we slip into the 128-bit (or +64-bit)
> > era? Still using the legacy [...]/lib notion?
> > The mail list has already many questions about the naming, maybe time to
> > step into the current reality?
> >
> > Looking at production machines, with current UNIX and Linux
> > distributions, many of them are already using a schema which
> > differentiate already between bit sizes.
> > Currently, I have a conversation on the FHS mailing list of due to the
> > ambiguous nature of qualifiers.
> >
> > A snippet from the latest mail exchange:
> > That said, I can appreciate also the idea that on hardware capable of
> > handling multiple architectures - read size of data paths - you always
> > use qualifiers, regardless if only one or multiple library directories
> > are used. So my previous second proposal is then augmented into:
> >
> >[/usr[/local]]/lib for each different set of libraries
> >
> > For compatibility one should also add
> >[/usr/[/local]]/lib -> [/usr[/local]]/lib
> >Where .../lib links to the library directory supporting the native bit
> >size.
> >
> > This implies that on 32-bit intel like systems, you always have a
> > [...]/lib32 directory, an optional [...]/lib16 and [...]/lib is a link
> > to [...]/lib32.
> > On 64-bit Intel like systems you have [...]/lib64, an optional
> > [...]/lib<32|16> and [...]/lib is a link to [...]/lib64.
> >
> > The above schema is already in widespread use on 64-bit machines, with
> > the exception of the legacy use of [...]/lib for 32-bit library
> directories.
> > Also, modification of sources for glibc, gcc, libcap, perl etc, are not
> > needed anymore. Due to the fact that some of these packages are core
> > packages and it would require a lot of effort for the maintainers to
> > change their current hard coded assumptions into more flexible code.
> > ---
> >
> > I wait to see where this all is going before I decide what to do with
> > the current patches. Note that there are more patches required then
> > currently given in the LFS development branch.
> >
> > Regards, Frans.
>
>
> Will this change do away with the very annoying screens of warning
> messages from package libtool scripts about libraries seemingly having
> moved? I'm sure I'm not the only person who finds them off-putting.
> --


Our current setup (thanks to DJ) gets rid of them entirely. I haven't seen
a single one
-- 
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

Re: [lfs-support] Error systemd

[Douglas R. Reno]

On Wed, Dec 7, 2016 at 2:37 AM, Frans de Boer  wrote:

> On 07-12-16 09:07, Frans de Boer wrote:
>
>> On 06-12-16 23:21, Douglas R. Reno wrote:
>>
>>> Frans de Boer wrote:
>>>
>>>> While building systemd-232, I encounter the next errors during
>>>> installing:
>>>>
>>>> mv: cannot stat '/usr/lib/libnss_myhostname.so.2': No such file or
>>>> directory
>>>> mv: cannot stat '/usr/lib/libnss_mymachines.so.2': No such file or
>>>> directory
>>>> mv: cannot stat '/usr/lib/libnss_resolve.so.2': No such file or
>>>> directory
>>>> root:/sources-lfs# find / -iname libnss_resolve.so.2
>>>> /lib/libnss_resolve.so.2
>>>>
>>>> As one can see, the libraries are not in /usr/lib, rather they are in
>>>> /lib. Has this been overlooked or am I the only one? In which case I
>>>> have to hunt deeper.
>>>>
>>>> Regards, Frans.
>>>>
>>> What version of the book are you building?
>>>
>>> We don't have those commands in the LFS page currently. I haven't
>>> checked BLFS as I wasn't the one who did that page, yet.
>>>
>>> Those are now installed in /lib by default so that the NSS service in
>>> Glibc can pick them up without extra hassle.
>>>
>>> Except for the last two lines, those are not my commands. They seem to
>> come from the make install command aka Makefile.
>>
>> As I stated, it is the development version and implies systemd-232. All
>> according to the book.
>> I know that it is placed into /lib and not /usr/lib. Is something gone
>> wrong during the creation of the LFS specific systemd?
>>
>> I will examine the Makefile(s?) myself.
>>
>> --- Frans
>>
> Oeps, I feel stupid :\, yesterday checked it and today againonly to
> find that the mv command where a leftover of previous systemd build chain.
> It was right under the install command and I did not see that before.
>
> Sorry for my sloppiness.
>
> --- Frans
>
>
Hey,

It happens to all of us at some point. Don't call yourself stupid, I've
done that several times in the past few months. I'm happy that I could at
least point you in the right direction. :-)

Thank you,

 Douglas R. Reno
-- 
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

Re: [lfs-support] Error systemd

[Douglas R. Reno]

Frans de Boer wrote:
While building systemd-232, I encounter the next errors during 
installing:


mv: cannot stat '/usr/lib/libnss_myhostname.so.2': No such file or 
directory
mv: cannot stat '/usr/lib/libnss_mymachines.so.2': No such file or 
directory

mv: cannot stat '/usr/lib/libnss_resolve.so.2': No such file or directory
root:/sources-lfs# find / -iname libnss_resolve.so.2
/lib/libnss_resolve.so.2

As one can see, the libraries are not in /usr/lib, rather they are in 
/lib. Has this been overlooked or am I the only one? In which case I 
have to hunt deeper.


Regards, Frans.

What version of the book are you building?

We don't have those commands in the LFS page currently. I haven't 
checked BLFS as I wasn't the one who did that page, yet.


Those are now installed in /lib by default so that the NSS service in 
Glibc can pick them up without extra hassle.


--
Douglas R. Reno
--LFS/BLFS systemd maintainer

--
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

Re: [lfs-support] PiLFS - LFS on Raspberry Pi

[Douglas R. Reno]

On Mon, Nov 14, 2016 at 3:09 PM, akhiezer  wrote:

>
> In case of use and not already known about:
>
>   www.intestinate.com/pilfs/
>
>  - LFS on raspberry pi 1/2/3 .
>
>
> BLFS isn't covered fully: it's mainly via several examples of 'how to
> install main-app with deps'. The '*.Slackbuild' scripts and related
> materials, in 'Slackware on Raspberry Pi' (www.fatdog.eu), are useful
> references for BLFS (& LFS) packages.
>
>
>
> akh
>
>
>
I have heard of this.

If I happen to get my paws on a Raspberry Pi anytime soon, I'll go through
the process of validating BLFS and LFS on it before the next release. But I
have to have the $25 + SD Card + other accessories first to do so.
-- 
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

Re: [lfs-support] Compiling

[Douglas R. Reno]

On Tue, Nov 1, 2016 at 7:58 PM, Jared lima 
wrote:

>
>
> On Wed, Nov 2, 2016 at 12:22 AM, Ken Moffat 
> wrote:
>
>> On Tue, Nov 01, 2016 at 11:38:27PM +, Jared lima wrote:
>> > im not sure how to do the compiling.
>> >
>> > I try to run the given command:
>> >
>> > ../configure --prefix=/tools \
>> > --with-sysroot=$LFS \
>> > --with-lib-path=/tools/lib \
>> > --target=$LFS_TGT \
>> > --disable-nls \
>> > --disable-werror
>> >
>> >
>> > after cd'ing to /mnt/lfs/sources/build
>> >
>> > and it says
>> > "bash: ../configure: no such file or directory"
>> >
>> >
>> > help?
>>
>> For each package: untar the package, cd into the directory it
>> created, THEN run the commands.  After you install it, cd ../ and
>> then remove the directory.
>>
>> I assume this is pass one binutils.  So first extract the binutils
>> tarball (tar -xf or tar -xvf), cd into the binutils-2.XX
>> directory, mkdir build, cd build, ../configure ...
>>
>> And make sure that LFS and LFS_TGT are in your environment.
>>
>> ĸen
>> --
>> `I shall take my mountains', said Lu-Tze. `The climate will be good
>> for them.' -- Small Gods
>> --
>> 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
>>
> So what is the command to make both of those in the path environment
>
>
$ echo $LFS

$ echo $LFS_TGT

Have you ever used a shell before?
-- 
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

Re: [lfs-support] Differenfe Between the GCC of Chapter 5 and the one of Chapter 6

[Douglas R. Reno]

On Mon, Oct 31, 2016 at 7:37 PM, Michele Bucca 
wrote:

>
> >>
> >> On Tuesday, 1 November 2016, Michele Bucca 
> wrote:
> >>>
> >>> > The cross-toolchain is extremely stripped down, and doesn't include
> several libraries that many packages will need to compile. It is also setup
> for a different target - we do that to isolate the final system from the
> host and ensure that there are no dependencies on libraries from the host.
> >>>
> >>> Can These libraries that are not included  be added later and built
> separately?
> >>
> >> I have never tried, but I would say it would require a lot of
> customisation, basically I would say it is so hard, but probably possible.
> You would need to edit current binaries, adjust config, and if you want to
> delete /tools, well you get the idea.
> >>
> >>
> >
> > I think that it would take more time to accomplish this than it would to
> complete the entirety of Chapter 6 w/out tests.
>
> Ok, is there a way to stop the compile process and resume it later, eg the
> next day? I can't leave my laptop on for 8 hours
>
I think that it is possible.

Ctrl-C it and then run "make" again later. I've done it, but I don't recall
the safety of the endeavor. I know it worked at one time though.
-- 
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

Re: [lfs-support] Differenfe Between the GCC of Chapter 5 and the one of Chapter 6

[Douglas R. Reno]

On Mon, Oct 31, 2016 at 7:32 PM, Samuel Tyler <
samuel.ty...@education.nsw.gov.au> wrote:

>
>
> On Tuesday, 1 November 2016, Michele Bucca 
> wrote:
>
>> > The cross-toolchain is extremely stripped down, and doesn't include
>> several libraries that many packages will need to compile. It is also setup
>> for a different target - we do that to isolate the final system from the
>> host and ensure that there are no dependencies on libraries from the host.
>>
>> Can These libraries that are not included  be added later and built
>> separately?
>>
> I have never tried, but I would say it would require a lot of
> customisation, basically I would say it is so hard, but probably possible.
> You would need to edit current binaries, adjust config, and if you want to
> delete /tools, well you get the idea.
>
>
>
I think that it would take more time to accomplish this than it would to
complete the entirety of Chapter 6 w/out tests.
-- 
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

Re: [lfs-support] Differenfe Between the GCC of Chapter 5 and the one of Chapter 6

[Douglas R. Reno]

On Mon, Oct 31, 2016 at 7:21 PM, Michele Bucca 
wrote:

>
> >> >
> >> >
> >>
> >> i use a Intel Celeron n2840 with 4GB of RAM
> >>
> >>
> > In your case, you are running a 2.16GHz CPU. You will save many hours by
> not running the tests (I ran them on a Core2Duo @ 2.0GHz last night. It
> took 8 hours to complete).
> >
> > I can't offer an exact estimation, but it will save a lot of time by not
> running them.
> >
> Why building a cross-toolchain (chapter 5) takes less time?
>
>
> The cross-toolchain is extremely stripped down, and doesn't include
several libraries that many packages will need to compile. It is also setup
for a different target - we do that to isolate the final system from the
host and ensure that there are no dependencies on libraries from the host.
-- 
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

Re: [lfs-support] Differenfe Between the GCC of Chapter 5 and the one of Chapter 6

[Douglas R. Reno]

On Mon, Oct 31, 2016 at 2:38 PM, Michele Bucca 
wrote:

>
> >> How much time can i save by skipping tests? How much SBUs does it take
> >> to compile without tests?
> >
> >
> > I don't know that in SBU, but a Core2Duo using 1 core takes about 30
> minutes.  On a i7-5820K CPU @ 3.30GHz using 10 cores, gcc without tests
> takes 283 seconds.  :)
> >
> >
> >   -- Bruce
> >
> >
>
> i use a Intel Celeron n2840 with 4GB of RAM
>
> In your case, you are running a 2.16GHz CPU. You will save many hours by
not running the tests (I ran them on a Core2Duo @ 2.0GHz last night. It
took 8 hours to complete).

I can't offer an exact estimation, but it will save a lot of time by not
running them.
-- 
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

Re: [lfs-support] Grub2 won't boot new UEFI LFS build

[Douglas R. Reno]

On Sun, Oct 30, 2016 at 9:21 PM, Ken Moffat  wrote:

> On Sun, Oct 30, 2016 at 09:25:06PM -0400, jacob wrote:
> >
> > I am using chainloading probably incorrectly here, sorry, I shall
> explain a
> > few things regarding my setup. I'm essentially attempting to boot LFS
> > through UEFI in 2 different ways - Through the LFS install with LFS's
> grub,
> > and through Arch grub. Unrelated to the issue, UEFI indeed works on
> grub2,
> > because I have an entry on my UEFI for arch linux that successfully boots
> > arch. UEFI booting also works on the arch iso from a USB drive. However,
> I
> > can't say UEFI works on LFS personally as of yet.
> >
>
> The LFS grub is probably incorrectly built for UEFI.  But unless you
> chainload, only one bootloader (i.e. Arch's grub, unless you
> overwrite it) is likely to be used.  Hmm, I suppose that might not
> be true for UEFI - but first you need to get both your LFS kernel
> and the stanza in Arch's grub.cfg to work.
>
> Only after that should you think about installing grub from LFS.
>
> > Referring to arch grub, I'm specifically pointing out the generated entry
> > for LFS to boot its kernel on it:
> >
> > menuentry 'Linux From Scratch (7.10-systemd) (on /dev/sdc2)' --class
> > linuxfromscratch --class gnu-linux --class gnu --class os
> > $menuentry_id_option
> > 'osprober-gnulinux-simple-d6788259-f948-4164-ae29-d1b996ffd6d9' {
> >   insmod part_gpt
> >   insmod ext2
> >   set root='hd2,gpt2'
> >   if [ x$feature_platform_search_hint = xy ]; then
> > search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt2
> > --hint-efi=hd2,gpt2 --hint-baremetal=ahci2,gpt2
> > d6788259-f948-4164-ae29-d1b996ffd6d9
> >   else
> > search --no-floppy --fs-uuid --set=root
> > d6788259-f948-4164-ae29-d1b996ffd6d9
> >   fi
> >   linux /boot/vmlinuz-4.7.2-lfs-7.10-systemd
>
> I note you don't care about the recent Dirty COW vulnerability.  But
> since it doesn't boot, that kernel version is the least of your problems.
> But when it does boot, safest to upgrade to any stable kernel
> released after 20th October - my notes say 4.7.9, 4.8.3, 4.4.26 or
> later - but for other people, some old stable kernels were also
> fixed.
>

He probably doesn't know about it.

This is why I want *more* transparency in our fixing of security issues.
Communication is key, and with the other vulnerabilities that are
discovered daily that our users are affected by, and the impact that they
can have, it is the least that we can do is to keep them informed.

Wasn't that what the old lfs-security mailing list was for?


>
> > root=UUID=d6788259-f948-4164-ae29-d1b996ffd6d9 rootfstype=ext4 ro
> > }
> >
>
> Is the UUID correct for the LFS partition ?
> > Either way when booting from both entry's regardless of which grub it
> fails
> > to boot. linux /boot/vmlinuz-4.7.2-lfs-7.10-systemd
> > root=UUID=d6788259-f948-4164-ae29-d1b996ffd6d9 rootfstype=ext4 ro is the
> > exact same on the LFS grub entry even, with my latest slight
> modifications
> > for testing and revisioning.
>
> Does the Arch grub give you a graphical screen ?  If so, try adding
> 'nomodeset' to the grub command line.
>
> I also found an old (ubuntu) report that UEFI does not support
> booting in text mode.  Dunno, I've got enough trouble with BIOS
> hardware.
>
> ĸen
> --
> `I shall take my mountains', said Lu-Tze. `The climate will be good
> for them.' -- Small Gods
> --
> 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
>
-- 
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

Re: [lfs-support] TzData2016f extracting question

[Douglas R. Reno]

On Sun, Oct 30, 2016 at 9:17 PM, Jared lima 
wrote:

>
>
> On Mon, Oct 31, 2016 at 2:15 AM, Douglas R. Reno 
> wrote:
>
>>
>>
>> On Sun, Oct 30, 2016 at 9:13 PM, Jared lima 
>> wrote:
>>
>>> okay so do i uncompress and extract it anyways? also ialready did the
>>> glibc-2.24 archive and there isnt a /build directory in it... does that get
>>> created at a later time?
>>>
>>> On Mon, Oct 31, 2016 at 2:10 AM, Douglas R. Reno 
>>> wrote:
>>>
>>>>
>>>>
>>>> On Sun, Oct 30, 2016 at 9:09 PM, Jared lima <
>>>> jared.lima.alk...@gmail.com> wrote:
>>>>
>>>>> ok, so when i run that command, i should expect the creation of a
>>>>> folder containing the contents like what the other packages make?
>>>>>
>>>>> because when i ran the command to extract a tar.gz file, this archive
>>>>> dumped all the contents into the "root directory" for /sources.  it didn't
>>>>> create its own folder.
>>>>>
>>>>> On Mon, Oct 31, 2016 at 2:07 AM, Douglas R. Reno >>>> > wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Oct 30, 2016 at 9:05 PM, Jared lima <
>>>>>> jared.lima.alk...@gmail.com> wrote:
>>>>>>
>>>>>>> okay, but when i ran the wget-list command to download all the
>>>>>>> packages in a previous chapter, it downloaded a "tzdata2016f.tar.gz"
>>>>>>> archive.  do i ignore the archive thats all by itsself or what?
>>>>>>>
>>>>>>> On Mon, Oct 31, 2016 at 2:04 AM, Douglas R. Reno <
>>>>>>> renodr2...@gmail.com> wrote:
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sun, Oct 30, 2016 at 9:02 PM, Jared lima <
>>>>>>>> jared.lima.alk...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>> I have already asked this but i figured i should make a dedicated
>>>>>>>>> post for this, plus my question still hasnt exactly been answered
>>>>>>>>>
>>>>>>>>> Using LFS 7.10 stable,
>>>>>>>>>
>>>>>>>>> Chapter 5.3, the part where you extract all the downloaded
>>>>>>>>> packages before compiling.
>>>>>>>>>
>>>>>>>>> When i extract the tzdata2016f.tar.gz archive, it puts all the
>>>>>>>>> contents into the source directory /mnt/lfs/sources , aka the folder 
>>>>>>>>> where
>>>>>>>>> all the downloaded packages are.
>>>>>>>>>
>>>>>>>>> it doesn't create its own "protected" directory for all the files
>>>>>>>>> like all the other packages make.
>>>>>>>>>
>>>>>>>>> so im a bit confused if thats normal or not.  i was told that the
>>>>>>>>> book extracts tzdata from within the glibc-2.24/build directory.
>>>>>>>>>
>>>>>>>>> so should i just move on, and let the extracted files rest inside
>>>>>>>>> the "root directory" of the location of all the extracted sources
>>>>>>>>> (/mnt/lfs/sources), or do i need to create a directory for 
>>>>>>>>> tzdata2016f and
>>>>>>>>> change the permissions to what the others are?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> im sorry, this stuff is just a bit confusing to me.
>>>>>>>>>
>>>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> In the book, tzdata is installed as part of the glibc page. We
>>>>>>>> assume that you are in the glibc-(insert version here)/build directory 
>>>>>>>> when
>>>>>>>> you unpack that tarball. Yes, it is a separate package theoretically, 
>>>>>>>> but
>>>>>>>> as far as I understand, it made sense for us to keep it in that page.
>>>>>>>>
>>>>>>>> --
>>>>>>>> http://l

Re: [lfs-support] TzData2016f extracting question

[Douglas R. Reno]

On Sun, Oct 30, 2016 at 9:13 PM, Jared lima 
wrote:

> okay so do i uncompress and extract it anyways? also ialready did the
> glibc-2.24 archive and there isnt a /build directory in it... does that get
> created at a later time?
>
> On Mon, Oct 31, 2016 at 2:10 AM, Douglas R. Reno 
> wrote:
>
>>
>>
>> On Sun, Oct 30, 2016 at 9:09 PM, Jared lima 
>> wrote:
>>
>>> ok, so when i run that command, i should expect the creation of a folder
>>> containing the contents like what the other packages make?
>>>
>>> because when i ran the command to extract a tar.gz file, this archive
>>> dumped all the contents into the "root directory" for /sources.  it didn't
>>> create its own folder.
>>>
>>> On Mon, Oct 31, 2016 at 2:07 AM, Douglas R. Reno 
>>> wrote:
>>>
>>>>
>>>>
>>>> On Sun, Oct 30, 2016 at 9:05 PM, Jared lima <
>>>> jared.lima.alk...@gmail.com> wrote:
>>>>
>>>>> okay, but when i ran the wget-list command to download all the
>>>>> packages in a previous chapter, it downloaded a "tzdata2016f.tar.gz"
>>>>> archive.  do i ignore the archive thats all by itsself or what?
>>>>>
>>>>> On Mon, Oct 31, 2016 at 2:04 AM, Douglas R. Reno >>>> > wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Sun, Oct 30, 2016 at 9:02 PM, Jared lima <
>>>>>> jared.lima.alk...@gmail.com> wrote:
>>>>>>
>>>>>>> I have already asked this but i figured i should make a dedicated
>>>>>>> post for this, plus my question still hasnt exactly been answered
>>>>>>>
>>>>>>> Using LFS 7.10 stable,
>>>>>>>
>>>>>>> Chapter 5.3, the part where you extract all the downloaded packages
>>>>>>> before compiling.
>>>>>>>
>>>>>>> When i extract the tzdata2016f.tar.gz archive, it puts all the
>>>>>>> contents into the source directory /mnt/lfs/sources , aka the folder 
>>>>>>> where
>>>>>>> all the downloaded packages are.
>>>>>>>
>>>>>>> it doesn't create its own "protected" directory for all the files
>>>>>>> like all the other packages make.
>>>>>>>
>>>>>>> so im a bit confused if thats normal or not.  i was told that the
>>>>>>> book extracts tzdata from within the glibc-2.24/build directory.
>>>>>>>
>>>>>>> so should i just move on, and let the extracted files rest inside
>>>>>>> the "root directory" of the location of all the extracted sources
>>>>>>> (/mnt/lfs/sources), or do i need to create a directory for tzdata2016f 
>>>>>>> and
>>>>>>> change the permissions to what the others are?
>>>>>>>
>>>>>>>
>>>>>>> im sorry, this stuff is just a bit confusing to me.
>>>>>>>
>>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> In the book, tzdata is installed as part of the glibc page. We assume
>>>>>> that you are in the glibc-(insert version here)/build directory when you
>>>>>> unpack that tarball. Yes, it is a separate package theoretically, but as
>>>>>> far as I understand, it made sense for us to keep it in that page.
>>>>>>
>>>>>> --
>>>>>> 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
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>> tzdata2016f is a separate file archive. We use that "tar -xf ..."
>>>> command to untar it.
>>>>
>>>&g

Re: [lfs-support] TzData2016f extracting question

[Douglas R. Reno]

On Sun, Oct 30, 2016 at 9:09 PM, Jared lima 
wrote:

> ok, so when i run that command, i should expect the creation of a folder
> containing the contents like what the other packages make?
>
> because when i ran the command to extract a tar.gz file, this archive
> dumped all the contents into the "root directory" for /sources.  it didn't
> create its own folder.
>
> On Mon, Oct 31, 2016 at 2:07 AM, Douglas R. Reno 
> wrote:
>
>>
>>
>> On Sun, Oct 30, 2016 at 9:05 PM, Jared lima 
>> wrote:
>>
>>> okay, but when i ran the wget-list command to download all the packages
>>> in a previous chapter, it downloaded a "tzdata2016f.tar.gz" archive.  do i
>>> ignore the archive thats all by itsself or what?
>>>
>>> On Mon, Oct 31, 2016 at 2:04 AM, Douglas R. Reno 
>>> wrote:
>>>
>>>>
>>>>
>>>> On Sun, Oct 30, 2016 at 9:02 PM, Jared lima <
>>>> jared.lima.alk...@gmail.com> wrote:
>>>>
>>>>> I have already asked this but i figured i should make a dedicated post
>>>>> for this, plus my question still hasnt exactly been answered
>>>>>
>>>>> Using LFS 7.10 stable,
>>>>>
>>>>> Chapter 5.3, the part where you extract all the downloaded packages
>>>>> before compiling.
>>>>>
>>>>> When i extract the tzdata2016f.tar.gz archive, it puts all the
>>>>> contents into the source directory /mnt/lfs/sources , aka the folder where
>>>>> all the downloaded packages are.
>>>>>
>>>>> it doesn't create its own "protected" directory for all the files like
>>>>> all the other packages make.
>>>>>
>>>>> so im a bit confused if thats normal or not.  i was told that the book
>>>>> extracts tzdata from within the glibc-2.24/build directory.
>>>>>
>>>>> so should i just move on, and let the extracted files rest inside the
>>>>> "root directory" of the location of all the extracted sources
>>>>> (/mnt/lfs/sources), or do i need to create a directory for tzdata2016f and
>>>>> change the permissions to what the others are?
>>>>>
>>>>>
>>>>> im sorry, this stuff is just a bit confusing to me.
>>>>>
>>>>>
>>>> Hello,
>>>>
>>>> In the book, tzdata is installed as part of the glibc page. We assume
>>>> that you are in the glibc-(insert version here)/build directory when you
>>>> unpack that tarball. Yes, it is a separate package theoretically, but as
>>>> far as I understand, it made sense for us to keep it in that page.
>>>>
>>>> --
>>>> 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
>>>>
>>>>
>>>
>>>
>>>
>> tzdata2016f is a separate file archive. We use that "tar -xf ..." command
>> to untar it.
>>
>>
>> --
>> 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
>>
>>
>
>
When you decompress that package, because of the way that it is created, it
does not create a separate directory. Our instructions have it unpacked in
the "glibc-2.24/build" directory.
-- 
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

Re: [lfs-support] TzData2016f extracting question

[Douglas R. Reno]

On Sun, Oct 30, 2016 at 9:05 PM, Jared lima 
wrote:

> okay, but when i ran the wget-list command to download all the packages in
> a previous chapter, it downloaded a "tzdata2016f.tar.gz" archive.  do i
> ignore the archive thats all by itsself or what?
>
> On Mon, Oct 31, 2016 at 2:04 AM, Douglas R. Reno 
> wrote:
>
>>
>>
>> On Sun, Oct 30, 2016 at 9:02 PM, Jared lima 
>> wrote:
>>
>>> I have already asked this but i figured i should make a dedicated post
>>> for this, plus my question still hasnt exactly been answered
>>>
>>> Using LFS 7.10 stable,
>>>
>>> Chapter 5.3, the part where you extract all the downloaded packages
>>> before compiling.
>>>
>>> When i extract the tzdata2016f.tar.gz archive, it puts all the contents
>>> into the source directory /mnt/lfs/sources , aka the folder where all the
>>> downloaded packages are.
>>>
>>> it doesn't create its own "protected" directory for all the files like
>>> all the other packages make.
>>>
>>> so im a bit confused if thats normal or not.  i was told that the book
>>> extracts tzdata from within the glibc-2.24/build directory.
>>>
>>> so should i just move on, and let the extracted files rest inside the
>>> "root directory" of the location of all the extracted sources
>>> (/mnt/lfs/sources), or do i need to create a directory for tzdata2016f and
>>> change the permissions to what the others are?
>>>
>>>
>>> im sorry, this stuff is just a bit confusing to me.
>>>
>>>
>> Hello,
>>
>> In the book, tzdata is installed as part of the glibc page. We assume
>> that you are in the glibc-(insert version here)/build directory when you
>> unpack that tarball. Yes, it is a separate package theoretically, but as
>> far as I understand, it made sense for us to keep it in that page.
>>
>> --
>> 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
>>
>>
>
>
>
tzdata2016f is a separate file archive. We use that "tar -xf ..." command
to untar it.
-- 
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

Re: [lfs-support] TzData2016f extracting question

[Douglas R. Reno]

On Sun, Oct 30, 2016 at 9:02 PM, Jared lima 
wrote:

> I have already asked this but i figured i should make a dedicated post for
> this, plus my question still hasnt exactly been answered
>
> Using LFS 7.10 stable,
>
> Chapter 5.3, the part where you extract all the downloaded packages before
> compiling.
>
> When i extract the tzdata2016f.tar.gz archive, it puts all the contents
> into the source directory /mnt/lfs/sources , aka the folder where all the
> downloaded packages are.
>
> it doesn't create its own "protected" directory for all the files like all
> the other packages make.
>
> so im a bit confused if thats normal or not.  i was told that the book
> extracts tzdata from within the glibc-2.24/build directory.
>
> so should i just move on, and let the extracted files rest inside the
> "root directory" of the location of all the extracted sources
> (/mnt/lfs/sources), or do i need to create a directory for tzdata2016f and
> change the permissions to what the others are?
>
>
> im sorry, this stuff is just a bit confusing to me.
>
>
Hello,

In the book, tzdata is installed as part of the glibc page. We assume that
you are in the glibc-(insert version here)/build directory when you unpack
that tarball. Yes, it is a separate package theoretically, but as far as I
understand, it made sense for us to keep it in that page.
-- 
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

Re: [lfs-support] Grub2 won't boot new UEFI LFS build

[Douglas R. Reno]

On Sun, Oct 30, 2016 at 7:43 PM, jacob  wrote:

> On 2016-10-30 20:33, Ken Moffat wrote:
>
>> On Sun, Oct 30, 2016 at 06:55:56PM -0400, jacob wrote:
>>
>>>
>>>
>>> I've changed grub-install to add the --modules flag, so it's now ran as
>>> grub-install --target=x86_64-efi --efi-directory=/boot/efi
>>> --bootloader-id=LFS --modules=part_gpt --recheck --debug
>>>
>>> Here is my grub.cfg, although it attempted to boot into blind mode
>>> without
>>> loading efi_gop and efi_uga. I believe the grub configuration is
>>> irrelevant
>>> because I can chainload off my arch linux install, and still come to the
>>> same issue.
>>>
>>>
>> I might be *wildly* mistaken here (I don't use UEFI, and I recall
>> loads of problems for people trying to use it), but doesn't
>> chainload cause (Arch's) grub to transfer to another bootloader ?
>>
>> If so, I guess that second bootloader is the LFS grub, and therefore
>> the way it was compiled, and its config file, are still relevant ?
>>
>> I also remember that distros such as Fedora do not support chainload
>> because it might not work (and I think the notworking examples in
>> their bug that caused that were UEFI).
>>
>> ĸen
>> --
>> `I shall take my mountains', said Lu-Tze. `The climate will be good
>> for them.' -- Small Gods
>>
>
> Not exactly, a bootloader won't load another bootloader.
> Grub on either LFS or Arch, or any linux distro will always execute the
> linux kernel with generated configurations.
>
> Thanks, Jacob.
>
>
I might be *wildly* wrong here, but are you sure that Grub2 supports UEFI?
I remember discussions about rEFInd in the past.

Dan McGhee wrote a hint about it here:

http://linuxfromscratch.org/hints/downloads/files/lfs-uefi.txt
-- 
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

Re: [lfs-support] systemd-231: Cannot resolve properly using the stub resolver

[Douglas R. Reno]

On Thu, Oct 6, 2016 at 12:18 AM, aur basica  wrote:

> On Wed, Oct 5, 2016 at 9:43 PM, Wayne Blaszczyk 
> wrote:
>
>> The instructions on how to install systemd-231 involves the following
>> instruction.
>>
>> Fix a broken symlink created by the systemd installation process:
>>
>> rm -fv /etc/resolv.conf
>> ln -s ../lib/systemd/resolv.conf /etc/resolv.conf
>>
>> If I do this, it breaks DNS resolving. I find that more than half of the
>> urls that I visit (via firefox) do not work.
>>
>> If I revert back to to the old way,
>> ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf
>> then everything works fine.
>> Has no one come across this?
>>
>> I've found the following that matches my symptoms to a tee:
>>
>> https://github.com/systemd/systemd/issues/3826
>>
>> Regards,
>> Wayne.
>>
>>
>>
>>
>> --
>> 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
>>
>
> Hi Wayne,
>
> I discovered the same issue as well. I had issues downloading packages
> with curl so at the time I thought it might've been an issue with it till I
> saw it happen with wget.
>
> --
> 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
>
>
Wayne,

I fixed this at r11133. Can you please check the development book tomorrow
and tell me what you think?

I might add this to the errata page soon.
-- 
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

Re: [lfs-support] Development systemd - no bash startup files?

[Douglas R. Reno]

On Oct 7, 2016 3:22 PM, "Frans de Boer"  wrote:
>
> Dear all,
>
> I noticed that in the current development papers, there is no mention of
creating the bash startup files. An omission, or by design?
>
> Regards, Frans.
>

Hello Frans!

The Bash Startup Files are in Chapter 3 (After LFS Configuration Issues) of
BLFS.
-- 
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

Re: [lfs-support] systemd-231: Cannot resolve properly using the stub resolver

[Douglas R. Reno]

On Wed, Oct 5, 2016 at 5:43 AM, Wayne Blaszczyk 
wrote:

> The instructions on how to install systemd-231 involves the following
> instruction.
>
> Fix a broken symlink created by the systemd installation process:
>
> rm -fv /etc/resolv.conf
> ln -s ../lib/systemd/resolv.conf /etc/resolv.conf
>
> If I do this, it breaks DNS resolving. I find that more than half of the
> urls that I visit (via firefox) do not work.
>
> If I revert back to to the old way,
> ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf
> then everything works fine.
> Has no one come across this?
>
> I've found the following that matches my symptoms to a tee:
>
> https://github.com/systemd/systemd/issues/3826
>
> Regards,
> Wayne.
>
>
>
Hi Wayne,

We've come across it. DJ and I have been discussing changing it back to the
old behavior.

The following lines in the v231 changelog made me think that it needed to
be changed:

"* systemd-resolved now listens on the local IP address 127.0.0.53:53
  for DNS requests. This improves compatibility with local programs
  that do not use the libc NSS or systemd-resolved's bus APIs for
name
  resolution. This minimal DNS service is only available to local
  programs and does not implement the full DNS protocol, but enough
to
  cover local DNS clients. A new, static resolv.conf file, listing
just
  this DNS server is now shipped in /usr/lib/systemd/resolv.conf.
It is
  now recommended to make /etc/resolv.conf a symlink to this file in
  order to route all DNS lookups to systemd-resolved, regardless if
  done via NSS, the bus API or raw DNS packets. Note that this local
  DNS service is not as fully featured as the libc NSS or
  systemd-resolved's bus APIs. For example, as unicast DNS cannot be
  used to deliver link-local address information (as this implies
  sending a local interface index along), LLMNR/mDNS support via
this
  interface is severely restricted. It is thus strongly recommended
for
  all applications to use the libc NSS API or native
systemd-resolved
  bus API instead."
-- 
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

Re: [lfs-support] systemd build issues

[Douglas R. Reno]

On Oct 2, 2016 4:43 PM, "Bruce Dubbs"  wrote:
>
> Frans de Boer wrote:
>>
>> On 02-10-16 18:04, Bruce Dubbs wrote:
>>>
>>> Frans de Boer wrote:
>>>>
>>>> On 02-10-16 11:35, Pierre Labastie wrote:
>>>>>
>>>>> On 02/10/2016 10:25, Frans de Boer wrote:
>>>>>>
>>>>>> LS,
>>>>>>
>>>>>> Chapter 6 contains directions to build systemd. Two issues:
>>>>>> 1 - "configure" is not yet available, one has to run ./autogen.sh
>>>>>> first.
>>>>>> 2 - at some point xsltproc is needed, but not found.
>>>>>>
>>>>>> Am I missing something or is this not yet tested by others?
>>>
>>>
>>>>> For 1 - I just untarred systemd-231 (used in both stable and
development
>>>>> LFS):
>>>>> configure is available... Have you downloaded systemd using the link
>>>>> in the
>>>>> book (from anduin.linuxfromscratch.org)?
>>>>> For 2 - the instructions tell to create a config.cache file. This
should
>>>>> allow
>>>>> to work around a missing xsltproc.
>>>
>>>
>>>> 1 - No, I use the systemd-231 from the systemd project site, not the
>>>> anduin.
>>>> IMO, if modifications are needed to the original, it should have been
>>>> mentioned in the book itself. After all, the purpose is to learn ;)
>>>
>>>
>>> Modifications are not needed other than the packaging.  The systemd
>>> upstream package needs dependencies not in LFS to build the man pages.
>>> We repackage the tarball just to add the man pages and remove the
>>> dependency on xsltproc.
>
>
>> So, it seems that systemd has become too bloated to be considered a
>> replacement of the vinit system as it once was presented - or am I
kicking
>> in open doors now ;)
>
>
> It's been that way since it incorporated udev and killed the separate
version of udev (thankfully forked as eudev).  That was somewhere around
version 180 or so IIRC.
>
>
>> Anyhow, I will use the repackaged tar ball, but would recommend to add a
>> note in the documentation itself that one is expected to use the
>> repackaged tar ball due to adaptations.
>
>
> Douglas or DJ?  I think that's your department.
>
>   -- Bruce

I'll pop one in once I get back in an hour or so.

Douglas R. Reno
-- 
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

Re: [lfs-support] Perl make -k check fail

[Douglas R. Reno]

On Sep 28, 2016 4:02 PM, "Michele Bucca"  wrote:
>
>
> Il 28 set 2016 11:01 PM, "Bruce Dubbs"  ha scritto:
> >
> > Michele Bucca wrote:
> >>
> >> Il 28 set 2016 10:31 PM, "Chris Fowler"  ha scritto:
> >>>
> >>>
> >>> I've had test fail when they took too long to complete.  An example
> >>> would be a module that for some reason will fail if execution of a
> >>> test took longer than 10s.  I'm doing my build on a USB stick that is
> >>> 2.0 and slow.
> >
> >
> >> I'm doing my build on usb too...I wonder if I will be able to boot my
> >> system on that when I will finish
> >
> >
> > Should be OK.  There really isn't anything timing dependent in a base
LFS system.  About the only thing is a rootdelay=5 may be needed in the
linux line of the grub configuration file.
> >
> >
http://www.linuxtopia.org/online_books/linux_kernel/kernel_configuration/re58.html
> >
> >   -- Bruce
> >
> >
> >
> >
> Can I Continue?
>

Yeah, you should be good.

Douglas R. Reno
-- 
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