Hi,

I hope we can keep Abhisek in the loop as he has detailed information on the XS version deployed in Nepal. The procedure there is to build XS and release it as an img. The image is loaded to a usb drive (mkusbinstall.sh). This key is used to install all of the deployed school servers. I have attached the instructions for installing NEXS from the olenepal redmine (slightly edited).

I am very internet-challenged (at this campground I arrived on Thursday and used the internet for about two hours and then it died - now on Sunday evening it is working intermittently!), so I think some of my previous comments have not been received. So please be patient if you have read this before:

I think the separation of the server into two components XS and XC is very valuable. The XC build should provide a working schoolserver which can be accessed via the LAN from an XO using ssh. With the XS-Au fix for the 'race' condition in kickstart, it should be possible to do this install 'headless' on a server which supports booting from the usb drive when present (and bootable).

XC provides the content for the /library partition. However, with Daniel Drake's usbmount scripts XC could be used to install any optional packages such as Dan's Guardian, Moodle (forgive me, Martin), Fedora Commons, Fez, mediawiki, and so on.

The netsetup.sh script should be used to configure the WAN network and should not be needed when the school server is not connected to an external network (the LAN network is configured the same in every school as 172.18.0.1). The LAN should be configured for the baseboard (RJ45) port and the WAN for a secondary port (e.g. usb-ethernet).

Essentially this is the procedure used in Nepal with considerable success over the past two years (success measured by the schoolserver very rarely being a problem requiring service (UPS failures seem far more frequent).

Tony

P.S. http://wiki.laptop.org/go/OLE_Nepal:Procedure_to_build_NEXS_from_OLPC_XS gives a description of the build procedure used for XS-0.4. It provides details on the installation of the extra packages as of that time. Abhishek Singh can provide more recent details.

On 06/03/2011 04:21 PM, Sridhar Dhanapalan wrote:
On 4 June 2011 00:00, Aleksey Lim<alsr...@activitycentral.org>  wrote:
On Fri, Jun 03, 2011 at 09:40:48AM -0400, Martin Langhoff wrote:
On Fri, Jun 3, 2011 at 7:49 AM, Sridhar Dhanapalan
<srid...@laptop.org.au>  wrote:
On 3 June 2011 21:31, Aleksey Lim<alsr...@activitycentral.org>  wrote:
btw, did someone try to use cloning paradigm for setting up new school
servers instead of using regular install way? Just clonning the system
will lest avoid many issues by design.
Do you mean creating an image of a server installation and applying it
to other machines?

We've done that with the XS-AU (using clonezilla), and I'm pretty sure
it works with an OLPC XS.
Note that without a script that cleans up config&  state, you're bound
to have some fun problems with the resulting systems.
Do you mean particular script, which one?
You'll need to clean up:

     /etc/udev/rules.d/70-persistent-net.rules (delete the lines that
refer to all the eth devices)
     /etc/sysconfig/network-scripts/ifcfg-eth* (remove the HWADDR line)
     ssh keys (/etc/ssh/ssh_host_*)
     postgresql server.crt

Info: http://dev.laptop.org.au/issues/422

Sridhar


NEXS installation¶

>From USB¶

   1. Take a USB disk, create a single partition with type 0x83 (Linux) (e.g. 
using fdisk) and format it as VFAT (e.g. using mkfs.vfat)
          * This conflict of partition type vs filesystem is intentional; the 
Anaconda installer seems a bit sensitive to other configurations and may get 
confused at the bootloader install stage if you don't use this configuration
   2. Download the NEXS .iso corresponding to the NEXS version that you want to 
install to your hard disk
   3. Download 
http://hg.olenepal.org/NEXS-image-builder/raw-file/tip/mkusbinstall to your 
hard disk
   4. Run:

      # sudo bash ./mkusbinstall /path/to/nexs.iso /dev/sdb1

          * where /dev/sdb1 is the partition of your USB disk
   5. Plug the USB disk into the Wind computer
   6. Turn on and press F11 until menu appears
   7. Choose USB device from the boot device menu
   8. Choose the default "Install with kickstart" option from the boot menu
   9. After a few seconds, you will see an error that says that the kickstart 
file cannot be found. Wait 5 seconds, then press enter twice to retry.
          * This is an Anaconda bug where it tries to access the USB disk 
before it is ready
  10. You may see another error message saying that the installation media 
cannot be found. If so, try selecting /dev/sdc1 as the installation device (the 
default is sdb1)
          * This is because on some Wind systems, the onboard SD card reader 
takes the sdb position

Once installation completes, the system will reboot. Remove the USB disk at 
this time, and continue with the configuration steps below.
NEXS configuration¶

During first boot, you will be shown a list of instructions. These are:

   1. Login as root.
   2. Run /usr/share/nexs-custom/netsetup.sh to configure network.
   3. Reboot.
   4. (Optional) plug in USB customization disk. If it is already present, then 
make sure to replug it because not all installations will have taken effect 
before this point in time.

Follow these instructions. The root password is xxx.

The netsetup script is for configuring the internet connection (eth0) (e.g. 
IP/gateway details) as well as setting a hostname for the server. You should 
choose a hostname based on the location of the school e.g. 
laxmi.mkw.olenepal.org for the Laxmi school in Makwanpur.

When run with no parameters, the netsetup script shows a usage message. You 
must re-run this script with appropriate parameters. The only required 
parameter is a hostname, e.g.:

# /usr/share/nexs-custom/netsetup.sh laxmi.mkw.olenepal.org

The final step is documented on the NEXS installing content page.
_______________________________________________
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel

Reply via email to