Yup, works fine. Just make sure you stub out the default udev rules for the ethernet port. From my notes: QuoteFix to allow thumbdrive to be moved from one Dockstar to another: http://forum.doozan.com/read.php?3,323,2038#msg-2038 # vi /etc/udev/rules.d/70-persistent-net.rules /* comment out line: SUBSYSTEM=="net",...NAME="eth0" */ # vi /lib/udev/rules.d/75-persiby restamp - Debian
Thanks for posting your environment. I see nothing out of the ordinary that stands out. Two suggestions: 1. After downloading a full version of 'nc' on the "listening" pogoplug (or other Linux box), try invoking it as: $ nc -klu 6666 (That's what I use successfully here to interact with netconsole from a Ubuntu PC.) 2. The Pogoplug does have mini-LEDs on itsby restamp - uBoot
1. Remove your USB drive from your Pogoplug, boot into its default Unix, run the command /usr/sbin/fw_printenv (as root), and post the results. 2. Give us the exact 'nc' command you are using to listen on your PC, plus the PC's IP address and the OS you are running on it.by restamp - uBoot
Thanks for the info, varkey. FWIW, I ordered two grey Pogoplugs on Wednesday evening from buy.com and they were on my doorstep Friday around noon. I'm surely impressed with their free shipping! I just upgraded the uBoot on one of them and have a spare Debian load I once built for a Dockstar and loaded onto a thumb drive up and running on it now. I like the extra 128MB of RAM memory, anby restamp - Debian
I really don't know Pogoplugs. So, what do we have here? 128MB or 256MB of main memory? armv5 or armv6 cpu? Are the grey and pink versions identical? If not, how do they differ? Is there a viable uboot for these? The chatter here suggests that Jeff's dockstar uboot doesn't really work well, if at all. Thanks in advance.by restamp - Debian
I can't comment on Acronis, but I'm currently running my Dockstar completely from a 1TB Seagate GO drive (no solid-state media on it at all, except for the uBoot), so I can vouch for it being doable. Good luck with it!by restamp - Debian
It's wise to always specify the shell in the script itself, as darethehair suggests, but if you want to always use a particular shell in cron, you can do this by specifyingSHELL=/bin/bash as the first line of your crontab. (You can also specify "PATH=...", and/or other environment variables, at this point.)by restamp - Debian
With regards to your first comment, I suspect your Pogoplug is using the wrong character set. (What exactly does "go crazy" mean?) Try echoing $LANG on both your desktop system and your Plug. I bet the Plug is set to "C" and the desktop to something like "en_US.utf8". If you need to edit files with special characters (those not in the ASCII character set) on yourby restamp - Debian
I'd try# fsck -n /dev/sdb1first to see if there are problems. If there are, you need to run the command without the '-n' argument and correct them. But, beware: If there is corruption, fsck will make the file system internally consistent, but not necessarily complete. It can remove corrupt files that are needed for the OS to boot or run properly. This is an unlikely, but possiby restamp - uBoot
As someone who has run his Dockstar with a root file system mounted on a hard drive for quite some time, I can attest that it is nearly impossible to make the system quiescent enough to allow the HD to remain spun down over the long haul. If you have any packages loaded to speak of, the disk will continually be spinning up and down. Since I've loaded asterisk on my Dockstar, the disk prettby restamp - Debian
1. Take your USB drive to another machine and see if it is recognized there. If so, fsck its file systems and make sure it is clean. If errors are found, pay attention to what is being removed, and if is important, make sure you restore it before trying to boot with that stick again. 2. How do you know it is not booting to the internal OS? If you haven't modified it on the NAND, it pby restamp - uBoot
With the default extensions.conf file modifications provided by Mario Limonciello, 800 numbers do not go through. I'm not sure why. Mario uses ideasip.com to place them, and ideasip claims to pass SIP originated 800 calls for free and with no registration. In any event, I couldn't get ideasip.com to accept my calls, so I changed the section of the extensions.conf file from: exten =by restamp - Debian
Thanks, peaslaker!by restamp - uBoot
On a slightly different topic, today, for security, I converted my Asterisk server to run under its own "asterisk" userid instead of "root". This may not be a comprehensive list of what needs to be changed to de-root a full-fledged Asterisk server, but it seems sufficient for what I am doing, namely using Asterisk solely as a conduit from my VoIP phones to Google Talk. # addby restamp - Debian
Anthony, where are you seeing these messages? In /var/log/asterisk/messages? I don't see any of them here, even the rather benign looking Notice. I rather suspect that you have one or more of your conf files in /etc/asterisk misconfigured. The ones that must be modified/personalized are: jabber.conf, sip.conf, gtalk.conf, and extensions.conf, plus modules.conf if you want to minimizeby restamp - Debian
rat, do you know whether these $50 black PogoPlugs come with 128Mb or 256Mb of DRAM memory? Thanks.by restamp - Debian
Glad you found the DHCP problem with your router, Tommaso. With regards to file system corruption, fsck would not have modified your /etc/fstab, but the OS will remount the file system in the mode specified there. Actually, mounting an ext3 file system (and probably ext4) as an ext2 should work OK. You'll just lose the benefit of the journal. For actual disk devices, I use ext3. ext4 isby restamp - uBoot
eltommi, your English is fine. It is unlikely that a power failure has corrupted the NAND memory. Honestly, I would suspect some problem with your DHCP server, since both the Dockstar internal Linux and the Debian load both seem to be unable to get a dynamic IP address, yet netconsole is capable of using the same ethernet connection to pass packets to your PC. I suppose if this were me: 1by restamp - uBoot
I take it you are unable to ssh into the Dockstar with the USB drive installed. What probably happened is that the drive has some corruption and needs to be fscked. Normally, you do this from the console -- Linux comes up to a certain point and says a manual fsck is required and waits for your input -- and with a console this would be clear. However, unless you have hacked in a console, you woby restamp - uBoot
Unless your *nix is set up for a read-only root, I think it would break things to simply declare / a ro file system. If it were me, I'd use 'lsof' to try to understand what 'rsync' is doing during these sessions. I suspect it may be maintaining either an open unattached temp file or pipe which it is writing to. The other thing I would suggest is that you consider sby restamp - Debian
Thanks for the info on QoS, petergunn. I wondered the same thing about the need for Apache. Here's my best guess: twinclouds was running FreePBX along with Asterisk, and FreePBX would of course require Apache. I would be surprised if Asterisk needs Apache when running stand-alone, since it has no web-based interface.by restamp - Debian
FWIW, I did a bit of playing around with my new asterisk server today (thanks again, guys!). One problem I observed was that the incoming caller id was passed in the squirrelly Google format no phone understands, and thus it wasn't recognized by my phone as being from a known caller. I traced this down to the fact that several of the functions used to translate the Google format to the staby restamp - Debian
Thanks for the tutorials, petergunn and twinclouds. Asterisk installed without a hitch and with your downsized module set, it fits just fine in the Dockstar's 128MB memory. You two deserve gold stars or kudos or something. FWIW, in a perfect world I would probably have put the Asterisk server on my SheevaPlug server, but I decided instead to use a spare Dockstar that I had laying aroundby restamp - Debian
Eric House Wrote: ------------------------------------------------------- > I probably don't need an actual image: I bet a > listing of the files would do. Would anybody mind > posting the results of running > > # ls -l / > > on a debian/squeeze Dockstar? Not sure what this will accomplish for you, but here it is: $ ls -la / total 92 drwxr-xr-x 22 roby restamp - Debian
Although people claim that Seagate has a program to change the GO drives' configurations to prevent auto-spindown, I've never figured out how to do it. If someone has successfully done this, I'd be interested in the details. But, even with the spindown, the drive is still eminently usable; you just get a short delay occasionally. Personally, I feel the default 5-minute timeout iby restamp - Debian
bodhi, I have used a Seagate GO drive for streaming video for over a year now, and it works fine. Actually, before I found out about the Dockstar, I had configured a SheevaPlug for just this purpose. I don't use MythTV. Maybe I should, but instead I cobbled together my own scripts to record programming OTA using an HDHomeRun tuner box and cron. I record the material to an older (5400 RPMby restamp - Debian
I would start by using the "top" program, which should allow you to see just how busy the processor is and how full your memory is. If you are seeing significant paging or swapping, you probably want to offload your real-time critical packages, like asterisk, to another Dockstar. You might be able to improve the situation by "nicing" the critical processes or locking them inby restamp - Debian
If the Dockstar would boot from the USB device with Debian on it before it was unplugged and after you changed the arcNumber, then I'd speculate that Debian is dropping into single user mode due to the need to manually fsck the filesystem. File system corruption sometimes occurs after a sudden power failure. Take the USB device to another Linux machine and fsck it there. Be careful if theby restamp - Debian
I believe it is unlikely that your uBoot was reflashed at the time it was registered. Here's what Jeff wrote to me: QuoteI think it's more likely that you have a bad block, but I'll take a look. Run the following and send me the resulting file: cd /tmp wget http://jeff.doozan.com/debian/uboot/nanddump chmod +x nanddump nanddump -nof mtd0 /dev/mtd0 After doing this, Jeffby restamp - uBoot
Papst, I don't know what's causing your problems. However, to shed a bit of light on fsck... Without the '-f' argument, the command will check to see if the 'clean' flag is set in the filesystem. This flag is set if the file system is in a consistent state -- i.e., if the file system is quiescent or has been cleanly dismounted. It indicates that there should beby restamp - Debian