• Home
  • Help
  • Search
  • Login
  • Register
  Show Posts
Pages: 1 2 [3] 4
31  General Category / General Discussion / Re: Using the SheevaPlug as a fileserver? on: June 05, 2010, 12:12:52 PM
Actually, one ws dual boots winxp and 3 linux distros, another ws is an iMac, one laptop is linux only and another laptop is a Mac. I set up a peer to peer samba network as I think samba is my only option to include all the clients. On the linux machines I use smbfs (cifs) to mount a Plug data share. Is it practical to work on my data files directly on the Plug? That would simplify syncing data to the clients, since the latest file would always be on the Plug. Previously, I had been syncing back and forth between laptop and ws. This can get confusing unless I remember to sync at the beginning and end of each work session.

The Plug seems powerful enough and quick enough to handle text files, jpegs etc, but probably not video. Does that sound right?

btw, thx for the offer of help on samba config. I think I have it working OK, but it has been a frustrating learning curve!

Regards,
feffer
32  Linux Stuff / Linux distributions / Re: Twonkymedia Problems on: June 04, 2010, 10:33:28 PM
This topic is old, but I just installed TwonkyMedia and used mgillespie's info for the most part. There were a couple of issues though. There is a newer version, TwonkyMedia_5.1.5 avalable now. Also the init script at File:Mediaserver.gz seems corrupt. Or at least I couldn't get it to open w/gunzip. I googled and found another twonky init script and used it instead. It didn't have the function to move the twonky db though so I manually moved /var/run/twonkeymedia from my SD card to an attached hdd, and left a sym-link in /var/run/ These mods seemed to work, OK. If there is anything I'm missing, please let me know.

thx,
feffer
33  General Category / General Discussion / Using the SheevaPlug as a fileserver? on: June 04, 2010, 02:53:19 PM
My std Plug runs debian squeeze from a class 4 SD card. It has a WD Elements (powered) ext hdd attached via a powered usb hub. Everything seems to be working well. I'm considering using it as a fileserver to 3 other machines on my LAN. Anyone else doing anything like that?

