Previous Thread
I have had my network port for about a week. Today two of the three drives are failing to show on the network. I tried to re initialize by shutting everything down but still only one drive showing. Tried to enter the pogo plugged website but it refuses to let me log in to see if there is any remedy for this problem. Guess it's time to look for another product, since this one is looking a lot like a waste of $80.00.
Categories: PogoPlug Development
I'll keep it as short and simple as possible:
TonidoPlug and Sheevaplug support booting from USB - kernels and all. Both of those run 2.6.33 with Webcam, ext4, and lots of great new things..support. This is the "full" and "official" PlugApps install and is the whole experience and isn't limited by anything.
Pogoplug doesn't have a bootloader that loads from USB because CloudEngines said so. They also embedded the device ID into the bootloader variables (instead of in a simple configuration file).
So PlugApps right now first boots the old 2.6.22.18 kernel and just enough to trick the system to veer off the bootup path into PlugApps on a USB drive. This means that the kernel is still old and remnants of Pogoplug's firmware are all over the place. It also loads up my.pogoplug.com functionality (by the XCE module). The XCE module only works on 2.6.22.18.
So we (IanJB and aholler for the very large majority) came up with installing a second bootloader and telling Pogoplug's proprietary bootloader to load the other one. The other bootloader loads a kernel and operating system from USB just like any other plug would. It's better, faster, and remnant and failure-free. Runs the newest kernel and all as well.
But it doesn't have my.pogoplug.com functionality because we still don't have a 2.6.33 XCE module from Cloud Engines. There is no ETA for this. We've been asking for a few weeks now though.
That's where we're at.
March 21, 2010 5:39 AM
updated: March 21, 2010 6:16 AM
I haven't yet tried PlugApps -- I intended to install this weeks ago, but recently have been focussing on the new Pogoplug uPnP feature.
But my impression, as a total newbie here, was always that PlugApps and Pogo proprietory were exclusive ored -- ie, when you boot with PlugApps you forego all the standard Pogoplug functionality.
This seemed reasonable to me, but I gather from your post, crimsonredmk, that I'm wrong. I can have my cake and eat it (Pogoplug + PlugApps) if I stick with the older, less capable kernel that my Pogoplug is already running. But there is a newer, faster PogoApps with the later kernel, that isn't able to include the Pogo proprietary stuff (XCE).
The Pogoplug section of the Wiki at plugapps.com refers only to the pivot_root method of bootloading PlugApps, so this must be the "Pogoplug right now" you refer to, which -- I now see from a closer reading of the Wiki -- clearly says "Pogoplug functionality is maintained".
OK. Sorry, I'm being ponderous about this because if I'm confused there's a good chance that others may be confused too, so I thought it worthwhile thinking aloud here.
If this thinking is right, let me add my 2c's worth. I believe that PogoApps is GPL licenced (I can only find one tangential reference to this in the Wiki -- IMHO this important information should be right there up front, because it matters). If so, then it's great that the current version of PlugApps has been able to incorporate and co-exist with Pogo proprietary. But surely there is no way that PlugApps can guarantee to carry this forward. Or even expect to do so, unless there's some private arrangement with CE I don't know about. And therefore no way that XCE compatibility can be incorporated into the PlugApps design goal.
So I think what I'm saying amounts to this: by all means nudge and cajole CE to provide an updated XCE that works with the new kernel, but shouldn't this be a matter for private correspondence? To go public with this (under the heading "Why PogoApps sucks...") sounds to me very like a whinge. And one for which -- as a very long-term, old school GPL advocate -- I can see no justification.
I need a sanity check on this. Do get back to me. Anybody?
--
Chris
March 21, 2010 12:28 PM
updated: March 21, 2010 4:13 PM
The problem with PlugApps wiki at this time - and the biggest thing limiting it - are the age of the tutorials and the lack of content. Add that the wiki is locked, so people cant contributor or fix errors, and that means the one person who has access is the bottleneck.
Nevermind the fact that things installed with pacman don't work 90% of the time, based on my personal experience. Sure, the mypogo functionality is lacking, intrusive, and the lack of security - port 80 is effectively running a root shell after all - make it something most companies would never want running on their network but if you want to present an alternative the least you could do is provide some basic NAS network capabilities. As it stands, the default installs of Samba, Apache, or ftpd do not even work.
Member
- member since: 05/17/2009
- rank: 6 of 6363
- 2 blog entries posted
- 17 forum threads started
- 218 comments
March 21, 2010 12:32 PM
I don't see any spam on our forums or wiki. All you need to do to edit it is be a registered member. We have the standard "Block new and unregistered users" restriction on most of the wiki because of spammers. You're also free to use discussion pages, which are unlocked for everybody.
Maybe you're talking about the OpenPogo forums and wiki though. Those are old and not what we're talking about here.
March 21, 2010 1:18 PM
So crimson, am I understanding you correctly? Did you just say that the wiki is not locked, but people simply do not update it? I actually tried to add my experience to it to improve it, but found no edit button.. so pardon me, no hostility intended.
I recently installed a FreeAgent Go/Stardock based system using a 750gig free agent go drive. I did this without following the instructions on the wiki, because the wiki has a few things missing. It was easier for me because I also run gentoo stage 1 installs for fun; But I doubt many noobs have the same experience.
That said, I was up till 5am last night working on this. I love the possibilities of this hardware but I'm not really happy with the "service" part of it as I find the implementation technically sloppy and insecure, not to mention the thought of servers I don't control being able to send commands to a device on a network I had thought I had locked down disturbs me greatly as a parent.
Member
- member since: 05/17/2009
- rank: 6 of 6363
- 2 blog entries posted
- 17 forum threads started
- 218 comments
March 24, 2010 4:19 PM
We got the XCE source code put up on http://pogoplug.com/opensource It was GPL'ed the whole time.
April 27, 2010 10:00 AM
So what does this mean for us "Noobs" is PlugApps still working? should I invest my time in it? Is Pogoplug still a good thing? I'm so confused....
PlugApps...Openpogo... Pogoplug :)
Add Your Reply
Copyright © 2010
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 DigitalEntertainer |
My Open Router |
Pogoplugged |
Robo Community |
Sansa Community |
TechLore |
TiVo Community |
TouchSmartDevZone
Pogoplug™ is a trademark of CloudEngines, Inc. PogoPlugged.com is not affiliated with CloudEngines, Inc.
View unverified member's comment - posted by JonW