Dr.-Ing. Edgar Alwers wrote:
Hi Bruce,
may I contribute with some remarks according to my actual experiences ?
1.) Until xorg is installed and running, I have to use "lynx" to download and
compile the programs. There are however difficulties with this. Lynx does not
work with "https", so I have to download this files on another box and
transfer to the new one with the help of rsync. Could "https" be avoided ?
All files are located at ftp://ftp.osuosl.org/pub/blfs/
Also, you can build most packages in chroot including Xorg. What I like
to do is build ssh and wget in chroot and then ssh into the system from a
fully developed system.
2.) the addresses given for all xorg programs,
"ftp.x.org/pub/individual/proto" ( this one as an example ) does'nt work for
me. Lynx cannot find the files. I had to use the systemd book addresses:
"xorg.freedesktop.org/archive/individual/proto"
Sounds like a DNS problem.
$ host ftp.x.org
ftp.x.org is an alias for annarchy.freedesktop.org.
annarchy.freedesktop.org has address 131.252.210.176
annarchy.freedesktop.org mail is handled by 10 gabe.freedesktop.org.
$ host xorg.freedesktop.org
xorg.freedesktop.org is an alias for annarchy.freedesktop.org.
annarchy.freedesktop.org has address 131.252.210.176
annarchy.freedesktop.org mail is handled by 10 gabe.freedesktop.org.
3.) The installation e.g. xorg protocoll headers etc. as user with the help of
"as_root" did not function for me, as sudo asked everytime for a password and
could not perform the task. sudo is in my opinion very nasty. To allow the
system administrator to execute programs without typing passwords, you gave an
example how to change sudoers. However, sudoers cannot be changed with normal
editors like vi, you have to use "visudo". I didnt manage it. The visudo
instructions are in my humble opinion terrible. I do not know, if it would be
possible to add the example ussage in BLFS with the corresponding "visudo"
commands.
Try su -c "vi /etc/sudoers". You have to save as :wq! because the
permissions are 0400.
What visudo does is call the EDITOR (the default is not vi, so it is
useful to use 'EDITOR=vi visudo' or add 'export EDITOR=vi' to
~/.bash_profile) and does a validity check when the editor exits. It does
that to prevent syntax errors in the /etc/sudoers file.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
