beta2

[mk01]

(2nd Nov, 2013 07:55 AM)Smultie Wrote:  I also couldn't SSH in without powercycling it by removing the power cable.

ok, this one case can be a single incident … anytime you will be ready, just try "reboot" from command line. if you get black screen all times always with three "flashes" from leds at the end, then reboot and poweroff is swapped. otherwise I will excuse myself telling story about random incidents

[Smultie]

K, let me check it with the latest update to xbian-update_1.0.2-8d

[mk01]

@Smultie crazy man. you have do-while loop running with sleep for 10 seconds between rounds doing apt-get update ? )

[Smultie]

Hey, you keep updating them every 30 minutes man
On a side-note, the last reboot worked as expected, so let's consider it just a fluke !

[mk01]

ok, thanks

[CurlyMo]

The latest updates of today from before 22:55 made my RPi unusable slow. Couldn't figure out what it was because SSH was not usable due to slowness.

[mk01]

@CurlyMo

there is still chance it was upstart job respawning. upstart is keeping own logs at /var/log/upsytart. you can check whether any of the logs is not interestingly big in size.

[CurlyMo]

(2nd Nov, 2013 08:27 AM)mk01 Wrote:  @CurlyMo

there is still chance it was upstart job respawning. upstart is keeping own logs at /var/log/upsytart. you can check whether any of the logs is not interestingly big in size.

I could if the system wasn't unusable slow

[mk01]

they are preserved during reboots. and syslog doesn't need to be enabled.

only if you are trying to say that you re-flashed.

[CurlyMo]

Yes, because i also control my lights and TV with that RPi

[mk01]

(2nd Nov, 2013 03:02 AM)lordgandhi Wrote:  I'm sorry, but I'm not sure what you mean by your second part, since input1 and 2 correspond to the mouse respective keybooard parts of my MCE remote. I'm not surce if you want me to create ohter devices in /dev and if so I don't know how to do that.

I know what they are. My question is, whether you can go around the lock on /dev/input/eventX file by creating new file pointing to the same device, but different name / file which you would access then.

there is mknod command and ls -la.

Code:

root@xbian02:/dev/input# ls -la /dev/input/event0
crw-rw---T 1 root input 13, 64 Nov  1 23:39 /dev/input/event0

first small c means 'character device', 13, 64 means MAJOR and MINOR number. so you can:

Code:

mknod /dev/input/event_manual_99 c 13 64

but i'm not sure whether the lock is active only on file level or it is going deeper into kernel and device handling.

[CurlyMo]

Another small detail. When i put the SD card in my windows machine it get the question what i want to do with "boot". I would suggest changing the boot partition label to xbian or xbian-boot instead of just boot.

[waterpolo]

I love the new features from beta 2.
Only playing ISO file is not working with beta 2. I can play ISO files with 1.1.
Please fix this and beta 2 is ready for RC.

[Killerbee]

@belese
Before it was possible to add two MPG2 (or WVC1) licence codes (comma seperated). Now it is not allowed anymore. Could you please make it possible again?

@mk01
I booted your latest image and run some apt-get install commands. The first one took verry long (I mean more than 15 minutes!). After that the speed was normal. Could it be that some btrfs defrag is running just after filesystem resize?

Second issue I had: I was unable to add a "Moviemeter" scrapper. I could not find any addon!
Maybe we need to set-up some repo?

KB

[CurlyMo]

A feature request i heard of when i was still a dev was that XBian should be able to have multiple repositories for each released version, and a development repository. This way, old versions can still be maintained without getting in conflict with newer packages. I'm currently successfully experimenting with such a setup for pilight.

I updated the apt repo creator to allow for this functionality.

What you need to do is the following.

1) Create a folder for each repo version you want to create. In this case they are called devel and stable.

Terminal

drwxrwxr-x 0 root root 0 nov 2 23:03 debs
drwxrwxr-x 0 root root 0 nov 2 23:41 devel
drwxrwxr-x 0 root root 0 nov 2 23:35 dists
drwxrwxr-x 0 root root 0 nov 2 23:41 .gnupg
-rwxrwxr-x 1 root root 15 nov 1 23:54 password
drwxrwxr-x 0 root root 0 nov 2 23:35 stable

2) Add the debs you want to add in this specific repo version and with the update.sh

Terminal

