XS Installing Software 0.6: Difference between revisions

From OLPC
Jump to navigation Jump to search
mNo edit summary
(remove latest releases table, it does not serve any purpose here and is a distraction)
 
(160 intermediate revisions by 43 users not shown)
Line 1: Line 1:
{{translations}}
{{OLPC}}
{{OLPC}}
[[Category:Software]]
[[Category:Software]]
Line 4: Line 5:
[[Category:SchoolServer]]
[[Category:SchoolServer]]


This page describes how to obtain a copy of the [[XS_Server_Software|XS school server software]], load it onto media, and install it onto a system. A more [[XS Software Repositories|complete description of the software repositories]] is available.
This page describes how to obtain a copy of the [[XS_Server_Software|XS school server software]], load it onto media, and install it onto a system.


This page covers '''XS 0.6 and newer'''. For older releases, see
=Downloading the System Image=


* [[XS_Installing_Software_0.5]]
* [[XS_Installing_Software_0.4]]

=Downloading the System Image=
You can obtain the latest image from [http://xs-dev.laptop.org/xs/ http://xs-dev.laptop.org/xs/]:
You can obtain the latest image from [http://xs-dev.laptop.org/xs/ http://xs-dev.laptop.org/xs/]:


wget http://xs-dev.laptop.org/xs/OLPC_XS_LATEST.iso
wget http://dev.laptop.org/xs/OLPC-School-Server-0.6-i386.iso


This can be copied onto a CD or DVD using your favorite software.
This can be copied onto a '''CD''' or '''DVD''' using your favorite software.


You can also [[XS_Techniques_and_Configuration#Installing_from_USB|install it from USB]] (warning: unsupported!)
It may also be copied onto a USB key, using the <tt>livecd-tools</tt> provided by Fedora 7:


=Installing the Software=
livecd-iso-to-disk OLPC_XS_LATEST.iso /dev/sdb1


'''Please read the [[XS Release Notes|release notes]] for the version you are installing.'''
where <tt>/dev/sdb1</tt> represents the USB key being copied onto.


The install from a '''CD''' or '''USB''' storage device will eventually be automatic upon booting. While the install is currently mostly automated (not interactive), it is not performed automatically upon boot.
=Installing the Software=


# Boot from the USB device or CD-ROM.
The install from a CD or USB key will eventually be automatic upon booting. While the install is currently mostly automated (not interactive), it is not performed automatically upon boot.
# Press enter to start the graphical boot menu.
# Select "Install using kickstart" at the initial boot screen.
## "Install using kickstart" is the last menu item. Do not use the other "Install" options on this menu as they only install Fedora 9 without the olpc scripts. The Anaconda installer will install around 546 packages. If it announces it is installing 407 packages, the olpc scripts are missing. Start again.
# '''Note: the default graphical installer can be unstable at times. You can press tab and add 'text' at the end of the line to request the text-based installer.'''
# Anaconda (the Fedora installer) takes over and you will be prompted for the standard questions - these are preset to the correct defaults for the School Server configuration. You will want to set keyboard type, the time zone, and a root password for your specific system.
## If you are planning to deploy to a large number of XSs, it is easy to modify the Kickstart file to have the whole process run automatically.
# When prompted to add specific packages, just leave the default and click next.
# When it has finished installing, you will be prompted to reboot. Remove the CD-ROM or USB device after power-down, but before the boot process begins.


You should now have a School Server! It needs initial configuration before it starts providing services to the laptops.
# Boot from the USB Key or CD-ROM -- Getting an older system to boot from a USB key can be difficult, but most will do it.
# Select "Run from Image" at the initial boot screen.
# When it has finished booting, login as root (no password is required) and type:
./olpc-install
# You will be prompted for the root password
# When it has finished installing, you will need to reboot. Remove the CD-ROM or USB key after power-down, but before the boot process begins.


== Automating the Install ==
You should now have a machine which somewhat resembles a school server.


If you want to install XS software using a cobbler-based Installation Server, please see [[XS_Install_Server]].
== Installing additional software ==


== Installing on an XO ==
If you wish to install packages that aren't part of the default school server distribution, you should first try using <tt>yum</tt>. The ''stable'' and ''testing'' school server repositories include all packages included in Fedora, even if they aren't installed by default. For third party software, such as Moodle, you should follow their installation procedure for Fedora 7


If you are wanting to run the XS software on an XO, please see [[XS-on-XO]].
=Release Notes=


= Initial Configuration =
==OLPC_XS_137==
This release supports hot-plug of the Active Antennas (unplugging and plugging while the server is running.) It also provides the latest firmware and drivers for the Active Antennas, fixing a number of stability problems and avoiding a problem where the mesh interacted badly with conventional 802.11b/g access points running a Broadcom chipset (such as the Linksys WRT54G).


== Setting hostname and domain ==
===Known Problems===
Login as root, with whatever password you assigned during installation.
* Plenty of missing functionality.


Right after installation, you '''must'''
===Upgrading from earlier releases===
* Set the server domain name (the hostname is always 'schoolserver') using:
/etc/sysconfig/olpc-scripts/domain_config example.org
* Reboot the machine so the hostname change can take effect:
reboot
* Installation and initial configuration are complete!


== What next? ==
This has been tested and should work fine, with one intentional exception:


'''Important: Register an XO and visit the Schoolserver'''. You should do this with the XO of a teacher or school principal, as the first XO to visit the Schoolserver will have the "course creator" role. [[XS Techniques and Configuration#Moodle|More about Moodle]]
To avoid disturbing any manual configuration of the server network interfaces, hot-plug of the Active Antennas will not be supported on an upgraded machine until <tt>/etc/sysconfig/olpc-scripts/network-config.py</tt> is run manually. After running this script, any manually configured network scripts (in <tt>/etc/sysconfig/network-scripts/</tt>) will be saved with a <tt>.bak</tt> suffix.
All the topics below are discussed in [[XS Techniques and Configuration]]


* Setting a static IP address for eth0, or using something other than eth0 as your WAN port.
==OLPC_XS_128==
* Using specific DNS servers (from your ISP, or from OpenDNS -recommended!)
This release has the registration server required for Trial3, as well as a fix to the inittab script which caused problems in India.
* You may want to enable the transparent HTTP proxy.
* and more...


=Network Configuration Notes=
==OLPC_XS_127==
A bug fix release, due to our lame QA department not testing build 126 on a server with a single wired interface before release. This fixes the network configuration problems in 125 and 126 on servers with a single wired interface.


The default server setup is to connect to the Internet on the '''first wired ethernet network interface''', using IPv4 DHCP. Laptops connect to the server over Access Points (APs) connected to the '''second wired ethernet network interface''' or via the wireless mesh using one or more [[Active Antenna]], connected through USB interfaces.
==OLPC_XS_126==
A bug fix release. This fixes the mesh channel assignment and network configuration problems in 125


If your XS has 2 network interfaces and you would like to reverse their (WAN, LAN) roles, or if you only have one network interface and would like to swap it's role, you can use the xs-swapnics utility. If you get your WAN via some other interface (e.g., ppp0) then you will want to see the [[XS_Techniques_and_Configuration#Using_a_different_WAN_connection|recipes for WAN connections]].
==OLPC_XS_125==
This release has basic network functionality. It supports laptops on the mesh.


IPv6 is not enabled by default and not needed -- to enable external IPv6 you will have to [[XS_Configuration_Management#IPv6|configure the global address of the machine and setup an IPv6 tunnel]].
It does NOT autoinstall automatically. You will need to login as root (no password), then run <tt>/root/olpc-install</tt>. You will be prompted for a root password, otherwise the installation is automatic.


The XS runs a fully-fledged DNS server internally, therefore there is no need to enter the DNS servers from your ISP into the configuration. If you do want the XS to use specific DNSs, see the instructions on [[XS_Techniques_and_Configuration#Use_ISP-provided_DNS_servers|using ISP-provided DNS servers]]
Missing:
* Registration
* Web services
* Presence service
* A configuration interface
* Lots more...


== Access Points ==
Known Problems:
* /etc/named.conf isn't being installed correctly from the xs-config RPM. The fix is:
cp /etc/named.conf.olpcnew /etc/named.conf
* Hotplug of the mesh interfaces doesn't trigger a restart of the olpc-mesh-config, which is needed for the mesh to work.
* SELinux is left in permissive mode, instead of completely disabled. Edit <tt>/etc/selinux/config</tt> and set <tt>SELINUX=disabled</tt>
* The channel on the mesh interface isn't being set correctly. This causes problems with XO builds later than 542. Set the channel manually using iwconfig for now. Fixed in build 126.
* The network configuration script could fail and assign a mesh interface as the WAN. Fixed in build 127.
* On machines with no serial port, there might be a problem resulting in an error message on the console: <tt>INIT : Id "s0" respawning too fast : disabled for 5 minutes</tt>. This is fixed in xs-config v0.1.7-4, (not currently in any live CD build).


[[Image:XS_Usage_APNormal.png|600px]]
The most common problem with the mesh is due to a hardware problem with the Marvell wireless modules used in the Active Antennas. They frequently do not reset properly, and need to be power cycled. The symptom is that you will get a message: "libertas: Unable to init firmware" on the console, and <tt>ifconfig</tt> won't show a mesh interface. A reboot will not fix the situation, you need to actually power cycle the USB adapter by unplugging it and plugging it back in.


Most access points are compatible with the XO. For a list of ones which have been shown to work see [[Wireless Access Point Compatibility]]. Unless a single access point is being used (not recommended for more than forty to fifty laptops), a network switch of some sort will also be needed.
=Manual Configuration=
There are some site-specific configuration which will need to be manually administered until we have a configuration interface in place. Specifically, these are setting up the WAN interface and assigning a domain name.


Make sure your AP is configured to act as an Access Point, with no added features or smarts. The AP should not be a DHCP server and should not act as a router.
==WAN Connection==


Some tips on configuring APs at [[XS_Techniques_and_Configuration]].
The file which configures this interface is <tt>/etc/sysconfig/network-scripts/ifcfg-eth0</tt>. The current default is to use DHCP to assign an IP address to this interface, and obtain DNS server info.


== Active Antennae ==
==Domain Name==
'''Important note: Active Antennae is not supported or available from OLPC at this time'''


If you have active antenna(e) to use, simply plug them in and reboot the XS. It will detect them and allocate them to mshbond0, mshbond1 and mshbond2. It should just work and XOs will see "School server mesh" when they connect to the mesh served by the XS. You may need to manually allocate different frequencies per antenna.
This name currently set to <tt>random.xs.laptop.org</tt> is unfortunately embedded in a number of files:

/etc/named.conf
=More configuration options=
/var/named/school.zone.inaddr.db

/var/named/school.zone.16.inaddr.db
For more information on keeping your XS up to date, Internet content filtering, alternative networking/routing setups, and a lot of other advanced configuration topics see [[XS_Techniques_and_Configuration]].
/var/named/school.zone.32.inaddr.db

/var/named/school.zone.48.inaddr.db
=Upgrading=

==Upgrade from XS 0.5 or later==

With the full ISO:
* The process is similar to a new (anaconda based) installation. Download the iso, and boot it...
* In the menu shown right after booting, you choose one of the 'Install or upgrade an existing system'.
* At the 'Install new or upgrade' screen choose upgrade.
* Reboot, and complete the 'steps after upgrade'.

With <code>yum</code>:

* Clean yum's caches
yum clean all
* Swith to the new repositories
rpm -Uvh http://xs-dev.laptop.org/xsrepos/stable/olpc/xs-0.6/i386/xs-release-9-0.4.15.2.ga69303f.noarch.rpm
* Check that the new repositories have not been installed as "rpmnew":
ls /etc/yum.repos.d/*rpmnew
* Run the install!
yum update
* Reboot, and complete the 'steps after upgrade'.

Steps after upgrade:
* Re-run the /etc/sysconfig/olpc-scripts/domain_config script with the appropriate domain name for the machine.
* Ensure the right Postgres is set to run
chkconfig --level 345 postgresql off
chkconfig --add pgsql-xs

==Upgrade from XS 0.4 or earlier==

If you are upgrading from XS 0.4 or earlier, the process is similar to a new installation, with some minor changes. In the menu shown right after booting, you should choose one of the 'Install or upgrade an existing system' options, press the Tab key, and add 'upgradeany' to the boot configuration line. After adding that line, press enter twice.

With this extra option, Anaconda will recognise the old installation and will offer to upgrade.

Steps after upgrade:
* Re-run the /etc/sysconfig/olpc-scripts/domain_config script with the appropriate domain name for the machine.
* Ensure the right Postgres is set to run
chkconfig --level 345 postgresql off
chkconfig --add pgsql-xs

Notes:
* The new OS may detect your network cards differently -- the roles of WAN and LAN cards may end up swapped from what they were under 0.4. If that happens, use the xs-swapnics script and reboot.

= See also =
* [[XS Techniques and Configuration]]
* [[XS Troubleshooting]]

[[Category:SchoolServer]]

Latest revision as of 21:56, 5 August 2013

  english | español | Copy "{{subst:requesttranslation}}" to 한국어 HowTo [ID# 290708]  +/-  


  This page is monitored by the OLPC team.

This page describes how to obtain a copy of the XS school server software, load it onto media, and install it onto a system.

This page covers XS 0.6 and newer. For older releases, see

Downloading the System Image

You can obtain the latest image from http://xs-dev.laptop.org/xs/: 

wget http://dev.laptop.org/xs/OLPC-School-Server-0.6-i386.iso

This can be copied onto a CD or DVD using your favorite software.

You can also install it from USB (warning: unsupported!)

Installing the Software

Please read the release notes for the version you are installing.

The install from a CD or USB storage device will eventually be automatic upon booting. While the install is currently mostly automated (not interactive), it is not performed automatically upon boot.

  1. Boot from the USB device or CD-ROM.
  2. Press enter to start the graphical boot menu.
  3. Select "Install using kickstart" at the initial boot screen.
    1. "Install using kickstart" is the last menu item. Do not use the other "Install" options on this menu as they only install Fedora 9 without the olpc scripts. The Anaconda installer will install around 546 packages. If it announces it is installing 407 packages, the olpc scripts are missing. Start again.
  4. Note: the default graphical installer can be unstable at times. You can press tab and add 'text' at the end of the line to request the text-based installer.
  5. Anaconda (the Fedora installer) takes over and you will be prompted for the standard questions - these are preset to the correct defaults for the School Server configuration. You will want to set keyboard type, the time zone, and a root password for your specific system.
    1. If you are planning to deploy to a large number of XSs, it is easy to modify the Kickstart file to have the whole process run automatically.
  6. When prompted to add specific packages, just leave the default and click next.
  7. When it has finished installing, you will be prompted to reboot. Remove the CD-ROM or USB device after power-down, but before the boot process begins.

You should now have a School Server! It needs initial configuration before it starts providing services to the laptops.

Automating the Install

If you want to install XS software using a cobbler-based Installation Server, please see XS_Install_Server.

Installing on an XO

If you are wanting to run the XS software on an XO, please see XS-on-XO.

Initial Configuration

Setting hostname and domain

Login as root, with whatever password you assigned during installation.

Right after installation, you must

  • Set the server domain name (the hostname is always 'schoolserver') using:
/etc/sysconfig/olpc-scripts/domain_config example.org
  • Reboot the machine so the hostname change can take effect:
reboot
  • Installation and initial configuration are complete!

What next?

Important: Register an XO and visit the Schoolserver. You should do this with the XO of a teacher or school principal, as the first XO to visit the Schoolserver will have the "course creator" role. More about Moodle

All the topics below are discussed in XS Techniques and Configuration

  • Setting a static IP address for eth0, or using something other than eth0 as your WAN port.
  • Using specific DNS servers (from your ISP, or from OpenDNS -recommended!)
  • You may want to enable the transparent HTTP proxy.
  • and more...

Network Configuration Notes

The default server setup is to connect to the Internet on the first wired ethernet network interface, using IPv4 DHCP. Laptops connect to the server over Access Points (APs) connected to the second wired ethernet network interface or via the wireless mesh using one or more Active Antenna, connected through USB interfaces.

If your XS has 2 network interfaces and you would like to reverse their (WAN, LAN) roles, or if you only have one network interface and would like to swap it's role, you can use the xs-swapnics utility. If you get your WAN via some other interface (e.g., ppp0) then you will want to see the recipes for WAN connections.

IPv6 is not enabled by default and not needed -- to enable external IPv6 you will have to configure the global address of the machine and setup an IPv6 tunnel.

The XS runs a fully-fledged DNS server internally, therefore there is no need to enter the DNS servers from your ISP into the configuration. If you do want the XS to use specific DNSs, see the instructions on using ISP-provided DNS servers

Access Points

XS Usage APNormal.png

Most access points are compatible with the XO. For a list of ones which have been shown to work see Wireless Access Point Compatibility. Unless a single access point is being used (not recommended for more than forty to fifty laptops), a network switch of some sort will also be needed.

Make sure your AP is configured to act as an Access Point, with no added features or smarts. The AP should not be a DHCP server and should not act as a router.

Some tips on configuring APs at XS_Techniques_and_Configuration.

Active Antennae

Important note: Active Antennae is not supported or available from OLPC at this time

If you have active antenna(e) to use, simply plug them in and reboot the XS. It will detect them and allocate them to mshbond0, mshbond1 and mshbond2. It should just work and XOs will see "School server mesh" when they connect to the mesh served by the XS. You may need to manually allocate different frequencies per antenna.

More configuration options

For more information on keeping your XS up to date, Internet content filtering, alternative networking/routing setups, and a lot of other advanced configuration topics see XS_Techniques_and_Configuration.

Upgrading

Upgrade from XS 0.5 or later

With the full ISO:

  • The process is similar to a new (anaconda based) installation. Download the iso, and boot it...
  • In the menu shown right after booting, you choose one of the 'Install or upgrade an existing system'.
  • At the 'Install new or upgrade' screen choose upgrade.
  • Reboot, and complete the 'steps after upgrade'.

With yum:

  • Clean yum's caches
 yum clean all
  • Swith to the new repositories
 rpm -Uvh http://xs-dev.laptop.org/xsrepos/stable/olpc/xs-0.6/i386/xs-release-9-0.4.15.2.ga69303f.noarch.rpm
  • Check that the new repositories have not been installed as "rpmnew":
 ls /etc/yum.repos.d/*rpmnew
  • Run the install!
 yum update
  • Reboot, and complete the 'steps after upgrade'.

Steps after upgrade:

  • Re-run the /etc/sysconfig/olpc-scripts/domain_config script with the appropriate domain name for the machine.
  • Ensure the right Postgres is set to run
 chkconfig --level 345 postgresql off
 chkconfig --add pgsql-xs

Upgrade from XS 0.4 or earlier

If you are upgrading from XS 0.4 or earlier, the process is similar to a new installation, with some minor changes. In the menu shown right after booting, you should choose one of the 'Install or upgrade an existing system' options, press the Tab key, and add 'upgradeany' to the boot configuration line. After adding that line, press enter twice.

With this extra option, Anaconda will recognise the old installation and will offer to upgrade.

Steps after upgrade:

  • Re-run the /etc/sysconfig/olpc-scripts/domain_config script with the appropriate domain name for the machine.
  • Ensure the right Postgres is set to run
 chkconfig --level 345 postgresql off
 chkconfig --add pgsql-xs

Notes:

  • The new OS may detect your network cards differently -- the roles of WAN and LAN cards may end up swapped from what they were under 0.4. If that happens, use the xs-swapnics script and reboot.

See also

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=XS_Installing_Software_0.6&oldid=290708"