linux tools coming to MCR

[Guest freeasabeer]

I don't have this issue...

I suspect it's once again an issue with your 2.1 rom which not well designed :)

Can it be that /init.rc lacks the TERMINFO definition ? If this is the case, then please add the following line:

export TERMINFO /system/etc/terminfo

at the begining of /init.rc along with the other "export foo" lines. You will need to tweak your custom rom to achieve this....

As an alternative you can also write a wrapper script to start nano that will export TERMINFO before launching nano.

Edited March 26, 2010 by freeasabeer

[Guest cowai]

I don't have this issue...

I suspect it's once again an issue with your 2.1 rom which not well designed :)

Can it be that /init.rc lacks the TERMINFO definition ? If this is the case, then please add the following line:

export TERMINFO /system/etc/terminfo

at the begining of /init.rc along with the other "export foo" lines. You will need to tweak your custom rom to achieve this....

As an alternative you can also write a wrapper script to start nano that will export TERMINFO before launching nano.

That gives me a "bad variable name".

terminfo is not listed in export. Got any tips?

[Guest cowai]

"export TERMINFO=/system/etc/terminfo" works. But nano is giving me the same error :/

[Guest freeasabeer]

"export TERMINFO=/system/etc/terminfo" works. But nano is giving me the same error :/

Villain ROM does not include terminfo stuff.

Please install the terminfo package, I will update the nano package tonight to add this dependency to terminfo.

[Guest Andcr]

Hi again..

I installed VillaROM 5.0 which is a ported version of the CDMA Hero 2.1 ROM

I followed the steps from the first thread but get the following:

# /data/xbin/opkg install /sdcard/opkg_0.1.7+svn519-2_arm.ipk

Collected errors:

 * opkg_conf_init: Couldn't stat /data/local/opkg.conf: No such file or directory.

# /data/xbin/opkg install /sdcard/opkg_0.1.7+svn519-2_arm.ipk

Installing opkg (0.1.7+svn519-2) to root...

Existing conffile /data/local/opkg.conf is different from the conffile in the new package. The new conffile will be placed at /data/local/opkg.conf-opkg.

Configuring opkg.

# opkg update

opkg: not found

# su

# opkg update

opkg: not found

first it doesn't see the .conf file, then I create it and it says it isn't the same

did I do something wrong?

thanks in advance!

btw. if this works, what feed should I use for this rom?

[Guest freeasabeer]

# /data/xbin/opkg install /sdcard/opkg_0.1.7+svn519-2_arm.ipk

Collected errors:

 * opkg_conf_init: Couldn't stat /data/local/opkg.conf: No such file or directory.

This warning can be safely ignored.

# /data/xbin/opkg install /sdcard/opkg_0.1.7+svn519-2_arm.ipk

Installing opkg (0.1.7+svn519-2) to root...

Existing conffile /data/local/opkg.conf is different from the conffile in the new package. The new conffile will be placed at /data/local/opkg.conf-opkg.

Configuring opkg.

Everything's ok here.

# opkg update

opkg: not found

# su

# opkg update

opkg: not found

This means that /data/xbin is not in the PATH. So, either update Villain's ROM /init.rc to add /data/xbin in the PATH definition (this one is tricky as you need to unpack the update zip file, then unpack the boot.img, edit init.rc, then repack boot.img, repack the update zip and finally resign it before flashing the whole thing). Or remember to type

export PATH=/data/xbin:$PATH

every time you start a shell session.... Unless we can use a .profile file somewhere (well where ash believe the HOME directory is, and this might be again different between MCR and Villain).

btw. if this works, what feed should I use for this rom?

I think you should use the cyanogen feed + the common feed. Definitively not the mcr feed.

Edited March 31, 2010 by freeasabeer

[Guest Andcr]

thanks a lot for your fast reply

kendon was so kind to provide an update.zip with the needed modifications and nprussel said it's include in VillainROM 5.03

it starts now but I get an error:

# opkg update

