I couldn't install any other thin client image than i386 and x86_64 (CentOS)

[Radek Bursztynowski]

Hello,

I try to install any other thin client image then i386 and x86_64 with
no result.

ltsp-build-client --list

sows:

epel-5-i386
epel-5-ppc
epel-5-x86_64
epel-6-i386
epel-6-ppc64
epel-6-x86_64
epel-7-ppc64
epel-7-x86_64
fedora-19-armhfp
fedora-19-i386
fedora-19-ppc64
fedora-19-ppc
fedora-19-s390
fedora-19-s390x
fedora-19-x86_64
fedora-20-armhfp
fedora-20-i386
fedora-20-ppc64
fedora-20-ppc
fedora-20-s390
fedora-20-s390x
fedora-20-x86_64
fedora-5-i386-epel
fedora-5-ppc-epel
fedora-5-x86_64-epel
fedora-devel-i386
fedora-devel-ppc64
fedora-devel-ppc
fedora-devel-x86_64
fedora-rawhide-aarch64
fedora-rawhide-armhfp
fedora-rawhide-i386
fedora-rawhide-ppc64
fedora-rawhide-ppc
fedora-rawhide-s390
fedora-rawhide-s390x
fedora-rawhide-sparc
fedora-rawhide-x86_64

then I try:

ltsp-build-client --release fedora-19-i386
--chroot /opt/ltsp/fedora-19-i386

or

ltsp-build-client --release fedora-6-i386
--chroot /opt/ltsp/fedora-6-i386

ltsb-build-client start an I can see installation progress up to 50% and
this script breaks his job. I can
see /var/lib/tftpboot/ltsp/fedora-19-i386 and /opt/ltsp/fedora-19-i386
directories. I cane see the bellow message (it is free translation from
Polish):

mv: `/opt/ltsp/mock/epel-6-i386/root' canot be moved to
`/opt/ltsp//opt/ltsp/epel-6-i386': there is no this file or directory
cp: it isn't possible to execute stat on
`/opt/ltsp//opt/ltsp/epel-6-i386/etc/skel/.bash*': there is no thi file
or directory.
LTSP client not installed.

ltsp-build-client --release fedora-20-i386
--chroot /opt/ltsp/fedora-20-i386

ltsp-build-client starts and I can see installation progres up to 20%
and this script suspends (there is no any progress within all night).

Similiar situation is with epel-5-i386
ltsp-build-client --release epel-5-i386 --chroot /opt/ltsp/epel-5-i386

Could anybody advice me how to fix this problem?

Best regards,
Radek

[Barry R Cisna]

Radek,

Before you start the chroot or ltsp-build-client command do the
following in terminal

su -
(rootpassword)

then,,your ltsp-build-client command as you have it.

do NOT use sudo

Barry

[Radek Bursztynowski]

Barry,

Thanks a lot for help.
I use ltsp-build-client logged in as a root only.
My description of my problem doesn't concern sudo truck.

Best regards,
Radek

---

Post by Barry R Cisna
Radek,
Before you start the chroot or ltsp-build-client command do the
following in terminal
su -
(rootpassword)
then,,your ltsp-build-client command as you have it.
do NOT use sudo
Barry
_______________________________________________
K12OSN mailing list
https://www.redhat.com/mailman/listinfo/k12osn
For more info see <http://www.k12os.org>