Welcome to the EternityProject's WebTop Modifications Thread for Motorola RAZR
...:: Unleash your Gentoo Power! ::...
What do we need?
A brain...... And willing to unleash the power of your device.... :°)
Download:
GenTop for Motorola RAZR - v0.2: HERE
domain_policy.conf: HERE
sudoers: HERE
Changelog:
Code:
v0.2:
- World has been updated (01/2012)
- Recompiled most things with NEON support
- Portage bug solved (can now emerge without tricks)
v0.1:
- First release
History:
GenTop for Motorola RAZR - v0.1: HERE
Instructions:
1. UnBz2/UnTar the archive
2. Copy the IMG file on the root of your external sdcard
3. Execute the scripts
4. Enjoy!
Script:
Only for the first time setup:
Code:
adb push domain_policy.conf /tmp/
adh push sudoers /tmp/
adb shell
su
cp domain_policy.conf /etc/tomoyo/
cp sudoers /etc/
chown root:root /etc/tomoyo/domain_policy.conf
chown root:root /etc/sudoers
chmod 440 /etc/sudoers
reboot
Then start WebTop and execute this:
Code:
su
/usr/bin/sudo -H -u adas bash
export DISPLAY=:0
xhost +
sudo -i
mknod -m640 /dev/loop94 b 7 94
mkdir /tmp/wtm
mount -o loop /sdcard-ext/eternitygentop.img /tmp/wtm
mount -o bind /proc /tmp/wtm/proc
mount -o bind /dev /tmp/wtm/dev
mount -o bind /dev/pts /tmp/wtm/dev/pts
mount -o bind /dev/shm /tmp/wtm/dev/shm
mount -o bind /proc/bus/usb /tmp/wtm/proc/bus/usb
mount -o bind /sys /tmp/wtm/sys
mount -o bind /tmp /tmp/wtm/tmp
mount -o bind /var/tmp /tmp/wtm/var/tmp
mount -o bind /var/run/dbus/ /tmp/wtm/var/run/dbus
mount -o bind /var/lib/dbus/ /tmp/wtm/var/lib/dbus
mount -o bind /sdcard /tmp/wtm/sdcard
mount -o bind /sdcard-ext /tmp/wtm/sdcard-ext
chroot /tmp/wtm /bin/bash
export DISPLAY=:0
xterm
The xterm window is acting on the new Gentoo system.
Replacing WebTop UI with Lightweight GNOME (only panels and metacity):
Code:
eprj_lightgnome
Replacing WebTop with Full GNOME:
Code:
eprj_fullgnome
Replacing WebTop UI with Lightweight GNOME (only panels and metacity -- manual):
Code:
kill $(ps -ef | grep 5000 | grep webtop-panel | cut -c10-15)
kill $(ps -ef | grep 5000 | grep apptray | cut -c10-15)
kill $(ps -ef | grep 5000 | grep metacity | cut -c10-15)
kill $(ps -ef | grep 5000 | grep xscreensaver | cut -c10-15)
sleep 3
gnome-panel &
metacity -c &
Replacing WebTop with Full GNOME (Manual):
Code:
kill $(ps -ef | grep 5000 | grep webtop-panel | cut -c10-15)
kill $(ps -ef | grep 5000 | grep apptray | cut -c10-15)
kill $(ps -ef | grep 5000 | grep metacity | cut -c10-15)
kill $(ps -ef | grep 5000 | grep webtop-wallpaper | cut -c10-15)
kill $(ps -ef | grep 5000 | grep xscreensaver | cut -c10-15)
sleep 3
gnome-session &
How to emerge packages:
Code:
cd /root
emerge --pretend --fetchonly MYEBUILD | sed -r '/^(ht|f)tp:\/\//{s/ +/\n/g;p};d' >urllist
xargs wget -nc -nd -P /usr/portage/distfiles/ <urllist
emerge MYEBUILD
rm -rf /usr/portage/distfiles/*
Replace "MYEBUILD" with your package's name.
Status:
Note that it is an alpha version so, not everything will work flawlessly and easily. If your network doesn't work, check /etc/resolv.conf.
The EternityProject Team Manager & Main Developer,
-kholk
EternityProject Team FTW! ^_^
Heh! When I promise something, I'll do. Unless you're a bad child.
Oh, forgetting to say and I didn't want to write that on first post, the GenTop image is intended to be used on a real MicroSD (first) ext4 partition if you want to install other things on it.
You know, Gentoo requires a lot of space when compiling
Great work. Looking forward to unleashing the Gentop!
I'll try and keep my extreme noobie questions to a minimum, but:
1. Do I need to root my phone?
2. So I paste these 3 (uncompressed) files onto the root directory of my SD card and open the 3 files using a file explorer. Does this open a terminal window where I type in the scripts you listed (similar to if I have a DOS window open on my PC?)
3. When I plug the phone into the lapdock, will I get a choice of whether it opens into webtop vs gentop?
Thanks.
1. Yup.
2. What a confusion... You should do the first time setup using a computer with ADB
3. No. It will simply boot WebTop, you'll replace it with GenTop later.
Thanks. I'll do some self directed learning before my next question
I'll start here: http://developer.android.com/guide/developing/tools/adb.html
Anyhow, I don't want to waste peoples time with too many overly basic questions. Your time is better spent developing this I still have to swap out my slightly defective phone, so probably won't get to installing this for about a week. In the mean time I'll read up on some of the basics...
Looking forward to try it out.
broken links got my hopes up here i miss gentoo
Oh, my bad, links fixed.
ArchTop would be the best option here IMHO. No need to compile-recompile especially on SD card which I believe will be affecting sd card life (lots of reads/writes cycles is bad for cards)
Link is not working for me...makes me a sad panda
Yup, I know. I'm really sorry for this, my head is giving me some bad jokes today.
Link re-fixed and tested. Now it works
Can you please explain how to create an ext4 partition to mount the gentop?
Unless you mean you want to get the IMG on an sdcard partition (in this case you should use fdisk and dd, and you can find more infos HERE) ....
....it's all written on first post.
Code:
export PATH=/data/local/bin:$PATH
[email protected]_spyder:/$ export PATH=/data/local/bin:$PATH
[email protected]_spyder:/$ su
[email protected]_spyder:/# /usr/bin/sudo -H -u adas bash
[email protected]:/$ export DISPLAY=:0
[email protected]:/$ xhost +
access control disabled, clients can connect from any host
[email protected]:/$ sudo -i
-bash: getprop: command not found
[email protected]:~# mknod -m640 /dev/loop94 b 7 94
mknod: /dev/loop94: File exists
[email protected]:~# mount -o loop /sdcard-ext/gentop.img /tmp/wtm
mount: you must specify the filesystem type
[email protected]:~# mount -o loop /sdcard-ext/gentop.img /tmp/wtm -t ext4
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
[email protected]:~# mount -o loop -t auto /sdcard-ext/gentop.img /tmp/wtm
mount: you must specify the filesystem type
[email protected]:~# mount -o loop -t ext3 /sdcard-ext/gentop.img /tmp/wtm
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
[email protected]:~# mount -o loop -t ext4 /sdcard-ext/gentop.img /tmp/wtm
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
[email protected]:~# dmesg | tail
[ 1635.078918] HDCP: hdcp_ioctl() - QUERY 1335468
[ 1635.627441] 1 1429 679 0
[ 1636.224029] 1 850 234 1
[ 1636.291473] 1 850 234 0
[ 1636.829101] HDCP: hdcp_ioctl() - QUERY 1337226
[ 1637.243896] CPU1: shutdown
[ 1638.579315] HDCP: hdcp_ioctl() - QUERY 1338976
[ 1640.329528] HDCP: hdcp_ioctl() - QUERY 1340726
[ 1642.080322] HDCP: hdcp_ioctl() - QUERY 1342476
[ 1643.830505] HDCP: hdcp_ioctl() - QUERY 1344226
[email protected]:~#
No luck mounting the image.. any advice?
mount -o loop -t ext4 /sdcard-ext/gentop.img /tmp/wtm
That works on my device.
OR...
....fsck.ext4 -f /sdcard-ext/gentop.img
and retry to mount.
This looks awesome as well, but I'm having the same issue that was occurring with the ubuntop mod where my screen goes blank after a random interval of time.
It's obvious. The problem comes from Moto's XServer and I cannot do anything right now for this as I'm looking to solve some other things and make something else to be easier.
Anyway this is solvable with some working (and it WILL be solved!) and you can avoid this to happen clicking sometimes on the mobile view window!
Take your time! Although I think the recent RAZR update broke it for the original WTM for ubuntu on my phone too...
GenTop looks much better then ubuntu but like really noob I don't know lot of things there. Like how to install apps(libreoffice, jdownloader,...), how to mount external drive, etc. I have also issue with MX video player when I switch it on full screen and back. On gentop mobile view stop working. And on ubuntu WebTop falls at all. But maybe it is caused by nebtop.
I think it looks very promising but there is lot of work to be done. I'll be glad to help you, if there is something that I could do.
Thanks.
EDITn standard webtop with nebtop it works fine.
Sent from my XT910 using XDA App
Related
[MESSAGE TO MODS, I could not include urls so have added spaces to pass spam filter.. please change?]
Well now we finally have root on our shiny devices I decided to crack open
the beers and get to work getting debian running on the X10..
the process is actually pretty straight-forward.
(as it turns out the x10's kernel already has support for most things needed
such as the ext2 filesystem)
-- step 1--
firstly we need to create a debian image for the phone, there are a few already out there but you can use the following to create your own
Code:
apt-get install debootstrap
dd if=/dev/zero of=debian.img seek=749999999 bs=1 count=1
mke2fs -F debian.img
mkdir debian
mount -o loop debian.img debian
debootstrap --verbose --arch armel --foreign lenny debian [ht]tp:[//]ftp. de. debian. org/debian
umount debian
how ever if you would prefer to use a ready built one (recomended for less techies ) you can get one from: rapidshare. com/files/161776007/debian-armel-750.img.bz2
(had to include spaces in the url to pass spam filter, could a mod please change this?)
now copy this too the root of your sdcard and make sure its called debian.img
-- step 2 --
I have created a script to do most of the other work for you:
Code:
alias b=busybox
export PATH=/data/local/bin:/usr/bin:/usr/sbin:/bin:$PATH
b mknod /dev/loop0 b 7 0
b mount -o loop,noatime /sdcard/debian.img /data/local/mnt
echo 'nameserver 4.2.2.2' >data/local/mnt/etc/resolv.conf
b chroot /data/local/mnt
mount -t devpts devpts /dev/pts
mount -t proc proc /proc
mount -t sysfs sysfs /sys
rm -f /etc/mtab
ln -s /proc/mounts /etc/mtab
put this in your sdcard to.
-- step 3 --
Finally in any terminal emulator cd to the location of the startdeb.sh file
and do the following:
Code:
chmod 777 ./startdeb.sh
./startdeb.sh
!! and your done !!
you should now be within the debian system.. i suggest running
Code:
apt-get update
and installing what ever apps you want
(my first choices were gcc, python and tightvncserver)
[ EXTRA ]
now your on debian you can use
Code:
apt-get install tightvncserver
to get the xwindow system and the vnc server
now set both your HOME and USER variables
Code:
export HOME=/root
export USER=root
(or what ever user you choose)
and run
Code:
tightvncserver
(your also gonna have to download lxde and do a few other bits of setup
have a look around for X11 "Ported" to android post on these forums)
you could also change the config so that the desktop is displayed
at the right size for the screen
just use a vnc client from the market to connect to your GUI
Kool. I had ubuntu running on my htc touch pro once but wasnt really worth having apart from the cool factor. This looks promising.............. ill wait a while till I play around, the rooting factor is still new and I dont see the major gain to root yet.
Way awesome, thanks for the guide.
Nice work, will give this a try after I get the R2B rooted on my phone.
Next step for me would be to get the arm cross compilation toolchain and start porting goodies for the android....
wow this looks sooooo awesome!! any screen shots? don't make me google
when i try mounting debian.img using ur cmd i got following error
Code:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
seems my mount requires -t parameters, so i try again, but still having error
Code:
mount -o loop,noatime -t ext2 /sdcard/debian.img /data/local/mnt
ioctl LOOP_SET_FD failed: Device or resource busy
please help thanks!
aget1 said:
when i try mounting debian.img using ur cmd i got following error
Code:
Usage: mount [-r] [-w] [-o options] [-t type] device directory
seems my mount requires -t parameters, so i try again, but still having error
Code:
mount -o loop,noatime -t ext2 /sdcard/debian.img /data/local/mnt
ioctl LOOP_SET_FD failed: Device or resource busy
please help thanks!
Click to expand...
Click to collapse
Are you running the script as root? If you not you might wanna try that.
This may sound kind of noobish, but would this be a dual-boot (I.e. running both android and debian on different boots of the phone, or would this be debian, until you reset the phone to be android again.
Sent from my X10a using XDA App
ddewbofh said:
Are you running the script as root? If you not you might wanna try that.
Click to expand...
Click to collapse
Still the same
Code:
whoami
whoami: unknown uid 0
mount -o loop,noatime -t ext2 /sdcard/debian.img /data/local/mnt
ioctl LOOP_SET_FD failed: Device or resource busy
aget1 said:
Still the same
Code:
whoami
whoami: unknown uid 0
mount -o loop,noatime -t ext2 /sdcard/debian.img /data/local/mnt
ioctl LOOP_SET_FD failed: Device or resource busy
Click to expand...
Click to collapse
And I assume you're either running the script or doing those commands manually? Including the mknod part?
ddewbofh said:
And I assume you're either running the script or doing those commands manually? Including the mknod part?
Click to expand...
Click to collapse
i run the script and found no luck, so i type in both adb and console, of coz mknod is done, either mkdir /data/local/mnt is done or not gives the same result, tried also mounting without loop,noatime and gives
Code:
mount: Block device required
would it be rooting problem or mount problem?
also tried losetup -d /dev/loop0, no luck
Code:
losetup: /dev/loop0: Device or resource busy
Keegan_P said:
This may sound kind of noobish, but would this be a dual-boot (I.e. running both android and debian on different boots of the phone, or would this be debian, until you reset the phone to be android again.
Sent from my X10a using XDA App
Click to expand...
Click to collapse
i see this to be a remounting of debian system on your phone, no modification on your phone so no, no dual boot
anybody can post a video tutorial please?
and the debian and android works together or just debian?
thx
A video tutorial would be amazing.
Sent from my X10a using XDA App
I will upload a video tutorial asap but at the moment I am having to use a 3G dongle for my internet (just moved out, am poor.. all donations to [email protected] on paypal ;-)) also this runs along side (or on top of) android so you'll still be able to get your texts and calls.. finally there are already a lot of debian apps compiled for ARM systems so have a look to see if the app you want is on apt (make sure you've run apt-get update first) please pm me if you have any problems
Thanks,
Sam Aldis
I tried to run it on the latest firmware and it seems loop device kernel module is not available in it.
Also the script is not fully functional :
you need to 'mkdir /data/local/mnt/'
also it's '/data/local' instead of 'data/local'
I haven't spend much time on this, so it's not working for now on my phone.
So help is welcome
Quick question:
Has anyone at all gotten this to work?
nope. I doubt it.
mod edit:..
sorry for stupid me, i don't know i can create loop device more than loop 0
i create loop0,loop1,loop2,loop7 and try mounting again, it success this time
so here is my script:
Code:
#!/system/bin/bash
export PATH=/data/local/bin:/usr/bin:/usr/sbin:/bin:$PATH
if [ ! -d /data/local/mnt ]
then
mkdir /data/local/mnt
fi
if [ ! -b /dev/loop2 ]
then
mknod /dev/loop0 b 7 0
mknod /dev/loop1 b 7 0
mknod /dev/loop2 b 7 0
mknod /dev/loop7 b 7 0
fi
if [ ! -d /data/local/mnt/bin ]
then
mount -o loop,noatime /sdcard/debian.img /data/local/mnt
fi
echo "nameserver 4.2.2.2" >data/local/mnt/etc/resolv.conf
chroot /data/local/mnt
mount -t devpts devpts /dev/pts
mount -t proc proc /proc
mount -t sysfs sysfs /sys
rm -f /etc/mtab
ln -s /proc/mounts /etc/mtab
Edited:
I just brick my device after some more work, every command even ls do no output, reboot machine freezes at sony ericsson logo, now i am re rooting the device......
Edited 2:
Should be not the problem of debian, seems working fine.
Few months ago, there was a post on XDA:
http://forum.xda-developers.com/showthread.php?t=718952
and a link to:
http://nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-nexus-oneandroid/
They explain how to install and run Ubuntu on Nexus One.
But a lot of people got problems when running script bootubuntu and ubuntu.sh, and I was one of them.
After Cyanogen Mod 6.0 was released, I could successfully run Ubuntu according to given instructions, but later I discovered the two scripts (ubuntu.sh and bootubuntu) don't always work, and I found them very complex and unnecessary statements can be removed.
Since few months ago I've been refining the two scripts to make them able to boot Ubuntu with less likelihood to get error. I thought I would like to share my findings to everyone interested.
Here are some reasons why it's useful to have Ubuntu on Nexus One
1. Fully functional web browser Firefox
2. Fully functional office suite OpenOffice
3. Fully functional Linux terminal with lots of ultilities
4. Fully functional image manipulation tool Gimp
5. Ability to run lots of useful native Linux programs
6. Python, gcc, g++..
I'll talk about my findings in next few posts.
Post #2: simplify ubuntu.sh, remove unnecessary script files
Post #3: simplify bootubuntu, forcibly umount
Post #4: how to shutdown Ubuntu properly if terminal application was closed by Android
Post #5: a little script which should be run before exiting from Ubuntu
Post #6: how to start GNOME desktop (instead of LXDE) and get correct keyboard mapping
Post #7: a possible solution to loop device's "resource or device busy" error
About my Nexus One:
bought on 2nd March
Cyanogen Mod 6.0
IntersectRaven HAVS CM CFS 1020 kernel
Busybox 1.17
Radio 5.0.8
Gapps hdpi 20101020.1
Please don't hesitate to tell me if I made any mistake, I'm a Linux beginner because I taught myself Linux, my University will teach Unix next semester.
Attachment: ubuntu_scripts.zip
contains all modified scripts.
Finding #1:
In original Zip package, there are five scripts, but only two of them are actually used to install and boot up Ubuntu.
fsrw, mountonly, unionfs are not necessary to install and boot ubuntu, thus their reference can be removed from ubuntu.sh
Here is my simplified version of ubuntu.sh
#-------------------------------
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm -f /system/bin/bootubuntu
rm -r -f /data/local/ubuntu
cp -f bootubuntu /system/bin
cd /
echo "Type 'bootubuntu' to boot Ubuntu"
#-------------------------------
Simplified ubuntu.sh removed unnecessary statements to reduce risk of error.
Also I discovered:
Files in /sdcard/ubuntu can not be chmod, and it's unnecessary to chmod 4777 to them.
chmod 4777 /system/bin/* will cause some Android softwares to malfunction (e.g. Orbot), also it *possibly* cause some roms to fail to boot up next time (CM6.0)
Finding #2:
Here's my simplified bootubuntu script, there are minor changes to script flow and removed all unnecessary statements:
#-------------------------------
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
echo "SETTING VARIABLES"
export bin=/system/bin
export mnt=/data/local/ubuntu
export PATH=$bin:/usr/bin:/usr/sbin:/bin:$PATH
export TERM=linux
export HOME=/root
if [ ! -d /data/local/ubuntu ]
then
mkdir /data/local/ubuntu
fi
echo "SETTING UP LOOP DEVICE"
losetup /dev/block/loop1 /sdcard/ubuntu/ubuntu.img
echo "MOUNTING"
mount -t ext2 /dev/block/loop1 /data/local/ubuntu
mount -t devpts devpts $mnt/dev/pts
mount -t proc proc $mnt/proc
mount -t sysfs sysfs $mnt/sys
echo "SETTING UP NETWORK"
sysctl -w net.ipv4.ip_forward=1
echo "nameserver 208.67.222.222" > $mnt/etc/resolv.conf
echo "nameserver 208.67.220.220" >> $mnt/etc/resolv.conf
echo "127.0.0.1 localhost" > $mnt/etc/hosts
echo "Brought to you by NexusOneHacks.net and the open source community! "
chroot $mnt /bin/bash
echo "UMOUNTING"
umount -lfr $mnt/dev/pts
umount -lfr $mnt/proc
umount -lfr $mnt/sys
umount -lfr $mnt
losetup -d /dev/block/loop1
#-------------------------------
and it forcibly,lazily,read-only-if-failed umount $mnt, thus losetup -d will less likely to fail and eliminate the problem when booting ubuntu second time.
Finding #3:
If terminal application is terminated automatically by Android system, in this situation, the Ubuntu is not properly umounted.
Thus we change ubuntu.sh into:
#------------------------------
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm -f /system/bin/bootubuntu
rm -f /system/bin/exitu
rm -r -f /data/local/ubuntu
cp -f bootubuntu /system/bin
cp -f exitu /system/bin
cd /
echo "Type 'bootubuntu' to boot Ubuntu"
#------------------------------
and we create a new script named "exitu" in sdcard/ubuntu directory:
#------------------------------
export mnt=/data/local/ubuntu
echo "UMOUNTING"
umount -lfr $mnt/dev/pts
umount -lfr $mnt/proc
umount -lfr $mnt/sys
umount -lfr $mnt
losetup -d /dev/block/loop1
#------------------------------
remember to run "sh ./ubuntu.sh" to copy new exitu script into /system/bin.
Then whenever you went back to terminal, found Ubuntu terminal is gone, simply type exitu (remember to be su first) to exit ubuntu, then bootubuntu again to enter ubuntu terminal. It's harmless to execute exitu multiple times to ensure $mnt is umounted successfully.
Sometimes exitu still can not successfully remove loop1 assignment with /sdcard/ubuntu/ubuntu.img, but seems like it doesn't really matter, ubuntu still can boot up successful even loop1 was not unassigned successfully
Finding #4:
To reduce likelihood of getting "device or resource busy" error when removing loop device assignment, it's good to have this script in your Ubuntu, and run the script before exiting from Ubuntu:
#-------------------
export USER=root
vncserver -kill :1
vncserver -kill :2
sudo reboot
sudo halt
#-------------------
(remember, the script should be in your Ubuntu's file system, not your android's file system!)
run the script before you exiting from Ubuntu, this will greatly reduce likelihood of getting device or resource busy error when exiting.
Finding #5:
For those of you who prefer to enter GNOME desktop manually (no automatically start-up), this script may help, also this script should be able to fix androidVNC keyboard mapping problem:
(this script should be in Ubuntu)
#--------------------
cd /
rm -r -f tmp
mkdir tmp
cd /
export USER=root
export XKL_XMODMAP_DISABLE=1
vncserver -geometry 800x600
#--------------------
regarding the guide:
http://nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-nexus-oneandroid/
if you would like to enter gnome and not to autostart desktop environment, please don't follow its instruction on making change to /root/.vnc/xstartup and /root/.bashrc
instead, create a script as I mentioned above, and run the script to bring up VNC server, and you will get GNOME desktop in VNC with correct keyboard mapping
Finding #6
If you're constantly getting "device or resource busy" error when mounting loop1 to /data/local/ubuntu, the reason might be caused by Android App2SD (Froyo version), if you have any software installed on SD card, it may cause all loop devices to be busy all the time (even newly created loop device!) And busy loop device can not be mounted, thus generates "device or resource busy" error message.
Most people had the same problem few months ago, when they execute bootubuntu, they get an error saying loop device is busy, and even changing loop device wouldn't help.
Now I think the reason is determined. After uninstalled all applications which are on SD card (or move all of them from SD card to internal storage), the Ubuntu can boot successfully without getting "device or resource busy" error when mounting loop device.
Edit 2010-11-04:
If bootubuntu gets executed before Android loads all app2sd applications, it is possible solves the loop device busy error even with App2SD applications installed. It requires a very perfect timing, today after few experiments on my phone, I worked out a process which can always boot up Ubuntu on my phone:
1. Reboot phone
2. as soon as you enter lock screen, unlock screen
3. quickly go to terminal emulator
4. become su by typing su and enter
5. type bootubuntu and wait (type it fast... practice )
-------------
1-5 must be done before SD "Checking for errors" notification disappears, if you fail to do so.. reboot and try again
------------
6. as soon as SD "Checking for errors" notification disappears, hit enter IMMEDIATELY
Now you should be able to enter Ubuntu terminal.
Do NOT exit from your Android terminal (don't press back or home button), wait 1-2 minutes for Android to load applications on SD card.
Once you reboot your phone, you'll need to repeat the above procedure again to enter Ubuntu successfully.
Also chmod 4777 is horrible from a security point of view. It makes all the system bin files writable by anyone and run with root privileges (setuid root).
Sent from my Nexus One using XDA App
houzuoguo said:
Finding #6
If you're constantly getting "device or resource busy" error when mounting loop1 to /data/local/ubuntu, the reason might be caused by Android App2SD (Froyo version), if you have any software installed on SD card, it may cause all loop devices to be busy all the time, thus loop device can not be mounted to /data/local/ubuntu anymore.
Most people had the same problem few months ago, when they execute bootubuntu, they get an error saying loop device is busy, and even changing loop device wouldn't help.
Now I think the reason is determined. After uninstalled all applications which are on SD card (or move all of them from SD card to internal storage), the Ubuntu can boot successfully without getting "device or resource busy" error when mounting loop device.
Click to expand...
Click to collapse
This is because with Froyo apps to SD android creates an encrypted loopback device for each app on the SD card, so depending on the number of apps on your SD card loop0-7 may be in use. I solve this by using a high loop number with losetup - loop99.
Sent from my Nexus One using XDA App
Use a higher loop device, the best option
It worked for me on loop7, but to be on the safe side, decided to use a higher loop number as suggested, but it requires to create the loop device as it doesn't exists, use mknod:
Code:
echo "SETTING UP LOOP DEVICE"
mknod /dev/block/loop99 b 7 99
losetup /dev/block/loop99 /sdcard/ubuntu/ubuntu.img
Now is working on loop99 too!. The clean up section for both bootubuntu and exitu scripts:
Code:
echo "UMOUNTING"
umount -f $mnt/dev/pts
umount -f $mnt/proc
umount -f $mnt/sys
umount -f $mnt
losetup -d /dev/block/loop99
rm /dev/block/loop99
I'm not sure about how I am cleaning up the new node, rm erases it... but is this the best method? rebooting the phone will erase the node anyway so maybe an if clause to test for the node loop99 before creating it will be better.
fralacos said:
It worked for me on loop7, but to be on the safe side, decided to use a higher loop number as suggested, but it requires to create the loop device as it doesn't exists, use mknod:
Code:
echo "SETTING UP LOOP DEVICE"
mknod /dev/block/loop99 b 7 99
losetup /dev/block/loop99 /sdcard/ubuntu/ubuntu.img
Now is working on loop99 too!. The clean up section for both bootubuntu and exitu scripts:
Code:
echo "UMOUNTING"
umount -f $mnt/dev/pts
umount -f $mnt/proc
umount -f $mnt/sys
umount -f $mnt
losetup -d /dev/block/loop99
rm /dev/block/loop99
I'm not sure about how I am cleaning up the new node, rm erases it... but is this the best method? rebooting the phone will erase the node anyway so maybe an if clause to test for the node loop99 before creating it will be better.
Click to expand...
Click to collapse
thanks a lot
I tried this idea already but it seems doesn't work under CM6.0...
and the problem was, every newly created loop device will always be busy, if app2sd is used. (Don't know why)
I'm going to try a different approach, I try to mount loop device to /data/local/ubuntu before Android mounts all app2sd applications
mathrock said:
This is because with Froyo apps to SD android creates an encrypted loopback device for each app on the SD card, so depending on the number of apps on your SD card loop0-7 may be in use. I solve this by using a high loop number with losetup - loop99.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
thanks.
my finding is, Android froyo app2sd uses dm-xx loop devices for sd applications, for example, now I have three games on sd card, by entering mount in terminal, i read that
/dev/block/dm-0,dm-1,dm-2 are used.
After I removed all SD applications and reboot system, all of those dm-xxx devices are not mounted anymore.
Also the only difference between mount result with app2sd and mount result without app2sd is usage of dm-xx devices.
Finally I've found solution to the "device or resource busy" error
but it seems like people are now less interested in running Ubuntu on Nexus One
the original post got more than 35k hits and more than 200 replies
Hi houzuoguo!!
I'm trying to type bootubuntu when enter in system, but i think i'm not fast enough or that not work for me. Everytime i get:
# bootubuntu
SETTING VARIABLES
SETTING UP LOOP DEVICE
losetup: /dev/block/loop1
MOUNTING
mount: mounting /dev/block/loop1 on /data/local/ubuntu failed: Device or resource busy
mount: mounting devpts on /data/local/ubuntu/dev/pts failed: No such file or directory
mount: mounting proc on /data/local/ubuntu/proc failed: No such file or directory
mount: mounting sysfs on /data/local/ubuntu/sys failed: No such file or directory
SETTING UP NETWORK
net.ipv4.ip_forward = 1
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexistent
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexistent
bootubuntu: cannot create /data/local/ubuntu/etc/hosts: directory nonexistent
Brought to you by NexusOneHacks.net and the open source community!
chroot: can't execute '/bin/bash': No such file or directory
UMOUNTING
umount: can't forcibly umount /data/local/ubuntu/dev/pts: No such file or directory
umount: can't forcibly umount /data/local/ubuntu/proc: No such file or directory
umount: can't forcibly umount /data/local/ubuntu/sys: No such file or directory
umount: can't forcibly umount /data/local/ubuntu: Invalid argument
losetup: /dev/block/loop1: Device or resource busy
#
Whats the problem then?¿?
Thanks in advance.
devex said:
Hi houzuoguo!!
I'm trying to type bootubuntu when enter in system, but i think i'm not fast enough or that not work for me. Everytime i get:
# bootubuntu
SETTING VARIABLES
SETTING UP LOOP DEVICE
losetup: /dev/block/loop1
MOUNTING
mount: mounting /dev/block/loop1 on /data/local/ubuntu failed: Device or resource busy
mount: mounting devpts on /data/local/ubuntu/dev/pts failed: No such file or directory
mount: mounting proc on /data/local/ubuntu/proc failed: No such file or directory
mount: mounting sysfs on /data/local/ubuntu/sys failed: No such file or directory
SETTING UP NETWORK
net.ipv4.ip_forward = 1
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexistent
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexistent
bootubuntu: cannot create /data/local/ubuntu/etc/hosts: directory nonexistent
Brought to you by NexusOneHacks.net and the open source community!
chroot: can't execute '/bin/bash': No such file or directory
UMOUNTING
umount: can't forcibly umount /data/local/ubuntu/dev/pts: No such file or directory
umount: can't forcibly umount /data/local/ubuntu/proc: No such file or directory
umount: can't forcibly umount /data/local/ubuntu/sys: No such file or directory
umount: can't forcibly umount /data/local/ubuntu: Invalid argument
losetup: /dev/block/loop1: Device or resource busy
#
Whats the problem then?¿?
Thanks in advance.
Click to expand...
Click to collapse
I worked on that problem for few weeks and finally I discovered, once I moved all SD applications back to Internal storage, loop1 no longer be busy.
Are you using Froyo app2sd?
houzuoguo said:
thanks a lot
I tried this idea already but it seems doesn't work under CM6.0...
and the problem was, every newly created loop device will always be busy, if app2sd is used. (Don't know why)
I'm going to try a different approach, I try to mount loop device to /data/local/ubuntu before Android mounts all app2sd applications
Click to expand...
Click to collapse
Some of us are still interested in this info but ubuntu runs pretty slow on the nexus. I say it would be nice to have the newest ubuntu (10.10) installed on the nexus one. Possibly the netbook remix version.
Lou2serious said:
Some of us are still interested in this info but ubuntu runs pretty slow on the nexus. I say it would be nice to have the newest ubuntu (10.10) installed on the nexus one. Possibly the netbook remix version.
Click to expand...
Click to collapse
thanks haha, good to hear that I'm not the only one still interested in running Ubuntu on Nexus One.
I'm thinking, if Nexus Two can be overclocked to 1.4Ghz, together with top class SD card, the speed will be enough to run Ubuntu fluently.
Hi! Thanx for ur work! It helped me.....
Now i´m having another issue....i´m triying either to resize the ubuntu.img to make it bigger so i can install the stuff i want ( clean install has 100 mb left) or (preffered option) mounting my sdcard so i can install the native programs from there...any ideas?¿
I think the simple way is just to create another file bigger.
funkatiko said:
Hi! Thanx for ur work! It helped me.....
Now i´m having another issue....i´m triying either to resize the ubuntu.img to make it bigger so i can install the stuff i want ( clean install has 100 mb left) or (preffered option) mounting my sdcard so i can install the native programs from there...any ideas?¿
Click to expand...
Click to collapse
You might want to build your own rootfs - check this site out - it worked great for me.
https://wiki.ubuntu.com/ARM/RootfsFromScratch
Ok I'm on the OTA 2.3.4 from a fresh unlocked 4.1.83 no problems what soever and I'm looking to make a few mods when I saw the link posted for the 2.3.4 HDMI Mirror over at
http://forum.xda-developers.com/showthread.php?t=1169457
I went ahead and ran
adb shell
su
mount -o remount,rw /dev/block/mmcblk0p12 /system
sed -ie s/ro.hdmi.mirror.enable=false/ro.hdmi.mirror.enable=true/g /system/build.prop
mount -o remount,ro /dev/block/mmcblk0p12 /system
cd /etc/init.d
cp startXServer.sh startXServer.bak
(head -n 40 startXServer.bak; echo "if [ ! -e /var/run/noWebtop ]; then"; tail -n 12 startXServer.bak; echo "fi") > startXServer.sh
restart your phone
I read through the command and seemed pretty safe and was excited because the post listed the HDMI Mirror as being in "landscape" mode. Hell yeah right! Well it wasn't, it was the same portrait so I was looking to revert back. Go change the build.prop back for the ro.hdmi.mirror to equal false. No big deal that's easy enough with root explorer. Read through the commands and saw that the startXServer.sh was cp to startXServer.bak. Easy enough just delete the startXServer.sh and rename startXServer.bak to .sh.
Well there is the problem. When i ran the commands the first time didn't work so i went into the build.prop and did a manual change. Then re-ran the bottom half. It seems doing that I over wrote the .bak agan and now both files are exactly the same and have no way of reverting. I have the system, boot, and webtop backed up with an .img but that didn't fix my entertainment center when I plug in an HDMI to the TV. The original commands did a back-up so I didn't double back-up the file.lol
I was wondering if a dev that has a little more command line knowledge, maybe the orginal contents of startXServer.sh, or the actual file could help me out with the revert back and a working entertainment center. The current contents are
if [ ! -e /var/run/noWebtop ]
fi
I'm pretty sure that's the problem, unless someone else sees something I'm missing.
**Edit**
This was solved under the Q&A Section from a earlier post yesterday afternoon. Mods please close if necessary. In case any one needs it see below. I just rewrote the startXServer.sh to contain the following.
#!/bin/sh
#
# startX.sh
#
# This script starts the X server
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
NAME=startX
DESC="OSH X Server"
. /lib/lsb/init-functions
#umask 002
log_begin_msg "Starting $DESC: $NAME"
rm -f /tmp/serverauth.*
rm -f /tmp/.X0-lock
rm -fr /tmp/.X11-unix
rm -fr /tmp/.ICE-unix
if [ ! -e /home/adas/.tag_master_reset_ls ]; then
/usr/local/sbin/update-language.pl "en_US.UTF-8"
echo 1 > /home/adas/.tag_master_reset_ls
fi
. /etc/environment
export PATH
export LANG
export DISPLAY
export LD_LIBRARY_PATH
export USER=adas
export HOME=/home/$USER
# new way of starting
if [ $1 = "webtop" ]
then
sudo -u adas -i /usr/bin/startx -- -nolisten tcp -layout HDMI vt2 &
else
sudo -u adas -i /usr/bin/startx /usr/local/bin/xnull -- -nolisten tcp -layout HDMI vt2 &
fi
Welcome to the EternityProject's WebTop Modifications Thread for Motorola RAZR
What do we have here?
Ubuntu Natty. Ubuntu Natty. Ubuntu Natty. Is it enough?
What do we need?
1. A brain
2. A RAZR
3. .....Anything you want
Download:
WebTopMOD v0.2a (Natty) for Motorola RAZR: HERE
domain_policy.conf: HERE
sudoers: HERE
Easy INSTALL & STARTUP Scripts: HERE
Instructions:
1. UnBz2/UnTar the archive
2. Copy the IMG file on the root of your external sdcard
3. Install the Easy Scripts with bootstrap/safestrap recovery
4. Enjoy!
WebTopMOD Changelog:
Code:
v0.2a:
Image file now is 3.5GB, FAT32 friendly!
v0.2:
Updated to Natty Narwhal
Prelinked all libraries for faster execution
Added EternityProject branding
Installed base dev tools
The Gimp included
Fixed some errors in APT
Regenerated all the locales and fixed locale errors
....and many many other fixes :)
v0.1:
- First release.
EPRJWTScripts Changelog:
Code:
v0.1:
- First time setup included
- Added scripts for WebTopMOD easy boot
MANUAL First Time Setup:
Code:
adb push domain_policy.conf /tmp/
adh push sudoers /tmp/
adb shell
su
cp domain_policy.conf /etc/tomoyo/
cp sudoers /etc/
chown root:root /etc/tomoyo/domain_policy.conf
chown root:root /etc/sudoers
chmod 440 /etc/sudoers
reboot
Then start WebTop and execute this:
Code:
*********PRELIMINARY VERSION SCRIPT*********
su
/usr/bin/sudo -H -u adas bash
export DISPLAY=:0
xhost +
sudo -i
mknod -m640 /dev/loop94 b 7 94
mkdir /tmp/wtm
mount -o loop /sdcard-ext/eternitywtm.img /tmp/wtm
mount -o bind /proc /tmp/wtm/proc
mount -o bind /dev /tmp/wtm/dev
mount -o bind /dev/pts /tmp/wtm/dev/pts
mount -o bind /dev/shm /tmp/wtm/dev/shm
mount -o bind /proc/bus/usb /tmp/wtm/proc/bus/usb
mount -o bind /sys /tmp/wtm/sys
mount -o bind /tmp /tmp/wtm/tmp
mount -o bind /var/tmp /tmp/wtm/var/tmp
mount -o bind /var/run/dbus/ /tmp/wtm/var/run/dbus
mount -o bind /var/lib/dbus/ /tmp/wtm/var/lib/dbus
mount -o bind /sdcard /tmp/wtm/sdcard
mount -o bind /sdcard-ext /tmp/wtm/sdcard-ext
chroot /tmp/wtm /bin/bash
export DISPLAY=:0
xterm
The xterm window is acting on the new Maverick system.
Replacing WebTop UI with Lightweight GNOME (only panels and metacity) in v0.2:
Code:
eprj_lightgnome
Replacing WebTop with Full GNOME in v0.2:
Code:
eprj_fullgnome
Replacing WebTop UI with Lightweight GNOME (only panels and metacity) in v0.1:
Code:
kill $(ps -ef | grep 5000 | grep webtop-panel | cut -c10-15)
kill $(ps -ef | grep 5000 | grep apptray | cut -c10-15)
kill $(ps -ef | grep 5000 | grep metacity | cut -c10-15)
kill $(ps -ef | grep 5000 | grep xscreensaver | cut -c10-15)
sleep 3
gnome-panel &
metacity -c &
Replacing WebTop with Full GNOME in v0.1:
Code:
kill $(ps -ef | grep 5000 | grep webtop-panel | cut -c10-15)
kill $(ps -ef | grep 5000 | grep apptray | cut -c10-15)
kill $(ps -ef | grep 5000 | grep metacity | cut -c10-15)
kill $(ps -ef | grep 5000 | grep webtop-wallpaper | cut -c10-15)
kill $(ps -ef | grep 5000 | grep xscreensaver | cut -c10-15)
sleep 3
gnome-session &
Status:
The WebTop MOD FileSystem is ready.
Note that it is an alpha version so, not everything will work flawlessly and easily. If APT doesn't work, check /etc/resolv.conf.
Oldies:
WebTopMOD v0.1 (Maverick) for Motorola RAZR: HERE
Heheh!
So, I wanna do some questions to the community for making this to be better.
1. What do you expect from this release?
2. What are the programs you want to find on it?
3. What do you want to be able to do?
Thanks for your replies, guys!
The EternityProject Developer,
-kholk
Installed:
Full GNOME Environment
XTerm
OpenOffice.org Writer
Preview:
Click!
Great work!
1. What do you expect from this release?
A perfectly functional Ubuntu Maverick. Support for sudo, apt-get and such tings. I have never used webtop so I don't know what to expect. But a working Ubuntu as close as possible to the desktop edition would be a dream.
2. What are the programs you want to find on it?
Except from the default (maybe remove some unnecessary if space is needed, for example evolution (I think most android users use gmail) and gimp if it was still included in 10.10) I just want programs needed for correct function.
3. What do you want to be able to do?
Everything
Just a thought. Was 10.10 released for ARM?
Wondering if there are repositories available...
And why 10.10 and not 11.10? Is webtop using the same kernel as Android so we can't compile a newer one?
Im not exactly sure what I expect, I had a Bionic for 2 weeks prior to the RAZR, and its webtop mod basically made the Bionic a mouse and HDMI out to a tv a computer. Thats all I want, Santa.
You, good sir, have made my day!
1. What do you expect from this release?
I'd love the webtop be to much quicker. I think if you could introduce swap space, the speed could be increased greatly. I know there was a patch for that on the Bionic, so it would be excellent to see that on here to ensure it performs well.
2. What are the programs you want to find on it?
Is Mobile View possible? Also, I'd like to be able to compile code... can you maybe get Eclipse or Netbeans? Additionally, OpenOffice would be nice.
3. What do you want to be able to do?
I'm using my webtop primarily for taking notes in class, but I would absolutely love to have the ability to compile code so I can work on assignments on-the-go.
THANK YOU!!!
I'm installing Evolution and OpenOffice. I'll possibly install GIMP, too, but Eclipse and Netbeans are really big, so if anyone needs it, apt-get will work so you'll be able to install it on your own.
Anyway, please don't request big things, it should be a base system. Its size now (with Evolution) is 2GB. I expect it to grow to 2.5GB with OpenOffice.
How does it seem to be performing so far? Compared to the lapdock OS already installed?
This must be something different than what was out for the Bionic. That was just a couple megs and basically allowed webtop over HDMI without any adapters.
What you're referring to was a modification to Motorola's APKs for allowing WebTop over HDMI. This is a chroot into full Ubuntu Maverick through WebTop.
The link is broken... you added an extra w in the newworld part lol
kholk said:
What you're referring to was a modification to Motorola's APKs for allowing WebTop over HDMI. This is a chroot into full Ubuntu Maverick through WebTop.
Click to expand...
Click to collapse
Cool!
Soooooo....and talk to me as if Im an idiot, because, well, I am,..lol.....what is this then? And what are the advantages of this over Moto's webtop? And can I still use this over HDMI? Also if something goes horrifically wrong, will a nadroid back up made previously suffice in getting everything right again?
Every modification made to this system won't be reflected to the Motorola WebTop partition, so, if you totally screw up my Ubuntu Maverick installation, your device won't be screwed up: you just need to recopy the original WebTopMOD partition and... start over without problems!
Motorola WebTop is a modified Ubuntu system, with some Moto proprietary libraries and APT screwed up / disabled, so you cannot install anything over it.
WebTopMOD has got full APT so you can install everything you want or, well, everything available on Ubuntu repositories.
It's like having a "normal" (barely normal) PC Ubuntu Maverick installation.
I think the file is corrupt... wouldn't unzip for me. Downloading again...
your work is so awesome =)
what is a ubuntu maverick? googled it and nothing came up..
Ubuntu is a operating system like windows or OSX. Maverick is a version like Vista or Lion
See ubuntu.com or wikipedia
Sent from my awsome Motorola RAZR
link is broken =(
fighting4fun said:
link is broken =(
Click to expand...
Click to collapse
Remove one of the w's in newwwworld. It's spelled wrong in his link.
Someone has test it? i guess root is required, right?
proalius said:
Someone has test it? i guess root is required, right?
Click to expand...
Click to collapse
I'm pretty sure you need root. However, I downloaded the file twice now, and WinRAR wouldn't open with it. 7zip seems to work, but I'm a bit concerned that it might be corrupt. I'll post again if it works for me.
EDIT: File is corrupt. I can't open the img file. I've tried downloading and extracting on two different computers.
Re: [MOD] Full Linux (Debian) inside WebTop! v0.2.7
I managed to unlock, root and install WebTopMOD on my new2me searet Atrix 4g. Great feeling for an android n00b! I can run iceweasel, gimp and whatever I like just like any linux distro on the webtop as long as I start a new shell to launch linux apps. I had wanted to continue on to using the instructions in post #865 by jissee44 to get the xfce4 window manager running. No luck! I can launch (I think) xfce4 manually and the entire view changes - new wallpaper, new toolbar, but no access to the linux filesystem - everything connects to the android filesystem.
Here is what I think is needed to see what went wrong. There are only two files to edit when following post #865. I am including the entire file as the posting I was following does not include diffs.
/osh/usr/sbin/linux
Code:
#!/bin/bash
CHROOTDIR="/osh/opt/WebTopMOD/root"
LOOPDEVICE="/dev/block/loop50"
function enablex {
xhost +
}
function mountlinuxdisk {
loopdevice
sudo mount -t ext3 -o loop=$LOOPDEVICE $FILENAME $CHROOTDIR
touch /tmp/linuxdiskactive
}
function umountlinuxdisk {
sudo umount $CHROOTDIR
sudo umount $LOOPDEVICE
rm /tmp/linuxdiskactive
}
function startfulllinuxchroot {
mountlinuxdisk
sudo mount -o bind /proc $CHROOTDIR/proc
sudo mount -o bind /dev $CHROOTDIR/dev
sudo mount -o bind /dev/pts $CHROOTDIR/dev/pts
sudo mount -o bind /dev/shm $CHROOTDIR/dev/shm
#sudo mount -o bind /proc/bus/usb $CHROOTDIR/proc/bus/usb
sudo mount -o bind /sys $CHROOTDIR/sys
sudo mount -o bind /tmp $CHROOTDIR/tmp
sudo mount -o bind /var/tmp $CHROOTDIR/var/tmp
sudo mount -o bind /var/run/dbus/ $CHROOTDIR/var/run/dbus
sudo mount -t vfat /dev/block/vold/179:18 $CHROOTDIR/sdcard
sudo mount -t vfat /dev/block/vold/179:33 $CHROOTDIR/sdcard-ext
sudo mount -o bind /etc $CHROOTDIR/mnt/DEVICE/etc
sudo mount -o bind /usr $CHROOTDIR/mnt/DEVICE/usr
touch /tmp/fulllinuxchrootactive
}
function startxterm {
# sudo chroot $CHROOTDIR /usr/bin/xterm pdmenu
sudo chroot $CHROOTDIR /usr/bin/xterm
}
function startxfce {
kill $(ps -ef | grep 5000 | grep webtop-wallpaper | cut -c10-15)
kill $(ps -ef | grep 5000 | grep xscreensaver | cut -c10-15
sudo chroot $CHROOTDIR /usr/bin/xfce4-session
}
function stopfullchroot {
CHECKS=0
until [ "$CHECKS" -eq "15" ]
do
TOUMOUNT=`sudo mount | grep "$CHROOTDIR" | awk '{ print $3 }'`
if [ "$TOUMOUNT" = "" ]; then break; fi
for i in $TOUMOUNT
do
sudo umount $i
done
CHECKS=$(( $CHECKS + 1 ))
done
rm /tmp/fulllinuxchrootactive
mountlinuxdisk
}
function checkwhereislinux {
if [ -e /sdcard/WebTopMOD/linuxdisk ]; then
FILENAME="/sdcard/WebTopMOD/linuxdisk"
if [ "$1" -eq 1 ]; then
/usr/bin/xmessage "Found image in /sdcard/WebTopMOD/linu
xdisk!"
checklinuxdisk
fi
else
if [ -e /sdcard-ext/WebTopMOD/linuxdisk ]; then
FILENAME="/sdcard-ext/WebTopMOD/linuxdisk"
if [ "$1" -eq 1 ]; then
/usr/bin/xmessage "Found image in /sdcard-ext/We
bTopMOD/linuxdisk!"
checklinuxdisk
fi
else
if [ "$1" -eq 1 ]; then
/usr/bin/xmessage "Sorry, no image available...
put linuxdisk in /sdcard/WebTopMOD/ OR /sdcard-ext/WebTopMOD/linuxdisk"
exit 1
fi
fi
fi
}
function checklinuxdisk {
if [ ! -s $FILENAME ]; then
/usr/bin/xmessage "But... Wait... Your disk looks damaged, maybe
you tried to copy an image larger then 4gB? This is a FAT32 limit."
exit 1
fi
if [ -d $FILENAME ]; then
/usr/bin/xmessage "Damn! linuxdisk is a file and it MUST be plac
ed in /sdcard/WebTopMOD/ OR /sdcard-ext/WebTopMOD/ folder. Otherwise this mod CA
N'T work' "
exit 1
fi
}
function loopdevice {
if [ -e $LOOPDEVICE ]; then
echo "Device exist"
else
sudo mknod -m600 $LOOPDEVICE b 7 50
fi
}
enablex
if [ -e /tmp/linuxdiskactive ]; then
if [ -e /tmp/fulllinuxchrootactive ]; then
startxterm
else
checkwhereislinux 0
startfulllinuxchroot
startxterm
fi
else
checkwhereislinux 1
mountlinuxdisk
startfulllinuxchroot
startxfce
# startxterm
fi
#RUNNINGXTERM=`ps -C xterm h | wc -l`
#if [ "$RUNNINGXTERM" -eq 0 ]
#then
# stopfullchroot
# umountlinuxdisk
#fi
exit 0
/osh/usr/local/bin/start-oshwt-2.sh
Code:
#! /bin/sh
### BEGIN INIT INFO
# Provides: start_lxde2.sh
# Required-Start:
# Required-Stop:
# Default-Start:
# Default-Stop:
# Short-Description: started by adas user at login
### END INIT INFO
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
export LD_LIBRARY_PATH=/usr/lib:/usr/local/lib
. /lib/lsb/init-functions
log_action_msg "Will now start OSHWT 2 scripts"
# start OSHWT 2 scripts
sfalv -i "lxpanel"
#sfalv -i "awn-autostart"
sfalv -i "webtop-panel"
sfalv -i "webtop-wallpaper"
sfalv -i "evbridge"
sfalv -i "window_switcher"
sr-test avahi_start &
Can someone give me some clues as to what has gone wrong? I'm not sure if something is missing or if I broke something in my edits, and there are no follow up questions on the post. There are 13 thanks.
ruarri
making progress?
Okay, I'm just hearing the crickets.
> startxfce4
provides some of the results I want, but leaves AWN in control. Now that the new ICS ROMs are coming out I'll have to see if I can just make webtopMOD usable until something better comes along. It would be good to see better documentation for n00bs. The forums are a little rambling. There is a lot of good info, its just scattered.
ruarri
ruarri said:
no access to the linux filesystem - everything connects to the android filesystem.
Click to expand...
Click to collapse
Hi,
What do you mean ?
The Debian is a Chroot
Good'nough
jisse44 said:
The Debian is a Chroot
Click to expand...
Click to collapse
Thanks for the terse explanation, jisse44. It took me a while to get around to reading the docs on chroot. It makes sense that webtop isrunning in a sandbox. That is inherently limiting.
I still love webtop and my lapdock. It will be interesting to see what happens with webtop and the ICS ROMs on the Atrix 4G.
ruarri said:
It will be interesting to see what happens with webtop and the ICS ROMs on the Atrix 4G.
Click to expand...
Click to collapse
Or not....
By now you can only run last new "webtop" on ICS Roms, and this is not THE webtop, it's a tablet mode: no Ubuntu or debian, only Android....