Downloading http://freeasabeer.byethost33.com/android/feed/common/Packages.gz.

wget: bad address 'freeasabeer.byethost33.com'

Downloading http://freeasabeer.byethost33.com/android/feed/cyanogen/Packages.gz.

wget: bad address 'freeasabeer.byethost33.com'

Collected errors:

 * opkg_download: Failed to download http://freeasabeer.byethost33.com/android/feed/common/Packages.gz, wget returned 1.

 * opkg_download: Failed to download http://freeasabeer.byethost33.com/android/feed/cyanogen/Packages.gz, wget returned 1.

while searching this topic I found that it had something to do with resolv.conf or busybox

I did have to install another busybox than the one that was provided in the rom because Titanium Backup asked me to..

[Guest freeasabeer]

Oh dear... the egg and chicken story then...

you definitively need my version of busybox + a valid /etc/resolv.conf file !

Meanwhile, can you try try edit the opkg.conf file and replace all instances of freeasabeer.byethost33.com by 209.190.85.13 ?

[Guest Andcr]

edited opkg.conf and now I get

# opkg update

Downloading http://209.190.85.13/android/feed/common/Packages.gz.

wget: bad address 'mybookface.net'

Downloading http://209.190.85.13/android/feed/cyanogen/Packages.gz.

wget: bad address 'mybookface.net'

Collected errors:

 * opkg_download: Failed to download http://209.190.85.13/android/feed/common/Packages.gz, wget returned 1.

 * opkg_download: Failed to download http://209.190.85.13/android/feed/cyanogen/Packages.gz, wget returned 1.

is there any way to install your version of busybox again after installing another one?

[Guest freeasabeer]

It was worth trying...

Download the busybox ipk (cyanogen variant): http://freeasabeer.byethost33.com/android/....16.0-2_arm.ipk on your sdcard and install it from there.

So you'll get the egg for the chicken :P

[Guest Andcr]

thanks! I like my eggs fresh :P

