On Mon, May 25, 2015 at 05:24:45PM -0500, Daryl Voss wrote:
> I guess I should have introduced myself before jumping in with my problem.
> 
Hi Daryl,

for this list, not necessary - but context about the person with the
problem is always welcome.

> My name's Daryl Voss. I've dabbled in Linux sporadically over the last 10-15 
> years. I'm not taking it more seriously and trying to learn as much as I can. 
> I'm taking the free Introduction to Linux (LFS101x.2 from the Linux 
> Foundation) course on edX.org and decided to accompany that with going 
> through the LFS book.
> 

Can you limit your line length to something shorter in future posts,
please ?  Something around 70 characters usually works well (that
is, it still fits in "old" 80 character lines when quoted in several
levels of reply with '> > > > ' on the front of each line.

It also makes it much easier for people who reply to only quote the
part of a paragraph which is relevant.  Thanks.

> I've configured and run several VPSs and machines in my own labs . I have an 
> ownCloud VPS I use almost daily that I setup from a minimal Linux image. I 
> used a Debian box as a bridge and console server to my Cisco study lab with a 
> couple of quad port serial cards.
> 
> I have a good base knowledge of Linux but it has been mostly learn how to do 
> X, forget most of the commands, learn how to do Y by re-researching most of 
> what I did for X, forget most of the commands again. 
> 

Keeping notes (in plain text, so you can grep them), and backing
them up, works for me - I keep mine on nfs, but using ssh to get to
the machine with the notes also works (obviously, not a problem for
people with only one machine).
> I'm trying to learn in a more organized way now and hopefully will find some 
> work relating to Linux so I can use it daily and grow my skill-set.
> 
> Thanks and I hope to contribute as much or more than I request help
> 
> Daryl Voss

For your problem in the other post, google [ /mnt/lfs/tools/bin
cannot find crt1.o ] suggested that your /tools symlink on the host
is incorrect.  On the host 'ls -l /' should show /tools pointing to
/mnt/lfs/tools.

Another search result (stackoverflow - probably not the best place to
ask about LFS, because most of the people who might reply don't
understand how we bring up a new system) the poster eventually
claimed he'd fixed it and the problem was because he had not used
'sudo make install' : that was clearly the wrong answer, but /mnt/lfs
/mnt/lfs/sources if that is where you build (it's what the books use -
I'm eccentric and make that an nfs mount, so I don't build there) and
/mnt/lfs/tools need to be writable by the lfs user.

If either of those match your situation, best to start again and fix
the problem.  If they don't, perhaps google knows of other problems
(I don't recall seeing this particular problem on our lists in the
last few months, but at the moment what happened a month ago seems a
very long time ago - too many simultaneous and unrelated problems :).

ĸen
-- 

Nanny Ogg usually went to bed early. After all, she was an old lady.
Sometimes she went to bed as early as 6 a.m.
-- 
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

Reply via email to