[SOLVED] RPi invisible on network / nmbd issue

[mk01]

@mrpi @Skywatch

if you want the background that happened:
- since B2 there is upstart on XBian taking care of boot process
- unfortunately the "debian way" of providing long-term backward compatibility means:
- upstart IS really the one which starts first but contains only bare minimum of native jobs - actually to very soon in boot process call again the old sysv system (what very much means only ONE more system to take care of with no benefits)
- so since then XBian is slowly doing the migration on its own (if feasible with respect to integrity of the system - in that case by utilising .override files - if there is PKG native .conf file, user (or we at XBian) can create .override file. any info/config param provided in override file takes precedence for upstart (clean and user-easy way hot to override system functions but actually not touch the system files)

a while ago we did that for samba (smbd/nmbd processes). in advance we shipped .override file - to have system already tuned at the time when updated samba package hits debian stable repo meaning it will also rm old sysv boot script and will place own into /etc/init.
but due to bug inside samba native pkg installer script, old sysv was removed, but new wasn't placed. into /etc/init. for upstart .override file is not considered at all until original .conf exists - what is ok, otherwise it would be a place to hack actually.
so on the day raspbian installed samba update, it broke nmbd loading at boot.

normally we would find that before user - but there our part kicked in - because wheezy will soon turn into jennie, we do all the development & test on primarily on jennie. but because jennie version of upstart is much ahead of the one in wheezy - it has deployed .conf file for nmbd long ago and all was fine (for all imx6 users and devels).

so something what you cant see until properly reported - then it was easy to track down. so so now you how such empty command as touch can solve this - because it creates (although empty) conf file for nmbd, upstart reads it - creates internally JOB nmbd, then looks for override - and because XBian provided this in advance nmbd is properly started from that configuration.

but yes, indeed funny - try to convince a system administrator (from user perspective) that REALLY creating and empty file made SAMBA working again.
but no magic again

I'm just pushing xbian-update containing among others also that fix so it will be distributed today - unfortunately I couldn't find the 3rd buggy line (maybe more, who knows) removing samba mounts from fstab ... so do a backup because your gets again removed ... but I have not forgotten about that