Walltop: Difference between revisions

From Wildsong
Jump to navigationJump to search
← Older edit
VisualWikitext
Brian Wilson (talk | contribs)
Bureaucrats, restrict, Administrators, uploaders
11,470 edits
Brian Wilson (talk | contribs)
Bureaucrats, restrict, Administrators, uploaders
11,470 edits
mNo edit summary
 
(29 intermediate revisions by the same user not shown)
Line 1: Line 1:
WallTop computers... recycle an old laptop by removing all the extraneous parts such as the cdrom drive, floppy drive, (dead) battery and then hanging it on the wall.
WallTop computers... the concept is to recycle an old laptop by removing all the extraneous parts such as the cdrom drive, floppy drive, (dead) battery and then hanging it on the wall.


I am building one from an old Dell Inspiron 3700.
= Available hardware =


== Operating system ==
My first attempt is based on a Dell Inspiron 3700 C466GT.


I looked at using Debian, Damn Small Linux, Puppy Linux (which immediately panics on boot), and Movix. I decided I might as well stick with Ubuntu so I am building a custom Live CD. I will then transfer it to a Compact Flash card, which will be plugged into an IDE adapter and replace the incredibly noisy stock 4200 rpm hard drive.
* 466 MHz Celeron processor
* 256 MB PC100 SODIMM memory
* one PATA slot
* two broken PC card slots
* one USB port


See http://www.debuntu.org/how-to-customize-your-ubuntu-live-cd
Removed: case, 4200 RPM hard drive, dead battery


'''Oh! This was a bad idea. Much stuff about Ubuntu live cd's has been deleted from this page!'''
Added: a shadow box frame from Michaels, a power supply from OSUsed, a CF to 44pin PATA adapter, a 1GB CF card, and an ASUS 802.11g WiFi USB adapter


=== Debian Live! ===
I had to modify the frame to add cooling slots.


