Posts by escalade

Probably best done with a check-box in the provider setup dialog and then an ip-up script in the generated OpenVPN config file. I don't use any VPN addons myself so that's just a suggestion, there are a number of ways it could be done.

I don't see why an addon would throw away your autostart.sh, that would make a lot of people angry. It should be fine to use that. You can use tun+ instead of tun0 if you happen to have more than one VPN at a time as well. Yes, systemd is another way of running scripts during start.

extremeaudio

DDNS is simply a way to update a DNS name with your external IP address. It does not in any way expose any services for you. You would need to forward ports to the service you like to use externally, which isn't recommended because of obvious security concerns. If your router has some kind of VPN server that would be a better option.

Quote from infinity85

Code

iptables -F
iptables -A INPUT -i tun0 -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A INPUT -i tun0 -j DROP

No need for the -F (flush) as there are no rules to begin with. Even if there was, you probably wouldn't want to flush them.

It's a good idea to filter unrelated packets if a one-directional VPN is what you want, but there might be people that don't want this too. In any case, this can be implemented in the addon itself as a per-VPN option. Definitely does not belong in the first run wizard.

Come on, too lazy to read the first page?

That binary is not included, use ssh-keygen and scp.

DaRKeN

You can put the pactl command in autostart.sh, it needs to be run every boot.

bibi

I don't know.

It's a well known fact the NTFS R/W driver under linux is using FUSE which is user space and dog slow. For performance use any filesystem that is natively supported by the kernel. You should probably use EXT4 over EXT3 as well.

The storage partition can be completely empty it will self populate. Simply create a new filesystem on it and boot.

I agree, and that's why I changed the order in the first place. Let's have someone actually test this before considering anything further.

You can still playback 10bit media just not with hardware acceleration. Doesn't matter much as NUCs are fast enough anyways.

outcave

Nobody confirmed it yet, it's simply a theory although since you say it started in .008 it might be correct. If you can do the test I suggested and report back I'll create a PR to change it once you have confirmed. Might be in time for the next alpha.

LibreELEC have udev rules for it and retroarch-joypad-autoconfig supports it so it should work out of the box.

It might well be related to this change.

I wrongly assumed in the past that Kodi didn't use Samba for SMB, but it seems it does use libsmbclient. Kodi might be trying to look up the name through the hosts file and fail instead of trying bcast next like it should logically.

Someone with this issue should try to copy /etc/samba/smb.conf to /storage/.config/samba.conf and edit

name resolve order = host bcast wins

To this:

name resolve order = bcast host wins

Then restart Kodi.

Probably a better default anyway since most users won't edit their hosts file.

Oh and I wonder if this means an upgrade to Samba would automatically let Kodi use SMB2/3.

Quote from infinity85

Do you happen to know whether this will be changed somewhen as default?

Not to my knowledge. I'm sure if you could document that a different default block size would be beneficial a change would be considered.

Quote

If I understand it correctly, you suggest I put the card into my Laptop (Windows machine), use e.g. MiniTool Partition Wizard or similar to reformat the second partition with some other blocksize, yes?

No, I would never recommend using Windows to create Linux filesystems.

Quote

Any recommendation which blocksize / filesystem would be best?

I have no idea, you are the one who brought this up so you should know

Probably no thought behind it at all, as they just go with the default:

LibreELEC.tv/installer at master · LibreELEC/LibreELEC.tv · GitHub

You can simply backup your /storage, overwrite the filesystem with the block size you want and then restore.

This was answered in the same quote as well.... You can always "rm /storage/.config/usepulse" and be back where you started.

If you follow the first Makefile, you'll see that a "make image" runs "scripts/image". You should read that to get a better understanding of how packages are installed. Basically, everything gets installed in there through running "scripts/install package". I simply add dependencies to the "oem" virtual package which is already included in scripts/install. The scripts locates package.mk inside any subdirectory in there.
[hr]
I've got both mame2010 and mame2014 running on the rpi now after borrowing some cross compilation patches from lrusak They work good but you can see small slowdowns in some games on '10 and on most games with '14. The binary size of '10 is 50MB and '14 is 97MB. Guess it's like they say, later versions of mame are more accurate but at the cost of performance. Also the rpi isn't very powerful. Everything is silky smooth in the mame2003 core though.