[Fabio72]

(7th Mar, 2014 04:50 PM)mk01 Wrote:  why (mostly) nobody is using XBIAN-CONFIG (CLI/XBMC) to update, but directly tries the "hacker" way in terminal? I don't mean the question in a stupid way - but as honest question.

is it lack of this info? or other reasons?

as we spent quite much time with delivering this function (to be easy of use, troubles free etc) specially because such complications with apt (when apt-get changed to more strict way of operations).

XBIAN-CONFIG handles then those dependencies automatically while simply installing all needed updates & prerequisites - after user confirm this with few clicks - offloading user's involvement almost down to zero.

I'm used to work on linux by console, so in my case is a sort of professional distortion.

Moreover, after installing beta2 i tried to upgrade twice by XBIAN-CONFIG-CLI and once by XBMC and every single time I got errors and xbmc or even xbian not starting.
When I saw an user giving upgrade instructions using apt-get I made a last try and i was successfull.

---

(7th Mar, 2014 03:34 PM)mk01 Wrote:  remove rootfs entry completely from /etc/fstab. those lines (like rootfs for instance) are only resemblance of times decades ago when we had on linux only one way to get filesystem info (through accessing "manually" handled entries).

by any case, rootfs should still not appear on list of filesystems for autofs - I will fix that.

I was not talking about the false "rootfs" mount problem, but I got also two
192.168.1.8:/srv/Xbian on / type nfs
192.168.1.8:/srv/Xbian on / type nfs

Then I can "umount /" and only one of them is left.

Quote:the "double" mounted filesystem I was already explaining somewhere. it is not double mounted - it is the way how autofs works. it won't mount filesystem until really needed - accessed. so it is installing ioctl trigger there (it looks like fs would be mounted - on mount or df list). but it is not mount.

mount will occur when you access any entry in it's dir/subdir (and until not mounted, access is blocking io call - what is one of the benefits as application is force waiting - and will not return error or file not exists in case of access and late mount).

if you say only two are mounted can be that those are accessed very early on your setup. the others have not yet been accesses thus mount wasn't needed yet.

I have ~7 filesystems in fstab, only one is mounted on boot (xbmc's shared userdata dir). other entries are mounted upon requirement.

I'm more used to work with server distributions, so when I put an entry in fstab I must see it mounted after boot

Quote:actually it is

Code:

sudo xbian-config packages updatedb

I just tried (I can ssh from work) and the output was 1
I will try later to launch the gui xbian-config

Quote:downgrade to xbian-package-cec version which was on beta2.

I'm a bit too lazy to do this test
when CEC doen't work after boot I just have to do few clicks on the TV remote to make it work again