totaal 2048
-rwxrwxr-x 1 root root 198526 nov 2 23:23 pilight1.0.deb
-rwxrwxr-x 1 root root 7404 nov 2 23:42 update.sh

3) Edit the update.sh file and especially the APTNAME and APTDESC variable:

Terminal

NAME="pilight";
LABEL="pilight repository";
APTNAME="devel";
APTDESC="pilight development apt repository";
PASSFILE="../password";
PREFIX="../";
GNULOC="../.gnupg";

4) Run the update.sh in each folder.

5) In my case, a devel and a stable repository are created:

Terminal

dists/:
totaal 0
drwxrwxr-x 0 root root 0 nov 2 23:41 devel
drwxrwxr-x 0 root root 0 nov 2 23:35 stable

dists/devel:
totaal 3072
-rwxrwxr-x 1 root root 1440 nov 2 23:41 InRelease
drwxrwxr-x 0 root root 0 nov 2 23:35 main
-rwxrwxr-x 1 root root 903 nov 2 23:41 Release
-rwxrwxr-x 1 root root 490 nov 2 23:41 Release.gpg

dists/devel/main:
totaal 0
drwxrwxr-x 0 root root 0 nov 2 23:41 binary-armhf

dists/devel/main/binary-armhf:
totaal 3072
-rwxrwxr-x 1 root root 0 nov 2 23:41 Packages
-rwxrwxr-x 1 root root 29 nov 2 23:41 Packages.gz
-r-xr-xr-x 1 root root 126 nov 2 23:41 Release

dists/stable:
totaal 3072
-rwxrwxr-x 1 root root 1436 nov 2 23:35 InRelease
drwxrwxr-x 0 root root 0 nov 2 23:34 main
-rwxrwxr-x 1 root root 899 nov 2 23:35 Release
-rwxrwxr-x 1 root root 490 nov 2 23:35 Release.gpg

dists/stable/main:
totaal 0
drwxrwxr-x 0 root root 0 nov 2 23:35 binary-armhf

dists/stable/main/binary-armhf:
totaal 3072
-rwxrwxr-x 1 root root 0 nov 2 23:35 Packages
-rwxrwxr-x 1 root root 29 nov 2 23:34 Packages.gz
-r-xr-xr-x 1 root root 121 nov 2 23:35 Release

6) Also each repository will have his own pool subfolder so packages don't overwrite each other:

Terminal

pool/:
totaal 0
drwxrwxr-x 0 root root 0 nov 2 23:57 devel
drwxrwxr-x 0 root root 0 nov 2 23:57 stable

pool/devel:
totaal 0
drwxrwxr-x 0 root root 0 nov 2 23:57 main

pool/devel/main:
totaal 0
drwxrwxr-x 0 root root 0 nov 2 23:57 p

pool/devel/main/p:
totaal 0
drwxrwxr-x 0 root root 0 nov 2 23:57 pilight

pool/devel/main/p/pilight:
totaal 1024
-rwxrwxr-x 1 root root 199380 nov 2 23:57 pilight_1.1-1_armhf.deb

pool/stable:
totaal 0
drwxrwxr-x 0 root root 0 nov 2 23:57 main

pool/stable/main:
totaal 0
drwxrwxr-x 0 root root 0 nov 2 23:57 p

pool/stable/main/p:
totaal 0
drwxrwxr-x 0 root root 0 nov 2 23:57 pilight

pool/stable/main/p/pilight:
totaal 1024
-rwxrwxr-x 1 root root 198526 nov 2 23:57 pilight_1.0_armhf.deb

7) If users want to use one of the repositories they can simply use:

Code:

deb http://apt.xbian.org/ stable main

or

Code:

deb http://apt.xbian.org/ devel main

Or both.

However, it would be great if we can have these so users can choose any of them:

Code:

deb http://apt.xbian.org/ beta1 main
deb http://apt.xbian.org/ beta1.1 main
deb http://apt.xbian.org/ beta2 main

In the current situation, you can change:

Code:

deb http://xbian.brantje.com/ wheezy main

to

Code:

deb http://xbian.brantje.com/ beta1.1 main

and

Code:

deb http://xbian.brantje.com/devel wheezy main

to

Code:

deb http://xbian.brantje.com/ devel main

By using this method, the old repository can always exists next to newer versions which will result in more happy users