View Single Post
Old 10-11-2007, 02:54 PM   #36
jharker
Developer
jharker could sell banana peel slippers to a Deveel.jharker could sell banana peel slippers to a Deveel.jharker could sell banana peel slippers to a Deveel.jharker could sell banana peel slippers to a Deveel.jharker could sell banana peel slippers to a Deveel.jharker could sell banana peel slippers to a Deveel.jharker could sell banana peel slippers to a Deveel.jharker could sell banana peel slippers to a Deveel.jharker could sell banana peel slippers to a Deveel.jharker could sell banana peel slippers to a Deveel.jharker could sell banana peel slippers to a Deveel.
 
Posts: 345
Karma: 3473
Join Date: Apr 2007
Location: Brooklyn, NY, USA
Device: iRex iLiad v1, Blackberry Tour, Kindle DX, iPad.
Yes, I agree with Adam. It used to be that the 'unbrickable' package was the only way to recover if something went wrong with your iLiad. Now that iRex includes the 'reflash from CF' feature with shell access, the 'unbrickable' package isn't necessary for that.

Instead, 'unbrickable' is a very easy way to access the iLiad's filesystem by logging on via SSH. Once 'unbrickable' is installed, every time your iLiad boots it will turn on wired (or wireless?) networking and start an SSH server. If you plug into your network, you'll be able to log in as root over SSH.

The drawback to this is that having wired/wireless networking running draws some extra power. Since 'unbrickable' is set to run them automatically at boot, you have to turn them off manually if you want to save power.

In my opinion, if you're not a developer, there's no reason to install 'unbrickable'. If you're in a position to mess up your iLiad, then you already have the iRex reflash tool installed anyway.
jharker is offline   Reply With Quote