On 1/5/2020 5:52 AM, Cindy Sue Causey wrote:
On 1/4/20, Alan Feuerbacher <[email protected]> wrote:
On 1/4/2020 12:49 PM, Xi Ruoyao wrote:
On 2020-01-04 10:21 -0700，Alan Feuerbacher wrote:
I've run into a problem in building Version 20200101-systemd Section
6.9. Glibc-2.30.
After several repetitions of compiling, I've found that if I run
"make check", the various localedef invocations that follow, like
"localedef -i cs_CZ -f UTF-8 cs_CZ.UTF-8", sometimes fail with a message
like
"cannot create temporary file: /tools/lib/locale/locale-archive.J6uC5g:
No such file or directory".
However, if I skip "make check", all of the "localedef" commands
run ok.
That's abnormal. NEVER continue blindly with this kind of phenomena.
That may
be a bomb and may blow up your entire system.
Can you please expand on what I did wrong? I don't really understand
what you mean by "continue blindly".
While you're waiting for the reply, my brain's interpretation is that
it is a well-meaning version of "STOP! DO NOT PASS *GO*! DO NOT
COLLECT $200!" In a good way, I mean... :)
Ok, I understand.
This brings up another issue: when should someone playing with LFS try
to figure the problem out for herself, as opposed to contacting this
list? I usually do the former as far as I know how, until I get stuck.
Sometimes I don't know enough to say "I'm stuck."
This reminds me of the skit on Saturday Night Live from 20+ years ago
where Jimmy Fallon played "Nick Burns the Computer Guy" (
https://www.nbc.com/saturday-night-live/video/nick-burns-your-companys-computer-guy/n11524
). Anyone who's worked in a corporate environment recognizes the
character -- testy and always complaining about getting calls from other
employees to do his job -- help solve their computer problems. In real
life it's not so funny.
Thank goodness that most of the people replying to this lfs-support list
are not like the SNL guy. They're generally helpful and kind, even to
people like me who sometimes have brain glitches and ask 'stupid'
questions.
Their advisement further a little bit sounds like whatever's going on
in the error maybe could potentially affect your ENTIRE system
*including your very important, very necessary HOST operating system*.
That would be a reason for advising that everything come to a complete
stop until you can figure out what's going on.
This is phenomenally coincidental to something I JUST seconds ago
typed over at Debian-User. Why they might say STOP NOW, DON'T TOUCH
*ANYTHING* until we figure this out is because maybe the error's
trying to say that something may be accidentally linked directly into
your *HOST* system, not the practice play session.
If that is in any way the case, if you were to do something like start
deleting everything in your play session, it's possible that...
maybe... a "hard link" is pointing at your HOST session. If that is
what's going on AND you were to start deleting your PLAY session to go
back to Chapter 1 or something, that accidentally created wrong *hard
link* WILL delete your *HOST* system files.
Boy does that ring true! Due to various other commitments I hadn't
turned on my Fedora host system for more than a year. So when I decided
to start playing with LFS again a couple of weeks ago, and turned the
system on, Fedora want to update to version 31. I let it rip, and
something went terribly wrong. After turning off power the system
wouldn't boot, so I knew I had to reinstall Fedora. Now, the hard drive
containing the crashed Fedora contains many files that need to be saved,
so I moved the disk to slot three, installed a new disk in slot one, and
installed Fedora to the new disk. Then I mounted the crashed disk and
recovered the files. I had to do all this because, for unknown reasons,
trying to reinstall Fedora on the messed up disk would not allow me to
retain parts of the filesystem such as /home-- the upgrade insisted on
reformatting the entire disk.
After jumping through those hoops I resumed trying to install LFS on
disk number two. After going through the process several times and
messing up several times, I got solidly stuck and decided to remove some
directories on the LFS disk, but I seem to have suffered an extreme
brain glitch and removed several critical directories on the Fedora
disk, like /boot and /usr. This was late at night, after a long day. Of
course, Fedora quit working and I had to reinstall it all over again. I
learned some valuable lessons.
I'm speaking firsthand from having created exactly that situation
during my earliest Debian debootstrap efforts. Actually, I got a HARSH
reminder AGAIN in later debootstraps when I deleted a "mount -B link
that was pointed at thousands of package archive files.
What does "debootstrap" mean?
I looked at the man page for mount -- it's almost 1600 pages!
I used to "soft link" a symlink to those same package archive files
until debootstrap failed for that very reason so I learned to go the
"mount --bind" route. THEN I learned the very hard way that you can
harmlessly delete a "soft link" but a mounted "mount -B" link will
wipe out that hard link AND the directory it's feeding from....
I don't know enough about links and mounts to understand all this.
Heartbreaking doesn't begin to cover learning something like that by
being the one who did it firsthand..... A healthy, ACTIVE backup
system is a User's best friend in these cases.....
Cindy :)
What do you use for backup on Linux? For many years, on my Windows
computer, I've had two extra backup disks installed, and use Acronis to
do incremental backups to one of those disks every day. Every couple of
weeks I switch the backup to the other disk, so I have some redundancy.
Alan
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
