Difference between revisions of "Debian Wheezy Instructions"

From odroid US
Jump to: navigation, search
(Image Creation Details)
Line 5: Line 5:
 
Several Debian SD-Card images and root file system images are available for the odroid-u2 board.  The root file system images <should> work for other odroid models, but they would have to be merged with the "stock" SD Card image and the kernel modules would have to be pulled from the "foriegn" kernel build.  If this doens't make sense, please ask on the forum.
 
Several Debian SD-Card images and root file system images are available for the odroid-u2 board.  The root file system images <should> work for other odroid models, but they would have to be merged with the "stock" SD Card image and the kernel modules would have to be pulled from the "foriegn" kernel build.  If this doens't make sense, please ask on the forum.
  
=== Versions ===
+
== Versions ==
 
*''minimal system'' ('''base''') - headless or server-style.  Login with USB-UART kit or using ssh.  No GUI.
 
*''minimal system'' ('''base''') - headless or server-style.  Login with USB-UART kit or using ssh.  No GUI.
 
*''system with visual desktop'' ('''gnome''', '''xfce''') - '''recommended for new users'''
 
*''system with visual desktop'' ('''gnome''', '''xfce''') - '''recommended for new users'''
Line 13: Line 13:
  
 
For Windows users, see [[Debian_Wheezy_SD_Card_prepare_(Windows)|Tutorial: Step-by-step SD-card setup on Windows]]
 
For Windows users, see [[Debian_Wheezy_SD_Card_prepare_(Windows)|Tutorial: Step-by-step SD-card setup on Windows]]
 
 
=== Standard armhf Images ===
 
You should use the standard images that support hard-floating point.  These will be faster than the soft-float versions.
 
 
[http://odroid.us/odroid/odroidu2/debian/ http://odroid.us/odroid/odroidu2/debian/]
 
 
=== Alternate armel Images ===
 
A secondary set of images that are armel based, using soft floating point, are stored here:
 
 
[http://odroid.us/odroid/users/osterluk/debian-armel/ http://odroid.us/odroid/users/osterluk/debian-armel/]
 
 
You can't easily mix soft-float compiled and hard-float compiled binaries on the same system.
 
  
 
== Features ==
 
== Features ==
Line 38: Line 25:
 
If you log in as user, you can use command ''su'' to become root.
 
If you log in as user, you can use command ''su'' to become root.
  
==== Checking archive Integrity with md5sum ====
+
== Revision History ==
* Files next to SD images (''with the .md5sum extensions'') give you an easy way to check validity after downloading, using md5sum like this:
+
See [http://odroid.us/mediawiki/index.php?title=Debian-wheezy-revision-history here] for all revision history.
<pre>
+
md5sum -c odroidu2_20130104-debian-wheezy-3.img.xz.md5sum
+
# odroidu2_20130104-debian-wheezy-3.img.xz: OK
+
</pre>
+
  
==== The Image structure ====
+
== Standard armhf Images ==
The non-filesystem area, including the bootloader(s) generally follow the HardKernel ubuntu images, like odroidu2_20130125-linaro-ubuntu-desktop-uSDeMMC.img.xzThe partition layout is the same, the bootloaders are the same.
+
You should use the standard images that support hard-floating pointThese will be faster than the soft-float versions.
  
The boot partition holds the kernel, initrd and u-boot boot scripts. These will not exactly track the HK releases.
+
[http://odroid.us/odroid/odroidu2/debian/ http://odroid.us/odroid/odroidu2/debian/]
  
== Revision History ==
+
== Alternate armel Images ==
See [http://odroid.us/mediawiki/index.php?title=Debian-wheezy-revision-history here] for all revision history.
+
A secondary set of images that are armel based, using soft floating point, are stored here:
 +
 
 +
[http://odroid.us/odroid/users/osterluk/debian-armel/ http://odroid.us/odroid/users/osterluk/debian-armel/]
 +
 
 +
You can't easily mix soft-float compiled and hard-float compiled binaries on the same system.
  
  

Revision as of 13:29, 23 May 2013


Availability

Several Debian SD-Card images and root file system images are available for the odroid-u2 board. The root file system images <should> work for other odroid models, but they would have to be merged with the "stock" SD Card image and the kernel modules would have to be pulled from the "foriegn" kernel build. If this doens't make sense, please ask on the forum.

Versions

  • minimal system (base) - headless or server-style. Login with USB-UART kit or using ssh. No GUI.
  • system with visual desktop (gnome, xfce) - recommended for new users
  • root filesystem only (rootfs) image - Tutorial: Updating from Root File System Images

For Linux host users, see Tutorial: Step-by-step SD-Card setup on Linux host

For Windows users, see Tutorial: Step-by-step SD-card setup on Windows

Features

Writing the base SD-card image and booting will give you a complete, headless Debian 7.0 system.
Headless, meaning only the Linux console is active -- not the HDMI display.

The network will come up automatically, using DHCP and the ssh daemon will be started so you can connect from another computer.

The login is: user/password or root/root. Specifically, this means username: user and password: password will get you in. Or you can use username: root, password: root.

If you log in as user, you can use command su to become root.

Revision History

See here for all revision history.

Standard armhf Images

You should use the standard images that support hard-floating point. These will be faster than the soft-float versions.

http://odroid.us/odroid/odroidu2/debian/

Alternate armel Images

A secondary set of images that are armel based, using soft floating point, are stored here:

http://odroid.us/odroid/users/osterluk/debian-armel/

You can't easily mix soft-float compiled and hard-float compiled binaries on the same system.


Security Issues and Initialization

When you use an existing image, you pick up some keys that you should change for security reasons. Once you boot your system the first time do this: (as root)

rm /etc/ssh/*.pub /etc/ssh/*_key
#images starting at debian-wheezy-base-6.1 should have openssh-server installed
# re-generate the host ssh keys
dpkg-reconfigure openssh-server

It is best to set a unique persistent MACID. This script will do it:

echo $( ifconfig | grep HWaddr | awk '{ print $5 }' ) >/etc/smsc95xx_mac_addr

Debian Tips

This page is for Debian Tips Debian Tips

Image Creation Details

You can completely re-create any of these Debian root filesystem images own your own. All the instructions are here: Custom_Debian_Root_Filesystem_Image.