I really hate but I still have to bug you :(

/sdcard # opkg install busybox_cyanogen_1.16.0-2_arm.ipk 

Installing busybox (1.16.0-2) to root...

Configuring busybox.

ln: ./resolv.conf: File exists

mount: mounting /dev/block/mtdblock3 on /system failed: Device or resource busy

update gives an error

/sdcard # opkg update

Downloading http://209.190.85.13/android/feed/common/Packages.gz.

Inflating http://209.190.85.13/android/feed/common/Packages.gz.

Updated list of available packages in /data/local/opkg/lib/opkg/lists/common.

Downloading http://209.190.85.13/android/feed/cyanogen/Packages.gz.

Inflating http://209.190.85.13/android/feed/cyanogen/Packages.gz.

Updated list of available packages in /data/local/opkg/lib/opkg/lists/cyanogen.

Collected errors:

 * unzip: Invalid gzip magic

 * unzip: Invalid gzip magic

installing rsync gives an error

/sdcard # opkg install rsync

Collected errors:

 * opkg_install_cmd: Cannot install package rsync.

but when I try to re-install opkg it sees that it has the current version installed so the listing of packages somehow seems ok

/sdcard # opkg install opkg

Package opkg (0.1.7+svn519-2) installed in root is up to date.

any more tips?

and thanks again for your continued help and patience

[Guest freeasabeer]

mount: mounting /dev/block/mtdblock3 on /system failed: Device or resource busy

I don't really like that one. Busybox update might have actually failed.

* unzip: Invalid gzip magic

* unzip: Invalid gzip magic

Downloaded files are corrupted.

Can you try to revert the previous opkg.conf changes (e.g. revert to the former URL instead of the hard coded IP address) ?

Collected errors:

* opkg_install_cmd: Cannot install package rsync.

No idea about that one !

but when I try to re-install opkg it sees that it has the current version installed so the listing of packages somehow seems ok

/sdcard # opkg install opkg

Package opkg (0.1.7+svn519-2) installed in root is up to date.

If you really want to reinstall, then use the --force-reinstall option.

[Guest Andcr]

yay, the egg turned into a chicken :P

it works now!

I opened SUFBS and mounted system and data as RW and the installed busybox again

# opkg install busybox_cyanogen_1.16.0-2_arm.ipk

Installing busybox (1.16.0-2) to root...

Configuring busybox.

ln: ./resolv.conf: File exists

then first tried with the IP in the .conf but got the same error

# opkg update

Downloading http://209.190.85.13/android/feed/common/Packages.gz.

Inflating http://209.190.85.13/android/feed/common/Packages.gz.

Updated list of available packages in /data/local/opkg/lib/opkg/lists/common.

Downloading http://209.190.85.13/android/feed/cyanogen/Packages.gz.

Inflating http://209.190.85.13/android/feed/cyanogen/Packages.gz.

Updated list of available packages in /data/local/opkg/lib/opkg/lists/cyanogen.

Collected errors:

 * unzip: Invalid gzip magic

 * unzip: Invalid gzip magic

then changed IP back to URL and this worked great

# opkg update

Downloading http://freeasabeer.byethost33.com/android/feed/common/Packages.gz.

Inflating http://freeasabeer.byethost33.com/android/feed/common/Packages.gz.

Updated list of available packages in /data/local/opkg/lib/opkg/lists/common.

Downloading http://freeasabeer.byethost33.com/android/feed/cyanogen/Packages.gz.

Inflating http://freeasabeer.byethost33.com/android/feed/cyanogen/Packages.gz.

Updated list of available packages in /data/local/opkg/lib/opkg/lists/cyanogen.

and now installed rsync just fine

# opkg install rsync

Installing rsync (3.0.6-1) to root...

Downloading http://freeasabeer.byethost33.com/android/feed/common/rsync_3.0.6-1_arm.ipk.

Installing dropbear (0.52-1) to root...

Downloading http://freeasabeer.byethost33.com/android/feed/cyanogen/dropbear_cyanogen_0.52-1_arm.ipk.

Configuring dropbear.

Configuring rsync.

thanks for all the help!

gonna keep this text for future references in case I mess up again :(

[Guest freeasabeer]

Excellent !

Your painfull attempt to get opkg properly working on your rom led me to start developping a very basic (and very ugly as well) android application that will do all the boostrap and initial egg & chicken stuff for you...

Stay tuned, it should arrive soon here...

[Guest Andcr]

Your painfull attempt to get opkg properly working on your rom led me to start developping a very basic (and very ugly as well) android application that will do all the boostrap and initial egg & chicken stuff for you...

oh my, that's cool!

I'm sure this will come in handy in the near future for me and for a lot of other users

[Guest freeasabeer]

if there are brave enough people to test the babe... here it is bootstrap.zip !

The apk is inside the zip file, so just unzip and install with

adb install bootstrap.apk

Then I hope it should be straithforward.... (just don't forget to have an internet connection ON before starting the bootstrap)!

[Guest Andcr]

I flashed the Semi-Vanillain 1.0, connected to wifi and installed the .apk through SUFBS on my phone instead of adb

install went fine, it started ok

it downloaded busybox, opkg and installed then ok but in the end I got the message

Writing a default opkg config file in: /data/local/opkg.conf: Parent directory of file is not writable: /data/local/opkg.conf

All done !

when I then opened SUFBS and typed

su

opkg

I got the message not found

I rebooted but that didn't change anything

then I opened SUFBS and remounted system and data as RW and installed and ran the application again but the result was the same

perhaps I'm just cursed :P

it does look like a great tool, and easy!

[Guest cowai]

Andcr: try running /data/xbin/opkg instead.

[Guest freeasabeer]

@Andcr: thanks for the feedback... and as a result an updated version that should fix the

Parent directory of file is not writable: /data/local/opkg.conf

issue.

bootstrap.zip

[Guest Andcr]

I tried the new version on the VillainROM 5 and VanillainROM (both based on CDMA port) and both give the same not found error

also both seem to already have rsync installed but not opkg

I did try /data/xbin/opkg as cowai suggested but only tried it on the VillainROM but forgot it on the Vanillain, on the Villain it didn't make any difference

for me it's all ok because rsync seems to be pre-installed but if you need someone to test this application I would very much like to do so :P

[Guest freeasabeer]

I've finally installed Villain 5.2 on my Hero to be able to debug the whole thing myself!

1) it appears that V(an)illain ROMs should be considered as Modaco like ROMs and not as Cyanogen like ROMs from an ipk point of view. So I have added V(an)illain as a new option.

2) I have an updated boostrap (v 1.2) bootstrap_1.2.zip that really works on my phone with a Villain ROM. (It was already working with MCR 3.2).

[Guest Andcr]

I've finally installed Villain 5.2 on my Hero to be able to debug the whole thing myself!

1) it appears that V(an)illain ROMs should be considered as Modaco like ROMs and not as Cyanogen like ROMs from an ipk point of view. So I have added V(an)illain as a new option.

