[K12OSN] K12Linux EL6 Setup Instructions

[Dean Jones]

I suggest using these instructions:
https://fedorahosted.org/k12linux/wiki/InstallGuide

On Mon, Oct 24, 2011 at 5:26 AM, Julius Szelagiewicz <julius at turtle.com> wrote:
> Dear Folks,
>  I'm trying to set up a CentOS 6 server and I've followed the beta
> instrunctions faithfully (substituting CentOS 6 for SL 6). The software
> appears to load happily, but there is no /tftpdir created and /opt/ltsp
> stays empty. Any ideas?
> Julius
>
>
>
>> Setup LTSP Server on Scientific Linux 6
>> =======================================
>> 1. Install Scientific Linux 6 with GNOME desktop.
>>
>> 2. http://mplug.org/~k12linux/rpm/el6/
>> Install ltsp-server, ltspfs and nbd from here, choose i686 or x86_64
>> matching your server arch.
>>
>> 3. Grab http://togami.com/~warren/temp/ltsp-i386.ks and replace the file
>> at /etc/ltsp/kickstart/Fedora/el6/ltsp-i386.ks.  Keep in mind that
>> future ltsp-server RPM upgrades will wipe out your changed ltsp-i386.ks,
>> so you will need to replace it again until the beta goes public.
>>
>> 4. https://fedorahosted.org/k12linux/wiki/InstallGuide
>> Follow the directions here but stop after you have disabled the iptables
>> firewall.
>>
>> 5. Run /usr/bin/ltsp-server-tweaks
>> https://fedorahosted.org/k12linux/wiki/Devel/ltsp-server-tweaks
>> See here for important details.
>>
>> Network Setup with K12Linux EL6
>> ===============================
>> The old Fedora instructions to make service network and NetworkManager
>> co-exist doesn't work because system-config-network lacks a GUI
>> interface in EL6.  Thus we need to manually configure attaching a
>> dedicated ethernet device to the bridge.
>>
>> Requirements:
>> * TWO network interfaces, either two ethernet, or one wifi and one
>> ethernet.
>> * One of the ethernet interfaces must be dedicated to serving DHCP and
>> booting thin clients on an isolated network segment.  This interface has
>> NM_CONTROLLED=no to ensure that NetworkManager wont interfere with it.
>> * The other interface (ethernet or wifi) must be the route to the
>> Internet.  This interface is managed by NetworkManager.  NetworkManager
>> in EL6 is a lot better than earlier versions.  You can define interfaces
>> as static and always available, so they are configured at bootup without
>> a user logging into the desktop.
>>
>> 1. Run "ifconfig" and look for the unused ethernet interface, it should
>> look something like the below.  Write down the ethX device name and MAC
>> address as you will need this in the following steps.
>>
>> eth0      Link encap:Ethernet  HWaddr 00:15:58:7E:24:66
>>            inet6 addr: fe80::215:58ff:fe7e:5470/64 Scope:Link
>>            UP BROADCAST MULTICAST  MTU:1500  Metric:1
>>            RX packets:2071831 errors:0 dropped:0 overruns:0 frame:0
>>            TX packets:2769292 errors:0 dropped:0 overruns:0 carrier:0
>>            collisions:0 txqueuelen:100
>>            RX bytes:399370077 (380.8 MiB)  TX bytes:2658000993 (2.4 GiB)
>>            Memory:ee000000-ee020000
>>
>> 2. cd /etc/sysconfig/network-scripts
>>
>> 3. Look at ifcfg-* files.  Is there a ifcfg-Auto_ethX matching the
>> device name of the interface you chose above?  If so, rename it to
>> ifcfg-ethX.
>>
>> 4. Replace the contents of ifcfg-ethX with something similar to below,
>> replacing the ethX device name and MAC address with your own.
>>
>> HWADDR=00:15:58:7E:24:66
>> TYPE=Ethernet
>> BOOTPROTO=none
>> IPV4_FAILURE_FATAL=no
>> IPV6INIT=no
>> NAME="eth0"
>> ONBOOT=yes
>> NM_CONTROLLED=no
>> BRIDGE=ltspbr0
>>
>> 5. service network restart; chkconfig network on
>>
>> 6. brctl show
>> This command should show that your chosen ethX device is added to the
>> ltspbr0 bridge.
>>
>> 7. At this point you should be able to plug in and boot a PXE thin
>> client on that Ethernet interface.
>>
>> Other New K12Linux EL6 Instructions
>> ===================================
>> https://fedorahosted.org/k12linux/wiki/VirtualPXEClient
>> Virtual Machine PXE Client
>> https://fedorahosted.org/k12linux/wiki/LocalAppsSupport
>> Learn how to install and run Firefox as a Local App.  Requires maybe 1GB
>> RAM on the client, maybe 512MB RAM after I later build a new client
>> kernel.
>>
>> Warren Togami
>> warren at togami.com
>>
>
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
>