Quantcast
Channel: PirateBox Forum - Raspberry Pi(rate)Box
Viewing all 1863 articles
Browse latest View live
↧

Re: Pi(rate) box on Pi2B

June 13, 2015, 9:26 am
$
0
0
I have a torrent link in the developer forum which points to an archlinux for arm6.
It is only about 277 mb in size, so I would go with the archlinux path, too.
↧
Search

Re: RaspberryPI USB wifi compatibility list

June 14, 2015, 2:08 pm
$
0
0
Mathias,
The Alfa AWUS036AC WiFi adapter is not compatible with this distro of Arch. Although Alfa's website posts a Linux driver but I haven't been able to get it to work with this distro. Any ideas?
↧
↧

minidlna permission issue

June 16, 2015, 7:21 am
$
0
0
hi.

I have installed piratebox on my rpi b+.

At the end of the post-install instructions, it is said to run 
systemctl start minidlna
But it is not that simple. Running 
systemctl status minidlna
shows it failed to start with permission issue.

minidlna can't create the sqlite database in /opt/piratebox/tmp. I fixed that with ACL, running 
setfacl -m u:minidlna:rwx /opt/piratebox/tmp
setfacl -m mask::rwx /opt/piratebox/tmp

But this not enough. I have uploaded a file and the file dropped in /opt/piratebox/share/Shared has only -rw------- permission so it's not readable by minidlna again. so minidlna can't update its database...

How do I fix droppy config so that files droppped are 644 by default ? change its umask ?

Even though, I have manually changed permission of files in /opt/piratebox/share/Shared, I still can't see any files when I try to access minidlna with vlc from over the LAN. I don't know if it's vlc failing or minidlna.

Note: you really need to fix this mess...
↧

Re: minidlna permission issue

June 17, 2015, 10:36 pm
$
0
0
Hi,

I tried your steps on my raspberry pi. My configuration might be different because I moved /opt/piratebox/share/Shared to my external usbdrive.
I am able to start the minidlna Service and it is now in status active(running).

Can you tell me more about your configuration?
↧

Re: minidlna permission issue

June 18, 2015, 2:25 am
$
0
0
If you use an external usbdrive, then it is the mount permission option that matters.

But in my case, I did not use any external drive. /opt/piratebox/share/Shared is the same as after the install. Except the change I made with getfacl.

And yes after the step I have described, the minidlna service is running with active status. The problem is that without those extra steps it is not by default.
↧
↧

WPA on Raspberry Pi(rateBox) running PirateBox 1.0.2 OS

June 18, 2015, 8:54 am
$
0
0
I'd like to set up a password for the WiFi network my PirateBox generates. I'm using the PirateBox installation image based in Arch, a distro I have no familiarity with. Through tutorials I managed to get everything set up and working, but now the only tutorials I see for setting up encryption are for Raspbian (my system has no /etc/network/interfaces file to edit).

How do I do this on the Arch version of PirateBox? (If it's of any consequence, I'm using the Edimax EW-7811Un)

Thanks!
SG
↧

Re: minidlna permission issue

June 18, 2015, 3:26 pm
$
0
0
Thank you for telling us about the problem.
We found the origin and will fix this in the next update.
I am going to update the post-install instruction very soon.
↧

Re: minidlna permission issue

June 18, 2015, 5:47 pm
$
0
0
Why do files dropped in /opt/piratebox/share/Shared (via upload feature) get the wrong permission ?
↧
Search

Re: RaspberryPI USB wifi compatibility list

June 19, 2015, 5:05 am
$
0
0
hi, i bought a tl-wn822n to create an AP on my RPI2 and i can't anymore.
can you give me your hostapd please?
↧
↧

Fix for droopy and minidlna

June 19, 2015, 5:31 am
$
0
0
Following my post about minidlna permission issue, I have found out that dropped file via the upload feature of Piratebox (into /opt/piratebox/share/Shared) have by default permission -rw-------.

This make those files unreadable by minidlna, and minidlna can not update, nor provide the newly dropped files.

So minidlna is still broken, even if you have taken care of the permission issue mentionned elsewhere.

Here is the fix for this: 
--- /opt/piratebox/bin/droopy	2015-06-19 11:33:20.216375704 +0000
+++ /opt/piratebox/bin/droopy.2	2015-06-19 11:33:30.306281245 +0000
@@ -918,6 +918,7 @@
                 fout = file(localpath, 'wb')
                 shutil.copyfileobj(fileitem.file, fout)
                 fout.close()
