Hi All,
im trying installing Linux 6.5 with kick-start file done by 3rd party , still get error ( Unable to read group information from repositories ,this is problem with the generation of your install tree

Sorry, but you need to read the "Question Guidelines" link in my posting signature. You've not provided near enough information for us to be able to help you, and your post itself is confusing (what do you mean by "with kick-start file done by 3rd party"??)

Further, if you're using Red Hat enterprise Linux 6.5 you need to be aware of a few things. First, that's OLD...if you're building new servers, load the latest 7.x Secondly, RHEL is not free, and if you're using it, you need to be paying for it...as such, you can contact Red Hat support for assistance with Kickstart. They also have extensive documentation on it:

https://access.redhat.com/documentat...art-howto.html

Hi sameh.dewdar and welcome to LQ.

This error may be part of the kick start or it may be a native RHEL error. My understanding is that you can obtain a kick start from a system administrator who is authorized to create RHEL kick start installations.

Therefore the first thing you should do is contact the system administrator who gave you this kick start, inform them of the error you are seeing, and let them assist you with this problem.

If you've obtained this kick start installation from an unsupported means, meaning that there's no one for you to contact, then there's little that persons here can offer you by way of support. This is because people will not know the details about how that kick start has been created, what it contains, and other details. Further, that particular error seems to always be a problem with how the install tree was generated for that kick start. Many times it means the kick start was done incorrectly.

1 members found this post helpful.

Hi rtmistler and TB0ne ,
manhy thanks for your reply and interest , i jut using customize kickstart from Avaya company to install Avaya voice system , below is the content kickstart , and my question is , which image from liunx shall i use if its not allowed to put red hat official one


install
cdrom
lang en_US.UTF-8
keyboard us
network --device=eth0 --bootproto=static --ip=x.x.x.x --netmask=255.255.255.0 --gateway=x.x.x.x --nameserver=x.x.x.x --hostname=x
rootpw --iscrypted $1$8HMFbnhF$1Rc36Q3MkV7LeAVN/Rh6O.
firewall --disabled
selinux --disabled
auth --useshadow --enablemd5
timezone --utc Asia/Duabi
bootloader --location=mbr
clearpart --all --initlabel
part /boot --fstype=ext3 --size=100
part / --fstype=ext3 --size=10000
part /var --fstype=ext3 --size=40000
part swap --recommended
part /calls --fstype=ext3 --size=1000 --grow
%packages
@ core
@ general-desktop
@ x11
@ base
@ basic-desktop
@ graphical-admin-tools
-cyrus-sasl-plain
-lftp
-redhat-lsb
-rsh
-pax
-stunnel
-wireless-tools
-tftp
-rp-pppoe
-openoffice-libs
-wvdial
-rdate
-cups-libs
-pdksh
-cups
-aspell
-dvd+rw-tools
-nano
-irda-utils
-sharutils
-sendmail
-setuptool
-jfsutils
-nc
-finger
-rdist
-mtr
-cyrus-sasl-gssapi
-jwhois
-redhat-config-network-tui
-ash
ntp
perl
postgresql-plpython
mkisofs
postgresql-server
libstdc++.i686
firefox
postgresql-docs
postgresql-plperl
tigervnc-server
postgresql-libs
glibc.i686
perl-libwww-perl
ppp
postgresql
%post
/bin/echo "#!/bin/bash" > /etc/init.d/ksonce
/bin/echo "# chkconfig: 35 20 80" >> /etc/init.d/ksonce
/bin/echo "# description: kickstart first boot" >> /etc/init.d/ksonce
/bin/echo "case "\$1" in" >> /etc/init.d/ksonce
/bin/echo " start)" >> /etc/init.d/ksonce
/bin/echo " su - postgres -c "initdb --encoding=UNICODE --auth='ident'"" >> /etc/init.d/ksonce
/bin/echo " sed -i '/^host/s/ident/md5/g' /var/lib/pgsql/data/pg_hba.conf" >> /etc/init.d/ksonce
/bin/echo " echo 'witness soft nproc 4096' >> /etc/security/limits.conf" >> /etc/init.d/ksonce
/bin/echo " sed -i '/^#vac/s/#vacuum_cost_delay = 0/vacuum_cost_delay = 10/g' /var/lib/pgsql/data/postgresql.conf" >> /etc/init.d/ksonce
/bin/echo " chkconfig --del ksonce" >> /etc/init.d/ksonce
/bin/echo "esac" >> /etc/init.d/ksonce
/bin/chmod 755 /etc/init.d/ksonce
/sbin/chkconfig --add ksonce
/sbin/chkconfig --level 345 postgresql on
/sbin/chkconfig --level 345 ntpd on
/sbin/chkconfig --del cups
/usr/sbin/useradd -u 501 witness
/usr/sbin/usermod -p '$1$PkfRAU51m2Z/omsTd5/' witness
/usr/sbin/usermod -G cdrom -a witness
/bin/chown witness.witness /calls
/bin/echo "restrict default nomodify notrap noquery" > /etc/ntp.conf
/bin/echo "restrict 127.0.0.1" >> /etc/ntp.conf
/bin/echo "server 10.1.1.1" >> /etc/ntp.conf
/bin/echo "driftfile /var/lib/ntp/drift" >> /etc/ntp.conf
/bin/echo "broadcastdelay 0.008" >> /etc/ntp.conf
/bin/echo "x.x.x.x" > /etc/ntp/step-tickers
/bin/echo "Created 11.1" > /etc/ksversion

Are you putting this onto a custom platform provided by Avaya? If so, you should talk to Avaya.

i guess that would be centos then?
http://centos.org/

Why is it so hard to pay a fairly small amount of money to Red Hat, and use it? Especially since this is for your business??? And since Avaya provided things, it makes sense to use what they provided, and stay in a supported environment.

Pay for your RHEL subscription; enjoy having a stable server with tech support you can call if needed, and having Avaya still support you, since you're running what they recommend.

1 members found this post helpful.

I wholeheartedly agree with TB0ne. This is less about fair compensation to the manufacturer, however that entirely should be considered. But it is also about the technology. Whether you are using this for business or home, you are using a phone system which has been designed to be a phone system.

1. If you want to use their box as a general purpose computer and think it'll be cool to run Linux on it. Have at it and use anything. Best of luck, there may be custom hardware on there that any general form of Linux will not understand. Better instead to just use a normal computer.
2. If you are trying to use this product as designed and as intended, then exactly what TB0ne is saying.

Not sure this would be a good idea. Avaya is a communications company and the device is likely an Avaya VoIP server of some sort. To me this is an embedded device and likely has a custom form of Linux. You can't just "grab" something and march ahead. Not saying that another person won't have the expertise, however sometimes that expertise is extremely difficult to come by. For instance, the developers working for Avaya who may have customized the Linux for that box, may have compiled the kernel with very certain flags, may have chosen to make drivers internal versus modules, may have written custom drivers for the box, and may have a custom derived bootloader which probably was uboot, or grub2, but nothing saying they didn't edit it. How many times have I customized systems to make them boot fast, contain the correct drivers, and so forth. This all having been done with the design files for the PCB's and collaboration with the firmware team who wrote the code for the real time hardware.

If this box is purely a general server appliance and nothing more special than an x86 architecture with a few added well known parts like standard hard drives and standard serial ports, etc, then fine. But seems a big risk.

1 members found this post helpful.