The way to do this is [http://live.debian.net/ Debian Live!]
This laptop will only boot when you touch its power on button. To make the button accessible I mounted the motherboard upside down (what used to be the top is towards the wall when it's hanging up.
I drilled a hole in the back about 3/8" diameter. You can poke the button with a pencil eraser to boot it up. Yes.. its a pain.
 
== More hardware available for future projects ==
 
Micron TransPort GX2: Pentium III 1.2Ghz
* 15-inch LCD at 1,280-by-1,024
 
http://www.pcmag.com/article2/0,2817,7733,00.asp
 
Micron TransPort XT Notebook Computers CPU: Intel Pentium III 750 ~ 850MHz
* Standard Memory: 64MB~256MB
* Maximum Memory: 512MB
14" screen
 
http://www.pcworld.com/article/54784/micronpc_launches_transport_xt_notebook.html
 
= The software =
 
== Which distribution to use? ==
 
After much research and experimentation I settled on
[http://live.debian.net/ Debian Live!]
 
This allows me to build an image on a big fancy Ubuntu desktop system ([[Raven]]) and test it in qemu.
 
Once the image is built I transfer it to a Compact Flash card, which will be plugged into an IDE adapter and replace the incredibly noisy stock 4200 rpm hard drive.
 
I am also now using Debian Live! to build [[Asterisk]] phone systems.
 
Some other options that I investigated:
*Debian
*Damn Small Linux
*Puppy Linux (which immediately panics on boot)
*Movix
*Ubuntu, building a [http://www.debuntu.org/how-to-customize-your-ubuntu-live-cd custom Live CD]
 
== Debian Live! installation ==


[http://wiki.debian.org/DebianLive Debian Live wiki]
[http://wiki.debian.org/DebianLive Debian Live wiki]
Line 56: Line 97:
  lh_config
  lh_config
  lh_bootstrap
  lh_bootstrap
# Prepare for a chroot system so you can do hacks
  lh_chroot
  lh_chroot
  lh_chroot_hosts install
  lh_chroot_hosts install
Line 61: Line 103:
  lh_chroot_proc install
  lh_chroot_proc install
  chroot chroot
  chroot chroot
  #do the hacks here, for example "apt-get install asterisk".
#do the hacks here, for example "apt-get install asterisk".
exit
# Now remove the changes make to do chroot
  lh_chroot_hosts remove
  lh_chroot_hosts remove
  lh_chroot_resolv remove
  lh_chroot_resolv remove
  lh_chroot_proc remove
  lh_chroot_proc remove
# I wonder what this does
  lh_binary
  lh_binary
# Build the image
  lh_build
  lh_build


Line 89: Line 135:
http://www.debianadmin.com/how-to-auto-login-and-startx-without-a-display-manager-in-debian.html
http://www.debianadmin.com/how-to-auto-login-and-startx-without-a-display-manager-in-debian.html


== Debian Live operating system ==
=== Building a working image ===


[http://live.debian.net/ Debian Live!]
To make (large) changes, you build a new, complete image from scratch.
is designed to run from read only media such as a CD,
You copy the new image to CF, put it in the computer, and boot.
I am trying to install it on a USB flash device for ease of use.


=== The basic principles ===
I add scripts to config/chroot_local-hooks. I keep backup copies of the scripts at the top level so that I can wipe the config/ directory and rebuild it from scratch.
I keep copies of the files that will be included in MyConfigIncludes/


To make (large) changes to the phone server, you build a new, complete USB image from scratch.
Create scripts to customize the images
You copy the new image to a stick, test on a spare machine, then when you are ready to switch over, you shut down the phone server, swap sticks, and reboot. If the new system fails, fall back to the old stick and try again.


The build process described below includes all configuration settings. There should not be any tweaking of the finished USB stick required. If you tweak it in the test phase, then make the changes permanent by updating the build settings and building a new stick before releasing it on the phone server.  
'''''nn-name''.sh''' where 'nn' is a number to control execution order, and 'name' is a meaningful name, for example '''01-password.sh''' would be used to install local user accounts and set user and root passwords.


Don't fiddle with the server while it's running. It's behind a firewall and it has no writable hard drive, so it is not too too prone to being hacked and if it is hacked they can't do much that can't be undone with a reboot.
== Networking ==


'''The exception''' to this (of course there is always an exception) is the phone system settings in /etc/asterisk.
Depending on how I deploy things, wired or wifi might be easier.
These files change frequently, so you have to be able to edit them.
From my notes below I have concluded wired is easier!
'''TODO - make them "COW" files or save them in MySQL.'''


=== Useful links ===
=== Wired network ===


* For my personal notes on using Debian Live on a laptop see http://www.wildsong.biz/index.php?title=Walltop
I ended up pulling a USB-to-ethernet adapter out of my junkbox. It's a 3COM 3C19250 from a 3COM [[Audrey]]. I hooked it up to my VirtualBox simulated walltop and it started right up. Now I have to do the DHCP set up in Debian Live and see if it works on the Dell hardware.
* [http://wiki.debian.org/DebianLive Debian Live wiki]
* [http://live.debian.net/manual/html/ch03s03.html Building an USB/HDD image]


=== Developer notes ===
=== WiFi Network ===


I want a minimal server, with just the addition of packages that make life with Asterisk bearable. The server handles phones and faxes. It keeps its call log files on Kilchis via mysql. There are no modems, just a 4 port "Wildcard" to connect to the phone company. It needs to be able to send email notices.
These are WiFi cards I ''was'' considering using. They are still in my junk box but when I actually went to plug one in, I found that this Dell's PC card slots are messed up, so instead I plugged in an ASUS USB adapter.


Currently voicemail messages get stored on this server. I might change that by using an NFS filesystem on Kilchis. It would be nice to get Apache off of the phone server.
D-Link DW650M
http://sourceforge.net/apps/mediawiki/ndiswrapper/index.php?title=D-Link_DWL-G650M


Hylafax has not been completely set up, we can receive faxes but there is no fancy Windows client to send faxes. There was some reason I had to build it from sources. See the [[Fax]] page. I think I should run the server portion on the phone server and the client(s) on Kilchis.
Microsoft MN-720


I included flite ("festival lite") to allow text-to-speech but have not used it yet. Should remove it if we're not going to use it.
I have not completed testing of ndiswrapper since I switched to using the ASUS USB adapter. Here are my notes for the NEXT walltop. I have several more laptops...


==== Asterisk MySQL integration ====
To use these I need to use the manufacturer's drivers + ndiswrapper.
http://wiki.debian.org/NdisWrapper


The DebianLive setup uses all the Debian Asterisk packages, so for MySQL
In chroot environment
the package is called asterisk-mysql. See /usr/share/doc/asterisk-mysql, especially the examples directory which contains setup files.
m-a prepare
m-a a-i ndiswrapper
echo ndiswrapper >> /etc/modules


==== TODO LIST ====
==== WiFi Security settings ====


I copied the /usr/local stuff from (the old) Roaring and need to make sure I can build it from scratch on the development server.
With this device it's just a matter of plugging it in and then getting the correct security settings for the network. I was able to turn off security on my Linksys and get a connection. Since my ultimate goal is to take this to work and hang it on the wall there, turning security at the WAP off is not an option.


=== Build procedure ===
I first I spent a couple hours wrestling with getting it to work with wpa_supplicant on an Ubuntu desktop. I tried all sorts of combinations of security settings to no avail. Very frustrating.


First time around, install the live-cd packages the build host, "apt-get install live-cd"
Then I found [http://wicd.sourceforge.net/ wicd]. I installed it (apt-get install wicd), started the daemon (sudo wicd) and the client (wicd-client -n) and had a link up in about 60 seconds. Conclusion: '''USE WICD'''!!


* This list does not include the hylafax support yet. I currently only included the generic hylafax package for testing.
What I actually ended up doing was installing wicd, using it to set up wpa_supplicant, and then removing it from my installation. The wpa_supplicant configuration that worked that I created with wicd-curses looks like this
* I use [[Dev]] as the build host.
* I work in a subdirectory on the RAID array, /mnt/stripe/DebianLive
* I work su'ed to root, because the build stage requires it.
* I might be building on a 64 bit machine so I have to say '''-k 686''' to get the 32 bit kernel.
* I used to include the '''minimal''' keyword but it left out things like networking and vi.


Clean out the build area.
ap_scan=1
  lh_clean --binary
ctrl_interface=/var/run/wpa_supplicant
  network={
      ssid="wildsong"
      scan_ssid=0
      proto=WPA RSN
      key_mgmt=WPA-PSK
      pairwise=CCMP TKIP
      group=CCMP TKIP
      psk=67c4e0a7ff7736641fdf9bc8094c45a8b7c60a33f45321f6c3d08f42ec0397af
}


I used a script to configure and copy appropriate files around. See Configure.sh
Check the downloads page for more documentation


Configure.sh has code something like this
'''In Debian Lenny''', wicd is a [http://www.backports.org/dokuwiki/doku.php?id=instructions backport], so installing it requires additional work. Add this to /etc/apt/sources.list; like this


  lh_config -b usb-hdd -k 686 --bootstrap-flavour \
  echo 'deb http://www.backports.org/debian lenny-backports main contrib non-free ' > config/chroot_sources/backports-wicd.chroot
  --packages-lists "stripped" --binary-indices disabled\
wget -O - http://backports.org/debian/archive.key -O config/chroot_sources/backports-wicd.binary.gpg
  --memtest "none"\
  --packages "asterisk mysql-client libsox-fmt-mp3\
  hylafax-server iaxmodem\
  festival festvox-kallpc16k \
  apache2-mpm-prefork php5-mysql php-pear\
  openssh-server portmap nfs-common autofs\
  debconf-english"\
  --bootappend-live "nolocales" --syslinux-timeout 50


Next it copies files and scripts.
NOTE '''Backports is also required for the USB firmware'''


I add scripts to config/chroot_local-hooks. I keep backup copies of the scripts at the top level so that I can wipe the config/ directory and rebuild it from scratch.
Then in the chroot environment I do this
I keep copies of the files that will be included in MyConfigIncludes/
apt-get update
 
apt-get install debian-backports-keyring
Create scripts to customize the images
apt-get -t lenny-backports install wicd
 
'''''nn-name''.sh''' where 'nn' is a number to control execution order, and 'name' is a meaningful name, for example '''01-password.sh''' would be used to install local user accounts and set user and root passwords.


The simple next step, the build.
...which installs about a zillion more dependent packages! All just to get my  wireless link going!
A complete build takes about 15 minutes on Dev.


lh_build
== SSH services ==


If the build succeeds there will be a file called binary.img in the top directory.
The lsh-server is a small SSH server.


=== Testing ===
By default it generates keys on the first run, which alas is every time on a Debian Live system. So I generate keys on the development host and copy them into the config tree.


To test the image in a virtual machine, you can either start it in qemu or convert the img file to a vmdk and use vmware.  
This is how I generate the seed file and keys.  


Of course, you can also the virtual machine to boot from the USB stick but testing the img file first means you don't have to keep copying the image to the stick.)
mkdir ~/.lsh && cd ~/.lsh
lsh-make-seed --sloppy -o yarrow-seed-file
lsh-keygen | lsh-writekey


"Qemu" is installed on 'dev' already. You need to set up an X11 connection back to your desktop to use it, if you are burdened with a Windows machine see the [[Cygwin]] page. When you have an xterm window open on your desktop, type 'qemu binary.img' and wonder at the marvels of modern technology.
== Testing ==


Once the Qemu window captures your mouse you can escape with Ctl-Alt.
To test the image in a virtual machine, you can either start it directly in qemu or convert the img file to a vdi and use [[VirtualBox]]
Thought you might want to know that.


=== Test plan ===
I really don't like using Qemu so I deleted the instructions that I used to have here. I don't intend to use it again.


# Test the image in an emulator.
Converting the IMG file to a VDI file
# Test the usb stick in the backup computer.
# Test on real hardware. (When ready to go live.)


==== Testing image in Qemu ====
VBoxManage convertfromraw -format VDI binary.img binary.vdi


There are clever ways to set up Qemu networking. It requires setting up a TAP interface on the host. Not sure if I am up to that. I think [http://compsoc.dur.ac.uk/~djw/qemu.html this is the proper way to do it] but I don't want to accidentally shut down [[Dev]] right now.
Now you can create a virtual machien and mount the VDI as a virtual disk and boot from it. It boots about 10 times faster on the development system as on the real computer. Poor little obsolete laptop!


Here is the command to start the image in [http://www.nongnu.org/qemu/ qemu]. This MAC number is one digit off from the real thing. (24 vs 25) ([http://www.gnome.org/~markmc/qemu-networking.html qemu networking hints])
You can also the virtual machine to boot from the USB stick but testing the img file first means you don't have to keep copying the image to the stick.)


qemu -net nic,model=rtl8139,vlan=1,macaddr=00:e0:29:93:3a:25 binary.img
== Deployment ==


 
Copy the image to a CF card, completely overwriting it: '''dd if=binary.img of=''<devicename>'''''. You can get the device name with '''dmesg''', it will be buried in the last few messages after you insert the stick. Something like /dev/sda. Don't use the first partition (which would be /dev/sda1), use the whole drive, you have to overwrite everything there including the boot block and the partition table.
 
 
 
==== Testing on the real hardware (with Wildcard in place) ====
 
Repeat all image and offline tests.
 
Test phone system.
* Interoffice - Place a call from one extension to another
* Place a test call to extension 100 to test the auto-attendant functions.
* Call out using a local number
* Call out using a long distance (VOIP call)
* Call into the office from a cellphone.
* Test the voicemail system (extension 85 or the voicemail button)
* Try each incoming phone number including the fax line. (See [[Phone_Book]])
* Make sure the calls are being logged in the MySQL server.
 
Test fax system.
* Generate a fax and see if it arrives on the server. (See [[Fax]] page.)
* Make sure it forwarded the fax over to the email system. (Ask John or Brian)
* Send a fax from the command line and see if it went out (check email notices too.)
 
Test UPS daemon
* Does the apcupsd daemon work? (Should be able to ask it how the batteries are doing.)
 
=== Deployment ===
 
Copy the image to a USB stick, completely overwriting it: '''dd if=binary.img of=''<devicename>'''''. You can get the device name with '''dmesg''', it will be buried in the last few messages after you insert the stick. Something like /dev/sda. Don't use the first partition (which would be /dev/sda1), use the whole drive, you have to overwrite everything there including the boot block and the partition table.


'''Note: If you select the wrong device name you can make the host system unbootable in about 250 mS. If you do this, don't come whining to me about it. Fix it.'''
'''Note: If you select the wrong device name you can make the host system unbootable in about 250 mS. If you do this, don't come whining to me about it. Fix it.'''
To use in the target system, simply plug in the stick and reboot it. You have to set it to boot from USB in BIOS. If you can't set it, get a newer computer!
Incidentally installing Linux onto the USB stick makes it unusable in Windows. If you want to use it in Windows again ever you will need to partition it and create a FAT filesystem on it.

Latest revision as of 05:32, 6 July 2010

WallTop computers... the concept is to recycle an old laptop by removing all the extraneous parts such as the cdrom drive, floppy drive, (dead) battery and then hanging it on the wall.

Available hardware

My first attempt is based on a Dell Inspiron 3700 C466GT.

  • 466 MHz Celeron processor
  • 256 MB PC100 SODIMM memory
  • one PATA slot
  • two broken PC card slots
  • one USB port

Removed: case, 4200 RPM hard drive, dead battery

Added: a shadow box frame from Michaels, a power supply from OSUsed, a CF to 44pin PATA adapter, a 1GB CF card, and an ASUS 802.11g WiFi USB adapter

I had to modify the frame to add cooling slots.

This laptop will only boot when you touch its power on button. To make the button accessible I mounted the motherboard upside down (what used to be the top is towards the wall when it's hanging up. I drilled a hole in the back about 3/8" diameter. You can poke the button with a pencil eraser to boot it up. Yes.. its a pain.

More hardware available for future projects

Micron TransPort GX2: Pentium III 1.2Ghz

  • 15-inch LCD at 1,280-by-1,024

http://www.pcmag.com/article2/0,2817,7733,00.asp

Micron TransPort XT Notebook Computers CPU: Intel Pentium III 750 ~ 850MHz

  • Standard Memory: 64MB~256MB
  • Maximum Memory: 512MB

14" screen

http://www.pcworld.com/article/54784/micronpc_launches_transport_xt_notebook.html

The software

Which distribution to use?

After much research and experimentation I settled on Debian Live!

This allows me to build an image on a big fancy Ubuntu desktop system (Raven) and test it in qemu.

Once the image is built I transfer it to a Compact Flash card, which will be plugged into an IDE adapter and replace the incredibly noisy stock 4200 rpm hard drive.

I am also now using Debian Live! to build Asterisk phone systems.

Some other options that I investigated:

  • Debian
  • Damn Small Linux
  • Puppy Linux (which immediately panics on boot)
  • Movix
  • Ubuntu, building a custom Live CD

Debian Live! installation

Debian Live wiki

Building an USB/HDD image

FluxBox

Install the tools to build Debian Live! systems 

apt-get install live-helper

Build an image. 

lh_clean --binary
lh_config -b usb-hdd -k 686 --bootstrap-flavour minimal\
--packages-lists "stripped" --binary-indices disabled\
--memtest "disabled"\
--packages "x-window-system-core fluxbox\
openssh-server vlc gnash portmap nfs-common\
autofs debconf-english"\
--bootappend-live "nolocales" --syslinux-timeout 50

I build on a 64 bit machine so I have to say -k 686 to get the 32 bit kernel

Add scripts to config/chroot_local-hooks

02-fix_inittab.sh - changes runlevel to 5 and adds the tty7 login line so I have only one login running instead of default 5

40-bash_profile.sh - append or create a .bash_profile script that will run a script from nfs and then do a 'startx'.

50-windowmanager.sh - configures fluxbox startup files

99-make-export.sh - make the directories needed for autofs

Add files to config/chroot_local-includes I add the autofs.* files that I use to mount nfs servers.

Doing customizations, do this (as root) 

lh_clean --binary
lh_config
lh_bootstrap
# Prepare for a chroot system so you can do hacks
lh_chroot
lh_chroot_hosts install
lh_chroot_resolv install
lh_chroot_proc install
chroot chroot
#do the hacks here, for example "apt-get install asterisk".
exit
# Now remove the changes make to do chroot
lh_chroot_hosts remove
lh_chroot_resolv remove
lh_chroot_proc remove
# I wonder what this does
lh_binary
# Build the image
lh_build

Copy image to CF: dd if=binary.img of=${USBSTICK}

To test image, start in qemu or convert img file to a vmdk and use vmware

To use in walltop, transfer CF to laptop and boot it

Customization that I might want to do 

other codecs???
emacs21-nox
libcurl3
realplayer?
firefox - use iceweasel, unless like me your laptop is puny, then forget it!
flash - use gnash??

I need something to do a slide show of pictures, driven from command line. Image-magick supports this.

Starting X / fluxbox without a window manager http://www.debianadmin.com/how-to-auto-login-and-startx-without-a-display-manager-in-debian.html

Building a working image

To make (large) changes, you build a new, complete image from scratch. You copy the new image to CF, put it in the computer, and boot.

I add scripts to config/chroot_local-hooks. I keep backup copies of the scripts at the top level so that I can wipe the config/ directory and rebuild it from scratch. I keep copies of the files that will be included in MyConfigIncludes/

Create scripts to customize the images

nn-name.sh where 'nn' is a number to control execution order, and 'name' is a meaningful name, for example 01-password.sh would be used to install local user accounts and set user and root passwords.

Networking

Depending on how I deploy things, wired or wifi might be easier. From my notes below I have concluded wired is easier!

Wired network

I ended up pulling a USB-to-ethernet adapter out of my junkbox. It's a 3COM 3C19250 from a 3COM Audrey. I hooked it up to my VirtualBox simulated walltop and it started right up. Now I have to do the DHCP set up in Debian Live and see if it works on the Dell hardware.

WiFi Network

These are WiFi cards I was considering using. They are still in my junk box but when I actually went to plug one in, I found that this Dell's PC card slots are messed up, so instead I plugged in an ASUS USB adapter.

D-Link DW650M http://sourceforge.net/apps/mediawiki/ndiswrapper/index.php?title=D-Link_DWL-G650M

Microsoft MN-720

I have not completed testing of ndiswrapper since I switched to using the ASUS USB adapter. Here are my notes for the NEXT walltop. I have several more laptops...

To use these I need to use the manufacturer's drivers + ndiswrapper. http://wiki.debian.org/NdisWrapper

In chroot environment 

m-a prepare
m-a a-i ndiswrapper
echo ndiswrapper >> /etc/modules

WiFi Security settings

With this device it's just a matter of plugging it in and then getting the correct security settings for the network. I was able to turn off security on my Linksys and get a connection. Since my ultimate goal is to take this to work and hang it on the wall there, turning security at the WAP off is not an option.

I first I spent a couple hours wrestling with getting it to work with wpa_supplicant on an Ubuntu desktop. I tried all sorts of combinations of security settings to no avail. Very frustrating.

Then I found wicd. I installed it (apt-get install wicd), started the daemon (sudo wicd) and the client (wicd-client -n) and had a link up in about 60 seconds. Conclusion: USE WICD!!

What I actually ended up doing was installing wicd, using it to set up wpa_supplicant, and then removing it from my installation. The wpa_supplicant configuration that worked that I created with wicd-curses looks like this 

ap_scan=1
ctrl_interface=/var/run/wpa_supplicant
network={
      ssid="wildsong"
      scan_ssid=0
      proto=WPA RSN
      key_mgmt=WPA-PSK
      pairwise=CCMP TKIP
      group=CCMP TKIP
      psk=67c4e0a7ff7736641fdf9bc8094c45a8b7c60a33f45321f6c3d08f42ec0397af
}

Check the downloads page for more documentation

In Debian Lenny, wicd is a backport, so installing it requires additional work. Add this to /etc/apt/sources.list; like this 

echo 'deb http://www.backports.org/debian lenny-backports main contrib non-free ' > config/chroot_sources/backports-wicd.chroot
wget -O - http://backports.org/debian/archive.key -O config/chroot_sources/backports-wicd.binary.gpg

NOTE Backports is also required for the USB firmware

Then in the chroot environment I do this 

apt-get update
apt-get install debian-backports-keyring
apt-get -t lenny-backports install wicd

...which installs about a zillion more dependent packages! All just to get my wireless link going!

SSH services

The lsh-server is a small SSH server.

By default it generates keys on the first run, which alas is every time on a Debian Live system. So I generate keys on the development host and copy them into the config tree.

This is how I generate the seed file and keys. 

mkdir ~/.lsh && cd ~/.lsh
lsh-make-seed --sloppy -o yarrow-seed-file
lsh-keygen | lsh-writekey

Testing

To test the image in a virtual machine, you can either start it directly in qemu or convert the img file to a vdi and use VirtualBox

I really don't like using Qemu so I deleted the instructions that I used to have here. I don't intend to use it again.

Converting the IMG file to a VDI file 

VBoxManage convertfromraw -format VDI binary.img binary.vdi

Now you can create a virtual machien and mount the VDI as a virtual disk and boot from it. It boots about 10 times faster on the development system as on the real computer. Poor little obsolete laptop!

You can also the virtual machine to boot from the USB stick but testing the img file first means you don't have to keep copying the image to the stick.)

Deployment

Copy the image to a CF card, completely overwriting it: dd if=binary.img of=<devicename>. You can get the device name with dmesg, it will be buried in the last few messages after you insert the stick. Something like /dev/sda. Don't use the first partition (which would be /dev/sda1), use the whole drive, you have to overwrite everything there including the boot block and the partition table.

Note: If you select the wrong device name you can make the host system unbootable in about 250 mS. If you do this, don't come whining to me about it. Fix it.

Retrieved from "https://wiki.wildsong.biz//index.php?title=Walltop&oldid=5891"