Hmm. I'm still sitting at 1.0.1e-2+deb7u4 after an "apt-get update; apt-get upgrade" (which did nothing). What are you using as the repositories bodhi?by restamp - Debian
Anyone know when Debian (and in particular, Debian ARM) will be pushing the fixes for the openssl Heartbleed bug? (Or am I missing something?)by restamp - Debian
Thanks, twinclouds. I'll squirrel this away for future use. Are you planning to try to implement this method yourself?by restamp - Debian
Yes, that's what I used. I ran it back in March, and I don't believe it has been updated since then. The script is very nicely and conservatively written: It will pull the existing uBoot off the NAND and checksum it, and not proceed (unless you force it) if it doesn't recognize the original uBoot, and I think it will abort if it finds you're already on the latest version.by restamp - uBoot
Freakeao Wrote: ------------------------------------------------------- > Do I need to upgrade my uBoot to install Wheezy? Probably. You should be at least on uBoot 2011.12, produced around Feb 2012. (I'm not sure of the exact date for Dockstars, but Feb 20 2012 - 21:21:59 is the correct date for Pogoplugs.) > Should I upgrade it? (what benefits does an > upgrade uBoot pby restamp - uBoot
FYI: Looks like the days of running Asterisk on our ARM boxes to serve up Google Voice are numbered: http://www.reddit.com/r/google/comments/1pq6pu/google_voice_dropping_xmpp_calling_on_may_15_2014/ https://groups.google.com/forum/#!msg/indian-android/BQ6W8stwQ8w/TpM_KaxLaVYJ Sigh. Well, it was fun while it lasted. I think I got three good years out of it.by restamp - Debian
Perhaps Bodhi can give a better explanation, but from what I've read here in the past, in disks greater than 2T the number of sectors exceeds what can be represented in a drive's conventional partition table. 3T drives use a different table and one that our current uBoot does not understand. Thus, it cannot boot from a 3T drive, and indeed, even having such a drive connected at boot tby restamp - uBoot
Your problem isn't with samba, but with either apt-get or the samba package itself. One is broken. Can you "apt-get install" other packages? Do the /var/log/* files show anything interesting? Have you fscked the root (and var, if separate) file systems recently? I'm not a Debian apt-get expert, so I don't know what to suggest to clean a corrupted apt-get database.by restamp - Debian
I'm curious: How can the uBoot find the UUID from which it is desired to boot from unless it scans the USB devices first?by restamp - uBoot
Have you upgraded your uBoot on the Dockstar that won't boot? The original uBoot featured on this site, U-Boot 2010.09 (Oct 23 2010 - 11:49:22), cannot boot the Wheezy 3.2 kernel. The one currently being offered here, U-Boot 2011.12 (Feb 20 2012 - 21:21:59) -- this one is for the Pogo Pink, so the build date might be slightly different for the Dockstar -- is needed to boot Wheezy (and it wby restamp - Debian
The parts you pointed me to arrived last week and the serial console on my test Pogo is working great. Thanks again, bodhi. One question: What is the "RST" pin on the USB-to-TTL interface? I've heard of "RTS" -- Request to Send -- but not RST. Some sort of Reset? I've left it disconnected, but inquiring minds...by restamp - Off-Topic
Have you verified that your root filesystem is indeed an ext3 filesystem?by restamp - Debian
Ordered. Thanks, bodhi! Actually, from the looks of things I might have been able to avoid the JST header altogether and just plug the wires that come with the USB-to-TTL-serial widget directly onto the Pogoplug header. Should I connect the +3V line or not? Thanks again.by restamp - Off-Topic
I've decided to open up one of my spare Pogoplug E02s and wire up its serial port so that I can see what's going on if one of my in-service Pogoplug's loads decides it doesn't want to boot anymore. (So far, I've been lucky.) It seems straight-forward enough, but I can't seem to find a socket which will fit the 4-pin connector on the E02's motherboard. I'by restamp - Off-Topic
Just a few observations: 1. It appears you are running a Dockstar uBoot in your E02. Mine shows "Pogoplug E02". Not sure what effect this would have on things. (My guess is that it would likely work if you aren't concerned about areas where the two devices are architecturally different.) 2. Wheezy is designed for a 3.2 kernel. Not sure what effect running a 2.6 kernel wby restamp - Debian
I have always presumed -- a dangerous thing to do -- that the exclude pattern wasn't anchored unless it began with a leading slash, but otherwise, it applied if the pattern was a subset of the filename. In other words, 'a/b' would match the file 'aaa/bbb'. But now I believe this is wrong and it would only match the case where there was a 'b' entity within an &by restamp - Debian
OK. If I am reading this correctly, you have not quoted any of the arguments to your --excludes, and they all contain '*' shell expansion characters, so the shell will attempt to expand them before it invokes rsync. When running out of cron.daily, cron initializes the cwd to '/', so something like 'proc/*' will match the files under the /proc file system and be eby restamp - Debian
Hmm. Interesting. Do you use full paths in your "--exclude"s? Do you use shell variables in your backup script? Note that root's crontab sets certain variables such as $HOME and invokes scripts from root's home directory whereas cron.daily does not and operates from '/'. Also note that the shell invoked may be different in one versus the other. It'sby restamp - Debian
Actually, this thread prompted me to implement something I've been meaning to do for some time. I have two Pogos up and running, predominantly in active/standby mode. Once a day the active /home directory is rsynced to the standby box. However, there are a few files which need to be box-specific. So, I just created a /home/local directory for that purpose, and use symlinks to access it aby restamp - Debian
I use rsync extensively. On my Internet VPSes, I do things slightly differently -- I use the '-x' option to prevent rsync from venturing off the selected file systems. It creates the mount points on the backup, but goes no further. I do use '--exclude' also, and have never had any problems with it. For instance, '--exclude=/var/run' and '--exclude="/homby restamp - Debian
I don't know if this has anything to do with your problem, but on my Pogo E02, which was built initially from a very old version of squeeze, I had to run the command "flash-kernel" after an "apt-get upgrade" in order to permit a new kernel download to take effect. If I didn't do this, it just booted on the old kernel and sometimes complained about bad modules whichby restamp - Debian
Does an "ifconfig" show any errors or packet loss (dropped packets)?by restamp - Debian
I don't see this latency issue here. Methinks you have another problem, or a non-standard issue with your Pogo E02. On my local LAN, ping times to my Pogos are about 1/5 of a ms.by restamp - Debian
About two weeks ago, my Asterisk implementation used to interface to Google Voice (Asterisk server 1.8.9.2, built as described in this forum) started leaving me high-and-dry (would place calls, but I'd never get a ring tone) the first thing every morning. Waiting about 20 minutes after placing the first call or rebooting Asterisk would bring it back to life, after which it was good for theby restamp - Debian
It has been claimed that the uBoot does not know how to boot from an ext3 partition, but I have never had a problem here locally. I use ext2 to solid state devices in order to cut down on the number of write cycles, but I use ext3 for conventional disks for reliability in the event of crashes or power failures. If you think about it, it's hard to make a case that searching an ext3 partitioby restamp - uBoot
I presume it's because, even though you have a connection to the serial console, you still are directing uBoot to use the netconsole. So, the initial uBoot info comes out on the serial console, up to the point where the uBoot executes the "preboot" command ("run if_netconsole start_netconsole", which redirects stdin, stdout, and stderr) and after that the remaining outpuby restamp - uBoot
Thanks for the info syong. I played with hdparm years ago, but the latest version of smartctl seems to have everything I need to control the disk. I'm really more concerned about the automatic head parking than the spin downs. Usually, my system is busy enough that the main disks never spin down due to not being accessed recently. Regarding High_Fly_Writes, yes, I am familiar with thby restamp - Debian
Very similar here, syong, except I'm running a SheevaPlug with an SD-card root: Device Model: ST2000DL003-9VT166 ... 9 Power_On_Hours 0x0032 086 086 000 Old_age Always - 12998 ... 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 23 ... 189 High_Fly_Writes 0x003a 086 086 000 Old_age Alwaysby restamp - Debian
I've observed this auto-parking "feature" in my WDs and also in my Toshiba 2.5" external drives. The Seagates I've encountered to date don't seem to have gone this route, or perhaps just don't keep tabs on and/or report the number of head parkings. But I have one Seagate 2.5" drive that has been running for years on a Dockstar and is still going strong.by restamp - Debian
I have recently been investigating the suitability of small 2.5" pocket disk drives in a 24/7 application as the main drive on an Arm (Pogoplug, Dockstar, etc.) server. These drives are nice to use because they are self-contained, take little power, and require only one connection to the outside world -- the USB cable. I have one such server which I set up in January using an old Western Dby restamp - Debian