2) I have an updated boostrap (v 1.2) bootstrap_1.2.zip that really works on my phone with a Villain ROM. (It was already working with MCR 3.2).

I still have the "not found" on my current VillainROM

I have 5.1 and I think you have installed 5.02 as 5.1 is the highest number available now

When I install and click run the app, everything gives the message OK but when I type

opkg

or

su

opkg

I still get not found

even after a reboot..

I tried from SUFBS and adb..

[Guest freeasabeer]

Yeah, it was 5.1..

Until nprussell does add /data/xbin into the PATH definition, you'll still have the "not found" issue.

But if you call opkg explicitely (e.g. /data/xbin/opkg) it should work as expected (at least it did on my phone yesterday).

[Guest Andcr]

But if you call opkg explicitely (e.g. /data/xbin/opkg) it should work as expected (at least it did on my phone yesterday).

:P oops :(

I forgot about the path as he said he added it in 5.01 I thought it would also be included in 5.1.

Or I might have messed up myself by trying to install OpenVPN which might have changed the boot..

anyways thanks :(

this is working great now!

[Guest Pitel]

I have following problems with installing mc:

Installing mc (4.6.2-1) to root...

Downloading [url="http://freeasabeer.byethost33.com/android/feed/common/mc_4.6.2-1_arm.ipk"]http://freeasabeer.byethost33.com/android/...4.6.2-1_arm.ipk[/url].

Installing terminfo (5.6-1) to root...

Downloading [url="http://freeasabeer.byethost33.com/android/feed/common/terminfo_5.6-1_arm.ipk"]http://freeasabeer.byethost33.com/android/...o_5.6-1_arm.ipk[/url].

Configuring terminfo.

Configuring mc.

Collected errors:

 * extract_archive: Cannot make dir /system/etc/terminfo/x/: Read-only file system.

 * wfopen: /system/etc/terminfo/x/xterm-xfree86: No such file or directory.

 * wfopen: /system/etc/terminfo/x/xterm: No such file or directory.

 * wfopen: /system/etc/terminfo/x/xterm-color: No such file or directory.

 * extract_archive: Cannot make dir /system/etc/terminfo/a/: Read-only file system.

 * wfopen: /system/etc/terminfo/a/ansi: No such file or directory.

 * extract_archive: Cannot make dir /system/etc/terminfo/d/: Read-only file system.

 * wfopen: /system/etc/terminfo/d/dumb: No such file or directory.

 * extract_archive: Cannot make dir /system/etc/terminfo/v/: Read-only file system.

 * wfopen: /system/etc/terminfo/v/vt220: No such file or directory.

 * wfopen: /system/etc/terminfo/v/vt100: No such file or directory.

 * wfopen: /system/etc/terminfo/v/vt102: No such file or directory.

 * extract_archive: Cannot create symlink from ./system/etc/terminfo/v/vt200 to 'vt220': No such file or directory.[/codebox]