Kevux Systems
Turtle Kevux - Documentation - System Configuration
Home
Documentation
Software Listing
Booting & Running
Installing Turtle Kevux
System Configuration
Server Configuration
Additional Notes
Credits

First Time Running Configuration

The very first time the system is run, there are some important things to do.
Most important of all is changing the root password and adding users.
If you do not change your root password immediately, your system is vulnerable to hacks.
If you do not add users, then your users will not be able to use your system unless they run as the root user.
WARNING: Running as the root user is dangerous, do so at your own lethal risk.

Changing the root user password is simple:
  - Login to your root user (by default this is turtle).
  - In a command-line prompt (or a terminal), run the command passwd.
    - NOTE: the command passwd must not contain the "or", passwd is exactly as the command should be spelled.
  - Follow the instructions and your done.


Setting Up Usernames and Passwords

To add a user to the system, use the command line program called adduser, which requires root user access.
NOTE: In previous versions the gadduser program was supplied as a graphical user interface to adding users, but this has been removed for the time being.


To add a user, open up a terminal and switch to root access.
Simply specify the username followed by the permissions group they should belong to.
There are 3 major permissions groups: admin, power, and desktop.
The admin user has the most priviledges on the system and can gain root access, there is little this user cannot do.
The power user is a slightly weakened version of admin and the power user cannot gain root access.
The desktop user has the standard permissions needed for standard desktop usage and has no heightened priviledges beyond that.


After you begin the add user process you will be prompted for a password.
Following this, if everything went well the user will have been added to the system.
If you ever need to remove a user, the deluser program can be used and functions in an almost identical fassion.

NOTE: By default the deluser program will remove all files own by the deleted user, to prevent this from happing use the unsetup script called none.
For example, normally to delete the user BOB the command would be 'deluser BOB'.
To delete BOB without removing BOB's files, the command would be: 'deluser BOB none'.


Setting Up the Network


Configuration Path: /etc/network/

The Files:

  1. default-blacklist
  2. default-firewall
  3. default-device
  4. example-device
  5. example-device-firewall
  6. example-device-wpa
  7. example-wireless
  8. example-bridge
  9. hostname
  10. hosts
  11. proc_settings
  12. resolution
  13. protocols
  14. services
  15. gre0, tunl0


Setting Up the Xorg Display


Configuration Path: /etc/X11/

The file to be configured is: /etc/X11/xorg.conf
The file /etc/X11/xorg.conf has examples and slight documentaton on how to configure the xorg display.
You can also visit http://www.x.org/ for details.
Alternatively visit http://die.net/ and search for xorg.conf.


If you need to use a different video driver, edit the /etc/X11/xorg.conf file.
Scroll to the bottom and uncomment and set the Driver to whatever you need it to be.

If you are on an OLPC, you could copy the pre-created olpc xorg configuration file:
   cd /etc/X11/
   cp -v xorg.conf.olpc xorg.conf


Updating the ClamAV Database


Configuration Path: /home/services/clamav/database/

You will need to open a terminal and switch to the clamav user.
Now execute the freshclam program.
NOTE: This requires network access, so this will fail if you have no working network active.


Tweaking the Boot Process


Configuration Path: /etc/initng/

The file to be configured is: /etc/initng/runlevel/default.runlevel
The default.runlevel file specifies how the system boots, but not the order.
The order is handled by the individual dependencies.

Most of the available boot-time software have rules already created such that all you need to do is add them to the default runlevel.
To add/remove anything to the boot process, the syntax of the file requires the directory and then the filename (without the extension) on a line by itself.

If you wanted to add an SSH server to your boot process, then you would simple add target/ssh on any newline in the file.
The directory target/ can be found in the /etc/initng/ directory.

If you wish to boot using a runlevel other than default, look into the runlevel= boot option.

Once settings are changed, you can use the ngc program to start/stop and do other initng administrative commands.


PCI and USB ID Updating


Configuration Path: /etc/

The files to be configured are: /etc/pci.ids and /etc/usb.ids
The /etc/pci.ids and /etc/usb.ids files specify vender-specific information on what any particular hardware device is.
In particular, the lspci and lsusb utilities read this information.

To update /etc/pci.ids to the latest version, download: http://pciids.sourceforge.net/v2.2/pci.ids
To update /etc/usb.ids to the latest version, download: http://www.linux-usb.org/usb.ids

Once this is done, make sure that the file permissions are correct:
   chgrp hardware_browse /etc/{pci,usb}.ids
   chmod g-wx+r,o-rwx /etc/{pci,usb}.ids


Using Turtle Kevux on the OLPC

The first step is to follow the instructions on the OLPC website to obtain the developer key.
This may take a while, so come back a few hours later.

There are two possible ways to boot kevux without touching the original OLPC system.
The first is to install Turtle Kevux onto a USB-Stick, whose partition should be labelled turtle-usb-olpc
The second is to install Turtle Kevux onto a MMC, whose partition should be labelled turtle-sd-olpc
If you do not know how to label or format the USB-Stick or MMC:

  1. Read the partitioning tutorial
  2. Make sure to properly select the correct USB-Stick or MMC.
  3. Create a single partition and set the label to either turtle-usb-olpc or turtle-sd-olpc for USB-Stick and MMC respectively.

The next step is to obtain the custom compiled OLPC kernels from the kevux website.
Once you have the custom OLPC kernel and its appropriate kernel modules, put them on the system.
Lets say you downloaded the custom compiled OLPC kernel from kevux.org and it is called turtle-2.6.26.5-olpc and the maintenance kernel is called turtle-2.6.26.5-olpc-maintenance.
Lets say that you also dowloaded the appropriate kernel modules and it is called 2.6.26.5-olpc.tz2.
You will also need to extract the kernel modules to modules/
What you would do is:
   mv -v turtle-2.6.26.5-olpc boot/
   ln -vs turtle-2.6.26.5-olpc boot/turtle-olpc
   tar -xf 2.6.26.5-olpc.tz2 -C modules/
   mv -v turtle-2.6.26.5-olpc-maintenance boot/
   ln -vs turtle-2.6.26.5-olpc-maintenance boot/turtle-olpc-maintenance

Replace the default xorg.conf file with the the xorg.conf.olpc file so that you can get a working graphical display:
   cp -v etc/X11/xorg.conf.olpc etc/X11/xorg.conf

You are now ready to boot to the OLPC.
Plug your device into the OLPC and reboot the OLPC.
If all goes well, you should get a prompt where you can press a key to select the desired method of booting.
NOTE: Don't select the Squash or Squish boot methods unless you know what you are doing.

If all went well, you are sitting in a graphical environment.
You now have one more step at tweaking the system.


Open up the Applications->Settings->Appearance.


Select the Fonts tab.


Enable the Custom DPI Settings checkbox and set DPI to 140.

You should now be able to fully use OLPC.
NOTE: Use the TVCard Player called xawtv to access the camera.