Difference between revisions of "Debian Wheezy Instructions"

From odroid US
Jump to: navigation, search
(Revision History)
(Adding an X Display Manager)
 
(75 intermediate revisions by 3 users not shown)
Line 1: Line 1:
  
  
== Availability ==
+
== Introduction ==
An SD Card image for a Debian system for odroid-u2 is available in the downloads area [http://odroid.us/odroid/odroidu2/debian/ Debian-wheezy]
+
This effort started before HardKernel had a supported Debian image, now they have some.  At this writing the official build comes with the LXDE window manager installed -- depending on odroid board type.
  
The files with the .md5sum extensions give you an easy way to check validity after downloading, using md5sum like this:
+
There are some great full-featured user-contributed images available (GUI, XBMC and so on). For example: [http://forum.odroid.com/viewtopic.php?f=56&t=610 @robroyhall images]
<pre>
+
md5sum -c odroidu2_20130104-debian-wheezy-3.img.xz.md5sum
+
# odroidu2_20130104-debian-wheezy-3.img.xz: OK
+
</pre>
+
  
The non-filesystem area, including the bootloader(s) generally follow the HardKernel ubuntu images, like odroidu2_20130125-linaro-ubuntu-desktop-uSDeMMC.img.xz.  The partition layout is the same, the bootloaders are the same.
+
In order to keep this branch relevant, it has been updated to match the Hardkernel setup.  It has the same bootloader, boot scripts, partition layout, kernel version, and kernel modules -- only it is headless, meaning no GUI.  The approach is modular and you can follow the steps to add Gnome or XFCE as you like.
  
The boot partition holds the kernel, initrd and u-boot boot scriptsThese will not exactly track the HK releases.
+
The images have full provenance, you could create the same setup starting from bootstrapping with an emulated ARMThis topic is meant to help teach about embedded Linux.
  
debian-wheezy describes the system. The .img means it is a SD card image and .xz shows the file compression typeI recently dropped the added version number in favor of a date.
+
== 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 - Need special handling[[Updating from Root File System Images|Tutorial: Updating from Root File System Images]]
  
There are two versions, one is a minimal system and the other is a larger development version.  The development version includes a native gcc compiler, and all locales.
+
For Linux host users, see [[Step-by-step_Ubuntu_SD_Card_Setup|Tutorial: Step-by-step SD-Card setup on Linux host]]
  
== Revision History ==
+
For Windows users, see [[Debian_Wheezy_SD_Card_prepare_(Windows)|Tutorial: Step-by-step SD-card setup on Windows]]
=== debian-wheezy-2 ===
+
:initial release
+
=== debian-wheezy-3 ===
+
  
:Added curl package, updated to kernel 3.0.57
 
=== debian-wheezy-devel-4 ===
 
:<li>This is setup for native compiling.  linux-3.0.57 is ready to build in /usr/src/linux.
 
:<li>Added prerequsites for building the kernel
 
:<li>Added sudo
 
:<li>Built and installed the kernel per this tutorial: [[Kernel compiling]]
 
  
=== odroidu2-20130205-debian-wheezy-devel ===
+
== Availability ==
:<li>This is setup for native compiling. 
+
:<li>A private kernel build is installed: linux-3.0.61
+
:<li>The kernel source is removed from /usr/src/ in the interest of a smaller image
+
:<li>Fixed locale setup.  Added all locales.
+
:<li>Set the timezone to GMT+8 (USA Pacific)
+
:<li>Added ntpupdate package to update time from network
+
:<li>The MAC ID is chosen randomly on first boot, but stored persistently in /etc/smsc95xx_mac_addr.  For example the expected file contents would be like:  A6:2A:DC:0B:56:74.  You can edit the file to set the MAC ID if you need a specific one.
+
  
==== Issues ====
+
Several Debian SD-Card images and root file system images are available for various odroid boards.  This set of links is not completeYou can browse the download area for more.
On first boot, the mac id file is not created, the root file system has not been mounted read/write at that timeMake up your own random mac id and do something like this:
+
<pre>
+
echo A6:2A:DC:0B:56:74 > /etc/smsc95xx_mac_addr
+
</pre>
+
  
You will see a message like: FATAL: Could not load /lib/modules/3.0.61/modules.dep: No such file or directory.  This is not actually fatal, it is coming from the initrd -- which does not have a set of kernel modules matching the kernel, 3.0.61.
+
[[Debian-jessie-armel-odroidxu]]
  
=== debian-wheezy-base-6 ===
+
== Download Area ==
[debian-wheezy-base-6 Build Notes]
+
'''Note:''' The file arrangement is by hardkernel board names.  Make sure to download from the area that matches your board.
 +
 
 +
The download area is here: [http://odroid.us/odroid/ http://odroid.us/odroid/]
  
 
== Features ==
 
== Features ==
Writing an SD-card image and booting will give you a completely pristine, up-to-date, headless Debian 7.0 system. Headless, meaning only the Linux console is active -- not the HDMI display.
+
Writing the '''base''' SD-card image and booting will give you a complete, headless Debian system. <br/>
 +
Headless, meaning only the Linux console is active -- not the HDMI display.
  
The network will come up automatically, using DHCP.
+
The network will come up automatically, using DHCP and the ssh daemon will be started so you can connect from another computer -- even without the USB-UART kit.
  
The login is: user/password or root/root.  Specifically, this means username: user and password: password will get you in.
+
== Login ==
Or you can use username: root password: root.  Yes, I do let root log in to the console...
+
=== Version 7 Credentials ===
 +
As of release 7, the login credentials are odroid/odroid and root/odroid in order to match the official Hardkernel Debian release.  Specifically, this means username: odroid and password: odroid will get you in.  
  
If you log in as user, you can su to become root.
+
Or you can use username: root, password: odroid.
  
 +
If you log in as user, you can use command ''su'' to become root.
  
'''Source(s):'''  [http://www.downloadranking.com  Debian Wheezy Instructions]
+
=== Version 6 Credentials ===
 +
Previous to version 7, the credentials were user/password and root/root
  
 +
== Revision History ==
 +
See [http://odroid.us/mediawiki/index.php?title=Debian-wheezy-revision-history here] for a complete revision history of all images
  
== Root Filesystem Images ==
+
The top of the tree for these Debian images is: [http://odroid.us/odroid/ http://odroid.us/odroid/]  Notice the arrangement by hardkernel board names?  Make sure you download from the area that matches your board.
The tarball with the -rootfs.tgz suffix is just the content of the rootfs partition of the SD card.
+
  
If you have flashed the Ubuntu SD-Card image and want to try the Debian system, you can just mount the partition, delete all the files and then extract the tarball onto the SD card.
+
You should use the standard images that support hard-floating point if possible (armhf).  They will be faster than the soft-float versions -- yes, even of you are not doing floating point. The additional registers may be used to pass parameters.
  
See this tutorial for step-by-step instructions: [[Updating from Root File System Images]]
+
Some alternate images using soft floating point are also available (armel)
  
 +
You can't easily mix soft-float compiled and hard-float compiled binaries on the same system.  It is possible, but the general technique is not worked out yet (as far as I know).  The standard hardkernel kernels all built to support hard floating point, and that is a necessary requirement.
  
'''Source(s):'''  [http://www.downloadranking.com  Debian Wheezy Instructions]
+
== Security Issues and Initialization ==
 
+
When you use an existing image, you pick up some keys that you should change for security reasonsOnce you boot your system the first time do this: (as root)
 
+
== Debian Tips ==
+
This page is for Debian Tips [[Debian Tips]]
+
 
+
 
+
'''Source(s):'''  [http://www.downloadranking.com  Debian Wheezy Instructions]
+
 
+
 
+
== Image Creation Details ==
+
This section details how a Debian root file system for the odroid can be created.  Following the steps will not give you exactly the same results as in the prepared images because packages are periodically updated.
+
 
+
Debian is Debian.  If you have any Debian system, it can be updated or upgraded -- without having to go through your own bootstrap process.  It can be difficult to go through a bootstrap for a number of reasons including:
+
:<li>Crossing processor architectures is always an issue. If you are building for x86, no problem.  Most utilities work.  But, most people are not faced with building custom x86 distros
+
:<li>Debian has been around a long time.  Tools and approaches are always changing.  Googling is helpful, but you get a lot of information that is dated.
+
:<li>If you are bringing up a new platform, you don't have a known-good starting pointFor example, to do a network install, you need to have a root file system of some sort and you need a working network connection.
+
 
+
I did not invent any of this stuff, I just put it together and tested it specifically for use on an odroid target.
+
 
+
The bootstrap approach I show was tested on a clean Debian 6 machine, a VMWare virtual machine. You can find your own copy here: [http://www.trendsigma.net/vmware/debian6t.html Debian6t VM]  VMWare Player is free as well: [https://my.vmware.com/web/vmware/free#desktop_end_user_computing/vmware_player/4_0 VMWare Player].
+
 
+
 
+
'''Source(s):'''  [http://www.downloadranking.com  Debian Wheezy Instructions]
+
 
+
 
+
=== Setup sudo on the host ===
+
You might want to install the sudo package and add yourself to the sudoers list if you have not already done it.  This section is optional, but if you object to using sudo, there are commands you need to run as root.
+
 
+
As root (on the host):
+
 
<pre>
 
<pre>
apt-get install sudo
+
rm /etc/ssh/*.pub /etc/ssh/*_key
# You need to add yourself to the "sudoers list", and how exactly that is done depends on the distribution.
+
#images starting at debian-wheezy-base-6.1 should have openssh-server installed
# This hack works for Debian Wheezy
+
# re-generate the host ssh keys
# as root, add normal user (named user) to adm group
+
dpkg-reconfigure openssh-server
adduser user adm
+
# configure the adm group to have no restrictions
+
echo "%adm ALL=(ALL) ALL" >> /etc/sudoers
+
# sudo will complain if it cannot resolve the hostname
+
echo "127.0.0.1 $(hostname )" >> /etc/hosts
+
</pre>
+
You need to logout/login after making the change to the sudoers list in order for it to take effect
+
  
 
'''Source(s):'''  [http://www.downloadranking.com  Debian Wheezy Instructions]
 
 
 
=== Install Prerequisites ===
 
<pre>
 
sudo apt-get update
 
sudo apt-get install binfmt-support qemu qemu-user-static debootstrap
 
 
</pre>
 
</pre>
  
We must have the qemu-arm-static binary to bring up the system and qemu version 0.12.5 is known to fail. As of this writing, qemu 1.4.0 is current and is known to workInterim versions might also work. 
+
It is best to set a unique persistent MACIDThis script will do it:
 
+
If it helps, you might be able to use one of the binaries I built, posted here: [http://odroid.us/odroid/users/osterluk/debian-armhf/ http://odroid.us/odroid/users/osterluk/debian-armhf/] 
+
 
+
 
<pre>
 
<pre>
wget http://odroid.us/odroid/users/osterluk/debian-armhf/debian-armhf.tgz
+
echo $( ifconfig | grep HWaddr | awk '{ print $5 }' ) >/etc/smsc95xx_mac_addr
wget http://odroid.us/odroid/users/osterluk/debian-armhf/debian-armhf.tgz.md5sum
+
md5sum -c debian-armhf.tgz.md5sum
+
# if the checksum is OK, then extract the files:
+
tar -xvzf debian-armhf.tgz
+
</pre>
+
  
The files are:
 
<pre>
 
launch-wheezy-no-bridge  A script to launch the root file system on the host using qemu-system-arm
 
qemu-arm-static-i386    Statically built, current version of qemu-arm for 32-bit Linux host
 
qemu-arm-static-x86_64  Statically built, current version of qemu-arm for 64-bit Linux host
 
zImage-vexpress-a9      A kernel built for a cortex-a9 machine, vexpress-a9 that is a good stand-in for
 
 
</pre>
 
</pre>
  
The -i386 version will probably run on and x86 Linux host, but only because it is statically linked.  Just rename it to qemu-arm-staticThe x86_64 will not run on a 32-bit host.
+
== Adding Native Compiler and Tools ==
 
+
The base, xfce and gnome images do not include tools required to build the kernel or other compile other packagesHere are steps you can do to add that capability: (as root).  We get some (but not all) recommended packages tooAll recommended packages add over 1GiB to the flash footprint
Check the "Building QEMU" section of this tutorial if you need to build an updated qemu-arm-static binary:  
+
[http://odroid.us/mediawiki/index.php?title=Step-by-step_Using_qemu_to_Boot_an_Emulated_Odroid Building QEMU]
+
 
+
 
+
'''Source(s):'''  [http://www.downloadranking.com Debian Wheezy Instructions]
+
 
+
 
+
=== Use debootstrap to Create Debian Root File System ===
+
To get started, we need a root file system that has all the components needed to boot DebianOnce we have that, we can configure the system and add more packages. This technique uses qemu-system-arm, so qemu (quick emulator) needs to be installed.
+
  
 
<pre>
 
<pre>
# Go to a convenient directory
+
apt-get install build-essential ncurses-dev
cd $HOME
+
apt-get install gcc-4.6-locales debian-keyring libstdc++6-4.6-dbg autoconf automake1.9 libtool flex bison gdb libmudflap0-4.6-dev
# make a place to work
+
apt-get install libgcc1-dbg libgomp1-dbg libmudflap0-dbg binutils-gold ed p7zip-full
mkdir debian-bootstrap
+
# and go there
+
cd debian-bootstrap
+
# Create the root file system, this can take some time...
+
sudo debootstrap --verbose --arch armhf --foreign wheezy $PWD/armhf http://ftp.at.debian.org/debian
+
# Now the directory $HOME/debian-bootstrap/armhf holds a wheezy root file system, built from binary packages
+
</pre>
+
  
We are going to chroot into the the armhf directory and we need qemu-arm-static available to be able to run the bootstrap script while hiding the rest of the host files from the process.  qemu-arm-static knows how to run armhf binaries on our x86 machine -- cool when you think about it.  Quite a nice piece of work.
 
 
Find qemu-arm-static:
 
<pre>
 
$(which qemu-arm-static)
 
 
</pre>
 
</pre>
/usr/local/bin/qemu-arm-static
 
  
Make a local copy, for clarity: (copy from your downloads folder, if you plan to use the pre-built binary)
+
== Adding an X Display Manager ==
<pre>
+
sudo cp /usr/local/bin/qemu-arm-static .
+
</pre>
+
  
copy qemu-arm-static into what will be the chroot jail:
+
[[ X Display Manager for odroidu2 ]]
<pre>
+
sudo cp qemu-arm-static armhf/usr/bin
+
</pre>
+
  
Run debian second stage: (this is the place where a downlevel qemu-arm-static will fail)
+
[[ X Display Manager for odroidxu ]]
<pre>
+
DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true \
+
LC_ALL=C LANGUAGE=C LANG=C sudo chroot armhf /debootstrap/debootstrap --second-stage
+
</pre>
+
  
Trigger post-install scripts:
+
== Debian Tips ==
<pre>
+
This page is for Debian Tips [[Debian Tips]]
DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true \
+
LC_ALL=C LANGUAGE=C LANG=C sudo chroot armhf dpkg --configure -a
+
</pre>
+
 
+
 
+
'''Source(s):'''  [http://www.downloadranking.com  Debian Wheezy Instructions]
+
 
+
 
+
=== Fixup Virgin Root File System ===
+
Edit inittab to put a getty on the serial console -- and also to boot to the root shell since I don't know the default username/password. (maybe there is a better, more general way to do this)
+
 
+
Make sure to notice: if you want to boot with qemu, then you must change ttySAC1 below to ttyAMA0.  If you do not do this, you will not get an initial console and the problem will not be obvious...
+
 
+
As root, in armhf/etc/inittab, change:
+
<pre>
+
#T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
+
</pre>
+
to
+
<pre>
+
# To use with qemu, in next line, replace ttySAC1 with ttyAMA0
+
T0:23:respawn:/sbin/getty -L ttySAC1 115200 vt102
+
</pre>
+
 
+
As root, in armhf/etc/inittab, change:
+
<pre>
+
id:2:initdefault:
+
</pre>
+
to
+
<pre>
+
id:1:initdefault:
+
</pre>
+
 
+
 
+
'''Source(s):'''  [http://www.downloadranking.com  Debian Wheezy Instructions]
+
 
+
 
+
==== Drop in Kernel Modules ====
+
Kernel modules must always match the kernel in use.  If you don't care about bring up the network, you can come back to this step later.
+
 
+
See the main page for a list of kernel building tutorials: [http://odroid.us/mediawiki/index.php?title=Main_Page#Tutorials]
+
 
+
You need to either build a custom kernel and the kernel modules (drivers) that go with it or you need to extract the kernel modules from an existing root file system that you know has a set matching the kernel you want to use.  Kernel modules would be stored at /lib/modules/3.0.68 for example, if you have a set for 3.0.68.
+
 
+
[TODO: add a link to the HardKernel kernel update repository ]
+
 
+
 
+
'''Source(s):'''  [http://www.downloadranking.com  Debian Wheezy Instructions]
+
 
+
 
+
==== Add Device Nodes ====
+
 
+
Drop in some device nodes to let us run the root file system with qemu or real hardware
+
<pre>
+
sudo mknod  armhf/dev/ttyAMA0 c 204 64
+
sudo mknod  armhf/dev/ttySAC0 c 204 64
+
</pre>
+
 
+
 
+
'''Source(s):'''  [http://www.downloadranking.com  Debian Wheezy Instructions]
+
 
+
 
+
=== Create a Root File System Tarball ===
+
It is convenient to make a tarball of the root file system.
+
 
+
<pre>
+
cd $HOME/debian-bootstrap/armhf
+
sudo tar -cvzf ../rootfs-wheezy-custom.tgz .
+
cd ..
+
</pre>
+
 
+
Mount the SD-Card on your host and follow the tutorial: [[Updating from Root File System Images]] to update your SD-Card.
+
 
+
 
+
'''Source(s):'''  [http://www.downloadranking.com  Debian Wheezy Instructions]
+
 
+
 
+
=== Create a File System Image to use with QEMU (optional) ===
+
 
+
Convert the root file system to a filesystem image.  If you host has enough memory, you could increase the 500M to some larger value.
+
<pre>
+
qemu-img create rootfs-wheezy.ext4 500M
+
sudo mkfs.ext4 rootfs-wheezy.ext4
+
</pre>
+
 
+
And the second step:
+
<pre>
+
# We are going to need a mount point
+
mkdir mnt
+
sudo mount -o loop rootfs-wheezy.ext4 mnt
+
sudo cp -a armhf/* mnt
+
sync
+
sudo umount mnt
+
# Now rootfs-wheezy.ext4 has the same contents as the bootstrapped Debian
+
</pre>
+
 
+
 
+
'''Source(s):'''  [http://www.downloadranking.com  Debian Wheezy Instructions]
+
 
+
 
+
==== Boot with QEMU ====
+
 
+
TBD show how to use the qemu example to boot the RFS
+
 
+
 
+
'''Source(s):'''  [http://www.downloadranking.com  Debian Wheezy Instructions]
+
 
+
 
+
=== Boot the Target ===
+
The system will come up in a root shell.  We should change the passwords.  If you want to match the Hardkernel Ubuntu image, set the root password to root and the user password to password.
+
<pre>
+
passwd root
+
# answer with the root password you will remember -- consider making a note
+
# Add a user to login with
+
adduser user
+
</pre>
+
 
+
As root, in armhf/etc/inittab, change back to a password-protected shell, and make sure the serial console name
+
and terminal type are correct:
+
<pre>
+
id:1:initdefault:
+
T0:23:respawn:/sbin/getty -L ttyAMA0 9600 vt100
+
</pre>
+
to
+
<pre>
+
id:3:initdefault:
+
T0:23:respawn:/sbin/getty -L ttySAC1 115200 vt102
+
</pre>
+
 
+
You probably want to change the hostname too.  For the debootstrap build, the hostname will be the same as the host you built it on.  To set the hostname to odroidu2, do this: (as root)
+
<pre>
+
echo odroidu2 > /etc/hostname
+
</pre>
+
 
+
No need to keep the binary packages (about 50MiB) so clean them up like this: (as root)
+
<pre>
+
apt-get clean
+
</pre>
+
 
+
 
+
'''Source(s):'''  [http://www.downloadranking.com  Debian Wheezy Instructions]
+
 
+
 
+
 
+
And reboot
+
 
+
Now, we can (as root) set the apt sources, bring up the network and update.  You should choose a nearby mirror (respository)
+
<pre>
+
echo "deb http://ftp.us.debian.org/debian wheezy main" > /etc/apt/sources.list
+
dhclient eth0
+
apt-get update
+
</pre>
+
 
+
The system is complete.
+
  
 +
== Image Creation Details ==
  
'''Source(s):'''  [http://www.downloadranking.com  Debian Wheezy Instructions]
+
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]].

Latest revision as of 22:07, 20 January 2014


Introduction

This effort started before HardKernel had a supported Debian image, now they have some. At this writing the official build comes with the LXDE window manager installed -- depending on odroid board type.

There are some great full-featured user-contributed images available (GUI, XBMC and so on). For example: @robroyhall images

In order to keep this branch relevant, it has been updated to match the Hardkernel setup. It has the same bootloader, boot scripts, partition layout, kernel version, and kernel modules -- only it is headless, meaning no GUI. The approach is modular and you can follow the steps to add Gnome or XFCE as you like.

The images have full provenance, you could create the same setup starting from bootstrapping with an emulated ARM. This topic is meant to help teach about embedded Linux.

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 - Need special handling. 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


Availability

Several Debian SD-Card images and root file system images are available for various odroid boards. This set of links is not complete. You can browse the download area for more.

Debian-jessie-armel-odroidxu

Download Area

Note: The file arrangement is by hardkernel board names. Make sure to download from the area that matches your board.

The download area is here: http://odroid.us/odroid/

Features

Writing the base SD-card image and booting will give you a complete, headless Debian 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 -- even without the USB-UART kit.

Login

Version 7 Credentials

As of release 7, the login credentials are odroid/odroid and root/odroid in order to match the official Hardkernel Debian release. Specifically, this means username: odroid and password: odroid will get you in.

Or you can use username: root, password: odroid.

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

Version 6 Credentials

Previous to version 7, the credentials were user/password and root/root

Revision History

See here for a complete revision history of all images

The top of the tree for these Debian images is: http://odroid.us/odroid/ Notice the arrangement by hardkernel board names? Make sure you download from the area that matches your board.

You should use the standard images that support hard-floating point if possible (armhf). They will be faster than the soft-float versions -- yes, even of you are not doing floating point. The additional registers may be used to pass parameters.

Some alternate images using soft floating point are also available (armel)

You can't easily mix soft-float compiled and hard-float compiled binaries on the same system. It is possible, but the general technique is not worked out yet (as far as I know). The standard hardkernel kernels all built to support hard floating point, and that is a necessary requirement.

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

Adding Native Compiler and Tools

The base, xfce and gnome images do not include tools required to build the kernel or other compile other packages. Here are steps you can do to add that capability: (as root). We get some (but not all) recommended packages too. All recommended packages add over 1GiB to the flash footprint

apt-get install build-essential ncurses-dev
apt-get install gcc-4.6-locales debian-keyring libstdc++6-4.6-dbg autoconf automake1.9 libtool flex bison gdb libmudflap0-4.6-dev 
apt-get install libgcc1-dbg libgomp1-dbg libmudflap0-dbg binutils-gold ed p7zip-full

Adding an X Display Manager

X Display Manager for odroidu2

X Display Manager for odroidxu

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.