Categories: PogoPlug Development
DO NOT INSTALL/USE OPENPOGO ON THE NEW POGOPLUG v2 HARDWARE!!!
It has not been tested due to a lack of...well, new hardware. Therefore, please do not use OpenPogo on the new Pogoplugs, as you risk breaking your new Pogoplug. Older v1 power bricks with 2.0 SOFTWARE are NOT affected and can run OpenPogo like before.
Pogoplug v2 "Pink" Box - UNSUPPORTED, no ETA.
Pogoplug v1 "Powerplug" w/ 2.0.1 software (latest) - SUPPORTED
I have no idea when OpenPogo might support these newer plugs or if it will at all...
Crimsonredmk,
I just wanted to let you know that I have installed OpenPogo on my Pogoplug V2 and it seems to be working fine. I have Lighttpd with PHP FCGI up and running and all seems to be working. If you need any help testing give me A shout I'd be more than happy to help out.
Thanks
Jim
I've had 2 bricked Pogoplug people come to me for help in the past few days, and they ran OpenPogo, so there might or might not be a connection. I don't know why there would be as cloudEngines said that the Pogoplug's software is the same...so OpenPogo software should function the same way.
jim_richards said: Crimsonredmk, I just wanted to let you know that I have installed OpenPogo on my Pogoplug V2 and it seems to be working fine. I have Lighttpd with PHP FCGI up and running and all seems to be working. If you need any help testing give me A shout I'd be more than happy to help out.the pink one?
We're really, really close to releasing a guide to upgrade Pogoplugs to our new way of doing things. It boots from USB on the pink v2 one because CloudEngines got rid of our space on the new plug (only 87MB free!). Plus, if you break it, just remove the USB drive and you'll be back to regular Pogoplug :)
I've got openpogo running on V2 hardware (yes, the pink one).
UI Version: 2.0.1
Service Version: LINUX connect-server - 2.0.1
-bash-3.2# ipkg list_installed | cut -d- -f1,2
bzip2 - 1.0.5
libstdc++ - 6.0.9
mysql - 4.1.22
ncurses - 5.7
ncursesw - 5.7
openssh - 5.2p1
openssl - 0.9.8k
readline - 6.0
rsync - 3.0.6
squid - 2.6.21
zlib - 1.2.3
Successfully terminated.
-bash-3.2# df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/mtdblock2 32768 11868 20900 36% /
none 128004 8 127996 0% /tmp
/dev/mtdblock3 93184 16568 76616 18% /opt
/tmp/.cemnt/sda2 76145596 52039204 20238344 72% /tmp/.cemnt/mnt_sda2
-bash-3.2# uname -a
Linux Pogoplug 2.6.22.18 #44 Mon Aug 10 12:57:36 PDT 2009 armv5tejl unknown
It does wrok but be careful not to fill up mtdblock3 as it's only 91MB and users have been having problems after filling it up.
Yes indeed! I've kept my eye on /opt and I've had to be fairly picky in what I install. I was careful to configure squid to keep its cache and its logs on the usb drive for just that reason! But so far, it runs great!
I tried it, but it mounted /tmp and /sys like 20 times. Anyone else have that happen?
sjhill said: I tried it, but it mounted /tmp and /sys like 20 times. Anyone else have that happen?
Are you talking about the OpenPogo installation described here:
http://openpogo.com/wiki/index.php5?title=GUIDE:_Installing_Base_Package
or here:
http://www.pogoplugged.com/article/12101/How-to-Install-or-remove-OpenPogo-on...
Neither of these methods change how /tmp or /sys are mounted.
I just ordered my new Pogo Plug (Pink one!). What is the bext recommended practice for installing Openpogo. I do not want to brick mine. My daughter is going to love this one!
I'm rather biased but I think:
http://www.pogoplugged.com/article/12101/How-to-Install-or-remove-OpenPogo-on...
is the best way to go for OpenPogo (PlugApps is coming soon so you may want to check that out when your plug arrives).
My reasons are:
1. Reverting to regular Pogoplug operation is as simple as unplugging the USB drive with the Openpogo files.
2. The V2 Pink plug has only ~90MB for applications on nand. Installing Openpogo on a USB drive and you are only limited by the size of the drive.
As far as bricking your plug, the danger point is while the Pogoplug file system is in read/write mode. The most likely way the plug would be bricked is if the /etc/init.d/rcS file gets corrupted and you reboot. Be sure that /etc/init.d/rcS exists, is executable and is not corrupted before rebooting. Recovery from a corrupted /etc/init.d/rcS is possible using a serial console cable.
ianjb,
I followed every step on my Pink V2 with the exception of running opt-3.tar.gz instead of opt.tar.gz which all that was available from the download site:
http://www.pogoplugged.com/article/12101/How-to-Install-or-remove-OpenPogo-on.../
After rebooting, I get '-bash: ipkg: command not found' when issuing the 'ipkg update' command. My.pogoplug.com however comes up as normal with the USB ext2 drive mounted.
Any suggestions on what I might have done wrong?
jim_richards said: Crimsonredmk, I just wanted to let you know that I have installed OpenPogo on my Pogoplug V2 and it seems to be working fine. I have Lighttpd with PHP FCGI up and running and all seems to be working. If you need any help testing give me A shout I'd be more than happy to help out.What method did you use for getting this installed, jim_richards?
cbhyper,
The '-bash: ipkg: command not found' could be several things. I'll need your help to figure that out.
'ipkg' should be at '/opt/bin/ipkg', it needs to be executable and the PATH environment variable needs to point to it. Lets go through the possibilities.
The '/opt' folder could be missing. To find out login and type 'ls -al /opt' The response should look like
-bash-3.2# ls -al /optThe '/opt ->' shows that we have a link to the opt folder.
lrwxrwxrwx 1 root root 17 Feb 4 12:25 /opt -> /tmp/mnt_opt/.opt
-bash-3.2#
-bash-3.2# ls -al /opt/binNotice the line with 'ipkg'. The '-rwxr-xr-x' shows it is executable.
drwxr-xr-x 2 1000 100 1024 Feb 4 12:24 .
drwxr-xr-x 7 root root 1024 Feb 4 12:40 ..
-rwxr-xr-x 1 1000 100 3236 Aug 23 2008 ipkg
-rwxr-xr-x 1 1000 100 3236 Aug 23 2008 ipkg-opt
-rwxr-xr-x 1 1000 100 4248 Aug 23 2008 update-alternatives
-bash-3.2#
-bash-3.2# echo $PATHThe first part '/opt/bin' shows the path to ipkg is correct.
/opt/bin:/opt/sbin:/usr/bin:/usr/sbin:/bin:/sbin
-bash-3.2#
-bash-3.2# ipkg -v
ipkg version 0.99.163
-bash-3.2#
ianjb,
Thank you - So everything checks out up until:
-bash-3.2# ls -al /opt/bin
ls: /opt/bin: No such file or directory
However, this works:
-bash-3.2# echo $PATH
/opt/bin:/opt/sbin:/usr/bin:/usr/sbin:/bin:/sbin -bash-3.2#
So that path looks correct yet the files were not copied over?
But this obviously doesn't because the directory doesn't exist.
-bash-3.2# ipkg -v
-bash: ipkg: command not found -bash-3.2#
BTW - I partitioned this 4GB stick /dev/sda1 as EXT2 in Debian, though doesn't seem to have any relavance to this issue.
cbhyper,
I'll take a look at this tonight when I get home from work.
In the meantime, can you tell me what you get with 'mount'
it should look something like:
-bash-3.2# mount
rootfs on / type rootfs (rw)
/dev/root on / type jffs2 (ro)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw)
none on /tmp type tmpfs (rw)
/tmp/.cemnt/sda1 on /tmp/.cemnt/mnt_sda1 type ext2 (rw,nosuid,nodev,noexec,noatime)
/dev/sda1 on /tmp/mnt_opt type ext2 (rw,nosuid,nodev,noatime)
-bash-3.2#
-bash-3.2# ls -al /tmpis the 'mnt_opt' line missing?
drwxrwxrwt 5 root root 140 Feb 4 12:54 .
drwxr-xr-x 15 root root 0 Jan 1 1970 ..
drwxr-xr-x 3 root root 100 May 24 2009 .cemnt
-rw-r--r-- 1 root root 374 May 24 2009 hbplug.log
drwxr-xr-x 16 root root 1024 Feb 4 12:53 mnt_opt
-rw-r--r-- 1 root root 23 May 24 2009 resolv.conf
drwxr-xr-x 2 root root 40 Feb 4 12:54 var
-bash-3.2#
Correct.
I get everything but the '/dev/sda1' line.
-bash-3.2# mount
rootfs on / type rootfs (rw)
/dev/root on / type jffs2 (ro)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw)
none on /tmp type tmpfs (rw)
/tmp/.cemnt/sda1 on /tmp/.cemnt/mnt_sda1 type ext2 (rw,nosuid,nodev,noexec,noatime)
-bash-3.2#
Correct.
I am missing the 'mnt_opt' line.
-bash-3.2# ls -al /tmp
drwxrwxrwt 4 root root 160 Feb 4 05:31 .
drwxr-xr-x 14 root root 0 Jan 1 1970 ..
drwxr-xr-x 3 root root 100 Feb 4 03:57 .cemnt
-rw-r--r-- 1 root root 374 Jan 1 2000 hbplug.log
-rwxr-xr-x 1 root root 818533 Feb 4 05:31 mke2fs
-rw-r--r-- 1 root root 310767 Feb 4 05:31 mke2fs.zip
-rw-r--r-- 1 root root 22 Jan 1 2000 resolv.conf
drwxr-xr-x 2 root root 40 Jan 1 2000 var
-bash-3.2#
Something wrong with the way I formatted the drive?
I don't think it's your drive.
I just tried a new install on a flash drive and I had the same problem as you.
I don't know what (if anything) has changed since I wrote the article. I remember testing it more than once but ...
I just debugged it with a serial cable connected and watched the boot up sequence. It said './mount_opt file not found' To fix that we need to change one line in step 14.
echo './mount_opt' >> /etc/init.d/rcS
echo '/etc/init.d/mount_opt' >> /etc/init.d/rcSThat gives the full path and will enable it to be found.
echo '# code added below for OpenPogo /opt on USB with init on boot' >> /etc/init.d/rcS
echo '/etc/init.d/mount_opt' >> /etc/init.d/rcS
echo '/opt/etc/init' >> /etc/init.d/rcS
-sh-3.2# cat /etc/init.d/rcS
#!/bin/sh
mount -t proc none /proc
mount -t sysfs none /sys
mount -t devpts none /dev/pts
mount -t tmpfs none /tmp
mkdir /tmp/var
echo "/tmp/core_%e_%t" > /proc/sys/kernel/core_pattern
hostname Pogoplug
ifconfig lo 127.0.0.1
ifconfig eth0 169.254.37.133
udhcpc -b `hostname`
telnetd
/etc/init.d/db
ntpd -g
/etc/init.d/hbmgr.sh start
#/bin/mount -a
# code added below for OpenPogo /opt on USB with init on boot
/etc/init.d/mount_opt
/opt/etc/init
-sh-3.2#
Ok -
And just for clarification, after I've printed and confirmed the new matching lines in the rcS file, I need to follow your original steps 20 to 24 -- making the rcS file read-only again, then eject the USB drive, and then proceed with rebooting correct?
SUCCESS!!!! ianjb, THANK YOU!
I appear to be ready for some package goodness :)
-bash-3.2# ipkg update
Downloading http://openpogo.com/repo/Packages
Updated list of available packages in /opt/lib/ipkg/lists/cross
Successfully terminated.
-bash-3.2#
Congratulations! What do you plan to install?
BTW, I PM'd Peter and he renamed the file in the download section back to 'opt.tar.gz' Thanks for the heads up.
Any other updates necessary in the article?
For starters, SAMBA, rsync, FireFly, bind, OpenVPN... Webmin if possible. Getting rsync working with my NSLU2 will be a nice project. I'd also like to lock it down starting with root access. The provisioning/authentication control by PogoPlug doesn't make me feel very comfortable putting anything sensitive on there.
I'll keep you posted -- other than these changes, the article is extremely straight forward :) I really appreciate your help!
You're welcome.
The first lock down would probably be the root password and maybe disable telnet if you have ssh working. You'll need to make the file system read/write again for that but then you should be able to do everything on the USB drive in the /opt folder.
The /opt/etc/init file will run at boot time any executable scripts that start with 'S' (notice upper not lower case) in the /opt/etc/init.d folder. That's the way to start the SAMBA, etc. daemons.
Good luck and enjoy!
Copyright © 2012
Capable Networks LLC.. All Rights Reserved.
RSS |
Privacy Policy |
Advertise With Us |
Terms of Use |
About Us |
Contact Us |
Site Map
Our Capable Community Network:
DVR playground |
Explore3DTV |
MediaSmart Home |
MotoDash |
My Open Router |
Pogoplugged |
DijitCommunity |
Robo Community |
Sansa Community |
TechLore |
TiVo Community |
TouchSmartDevZone
Pogoplug™ is a trademark of CloudEngines, Inc. PogoPlugged.com is not affiliated with CloudEngines, Inc.
Did you forget your password?
You can also log in using OpenID.
Previous Thread