+            os.chmod(localpath, 0644)
             self.log_message("Received: %s", os.path.basename(localpath))
 
             # -- Reply
This will add one line in droopy to automatically change permission on dropped file to world-readable. That way minidlna will notice the file, read it and update its database, and provides the newly dropped file.

By the way, what have you done to droopy file ? This is an utf-8 encoded file. This is important for the localised string and translation in the file. But you have managed to mess it up and now it's garbage. Instead of getting a nice 'Fichier reçu' when I drop a file I got a weird character... I don't even talk about korean or chinese where it should be garbage and unreadable...
↧

Re: minidlna permission issue

June 19, 2015, 1:25 pm
$
0
0
There are two folders with ownership nobody.nogroup:
/opt/piratebox/tmp
/opt/piratebox/share

I modified the permission of the tmp folder to 777 and noticed the owner of the sqlite file was minidlna.minidlna.
This means, the permission was correct but ownership did not match the configured minidlna service in
/usr/lib/systemd/System/minidlna.service

This file is in the pacman package and we need to make sure that the different services work together without digging holes into the filesystem security.

I want to test this configuration before updating the build scripts and post installation instructions.
↧

Re: WPA on Raspberry Pi(rateBox) running PirateBox 1.0.2 OS

June 20, 2015, 2:22 am
$
0
0
Hi SG,

I changed /opt/piratebox/conf/hostapd.conf on the archlinux distro. 

interface=wlan0
driver=rtl871xdrv
ssid=PrivateBox
hw_mode=g
channel=1
ieee80211n=1
wmm_enabled=0
wpa=1
auth_algs=1
wpa_passphrase=first123
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP
macaddr_acl=0

Just give it a try.
↧

Re: minidlna permission issue

June 20, 2015, 4:06 am
$
0
0
I'm glad you finally understood the problem ;-)

You can either use ACL like I did or force minidlna to run as nobody user or include it in nogroup group so that minidlna get the correct permisison to access the files it needs.
↧
↧

Re: Banana Pi is there an image

June 23, 2015, 12:26 am
$
0
0
I'm bumping this as it's been some time without any word, is there an image yet? The banana pi has native sata
↧

New image avaliable for Raspberry Pi

June 23, 2015, 12:25 pm
$
0
0
Hi everyone,

I have a new image for raspberry pi (the old one with ARMv6) CPU.
    [*] Includes kareha imageboard
    [*] Fixed dlna permission
Language: HTML
magnet:?xt=urn:btih:b419cc4c736c8cc6a2120d86148a30ca200b488b&dn=ArchLinuxARMv6-2015-06_PirateBox1.0.2_rpi_1.0.5.img.zip&tr=udp%3a%2f%2ftracker.istole.it%3a80%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a80%2fannounce&tr=udp%3a%2f%2ftracker.publicbt.com%3a80%2fannounce

Have fun and send some feedback, please. (:P)

Regards
BlueSpider
↧
Search

Re: New image avaliable for Raspberry Pi

June 24, 2015, 10:15 am
$
0
0
made sticky, added to our torrent - client
I also adjusted you headline
Seems it take a while until we have it on the server. :(
↧

Re: Mising imageboard files in ArchLinuxARM-2014.10-PirateBox1.0.2_rpi_1.0.1.img.zip

June 24, 2015, 10:16 am
↧
↧

Re: New image avaliable for Raspberry Pi

June 24, 2015, 10:37 am
$
0
0
Ok, so upload on you side seems to work better now. in 50 minutes the image is ready.

I already exchanged the links on piratebox.cc , so please handle incoming requests :) B)-
↧

Re: Fix for droopy and minidlna

June 24, 2015, 1:37 pm
$
0
0
Hi,
just to let you know about it.
I added your patch into the current image.

Thank you for your support :)-D
BlueSpider
↧

Re: Fix for droopy and minidlna

June 25, 2015, 7:58 am
$
0
0
thank you for that fix.
I opened a github issue for fixing that. #109.
These changes shouldn't be only on the image itself, it should be in the origin changed, too.

About the utf8 problem, to be honest, no idea what happended. Maybe it would be worth to take the original script and reapply our changes. #110
↧
Viewing all 1863 articles
Browse latest View live
Search