Installed LFS, first questions about uninstalling, updating etc
 

After I finished installing LFS and am installing BLFS parts I have some questions:

1. At boot after login a message that link is up overlaps the command promt. How could I make it appear above the command prompt? Also can "No mail" be not shown there? I am not interested in checking mail at boot.
https://ibb.co/cJHC5w

2. I installed svn-20171020 and would be happy if I found a way to apply updates without having to rebuild.
Would it be save to update what is new from svn-20171020 to svn-20171028? Here are the packages:

Bash 4.4.12
Binutils-2.29.1
Check-0.12.0
Coreutils-8.28
DejaGNU-1.6.1
Eudev-3.2.4
E2fsprogs-1.43.7
Expat-2.2.4
Expect-5.45.3
File-5.32
Gawk-4.2.0
IPRoute2-4.13.0
Man-pages-4.13
MPFR-3.1.6
Perl-5.26.1
Texinfo-6.5
Tzdata-2017c
Util-Linux-2.31

Binutils-2.29.1 is part of the toolchain, so I should not update?

3. Is there any way to find reverse dependencies? Eg if I want to uninstall a progeram with it's dependencies how can I know if some dependencies are needed from another program I still use?

4. Is there any advise to make keeping my system up to date easier? Any easy way to find the packages that need to be updated? (without package manager)

Thank you!

I can't answer the other questions, but on this one, I use a simple recipe. Use at your own risk. Be aware that if anything goes wrong, there will be no help.

I upgrade LFS in place using the svn book, but only if there is a new glibc. I use the following approach:

If a new glibc is released, then using the latest LFS svn book, boot LFS/BLFS and login as root.

Install the latest linux API headers.

Compile glibc. Remember that you are already logged in to a working LFS system. Therefore, skip the symlinks. The symlinks are intended for an incomplete LFS build taking place from a host using chroot so that gcc can find its libraries and headers. The sinario here is that you have a completed LFS and BLFS with a fully configured gcc. If you run those symlinks, recovery is almost impossible. You will have hosed LFS/BLFS. That is why I back up LFS using Clonezilla.

Then compile binutils, coreutils, dbus, util-linux, and systemd.

Finally, compile the linux kernel corresponding to the API headers that you just installed.

Unless you are using proprietary graphics drivers, it should boot into an GUI login prompt. Run version.sh to see if the new glibc is there.

Upgrading the BLFS svn book is not difficult. No problems there. You pick only the installed packages that have new versions.

Hi
To remove the mail prompt you can add
unset MAILCHECK to your .bashrc

For help with number one try this link, if you are not using systemd.

https://superuser.com/questions/3513...ing-my-console

Thank you! So you leave the whole LFS without updates till there is new glibc? And if there is new glibc you update only glibc and toolchain? What about all other packages that don't belong to toolchain? Is it dangerous to update them too?

The dangerous packages are glibc, kernel headers, binutils, gcc and the three gcc libraries (mpc, mpfr, gmp). Anything else can be updated safely. Packages that should be updated regularly are the security ones: sudo, openssl/gnutils, nfs, nspr and your browser.

Yes, basically glibc and the toolchain.

No it is not dangerous to update the others. I skip them to save time and because they don't seem critical.

As far as gcc, it is also in the BLFS book. You can upgrade it from there at any time.

In post #6, hazel mentions a few more essential ones. Maybe you could add those to the toolchain. They are small and don't take up much time.

Thank you for replies!

Is there any recommended proceedure to update binutils?

Isn't .bashrc loaded after I enter startx? The "No mail" message appears before that.

No. Just cut and paste from chapter 6.16.1.

So, although it belongs to the toolchain it is an easy and safe update?

yes I think so. So far no problem with it.

Hi
To stop "mail check" at login
edit /etc/login.defs

from MAIL_CHECK_ENAB yes
MAIL_CHECK_ENAB no

Excellent, thank you!