I need to keep certain directories synced between 2 of the client machines, and thought that would be easier if I just worked on the files directly from the Plug hdd. However, one of the machines is a laptop, which sometimes is remote (I don't have vnc setup yet). So I have to keep the files on it updated before leaving home.

What's a good way to set something like this up?

thx,
feffer
34  Linux Stuff / General Linux questions / Re: Trouble using the Plug as a print server on: June 04, 2010, 11:05:17 AM
OK, here are the extra stanzas with my comments:
Code:
## found at the top of the file - maybe used when the file is updated by apt?
# "$Id: cupsd.conf.in 8805 2009-08-31 16:34:06Z mike $"

###################################
## two9ers stanzas (modify as needed) inserted here...
###################################

## Stuff from here down not in two9ers file, but seem necessary for cups to function on my
## debian squeeze system. Rather than create my config file by cutting and pasting, I copied
## the entire (original) cupsd.conf.default file, and went through it stanza by stanza modifying
## it using two9er's file as a model. Mostly, opening up permissions with "Allow All"

# Set the authenticated printer/job policies...
<Policy authenticated>
  # Job-related operations must be done by the owner or an administrator...
  <Limit Create-Job Print-Job Print-URI>
    AuthType Default
    Order deny,allow
  </Limit>

  <Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job CUPS-Move-Job CUPS-Get-Document>
    AuthType Default
    Require user @OWNER @SYSTEM
    Order deny,allow
  </Limit>

  # All administration operations require an administrator to authenticate...
  <Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
    AuthType Default
    Require user @SYSTEM
    Order deny,allow
  </Limit>

  # All printer operations require a printer operator to authenticate...
  <Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After CUPS-Accept-Jobs CUPS-Reject-Jobs>
    AuthType Default
    Require user @SYSTEM
    Order deny,allow
  </Limit>

  # Only the owner or an administrator can cancel or authenticate a job...
  <Limit Cancel-Job CUPS-Authenticate-Job>
    AuthType Default
    Require user @OWNER @SYSTEM
    Order deny,allow
  </Limit>

  <Limit All>
    Order deny,allow
  </Limit>
</Policy>

#
# End of "$Id: cupsd.conf.in 8805 2009-08-31 16:34:06Z mike $".
#
Since your file works in your system, two9er, you're not really missing anything! These last stanzas add some sort of functionality, but I'm not sure just what. Also there may be some other differences between the previous stanzas, that caused cups to balk on my system. Once I got it working, I didn't try to break it again to isolate the issue  Wink

Funny, two years ago when I used the Linksys NSLU2 as a print server (for the same HP printer), the whole process was easier. I didn't even have to manually touch cupsd.conf. I'm familiar with modifying some linux files, but not this cups one, so I resisted messing with it.

So thx again for the help, two9er -- that got me over the top.

Regards,
feffer
35  Linux Stuff / General Linux questions / Re: Trouble using the Plug as a print server on: June 03, 2010, 06:01:00 PM
After some delay, I got this working. There are some gotchas' so I'll mention these for others who might have issues. The cupsd.conf file posted by two9er is basically good, but cups balked when I tried to restart it on my debian squeeze Plug. CUPS may be doing some transitioning. Seems like it anyway. I got it working by copying cupsd.conf.default to cupsd.conf and then altering that file with two9er's edits. The default file has several stanzas added to the bottom where the posted one leaves off. They are needed to keep CUPS happy, on my system at least. After this, things worked normally.

Again for others who might be trying to do this, here's the process I used.

1. Get the /etc/cups/cupsd.conf file properly set up as mentioned above. Do this first, since you
    won't be able to get cups web access from your client machine unless you allow it in cupsd.conf
2. Maker sure your printer, usb cables etc are all attached securely and in good working order
    It might be a good idea to check it all out directly attached to your PC/Mac if you haven't already!
    If the hardware doesn't all work directly, you'll be endlessly frustrated! After getting #1 done, I had
    a loose usb cable from moving the printer around. I caught it quickly, but it could have caused grief!
3. Use the cups web interface to add your usb printer to the Plug. Use http://IP-of-your-Plug:631
4. Go to the admin page and make sure that your printer will be shared
5. Print the test page after adding the printer -- that shows that printing directly from the Plug works.
6. Now you can set up printing on your local machine. There are several ways to do this...
7. I used "ipp" My local machine gets something like "ipp://192.168.5.87:631/printers/name-of-printer"
    It's a good idea to use IP numbers rather than a name -- easier when guests come over w/laptops
    You can go to the cups web interface for your client machine with: "http:localhost:631"
    The ipp address is added there. The /printers/xxx part is a default debian printer queue.
    Use the same name for the printer here that you used when adding it to the Plug.
    If you use a Mac and add the printer there, the "ipp://IP-of-Plug:631" goes on one line
    and "/printers/name-of-printer" goes on the second queue line. All should work now!
8. Its even easier on a linux client machine. The Plug printer was automagically discovered and easily
    enabled. I didn't try it on Windows, but it should be fairly straight-forward as well. Several years ago,
    though I had a problem getting WinXP to recognize a very old network connected laser-writer. I finally
    got it to work by installing it as a "local" printer. So if your Win machine resists, try that work-around.

Regards,
feffer
36  Linux Stuff / General Linux questions / Re: Trouble using the Plug as a print server on: June 02, 2010, 08:37:44 PM
thx for the quick reply, Jim. I tried your cupsd.conf (with mods for me) but still no joy. I have a feeling it's some sort of connectivity or permissions problem. I'm using the ipp network protocol; "ipp://IP-of-Plug:631/printers/HP5550" and that seems right. I used something similar on an NSLU2 w/o problem. The local client machines seem to "see" the share, but find it "inaccessible".

thx,
feffer
37  Linux Stuff / General Linux questions / [SOLVED] Trouble using the Plug as a print server on: June 02, 2010, 05:41:16 PM
I have cups installed on the Plug (running debian) and a powered hub attached to the Plug. A hdd and a usb printer are attached to the hub. I altered the /etc/cupsd.conf to allow remote access via Port 631. From a client machine I brought up the CUPS web interface with "http:IP-of-Plug:631" Then I added the usb printer, set it to "share" and printed a test page. So far so good...the test page worked fine.

However, I cannot seem to get it to work from client machines on my network! It seems easy to add the printer using the ipp addressing, but it does not work. A test print page shows: "Unable to get printer status (Bad Request)!" I know I must be missing something basic, but not sure how to proceed??

thx,
feffer
38  General Category / General Discussion / Re: Shutting off the Plug on: May 16, 2010, 01:47:05 PM
Yeah its annoying that it wont shut off properly... i don't leave mine on all the time as its not clever enough to turn my hard drives off properly so i have to shut it down when not in use. So if i leave it on its alot more than just the power of the device being drawn.

Pretty sure all servers are always on devices Tongue but they all can turn off properly if you want them to Tongue
hmmm, that may be an issue with your hdd. I'm using a WD 1.5T Elements and it goes to sleep after 15-20 minutes of inactivity. However on the Linksys NSLU2 (precursor device to the sheeva) I used a Seagate FreeAgent and had to work hard to get it to sleep, but I finally did.

feffer
39  General Category / General Discussion / Re: Shutting off the Plug on: May 16, 2010, 11:49:10 AM
thx for bearing with me Peter. That's what I thought, but I wanted to be sure I wasn't missing something. When I finish my experimentation, I will just leave it on.

During the initial setup, I used the serial console, but now that debian is installed, I guess stopping the OS is just doing "halt" or "poweroff," and starting it again is sticking a straightened paperclip in the reset hole. I won't need the serial console again unless I want to change to booting from NAND or a USB drive.

Having lots of fun, and don't worry, I'll get over the "he's got to be kidding," questions shortly   Wink

Regards,
feffer
40  General Category / General Discussion / Re: Shutting off the Plug on: May 16, 2010, 10:49:06 AM
hmmm, "poweroff" seems to work the same way as "halt." The debian OS is shut down (mine is running on an SD card) but the power to the Plug stays on. It still receives network activity etc. I assume at this point it's safe to pull or switch the SD card and/or just pull the Plug out of its socket. So there's no real on/off -- just a choice between "reset" or literally "pull the Plug." Is that right?

I'm asking this because I also bought a GuruPlug and want to try switching it into my network and connecting it to the same external hdd etc. Hence the need to completely poweroff the Plug not just it's OS.

thx,
feffer
41  Linux Stuff / General Linux questions / Re: How to clone a SheevaPlug? on: May 15, 2010, 10:14:32 PM
What works well for me is to configure the sheeva with the root filesystem on SD.  Then when I want to backup the sheeva I shutdown, put the SD in in my notebook computer and tar up the SD image.  Restoring the SD is just a matter of formatting an SD and untarring my backup to the SD.  This makes it extremely easy to clone the sheeva.

Here's the script I run (on the notebook) to backup my SD.  The SD is mounted at /mnt/tmp.

#! /bin/bash
date=$(LC_ALL=C date +%Y.%m.%d)
sudo tar c -C /mnt/tmp --exclude=lost+found -J -v -f /var/tmp/SheevaRoot-$date.tar.xz .

I also want to backup my SD. I have debian on it using Martin Michlmayr's howto. This creates separate /boot and / rootfs. Using a card reader and dd, I created an image by
Code:
dd if=/dev/sdc of=~/sdcard.img
and then restored it to an identical SD card with
Code:
dd if=~/sdcard.img of=/dev/sdc
The cloned SD got the same UUID's and booted fine -- dd got the whole card with /dev/sdc even though there were 3 partitions (sdc1, 2 and 3). However, it took a long time -- 20 min to create the image and 50 min to restore it to the new card. I've used tar only a little -- it would probably be faster and I could then use it to backup minor changes to debian. My only concern is getting the formatting right and the partition table etc. How would I do that? Or is there a way to get dd to work faster?

EDIT: The process detailed above works fine, but there is a better, faster way to maintain a backup SD card than using dd each time. After making and testing the initial cloned SD card, use rsync to periodically copy the contents of the / and /boot partitions to a hdd. A backup SD card cloned as above can be synced fairly quickly from the hdd backup. Be sure to use rsync with the "-a" option to preserve ownership and permissions. This seems to work pretty well, but if there's a better way to do this, please tell.

Regards,
feffer
42  General Category / General Discussion / Shutting off the Plug on: May 15, 2010, 02:27:57 PM
I've just started using my SheevaPlug and wonder what's the proper way to shut it down. "Halt" seems to shut debian down, but there's no hardware off switch so it looks like the only option is to "pull the plug." Am I wrong about this? Is there a proper way?

thx
feffer
43  General Category / General Discussion / Re: GuruPlug - Received Yours Yet? on: May 15, 2010, 02:18:20 PM
Ordered the GuruPlug server plus in February and got it (in Northern CA) on May 13th. I called them two weeks ago to ask for shipping status. The operator checked my order and said it had been sent to "fulfillment" and I should get an email in a day or two. So that stretched out to two weeks.

I'm new to the Sheeva Plug, moving over from a Linksys Slug. So when I placed my order for the GuruPlug+ I also ordered a standard SheevaPlug. They billed me for a single shipping charge, so I worried that they might wait to ship them together, and that is just what they did. However, the whole order arrived and appears to be in good shape. I have the standard plug up and running with Debian. The GuruPlug also came with the free pre-ordered jtag connector. I'm content to spend time setting up the standard Sheeva and will watch the forum for info about the GuruPlug.

I don't give Globalscale high marks for customer service, but I was able to reach them by phone and as I said everything did get here and it was well-packed.

Regards,
feffer

btw, Blüto I watched your youTube vid and was confused by one thing you said. You referred to the figure 8 connector as a European one, but I thought it was just an extension cord that could be used in the U.S. as well.
44  General Category / General Discussion / Re: Debian installation problem on: May 13, 2010, 10:50:36 PM
OK, I see my mistake. I started the installer wrong by copying both lines as one. Sorry
45  General Category / General Discussion / Debian installation problem on: May 13, 2010, 09:01:09 PM
I'm trying to install debian squeeze to an external usb hdd on a standard sheeva plug using Martin Michlmayr's instructions. I get a kernel panic
Code:
after doing:  > ext2load usb 0:1 0x00800000 /uImage
....
[    1.030000] List of all partitions:
[    1.040000] 1f00            1024 mtdblock0 (driver?)
[    1.040000] 1f01            4096 mtdblock1 (driver?)
[    1.050000] 1f02          519168 mtdblock2 (driver?)
[    1.050000] No filesystem could mount root, tried:
[    1.060000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
How can I resolve this?

thx,
feffer
Pages: 1 2 [3] 4